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

[Bug 702] New: hotplug tries to load the wrong module.



http://bugs.skolelinux.no/show_bug.cgi?id=702

           Summary: hotplug tries to load the wrong module.
           Product: Skolelinux
           Version: CVS
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configuration
        AssignedTo: nobody@skolelinux.no
        ReportedBy: klaus@astro.uio.no


I have two different pcmcia card in my test-server-laptop, both contain a 
8139-chip. When hotplug tries to load these cards, it fail because it tries to 
load the module 8139cp, which doesn't function with either of these cards, the 
module 8139too is the correct one. 
 
Murasaki manages to load these cards. 
 
When I use hotplug, this is what I see in syslog: 
Apr  8 18:24:52 tjener cardmgr[8203]: socket 1: CardBus hotplug device 
Apr  8 18:24:52 tjener /etc/hotplug/pci.agent: Setup 8139cp for PCI slot 
05:00.0 
Apr  8 16:24:54 tjener kernel: 8139cp: 10/100 PCI Ethernet driver v1.1 (Aug 
30, 2003) 
Apr  8 16:24:54 tjener kernel: 8139cp: pci dev 05:00.0 (id 10ec:8139 rev 10) 
is not an 8139C+ compatible chip 
Apr  8 16:24:54 tjener kernel: 8139cp: Try the "8139too" driver instead. 
Apr  8 18:24:55 tjener 
insmod: /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o: init_module: No 
such device 
Apr  8 18:24:55 tjener insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more informtion in syslog or the output from dmesg 
Apr  8 18:24:55 tjener 
insmod: /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o: 
insmod /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o failed 
Apr  8 18:24:55 tjener 
insmod: /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o: insmod 8139cp 
failed 
Apr  8 18:24:55 tjener /etc/hotplug/pci.agent: ... can't load module 8139cp 
 
When I use murasaki (must then remove hotplug), then the module 8139too gets 
loaded, and the card works, this is what I see in syslog: 
Apr  8 18:46:34 tjener /etc/hotplug/pci.agent: PCI remove event not supported 
Apr  8 18:46:42 tjener murasaki.pci[13965]: device is added 
Apr  8 18:46:42 tjener cardmgr[8203]: socket 1: CardBus hotplug device 
Apr  8 18:46:42 tjener murasaki.pci[13965]: vendor:0x10ec device:0x8139 
subvendor:0x14cb subdevice 0x200 class:0x20000 class_mask:0x0(ignore) 
Apr  8 18:46:42 tjener murasaki.pci[13965]: MATCH(8139cp) -> vendor:0x10ec 
device:0x8139 subvendor:0xffffffff subdevice 0xffffffff class:0x0 
class_mask:0x0 
Apr  8 18:46:42 tjener murasaki.pci[13965]: MATCH(8139too) -> vendor:0x10ec 
device:0x8139 subvendor:0xffffffff subdevice 0xffffffff class:0x0 
class_mask:0x0 
Apr  8 18:46:42 tjener murasaki.net[13966]: device is registered 
Apr  8 18:46:42 tjener murasaki.net[13966]: execute ifup eth1 
Apr  8 18:46:42 tjener 
insmod: /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o: init_module: No 
such device 
Apr  8 18:46:42 tjener insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg 
Apr  8 18:46:42 tjener 
insmod: /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o: 
insmod /lib/modules/2.4.24-1-386/kernel/drivers/net/8139cp.o failed 
 
Not sure if bugs.skolelinux.no is the right place to bug this.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



Reply to: