NetStumbler.org Forums - View Single Post - Gericom USB 802.11b with SIS 162U chipset

metamorfo · 09-07-2004

Ok, here I am.
Last night I tried this driver on my machines.
Bad news is it didn't compile on a Slackware 9.1 with both kernel 2.6.8.1 and 2.4.22
Even if in the included README it says it should work with 2.4.0 and later versions of the kernel, the reality is it gets stuck , at compile time, checking something in the linux include ac97 codec. (have no idea why)

I tried on a different machine/kernel. It compiled with no problems on a Mandrake 8.1 (heavily patched kernel 2.4.18 ). It has a GUI configuration tool too. You need X to use it. You can launch from an xterm:
bash $ wlanutil
It started scanning the environment and easily found the AP, so that you can connect. It even displays a bar showing the signal strength.

I tried to ping the AP but I recieved no reply. There must have been some problem with network configuration. I hate mandrake cause it tries to configure everything without human intervention.

I'll try again tonight. My plan is to install slackware 8.1 with a 2.4.18 vanilla kernel and see what happens.

My suspect is I won't be able to use any kernel later than 2.4.19 and if it's so, it really sucks. If there's some developer reading this, do you think it could be possible to rewrite the drivers wrapper as to make it work under linux 2.6.x ?

09-07-2004	#8 (permalink)
metamorfo Registered Member Join Date: Sep 2004 Posts: 3	First impressions Ok, here I am. Last night I tried this driver on my machines. Bad news is it didn't compile on a Slackware 9.1 with both kernel 2.6.8.1 and 2.4.22 Even if in the included README it says it should work with 2.4.0 and later versions of the kernel, the reality is it gets stuck , at compile time, checking something in the linux include ac97 codec. (have no idea why) I tried on a different machine/kernel. It compiled with no problems on a Mandrake 8.1 (heavily patched kernel 2.4.18 ). It has a GUI configuration tool too. You need X to use it. You can launch from an xterm: bash $ wlanutil It started scanning the environment and easily found the AP, so that you can connect. It even displays a bar showing the signal strength. I tried to ping the AP but I recieved no reply. There must have been some problem with network configuration. I hate mandrake cause it tries to configure everything without human intervention. I'll try again tonight. My plan is to install slackware 8.1 with a 2.4.18 vanilla kernel and see what happens. My suspect is I won't be able to use any kernel later than 2.4.19 and if it's so, it really sucks. If there's some developer reading this, do you think it could be possible to rewrite the drivers wrapper as to make it work under linux 2.6.x ?