| 1 |
Ryan Tandy wrote: |
| 2 |
> Steven G Wagner wrote: |
| 3 |
>> I have a working hardened system, 2.6.16-hardened-r11, but I can't |
| 4 |
>> seem to |
| 5 |
>> get eth0 recognized. My NIC is a Netgear FA310TX Rev D2 and I found |
| 6 |
>> that it |
| 7 |
>> uses the "Tulip" driver. |
| 8 |
>> I've tried compiling this driver by itself into the kernel both |
| 9 |
>> built-in and |
| 10 |
>> as a module. I've tried compiling the entire "Tulip" family of |
| 11 |
>> drivers into |
| 12 |
>> my kernel, trying <*> next to every possible selection under "Tulip" and |
| 13 |
>> again using <m> in every instance allowed. I listed "tulip" in |
| 14 |
>> /etc/modules.autoload.d and it failed at boot, even though it was |
| 15 |
>> compiled |
| 16 |
>> as a module. |
| 17 |
>> Everything is copasetic when I boot off the livecd and I can ping |
| 18 |
>> google, |
| 19 |
>> etc. I tried emerging hotplug as one forum post I found indicated, |
| 20 |
>> but to no |
| 21 |
>> avail. I've done my best to find posts related to this, seemingly, |
| 22 |
>> common |
| 23 |
>> issue, but nothing has worked for me and I can't think of anything |
| 24 |
>> else to |
| 25 |
>> try. I've combed the handbook as well, but nothing there has helped me. |
| 26 |
>> If anyone could help me I would really appreciate it. I have used |
| 27 |
>> Hardened |
| 28 |
>> Gentoo before, but not on this older machine. |
| 29 |
>> Thanks a lot for any help, |
| 30 |
>> |
| 31 |
>> Steve |
| 32 |
>> |
| 33 |
> |
| 34 |
> Hi, |
| 35 |
> |
| 36 |
> I'm using the Tulip driver on one of my older boxes too. Under the |
| 37 |
> "Tulip family" selection in menuconfig, only one of them actually |
| 38 |
> compiles the tulip.o module - I forget the name of it (DEC something), |
| 39 |
> but last time I built a kernel it was second in the list. For it to |
| 40 |
> work properly, I had to enable all the options for the tulip module - |
| 41 |
> new bus layout, interrupt mitigation, whatever other fancy things it |
| 42 |
> has there. Are you sure it's the tulip.o driver you want, or is it |
| 43 |
> some other driver from the tulip family? |
| 44 |
> |
| 45 |
> You said that autoloading failed - can you paste the *exact* error |
| 46 |
> message? What happens if you try 'modprobe tulip' by hand, as root? |
| 47 |
> |
| 48 |
> Ryan |
| 49 |
|
| 50 |
I have a Davicom card and it is under the tulip family as well. I don't |
| 51 |
think you need to load a "tulip" module, I think you need to load the |
| 52 |
one specific for your card. Under the Tulip kernel config, there should |
| 53 |
be one of the others with a "m" in it. If you highlight it then right |
| 54 |
arrow over till help is highlighted at the bottom and hit enter, it will |
| 55 |
tell you the name of the module in there somewhere. |
| 56 |
|
| 57 |
Example, my Davicom uses this: "Davicom DM910x/DM980x support" and I |
| 58 |
have mine compiled in but modules will work too. The module that it |
| 59 |
would have to load is called "dmfe" not tulip. |
| 60 |
|
| 61 |
If you know the kernel and the modules are compiled correctly, try this |
| 62 |
command: "modprobe -l". That is a lower case L and leave off the |
| 63 |
quotes. That should list all the modules that are available to be |
| 64 |
loaded. Pick the correct one and try to load it. If it is not listed, |
| 65 |
then you have other issues. |
| 66 |
|
| 67 |
Hope that helps. |
| 68 |
|
| 69 |
Dale |
| 70 |
|
| 71 |
:-) :-) :-) |
| 72 |
-- |
| 73 |
gentoo-user@g.o mailing list |
Archives