[driverloader] suse 9.0 on Gateway 450xl

Stefan Voss St_Voss at gmx.net
Mon Nov 3 15:55:10 EST 2003


> Hallo folks,
> 
> Andy wrote:
> > I have been trying to set up my intel 2100 wireless card. I installed, 
> uploaded
> > windows driver, and it still does not show up in suse's network 
> configurator.
> 
> I have exactly the same problem with Suse 9.0 and my Toshiba M10.
> The installation of the drivers is no problem, but after installation 
> the
> networkdevice eth1 does not show up in the network configurator.
> 
> The strange thing is, that ifconfig -a and iwconfig list the correct 
> device eth1.
> The WLAN card seems to find the accesspoint, because the SID and the
> MAC Adress of the AP is correctly shown. But there is no network 
> connection.
> If i try to look at my network or to access the internet nothing 
> happens.
> 
> #iwconfig
> eth1      IEEE 802.11-DS  ESSID:"Wireless Home "  Nickname:"unknown"
>           Mode:Managed  Access Point: 00:09:5B:35:D9:FC  Bit 
> Rate=11Mb/s
>           RTS thr=1600 B   Fragment thr=2304 B
>           Encryption key:off
>           Power Management:off
>           Link Quality:1/1  Signal level:-28 dBm  Noise level:-200 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> 
> # ifconfig -a
> eth1      Protokoll:Ethernet  Hardware Adresse 00:04:23:51:26:36
>           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
>           Kollisionen:0 Sendewarteschlangenlänge:100
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

My guess is that it's not a problem with the driverloader if the device
does not show up in SuSE's configuration tool. Yast2 probably only shows
devices which have been detected before by the hardware scan running
at boot time. Look in /var/lib/hardware/unique-keys/ if your wlan interface
has
a file there by which it is represented.

If the scan is done before the driverloader module is loaded the scan
won't pick up the wlan interface.

It looks like driverloader has sucessfully configured your interface.
To test your interface you can set an ip address manually by doing

ifconfig eth1 <ip addr> netmask <mask>
and
route add default gw <gw addr> dev eth1

> 
> [...]
> Greetz, Philipp.

Regards,
   Stefan Voss

-- 
Stefan Voss
(st_voss at gmx.net)

NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++



More information about the driverloader mailing list