Thread: [Madwifi-users] how to proceed? bug #1206
Status: Beta
Brought to you by:
otaku
From: Joshua N P. <jpr...@po...> - 2007-05-28 08:45:56
|
http://madwifi.org/ticket/1206 I installed Ubuntu 7.04 (Fiesty) on a lark. I was astonished to see it detect my card. I attached dmesg output to the bug. Can somebody look at the dmesg output and speculate how to get HAL working on Debian? -- Make April 15 just another day, visit http://fairtax.org |
From: Pavel R. <pr...@gn...> - 2007-05-31 01:40:37
|
On Mon, 2007-05-28 at 14:15 +0530, Joshua N Pritikin wrote: > http://madwifi.org/ticket/1206 > > I installed Ubuntu 7.04 (Fiesty) on a lark. I was astonished to see it > detect my card. I attached dmesg output to the bug. Can somebody look at > the dmesg output and speculate how to get HAL working on Debian? You may be holding the key to the problem. It would be very helpful if you do some more research. The first step would be to fix out whether it's the kernel or MadWifi or maybe just a random event. To do that, please try MadWifi with Debian patches on Ubuntu and vice versa. If it's the driver, please see if the patches make any effect, or it's just the versions. If it's the kernel it would be strange, but not impossible. Maybe it's some PCI or IRQ setting. I see that the card sits directly on bus 0, which leaves little room for other issues to affect the driver. -- Regards, Pavel Roskin |
From: Joshua N P. <jpr...@po...> - 2007-05-31 07:39:47
|
On Wed, May 30, 2007 at 09:40:30PM -0400, Pavel Roskin wrote: > On Mon, 2007-05-28 at 14:15 +0530, Joshua N Pritikin wrote: > > http://madwifi.org/ticket/1206 > > > > I installed Ubuntu 7.04 (Fiesty) on a lark. I was astonished to see it > > detect my card. I attached dmesg output to the bug. Can somebody look at > > the dmesg output and speculate how to get HAL working on Debian? > > You may be holding the key to the problem. It would be very helpful if > you do some more research. > > The first step would be to fix out whether it's the kernel or MadWifi or > maybe just a random event. To do that, please try MadWifi with Debian > patches on Ubuntu and vice versa. Since I sent the e-mail you replied to, I have completed some experiments and run into further mysteries which I have noted in the bug report. Briefly, MadWifi 0.9.3.x was working on both Ubuntu and Debian. I went to sleep. In the morning, MadWifi 0.9.3.x starting giving the same old HAL 13 errors and stopped working (on both Ubuntu and Debian). However, the ndiswrapper driver continued to work. > If it's the driver, please see if the patches make any effect, or it's > just the versions. If it's the kernel it would be strange, but not > impossible. Maybe it's some PCI or IRQ setting. I see that the card > sits directly on bus 0, which leaves little room for other issues to > affect the driver. Well, I am certain that I have changed nothing in Ubuntu which might have caused the HAL to start malfunctioning. If you can suggest any further experiments, I am ready to try them. |
From: Pavel R. <pr...@gn...> - 2007-05-31 08:00:46
|
Quoting Joshua N Pritikin <jpr...@po...>: > Since I sent the e-mail you replied to, I have completed some > experiments and run into further mysteries which I have noted in the bug > report. Briefly, MadWifi 0.9.3.x was working on both Ubuntu and Debian. > I went to sleep. In the morning, MadWifi 0.9.3.x starting giving the > same old HAL 13 errors and stopped working (on both Ubuntu and Debian). > However, the ndiswrapper driver continued to work. My guess HAL is too sensitive to something, which may be the background radio noise, the voltage or the temperature. The main thing, it's not something under our control, unfortunately. > Well, I am certain that I have changed nothing in Ubuntu which might > have caused the HAL to start malfunctioning. > > If you can suggest any further experiments, I am ready to try them. I cannot think of anything at the moment. -- Regards, Pavel Roskin |