Hi developers!
I would like to notify my card, with ath5k driver, doesn't works.

Here's some detailed information:
#lspci
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x

802.11abg Wireless PCI Express Adapter (rev 01)
#lspci -v
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x

802.11abg Wireless PCI Express Adapter (rev 01)

        Subsystem: Apple Computer Inc. Device 0086

        Flags: bus master, fast devsel, latency 0, IRQ 17

        Memory at 60200000 (64-bit, non-prefetchable) [size=64K]

        Capabilities: <access denied>

        Kernel driver in use: ath_pci

        Kernel modules: ath_pci
#ath_info 60200000
Warning: Invalid EEPROM Magic number!

 -==Device Information==-

MAC Version:  2424  (0xa0)

MAC Revision: 5424  (0xa3)

5Ghz PHY Revision: SChip (0xa2)

2Ghz PHY Revision: SChip (0xa2)

 -==EEPROM Information==-

EEPROM Version:     5.3

EEPROM Size:        4K

Regulatory Domain:  0x6A

 -==== Capabilities ====-

|  802.11a Support: yes  |

|  802.11b Support: yes  |

|  802.11g Support: yes  |

|  RFKill  Support: no   |

|  32KHz   Crystal: no   |

 ========================

GPIO registers: CR 00000000 DO 00000000 DI 00000009
##dmesg
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17

PCI: Setting latency timer of device 0000:02:00.0 to 64

ath5k_pci 0000:02:00.0: registered as 'phy0'

ath5k phy0: failed to resume the MAC Chip

ACPI: PCI interrupt for device 0000:02:00.0 disabled

ath5k_pci: probe of 0000:02:00.0 failed with error -5
If you need some other information, feel free to contact me.
Many thanks.

Regards.

Fabrizio

_______________________________________________

ath5k-devel mailing list

ath5k-devel@lists.ath5k.org

https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Hello and thanx for your report, can you please check out latest

compat-wireless package that includes various updates ?

You can get it from here -> http://www.linuxwireless.org/en/users/Download
--

GPG ID: 0xD21DB2DB

As you read this post global entropy rises. Have Fun ;-)

Nick

_______________________________________________

ath5k-devel mailing list

ath5k-devel@lists.ath5k.org

https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Hi Nick and thanks for your reply.

Sorry for delay.

Do you know if is there a debian package of compat-wireless ?

Thanks again.
_______________________________________________

ath5k-devel mailing list

ath5k-devel@lists.ath5k.org

https://lists.ath5k.org/mailman/listinfo/ath5k-devel

I don't see compat-wireless in the list of Debian packages

(http://www.us.debian.org/distrib/packages)
The whole point of having compat-wireless it to allow compiling the

current wireless drivers on older kernels, including kernels provided by

distributions.  If distributions were to package compat-wireless, it

would be inevitably behind the current code, simply because no

distribution would be able to update it daily.
So it's quite natural that Debian doesn't package compat-wireless.
--

Regards,

Pavel Roskin

_______________________________________________

ath5k-devel mailing list

ath5k-devel@lists.ath5k.org

https://lists.ath5k.org/mailman/listinfo/ath5k-devel

This is true unless your distribution works on source based compile

installs, like Gentoo, which does seem to have a package for it. Or

unless the building of a package for this is automated somehow for

binary-based distributions. I actually think letting distributions

give users somehow the option to run the latest and greatest drivers

for their distribution kernel *right now* is a great feature. This

would hopefully encourage more integration of out-of-tree drivers into

the kernel and also allow users to get the drivers they may need

easily instead of having them hunt down drivers on the net or

compiling their own kernel. I'd even think this might be something

worth-while for the other subsystems as well. But that's just a

thought.
  Luis

_______________________________________________

ath5k-devel mailing list

ath5k-devel@lists.ath5k.org

https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Hmm, actually I just thought of the biggest problem if we start

relying on this for other subsystems or if distributions do pick this

up and start relying completely on it. Although you do get new shiny

drivers with compat-wireless like tarballs userspace applications for

the distribution were compiled *with* the old kernel headers therefore

not being able to able to make use of the new interfaces unless they

are also recompiled. This is not an issue unless you need new

userspace application interfaces of course. An example that comes to

mind is making use of iw [1] for use with nl80211 for shiny new

nl80211 commands like for Mesh.
Of course a patch to userspace applications is possible to get your

userspace applications to compile to compat-wireless like applications

(like the one below for iw) but in general I think its best to just

consider it a hack for now to get users up to speed with new drivers

until their distributions pick up new kernel releases, and that's it.

If users or distributions users of this don't mind recompiling the

userspace applications themselves then at least they know what they

are getting into but userspace application binaries must have been

compiled with the same the compat-wireless release currently used.

That is if compat-wireless is packaged by binary distributions then so

should an iw for specific compat-wireless releases, which seems

awfully painful. The alternative I guess is to just have a

compat-wireless which is built daily and an iw-latest which is also

built daily against the same compat-wireless.
[1] http://wireless.kernel.org/en/users/Documentation/iw
diff --git a/defconfig b/defconfig

index 346f699..64dcda8 100644

--- a/defconfig

+++ b/defconfig

@@ -11,8 +11,9 @@
 # Kernel location for GIT NL80211 kernel code (assumed to be running,

 # by default); only required if your installed nl80211.h is out of date.

+COMPAT_WIRELESS = /home/mcgrof/devel/compat-wireless-2.6/

 CONFIG_KERNEL_LOC = /lib/modules/`uname -r`/build/

-CFLAGS += -I...
[ message continues ]