I don't know how to make my Wifi Card Qualcomm Atheros QCA9377 to work on my Debian Jessie.
I found driver here: [URL] .....
Tintumon2 said it work for him on Ubuntu 14, but how can I make it to work on Debian?
@update:
When I try to install them on Debian using "./install.sh" I see black screen and then GNU/Linux reboots.
I'm trying out a Jessie install and have noticed VNC doesn't work as well as it used to. I often install a desktop environment on a headless machine, disable *dm, and use vnc4server to create a desktop session if I want to use a GUI. When I try to do the same on Jessie, I run into problems.
Using Gnome, all I get is the generic "Oops something went wrong" error. Looking at .xsession-errors, there are some errors that hint at the problem.
Code: Select allXsession: X session started for ryan at Mon Dec 29 06:07:30 CST 2014
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 109 (X_ChangeHosts)
Value in failed request: 0x5
Serial number of failed request: 6
Current serial number in output stream: 8
[Code] ....
Some possibly related bugs: [URL] ...
The same thing seems to happen with Cinnamon. Since I doubt a fix for the above issue will make it into Jessie, I tried XFCE. However, that doesn't work correctly either. When running XFCE via VNC something is misreporting the version of xrandr as 1.1 instead of 1.4. Since xfsettingsd appears to want version 1.2+, many things are broken.
This post on the Ubuntu forums suggests the issue might be fixed in xfsettingsd version 4.11: [URL] .....
Is there a better way of getting a remote desktop in Jessie that I'm overlooking?
Everything was working fine on Deb 7.7 with propriety driver. Then I did what I "presumed" to be an "update" through apper but it upgraded to Deb 8. The upgrade borked half way through with errors (cannot remember what they were, unfortunately I had to go out - wasn't expecting an upgrade or I'd have done it with more time).
Apper stated it had part installed stuff and trying to run update again (through apper) then had "no permissions" issues even though I entered password. After a few reboots and upgrading through recovery I "seem" to have resolved that, but might be related to this issue.
After resolving that issue I booted up and the grey GUI login screen was fine, after entering password the next screen was a colourful splash screen (with "Desktop" tab in top right corner), but it doesn't advance from that screen. No mouse, can't click or tab. Ctrl Alt Del does nothing.
The image looked like this, but with only "Desktop" in a black tab at the top right.
[URL] ....
I've never seen this screen before.
After followed this guide using recovery boot:
[URL] ....
Code: Select allapt-get purge "fglrx.*"
rm /etc/X11/xorg.conf
sudo apt-get install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64
sudo dpkg-reconfigure xserver-xorg
My system booted fine, albeit low resolution etc.
So I tried to install proprietary again using this Debian how to: [URL] ....
Although the procedure looks the same for Deb7 as it does Deb8 (barring the source).
The same problem happened where I was stuck at the loading/splash screen after GUI login.
So I removed the proprietary drivers again and am now back in, again albeit low res like am back in he 90's. Also, that splash screen doesn't show at all now.
The driver is supposed to be fine with my setup, so is there some issue left over from the borked upgrade perhaps? Everything seems fine otherwise.
I'm fairly new to linux. A few months ago I installed Debian Jessie and for the most part everything has gone pretty smoothly. The last piece of hardware I have to get working is my ScanJet 8200 flatbed scanner. From the SANE documentations, I know the hardware is supported, so I assume I must be doing something wrong with setup. It is correctly identified using lsusb:
Code: Select allroot@debian:/home/jessiesgirl# lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
[code]....
I get an error. Trying to use an application like SimpleScan give me an error telling me that it is unable to connect to the scanner.
Running Jessie, x64 Intel iCore 7 16 RAM with a properly partitioned drive to the specifications I prefer. Running the KDE Shell. For some reason my third monitor is not detected by Debian Jessie at all. When I run the command to list the monitors lspci | grep VGA I think. Only two monitors are listed, I know the other monitor works. During Grub bootup it even has some startup text running in it.
View 9 Replies View RelatedI would like to upgrade from Win8.1 to Debian 8. This post might require some Wind expertise as well. I have to deal with the dreaded UEFI interface.
I got the iso with the added firmware from here: [URL] ....
The i386 download and it appears to be 334 MB. I pretty got it because I don't want to mess with the wireless controller (been there done that.)
As far as the Wind side goes I disabled secure boot. Just whenever I get to the fancy blue screen, I select boot from EFI DVD. Then it just says it can't load it and asks if I want to continue loading the OS. This might be useful I used the default Desktop Burning Gadget to burn the disk image.
Debian configurating, so I try to use wifi adapter, but it doesn't work. I have installed Debian Jessie from netinst CD. To reach perfect speed no options were selected. After I installed xfce4 and xfce4-goodies.I follow some different instructions and no dice. Wicd show me no avalable wifi connections. used Ubuntu 14, Ubuntu 12, etc. and I didn't have any problems with wi-fi connections. Some outputs of comands...
Code: Select allsatyva@meliorD:~$ cat /etc/debian_version
8.3
Code: Select allsatyva@meliorD:~$ lspci | grep 4313
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
[code]....
I've tried installing both ibus-anthy and ibus-mozc in Jessie but I still cannot input Japanese.
By contrast, In Wheezy, when using anthy for example, I can see ibus preferences icon where I can configure ibus and anthy. This doesn't show up in Jessie.
I recently install a Debian 8.0 Jessie on a Laptop Dell latitude E6540 with gnome 3.14+3. But the problem is that it doesn't recongnize my multimedia buttons, I tried some methods but I didn't get results.
Code:
Code: Select all$showkey --scancodes
volume up -- 0xe0 0x30 0xe0 0xb0
volume down -- 0xe0 0x2e 0xe0 0xae
volume mute -- 0xe0 0x20 0xe0 0xa0
$showkey --keycodes
volume up -- 115
volume down -- 114
volume mute -- 113
[Code] ....
When I reassinged the keys on Settings>Keyboard>Shortcuts to F7, F8 and F9 it works, but when use the keys volume up, down and mute It doesn't show anything.
The same happens with Fn + Brightness keys, in this case it worked the first time but then stop to work I don't know why..
I'm using Debian Jessie. All the firmware packages are properly installed, and so are the radeon free driver packages.
However, Gallium falls back to llvmpipe, which from what I understand is a software rasterizer and not actually hardware rendering.
Everything works fine except some specific things like KDE's cube animation, which says it can't be enabled because it requires OpenGL.
How do I get Debian to run Gallium properly?
I attached some relevant info...
glxinfo | grep -i opengl
It has happened to my debian jessie system that the sound sometimes ceased to work, but after a quick review of alsamixer, pavucontrol it was easy to put everything back to normal. Not this time
The sound works as a charm with no headphones, but not with them, and I find them particularly useful for talking with people since the sound quality is way better...
I have alsa and pulseaudio installed on my system
uname -a
Linux device 3.14-2-amd64 #1 SMP Debian 3.14.13-2 (2014-07-24) x86_64 GNU/Linux
lspci -v| grep Audio
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
In pavucontrol everything looks normal, and the output seems to be working...
My wifi does not work in the actual debian testing jessie lxde amd64 with wicd version (fresh install). What I've done:
0. Fresh testing jessie install (offline and ignored the question for adding iwlwifi)
1. Adding following sources:
deb http://ftp.de.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
2. apt-get update
3. apt-get install firmware-iwlwifi
4. modprobe -r iwlwifi ; modprobe iwlwifi
So searching the web just brings up the wheezy way solution (backport new kernel and iwlwifi).
But in this case, actual jessie testing kernel is already installed by default and so the actual 43 firmware-iwlwifi
Some information:
Code: Select all# dpkg -l |grep -i iwlwifi
ii firmware-iwlwifi 0.43 all Binary firmware for Intel Wireless cards
Code: Select all# dmesg | grep wifi
[ 7.890216] iwlwifi 0000:02:00.0: irq 107 for MSI/MSI-X
[ 8.478878] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7260-9.ucode
[ 8.479867] iwlwifi 0000:02:00.0: loaded firmware version 23.214.9.0 op_mode iwlmvm
[ 8.553105] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[ 8.553193] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[Code] ....
I must add: lxde Debian uses Wicd, so network-manager is not installed !
Wicd seems to be the problem. After changing to network-manager, everthing is ok.
Next install with the official Jessie release, i will look, why wicd not work out of the box.
I am trying to get the QL1060N to print and cut under Jessie.
I used the Ql1060N on wheezy (cups 1.5.3) with the standard Brother driver and the ptouch/foomatic driver of the QL550. They both worked out of the box.
Configuration for Brother QL1060N Driver:
Description:ql1060n
Location:
Driver:Brother QL-1060N CUPS v1.1 (grayscale, 2-sided printing)
Connection:socket://XXX:9100
[Code] ....
On Jessie (cups 1.7.5):
I first tried the standard Brother driver from here: [URL] ....It didn't work at all. When I print, Cups tells me that the job has been completed, even though nothing has been done. Sometimes I also got the error "job canceled, filter failed", but I can't reproduce this error...
The foomatic/ptouch driver for the QL550 prints like it did before, but doesn't cut the lables automatically like it used to in wheezy. (I'm using the same printing file/picture as in wheezy and also the same configuration.)
I have a Toshiba laptop and Toshiba netbook (both Intel chipsets). Laptop - Squeeze install gave me the 2.6.32 kernel and sound only worked thru headphones but not the speakers. Later on, I compiled kernel 2.6.36.1 (and just imported .config from original kernel) and sound WORKED perfectly. I had a few other errors ("address space collision" / PM error) so recently I compiled kernel 2.6.38, which solved other hardware issues but sound is back to original problem (works thru headphones but not thru speakers). I even installed the "backports" kernel (2.6.38.4) and it didn't make a difference.
Netbook - Did exact same things as above but no matter what, the sound never worked on it... same issue (sound in headphones.. no sound in speakers) So, how do I "reverse-engineer" the laptop working sound install with kernel 3.6.36.1 and make it work with later kernel (nothing... and I've tried about 30+ thread suggestions makes the sound cards work properly.. other than kernel 2.6.36.1)
cdma usb modem recognized on as mass storage device.nstalled wvdialler and made appropriate lines to conf file and still does not work.
View 5 Replies View RelatedI've got a little netbook, and all works fine, except for one small thing. I'm able to connect to a wireless network with my Atheros AR5001 just fine. However, if I right click on the network icon, and disable network or wireless and enable it again, wireless won't work anymore. I can't see and connect to any network at all. Except when using airodump-ng from the famous aircrack-ng tool set. When using airodump I'm able to see any network and their specs just fine. I don't even have to be in monitor mode to do airodump-ng (the wireless must be off in the network manager though). Is there any way of getting my wireless back when I turn it on again?
View 9 Replies View RelatedI have used Ubuntu without trouble for quite some time now on my computer (maybe 2 years; recently upgraded to 10.04) and have just bought a new computer for the office. When I install 10.04 on the new computer it doesn't seem to recognise the lan card, an atheros AR8151 onboard card (on a GA-G41MT-S2 mobo).
p.s. phrases such as 'build-essentials', 'sudo' and '.tar.gz' files don't mean anything to me (except the last is a bit like a zip file I think).
In my laptop, after upgrade, wifi stop working.My laptop is Fujitsu-Siemens Amilo Pro V2065, wifi cart Philips 12127e (from IBM T41), linux kernel: 2.6.37-020637rc3.This card worked before upgrade, and work on windows Command lshw -c network return:Quote:
*-network:0 UNCLAIMED
description: Ethernet controller
product: AR5212 802.11abg NIC
[code]....
I have a Lenovo W510 Laptop with Ubuntu 10.04. The laptop has an on board Qualcomm 3g modem. I have managed to install the Qualcomm firmware and Network Manager detects the 3g device but when I try to connect it disconnects after a few seconds. My syslog has the error
Code: Got failure code 100: Unknown error
F13 on a EEEPC 1000HD.I have big problems with my wireless card. lspci says:
Code:
01.00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
I can't use Network Manager (it continue to ask me for the WPA password9. So I stopped it and I use command line, following this: [URL]
From the log I can see that it tried to associate to AP and after a lot of tries: it connects BUT the connection is really SLOW and UNSTABLE! (pinging hosts on the same network gives me about 50% packets loss) I am worried about this entry in the log:
Code:
ath5k phy0: unsupported jumbo
I am going to try to install madwifi, but before that I'd like to have your opinion and listen your experience! I see a lot on infos about ath5k, but I'd like to be pointed to the right direction!
i'm running Ubuntu 10.10 32-bit on an Acer Aspire 3050 laptop with an Atheros AR5BMB5 WiFi card.
The problem i'm having is that the hardware switch to turn the WiFi on and off isn't working right. When I hit the switch to turn it off, the light doesn't turn off, and Ubuntu just disconnects from the network and searches for more WiFi networks - it doesn't say that the WiFi has been deactivated, and I don't think it is. When I hit the switch again, it finds my network and connects to it.
The lspci -v | less command gives me the following information for the WiFi:
Code:
08:04.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
Subsystem: AMBIT Microsystem Corp. Device 0418
Flags: bus master, medium devsel, latency 168, IRQ 21
[Code]....
It lists a different model of card, but it's using what I assume is the correct driver, so I don't know if that has anything to do with it. I've checked the card itself and it is a AR5BMB5.
I would like to fix it so the switch actually turns the WiFi off instead of just making it search for more networks (I assume it's not actually turning off), and perhaps make the light turn off as it should as well.
i used to have shaw cable that i paid for and with that a "wired" connection which no matter what linux i chose to play with would recognize and automatically install the network drivers etc... so that i could access the web. now though i use a connection via wifi in the hotel that i now reside at and when i install or use live cd versions of linux i cant get it to use my wifi. due to the fact i have an atheros card. i researched this and found that apparently i need to have mad wifi installed and configured. however i haven't been able to get it to work. i can't seem to get an accurate step by step on installing it. same when i step by step try to install linux onto a usb stick and have it bootable. furthest i've gotten is the start up splash screen and then it freezes. anywho can someone steer me towards the "easiest dumbest person using it" install madwifi and or get a copy that works for an atheros card.
View 6 Replies View RelatedI have installed Ubuntu 9.10 (64 bit) as a dual-boot setup (along with Win 7) on my desktop. I can't emphasize how much faster Ubuntu loads when compared with Windows. There is only one problem though, I cannot figure out how to use my existing FakeRaid array (two 2TB hdds setup as RAID 1 - mirroring) to work with Ubuntu. I am NOT trying to install Ubuntu onto a raid array (I have Win 7 mounted on a separate boot drive , 4 hdds altogether, two for each OS and two for the RAID array). The raid array works fine in Windows and it's an Intel Raid Controller. How can I do the same for Ubuntu without losing any data? Is this possible?
View 3 Replies View RelatedI installed Debian awhile ago, but then replaced the mobo. Now my system doesn't detect the onboard LAN card, installing the windows driver fixed that problem on windows but I can't seem to find the appropriate driver for Linux.
The card is an Atheros 8151.
The problem is that my install of linux (64bit) does not recognize any adapter on the system. I went and downloaded a driver, after a make, make install, and reboot it still wasn't fixed.
I can find on this recommends downloading from some partner.atheros.com which seems defunct.
I am preparing to install Debian. I use an USB-adapter for wireless network access, the chipset of the network card in the adapter is "Atheros AR9271". Using this adapter is my only means of accessing the internet.
For some reason I had a hunch that my adapter might not be supported in Debian. I started searching around and found that quite a few people have been having some difficulties installing it to work in Debian. So, when I will have installed Debian there seems to be a significant risk I won't be able to go online.
Since I don't have any other way of connecting to the internet, thus no other network card and no parallel computer to use, I will get in trouble when I have to try to get my adapter to work with Debian. That is to say, it will be impossible to search for solutions on Google, ask for help online etc. I want to forestall such a situation. Hence a few questions:
1) What exactly will I have to do in order to be able to use the adapter with Debian?
2) Is there any way of doing it without going online after I have finished installing Debian? I'm thinking about if it would, for example, be possible to include any required files in the installation package I will use to install Debian?
I've installed Debian for the first time, and am excited to use it. However, it's asking me for a username and login. I haven't configured anything related to that yet, since I haven't started using Debian yet. Is there a special username and login I am supposed to know?
View 14 Replies View RelatedJust installed the new version of Ubuntu and having problems. My Dell Vostro works fine and the he Internet also works fine after giving the machine the router pass-phrase however the Windows 7 network showing but I cannot open it. the 2 daemons for Samba are running ok and I am just na bit stumped with this one.
View 1 Replies View RelatedI seem to have a problem that a lot of people have: My work uses exchange server 5.5/2007. Does evolution still not support this? I tried to set it up and it tells me that it won't work with exchange 5.5.
View 4 Replies View RelatedI juat got 11.04 and as usual the additions will not install on Ubuntu.Does anyone take charge of making sure that ubuntu will work in VBox?
View 1 Replies View RelatedI am attempting to install Debian 5.0 amd64 to my Toshiba laptop, which has an Atheros AR8131 Gigabit network card.Unfortunately the installer is not finding the card. I have downloaded the Linux drivers for my card to a USB drive. When I tell the installer to load the drivers from removable media it is telling me that it is not able to read the files. I am guessing that I either need to place the files into a particular named directory or I have the wrong file format (currently a .tar)
View 11 Replies View Related