[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-04-22 Thread Guy K. Kloss
I've also have had problems with the 2.6.20.15.27 (-generic) that came with the now stable Feisty on my laptop. The Prism54 based PCMCIA card (Netgear WG511) just wouldn't work with the modules provided by the kernel (prism54pci, prism54common, and prism54usb). What finally did work was baking my

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-19 Thread Michael Bienia
I've retested with linux-image-2.6.20-12-lowlatency 2.6.20-12.19 and got my wireless connection back. It works for me. Thanks. A small drawback: iwconfig doesn't report the connection speed anymore, only the link quality. But I don't know if it's the driver or iwconfig at fault here. --

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-19 Thread Martin Jürgens
** Changed in: linux-source-2.6.20 (Ubuntu) Status: Needs Info = Fix Released -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-19 Thread Martin Jürgens
For all that have something with eeprom in their logs: This is the wrong bug report, please have a look at bug 90902 -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-18 Thread Martin Jürgens
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) = Ubuntu Kernel Team -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-18 Thread Ben Collins
Please retest with 2.6.20-11.18 kernel or newer. ** Changed in: linux-source-2.6.20 (Ubuntu) Importance: Undecided = Medium Assignee: Ubuntu Kernel Team = Ben Collins Status: Confirmed = Needs Info -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 --

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-16 Thread Martin Jürgens
** Changed in: linux-source-2.6.20 (Ubuntu) Status: Unconfirmed = Confirmed -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-15 Thread cplim
I have the same problem, my card stopped working after the upgrade to the new kernel. ~$ uname -a Linux draco 2.6.20-11-386 #2 Thu Mar 15 07:58:11 UTC 2007 i686 GNU/Linux ~$ lspci 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 04) 00:01.0 PCI bridge: Intel Corporation

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-15 Thread cplim
i am using a Netgear WG511 pcmcia card. -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-13 Thread jonnybecker
** Attachment added: lspci-vvnn.log http://librarian.launchpad.net/6787702/lspci-vvnn.log -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-13 Thread jonnybecker
Same problem here with 2.6.20-10-generic. uname -a tells me: Linux horst 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux 'ifdown wlan0' tells me: There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 ...

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-03-02 Thread Tino Wagner
Same problem here with linux-image-2.6.20-9-386. Disabled the new Prism54 driver and reenabled the old one, then recompiled the kernel. Works like a charm. Linux saturn 2.6.20-9-386 #2 Mon Feb 26 02:58:41 UTC 2007 i686 GNU/Linux /var/log/messages excerpt: Mar 1 20:59:35 saturn kernel: [

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-22 Thread Cristian Aravena Romero
See Bug #85250 -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-20 Thread Manfred Paul
I have a prism45 wlan card. Since kernel 2.6.20-8 it is not working. Here the error message: Feb 18 21:45:16 kubuntu kernel: [ 85.148000] pccard: CardBus card inserted into slot 0 Feb 18 21:45:16 kubuntu kernel: [ 85.148000] PCI: Enabling device :03:00.0 ( - 0002) Feb 18 21:45:16

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-19 Thread Michael Bienia
The output of uname -a is: Linux vorlon 2.6.20-8-lowlatency #2 SMP PREEMPT Tue Feb 13 01:17:13 UTC 2007 x86_64 GNU/Linux -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-19 Thread Michael Bienia
** Attachment added: dmesg.log http://librarian.launchpad.net/6470218/dmesg.log -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-19 Thread Michael Bienia
** Attachment added: lspci-vvnn.log http://librarian.launchpad.net/6470224/lspci_vvnn.txt -- Please reenable CONFIG_PRISM54 again https://launchpad.net/bugs/85315 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 85315] Re: Please reenable CONFIG_PRISM54 again

2007-02-18 Thread Cristian Aravena Romero
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the