You are not logged in.
I'm trying out Arch for the first time and have run into a problem. When I try bringing up my wireless card (ifconfig wlan0 up) my computer freezes. The only thing I can do is forcefully reboot it by holding the power button down.
My wireless card:
[nikosapi@nikosapi-laptop ~]$ lspci | grep Wireless
04:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Kernel version:
[nikosapi@nikosapi-laptop ~]$ uname -a
Linux nikosapi-laptop 2.6.35-ARCH #1 SMP PREEMPT Fri Aug 27 16:22:18 UTC 2010 i686 AMD Athlon(tm) Processor L110 AuthenticAMD GNU/Linu
It used to work fine in all the other distros I've used in the past (Ubuntu, Fedora, etc) so it's definitely a regression. My kernel logs show nothing, and I can't seem to find any similar reports. What can I do to further debug this problem?
Last edited by nikosapi (2010-09-04 00:39:12)
Offline
Can you post the output of lsmod?
Offline
Can you post the output of lsmod?
With pleasure
The wireless card uses the ath9k driver if that's what you're looking for.
Module Size Used by
ipv6 239277 8
fuse 54698 3
ext2 56204 1
snd_hda_codec_realtek 193684 1
arc4 1070 2
snd_seq_dummy 1079 0
joydev 7503 0
ecb 1589 2
snd_seq_oss 25104 0
radeon 811403 2
snd_seq_midi_event 4496 1 snd_seq_oss
ath9k 68132 0
ath9k_common 4386 1 ath9k
ath9k_hw 268674 2 ath9k,ath9k_common
snd_hda_intel 19020 0
snd_seq 41752 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
uvcvideo 53488 0
ath 6786 2 ath9k,ath9k_hw
ttm 44599 1 radeon
videodev 39124 1 uvcvideo
v4l1_compat 13562 2 uvcvideo,videodev
snd_seq_device 4369 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_hda_codec 67274 2 snd_hda_codec_realtek,snd_hda_intel
snd_pcm_oss 33662 0
snd_mixer_oss 14686 1 snd_pcm_oss
snd_hwdep 4764 1 snd_hda_codec
mac80211 167958 2 ath9k,ath9k_common
snd_pcm 58308 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
drm_kms_helper 22011 1 radeon
ohci_hcd 19595 0
drm 134132 4 radeon,ttm,drm_kms_helper
snd_timer 15423 2 snd_seq,snd_pcm
cfg80211 124335 4 ath9k,ath9k_common,ath,mac80211
video 15889 0
ehci_hcd 32860 0
i2c_algo_bit 4407 1 radeon
i2c_piix4 7772 0
snd 43283 11 snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_seq,snd_seq_device,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_hwdep,snd_pcm,snd_timer
battery 7879 0
output 1448 1 video
ac 2329 0
psmouse 51529 0
wmi 5962 0
soundcore 5025 1 snd
usbcore 121705 4 uvcvideo,ohci_hcd,ehci_hcd
processor 25126 1
r8169 33406 0
rfkill 12854 1 cfg80211
serio_raw 3566 0
i2c_core 15599 6 radeon,videodev,drm_kms_helper,drm,i2c_algo_bit,i2c_piix4
pcspkr 1359 0
shpchp 27005 0
snd_page_alloc 5981 2 snd_hda_intel,snd_pcm
button 3746 0
ati_agp 4722 0
thermal 9786 0
k8temp 2663 0
evdev 6820 15
led_class 1843 1 ath9k
mii 3198 1 r8169
pci_hotplug 21811 1 shpchp
sg 20932 0
agpgart 23520 3 ttm,drm,ati_agp
rtc_cmos 7746 0
rtc_core 11831 1 rtc_cmos
rtc_lib 1494 1 rtc_core
ext4 282514 2
mbcache 4290 2 ext2,ext4
jbd2 58396 1 ext4
crc16 1053 1 ext4
sd_mod 26768 5
ahci 17813 0
pata_acpi 2308 0
libahci 16174 5 ahci
pata_atiixp 2841 0
libata 140707 4 ahci,pata_acpi,libahci,pata_atiixp
scsi_mod 105888 3 sg,sd_mod,libata
Offline
itsbrad212 wrote:Can you post the output of lsmod?
The wireless card uses the ath9k driver if that's what you're looking for.
I was just trying to see if you had ath9k loaded.
What you are experiencing seems to be a known problem:
http://www.spinics.net/lists/linux-wire … 54555.html
I'm guessing that the problem lies with your kernel or net-tools (ifconfig).
Have you updated net-tools lately?
cat /var/log/pacman.log | grep net-tools
Try to test different factors each time, such as downgrading the kernel but leaving net-tools the same, downgrading net-tools but leaving the kernel the same, etc.
Last edited by cesura (2010-09-03 22:12:39)
Offline
nikosapi wrote:itsbrad212 wrote:Can you post the output of lsmod?
The wireless card uses the ath9k driver if that's what you're looking for.
I was just trying to see if you had ath9k loaded.
What you are experiencing seems to be a known problem:
http://www.spinics.net/lists/linux-wire … 54555.htmlI'm guessing that the problem lies with your kernel or net-tools (ifconfig).
Have you updated net-tools lately?cat /var/log/pacman.log | grep net-tools
Try to test different factors each time, such as downgrading the kernel but leaving net-tools the same, downgrading net-tools but leaving the kernel the same, etc.
Awesome, my google-fu is weak apparently.
I just did a net-install a few hours ago so I assume I have the latest net-tools:
[2010-09-03 13:40] installed net-tools (1.60-14)
I'll try downgrading the kernel first and let you know how it goes, thanks!
Offline
I just did a net-install a few hours ago so I assume I have the latest net-tools:
[2010-09-03 13:40] installed net-tools (1.60-14)
I was pointing out that to show you that just because a package is in the official repos doesn't mean it will work for you.
Offline
I tried a bunch of stuff and I'm glad to report that it works now!
First I tried downgrading to the first kernel in .35 series (I went from 2.6.35.4 down to 2.6.35.1) and the problem persisted. Then I went down to the last .34 kernel (2.6.34.3) available from an arch testing mirror. I was quite happy to see that the .34 kernel did the trick. I didn't stop there, I upgraded back to 2.6.35.4 and then got the compat-wireless drivers from 2010-08-21 and that also worked. I went with a non-current version of compat-wireless because it was what the guy used in the thread you linked to.
Anyway, it works now, thank you. Should I report this on the bug tracker?
Offline
Anyway, it works now, thank you. Should I report this on the bug tracker?
I'm glad to hear it! If you think you have sufficient information and have nailed it down to the kernel (which it sounds like you have), then I don't see the harm in reporting it if it hasn't been already.
Offline
nikosapi wrote:Anyway, it works now, thank you. Should I report this on the bug tracker?
I'm glad to hear it! If you think you have sufficient information and have nailed it down to the kernel (which it sounds like you have), then I don't see the harm in reporting it if it hasn't been already.
Offline
itsbrad212 wrote:nikosapi wrote:Anyway, it works now, thank you. Should I report this on the bug tracker?
I'm glad to hear it! If you think you have sufficient information and have nailed it down to the kernel (which it sounds like you have), then I don't see the harm in reporting it if it hasn't been already.
Awesome. I guess that would make this thread solved, although you had to downgrade your kernel. If it is, could you please prepend [SOLVED] to the title by editing the first post?
Offline