Re: NM & ath0 trouble
> Message: 6 > From: Tim Niemueller <[EMAIL PROTECTED]> > Subject: Re: NM & ath0 trouble > Message-ID: <[EMAIL PROTECTED]> > Note that the mentioned website is about the new madwifi-ng driver, > which uses the new HAL from Atheros. The old madwifi driver can be > checked out as madwifi-old branch > (http://www.madwifi.org/browser/branches/madwifi-old) from svn and works > just fine. > > Tim my October post was about NM and the old madwifi driver - it didn't work for me as described there. and going back to an old madwifi driver now ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) wlan: 0.8.6.0 (EXPERIMENTAL) ath_rate_sample: 1.2 ath_pci: 0.9.6.0 (EXPERIMENTAL) ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 ACPI: PCI Interrupt :02:0a.0[A] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 Build date: Oct 27 2005 still does not work: NetworkManager:ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager:nm_device_new(): waiting for device's worker thread to start NetworkManager:nm_device_new(): device's worker thread started, continuing. NetworkManager:Now managing wireless device 'ath0'. NetworkManager:Deactivating device ath0. NetworkManager:Updating allowed wireless network lists. NetworkManager:FORCE: device '/org/freedesktop/NetworkManager/Devices/ath0', network 'default' NetworkManager:Deactivating device ath0. NetworkManager: [1136481046.955453] (): Forcing AP 'default' NetworkManager:Device ath0 activation scheduled... NetworkManager:Activation (ath0) started... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) scheduled... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) started... NetworkManager:Activation (ath0) Stage 2 (Device Configure) scheduled... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) complete. NetworkManager:Activation (ath0) Stage 2 (Device Configure) starting... NetworkManager:Activation (ath0/wireless) Stage 2 (Device Configure) will connect to access point 'default'. NetworkManager:Activation (ath0/wireless): access point 'default' is unencrypted, no key needed. NetworkManager:Activation (ath0/wireless): using essid 'default', with no authentication. NetworkManager: [1136481055.331714] (): Activation (ath0/wireless): no hardware link to 'default' in non-encrypted mode. NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) Stage 2 (Device Configure) complete. NetworkManager:Activation (ath0) failed for access point (default) NetworkManager:Deactivating device ath0. NetworkManager:Activation (ath0) failed for access point (default) NetworkManager:Deactivating device ath0. i don't understand why it should not work for me if it works for others. any debugging suggestions? Sven ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
On Thu, 2006-01-05 at 11:01 -0500, Dan Williams wrote: > So in the 3rd Edition of your book, Robert, can you pleasepleaseplease > add a chapter for "Making your driver play nice with others, including > HAL" that has a section on what to do to get the correct sysfs entries, > ie stuff like SET_NETDEV_DEV and ensuring the sysfs 'driver' link is > correct by passing the correct driver structure to the device init > routines (which I believe is SET_MODULE_OWNER)? > > It seems there's complete lack of documentation on how to make drivers > interact with sysfs. God, yes. Linux drivers are absolutely horrid and networking is the worst subsystem and wireless the worst grouping therein. Just terrible. But the problem really lies on three issues (a) No documentation. Driver writers do not know what to do or how to do it. (b) Incomplete implementation in current kernels, so driver writers "roll their own" solution. Nice in the short-term, awful in the longer term. (c) Other kernel hackers and some users just don't care. Until things like HAL, g-v-m, and NM, the need for a unified API just was not there. And there is one other concern, broader in scope: People simply do not treat sysfs as API--immutable and important--in the same way they treat system calls or even, for that matter, device nodes. I added a brief sysfs section to the 2ed, but it was largely a "sysfs internals" -- how to hack the sysfs code, not work with sysfs in your own driver. A 3ed will surely do better. Also, I think Linux Device Drivers 3ed has a decent treatment of this material. But probably not enough. We really need to outline MANDATORY behavior and MANDATORY sysfs entries that all drivers need support. It is a lot of work to document all of that. But, damn, we need it. Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
On Thu, 2006-01-05 at 09:28 -0500, Robert Love wrote: > On Thu, 2006-01-05 at 14:28 +0100, Tim Niemueller wrote: > > > Note that the mentioned website is about the new madwifi-ng driver, > > which uses the new HAL from Atheros. The old madwifi driver can be > > checked out as madwifi-old branch > > (http://www.madwifi.org/browser/branches/madwifi-old) from svn and works > > just fine. > > Indeed. > > But work is continuing on madwifi-ng and that will be the solution going > forward, so we should get working on that. It fixes a lot of other > madwifi issues nicely, too. So in the 3rd Edition of your book, Robert, can you pleasepleaseplease add a chapter for "Making your driver play nice with others, including HAL" that has a section on what to do to get the correct sysfs entries, ie stuff like SET_NETDEV_DEV and ensuring the sysfs 'driver' link is correct by passing the correct driver structure to the device init routines (which I believe is SET_MODULE_OWNER)? It seems there's complete lack of documentation on how to make drivers interact with sysfs. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
On Thu, 2006-01-05 at 14:28 +0100, Tim Niemueller wrote: > Note that the mentioned website is about the new madwifi-ng driver, > which uses the new HAL from Atheros. The old madwifi driver can be > checked out as madwifi-old branch > (http://www.madwifi.org/browser/branches/madwifi-old) from svn and works > just fine. Indeed. But work is continuing on madwifi-ng and that will be the solution going forward, so we should get working on that. It fixes a lot of other madwifi issues nicely, too. Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
Dan Williams wrote: > On Wed, 2006-01-04 at 21:23 -0500, Sven Rinke wrote: > > > Haha, I hadn't realized they didn't have SET_NETDEV_DEV... I could > swear the driver had that correct at least 6 months ago or so, I have > used an Atheros b/g card quite extensively before with 2.6.12 and 2.6.13 > kernels. Weird. Well, I'll give it a shot and see what happens in the > next couple days here. Note that the mentioned website is about the new madwifi-ng driver, which uses the new HAL from Atheros. The old madwifi driver can be checked out as madwifi-old branch (http://www.madwifi.org/browser/branches/madwifi-old) from svn and works just fine. Tim -- Tim Niemueller <[EMAIL PROTECTED]> www.niemueller.de = Imagination is more important than knowledge. (Albert Einstein) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
On Wed, 2006-01-04 at 21:23 -0500, Sven Rinke wrote: > Dan, > > thanks for your prompt reply. my kernel version is > 2.6.14-1.1636 with swusp2 patches, and i'm using the binary-HAL from > www.madwifi.org , a recent version with a fix for some trouble with NM: > www.madwifi.org/changeset/1380 Haha, I hadn't realized they didn't have SET_NETDEV_DEV... I could swear the driver had that correct at least 6 months ago or so, I have used an Atheros b/g card quite extensively before with 2.6.12 and 2.6.13 kernels. Weird. Well, I'll give it a shot and see what happens in the next couple days here. Dan > Sven > > On Wed, 2006-01-04 at 21:11 -0500, Dan Williams wrote: > > So we've finally got an a/b/g Atheros card (Netgear) at work now for > > testing. What exact version of the driver are you using? Are you using > > the reverse-engineered HAL or the normal binary-HAL? What kernel > > version? > > > > Dan > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
Dan, thanks for your prompt reply. my kernel version is 2.6.14-1.1636 with swusp2 patches, and i'm using the binary-HAL from www.madwifi.org , a recent version with a fix for some trouble with NM: www.madwifi.org/changeset/1380 Sven On Wed, 2006-01-04 at 21:11 -0500, Dan Williams wrote: > So we've finally got an a/b/g Atheros card (Netgear) at work now for > testing. What exact version of the driver are you using? Are you using > the reverse-engineered HAL or the normal binary-HAL? What kernel > version? > > Dan > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM & ath0 trouble
On Wed, 2006-01-04 at 20:39 -0500, Sven Rinke wrote: > hi, > > i have not been able to use NM for a while now due to issues described > in my 2005-October/msg00208.html post (any reason why there was no > response to that?). here's another (unsuccessful) try using the new > madwifi driver... > > i'd like to use NM again, so any hints or comments. i'm running FC4 with > NetworkManager-0.5.1-1.FC4.4 > dhcdbd-1.9-1.FC4 > wireless-tools-28-0.pre10.4 > dhcp-3.0.2-28.FC4 So we've finally got an a/b/g Atheros card (Netgear) at work now for testing. What exact version of the driver are you using? Are you using the reverse-engineered HAL or the normal binary-HAL? What kernel version? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM & ath0 trouble
hi, i have not been able to use NM for a while now due to issues described in my 2005-October/msg00208.html post (any reason why there was no response to that?). here's another (unsuccessful) try using the new madwifi driver... i'd like to use NM again, so any hints or comments. i'm running FC4 with NetworkManager-0.5.1-1.FC4.4 dhcdbd-1.9-1.FC4 wireless-tools-28-0.pre10.4 dhcp-3.0.2-28.FC4 NM is trying to connect to an open network but fails... here's the output from "NetworkManager --no-daemon": NetworkManager:ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager:nm_device_new(): waiting for device's worker thread to start NetworkManager:nm_device_new(): device's worker thread started, continuing. NetworkManager:Now managing wireless device 'ath0'. NetworkManager:Deactivating device ath0. NetworkManager:eth0: Device is fully-supported using driver 'e100'. NetworkManager:nm_device_new(): waiting for device's worker thread to start NetworkManager:nm_device_new(): device's worker thread started, continuing. NetworkManager:Now managing wired device 'eth0'. NetworkManager:Deactivating device eth0. NetworkManager:Updating allowed wireless network lists. NetworkManager:FORCE: device '/org/freedesktop/NetworkManager/Devices/ath0', network 'default' NetworkManager:Deactivating device ath0. NetworkManager: [1136423147.346090] (): Forcing AP 'default' NetworkManager:Device ath0 activation scheduled... NetworkManager:Activation (ath0) started... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) scheduled... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) start ed... NetworkManager:Activation (ath0) Stage 2 (Device Configure) scheduled... NetworkManager:Activation (ath0) Stage 1 (Device Prepare) complete. NetworkManager:Activation (ath0) Stage 2 (Device Configure) starting... NetworkManager:Activation (ath0/wireless) Stage 2 (Device Configure) will connect to access point 'default'. NetworkManager:Activation (ath0/wireless): access point 'default' is unencrypted, no key needed. NetworkManager:Activation (ath0/wireless): using essid 'default', with no authentication. NetworkManager: [1136423162.703110] (): Activation (ath0/wireless): no hardware link to 'default' in non-encrypted mode. NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) failure scheduled... NetworkManager:Activation (ath0) Stage 2 (Device Configure) complete. NetworkManager:Activation (ath0) failed for access point (default) NetworkManager:Deactivating device ath0. NetworkManager:Activation (ath0) failed for access point (default) NetworkManager:Deactivating device ath0. and in /var/log/messages: dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason driver info from "dmesg": ath_hal: 0.9.16.13 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, DFS) ath_rate_sample: 1.2 ath_pci: 0.9.4.5 (Atheros/multi-bss) ACPI: PCI Interrupt :02:0a.0[A] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: H/W encryption support: WEP AES AES_CCM TKIP wifi0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 wifi0: Use hw queue 1 for WME_AC_BE traffic wifi0: Use hw queue 0 for WME_AC_BK traffic wifi0: Use hw queue 2 for WME_AC_VI traffic wifi0: Use hw queue 3 for WME_AC_VO traffic wifi0: Use hw queue 8 for CAB traffic wifi0: Use hw queue 9 for beacons wifi0: Atheros 5212: mem=0xfcee, irq=11 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
