I have a similar symptom in karmic (9.10) 32 and 64 bit system using a DWL-G122
Rev. B1.
When I try to connect to the access point the protocol negotiation seems to
work but I can't get an IP address. If I configure the stick manually I can't
ping anywhere, not even to the AP. The USB-Adapter wo
** Attachment added: "information aquired using apport-cli"
http://launchpadlibrarian.net/34569027/apport.network-manager.boBj1j.apport
--
Latest karmic networkmanager update breaks wifi
https://bugs.launchpad.net/bugs/453099
You received this bug notification because you are a member of Ubun
** Attachment added: "syslog"
http://launchpadlibrarian.net/34568538/syslog
--
Latest karmic networkmanager update breaks wifi
https://bugs.launchpad.net/bugs/453099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I tried the karmic daily-build live cd from today and have a similar problem
with network-manager 0.7.996. Unfortunately I can't use ubuntu-bug because I
have no network at all when the error occurs.
It seems that the wifi stick connects to the access point but fails to obtain
an ip address. Fin
** Attachment added: "lsusb"
http://launchpadlibrarian.net/34568554/lsusb
--
Latest karmic networkmanager update breaks wifi
https://bugs.launchpad.net/bugs/453099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I have a similar issue using the Karmic Koala daily-build live CD from
today: I can connect to the AP entering IP address, netmask and other
parameters. Using the automated setup by only entering the AP-Wifi-key
results in a drop of the connection because there is no dhcp address
found (don't know
Works for me with the daily-build live cd from today (2009-10-28).
--
Karmic beta boots to busybox prompt: Target filesystem doesn't have /sbin/init
https://bugs.launchpad.net/bugs/442462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I can confirm this bug using a DELL Dimension 521 using the x64 live CD
or a USB boot device (both from the official beta). When trying to boot
a DELL XPS M2010 "laptop" everything works so I think it is some problem
with the mainboard od the Dimension.
--
Karmic beta boots to busybox prompt: Tar
