Bug 409254

Summary:	rt61pci module not loaded on startup
Product:	[openSUSE] openSUSE 11.0	Reporter:	H. Hansen <cyberbeat>
Component:	YaST2	Assignee:	Michal Marek <mmarek>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jeffm
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description H. Hansen 2008-07-15 14:38:15 UTC

I upgraded from opensuse-10.3. I have a wired and a wireless rt61pci networkcard. 

I can get my wireless card working with modprobing rt61pci and knetworkmanager and unplugging eth0 (for default gateway).

Even if I manually edit the hardware-config-tab to load the rt61pci module, the module is not loaded at next system-start. If I run yast-network-settings without the loaded module, the wireless card seems not to be auto-detected.

I wonder why the opensuse-11 installer detected the wireless card and loaded the kernel module.

Comment 1 Michal Zugec 2008-07-15 14:40:18 UTC

Please provide output from "hwinfo --netcard". Sometimes these happend in kernel ...

Comment 2 H. Hansen 2008-07-15 14:58:09 UTC

12: PCI 0f.0: 0282 WLAN controller
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_1814_301
  Unique ID: y9sn.gohsp1cSoiA
  SysFS ID: /devices/pci0000:00/0000:00:0f.0
  SysFS BusID: 0000:00:0f.0
  Hardware Class: network
  Model: "RaLink EW-7108PCg"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x0301 "RT2561/RT61 802.11g PCI"
  SubVendor: pci 0x1814 "RaLink"
  SubDevice: pci 0x2561 "EW-7108PCg"
  Driver: "rt61pci"
  Driver Modules: "rt61pci"
  Device File: wlan0
  Features: WLAN
  Memory Range: 0xcfff0000-0xcfff7fff (rw,non-prefetchable)
  IRQ: 11 (48700 events)
  HW Address: 00:0e:2e:ca:49:4b
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v00001814d00000301sv00001814sd00002561bc02sc80i00"
  Driver Info #0:
    Driver Status: rt61pci is active
    Driver Activation Cmd: "modprobe rt61pci"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

13: PCI 0d.0: 0200 Ethernet controller
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
  Unique ID: rBUF.IQxIdIhhuH7
  SysFS ID: /devices/pci0000:00/0000:00:0d.0
  SysFS BusID: 0000:00:0d.0
  Hardware Class: network
  Model: "Realtek RT8139"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8139 "RTL-8139/8139C/8139C+"
  SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  SubDevice: pci 0x8139 "RT8139"
  Revision: 0x10
  Driver: "8139too"
  Driver Modules: "8139too"
  Device File: eth0
  I/O Ports: 0xcc00-0xccff (rw)
  Memory Range: 0xcfffde00-0xcfffdeff (rw,non-prefetchable)
  IRQ: 11 (48700 events)
  HW Address: 00:02:44:28:0d:24
  Link detected: yes
  Module Alias: "pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00"
  Driver Info #0:
    Driver Status: 8139too is active
    Driver Activation Cmd: "modprobe 8139too"
  Driver Info #1:
    Driver Status: 8139cp is active
    Driver Activation Cmd: "modprobe 8139cp"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Comment 3 Michal Zugec 2008-07-22 07:19:20 UTC

reassigned to kernel maintainers
mechanism of autoloading expect drivers to correct provide pci aliases

Comment 7 Kay Sievers 2008-07-24 13:29:41 UTC

Btw, udev will always just blindly call modprobe. You can always check what modprobe will do with an modalias string and the modprobe current setup:

  /sbin/modprobe \
    --first-time \
    --verbose \
    --dry-run \
    pci:v00001814d00000301sv00001814sd00002561bc02sc80i00
WARNING: module 'rt61pci' is unsupported
FATAL: Module pci:v00001814d00000301sv00001814sd00002561bc02sc80i00 not found.

Comment 8 Jeff Mahoney 2008-08-08 17:57:16 UTC

Does updating to the latest kernel fix it for you? On my system, I see:

jeffm@galileo:/lib/modules/2.6.25.11-0.1-default>   /sbin/modprobe \
>     --first-time \
>     --verbose \
>     --dry-run \
>     pci:v00001814d00000301sv00001814sd00002561bc02sc80i00
insmod /lib/modules/2.6.25.11-0.1-default/kernel/drivers/misc/eeprom_93cx6.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/lib/crc-itu-t.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/drivers/input/input-polldev.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko
insmod /lib/modules/2.6.25.11-0.1-default/kernel/drivers/net/wireless/rt2x00/rt61pci.ko

Comment 9 H. Hansen 2008-08-08 20:40:19 UTC

I don't know, if this provides the info, but upgrading to newest kernel and after reboot applying the same command as above:


/lib/modules/2.6.25.11-0.1-pae # /sbin/modprobe --first-time --verbose --dry-run  pci:v00001814d00000301sv00001814sd00002561bc02sc80i00
WARNING: module 'rt61pci' is unsupported
FATAL: Module pci:v00001814d00000301sv00001814sd00002561bc02sc80i00 not found.

Comment 10 Jeff Mahoney 2008-08-11 15:58:19 UTC

That's really strange, since it is resolving it as rt61pci to issue the warning, but then isn't fetching the actual module?

The module is there and modules.alias contains the right information.

I'm going to assign this one to the module-init-tools maintainer.

As a note, my test was on x86_64 and the provided test is i586. It shouldn't matter, but apparently does.

Comment 11 Michal Marek 2008-08-19 15:45:05 UTC

Does 'tail -1 /etc/modprobe.d/unsupported.blacklist' show 'include modules.unsupported.blacklist' without any hash-mark? Then this is a duplicate of bug 338188. The workaround is to comment out the last line, then the unsupported blacklist won't apply. module-init-tools in 11.1 will handle this better.


*** This bug has been marked as a duplicate of bug 338188 ***