Kein WLAN unter 9.3 auf Amilo M 7400

linux:/home/cpu # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:"RedCPU" Nickname:"linux"
Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power:off
Retry:on RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Zum Vergrößern anklicken....

linux:/home/cpu # iwlist eth1 scan
eth1 No scan results

Zum Vergrößern anklicken....

Configure interface

Use iwconfig to configure wireless network interface. First, see if the interface is available, with

iwconfig

This tool is not likely to be present on your system : it is part of the package 'wireless-tools', which you should install.

This will print the wireless interface e.g., wlan0. In the examples below wlan0 is used replace wlan0 with the interface reported by iwconfig above. The wireless configuration to be used should match what your Access Point AP uses. First, find out if you can see your AP with

iwlist wlan0 scan

Note: You may have to set the network name before the scan can find
your Access Point. If the scan does not find your AP, try issuing the
command
iwconfig wlan0 essid ESSID

_before_ the using the command
iwlist wlan0 scan

If this lists your AP, you can continue. Otherwise, you may have one of two problems: Your AP doesn't broadcast SSID see the FAQ for more information or the radio of the card is off again, see the FAQ for details.

If you see the AP in scan above, set the operating mode of the interface according to your setup. In most cases, it is Managed

iwconfig wlan0 mode Managed

If you use encryption WEP, set the key:

iwconfig wlan0 key restricted XXXXXXXX

You can use 10 hex digits for 40-bit encryption or 26 hex digits for 128-bit encryption. You may need to use open security mode instead of restricted depending on the setup of your AP. If you want to write the key in ASCII use s: e.g. iwconfig wlan0 key restricted s:password.

Set the network name

iwconfig wlan0 essid ESSID

Replace ESSID with the network name used by your AP.

At this point, check to make sure that ESSID is set in output of iwconfig wlan0. If you see the ESSID as you set, you can proceed to next step. If you see ESSID: off/any, then your card is not associated to AP. Check if WEP encryption is set exactly as used by AP and the AP broadcasts ESSID. See FAQ for more details. Until ESSID is set in output of iwconfig wlan0, you may not use =wlan0= as network interface.

Now, setup the network parameters for the interface wlan0. This varies from distribution to distribution. Refer to your distribution's documents on how to do this. Once this is done, you can use network tools to bring up the network e.g.,

ifconfig wlan0 up

or

dhclient wlan0

or

dhcpcd wlan0

etc.

Remember, if you have a firewall, to let it know that wlan0 is an external interface and allow it to pass traffic otherwise you won't even be able to ping your AP

Zum Vergrößern anklicken....

cpu schrieb:

Hallo,
nachdem es bisher noch keiner Distribution (Debian, Ubuntu 5.04, Suse 9.1) gelungen war, den WLAN-Chip in meinem Notebook anzusprechen, hatte ich große Hoffnung in die Suse 9.3 gesetzt.
Und siehe da: Suse hat den Chip erkannt und nach einem Online-Update konnte ich auch WPA-PSK konfigurieren. Allerdings wird mein Access-Point nicht gefunden.
[...]
PS: Noch eine Info zum System: Beim Fujitsu Siemens Amilo M 7400 handelt es sich um ein Centrino Notebook mit 1500 MHz, 40 GB HD und 512 KB RAM.

Zum Vergrößern anklicken....