Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some time ago I decided to try Linux on a Compaq Armada 1750 featuring 384Mb RAM.
Excellent little laptop though a bit heavy. I tried different Linux distributions with general success, except for the sound.
Were tested:
- PCLinuxOS LXDE
- Puppy 5.x.x
- Slacko 5.5 PAE
- Debian 6 Squeeze
- Debian 7 Wheezy
Some other systems either, but if all these versions worked relatively well, NONE gave me the sound I so badly want.
Afterwards I reluctantly tried Windows 2000 and XP. Both these Windows systems activated the sound with no further problem, and believe me, this Armada 1750 model has a very good sound equipment, which is why I want to use it.
So, why isn't any of these Linux systems able to activate the sound, and most important: how can this be fixed? At the moment the laptop is running Debian 7 Wheezy, installed with the Net Install cd and completely up to date.
Thanks on forehand,
Paul
this Armada 1750 model has a very good sound equipment, which is why I want to use it.
Umm.....now I'm really not sure if this is an Armada 1750. All that has is 'Compaq Premier Sound for enhanced stereo audio, including integrated 16-bit Sound Blaster Pro-compatible stereo audio'. Which is not what I would have called 'very good' even when it was new (1999).
Umm.....now I'm really not sure if this is an Armada 1750. All that has is 'Compaq Premier Sound for enhanced stereo audio, including integrated 16-bit Sound Blaster Pro-compatible stereo audio'. Which is not what I would have called 'very good' even when it was new (1999).
Can you post your lspci and lshw output?
Well man, except in the improbable case of a constructor labeling his machines with another brand than his own, yes, no doubt: "COMPAQ Armada 1750" written in big letters,
384Mb Ram (I added myself the second chip), Mobile Pentium II, about 330MHz processor, 6333/T/6400/D/0/3. I qualifie the sound as excellent just by comparison to any other laptop, old or new, because of the good loudspeakers. No direct need for an external HiFi equipment when travelling, but this is anyway not the point: I'd like to have sound. Curiously the system "beeps" do work, and sound tests result in a mere plain "click".
What do you mean with "lspci" and "lshw"? Loudspeaker caracteristics I guess. In any case, the system(s) (I tried many) do not even notice the presence of a sound card... My guess is the driver is missing. Windows and/or Compaq protected copyright driver maybe? I noticed some people on this forum having had the same problem with the same laptop without finding out how to fix it.
Thanks for the links. I checked the PDF document. The drawing fits clearly the machine I have, but some details differ: mine doesn't feature a modem, supports more RAM (maximum 384Mb: 128Mb chip + 256Mb chip), supports a hard drive of till at least 80Gb (I use one), but the rest of the description seems to fit.
Sure its a Compaq Armada 1750? From the spec sheet I can find, its limited to 192MB-
After having double checked what I did I really added a 256Mb chip in the only one available slot, but the motherboard carries a RAM chip of only 64Mb. So, total RAM is actually 320Mb (confirmed after having checked and working very well), not 384Mb, but still more than the announced limit of 192Mb. This to be honest, although not really important because Debian Wheezy runs smoothly, and the problem is only the missing sound.
Kind regards, Paul
I have an old laptop, not quite that old. But it fails to load the snd-intel8x0 driver for it's soundcard at boot. Just add it to /etc/modules or do it manually each boot. Creative labs was not a big supporter of linux in those early days. I don't know if that's ever changed. Like windows, I stopped using their products long ago.
Meanwhile I'm studying the content of that link and installed some of the adviced Alsa stuff. I need some time to digest all this ;o)
Thanks and kind regards, Paul
This is what I get:
bash: lshw : commande introuvable
root@armada:/home/paul# lspci | grep audio
root@armada:/home/paul# speaker-test
speaker-test 1.0.25
Le périphérique de lecture est default
Les paramètres du flux sont 48000Hz, S16_LE, 1 canaux
Utilisation de 16 octaves de 'pink noise'
La fréquence est 48000Hz (demandée 48000Hz)
L'intervalle de la taille du tampon est de 192 à 2097152
L'intervalle de la taille de la période est de 64 à 699051
Taille max. de tampon 2097152 utilisée
Périodes = 4
was set period_size = 524288
was set buffer_size = 2097152
0 - Avant Gauche
Temps par période = 11,685334
0 - Avant Gauche
Temps par période = 11,805833
0 - Avant Gauche
Temps par période = 11,834096
0 - Avant Gauche
Temps par période = 11,795275
0 - Avant Gauche
Temps par période = 11,830598
0 - Avant Gauche
Temps par période = 11,802422
0 - Avant Gauche
Temps par période = 11,795604
0 - Avant Gauche
Temps par période = 11,830922
0 - Avant Gauche
Temps par période = 11,794017
0 - Avant Gauche
Temps par période = 11,825980
0 - Avant Gauche
Temps par période = 11,789389
0 - Avant Gauche
Temps par période = 11,384569
0 - Avant Gauche
Temps par période = 11,407085
0 - Avant Gauche
Temps par période = 11,402440
0 - Avant Gauche
Temps par période = 11,771282
0 - Avant Gauche
Temps par période = 11,416181
0 - Avant Gauche
Temps par période = 11,759693
0 - Avant Gauche
Temps par période = 11,861917
0 - Avant Gauche
No idea what this ultimately means, but the speakers DO hiss...
So, up for "alsamixer" command. I'll tell later if this helped.
I have an old laptop, not quite that old. But it fails to load the snd-intel8x0 driver for it's soundcard at boot. Just add it to /etc/modules or do it manually each boot.
Thanks for the suggestion, but "modprobe snd-sb16" doesn't seem to do anything. I also tried to add "snd-intel8x0" to the /etc/modules, and still no change, even after reboot. The speakers only hiss instead of giving any usable sound. Maybe I missed something, but it was worth a go.
Thanks, Paul
If the speakers hissed, then you have a sound driver and an audible mixer level. Or broken speakers that hiss with or without a computer.
The snd-intel8x0 example was specific to my hardware, not yours. Sorry for the confusion. You would probably use snd-sb16, but might not have to if your sound is working.
$ speaker-test -c 2
(this does a pink noise for 2 channels, that will alternate between left and right channel)
(mostly useful to figure out if you have your earbuds in backwards, or if your speakers have cables that can be easily reversed.)
(use ^C aka Cntrl+C key combonation to terminate that application)
$ alsamixer
(F1 key for help while in this mixer)
(ESC key to exit help and/or the mixer)
(It's not the only mixer available in linux, just be aware of that)
Once you have a working driver and it sounds like you do, you have other configuration choices to use or just be aware about. As some applications may not default to the configuration that you are using. Which can be mildly frustrating if you are unaware of them or why your configuration isn't playing by your desires. Pulseaudio is one of the more common configurations by default these days, and you'll want to use pavucontrol to adjust it's settings.
$ pavucontrol
It might not matter much on that hardware, but on newer hardware you have multiple soundcards in a lot of cases. The one for the motherboard, the one for the video card, one probably comes for your webcam, and on and on and on. That is why I suggested:
$ cat /proc/asound/cards
If there's a soundcard or soundcards, and a working driver, they will be listed there in almost all cases. You should note that in most cases with multiple soundcards, that the first entry listed under 0 is the assumed default output. Unless otherwise configured.
The "user" will have to be in the "audio" group to use the soundcard. And in the case of a pulseaudio configuration, also in the "pulse" and maybe "pulse-access" groups.
If the speakers hissed, then you have a sound driver and an audible mixer level. Or broken speakers that hiss with or without a computer.
$ speaker-test -c 2
(this does a pink noise for 2 channels, that will alternate between left and right channel)
(mostly useful to figure out if you have your earbuds in backwards, or if your speakers have cables that can be easily reversed.)
(use ^C aka Cntrl+C key combonation to terminate that application)
This test works well: the loudspeakers only hiss alternatingly left and right.
Quote:
$ alsamixer
(F1 key for help while in this mixer)
(ESC key to exit help and/or the mixer)
(It's not the only mixer available in linux, just be aware of that)
Alsamixer shows up without problems, and in spite of some adjustments problem not solved.
Quote:
$ pavucontrol
Nothing happens.
Quote:
$ cat /proc/asound/cards
I get this:
root@armada:/home/paul# cat /proc/asound/cards
0 [ES1869 ]: ES1869 - ESS AudioDrive ES1869
ESS AudioDrive ES1869 at 0x220, irq 5, dma1 1, dma2 5
Useful maybe to remember that Windows 2000 and XP have no problems with the sound, which excludes hardware failure.
Many thanks in any case, your help is much appreciated,
Paul
This means that you have a loaded driver and it's identified your hardware as supported by that driver. So it's a configuration issue. Or a setting in the application(s) you are trying to use that have made assumptions not applicable to your configuration.
Linux differs a lot from windows in that it is setup to be based on permissions. And unlike windows, the permissions are not set to anybody can do anything at all times, like the default windows configuration is in a lot of cases. You have to tell it, userX has permission to use the soundcard.
So back to basics. # in most examples represent root access. And $ represents can and should be run as a user. Most things should be done as a user. Except in admin situations.
$ groups
(as my user)
userX : userX cdrom audio video games pulse pulse-access
# groups userX
(alternatively gives the same result as a different user)
So the question I don't recall seeing an answer to is "is the user in the audio group"? If they are not and you are trying to access the soundcard as that user, then you don't have permission to use the soundcard. As root you can change the groups with "usermod" or by editing the /etc/group file directly. Admin wise you "should" use usermod. This permission configuration is normally the primary fail, when there is a driver and it is known to work (as root, but not as a user). You can run speaker-test as root and as the user and if you don't get the same result, there's your problem. If you change the group permission, you will need to relogin or reboot to make them be in effect.
So you have a driver and it works. May I ask what application you are expecting to hear sound from, but are not hearing it from?
Audacity, Avidemux, default video player, etc. Any application that should play sound instead of emitting a hiss.
Quote:
So back to basics. # in most examples represent root access. And $ represents can and should be run as a user. Most things should be done as a user. Except in admin situations.
$ groups
(as my user)
paul@armada:~$ groups
paul cdrom floppy audio dip video plugdev netdev scanner bluetooth
Quote:
# groups userX
(alternatively gives the same result as a different user)
root@armada:/home/paul# groups paul
paul : paul cdrom floppy audio dip video plugdev netdev scanner bluetooth
Quote:
So the question I don't recall seeing an answer to is "is the user in the audio group"?
I guess the answer is "yes".
Quote:
You can run speaker-test as root and as the user and if you don't get the same result, there's your problem. If you change the group permission, you will need to relogin or reboot to make them be in effect.
As root I get the left-right hiss.
As user just the same result:
paul@armada:~$ speaker-test -c 2
speaker-test 1.0.25
Le périphérique de lecture est default
Les paramètres du flux sont 48000Hz, S16_LE, 2 canaux
Utilisation de 16 octaves de 'pink noise'
La fréquence est 48000Hz (demandée 48000Hz)
L'intervalle de la taille du tampon est de 96 à 1048576
L'intervalle de la taille de la période est de 32 à 349526
Taille max. de tampon 1048576 utilisée
Périodes = 4
was set period_size = 262144
was set buffer_size = 1048576
0 - Avant Gauche
1 - Avant Droit
Temps par période = 12,372476
0 - Avant Gauche
1 - Avant Droit
Basically same result, and always that annoying useless hiss...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.