Bug 113077

Summary: No wifi connection
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Perret Florian <f-perret>
Component: NetworkAssignee: Joachim Gleissner <joachim.gleissner>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: ifcfg-wlan
messages

Description Perret Florian 2005-08-25 16:34:54 UTC
In beta 3, I can't set a wifi connection. I can enter every settings in Yast
with no problem. Like I have an ethenet card too, first I think it was a
conflict between ethernet and WIFI (like the bug in 9.3). But after deleting
ethernet card nothing goes better.
The applet cannot select any interface.
Comment 1 Joachim Gleissner 2005-08-26 08:09:18 UTC
Please attach /var/log/messages, 'hwinfo --netcard' output, 
and /etc/sysconfig/network/ifcfg-wlan-* (you can disguise WEP key or WPA 
passphrase if used). 
Comment 2 Perret Florian 2005-08-26 08:11:49 UTC
yAST is well config, but Kinternet shows me no network to choose. This is my
iwconfig and ifconfig -a :

iwconfig
lo        no wireless extensions.
sit0      no wireless extensions.
eth0      no wireless extensions.
 

ifconfig -a
eth0      Lien encap:Ethernet  HWaddr 00:11:D8:BF:2E:1C
          inet adr:192.168.0.102  Bcast:192.168.0.255  Masque:255.255.255.0
          adr inet6: fe80::211:d8ff:febf:2e1c/64 Scope:Lien
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interruption:185 Adresse de base:0x4c00

lo        Lien encap:Boucle locale
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:97 errors:0 dropped:0 overruns:0 frame:0
          TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:6906 (6.7 Kb)  TX bytes:6906 (6.7 Kb)

sit0      Lien encap:IPv6-dans-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
Comment 3 Perret Florian 2005-08-26 08:25:14 UTC
Created attachment 47718 [details]
ifcfg-wlan
Comment 4 Perret Florian 2005-08-26 08:26:01 UTC
Created attachment 47719 [details]
messages
Comment 5 Perret Florian 2005-08-26 08:27:24 UTC
And hwinfo --netcard' output gives :

23: PCI 200.0: 0200 Ethernet controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
  Unique ID: rBUF.SMQak7ZBX+8
  Parent ID: 6NW+.1yBhv2xnpj4
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "ASUSTeK RTL-8139/8139C/8139C+"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8139 "RTL-8139/8139C/8139C+"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x1045
  Revision: 0x10
  Driver: "8139too"
  Device File: eth0
  I/O Ports: 0xc800-0xc8ff (rw)
  Memory Range: 0xfeaffc00-0xfeaffcff (rw,non-prefetchable)
  IRQ: 185 (no events)
  HW Address: 00:11:d8:bf:2e:1c
  Link detected: no
  Module Alias: "pci:v000010ECd00008139sv00001043sd00001045bc02sc00i00"
  Driver Info #0:
    Driver Status: 8139too is active
    Driver Activation Cmd: "modprobe 8139too"
  Driver Info #1:
    Driver Status: 8139cp is not active
    Driver Activation Cmd: "modprobe 8139cp"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #17 (PCI bridge)

24: PCI 204.0: 0282 WLAN controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4220
  Unique ID: UVH2.9LS7U1W0872
  Parent ID: 6NW+.1yBhv2xnpj4
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:04.0
  SysFS BusID: 0000:02:04.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 2200BG"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4220 "PRO/Wireless 2200BG"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x2701
  Revision: 0x05
  Features: WLAN
  Memory Range: 0xfeafe000-0xfeafefff (rw,non-prefetchable)
  IRQ: 185 (no events)
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004220sv00008086sd00002701bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #17 (PCI bridge)
Comment 6 Joachim Gleissner 2005-08-26 08:43:25 UTC
On beta3 firmware hotplug is broken, and ipw2200 needs this. You can fix it by   
changing "firmware.hotplug.sh" to "udev.firmware.sh"   
in /etc/udev/rules.s/50-udev.rules, line 214. Reload module ipw2200 
afterwards. 

*** This bug has been marked as a duplicate of 112820 ***
Comment 7 Perret Florian 2005-08-26 09:10:47 UTC
With your solution it's better but another problem is already here, "messages"
file gives :

Aug 25 16:32:48 linux kernel: ipw2200: module not supported by Novell, setting U
taint flag.
Aug 25 16:32:48 linux kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network
Driver, 1.0.6
Aug 25 16:32:48 linux kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporation
Aug 25 16:32:48 linux kernel: ipw2200: Detected Intel PRO/Wireless 2200BG
Network Connection
Aug 25 16:33:10 linux kernel: ipw2200: ipw-2.3-boot.fw load failed: Reason -2
Aug 25 16:33:10 linux kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
Aug 25 16:33:10 linux kernel: ipw2200: failed to register network device

What is reason -2 ?
Comment 8 Joachim Gleissner 2005-08-26 09:17:42 UTC
It seems your system lacks ipw-firmware package (is not included in openSUSE). 
You can download it from ftp.suse.com:/pub/suse/i386/10.0/... 
Comment 9 Perret Florian 2005-08-26 10:19:48 UTC
OK, now wofome.
But I should delete the ethernet card to allow wifi to works (same problem
already exists in 9.3) : another bug ?
Comment 10 Joachim Gleissner 2005-08-26 10:34:06 UTC
You can configure the ethernet card with ifplugd (startmode 'on cable  
connection'), so it will use ethernet if plugged in or wlan otherwise. Or use 
scpm to manage different profiles.