LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 04-23-2008, 09:37 AM   #1
Vassos
Member
 
Registered: Jul 2007
Posts: 52

Rep: Reputation: 15
Netgear Wlan on Debian


hi
I installed the drivers for netgera WG111 through ndiswrapper. Everything was working allright.
I was actually surfing the net for some hours.
i was actually using the gnomes Network manager and everything wasvery easy to handle.

But after one restart everything goes wrong.

I first load the modules through modprobe ndiswrapper.
and it says its ok.But first of all in my log i get this messge:


Apr 23 17:07:40 spyros kernel: ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
Apr 23 17:07:40 spyros kernel: ndiswrapper: driver mrv8000c (Marvell,02/22/2005,3.1.1.7) loaded
Apr 23 17:07:40 spyros kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Apr 23 17:07:40 spyros kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [C0A4] -> GSI 11 (level, low) -> IRQ 11
Apr 23 17:07:40 spyros kernel: PCI: Setting latency timer of device 0000:03:00.0 to 64
Apr 23 17:07:40 spyros kernel: ndiswrapper: using IRQ 11
Apr 23 17:07:40 spyros kernel: wlan0: ethernet device 00:18:4d:77:28:56 using NDIS driver: mrv8000c, version: 0x3000036, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 11AB:1FAA.5.conf
Apr 23 17:07:40 spyros kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Apr 23 17:07:40 spyros kernel: usbcore: registered new interface driver ndiswrapper
Apr 23 17:07:40 spyros NetworkManager: <debug> [1208959660.685517] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_18_4d_77_28_56').
Apr 23 17:07:42 spyros kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready



The important part ist the link not ready.
i saw in other forums that sometimes trying to connect gets the link up. So i tried to connect.
Another thing . Once on the Netwotk Manager applet i was able to see the available wireless connections, but now i dont.
But if i go from the Network Settings of gnome , i can see them and i am able to choose one of them.
when i do that i get this on sys.log


Apr 23 17:32:57 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Apr 23 17:33:11 spyros dhclient: No DHCPOFFERS received.
Apr 23 17:33:11 spyros dhclient: No working leases in persistent database - sleeping.
Apr 23 17:33:11 spyros avahi-autoipd(wlan0)[4024]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 109).
Apr 23 17:33:11 spyros avahi-autoipd(wlan0)[4024]: Successfully called chroot().
Apr 23 17:33:11 spyros avahi-autoipd(wlan0)[4024]: Successfully dropped root privileges.
Apr 23 17:33:11 spyros avahi-autoipd(wlan0)[4024]: Starting with address 169.254.4.102
Apr 23 17:33:16 spyros avahi-autoipd(wlan0)[4024]: Callout BIND, address 169.254.4.102 on interface wlan0
Apr 23 17:33:16 spyros avahi-daemon[2996]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.4.102.
Apr 23 17:33:16 spyros avahi-daemon[2996]: New relevant interface wlan0.IPv4 for mDNS.
Apr 23 17:33:16 spyros avahi-daemon[2996]: Registering new address record for 169.254.4.102 on wlan0.IPv4.
Apr 23 17:33:20 spyros avahi-autoipd(wlan0)[4024]: Successfully claimed IP address 169.254.4.102




Only it actually does the DHCPDISCOVER for ten times ont different intervals. What about the last sentence " Successfully claimed IP address 169.254.4.102"

The point is that i still have no internet. It is very strange since i was working all right 2 hours ago.

pls any suggestions
 
Old 04-23-2008, 09:41 AM   #2
Vassos
Member
 
Registered: Jul 2007
Posts: 52

Original Poster
Rep: Reputation: 15
maybe this next part of the log file is also necessary

Apr 23 17:37:23 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Apr 23 17:37:26 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 23 17:37:34 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 23 17:37:42 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Apr 23 17:37:51 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Apr 23 17:38:07 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Apr 23 17:38:20 spyros dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Apr 23 17:38:24 spyros dhclient: No DHCPOFFERS received.
Apr 23 17:38:24 spyros dhclient: No working leases in persistent database - sleeping.
 
Old 04-23-2008, 10:41 AM   #3
Vassos
Member
 
Registered: Jul 2007
Posts: 52

Original Poster
Rep: Reputation: 15
Since i m working on it here is what i found already

finally i got the Network manager to find the avaulable connections but here is what happens when i try too connect to my modem:

I seems that it tries to connect but then it crushes
Here is the log file

Apr 23 18:32:39 spyros NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Apr 23 18:32:48 spyros dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Apr 23 18:32:48 spyros NetworkManager: <debug> [1208964768.472974] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'FRITZ!Box Fon WLAN 7140 Annex A'
Apr 23 18:32:48 spyros NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / FRITZ!Box Fon WLAN 7140 Annex A
Apr 23 18:32:48 spyros NetworkManager: <info> Deactivating device wlan0.
Apr 23 18:32:48 spyros NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Apr 23 18:32:48 spyros NetworkManager: <info> Device wlan0 activation scheduled...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) started...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0/wireless): access point 'FRITZ!Box Fon WLAN 7140 Annex A' is encrypted, but NO valid key exists. New key needed.
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'FRITZ!Box Fon WLAN 7140 Annex A'.
Apr 23 18:32:48 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) New wireless user key for network 'FRITZ!Box Fon WLAN 7140 Annex A' received.
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 23 18:33:17 spyros NetworkManager: <info> Activation (wlan0/wireless): access point 'FRITZ!Box Fon WLAN 7140 Annex A' is encrypted, and a key exists. No new key needed.
Apr 23 18:33:18 spyros NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Apr 23 18:33:20 spyros NetworkManager: <info> SUP: response was ''
Apr 23 18:33:20 spyros NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_supplicant_interface_init: supplicant error for 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'. Response: ''
Apr 23 18:33:20 spyros NetworkManager: <WARN> real_act_stage2_config(): Activation (wlan0/wireless): couldn't connect to the supplicant.
Apr 23 18:33:20 spyros kernel: ndiswrapper (set_essid:59): setting essid failed (C0000001)
Apr 23 18:33:20 spyros NetworkManager: <info> Activation (wlan0) failure scheduled...
Apr 23 18:33:20 spyros NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 23 18:33:20 spyros NetworkManager: <info> Activation (wlan0) failed for access point (FRITZ!Box Fon WLAN 7140 Annex A)
Apr 23 18:33:20 spyros NetworkManager: <info> Activation (wlan0) failed.
Apr 23 18:33:20 spyros NetworkManager: <info> Deactivating device wlan0.
Apr 23 18:33:20 spyros NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Apr 23 18:33:50 spyros kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 23 18:34:35 spyros kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Apr 23 18:34:35 spyros kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 23 18:34:35 spyros NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link.
Apr 23 18:34:35 spyros NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Apr 23 18:34:35 spyros dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Apr 23 18:34:35 spyros NetworkManager: <info> Will activate connection 'eth0'.
Apr 23 18:34:35 spyros NetworkManager: <info> Device eth0 activation scheduled...
Apr 23 18:34:35 spyros NetworkManager: <info> Activation (eth0) started...
Apr 23 18:34:35 spyros NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 23 18:34:35 spyros NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 23 18:34:36 spyros NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 23 18:34:37 spyros NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Apr 23 18:34:37 spyros NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Apr 23 18:34:37 spyros NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0
Apr 23 18:34:37 spyros avahi-autoipd(eth0)[2113]: client: RTNETLINK answers: Cannot assign requested address
Apr 23 18:34:37 spyros avahi-autoipd(eth0)[2113]: Script execution failed with return value 2
Apr 23 18:34:37 spyros avahi-daemon[2994]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::202:a5ff:feb4:fbf9.
Apr 23 18:34:37 spyros avahi-daemon[2994]: New relevant interface eth0.IPv6 for mDNS.
Apr 23 18:34:37 spyros avahi-daemon[2994]: Registering new address record for fe80::202:a5ff:feb4:fbf9 on eth0.*.
Apr 23 18:34:38 spyros NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0
Apr 23 18:34:41 spyros dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Apr 23 18:34:42 spyros dhclient: DHCPOFFER from 192.168.178.1
Apr 23 18:34:42 spyros dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 23 18:34:42 spyros dhclient: DHCPACK from 192.168.178.1
 
  


Reply



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
NetGear WG111v2 does not Get IP From Wlan Router NeroZero2 Linux - Wireless Networking 18 09-24-2006 08:53 PM
WLAN Problem Truemobile 1300 WLAN on Debian 3 with NDISWRAPPER FordPrefect Linux - Laptop and Netbook 2 08-08-2005 10:00 AM
NetGear MA521 (wlan-ng OR hostap) Almazick Linux - Wireless Networking 1 09-17-2004 05:32 PM
Netgear MA401RA WLAN problems samhogue Linux - Wireless Networking 0 04-07-2004 10:53 PM
netgear wlan card irq conflict scree_v Linux - Wireless Networking 0 03-22-2004 07:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 01:42 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