suse 9.2 pro wireless problem
 

hello
i installed suse 9.2 pro
on ibm r50 with intel 2200 bg wireless
iwconfig is :
o no wireless extensions.

eth0 no wireless extensions.

eth1 ieee 802.11b ESSID:"amphora" Nickname:"(none)"
Mode:Managed Frequency:2.427 GHz Access Point: 00:0D:88:E3:4A:50
Bit Rate=11 Mb/s
RTS thr:off
Encryption key:off
Power Management:off
Link Quality=69/100 Signal level=-30 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:12 Missed beacon:8

sit0 no wireless extensions.


i can ping my router
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=30 time=0.559 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=30 time=0.474 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=30 time=0.480 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=30 time=0.441 ms
still no wireless connection
what is wrong
please help

If you can ping your router, I would suspect it is working, at least a little. What does /var/log/boot and /var/log/messages say about your card? Did you load the correct firmware from YaST Online Update?

Wireless Problem SuSE 9.2 Pro
 

I am having a similar problem with an IBM R31. I wrote to SuSE to get installation assistance on this but they said installation instructions do not include networking. This laptop successfully wirelessly ran SuSE 9.0 Pro and SuSE 9.1 Pro. There are several symptoms. First on boot the wlan0 does not immediately get a DHCP address. The startup routine says "Waiting for manditory devices." After login, I can run ifconfig wlan0 or ifstatus wlan0 and get all the appropriate information.

I then attempt to ping loopback but the system can't resolve the name. I then try to ping the loopback IP address, 127.0.0.1 which does work. I then attempt to ping the wireless adapter's IP address, e.g. 192.168.0.33/24, which works. I then attempt to ping 192.168.0.1, broadband router, which does work but if I attempt to ping off the 192.168.0.0/24 net, I get network unreachable. I took a look at the routing table using the route command and noticed that it looks different to a working setup. Wired connections work perfectly. I attemted the load twice with no luck. I have since wiped the machine and installed Novell's Linux Desktop which works perfectly with the hardware. Any suggestions?

BTW - There is a trackpoint problem with IBMs. You have to pass i8042.nomux=1 to the kernel during load.