[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#405196: Problem installing etch with debian installer and Marvell 88E8001 network hardware.

reassign 405196 linux-2.6
retitle 405196 Two drivers listed for [11ab:4320] causing driver conflict

On Wednesday 03 January 2007 23:38, Geert-Jan Hut wrote:
> > The modules.pcimap for 2.6.18 shows two drivers for your ethernet
> > card: skge and sk98lin. This is unusual.
> > You can also try unload both these drivers (using 'modprobe -r') and
> > then, after only loading one, check again if you can configure the
> > network from the installer menu.
> This worked, using the following sequence during network device
> discovery I enabled the eth1 interface succesfully:
> modprobe -r skge
> modprobe -r sk98lin
> modprobe skge

OK, so it is a driver conflict. Reassigning to the kernel team.

The relevant device is 11ab:4320. In modules.pcimap:
skge        0x000011ab 0x00004320 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
sk98lin     0x000011ab 0x00004320 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

> I completed the installation and rebooted, which kept networking
> enabled. But after rebooting both drivers were present again. Removing
> the skge interface disabled networking, removing the sk98lin module
> didn't do much.

You should be able to blacklist the sk98lin module under /etc/modprobe.d.

> > You could check which kernel version Ubuntu is using and which module
> > is loaded during the Ubuntu installation for reference.
> Ubuntu only loads the skge module. Assuming that the skge driver is the
> only one needed for this ethernet card, maybe the other one could be
> removed also? What is strange of course is that the combination of both
> modules works when starting the kernel, but doesn't work when
> installing debian. I will try to check if the order of installation
> matters.

Yes, the order probably does matter and the order can change from one boot
to the next.

> After applying the changes above, and rebooting I couldn't start up
> GDM, because a number of drivers weren't loaded/ installed, such as the
> xserver-xorg-input-mice, xserver-xorg-input-kdm packages. Also my video
> card wasn't detected (correctly). Could this be caused by the way I
> installed it now? Or should I enter another bug-report for this?

If you can find out a bit more about what may have gone wrong, I suggest
filing a bug report against xserver-xorg-core.


Attachment: pgpuypHKWmoNs.pgp
Description: PGP signature

Reply to: