Re: Wireless stopped working after kernel upgrade
On Sat, Aug 29, 2009 at 10:53 PM, Osamu Aokios...@debian.org wrote: Hi, On Sat, Aug 29, 2009 at 10:09:20PM -0500, Autumn Lansing wrote: I've wasted most of my Saturday trying to get wireless to work with the latest kernel on my 64-bit Sid box. I have an Atheros ar5001x card, and I've been using an older 2.6.22 kernel with madwifi drivers for the past two years. I'm rather conservative in upgrading my kernel, precisely because of issues like I've had today, but I found need for 2.6.30-1. You know there is FREE driver for Atheros chips in kernel now. I guess yours is one of them. As madwifi is gone from Debian testing and unstable, I decided to switch to the ath5K drivers included in the latest kernel. I followed the instructions here: http://wiki.debian.org/ath5k, with the exception that I use wicd to manage my network, and as such I had no need to amend my interfaces file. After rebooting and a little fiddling, the ath5k driver came up, and wicd found my wireless network. I can't however connect to it. It tries to connect, usually timing out while getting a valid authentication, but sometimes it manages to validate the WEP key and attempts to obtain an IP address but then times out doing that. Have you ajusted configuration to new device names? As udev insists on renaming wlan0 to ath0, I haven't had to rename the device in configuration files. I've followed everything else in the instructions on the page I listed though. ath_pci is blacklisted, and ath5k is loaded. Osamu Autumn -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Wireless stopped working after kernel upgrade
I now have wireless up and working again, though I'm not quite sure how I did it. I was frustrated dealing with the Atheros card, so a few minutes ago I switched it for an Airlink N card, but that was unsuccessful, as the firmware wouldn't load using either the ra2860sta kernel module or ndiswrapper, so I switched back to my Atheros card. After rebooting, iwconfig didn't show any wireless networks, and ifconfig didn't show the device at all, though lspci reported it. I unloaded the ath5k module and reloaded it. Still nothing, so I rebooted again on a whim, and the card now mysteriously works. Oddly, udev no longer renames it to ath0. Instead, the card is named wlan1. I have a feeling that this might have been the issue, as all the instructions for using the ath5k driver say to use wlan instead of ath, but I'm hardly qualified to say for certain. Perhaps trying the other card and then reinstalling the Atheros card caused udev to act differently. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Wireless stopped working after kernel upgrade
Thanks, Stefan! I checked the file, which states that it is generated by the /lib/udev/write_net_rules program, probably run by the persistent-net-generator.rules rules file, and there is a line for the madwifi ath_pci driver that sets the wireless card to ath0. In addition, there's a line for the ath5k driver that sets it to wlan1. Ndiswrapper, which I used while attempting to solve the problem with the Airlink card, sets it to wlan0. I removed the line for the ath_pci driver. Hopefully that will prevent this problem from happening again. The ath_pci driver was blacklisted though, so I don't know why that rule would try to run, as the module wasn't loading, unless all the rules are run regardless of whether a driver is loaded or not. Given that the rule was written in the file before the ath5k rule, that would explain why it took precedence over it. I imagine that the ath5k driver was originally naming the device wlan0, before I installed ndiswrapper, which took over the name. That might also explain why ndiswrapper didn't work either. And it would explain why the ath5k driver finally did work. With ndiswrapper using the name wlan0, the ath5k driver chose wlan1, which had no conflicts. During my research into this problem, I saw other people mention that udev was renaming wlan0 to ath0, but no one seemed to think it was a problem, so I didn't either. Apparently it was. Thanks, Autumn -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Wireless stopped working after kernel upgrade
I've wasted most of my Saturday trying to get wireless to work with the latest kernel on my 64-bit Sid box. I have an Atheros ar5001x card, and I've been using an older 2.6.22 kernel with madwifi drivers for the past two years. I'm rather conservative in upgrading my kernel, precisely because of issues like I've had today, but I found need for 2.6.30-1. As madwifi is gone from Debian testing and unstable, I decided to switch to the ath5K drivers included in the latest kernel. I followed the instructions here: http://wiki.debian.org/ath5k, with the exception that I use wicd to manage my network, and as such I had no need to amend my interfaces file. After rebooting and a little fiddling, the ath5k driver came up, and wicd found my wireless network. I can't however connect to it. It tries to connect, usually timing out while getting a valid authentication, but sometimes it manages to validate the WEP key and attempts to obtain an IP address but then times out doing that. I've tried every suggestion that I could find through Google and this list, and none of them worked. The driver is loading correctly, and my card is being detected. It just won't connect. I even switched back to the madwifi drivers at one point, installing from source, and it still wouldn't connect to the router. (That plus the signal strength was horrible in madwifi.) The card was working properly this morning, so it's doubtful the problem is in the hardware. I've also tried switching to WAP and turning off security altogether, but that made no difference. One odd thing that occurs is that udev keeps renaming wlan0 to ath0. The ath5k instructions state to change all references of ath0 to wlan0, but that results in Device not found errors. The output from iwconfig is: ingrid:/home/autumn# iwconfig lono wireless extensions. eth1 no wireless extensions. eth3 no wireless extensions. wmaster0 no wireless extensions. ath0 IEEE 802.11bg ESSID:JohnWayne Mode:Managed Frequency:2.417 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 pan0 no wireless extensions. dmesg shows this every time I attempt to connect to the wireless router: [ 2707.953219] ath0: direct probe to AP 00:18:4d:24:09:8f try 1 [ 2708.152034] ath0: direct probe to AP 00:18:4d:24:09:8f try 2 [ 2708.352026] ath0: direct probe to AP 00:18:4d:24:09:8f try 3 [ 2708.552034] ath0: direct probe to AP 00:18:4d:24:09:8f timed out [ 2713.502701] ath5k phy0: noise floor calibration timeout (2417MHz) [ 2714.666870] ath5k phy0: noise floor calibration timeout (2417MHz) [ 2714.683331] ath0: direct probe to AP 00:18:4d:24:09:8f try 1 [ 2715.114532] ath5k phy0: noise floor calibration timeout (2417MHz) [ 2715.120196] ath0: direct probe to AP 00:18:4d:24:09:8f try 2 [ 2715.320031] ath0: direct probe to AP 00:18:4d:24:09:8f try 3 [ 2715.520029] ath0: direct probe to AP 00:18:4d:24:09:8f timed out ifconfig gives this result: ingrid:/home/autumn# ifconfig ath0 Link encap:Ethernet HWaddr 00:18:02:42:ac:d1 UP BROADCAST 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:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth1 Link encap:Ethernet HWaddr 00:50:bf:3a:2f:47 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:bfff:fe3a:2f47/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1470 errors:0 dropped:0 overruns:0 frame:0 TX packets:1940 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:588211 (574.4 KiB) TX bytes:416006 (406.2 KiB) Interrupt:19 Base address:0x6000 loLink 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:146 errors:0 dropped:0 overruns:0 frame:0 TX packets:146 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12328 (12.0 KiB) TX bytes:12328 (12.0 KiB) wmaster0 Link encap:UNSPEC HWaddr 00-18-02-42-AC-D1-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 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:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) My etc/network/interfaces file has no references to ath0 due to my use of wicd. # The loopback network
Re: Re: aterm segmentation fault
Thank you for the suggestion, however the problem ended up being my motherboard. Not long after I asked for help I began to get even more strange errors, and when being forced to reboot again I couldn't even get into my bios. A new motherboard and some repair work took care of the problem, and aterm works perfectly now. Thanks again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
aterm segmentation fault
Aterm has suddenly decided to stop working. When I call it from the menu
it fails to start. When trying to run a command that uses aterm through
nedit I receive a segmentation fault error. Running an strace verifies
the segmentation fault, though the results of the strace are pretty much
Greek to me. Bash works correctly, though xterm is also affected by this
problem. When I attempt to run xterm it ties up all my CPU, and I can't
do anything else. I'm forced to reboot. I installed rxvt to check it
too, and it produces that same results as xterm.
This all occured after I changed my video card. I was using an old Nvidia
TNT2 and installed an Nvidia GeForce FX5200. Aterm worked before this but
not after. I have removed and installed aterm to no success. I've
tracked down all the common files between aterm, xterm, and rxvt and can't
find a bug report that describes my problem, and I can't find anything on
google, so I'm at a loss on how to fix this problem. Any ideas?
Ending result of strace:
set_thread_area({entry_number:-1 - 6, base_addr:0xb73156c0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7f77000, 35648) = 0
brk(0) = 0x8067000
brk(0x8088000) = 0x8088000
open(/dev/zero, O_RDWR) = 3
mmap2(NULL, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0xb7f7e000
close(3)= 0
getpid()= 2919
mmap2(NULL, 397312, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb72b4000
modify_ldt(17, {entry_number:666, base_addr:0x8067320, limit:512,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0,
seg_not_present:0, useable:1}, 16) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Re: Re: xdm/gdm failure after dist-upgrade
Simply delete or rename your current xorg.conf file, then run dpkg-reconfigure xserver-xorg again. That worked for me. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Today's disaster with xorg update
On 15 Apr 2006, Anthony Campbell wrote: On 15 Apr 2006, Gonzalo HIGUERA D?AZ wrote: 2006--04-15 15:00 +0200, Gonzalo HIGUERA D?AZ [EMAIL PROTECTED] wrote: 2006-04-15 13:56 +0200, Anthony Campbell [EMAIL PROTECTED]: and to make matters worse something I've done to try to solve the problem has made matters worse. I'm now getting a new error about not being able to move /var/log/Xorg.log.0. I'm seriously thinking of purging all the packages related to X and starting again, except that I don't know which they are. xorg*, I think. I hope that if you have to resort to that, it will solve your problems. xserver-xorg*, rather (though if the dependancies are installed and uninstalled automatically --as with aptitude-- clearing xorg should show the rest). -- Gonzalo HIGUERA D?AZ [EMAIL PROTECTED] Unfortunately I ended by removing ALL the X-related stuff, which will have to be reinstalled later. Meanwhile, I still cannot get X to work. I reinstalled xorg but the same errors recur, i.e. 1. Cannot mv /var/log/Xorg.log.o /var/log/Xorg.log.0 If I try as root, the above error does not occur but instead I get: 2. could not open default font fixed. I'm not sure if it is possible to revert to the earlier xfree86 while this is going on. Footnote: After a bit of googling, I tried adding the s flag to /usr/bin/Xorg and this avoids the /var/log problem (though I don't know if it's the Right Thing to do). The font problem remains. Anthony I had the same problem. Simply delete or rename your xorg.conf file and run dpkg-reconfigure xserver-xorg. Reconfiguring will install a new xorg.conf file with the proper font paths and settings. The problem lies in the way Xorg handles upgrading the .conf file. It won't touch it if it's been customized, which unfortunately causes serious problems when a major upgrade changes the way Xorg works. Autumn __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
