Bug 142138

Summary: Strange kernel messages about configuration when inserting WLAN adapter
Product: [openSUSE] SUSE Linux 10.1 Reporter: Michael Stather <kontakt>
Component: YaST2Assignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: snwint
Version: Alpha 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST2 logs

Description Michael Stather 2006-01-09 19:14:58 UTC
I´ve an Acer WLan adapter which used to work with SuSE but after I removed the config from YaST and reconfigured it it doesn´t work any more.
I get this in the kernel log when inserting it:

Jan  9 20:09:31 r098089 kernel: usb 2-1: config 1 has an invalid interface number: 1 but max is 0
Jan  9 20:09:31 r098089 kernel: usb 2-1: config 1 has no interface number 0
Jan  9 20:09:31 r098089 kernel: ident: nic h/w: id=0x8026 1.0.0
Jan  9 20:09:31 r098089 kernel: ident: pri f/w: id=0x15 1.1.0
Jan  9 20:09:31 r098089 kernel: ident: sta f/w: id=0x1f 1.4.10
Jan  9 20:09:31 r098089 kernel: MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
Jan  9 20:09:31 r098089 kernel: CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
Jan  9 20:09:31 r098089 kernel: PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/3
Jan  9 20:09:31 r098089 kernel: STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/9
Jan  9 20:09:31 r098089 kernel: PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Jan  9 20:09:31 r098089 kernel: STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Jan  9 20:09:31 r098089 kernel: STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Jan  9 20:09:31 r098089 kernel: Prism2 card SN: 1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
Jan  9 20:09:31 r098089 kernel: dot11req_reset: the macaddress and setdefaultmib arguments are currently unsupported.
Jan  9 20:09:33 r098089 kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jan  9 20:09:33 r098089 kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Jan  9 20:09:33 r098089 kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
Jan  9 20:09:37 r098089 dhcpcd[10556]: terminating on signal 15
Jan  9 20:09:37 r098089 dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Jan  9 20:09:38 r098089 kernel: dot11req_reset: the macaddress and setdefaultmib arguments are currently unsupported.
Jan  9 20:09:43 r098089 kernel: linkstatus=ASSOCFAIL (unhandled)
Jan  9 20:09:49 r098089 kernel: wlan0: no IPv6 routers present
Jan  9 20:10:02 r098089 kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jan  9 20:10:02 r098089 kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Jan  9 20:10:02 r098089 kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
Jan  9 20:12:18 r098089 su: (to root) michael on /dev/pts/3
Jan  9 20:12:19 r098089 su: (to root) michael on /dev/pts/3

I attached the YaST logs. Perhaps there are some remains from the old configuration (I also filed another bug report which I think is perhaps related to this).
Comment 1 Michael Stather 2006-01-09 19:16:14 UTC
Created attachment 62469 [details]
YaST2 logs
Comment 2 Michael Stather 2006-01-09 19:17:24 UTC
Perhaps this is needed too

r098089:/home/michael # hwinfo --network
19: None 00.0: 10701 Ethernet
  [Created at net.111]
  UDI: /org/freedesktop/Hal/devices/net_00_02_a5_b8_1b_0f
  Unique ID: usDW.ndpeucax6V1
  Parent ID: rBUF.SPbcKWAadaA
  SysFS ID: /class/net/eth0
  SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:02:08.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "e100"
  Device File: eth0
  HW Address: 00:02:a5:b8:1b:0f
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #13 (Ethernet controller)

20: None 00.0: 10700 Loopback
  [Created at net.111]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

21: None 00.0: 10781 Network Interface
  [Created at net.111]
  Unique ID: wl2P.nfEXJulusj6
  SysFS ID: /class/net/sit0
  Hardware Class: network interface
  Model: "Network Interface"
  Device File: sit0
  Config Status: cfg=new, avail=yes, need=no, active=unknown

22: None 00.0: 1070a WLAN
  [Created at net.111]
  UDI: /org/freedesktop/Hal/devices/net_00_01_24_b0_5c_b3
  Unique ID: AYEt.QXn1l67RSa1
  Parent ID: iVWJ.rCwbDvswxUE
  SysFS ID: /class/net/wlan0
  SysFS Device Link: /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.1
  Hardware Class: network interface
  Model: "WLAN network interface"
  Driver: "p80211_prism2_usb"
  Device File: wlan0
  HW Address: 00:01:24:b0:5c:b3
  Link detected: no
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (WLAN controller)
Comment 3 Dr. Werner Fink 2006-01-10 10:01:03 UTC
Why this is an bugzilla entry?  If I read correct it has
worked upto to the point you've removed the configuration.
IMHO this looks like a configuration problem but not a bug.
Comment 4 Dr. Werner Fink 2006-01-10 12:58:23 UTC
Please provide the infos requested in comment #3
Comment 5 Michael Stather 2006-01-10 13:43:29 UTC
I was thinking about these lines in the log:
Jan  9 20:09:31 r098089 kernel: usb 2-1: config 1 has an invalid interface
number: 1 but max is 0
Jan  9 20:09:31 r098089 kernel: usb 2-1: config 1 has no interface number
IMHO this is a bug because I just used YaST to configure the device. If I have a device which works correctly, then remove it and set it up again with the same options in YaST it should work if YaST doesn´t do a mistake somewhere. If it´s a configuration problem there´s something wrong in YaST or some other part since it should write a correct one.
SuSE supports this device and it doesn´t work, so this is a bug IMHO.
And I´m just testing SuSE and don´t really use it for production, so this is not a "support request" from me *g I just like SuSE as bug-free as possible.
Comment 6 Martin Vidner 2006-01-10 15:09:40 UTC
You used to have ESSID and a key but now you don't have it in the config. That looks like the cause of the problem. Or did you disable encryption on your AP?

Did it work before with the same SUSE release? If it was a different one, kernel driver changes can be at fault. 
What is the other bug's number?
Please attach hwinfo --netcard (it is more useful than --network).

Anyway, Steffen, class_id and sub_class_id are zero so yast does not know the card (the config was done manually).
2006-01-07 22:17:28 <3> r098089(16456) [YCP] network/hardware.ycp:163 Unknown controller type: $["bus":"USB", "bus_hwcfg":"usb", "class_id":0, "dev_name":"w
lan2", "dev_names":["wlan2"], "device":"USB2.0 WLAN", "device_id":201233, "driver":"zd1211", "drivers":[$["active":true, "modprobe":true, "modules":[["zd121
1", ""]]]], "hotplug":"usb", "model":"ZyDAS USB2.0 WLAN", "old_unique_key":"6SUI.e__70k4BDK7", "resource":$["baud":[$["speed":12000000]], "hwaddr":[$["addr"
:"00:11:f6:7f:70:7d"]]], "rev":"43.30", "sub_class_id":0, "sysfs_bus_id":"2-1:1.0", "udi":"/org/freedesktop/Hal/devices/usb_device_ace_1211_noserial_if0", "
unique_key":"FKGF.1HPlSPIKalC", "vendor":"ZyDAS", "vendor_id":199374]
Comment 7 Steffen Winterfeldt 2006-01-10 15:15:53 UTC
Hm, what does 'hwinfo --netcard' say? (Note: not net*work*.)
Comment 8 Michael Stather 2006-01-10 15:32:37 UTC
I´m not talking about the card from "Zydas", that´s another thing I filed bug reports for because it doesn´t work. I mean "wlan0" which is an Acer adapter and has a SSID assigned.
I´ll post "hwinfo --netcard" soon
Comment 9 Michael Stather 2006-01-23 22:00:08 UTC
OK since this worked with exact the same setup some time ago (and I did some kernel upgrades since then) it must be a kernel issue. So I´ll try with the latest beta of 10.1. You can close this bug if it doesn´t work I´ll reopen it.
Comment 10 Harald Mueller-Ney 2006-04-23 05:40:56 UTC
Closing regardiing comment #9