[HARDY]IPN2220: after kernel 2.6.22 wlan0 does not connnect anymore

Bug #205000 reported by michele
20
Affects Status Importance Assigned to Milestone
dhcdbd (Ubuntu)
New
Undecided
Unassigned
hal (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Undecided
Unassigned
ndiswrapper (Ubuntu)
Confirmed
Undecided
Unassigned
network-manager (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: dhcdbd

I upgraded from kubuntu 7.10 to 8.04 alpha6 and my wlan0 did not worked anymore.
I have a laptop amd64 acer 1524 wmli and ipn2220 windows driver 64bit.
With kubuntu 7.10 everythings worked correctly, before the dist-upgrade.
So I installed a new kubuntu 8.04 beta on the old 7.10 upgraded (to 8.04 alpha6).
Now I had a new kubuntu 8.04 beta upgradede.
But the problem remain here. With the same old features :(
My wlan0, is present, ndiswrapper works ok, but I cannot connect to the router.
-----------------
dmesg:
[ 427.102202] ndiswrapper (iw_set_freq:334): setting configuration failed (C0010015)
[ 427.158917] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 430.992637] wlan0: no IPv6 routers present
[ 454.196578] ndiswrapper (iw_set_ap_address:575): setting AP mac address failed (C0010015)
[ 454.690078] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[ 454.692241] psmouse.c: issuing reconnect request
[ 456.194558] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 462.598529] eth0: no IPv6 routers present

---------------
/var/log/messages:
Mar 22 08:30:31 gigiottopoli64 dhcdbd: dhco_parse_option_settings: bad option setting: old_server_name =
Mar 22 08:30:37 gigiottopoli64 kernel: [ 427.102202] ndiswrapper (iw_set_freq:334): setting configuration failed (C0010015)
Mar 22 08:30:37 gigiottopoli64 kernel: [ 427.158917] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mar 22 08:31:50 gigiottopoli64 dhcdbd: Unrequested down ?:3
Mar 22 08:31:51 gigiottopoli64 kernel: [ 454.196578] ndiswrapper (iw_set_ap_address:575): setting AP mac address failed (C0010015)
Mar 22 08:31:53 gigiottopoli64 kernel: [ 454.690078] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
Mar 22 08:31:53 gigiottopoli64 kernel: [ 454.692241] psmouse.c: issuing reconnect request
Mar 22 08:31:57 gigiottopoli64 kernel: [ 456.194558] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 22 08:32:03 gigiottopoli64 dhcdbd: dhco_parse_option_settings: bad option setting: old_server_name =
Mar 22 08:32:03 gigiottopoli64 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Mar 22 08:32:03 gigiottopoli64 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Mar 22 08:32:03 gigiottopoli64 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Mar 22 08:32:03 gigiottopoli64 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
---------------------------------------------

I'm not a guru, but the wireless does not work.
eth0 works well.

mikj

Revision history for this message
michele (mikj) wrote :
Download full text (15.7 KiB)

this is syslog:
------------------------------
Mar 22 17:55:01 gigiottopoli64 NetworkManager: <debug> [1206204901.974780] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_bluetooth').
Mar 22 17:55:02 gigiottopoli64 anacron[5642]: Anacron 2.3 started on 2008-03-22
Mar 22 17:55:02 gigiottopoli64 anacron[5642]: Normal exit (0 jobs run)
Mar 22 17:55:02 gigiottopoli64 /usr/sbin/cron[5671]: (CRON) INFO (pidfile fd = 3)
Mar 22 17:55:02 gigiottopoli64 /usr/sbin/cron[5672]: (CRON) STARTUP (fork ok)
Mar 22 17:55:02 gigiottopoli64 /usr/sbin/cron[5672]: (CRON) INFO (Running @reboot jobs)
Mar 22 17:56:07 gigiottopoli64 NetworkManager: <info> Updating allowed wireless network lists.
Mar 22 17:56:07 gigiottopoli64 NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.
Mar 22 17:56:47 gigiottopoli64 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <debug> [1206205007.004472] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'Casa'
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Casa
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Deactivating device wlan0.
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Device wlan0 activation scheduled...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) started...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0/wireless): access point 'Casa' is encrypted, but NO valid key exists. New key needed.
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Casa'.
Mar 22 17:56:47 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 22 17:57:53 gigiottopoli64 NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Casa' received.
Mar 22 17:57:53 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 17:57:53 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 22 17:57:53 gigiottopoli64 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configur...

Revision history for this message
Topher (hunt-topher) wrote :

Just to clarify, did you upgrade Gutsy to Hardy, or did you do a clean install from disc?

Revision history for this message
michele (mikj) wrote :

Excuse me about my english :(
in a first time, I upgraded from gutsy (where everythings work fine) to hardy, but several things did not work correctly ... especially my wireless connection.
in a second time (after many and many attempts to make a working wireless connection), I made a fresh new installation of kubuntu 8.04 beta, erasing and ripartitioning the old partitions.
.... and my wireless connection still does not work ! (togheter nvidia-glx too)

mikj

Revision history for this message
Nifty (violentsense) wrote :

I have the same problem.

I have SONY VAIO SZ3 laptop with i3945abg wifi adapter

1. Install clean Ubuntu 8.04 beta 4
2. Install nVidia drivers, reboot
3. Everything works
4. Check for updates, and apply all of them (~150), reboot
5. WiFi and Ethernet doesn't work

In /var/log/messages ----------------------------------------------
Mar 23 07:20:13 nifty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Mar 23 07:20:53 nifty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
----------------------------------------------------------------------------

6. After this I go to System->Administration->Network, switch network configuration from "roaming" to "manual". And enter settings
for wireless adapter (AP name, encryption key etc.), click "Ok". After this "Network" application goes to "busy", but after 5-6 minutes back to normal. Click "Close".
7. Now wireless connection work, except one small thing - "nm-applet" in tray don't show network signal level, just empty "bars"

In syslog ---------------------------------------------------------
Mar 23 07:37:17 nifty-laptop NetworkManager: <info> Activation (wlan0): waiting for device to cancel activation.
Mar 23 07:37:48 nifty-laptop last message repeated 31 times
Mar 23 07:38:49 nifty-laptop last message repeated 61 times
Mar 23 07:39:50 nifty-laptop last message repeated 61 times
Mar 23 07:40:51 nifty-laptop last message repeated 61 times
----------------------------------------------------------------------

Revision history for this message
Nifty (violentsense) wrote :

8. After reboot - nothing works again, Network Manager only show "manual configuration" option
9. Go to System->Administration->Network and change wlan and ethernet back to roaming configuration
10. Reboot.
11. Network manager show "Attempting to join the wireless network xxxxx" and utulize CPU at 100%. I'm wait for 10 minutes, but nothing change :(

------------------- /var/log/messages -----------------------------------------------------------------------
...
Mar 23 08:02:46 nifty-laptop kernel: [ 52.692803] NET: Registered protocol family 10
Mar 23 08:02:46 nifty-laptop kernel: [ 52.693862] lo: Disabled Privacy Extensions
Mar 23 08:02:46 nifty-laptop kernel: [ 52.695327] ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 23 08:02:46 nifty-laptop kernel: [ 52.696891] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 23 08:02:52 nifty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
----------------------------------------------------------------------------------------------------------------------

------------------- /var/log/syslog ----------------------------------------------------------------------------
Mar 23 08:02:54 nifty-laptop NetworkManager: [New Thread 0xb7b69720 (LWP 5088)]
Mar 23 08:02:54 nifty-laptop NetworkManager: [New Thread 0xb7367b90 (LWP 5411)]
Mar 23 08:02:54 nifty-laptop NetworkManager: [New Thread 0xb7b68b90 (LWP 5403)]
Mar 23 08:02:54 nifty-laptop NetworkManager: (no debugging symbols found)
Mar 23 08:02:54 nifty-laptop last message repeated 9 times
Mar 23 08:02:54 nifty-laptop NetworkManager: 0xb7f63410 in __kernel_vsyscall ()
Mar 23 08:02:54 nifty-laptop NetworkManager: ******************* END **********************************
----------------------------------------------------------------------------------------------------------------------

Revision history for this message
michele (mikj) wrote :

If you change /etc/network/interfaces, by hand or by other way (knetworkconf) network-manager does not work anymore . It wants (network-manager) a clean and emtpy /etc/network/interfaces.
This bug is similar (or the same) 172330.
I'm not a guru, but it seems as after a long time to get an IP address something (maybe avahi packages) can not permit to lease an ip address ...

mikj

Revision history for this message
michele (mikj) wrote :

we have others users with similar problem

Changed in dhcdbd:
status: New → Confirmed
michele (mikj)
Changed in dhcdbd:
status: Confirmed → New
Revision history for this message
Jimmy.Zhou (jingchao-joe) wrote :

I have this problem too. My laptop is acer extensa 5620g and the same intel 3935 abg wlan card.

Revision history for this message
Nifty (violentsense) wrote :

My problem is gone, when after clean install I check for updates and agree to install all of them except these three:

hal
hal-info
libhal1

So, I think - new version of HAL package in this updates incompatible with gnome NetworkManager application (network manager is depends on HAL)

Revision history for this message
Nifty (violentsense) wrote :

After applying patch to network-manager package from this topic https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/204868 (http://launchpadlibrarian.net/12806466/debdiff) i can install "hal" related updates, reboot and everything works fine.

Revision history for this message
michele (mikj) wrote :
Download full text (9.6 KiB)

No, in my system the problem remain, th e things are going better but I can not connect.
Here is my new syslog:
---------------

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <debug> [1206372484.352697] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'Casa'

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) started...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Activation (wlan0/wireless): access point 'Casa' is encrypted, and a key exists. No new key needed.

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Deactivating device wlan0.

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> Device wlan0 activation scheduled...

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Casa

03/24/2008 04:28:04 PM gigiottopoli64 NetworkManager <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was '0'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: response was 'OK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: sending command 'ADD_NETWORK'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: sending command 'AP_SCAN 1'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: sending command 'ENABLE_NETWORK 0'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'

03/24/2008 04:28:05 PM gigiottopoli64 NetworkManager <info> SUP: sending command 'SET_NETWORK 0 group CCMP'

03/24/2008 04:28:05 PM gig...

Read more...

Revision history for this message
lanzen (lanzen) wrote :

Michele,

I have exactly the same machine as you have, same driver and, of course the very same problem. My syslog also seems a photocopy of yours. I have not so far done a clean install because everything else seems to be fairly right for a beta and this is, so far, the only "badly mutilating" bug.

Booting into the old kernel (2.6.22-12), at the cost of a low screen resolution, sees ndiswrapper working properly as it was in Gustsy (that's gustsy kernel anyhow, isn't it?) so, could it be a kernel problem?

On the other end someone suggested to try the temporary script as in http://ubuntuforums.org/showthread.php?t=734003, though that's about a different driver. I won't be able to try this, nor to see if this morning update made any difference - and I'm not too optimistic that it will - until later this evening.

I've managed to connect using two different usb sticks. They work, but simply opening the new nm-editors and clicking on the ssid seems to screw things up so I've been since careful not to touch it.

Revision history for this message
michele (mikj) wrote :

Ciao :)

Me too :) ... in the last days I'm guessing that it's a kernel related problem, with the 2.6.22 series the problem about dhcp, not sending of the essid , etc., went away and the ipn2220 and wlan0 works correctly ...
I add the new kernel package on the bugs about this issue, and the ubuntu men will try to shoot me ! ;)
Especially about my english ...
michele

Revision history for this message
michele (mikj) wrote :

The same problem :
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/194714

   I'm not able to solve this bug, (i'm not able -everytime+always- to solve the bug): We need help froma true linux hacker ...

:(

mikj

Revision history for this message
lanzen (lanzen) wrote :

I wanted to test 0.6.6-0ubuntu1 that someone said was working, but I can't find it anywhere. Synaptics doesn't show it and there no way I know to force version.

Any hints?

Revision history for this message
michele (mikj) wrote : R: [Bug 205000] Re: dhcdbd: wlan0 does not connnect anymore

On lauchpad, I'm replying from blackberry, or on ubuntu archives ... Maybe you can try enabling the sources.list on adept ...I' m sorry... Let me know
Mikj

mikj
-----
Sent from my BlackBerry® wireless device

-----Original Message-----
From: lanzen <email address hidden>

Date: Sat, 29 Mar 2008 15:29:53
To:<email address hidden>
Subject: [Bug 205000] Re: dhcdbd: wlan0 does not connnect anymore

I wanted to test 0.6.6-0ubuntu1 that someone said was working, but I
can't find it anywhere. Synaptics doesn't show it and there no way I
know to force version.

Any hints?

--
dhcdbd: wlan0 does not connnect anymore
https://bugs.launchpad.net/bugs/205000
You received this bug notification because you are a direct subscriber
of the bug.

michele (mikj)
description: updated
Revision history for this message
michele (mikj) wrote :

Ciao :)

I'm testing network-manager-0.6.6-0ubuntu5, but nothing still work ... and no one are considering our problem ... :(

mikj

Revision history for this message
michele (mikj) wrote :

Ciao :)

   tonight I upgraded to dhcp 3.0.6.dfsg-1ubuntu9 .... and nothing still works ... :(

mikj

Revision history for this message
lanzen (lanzen) wrote :

I've read in kubuntu-users that someone is suggesting to update to the latest ndiswrapper. The thing is we already have that. We got ndiswrapper 1.52!

So maybe we should try downgrading.

I've just booted into the old gutsy kernel and the working ndiswrapper is at version 1.45:

$ ndiswrapper -v
utils version: 1.9
driver filename: /lib/modules/2.6.22-14-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version: 1.45
vermagic: 2.6.22-14-generic SMP mod_unload 586

We now have:
$ ndiswrapper -v
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.24-12-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version: 1.52
vermagic: 2.6.24-12-generic SMP mod_unload

On SourceForge they got the whole range from 1.45 to 1.52. So, which one?

Revision history for this message
lanzen (lanzen) wrote :

With this morning updates bringing in the new kernel, hall and a big bunch of new packetsI've had the pleasure to see that this bug has been solved: ndiswpapper works again with my neti driver.

Nice work guys/gals, thanks!

I think, unless somebody advises otherwise, that all these ndiswrapper related issues could be closed.

Revision history for this message
lanzen (lanzen) wrote :

This evening it's not working again. See my comment at bug #194714,

Revision history for this message
michele (mikj) wrote :

Ciao :)

me too ... always the same routine ... :(

  I had not the pleausure to see my ipn2220 works ... I'm sad ...

mikj

Revision history for this message
michele (mikj) wrote :

Ciao :)

  Lanzen, do you can post the syslog ?

mikj

Revision history for this message
lanzen (lanzen) wrote :

At this very moment I am connected through the laptop and the built in card is working. What have I done? Nothing.

When I turned on the machine I had my ZyXel usb plugged in and Ubuntu connected. I then turned on the WiFi switch on the laptop and waited for a scan. A little later I could see both cards in network-manager and the list of all reachable networks. I then forced the inprocomm card to connect and it went into the long useless loop as before. I clicked back on the Zyxel and it reconnected. Clicked again on the Inprocomm, it took a while, not too much and the two little green lights lit one shortly after the other, There I was! I then slipped the usb Zydas stick out and here I am.

The info window shows "WiFi 802.11 (wlan0)" at 53 Mb/s, driver ndiswrapper.

I feel I'll have this problem again tomorrow, but it's getting better. Well, I'm just trying to be optimistic about this whole business.

Here's the last line related to wlan0 in ifconfig. I don't remember seeing it in Gutsy, but I'm likely to be wrong.

Interrupt:21 Memory:c0005000-c0005800

Revision history for this message
michele (mikj) wrote :

Ciao :)

   Your information is usefull.
   I don't think that our problems are ndiswrapper related. If you can connect (if I have understood) only with the usb network adapter plug it ... I think that our problems are more related to dhcp or network-manager ... but I'm not a guru, probably I'm wrong... because remain the fact that with the 2.6.22 kernel series we could connect ...
  You should try to monitoring the log files and the network files before the connection and after the connection ... and maybe we can begin to understand where we will try to find the solution of our wlan problems

mikj

michele (mikj)
Changed in ndiswrapper:
status: New → Confirmed
Changed in hal:
status: New → Invalid
Changed in linux-source-2.6.24:
status: New → Confirmed
Revision history for this message
lanzen (lanzen) wrote :

I haven't had much time to look at WiFi, but...
new kernel updated (uname -r 2.6.24-15-generic) and no difference from the previous.

One thing I've noticed in the past two days, even with the new kernel, while I was successfully connected, is that after a while the connection drops. You can tell by the fact that browser can't reach addresses, evolution or kmail signal loss of connection to imap and even trying to update the weather applet shows it's not happening. The Network Manager icon still shows all the bars lit and the info window says a connection is going on. Trying to re-connect by forcing the ssid in NM leads to failure, as I've already reported.

The good thing is that I've noticed this bug has been confirmed. Let's hope!

Revision history for this message
surfduke (hewlettdesignconsult) wrote :

I just reported the following as a bug:

"I am using a windows driver installed in wrapper. It worked fine in 7.10. Now in 8.04 the driver installs, the activity light flashes, (but the network manager does not list any networks). Please review this problem.

My machine is a dell inspiron 1100
the wireless card is a Blitzz netwave point II BW
p612B

What is so strange is that I did not have a problem with 7.10

Thanks,

Carl"

It seems to be related to the problem being reviewed in this thread. I too need help with this issue.

Revision history for this message
Pedro Saraiva (pedro-a34195) wrote :

Hello,

Same problem here using the final version of hardy... In gutsy all when fine with some hacks.
The ndiswrapper is working, but the card refuses to connect to the wireless network.

I'm using WPA Pessoal encryption... i've not tested without encryption, maybe someone could test this? I don't have much time to do so.

My hardware is an acer travelmate 2301 wlmi with the infamous Improcomm IPN2220 card.

Thanks,

Pedro Saraiva

Revision history for this message
lanzen (lanzen) wrote :

Ubuntu hardy:
kernel 2.6.24-16-generic
Works on open networks only, not if encrypted.
kernel 2.6.22-14-generic
Works as in gutsy on open, wep or wpa.

I have an ubuntu hardy updated from gutsy and a kubuntu gutsy on my acer 1524. I'm not updating the latter yet for this reason.

Typical warnings while trying to connect with Inprocomm:

NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
kernel: [ 4743.943573] ndiswrapper (iw_set_freq:334): setting configuration failed (C0010015)
NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.

I think all these are duplicate of bug #194714 and should be unified under the same header. The real problem, I'd say, arises in the kernel.

Revision history for this message
lanzen (lanzen) wrote :

I've added a comment on #bug 194714. It might be of interest as my machine uses neti2220.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 194714, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Changed in network-manager:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.