LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 03-01-2008, 01:36 PM   #1
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Rep: Reputation: 19
sis163u on an amilo Li 1818 and slackware


hi

I've got a Fujitsu-Siemens Amilo Li 1818 which came with some other OS preinstalled and a wlan card with a sis163u chip. I repartitioned the disk and put slackware 12 on it, but I cannot get wlan to work. I've got the sis163u driver and installed it with ndiswrapper:
Code:
# ndiswrapper -i sis163u.inf
Then
Code:
# ndiswrapper -l 
sis163u : driver installed
	device (0BF8:100F) present
# modprobe ndiswrapper

# iwconfig wlan0 key open x--------------x
# iwconfig wlan0 essid "Wir"
wlan0     IEEE 802.11g  ESSID:"Wir"  Nickname:"Newton"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:01:E3:77:4F:49   
          Bit Rate=54 Mb/s   Tx-Power:18 dBm   Sensitivity=0/3  
          RTS thr=2312 B   Fragment thr=2312 B   
          Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx   Security mode:open
          Power Management:off
          Link Quality:71/100  Signal level:-50 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

# dhcpcd wlan0
# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:30:05:DA:6F:FE  
          inet addr:192.168.1.102  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:16913 (16.5 KiB)  TX bytes:650 (650.0 b)
I think this all looks ok, but when I try to ping my router, I get this:

Code:
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.102 icmp_seq=1 Destination Host Unreachable
From 192.168.1.102 icmp_seq=2 Destination Host Unreachable
From 192.168.1.102 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
16 packets transmitted, 0 received, +3 errors, 100% packet loss, time 15017ms
What am I doing wrong? It occurred to me that the driver might be incompatible, so I installed pclos on a spare partition, just to see if I could get it working. And it does. With the same driver. Why? Or, more importantly, why can't I get it working with slackware? PCLOS has a gui network setup so I don't really know what exactly happens.

Please help. I would really like to stay with slack.

ros
 
Old 03-01-2008, 02:22 PM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Boy, that looks like it should go without a hitch. The only thing I can think of is that dhcpcd is failing somehow. What is the output of route -n? You're router's IP address should be in the Gateway column, and if it isn't, then something is going screwy with dhcpcd.

Now with that said, I have seen some threads on the Amilo where the kill switch has been a serious problem. You might do some digging in the log files and see if either the card or ndiswrapper are complaining about anything.
 
Old 03-01-2008, 03:54 PM   #3
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
I kind of thought it should be working too!

Here is the output from netstat -r from slackware 12

Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     *               255.255.255.0   U         0 0          0 wlan0
loopback        *               255.0.0.0       U         0 0          0 lo
default         192.168.1.1     0.0.0.0         UG        0 0          0 wlan0
And the same command issued from PCLOS, where it works (I'm using it right now)

Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     *               255.255.255.0   U         0 0          0 wlan0
169.254.0.0     *               255.255.0.0     U         0 0          0 wlan0
127.0.0.0       *               255.0.0.0       U         0 0          0 lo
default         speedport.ip    0.0.0.0         UG        0 0          0 wlan0
I don't know what that 169.254.0.0 is, or if its important...

I tried setting my ip address manually with ifconfig, but I still couldn't talk to the router (192.168.1.1). I reinstalled slackware, because I have a vague feeling, but I can't be sure if my memory is playing tricks on me, that the very first time I installed ndiswrapper it all worked... But to no avail.


Slack is just better and cleaner somehow.

ros
 
Old 03-02-2008, 06:44 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
I tried setting my ip address manually with ifconfig, but I still couldn't talk to the router (192.168.1.1).
In case you didn't know, that is actually a multi-step process, it isn't as simple as adding an IP address. You need to set the IP with ifconfig, set the gateway with route, and then add DNS servers to your /etc/resolv.conf files. When you run a DHCP client, that all happens automatically, but not if you set the IP manually.

To be honest, I don't see any reason why this isn't working. Your output from route -n is correct, as are all the other aspects you've been posting. What is really weird is that dhcpcd works. That strongly suggests that the card is functional. So basically, we're going to have to do some fishing to see if we can find some clues. Here is what I suggest you look at:

- The ability to scan: iwlist wlan0 scan
If that fails, it might suggest a driver problem, but if it works, it is more evidence the card and drivers are fine

- Your firewall: iptables -L
I'm guessing you didn't set up a firewall yet, but it doesn't hurt to look

-Your log files. I'm afraid you're going to have to spend some serious time in /var/log/messages, /var/log/syslog and the dmesg output and see if the card or ndiswrapper are leaving any clues as to what might be going wrong.

By the way, I'm assuming you've installed ndiswrapper from source. If that isn't true, I would try doing it and make sure you've got the latest version, but NOT an rc version. Also, check the ndiswrapper wiki and see what drivers are suggested for your card. If you're already using the suggested driver, you might try experimenting a little anyways. In the deep, dark past, ndiswrapper was very picky about which Windows drivers would work. It hasn't been a problem lately but it still might be worth trying a different driver.
 
Old 03-02-2008, 10:40 AM   #5
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Hi
I have a pristine slack 12 installation with the default kernel. I haven't added any of the security upgrades. I downloaded ndiswrapper v 1.52 and compiled it from source, following the instructions, because I've never needed ndiswrapper before. I don't know much about firewalls; I leave that to our router, perhaps I shouldn't? Thanks for that bit about setting ip manually; I didn't know that.
Anyway, here's a copy of what I typed in, and what happens in messages & system logs at the same time as I loaded the driver..


Code:
root@Newton:~# modprobe rndiswrapper
root@Newton:~# iwconfig wlan0 key open xxxxxxxxxxxxxxxxxxxxxxx
root@Newton:~# iwconfig wlan0 essid "Wir"
root@Newton:~# dhcpcd wlan0
root@Newton:~# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:30:05:DA:6F:FE
          inet addr:192.168.1.102  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:5ff:feda:6ffe/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:34 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12910 (12.6 KiB)  TX bytes:1370 (1.3 KiB)
root@Newton:~# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:"Wir"  Nickname:"Newton"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:01:E3:77:4F:49
          Bit Rate=54 Mb/s   Tx-Power:18 dBm   Sensitivity=0/3
          RTS thr=2312 B   Fragment thr=2312 B
          Encryption key:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   Security mode:open
          Power Management:off
          Link Quality:59/100  Signal level:-58 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
root@Newton:~# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     *               255.255.255.0   U         0 0          0 wlan0
loopback        *               255.0.0.0       U         0 0          0 lo
default         192.168.1.1     0.0.0.0         UG        0 0          0 wlan0

root@Newton:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

root@Newton:~# tail -f /var/log/messages
Mar  2 14:37:53 localhost kernel: NET: Registered protocol family 10
Mar  2 14:37:53 localhost kernel: lo: Disabled Privacy Extensions
Mar  2 14:42:46 localhost kernel: ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
Mar  2 14:42:46 localhost kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 2
Mar  2 14:42:46 localhost kernel: ndiswrapper: driver sis163u (Silicon Integrated Systems Corp.(1.08a.01),06/28/2006,5.1.1039.1081) loaded
Mar  2 14:42:47 localhost kernel: wlan0: ethernet device 00:30:05:da:6f:fe using NDIS driver: sis163u, version: 0x1000000, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 0BF8:100F.F.conf
Mar  2 14:42:47 localhost kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Mar  2 14:42:47 localhost kernel: usbcore: registered new interface driver ndiswrapper
Mar  2 14:42:47 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar  2 14:42:49 localhost logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 nick Newton
Mar  2 14:42:49 localhost logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 essid "W720V"
Mar  2 14:42:49 localhost logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 essid "W720V"
Mar  2 14:42:49 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

root@Newton:~# tail -f /var/log/syslog
Mar  2 14:33:41 localhost kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Mar  2 14:33:41 localhost kernel:  =======================
Mar  2 14:33:41 localhost kernel: kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
Mar  2 14:33:41 localhost kernel:  [<c03e86f7>] kobject_shadow_add+0x117/0x1a0
Mar  2 14:33:41 localhost kernel:  [<c013fba4>] mod_sysfs_setup+0x24/0xb0
Mar  2 14:33:41 localhost kernel:  [<c0141458>] sys_init_module+0x1648/0x1940
Mar  2 14:33:41 localhost kernel:  [<c0102ae8>] syscall_call+0x7/0xb
Mar  2 14:33:41 localhost kernel:  [<c0710000>] __mutex_lock_slowpath+0x40/0x90
Mar  2 14:33:41 localhost kernel:  =======================
Mar  2 14:45:54 localhost kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
That bit in the messages file about W720V is from when I checked if I could contact a router without a wep key. We have a spare router in the house which normally resides in a forgotten drawer in the cellar, but I got it out and plugged it into the mains (not the phone line), booted it up and switched on wlan. It has unencrypted access and the essid is W720V. That line is in rc.wireless.conf. But as you can see when I type iwconfig, the essid is "Wir". The spare router has now been relegated to the cupboard again, after I discovered I could access it without wep, but not with.

I'll look for another driver later on this evening

ros
 
Old 03-06-2008, 09:50 AM   #6
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Well now I'm really puzzled! I tried a version of ndiswrapper (1.48 - which is what pclos successfully uses), but the results were the same. iwlist wlan0 scan returns our ssid and that of our neighbour, but ping says the same old thing. So I booted up with grml, which comes with ndiswrapper 1.50 preinstalled and kernel 2.6.23-grml and did the same old thing - ndiswrapper -i sis163u.inf, modprobe ndiswrapper, iwconfig wlan0 key xxxx open. Then ifconfig wlan 0 192.168.1.102, route add default gw 192.168.1.1, edited /etc/resolve.conf to contain nameserver 192.168.1.1. And here I am. Admittedly, the environment is a bit alien - I've never used links before, so please excuse the total lack of formatting. But Why? I can more or less type these commands in my sleep now - and it worked first time no hiccups, peculiarities, nothing, and it just worked just like that. And I've never used grml before. So just why can't I do the same thing with slackware? Is there something very peculiar about slack that I've never noticed before?
 
Old 03-06-2008, 10:16 AM   #7
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Well now I'm really puzzled. After having zero success with other versions of ndiswrapper (14.8 like pclos uses and has success with), I downloaded grml and booted with that. And here I am. Kernel 2.6.23-grml and preinstalled ndiswrapper 1.50. I did the usual run of commands ndiswrapper -i sis163u.inf, modprobe ndiswrapper, iwconfig wlan0 key xxx open, ifconfig wlan0 192.168.1.102, route add default gw 192.168.1.1, added the following to /etc/resolve.conf: nameserver 192.168.1.1. And that was that. Just like it should be. If only that sequence would work in slackware...

Please help

ros
 
Old 03-06-2008, 12:19 PM   #8
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
OK, this may be a stupid question, but in Slackware, if you set up the card the way you've described can you surf the net? I'm wondering if there is something odd going on with ping rather than a serious driver problem. Because as far as I can see:

- The driver is installed properly
- The driver works (scanning works)
- You can associate with your AP
- You can get an IP address via DHCP
- You're gateway is set correctly

The only thing you haven't posted is your /etc/resolv.conf file after running dhcpcd. If that has nameservers in it, then I am completely stumped.
 
Old 03-07-2008, 04:16 AM   #9
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Hi
I don't think its a driver problem; 2 other linuxes can get this driver running. I must have set something up somewhere incorrectly, but I don't know where to look. This is what I typed this morning. First I set the ip address manually and showed the contents of resolv.conf, then I used dhcpcd. resolv.conf then gets a new value. I think it gets this from the router, because when I type in
Code:
http://192.168.1.1
from pclos or vista, it is redisplayed as
Code:
https://speedport.ip/index.html
Incidentally, this is ndiswrapper v 1.48. The router has been set up to always set my hardware address *A:6F:FE to 192.168.1.102.

Code:
root@Newton:~# ndiswrapper -l
sis163u : driver installed
        device (0BF8:100F) present
root@Newton:~# modprobe ndiswrapper
root@Newton:~# iwconfig wlan0 key open xxxxxxxxxxxxxx
root@Newton:~# ifconfig wlan0 192.168.1.102
root@Newton:~# route add default gw 192.168.1.1
root@Newton:~# cat /etc/resolv.conf
nameserver 192.168.1.1
root@Newton:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.102 icmp_seq=1 Destination Host Unreachable
From 192.168.1.102 icmp_seq=2 Destination Host Unreachable
From 192.168.1.102 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4017ms
, pipe 3
root@Newton:~# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:01:E3:77:4F:49
                    ESSID:"Wir"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:70/100  Signal level:-51 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:54 Mb/s; 48 Mb/s; 36 Mb/s; 24 Mb/s; 18 Mb/s
                              12 Mb/s; 11 Mb/s; 9 Mb/s; 6 Mb/s; 5.5 Mb/s
                              2 Mb/s; 1 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0

root@Newton:~# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:30:05:DA:6F:FE
          inet addr:192.168.1.102  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:5ff:feda:6ffe/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:88 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:32300 (31.5 KiB)  TX bytes:468 (468.0 b)

root@Newton:~#       
root@Newton:~# dhcpcd wlan0
root@Newton:~# cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search ip
nameserver 192.168.1.1
root@Newton:~#

root@Newton:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.102 icmp_seq=10 Destination Host Unreachable
From 192.168.1.102 icmp_seq=11 Destination Host Unreachable
From 192.168.1.102 icmp_seq=12 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
12 packets transmitted, 0 received, +3 errors, 100% packet loss, time 11008ms
, pipe 3
root@Newton:~# tail -f /var/log/messages
Mar  7 10:38:20 Newton kernel: ndiswrapper: driver sis163u (Silicon Integrated Systems Corp.(1.08a.01),06/28/2006,5.1.1039.1081) loaded
Mar  7 10:38:20 Newton kernel: wlan0: ethernet device 00:30:05:da:6f:fe using NDIS driver: sis163u, version: 0x1000000, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 0BF8:100F.F.conf
Mar  7 10:38:20 Newton kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Mar  7 10:38:20 Newton kernel: usbcore: registered new interface driver ndiswrapper
Mar  7 10:38:20 Newton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar  7 10:38:22 Newton logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 nick Newton
Mar  7 10:38:22 Newton logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 key ************
Mar  7 10:38:22 Newton logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 essid "Wir"
Mar  7 10:38:22 Newton logger: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan0 essid "Wir"
Mar  7 10:38:22 Newton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sorry about the double posting yesterday, but I've never used links before and I was getting in a bit of a muddle. I was quite excited that I could get online so easily with grml. Perhaps I should reinstall slack and start afresh.

I just reread your post and you asked if I can surf the net. Well, I hadn't tried that. So I opened firefox and typed in http://192.168.1.1 and got an Unable to connect message. Then I tried to access the Slackware home page and after an age I got a Can't find the server message. Then, just out of interest, I pressed the back button, and there was my router welcome page! I clicked on the start configuration button, but got the Unable to connect message. I tried reloading that page several times, but to no avail. But doesn't that show that I can talk to my router, just very slowly and unreliably? What is going on? So I've just rebooted to pclos and looked at the router log file for the last few minutes:
Code:
07.03.2008 11:29:49 DHCP ist aktiv: [03/07/08] [11:29:49] [WLAN] [00-30-05-da-6f-fe] [00:30:05:da:6f:fe] [192.168.1.102] [255.255.255.0] [] [192.168.1.1] [-1]  (H001)       <---- that's pclos just now getting an ip address

07.03.2008 11:18:49 DHCP ist aktiv: [03/07/08] [11:18:49] [LAN] [00-30-05-da-6f-fe] [00:30:05:da:6f:fe] [192.168.1.102] [255.255.255.0] [] [192.168.1.1] [-1]  (H001)       <---- that's Slackware getting an ip address 

07.03.2008 11:16:19 WLAN-Station abgemeldet: Rechnername: PC-da6ffe, MAC-Addresse:  <--- that's me looking at the log in pclos a few minutes ago
Interesting but what is going on??
ros

Last edited by Quercus ruber; 03-07-2008 at 04:43 AM. Reason: Can I surf the internet
 
Old 03-07-2008, 07:37 AM   #10
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
I'm going to be upfront about one thing. I have absolutely no idea why this isn't working. EVERYTHING you've posted suggests that you should be happily surfing away, so the stuff that follows is really a fishing expedition.


Quote:
The router has been set up to always set my hardware address *A:6F:FE to 192.168.1.102.
I think that for the time being, you should turn this off and let the laptop get whatever IP address it gets. At this point, the fewer complications, the better.

Quote:
So I opened firefox and typed in http://192.168.1.1 and got an Unable to connect message.
Wow. If the gateway was set, that should have worked if the driver was working.


Quote:
Then, just out of interest, I pressed the back button, and there was my router welcome page!
My aching head................................


The one thing that does look a little off is your resolv.conf after you've run dhcpcd. That should have contained the nameservers from your ISP, not just your router. However, that doesn't change the fact that trying to get to your router by IP address should have worked. I also see that you've set up your wireless card in /etc/rc.d/rc.inet1.conf. I think for the time being, you should comment out any changes you've made there and work exclusively from the command line.

Quote:
Perhaps I should reinstall slack and start afresh.
I usually hate to suggest this, but in your case, that might not be a bad idea. Something is screwed up, but it sure isn't leaving any clues.
 
Old 03-11-2008, 04:13 PM   #11
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
I'm getting quite depressed about this.
I've reinstalled slackware 12.0. I've disabled the setting on our router which assigns this laptop a specific ip address. I haven't touched rc.wireless.conf or rc.inet1.conf. Nothing. I'm only working from the command line. I compiled and installed ndiswrapper and then did the following:
Code:
root@darkstar:~# date
Tue Mar 11 21:28:25 CET 2008
root@darkstar:~# ndiswrapper -l
sis163u : driver installed
        device (0BF8:100F) present
root@darkstar:~# modprobe ndiswrapper
root@darkstar:~# iwconfig wlan0 key open x-----x
root@darkstar:~# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:"Wir"  Nickname:"darkstar"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:01:E3:77:4F:49
          Bit Rate=54 Mb/s   Tx-Power:18 dBm   Sensitivity=0/3
          RTS thr=2312 B   Fragment thr=2312 B
          Encryption key:x----x   Security mode:open
          Power Management:off
          Link Quality:70/100  Signal level:-51 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@darkstar:~# dhcpcd wlan0
root@darkstar:~# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:30:05:DA:6F:FE
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:5ff:feda:6ffe/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8668 (8.4 KiB)  TX bytes:1118 (1.0 KiB)

root@darkstar:~# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:01:E3:77:4F:49
                    ESSID:"Wir"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:59/100  Signal level:-58 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:54 Mb/s; 48 Mb/s; 36 Mb/s; 24 Mb/s; 18 Mb/s
                              12 Mb/s; 11 Mb/s; 9 Mb/s; 6 Mb/s; 5.5 Mb/s
                              2 Mb/s; 1 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0

root@darkstar:~# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     *               255.255.255.0   U         0 0          0 wlan0
loopback        *               255.0.0.0       U         0 0          0 lo
default         192.168.1.1     0.0.0.0         UG        0 0          0 wlan0
root@darkstar:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
From 192.168.1.100 icmp_seq=2 Destination Host Unreachable
From 192.168.1.100 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4018ms
, pipe 3
root@darkstar:~# date
Tue Mar 11 21:31:12 CET 2008
You can see the time when I did all this. Netstat -r takes an age to return the last line. I don't know if that is significant. I was unable to connect to the router with firefox as I did before. Then I rebooted into pclos and looked at the router log:
Code:
11.03.2008 21:41:20 192.168.1.102 Login erfolgreich (G001)

11.03.2008 21:39:48 DHCP ist aktiv: [03/11/08] [21:39:48] [WLAN] [00-30-05-da-6f-fe] [00:30:05:da:6f:fe] [192.168.1.102] [255.255.255.0] [] [192.168.1.1] [342000]  (H001)  <------- pclos getting an ip address

11.03.2008 21:28:48 DHCP ist aktiv: [03/11/08] [21:28:48] [WLAN] [00-30-05-da-6f-fe] [00:30:05:da:6f:fe] [192.168.1.100] [255.255.255.0] [] [192.168.1.1] [342000]  (H001)  <---- slackware getting an ip address

11.03.2008 21:20:09 WLAN-Station abgemeldet: Rechnername: PC-da6ffe, MAC-Addresse: 00:30:05:DA:6F:FE. (W001) <----- pclos shutting down

11.03.2008 21:09:52 DHCP ist aktiv: [03/11/08] [21:09:52] [WLAN] [00-30-05-da-6f-fe] [00:30:05:da:6f:fe] [192.168.1.102] [255.255.255.0] [] [192.168.1.1] [342000]  (H001)      <----- pclos getting an ip address
I think I'm going to install slackware 10.2 or 11.0 - it will be interesting to see if I get anywhere with that. Bearing in mind that 2 other linuxes have managed to get this thing working with the same driver leads me to think that it is a slackware peculiarity.


ros
 
Old 03-13-2008, 09:24 AM   #12
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
I think I'm going to install slackware 10.2 or 11.0 - it will be interesting to see if I get anywhere with that. Bearing in mind that 2 other linuxes have managed to get this thing working with the same driver leads me to think that it is a slackware peculiarity.
I agree with you on this, but to be honest, I have no idea what it could possibly be. As I've said before, everything appears to be functioning normally and the only conclusion I can reach is that there is some fundamental incompatibility between Slackware and your hardware. The one thing to keep in mind about Slackware is that it is a VERY conservative distro, and it could be that the incompatibility is due to some older software still being standard in Slackware. That would fit with the fact that newer distros are able to handle your card better. If this is the case, I'm not sure that moving to older versions of Slackware will help. On the other hand, Slackware 12 was a pretty substantial change from earlier versions and it is possible that something got introduced that is causing the problem.

Sorry I can't be of more help, but this one really has me stumped.
 
Old 03-13-2008, 04:24 PM   #13
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Throwing in the towel

Hi

Quote:
I think I'm going to install slackware 10.2 or 11.0 - it will be interesting to see if I get anywhere with that. Bearing in mind that 2 other linuxes have managed to get this thing working with the same driver leads me to think that it is a slackware peculiarity.
Well, that didn't work either. I've just, out of desperation, installed slackware-current, but still no go. I think I've invested quite enough time in this problem. Tomorrow I shall go and buy a usb wlan dongle, which feels a bit like giving up. So which one shall I buy? What chipset does slack support? On my desktop I've got one with a zd1211 chipset and I was jolly glad when that was incorporated into the kernel (2.6.18 I think) I don't have any problems with that. Hmmmm praps I should pop it into my laptop...

Thanks for your help and ideas.

ros
 
Old 03-13-2008, 05:39 PM   #14
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
You know, it might be cheaper to simply use another distro rather than buy a new wireless rig. Besides, given what you've seen on this laptop, I'm not sure that a different wireless card is going to be any different that what you've seen so far.

As for chipsets, I'm currently using an Intel 3945 in my main laptop, and that works fine. I think Atheros chipsets are also well supported as are some Ralink chipsets.
 
Old 03-14-2008, 05:03 AM   #15
Quercus ruber
Member
 
Registered: Mar 2004
Location: Bocholt, Germany
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 19
Hi
I guess you're right; I'll keep slackware on my desktop and something else that works, like pclos, here on the desktop.

ros
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
System Freeze w/ sis163u USB Wireless Stick Zinfidel Linux - Wireless Networking 1 01-22-2008 03:03 AM
Amilo A1650 and slackware 10.1 problems Ravendark Linux - Laptop and Netbook 1 09-28-2005 08:23 AM
Slackware 10.0 on Fujitsu-Siemens Amilo 1425 Blazarov Linux - Laptop and Netbook 0 08-14-2005 10:24 AM
Fujitsu siemens amilo d1840w and slackware -- irda Retrox Slackware 6 04-23-2005 05:09 PM
Using slackware on an Amilo D1840 laptop eirik.whitefox Linux - Laptop and Netbook 5 12-23-2004 08:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 04:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration