[Debian-eeepc-devel] eee 900 wifi problems

Sergio Blanco crimsomshadow at gmail.com
Fri Nov 7 12:26:46 UTC 2008


Nobody knows what to do?

I still insist, none of the USB Installers could scan, and only the oldest I
found could connect. Once I can scan for APs, probably everything will go
right

On Wed, Oct 29, 2008 at 9:00 PM, Sergio Blanco <crimsomshadow at gmail.com>wrote:

> Meanwhile the moderator accepts (or not) the message with the log file
> (40K), Iresend the text that accompanies the message ;-)
> ----------------------------------------
>
> Nope, no dongle, just basic eee 900.
>
> Lets  put some info here.
>
> lsmod gives out all this:
>
> Module Size Used by
> ipv6 235300 8
> usbhid 35904 0
> hid 33184 1 usbhid
> ff_memless 4392 1 usbhid
> wlan_scan_sta 11264 1
> ath_rate_sample 11072 1
> ath_pci 202552 0
> wlan 193776 4 wlan_scan_sta,ath_rate_sample,ath_pci
> ath_hal 300736 3 ath_rate_sample,ath_pci
> i915 25280 2
> drm 65256 3 i915
> reiserfs 189920 1
> pciehp 28540 0
> pci_hotplug 23460 1 pciehp
> joydev 8480 0
> usbtouchscreen 8356 0
> psmouse 32336 0
> serio_raw 4740 0
> rng_core 3940 0
> pcspkr 2432 0
> i2c_i801 7920 0
> i2c_core 19828 1 i2c_i801
> iTCO_wdt 9508 0
> video 16400 0
> output 2912 1 video
> battery 10180 0
> ac 4196 0
> button 6064 0
> eeepc_laptop 7440 0
> snd_hda_intel 324248 0
> snd_pcm 62628 1 snd_hda_intel
> atl2 22744 0
> snd_seq 41456 0
> snd_timer 17800 2 snd_pcm,snd_seq
> snd_seq_device 6380 1 snd_seq
> snd 45604 5 snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device
> intel_agp 22300 1
> agpgart 28776 3 drm,intel_agp
> soundcore 6368 1 snd
> snd_page_alloc 7816 2 snd_hda_intel,snd_pcm
> evdev 8000 7
> xfs 458040 2
> usb_storage 75936 0
> sd_mod 22200 5
> ata_piix 14180 3
> ata_generic 4676 0
> ahci 23176 0
> libata 140384 3 ata_piix,ata_generic,ahci
> scsi_mod 129356 3 usb_storage,sd_mod,libata
> dock 8272 1 libata
> ide_pci_generic 3908 0 [permanent]
> ide_core 96168 1 ide_pci_generic
> ehci_hcd 28428 0
> uhci_hcd 18672 0
> usbcore 118160 6 usbhid,usbtouchscreen,usb_storage,ehci_hcd,uhci_hcd
> thermal 15228 0
> processor 32576 2 thermal
> fan 4164 0
> thermal_sys 10856 4 video,thermal,processor,fan
>
> -----------------------
>
> Tail of syslog
>
> Oct 29 19:51:46 pegasus dhclient: Sending on LPF/eth0/00:22:15:02:46:49
> Oct 29 19:51:46 pegasus dhclient: Sending on Socket/fallback
> Oct 29 19:51:46 pegasus kernel: [ 425.169138] atl2: eth0 NIC Link is Up<100
> Mbps Full Duplex>
> Oct 29 19:53:46 pegasus kernel: [ 545.293749] ath_hal: module license
> 'Proprietary' taints kernel.
> Oct 29 19:53:46 pegasus kernel: [ 545.296189] AR5210, AR5211, AR5212,
> AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417)
> Oct 29 19:53:47 pegasus kernel: [ 545.323728] ACPI: PCI Interrupt
> 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 18
> Oct 29 19:53:47 pegasus kernel: [ 545.323752] PCI: Setting latency timer of
> device 0000:01:00.0 to 64
> Oct 29 19:53:47 pegasus kernel: [ 545.815093] MadWifi: ath_attach:
> Switching rfkill capability off.
> Oct 29 19:53:47 pegasus kernel: [ 545.849588] wifi0: Atheros AR2425 chip
> found (MAC 14.2, PHY SChip 7.0, Radio 10.2)
> Oct 29 19:53:47 pegasus kernel: [ 545.858058] ath_pci: wifi0: Atheros
> 5424/2424: mem=0xfbef0000, irq=18
> ----------------------------------------------
>
> Ifconfig
>
> ath0 Link encap:Ethernet HWaddr 00:15:af:a7:e0:d6
>   inet6 addr: fe80::215:afff:fea7:e0d6/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> eth0 Link encap:Ethernet HWaddr 00:22:15:02:46:49
>   inet addr:192.168.25.19 Bcast:192.168.25.255 Mask:255.255.255.0
>   inet6 addr: fe80::222:15ff:fe02:4649/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>   RX packets:1600 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:1537 errors:0 dropped:0 overruns:0 carrier:4
>   collisions:0 txqueuelen:1000
>   RX bytes:1392191 (1.3 MiB) TX bytes:0 (0.0 B)
>   Memory:fbfc0000-fc000000
>
> lo Link encap:Local Loopback
>   inet addr:127.0.0.1 Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING MTU:16436 Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> wifi0 Link encap:UNSPEC HWaddr
> 00-15-AF-A7-E0-D6-65-74-00-00-00-00-00-00-00-00
>   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:280
>   RX bytes:132 (132.0 B) TX bytes:1426 (1.3 KiB)
>   Interrupt:18
> --------------------------------------------------------
>
> iwconfig
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wifi0 no wireless extensions.
>
> ath0 IEEE 802.11g ESSID:"" Nickname:""
>   Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
>   Bit Rate:0 kb/s Tx-Power:17 dBm Sensitivity=1/1
>   Retry:off RTS thr:off Fragment thr:off
>   Encryption key:off
>   Power Management:off
>   Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm
>   Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>   Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> ------------------------------------------------------------
>
> Result of iwlist ath0 scanning just after modprobing ath_pci
>
> ath0 Interface doesn't support scanning : Network is down
>
> Same command after ifconfig ath0 up
>
> ath0 No scan results
> -----------------------------------------------------
>
> What about this lines of syslog?
>
> Oct 29 19:45:01 pegasus kernel: [ 15.936179] pciehp: Device 0000:03:00.0
> already exists at 3:0, cannot hot-add
> Oct 29 19:45:01 pegasus kernel: [ 15.936289] pciehp: Cannot add device
> 0x3:0
> Oct 29 19:45:01 pegasus kernel: [ 16.940193] Load service driver hpdriver
> on pcie device 0000:00:1c.1:pcie02
> Oct 29 19:45:01 pegasus kernel: [ 16.940231] pciehp: HPC vendor_id 8086
> device_id 2664 ss_vid 0 ss_did 0
> Oct 29 19:45:01 pegasus kernel: [ 17.944184] pciehp: Device 0000:01:00.0
> already exists at 1:0, cannot hot-add
> Oct 29 19:45:01 pegasus kernel: [ 17.944274] pciehp: Cannot add device
> 0x1:0
> Oct 29 19:45:01 pegasus kernel: [ 18.948196] Load service driver hpdriver
> on pcie device 0000:00:1c.2:pcie02
>
> Any ideas?
>
>
> On Wed, Oct 29, 2008 at 7:29 PM, Federico Castagnini <
> federico.castagnini at gmail.com> wrote:
>
>> On Wed, Oct 29, 2008 at 3:21 PM, Paul Menzel
>> <paulepanter at users.sourceforge.net> wrote:
>> > Dear Federico,
>> >
>> >
>> > Am Mittwoch, den 29.10.2008, 14:40 -0200 schrieb Federico Castagnini:
>> >> On Wed, Oct 29, 2008 at 7:18 AM, Ben Armstrong
>> >> <synrg at sanctuary.nslug.ns.ca> wrote:
>> >> > On Wed, 29 Oct 2008 06:57:37 +0100
>> >> > "Sergio Blanco" <crimsomshadow at gmail.com> wrote:
>> >> >> I'm using wicd so using the interfaces file is useless for me. Even
>> if I
>> >> >> tried, the first problem to solve would be it's inability to scan
>> for APs.
>> >> >> If I have the interface up and running it doesn't matter if it knows
>> where
>> >> >> to connect, I should be able to search for networks, no?
>> >>
>> >> I have made almost the same tests and still have the same problem, can
>> >> not scan or connect.
>> >>
>> >> With a usb dongle (mod rt73) i was able to scan and use that interface
>> >> as expected, so the trouble is with the atheros wifi device...
>> >>
>> >> This problem came up with an upgrade i made last week, that upgrade
>> >> the kernel (plus other things) from 2.6.26-4? to 2.6.26-8.
>> >>
>> >> I think this is something relevant.
>> >
>> > You can find out inspecting /var/log/dpkg.log.
>> >
>> > […]
>> >
>> >> > Let's start with logs.  Post /var/log/syslog and we can start there.
>> >
>> > Please provide the information, Ben asked for.
>> >
>>
>> finaly, looking into syslog after enabling the wifi, found a line saying
>> unable to load wlan_scan_sta
>>
>> and later google say:
>> http://madwifi.org/ticket/1737#comment:2
>>
>> now the Atheros wifi is working again.
>>
>> Thank you all who help us with this problem.
>> Federico Castagnini
>>
>> Sergio, do you have some dongle like me?
>> _______________________________________________
>> Debian-eeepc-devel mailing list
>> Debian-eeepc-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/attachments/20081107/927168e5/attachment-0001.htm 


More information about the Debian-eeepc-devel mailing list