Debian Configuration :: Wireless Not Working On Squeeze?
Feb 14, 2011
I am moving over to debian from ubuntu, and the latest install is to an acer aspire one netbook, the wireless card seems to be working and I can see available networks and even connect to mine (with WPA encryption) via the gnome network manager, however opening a browser or pinging both local and external machines all fail. its as if the OS does not not know to use the card. The wired works fine.
If memory serves the card is identified by lspci as Atheros AR5007.
There is no reference to wlan0 in etc/network/interfaces.
I do not have that system on now and have to leave for work, but I can post any further info from conf files etc as required when i get home tonight... Just thought I'd post a quick description in case I'm missing something obvious...
I don't print much, but tonight needed to print and found that none of the printers were listed in Okular or Openoffice, then when I tried to open Cups Administration http://localhost:631/ I got the error message Connection to Server Refused
This morning i installed Debian Squeeze and I'm sure it that was a good choice! I got my wireless stick to work (Linksys: Wusb600n v2), installed Chromium, VLC and some other stuff... and ye. I want to get Compiz working on my system! I'm not sure that my current drivers can deal with it, thought. I'm not good at Linux and I don't know what should I install (if there is something) so that I can have get better performance from my video-card. I made HardInfo report of my system. What are my options? How can I make the performance better and, maybe, run Compiz?
I upgraded from lenny to squeeze on a notebook and I can no longer connect to the wireless network. The computer is an LG notebook and the network card is ralink rt2860. I am using Gnome and NetworkManager. The wireless key is WEP hex. It was working fine with lenny till before the upgrade. After the upgrade, the network card stopped working. So, I checked
Then I reinstalled the driver with apt-get install firmware-ralink wireless-tools Then the network manager tray started working again and saw the network, but cannot connect. It was trying to connect but timed out and kept asking for the password. It is the correct password. I tried deleting the old connection and recreated a new one in the nm. But still does not work.
I have been using my system for couple of weeks, and normally update software when the icon is displayed on top bar (gnome). Last couple of days there were updates for X, and I am not sure whether that is the cause of my problem. Once bootup, I get the login screen. When enter the password the login screen keep coming back. there is no error about any password issue, or anything. It keeps prompt me to enter the password.
I could login back the following way.
1. ctrl + alt + F1 , and login with the same username/pwd as for X 2.change to root 3.pkill gdm3 4.exit from root to user privilege 5. startx
The system starts X correctly and no login screen is displayed. I could use the system as usual.
The only thing I did custom to my system was upgrading to the latest kernel (2.6.38) using the source. This was to get support for my hardware, but that was about a month ago. I do not see anything in /var/log (X, demesg etc).
The computer networking works fine with a normal static setup, but adding a USB wireless device is not successful. It is my own network so the wpa-ssid and wpa-psk are known to work with Lenny and a previous wireless device.The device is recognized (lsusb) and the driver is confirmed to be in the kernel (lsmod). Here is the iwconfig output:
wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off
After typing: ifconfig wlan0 192.168.1.144 up I can ping that address, but it is not working. I have just done a fresh install of Sid so that I could get the 2.6.35 kernel which contains the ath9k_htc driver for the USB wireless device that I am using. The firmware is ar9271.fw but my source of that is questionable because it does not seem readily available. I am temporarily using a PCMCIA wired connection which is what I am using to connect to the computer via telnet. (This is just for convenience so as to avoid getting up all the time.) Here is the ifconfig output:
I've been enjoying wireless for a long time on Squeeze (iwl3945) with KDE, but the recent network manager update stopped that. I've tried a few things, like going back to /etc/network/interfaces and ifup wlan0 that I use with Lenny, but still not working.
Testing distribution. Installed Linux 3.0 but left 2.6.32 on as backup. When I boot into the old kernel, wireless mostly works OK, but never when I boot with the new kernel.
Results of dmesg|grep wlan0 on 2.6:
[ 22.005102] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.196774] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.644779] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 30.688053] wlan0: direct probe to AP 00:19:5b:06:9f:ba (try 1) [ 30.694053] wlan0: direct probe responded
Noticing the Access Point looked like it needed the MAC address, I ran iwconfig wlan0 ap <MACADDRESS> and sometimes it will work, and wicd can connect to the access point. But sometimes the command fails to run.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I recently just installed Squeeze on an ia64 system and was having some troubles with running VNC.I get the following error, more specifically for some reason I get a malloc - memory corruption error:
Xtightvnc(9165): unaligned access to 0x60000000001ea06c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea074, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea07c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea084, ip=0x4000000000268280
After display all the code above, it just stops. The port 5901 is still closed - if it runs properly, would it open automatically?Is there something that is incompatible? Or am I missing some system configuration component?
how to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
I installed Firestarter firewall on debian Squeeze.Now i note there is a gui available in System->Administration which apparently does not need to be running all the time - its not set up to start on boot.When I boot I notice the boot message has a line saying "Starting Firestarter firewall .... failed"When I am logged in and type "/etc/init.d/firestarter status" as the Firestarter FAQs say, I get"Firestarter is running... ... (warning)"I can run the gui manually and still same message.
When I activate Tor in Iceweasel, it forbids me access to the internet completely. Even attempting Google results in "Iceweasel is configured to use proxy server that is refusing connection".
I have seen this in Lenny, too - it was caused by activating Tor without having installed privoxy. I installed privoxy and everything was okay. In Squeeze, Tor is using polipo. Polipo is installed and running. I have not played with settings of polipo or Tor, the configuration is the same as it was after installation.
What can be wrong? I am a rather an user than a networking guru. I am connected to internet by means of DHCP, no local lans, no special routings, no additional proxies. I have already tired to reinstall polipo.
Just installed squeeze on a new laptop(had been runny Lenny on my older one with no issues, but no sound or wireless on the new one).I decided to install the ATI drive for my Radeon Mobility 4500(or some close revision) because the fan is constantly running and based on some other postings, it seems that it could be the graphics card causing it.Downloaded the driver from ATI's site and it seemed to install fine but when starting X.
When I try to downgrade from sid squeeze I don't get GDM running just a login promt after a reboot.Have also reinstalled nvidia driver but still only login promt.I did aptitude update and aptitude full-upgrade after changing sources.list from sid to squeeze.
Got a problem mounting my Windows partition in Squeeze. It keeps refusing to mount it for me in Dolphin. I am a member of the disk and fuse groups, /dev/fuse is owned by root:fuse, and /sbin/mount.ntfs points to /sbin/mount.ntfs-3g, which in turn points to the ntfs-3g executable. I kind of need this ASAP. I am supposed to be finishing with this machine in 35min, and I am dead in the water without the ability to copy some files from the Squeeze ext4 partition over.
I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors.
The most interesting line from dmesg is:
Here is the full output from dmesg:
I found a thread that indicated that this bug was fixed in the next kernel version: 2.6.32-6. I am willing to upgrade the kernel to get rid of my problems. Is a squeeze kernel at 2.6.32-6 or higher available? If so, where? I have not compiled my own kernel, and am not very interested in getting into that.
I use my laptop at the college, and I've to suspend him frequently. So, I've decided to install the package pm-utils, to hibernate my PC, instead of power off it. When I try to do "# pm-hibernate", a tty appear, and this error is displayed :
[3506.405310] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2 [3506.405310] PM: Device usb1 failed to freeze: error -2 This is the result in pm-suspend.log : Initial commandline parameters:
I have upgraded my server to Debian 6.0 Squeeze but it looks like some of my sites are not compatible with PHP 5.3.x so I would like to revert to previous 5.2.6 version.So my question is what to do?a) Remove PHP 5.3.x from system via apt-get and install my old 5.2.6 from old archives at /var/cache/apt/archivesorb) just try to update from archives PHP to 5.2.6?
-rw-r--r--. 1 root root 2413316 May 11 2008 libapache2-mod-php5_5.2.0-8+etch11_i386.deb -rw-r--r--. 1 root root 2413290 Oct 6 2008 libapache2-
As a long time user of some other distributions I decided to switch to Debian and installed 6.0 from amd64 kde cd image.Upon logging to KDE I discovered thatant locate knetworkmanager anywhere,it doesnt autostart and I could not find it anywhere else.I am connecting through a wireless network to the Internet so I cant connect through the Ethernet to download it through apt-get for example,if it is not installed by default.lly confused,knetworkmanager is standard tool in KDE but I cant find it in Debian 6.0
A couple days ago I installed Debian Lenny (netinst) to my friend's laptop, a IBM Thinkpad T23. Got a black screen after gdm loaded and the laptop seemed frozen. Decided to upgrade to squeeze. I edited the apt sources file and changed all the instances of lenny to squeeze, and then upgraded.Had the same display problem, but found a web site that suggested disabling acpi. So I did that, got the sound working, (needed cs46xx firmware), and all seems to be running fine.I get some weird udev messages at boot time, but I have a feeling that's due to how I upgraded. I can't copy and paste since the messages aren't in my system log. If anybody wants more information about it, I can supply it. pgrep shows two instances of udev running so it appears the messages are only warnings.When upgrading to squeeze, I used tds.net debian mirror links. Earlier today I switched to Debian's official US repo URLs and had to upgrade about 250 packages after reloading package data.
Now, when I click on System -> Administration -> Time and Date.After a couple seconds I get a dialog box that says "The configuration data could not be loaded" in bold black letters. Underneath that in smaller letters, "You are not allowed to access the system configuration" I receive that same error when accessing "services" and "users and groups."But I can access the synaptic package manager and update manager from the administration submenu.
I've been testing Squeeze to determine whether KDE4 is finally suitable for my primary machine. Everything seems to be working fine except for detection of IDE devices. My CD/DVD drive no longer automounts and the reason seems to be that no device is being created. My Lenny system detects the drive as /dev/hda, but no such device exists in Squeeze. During boot, Squeeze appears to detect the drive as /dev/sr0 (according to dmesg), but in fact that device does not exist either.I'm actually running the Lenny kernel, as I am unable to compile my Ralink wireless driver (rt2860sta) using the Squeeze kernel. Also, for inquiring minds, I use removable HDD drive bays on my systems to simplify testing.
I have been trying to build a Debian-live-version for some time using live-helper. It works fine if I choose lenny as distribution. With sid I always get into trouble.Sometimes live-helper does't find any aufs-modules but it stops looking for them if I keep the options as simple as above.What is the problem of live-helper's to build on sid or squeeze (which I have met similar troubles with)?
Alright, first Squeeze wouldn't create an initial RAM disk even with "--initrd" specified. Now I don't need one and it's creating one for me even though I don't want one! How do I stop this? I'm beginning to feel like I am using Windows in the sense that it's doing things on its own. Don't make me a RAM disk unless I say so!
I just noticed that I had a sid line on my sources.list, at the end of all squeeze lines, and I've been updating more or less regularly. Does the ordering imply some sort of "preference", so that the first lines are preferred over the subsequent ones, or is it all about the latest version?After removing that line, and taking a look at my installed packages with synaptic, all the "latest versions" of the packages seem to be the ones that are already installed, and I click on properties, and there are no older versions available, only "##.##-### (testing)". Emphasis on "testing", rather than "sid" or "unstable". Of course I didn't check all of them, but about a dozen, and none deviated from that pattern. However, I went to double check on the web pages about the packages, and it seems that many of the squeeze's packages are at the same version of sid. I couldn't yet find one that is not.perhaps the sole fact that the sid line was on sources.list is enough to know that something happened -- as I don't recall having ever set up those configuration files about preferred sources/pins or however it's called), and suggestions on how to proceed? My hunch would be to just downgrade things gradually as they eventually fail (as I did with geeqie, which is why I suspect that there is some mess), but leave everything alone. Not try to fix what is not quite broken. And if it fails too often, go full-blown sid.