| Summary: | kernel loads the module tulip for a davicom ethernet card when it must be dmfe | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | Diego Jacobi <djacobi> |
| Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
| Status: | VERIFIED CANTFIX | ||
| Severity: | major | CC: | dsd |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | 3 configs files | ||
|
Description
Diego Jacobi
2005-12-19 16:09:52 UTC
(In adition to comment #0) after booting with the modules.autoload.d/kernel-2.6 loading the dmfe, the order change again eth0 = module dmfe or tulip = davicom card = work fine with both modules loaded at the same time eth1 = module 8139too = Realtek card = work thanks Definitely not a gernkenel problem and looks like a configuration issue. Can somebody else read through this and check? Thanks. (In reply to comment #2) > Definitely not a gernkenel problem and looks like a configuration issue. Can > somebody else read through this and check? Thanks. > i understand which genkernel or, more precisely the initrd provided, doas the autodetection. I think it is an autodetection bug. Well, the tulip driver can drive the davicom card, but only if the suboption "Davicom DM910x/DM980x support" has been selected in the Tulip menue.... So it indeed can be a genkernel/user error (missing selection) problem.. @Diego: Can you please provide your kernel config? Also, with what driver did you noticed this problem and have you already tried with a more recent kernel? About the interfaces names, that's a common problem. Sometimes a kernel modules just takes 1ms more to load in a newer kernel than the last stable version and happends that it registers the interface first. In this case, the ethernet interfaces "switch" modules. What I advise is to setup udev rules to force a interface name for a fisical ethernet card based on the MAC address of it. In my lappy, for example, I have a interface named "lan" and another named "wlan", no matter witch one gets initialized first. Buah... sorry, Replace "Also, with what driver" with "Also, with what kernel" Created attachment 77781 [details]
3 configs files
hi, since it was a long time ago, i really cant remember what exactly file was but i have a clue.
in the attached file are 3 files. the first one i create was the genkernel config file.
before see which dmfe was my driver and test it working, i recompile the kernel for my own striping all other unneeded drivers, and compiling on the kernel my drivers to not use any autodetection tool.
the was the second config file denoted as kernel without a v..
the third was for adding support for some networking stuff (i dont remember now what)
the kernel versions are on the file names respectively.
What i saw in the genkernel was that when i first compile it with the default options it doasnt work with my eth card with the tulip loaded, and on the live cd it works fine.
then i test for the module dmfe and it works. and then again on the kernel was the missing feature for the tulip module which doas the compatibility with my card.
i will look for udev it seems to be what i was looking for, but i made an script for gentoo to alias my connections and getting all the information which i need for my firewall.
Apparently there is no clear answer which driver works best: http://www.ussg.iu.edu/hypermail/linux/kernel/0107.3/0279.html tulip is the more generic driver, and davicom tried to clone tulip in their device, but apparently made a mess of it. I'm doubtful if it would get fixed, but you could try filing an upstream bug after testing tulip on the latest development kernel (currently 2.6.16-rc2) at http://bugzilla.kernel.org genkernel: you may wish to consider prioritising dmfe above tulip. If not, please just close this bug, there is no easy fix. dsd: adding you so you know what's going on with this. Genkernel doesn't load any network drivers at any point. Most likely, the problem is that the genkernel kernel *configures* both drivers by default. It appears that it is coldplug/some other service actually loading the module and causing the error. It sounds like the only solution possible from genkernel would be to *not* build the tulip module, which isn't acceptable as it would break many more network cards than it would fix. My suggestion is for the user to add "tulip" to /etc/hotplug/blacklist or to build a kernel using his own configuration without tulip enabled. (In reply to comment #9) > Genkernel doesn't load any network drivers at any point. Most likely, the > problem is that the genkernel kernel *configures* both drivers by default. It > appears that it is coldplug/some other service actually loading the module and > causing the error. It sounds like the only solution possible from genkernel > would be to *not* build the tulip module, which isn't acceptable as it would > break many more network cards than it would fix. but this doasn't explain why the universal cd have the compatibility support for davicom cards on the tulip driver enabled by default and making a default genkernel doas not. I didn't test the latest genkernel to see if it is fixed but i think which all the problem is just this, enabling compatility support on the tulip driver by default, this wont break any other card (the universal cd works very fine or not?) Coldplug or whatever uses the tulip driver for this cards and it is fine if the tulip driver is configured with compatibility support for davicom cards. They are the same config for 2006.0 (and 2005.1-r1) so I'm not sure where you're getting that they're different. At any rate, this should be fixed, I guess. |
