You are not logged in.
Pages: 1
I recently got arch running smoothly on a new asus laptop, but I just managed to break the wireless. I was checking out the function keys to see if they were all supported and pressed fn + F2 which apparently is a wireless kill switch.
I checked dmesg to make sure that was what caused it to fail. My problem is that after I reset the wireless kill switch my wireless stopped working completely.
I receive a segmentation fault when setting the essid and key with iwconfig. iwlist still works and the driver for my wireless card is loaded correctly. Any help would be super.
Last edited by bgodea (2007-01-28 02:19:28)
Offline
I have a Dell XPS M1710 laptop, and after the latest pacman upgrade Im having trouble with the ipw3945 daemon/drivers myself. Guess this is the appropriate log messages. Kernel boots fine, but after the ipw3945 daemon is started, X wont start and network daemon wont shutdown. Disable the ipw3945 daemon and everything is fine. Worked flawlessly before, so I have no idea what this may be..
Jan 25 21:49:16 xps ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
Jan 25 21:49:19 xps ieee80211_crypt: registered algorithm 'WEP'
Jan 25 21:49:19 xps BUG: unable to handle kernel paging request at virtual address ffffffa1
Jan 25 21:49:19 xps printing eip:
Jan 25 21:49:19 xps ffffffa1
Jan 25 21:49:19 xps *pde = 00004067
Jan 25 21:49:19 xps *pte = 00000000
Jan 25 21:49:19 xps Oops: 0000 [#1]
Jan 25 21:49:19 xps PREEMPT SMP
Jan 25 21:49:19 xps Modules linked in: arc4 ecb ieee80211_crypt_wep eth1394 usbhid ff_memless tsdev joydev intel_agp nvidia(P) agpgart sdhci mmc_core ohci1394 ieee1394 rtc psmouse i2c_i801 i2c_core serio_raw uhci_hcd ehci_hcd tg3 evdev sg snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_alloc ipw3945 ieee80211 ieee80211_crypt usbcore reiserfs sr_mod cdrom sd_mod ata_piix generic ide_core
Jan 25 21:49:19 xps CPU: 1
Jan 25 21:49:19 xps EIP: 0060:[<ffffffa1>] Tainted: P VLI
Jan 25 21:49:19 xps EFLAGS: 00010282 (2.6.19-beyond #1)
Jan 25 21:49:19 xps EIP is at 0xffffffa1
Jan 25 21:49:19 xps eax: c18e4000 ebx: f8ce73d0 ecx: ffffffa1 edx: f73d1dc3
Jan 25 21:49:19 xps esi: c1b5b885 edi: f73d1dd2 ebp: f73d1dcd esp: f73d1d98
Jan 25 21:49:19 xps ds: 007b es: 007b ss: 0068
Jan 25 21:49:19 xps Process iwconfig (pid: 3286, ti=f73d0000 task=c1a8c030 task.ti=f73d0000)
Jan 25 21:49:19 xps Stack: f887dccd c1abb5a0 c011f96e f73d1f44 c18e4400 01000202 c18e4000 00000000
Jan 25 21:49:19 xps c18e4ab0 00000005 04fdcab0 00000104 00000500 646f7200 00006f65 00000000
Jan 25 21:49:19 xps 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jan 25 21:49:19 xps Call Trace:
Jan 25 21:49:19 xps [<f887dccd>] ieee80211_wx_set_encode+0x19d/0x5c0 [ieee80211]
Jan 25 21:49:19 xps [<c011f96e>] activate_task+0x17e/0x1d0
Jan 25 21:49:19 xps [<f89dabd2>] ipw_wx_set_encode+0x62/0x150 [ipw3945]
Jan 25 21:49:19 xps [<c02ed9e1>] ioctl_standard_call+0x1b1/0x3b0
Jan 25 21:49:19 xps [<c02ee173>] wireless_process_ioctl+0x333/0x3e0
Jan 25 21:49:19 xps [<f89dab70>] ipw_wx_set_encode+0x0/0x150 [ipw3945]
Jan 25 21:49:19 xps [<f89dab70>] ipw_wx_set_encode+0x0/0x150 [ipw3945]
Jan 25 21:49:19 xps [<c02d62b0>] sock_ioctl+0x0/0x220
Jan 25 21:49:19 xps [<c02d62b0>] sock_ioctl+0x0/0x220
Jan 25 21:49:19 xps [<c02e2e03>] dev_ioctl+0x213/0x390
Jan 25 21:49:19 xps [<c016aee2>] __handle_mm_fault+0x222/0x920
Jan 25 21:49:19 xps [<c01729cd>] free_pages_and_swap_cache+0x8d/0xb0
Jan 25 21:49:19 xps [<c02d62b0>] sock_ioctl+0x0/0x220
Jan 25 21:49:19 xps [<c018a7bb>] do_ioctl+0x2b/0x90
Jan 25 21:49:19 xps [<c018a87c>] vfs_ioctl+0x5c/0x2b0
Jan 25 21:49:19 xps [<c018ab42>] sys_ioctl+0x72/0x90
Jan 25 21:49:19 xps [<c01032b1>] sysenter_past_esp+0x56/0x79
Jan 25 21:49:19 xps =======================
Jan 25 21:49:19 xps Code: Bad EIP value.
Jan 25 21:49:19 xps EIP: [<ffffffa1>] 0xffffffa1 SS:ESP 0068:f73d1d98
Jan 25 21:49:20 xps <6>NET: Registered protocol family 10
Jan 25 21:49:34 xps kdm[3287]: X server startup timeout, terminating
Jan 25 21:49:49 xps kdm[3287]: X server termination timeout, killing
Jan 25 21:49:59 xps kdm[3287]: X server is stuck in D state; leaving it alone
Jan 25 21:49:59 xps kdm[3287]: X server for display :0 can't be started, session disabled
Anyone knows of a solution for this?
Offline
same problem as kriguns here
Offline
My fault. That release was intended for 2.6.20, hence it not working. It will be corrected shortly.
Offline
Nice! Thanks
Offline
Pages: 1