[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Wed, Aug 23, 2006 at 10:40:30AM -, Matt Zimmerman wrote: > Has anyone experiencing this bug tried 2.6.17 in edgy? We've switched to madwifi-ng in Edgy, so the problem is gone there. It only happens with madwifi-old. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Jul 25, 2006 at 11:10:11AM -, Chris Jones wrote: > However, all of this makes it extraordinarily difficult to track down > what's really going on, especially with no serial port. Can anyone > think of some other way(s) we can collect information about what > failed? There's always netconsole.. Via the wired interface, of course. :-) Cheers. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Wed, Jul 19, 2006 at 02:22:36PM -, Michel Lesoinne wrote: > Apparently the way to get it fixed is stop NetworkManager from > continuously scanning... How does one do that? I don't know. I have not experienced this behaviour. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Jul 18, 2006 at 02:28:44AM -, Michel Lesoinne wrote: > Still as soon as NetworkManager starts it gets the wifi in a weird state > and never connects. I have to kill NetworkManager, unload the modules > and reload them to be able to connect manually. Soren, do you have a > package of what you did that I can install? Yes. It can be found here: http://www.linux2go.dk/ubuntu/pool/main/m/madwifi-ng-default/madwifi-ng-default_1.0_all.deb also, the patched wpasupplicant and NetworkManager: http://www.linux2go.dk/ubuntu/pool/main/n/network-manager/network-manager_0.6.2-0ubuntu7linux2go2_i386.deb http://www.linux2go.dk/ubuntu/pool/main/w/wpasupplicant/wpasupplicant_0.4.8-3ubuntu1.1linux2go1_i386.deb the really easy way is to add: deb http://www.linux2go.dk/ubuntu dapper main to your sources.list and run: $ sudo apt-get install madwifi-ng-default wpasupplicant network-manager IMPORTANT: For these packages to work, you need to have the linux-restricted-modules installed and NOT be using the madwifi-ng drivers from SVN as there are naming differences. Cheers! -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Mon, Jul 17, 2006 at 10:33:26PM -, Michel Lesoinne wrote: > I do not understand the changes you did when I installed a new > version of madwifi, it removed all the new_ath_* drivers and instead > installed the ath_* in their place. So why did you modify > NetworkManager and wpa_supplicant? The change to networkmanager enables it to detect if you're using the madwifi-ng (new_ath_* actually). madwifi and madwifi-ng has different API's and the change I've made to wpasupplicant lets it use both depending on a commandline option (which networkmanager can give it because I've taught it to know which driver is used). > I took the subversion madwifi and it did not work, as it would freeze > after a little bit of time and it did not work with NetworkManager. It will work with the patched networkmanager and wpasupplicant. > Now I am trying a snapshot madwifi-ng and still there are no > "new_ath_*" modules being loaded. What am I missing? new_ath_* are the names Ubuntu uses for madwifi-ng in order to let madwifi and madwifi-ng coexist on the system. If you compile them from SVN, they'll be named ath_*. Cheers. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Thu, Jul 13, 2006 at 04:41:33PM -, Michel Lesoinne wrote: > I have been experiencing the same problem. I have an Apple MacBook Pro > 17" and installed dapper on it. I also noticed it was network related > and perhaps triggered by wpa_supplicant/knetworkmanager combo. This > led me to find this thread. Unlike others, my lspci gives me slightly > different numbers: 168c:001c That's very useful info. I've hacked together a .deb that makes madwifi-ng be loaded instead of madwifi. That fixes it for me, but apparantly some people have other problems with -ng. I'll just finish polishing it (probably tomorrow) and upload it somewhere. Cheers, Søren. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Jul 11, 2006 at 11:23:42AM -, Gabriele Vivinetto wrote: > Me tto I'm experiencing these freezes. In addition I'v an ATI video > card on my Compaq Evo N800v, and it seems to be a relation between > madwifi and ati: > https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-ati/+bug/38181 I have an Intel graphics chipset, so that's not the case on my system. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
