-=| Paul Menzel, Thu, Sep 11, 2008 at 10:08:41AM +0200 |=- > Am Freitag, den 05.09.2008, 13:29 +0300 schrieb Damyan Ivanov: > > -=| Paul Menzel, Fri, Sep 05, 2008 at 09:21:01AM +0200 |=- > > > > This: > > > > > + echo 1 > > > > > + modprobe ath_pci > > > > > + sleep 1 > > > > > + ifconfig ath0 up > > > > > ath0: ERROR while getting interface flags: Kein passendes > > > > > Gerät gefunden (translation: No suitable device found.) > > > > and this: > > > [ 87.759957] MadWifi: unable to attach hardware: 'Hardware didn't > > > respond as expected' (HAL status 3) > > > > ring some bells from the past. You probably use an old version of > > madwifi sources, that does not work with the atheros chip in the eee. > > We used to distribute a patched package (madwifi-eeepc-source), but > > this is no longer necesary. > > These packages were installed before. > > Get fresh madwifi-source package from Sid, build and install the > > -modules package from it using module-assistant, > Ok. I did. > > $ # uncomment the eeepc.debian.net repository in /etc/apt/sources.list > $ # I did not add a sid repository, because packages.debian.org shows that > the versions are the same for linux-image-2.6.26-1-686 and madwifi* packages > $ sudo aptitude update && sudo aptitude safe-upgrade > $ sudo aptitude remove --purge madwifi-modules-2.6.26-1-686 madwifi-source > madwifi-tools > $ sudo m-a update > $ sudo m-a a-i madwifi # it installed also madwifi-tools
Did that actually build the modules? It may have used a previously built .deb. add "-f" to m-a a-i arguments to force module building. > $ # It still does not work. > > Detected WLAN module ath_pci on ath0 > + modprobe ath_pci > + sleep 1 > + ifconfig ath0 up > ath0: ERROR while getting interface flags: No such device > + exec /etc/acpi/actions/wireless.sh off > > > $ tail -f /var/log/messages > Sep 11 09:32:33 localhost kernel: [ 2179.559780] pciehp: Card present on > Slot(3) > Sep 11 09:32:34 localhost kernel: [ 2180.560682] program_fw_provided_values: > Could not get hotplug parameters > Sep 11 09:32:35 localhost kernel: [ 2180.840568] ath_pci 0000:01:00.0: > enabling device (0000 -> 0002) > Sep 11 09:32:35 localhost kernel: [ 2180.840599] ACPI: PCI Interrupt > 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 18 > Sep 11 09:32:35 localhost kernel: [ 2181.332544] MadWifi: ath_attach: > Switching rfkill capability off. > Sep 11 09:32:35 localhost kernel: [ 2181.334629] wifi0: Atheros AR2425 chip > found (MAC 14.2, PHY SChip 7.0, Radio 10.2) > Sep 11 09:32:35 localhost kernel: [ 2181.336463] ath_pci: wifi0: Atheros > 5424/2424: mem=0xf8000000, irq=18 > Sep 11 09:32:35 localhost kernel: [ 2181.535623] udev: renamed network > interface ath0 to wlan0 > Sep 11 09:32:37 localhost kernel: [ 2183.403510] ACPI: PCI interrupt for > device 0000:01:00.0 disabled > Sep 11 09:32:37 localhost kernel: [ 2183.459397] pciehp: Card not present on > Slot(3) > Sep 11 09:34:28 localhost kernel: [ 2294.618092] pciehp: PCI Express Hot Plug > Controller Driver version: 0.4 unloaded At least there is no "HAL status 3" error. > > unload/reload the module and all should be fine. > > Which modules should I have to reload? Is not that done by the > scripts. The scripts only un/load ath_pci. There are also others, I should have mentioned that. > Anyway I did not have time to do a reboot because the person owning > the Eee PC had to go. > > Now reading the logs, probably it was ath_hal not being reloaded. I > will test this soon. > > > Any ideas? Thanks, Hopefully the owher will reboot and suddelny find out that wireless works :) The only other idea I have is to increment the sleep value after modprobe ath_pci. Please see if a reboot helps first, having to wait for yet another second for the network to get up is irritating :) -- dam JabberID: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
_______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
