Hi, first post here! I'm a part-time Linux user, with experience on Mandrake and Fedora. After installing ubuntu 8.10, I find that my computer is very quiet, even when I don't want it to be! The only sound I can get is the beep when the arrow keys reach a limit, such as scrolling to the end of a list, or the end of a command line. The master volume is high, I have permission to Use Audio Devices, nothing is muted, am I missing something basic??? I've been to https://wiki.ubuntu.com/DebuggingSoundProblems <https://wiki.ubuntu.com/DebuggingSoundProblems> and lots of links from there. Learned a lot, accomplished little. :) I can turn off the beep (alert) in Sound Preferences, but I can't turn on other sounds, (Rhythmbox, youtube, etc.) Some info I picked up is shown below. I wasn't clear from checking http://www.alsa-project.org/main/index.php/Matrix:Main <http://www.alsa-project.org/main/index.php/Matrix:Main> whether my sound card is supported by ALSA. The Intel soundcard list includes ESB2, but nothing else remotely like 631xESB/632xESB. If that's the case, am I screwed? aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci -v 00:1b.0 Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller (rev 09) Subsystem: Dell Device 01c0 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at dfffc000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xdfffc000 irq 16 -Rich This e-mail message is generated from?Coghlin Companies Inc. or one of its subsidiaries including, but not limited to, Columbia Electrical Contractors, Inc. d/b/a Columbia Tech; DCI Automation, Inc.d/b/a DCI Engineering Services; Cogmedix, Inc.; and Coghlin Precision, Inc. This message may contain information that is?CONFIDENTIAL, and may also possibly contain information that is being held as a Trade Secret.? The information is intended to be disclosed solely to the addressee(s).? If you are the intended recipient, any information herein is to be held as CONFIDENTIAL pursuant to any Non-Disclosure Agreement applicable between the parties, or as a Trade Secret as applicable.? If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this e-mail information is prohibited.? If you have received this e-mail in error, please notify the sender by return e-mail and delete it from your computer system.
Hmmm.... do you have pulseaudio setup on your system? John
| Hmmm.... do you have pulseaudio setup on your system? | | John Yes, version 0.9.10. I'm not sure what it does. $ pulseaudio --version W: ltdl-bind-now.c: Failed to find original dlopen loader. pulseaudio 0.9.10 $ pulseaudio --check W: ltdl-bind-now.c: Failed to find original dlopen loader. $ | I had a similiar problem with my Gentoo system with KDE. | | I spent a large ammount of time checking out ALSA, kernel configuration etc... | | and I only got sound only after turning on my front mike input (in the output | | | section). | | It might be a good idea to try checking out KMix (if you use KDE 3.5) or whatever | sound mixer applies. | | kstratton@fastmail.us I'm running GNOME. Gnome ALSA Mixer says I have SigmaTel STAC9200, which matches the "aplay -l" output: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 It allows me to set volumes on Master, PCM, LFE, Capture and Capture (again). I don't understand them, but they're all set on max. -Rich This e-mail message is generated from?Coghlin Companies Inc. or one of its subsidiaries including, but not limited to, Columbia Electrical Contractors, Inc. d/b/a Columbia Tech; DCI Automation, Inc.d/b/a DCI Engineering Services; Cogmedix, Inc.; and Coghlin Precision, Inc. This message may contain information that is?CONFIDENTIAL, and may also possibly contain information that is being held as a Trade Secret.? The information is intended to be disclosed solely to the addressee(s).? If you are the intended recipient, any information herein is to be held as CONFIDENTIAL pursuant to any Non-Disclosure Agreement applicable between the parties, or as a Trade Secret as applicable.? If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this e-mail information is prohibited.? If you have received this e-mail in error, please notify the sender by return e-mail and delete it from your computer system.
Which model of Dell is it? I can tell you that they're a pain with sound. Search for your model and "sound" at the ubuntu forum, and see what others have done. Try different settings in gnome-sound-preferences - you might need to set all devices to ALSA, or you might need to set them all to Pulse Audio, as the person in this thread did - http://ubuntuforums.org/showthread.php?t=997506 Search for Dell in that thread - post#70 just changed to a newer kernel than the one on the install CD and got sound to work. If all else fails, drop back to 8.04, and one of our WLUG members who has a Dell laptop with sound working will lend you her config files. Greg Strazdas, Rich wrote:
| Hmmm.... do you have pulseaudio setup on your system? | | John
Yes, version 0.9.10. I'm not sure what it does. $ pulseaudio --version W: ltdl-bind-now.c: Failed to find original dlopen loader. pulseaudio 0.9.10 $ pulseaudio --check W: ltdl-bind-now.c: Failed to find original dlopen loader. $
| I had a similiar problem with my Gentoo system with KDE. | | I spent a large ammount of time checking out ALSA, kernel configuration etc... | | and I only got sound only after turning on my front mike input (in the output | | | section). | | It might be a good idea to try checking out KMix (if you use KDE 3.5) or whatever | sound mixer applies. | | kstratton@fastmail.us
I'm running GNOME. Gnome ALSA Mixer says I have SigmaTel STAC9200, which matches the "aplay -l" output: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 It allows me to set volumes on Master, PCM, LFE, Capture and Capture (again). I don't understand them, but they're all set on max.
-Rich This e-mail message is generated from?Coghlin Companies Inc. or one of its subsidiaries including, but not limited to, Columbia Electrical Contractors, Inc. d/b/a Columbia Tech; DCI Automation, Inc.d/b/a DCI Engineering Services; Cogmedix, Inc.; and Coghlin Precision, Inc. This message may contain information that is?CONFIDENTIAL, and may also possibly contain information that is being held as a Trade Secret.? The information is intended to be disclosed solely to the addressee(s).? If you are the intended recipient, any information herein is to be held as CONFIDENTIAL pursuant to any Non-Disclosure Agreement applicable between the parties, or as a Trade Secret as applicable.? If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this e-mail information is prohibited.? If you have received this e-mail in error, please notify the sender by return e-mail and delete it from your computer system.
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
I had a similiar problem with my Gentoo system with KDE. I spent a large ammount of time checking out ALSA, kernel configuration etc... and I only got sound only after turning on my front mike input (in the output section). It might be a good idea to try checking out KMix (if you use KDE 3.5) or whatever sound mixer applies. -- kstratton@fastmail.us
I had the same problem after upgrading to 8.10, below are my notes from fixing it. These steps worked for me. However, I have the nagging worry that maybe I didn't have to go through all of it (the steps 1 to 5) and that maybe I just had to futz around with the volume levels and other settings to get everything to work. So maybe try the stuff after step 5 first. What seems to have fixed sound after it didn't work after upgrade to 8.10:
From https://wiki.ubuntu.com/PulseAudio did: Go to System -> Administration -> and click on Users and Groups.
Click on Manage Groups, and scroll all the way to the bottom of the list where you will find: * pulse-access * pulse-rt Make sure to highlight each, one at a time, and click Properties. Just put a check next to each user that you want to be able to have access to sound. For example, there's "ted" and "root" and "kamilion" listed, and you only want "kamilion" to have access to sound, that's the one to check, leave the other two blank. Note: The "pulse" group is for pulseaudio internal use, and normal users should not be added to this group. Then did: 2. Configure libao applications to use PulseAudio: Code: $ echo "default_driver=pulse" >~/.libao 3. Perform the following steps to remove obsolete configuration files, ensure "libflashsupport" is not installed & you have the all the necessary packages up-to-date: Code: $ rm -r ~/.pulse ~/.asoundrc* $ sudo apt-get update && sudo apt-get dist-upgrade $ sudo apt-get remove libflashsupport $ sudo apt-get install libasound2-plugins padevchooser libao-pulse libsdl1.2debian-pulseaudio NOTE: Choose Yes to allow unsigned packages to be installed. 4. Go to System/Preferences/Sound. Set all "Sound playback" options to "Autodetect", and set "Sound capture" to "ALSA". 5. Reboot for changes to take effect! Then had to use: alsamixer -D hw:0 and turn up pcm volume to get sound. Recording still didn't work from the built-in mic. Also, the volume icon vanished somewhere along the line. Brought it back by going to the panel, right clicking and hitting add and adding it from there. Once it was there, right clicked on it and went to "open volume control". Go to preferences for each item in the dropdown and check everything. What seems to work is, under HDA ATI SB (Alsa Mixer), the volumes in the recording tab can all be all the way down and the device not set to be a recording device, under the switches tab though, it seems to be pretty important that analog loopback is unchecked. In the options tab, digital input source should be set to digital mic. Under HDA ATI HDMI (Alsa Mixer), IEC958 should be unchecked Under Sigmatel STAC9205 (OSS Mixer), it seems that the in-gain level is not important, as long as it isn't muted. Capture: Monitor Source of ALSA PCM on front:0 with toggle input source from master toggled on, unmuted and turned up Capture: ALSA PCM on front:0 (STAC92xx Analog) .. volume turned up, unmuted and master toggle on. Doesn't seem to matter what the volume level is, but it does matter if it's muted.
I'm running ubuntu 8.04 on Dell 1525n (laptop) and had sound problems out of the box when it arrived April 2008 with ubuntu 7.10 installed. I had it fixed within 24 hours. Then various kernel updates have had sound working or not, seemingly randomly. Now I'm running 8.04, with working sound in kernel 2.6.24-22 generic, which as I recall, did not need extra effort to get it working... they have it right in that one. I think we tested the later kernel and sound was broken again. Getting it going: I would first do Kieran's step 4 before starting to remove obsolete config files & that stuff. If you get any indication your sound is trying to work, go see about the switches in Alsamixer then. We have a new Gregbuilt* desktop in here, which runs ubuntu 8.04 very very nicely. But even in this, we had to set some sound switches oddly --labels on some of these speakers (front, back, etc) did not seem to correspond correctly. So it took some tweaking. If you are running on a Dell laptop (I saw something in your lspci output that mentioned Dell), and if all else fails, I would roll back to ubuntu 8.04 --the kernel I have working here --until the forums quit reporting broken sound.in intrepid. I like ubuntu hardy very well. I can share my amixer output (how switches are set in ALSA) if needed, or other config files or whatever. Your mileage may differ, but there may be some use in checking out what works here. Good luck, Liz J * a WLUG member. 2009/2/20 Kieran O'Callaghan <kieran@tiac.net>:
I had the same problem after upgrading to 8.10, below are my notes from fixing it. These steps worked for me. However, I have the nagging worry that maybe I didn't have to go through all of it (the steps 1 to 5) and that maybe I just had to futz around with the volume levels and other settings to get everything to work. So maybe try the stuff after step 5 first.
What seems to have fixed sound after it didn't work after upgrade to 8.10:
From https://wiki.ubuntu.com/PulseAudio did: Go to System -> Administration -> and click on Users and Groups.
Click on Manage Groups, and scroll all the way to the bottom of the list where you will find:
* pulse-access * pulse-rt
Make sure to highlight each, one at a time, and click Properties. Just put a check next to each user that you want to be able to have access to sound. For example, there's "ted" and "root" and "kamilion" listed, and you only want "kamilion" to have access to sound, that's the one to check, leave the other two blank.
Note: The "pulse" group is for pulseaudio internal use, and normal users should not be added to this group.
Then did: 2. Configure libao applications to use PulseAudio: Code:
$ echo "default_driver=pulse" >~/.libao
3. Perform the following steps to remove obsolete configuration files, ensure "libflashsupport" is not installed & you have the all the necessary packages up-to-date: Code:
$ rm -r ~/.pulse ~/.asoundrc* $ sudo apt-get update && sudo apt-get dist-upgrade $ sudo apt-get remove libflashsupport $ sudo apt-get install libasound2-plugins padevchooser libao-pulse libsdl1.2debian-pulseaudio
NOTE: Choose Yes to allow unsigned packages to be installed.
4. Go to System/Preferences/Sound. Set all "Sound playback" options to "Autodetect", and set "Sound capture" to "ALSA".
5. Reboot for changes to take effect!
Then had to use: alsamixer -D hw:0 and turn up pcm volume to get sound.
Recording still didn't work from the built-in mic. Also, the volume icon vanished somewhere along the line. Brought it back by going to the panel, right clicking and hitting add and adding it from there. Once it was there, right clicked on it and went to "open volume control". Go to preferences for each item in the dropdown and check everything. What seems to work is, under HDA ATI SB (Alsa Mixer), the volumes in the recording tab can all be all the way down and the device not set to be a recording device, under the switches tab though, it seems to be pretty important that analog loopback is unchecked. In the options tab, digital input source should be set to digital mic. Under HDA ATI HDMI (Alsa Mixer), IEC958 should be unchecked Under Sigmatel STAC9205 (OSS Mixer), it seems that the in-gain level is not important, as long as it isn't muted. Capture: Monitor Source of ALSA PCM on front:0 with toggle input source from master toggled on, unmuted and turned up Capture: ALSA PCM on front:0 (STAC92xx Analog) .. volume turned up, unmuted and master toggle on. Doesn't seem to matter what the volume level is, but it does matter if it's muted.
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
Hi Walt, Anything in /var/log? TC -----Original Message----- From: wlug-bounces@mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On Behalf Of Walt Sent: Friday, February 20, 2009 7:35 AM To: Worcester Linux Users Group Subject: [Wlug] Fedora freezes I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Hi Walt, Anything in /var/log? TC Yes, what should I look for? (see below) Check memory and power supply. If you're using a realtime kernel, that's a possible cause of lockup. And if you want to reboot more gracefully, use magic sysrq keys. http://en.wikipedia.org/wiki/Magic_sysrq Note that the instructions say to hold down alt-sysrq, but on my system, that brings up the window to take a screenshot. I have to hold down ctrl-alt-sysrq. Then press keys, one at a time, with a couple seconds between each: r - e - i - s - u - b (or other keys, if appropriate. See the chart in the wikipedia article.) Greg This just started recently; I've had the notebook for almost a year. It's had Fedora 9 and 10 on it. I'm not sure if I have a realtime kernel. Next time it locks, I'll try the ctrl-alt-sysrq. I've been experiencing the same thing. I've assumed it was due to vmware and/or the new scheduler. At one point I got frustrated, confirmed that the computer could still be connected to and just left it alone. After 10 mins or so it started responding again. Seems to happen most when doing something intensive in vmware (like compiling a big program) and opening tabs in firefox. Dennis Payne dulsi@identicalsoftware.com I seem to have VMware installed (if I type vm TAB TAB I get a bunch of choices, but if I rpm -q vmware, it's not installed), but I can't seem to get it to work, I use virtualbox. Thanks for all your help! Walt Smolts says my set-up is http://www.smolts.org/client/show/pub_7932ef68-1e8a-4e4a-a49c-c9414ff63bd2 Contents of /var/log anaconda.log anaconda.syslog anaconda.xlog aprsd audit BackupPC bittorrent boot.log boot.log-20090125 boot.log-20090201 boot.log-20090208 boot.log-20090215 bro btmp btmp-20090201 clamd.milter cluster collectl ConsoleKit cron cron-20090125 cron-20090201 cron-20090208 cron-20090215 cups dirmngr dirsrv dmesg dmesg.old faillog fax freshclam.log gdm glpi httpd iptraf jetty kismet lastlog ldirectord.log ldirectord.log-20090125 ldirectord.log-20090201 ldirectord.log-20090208 ldirectord.log-20090215 libvirt mail maillog maillog-20090125 maillog-20090201 maillog-20090208 maillog-20090215 mcelog messages messages-20090125 messages-20090201 messages-20090208 messages-20090215 munin mysqld.log mythtv nagios ntpstats ocsinventory-agent PackageKit pm-powersave.log pm-suspend.log ppp prelink privoxy rpmpkgs rpmpkgs-20090125 rpmpkgs-20090201 rpmpkgs-20090208 rpmpkgs-20090215 samba secure secure-20090125 secure-20090201 secure-20090208 secure-20090215 setroubleshoot snort spooler spooler-20090125 spooler-20090201 spooler-20090208 spooler-20090215 squid tallylog tinyerp tomcat5 tor vbox vbox-install.log vdradmin vmware wpa_supplicant.log wtmp wtmp-20081101 xen Xorg.0.log Xorg.0.log.old Xorg.1.log Xorg.1.log.old Xorg.2.log yum.log yum.log-20080302 yum.log-20080423 yum.log-20080630 yum.log-20090101 zabbix zoneminder Tal Cohen wrote:
Hi Walt, Anything in /var/log?
TC
-----Original Message----- From: wlug-bounces@mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On Behalf Of Walt Sent: Friday, February 20, 2009 7:35 AM To: Worcester Linux Users Group Subject: [Wlug] Fedora freezes
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Walt, Next time it locks up, after you reboot, get a look at /var/log/messages. Page down to check the last entries before the reboot, which should tell you what was going on when it froze. Do: less /var/log/messages which will output the actual text of the messages that are being saved in the /var/log directory.messages. You might need to be root to do this --we do have to be root in Debian and in Ubuntu. Since you have:
messages messages-20090125 messages-20090201 messages-20090208 messages-20090215
it means there are several message logs that have been made recently. You could also output: less /var/log/messages-20090215 But let's see the last bunch of entries in the latest one. You could also select text from these messages, and google that for forum postings. Liz J 2009/2/21 Walt <waltsaw@gmail.com>:
Hi Walt, Anything in /var/log?
TC
Wow, thanks! I guess I have some logs to look through. Thanks, Walt E Johnson wrote:
Walt,
Next time it locks up, after you reboot, get a look at /var/log/messages. Page down to check the last entries before the reboot, which should tell you what was going on when it froze.
Do:
less /var/log/messages
which will output the actual text of the messages that are being saved in the /var/log directory.messages. You might need to be root to do this --we do have to be root in Debian and in Ubuntu.
Since you have:
messages messages-20090125 messages-20090201 messages-20090208 messages-20090215
it means there are several message logs that have been made recently. You could also output:
less /var/log/messages-20090215
But let's see the last bunch of entries in the latest one. You could also select text from these messages, and google that for forum postings.
Liz J
2009/2/21 Walt <waltsaw@gmail.com>:
Hi Walt, Anything in /var/log?
TC
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Walt, Check memory and power supply. If you're using a realtime kernel, that's a possible cause of lockup. And if you want to reboot more gracefully, use magic sysrq keys. http://en.wikipedia.org/wiki/Magic_sysrq Note that the instructions say to hold down alt-sysrq, but on my system, that brings up the window to take a screenshot. I have to hold down ctrl-alt-sysrq. Then press keys, one at a time, with a couple seconds between each: r - e - i - s - u - b (or other keys, if appropriate. See the chart in the wikipedia article.) Greg Walt wrote:
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
I've been experiencing the same thing. I've assumed it was due to vmware and/or the new scheduler. At one point I got frustrated, confirmed that the computer could still be connected to and just left it alone. After 10 mins or so it started responding again. Seems to happen most when doing something intensive in vmware (like compiling a big program) and opening tabs in firefox. Dennis Payne dulsi@identicalsoftware.com Quoting Walt <waltsaw@gmail.com>:
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
On Fri, Feb 20, 2009 at 07:35:14AM -0500, Walt wrote:
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
Is the caps lock light blinking when this happens?
I had something like this too, in Debian (etch). In my case it was a string of USB disconnect/reconnects, related to either the mouse or the keyboard. /var/log/messages turned up hundereds of messages about this, eventually it would run out of new device numbers to assign to the "new" USB device (keyboard or mouse) and everything would lock up. Yes, when Firefox was running, but I think I reproduced it in Ubuntu 8.04 when no browser at all was running. Upgraded to Debian Lenny some weeks ago, and still had the USB disconnect/reconnect problem although I think I managed to avoid the total-lockup problem --possibly only because we rebooted several times due to power failures & etc. Now running PS2 keyboard here, resulting in no more USB disconnect/reconnect messages in /var/log/messages and no more lockups since then. Running mouse plugged into the laptop running Ubuntu (8.04 hardy) now results in the same USB disconnect/reconnect messages, although it has not locked up yet. But I haven't used it much lately, either. I did notice the other day that it was running a little hot --maybe because it never had a chance to suspend, because of this disconnect/reconnect thing that's constantly happening. What did /var/log/messages report? Liz J 2009/2/21 Chuck Anderson <cra@wpi.edu>:
On Fri, Feb 20, 2009 at 07:35:14AM -0500, Walt wrote:
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
Is the caps lock light blinking when this happens? _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
I can turn the light on (ThinkLight) and the NumLock. Other than that, no keyboard interaction happens. Thanks! Walt Chuck Anderson wrote:
On Fri, Feb 20, 2009 at 07:35:14AM -0500, Walt wrote:
I have been experiencing freezes with Fedora 10. For no apparent reason, the machine just stops. No mouse, no keyboard (no ctrl alt F1 or ctrl alt del). I can only reboot with the on-off switch. Any ideas as to what I can check? Thanks! Walt
Is the caps lock light blinking when this happens? _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
On Mon, Feb 23, 2009 at 07:44:05AM -0500, Walt wrote:
I can turn the light on (ThinkLight) and the NumLock. Other than that, no keyboard interaction happens. Thanks!
So the little house-shaped light with the "A" inside it that represents the state of the Caps Lock function doesn't blink all by itself? Because if it does, that indicates that the kernel paniced. If it doesn't, then the kernel did not panic.
Nope, the ONLY two things that work are the light and NmLk. These are operated (on my Lenovo X61s) using the Fn key. None of the other Fn key functions operate at time of lock-up. So I'm assuming a panic. Thanks! Walt Chuck Anderson wrote:
On Mon, Feb 23, 2009 at 07:44:05AM -0500, Walt wrote:
I can turn the light on (ThinkLight) and the NumLock. Other than that, no keyboard interaction happens. Thanks!
So the little house-shaped light with the "A" inside it that represents the state of the Caps Lock function doesn't blink all by itself? Because if it does, that indicates that the kernel paniced. If it doesn't, then the kernel did not panic. _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Has anyone had any experience with wireless video camera(s) along with motion sensor detection and recording in Linux? Looking for what works well, what to buy, install, etc. Thanks Al
While I can't speak for the hardware side of things, check out ZoneMinder. http://www.zoneminder.com/ On Mon, Feb 23, 2009 at 8:40 PM, Ritacco, Alan <Alan.Ritacco@umassmed.edu>wrote:
Has anyone had any experience with wireless video camera(s) along with motion sensor detection and recording in Linux? Looking for what works well, what to buy, install, etc.
Thanks
Al
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Conner Finlay
From: "Ritacco, Alan" <Alan.Ritacco@umassmed.edu>
< short question >
------_=_NextPart_001_01C99621.2786886E Content-Type: application/ms-tnef; name=winmail.dat Content-Transfer-Encoding: base64
eJ8+Ih4BAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAGQAAAFdpcmVsZXNzIFZpZGVvIGFu
< ~60 lines drivelish >
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
------_=_NextPart_001_01C99621.2786886E--
What is an ms-tnef, and can you make it stop? -- Keith
Ritacco, Alan wrote: Has anyone had any experience with wireless video camera(s) along with motion sensor detection and recording in Linux? Looking for what works well, what to buy, install, etc.
Thanks
Al
I have the Panasonic BL-C131 which I bought last year. It works well under Linux except for the ActiveX stuff like sound, which doesn't work at all, and live panning, which staggers. The motion sensor and recording is done in the device itself so your OS doesn't matter there. Also the only wireless security I can get my camera connected to my router with is WEP. When I set up WPA or WPA2 it won't connect. Not sure why. I haven't been able to google anyone with a similar problem. My other devices all connect fine. So I am happy with the camera and would recommend it, but there could be better cameras out there now for the money which I'm not aware of. -- Gary
Thank you all for your assistance. Kieran's libao magic got me outputting sound to "ALSA PCM on hw:1 (pcsp)". This was better than nothing, but it sounds like a tin-can-and-string phone. Other suggestions I found on the net were dead ends. Pulseaudio showed rhythmbox sound going to "ALSA PCM on front:0 (STAC92xx Analog)" but I couldn't get my mixer (right term?) to connect that to the speakers. ANYWAY, I went another route, installing ubuntu 8.10 on a partition on my laptop. It worked out of the box. I finally heard those bongos! -Rich -----Original Message----- From: wlug-bounces@mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On Behalf Of E Johnson Sent: Friday, February 20, 2009 6:22 AM To: Worcester Linux Users Group Subject: Re: [Wlug] no sound from ubuntu I'm running ubuntu 8.04 on Dell 1525n (laptop) and had sound problems out of the box when it arrived April 2008 with ubuntu 7.10 installed. I had it fixed within 24 hours. Then various kernel updates have had sound working or not, seemingly randomly. Now I'm running 8.04, with working sound in kernel 2.6.24-22 generic, which as I recall, did not need extra effort to get it working... they have it right in that one. I think we tested the later kernel and sound was broken again. Getting it going: I would first do Kieran's step 4 before starting to remove obsolete config files & that stuff. If you get any indication your sound is trying to work, go see about the switches in Alsamixer then. We have a new Gregbuilt* desktop in here, which runs ubuntu 8.04 very very nicely. But even in this, we had to set some sound switches oddly --labels on some of these speakers (front, back, etc) did not seem to correspond correctly. So it took some tweaking. If you are running on a Dell laptop (I saw something in your lspci output that mentioned Dell), and if all else fails, I would roll back to ubuntu 8.04 --the kernel I have working here --until the forums quit reporting broken sound.in intrepid. I like ubuntu hardy very well. I can share my amixer output (how switches are set in ALSA) if needed, or other config files or whatever. Your mileage may differ, but there may be some use in checking out what works here. Good luck, Liz J * a WLUG member. 2009/2/20 Kieran O'Callaghan <kieran@tiac.net>:
I had the same problem after upgrading to 8.10, below are my notes from fixing it. These steps worked for me. However, I have the nagging
worry that maybe I didn't have to go through all of it (the steps 1 to
5) and that maybe I just had to futz around with the volume levels and
other settings to get everything to work. So maybe try the stuff after
step 5 first.
What seems to have fixed sound after it didn't work after upgrade to 8.10:
From https://wiki.ubuntu.com/PulseAudio did: Go to System -> Administration -> and click on Users and Groups.
Click on Manage Groups, and scroll all the way to the bottom of the list where you will find:
* pulse-access * pulse-rt
Make sure to highlight each, one at a time, and click Properties. Just
put a check next to each user that you want to be able to have access to sound. For example, there's "ted" and "root" and "kamilion" listed,
and you only want "kamilion" to have access to sound, that's the one to check, leave the other two blank.
Note: The "pulse" group is for pulseaudio internal use, and normal users should not be added to this group.
Then did: 2. Configure libao applications to use PulseAudio: Code:
$ echo "default_driver=pulse" >~/.libao
3. Perform the following steps to remove obsolete configuration files,
ensure "libflashsupport" is not installed & you have the all the necessary packages up-to-date: Code:
$ rm -r ~/.pulse ~/.asoundrc* $ sudo apt-get update && sudo apt-get dist-upgrade $ sudo apt-get remove libflashsupport $ sudo apt-get install libasound2-plugins padevchooser libao-pulse libsdl1.2debian-pulseaudio
NOTE: Choose Yes to allow unsigned packages to be installed.
4. Go to System/Preferences/Sound. Set all "Sound playback" options to
"Autodetect", and set "Sound capture" to "ALSA".
5. Reboot for changes to take effect!
Then had to use: alsamixer -D hw:0 and turn up pcm volume to get sound.
Recording still didn't work from the built-in mic. Also, the volume icon vanished somewhere along the line. Brought it back by going to the panel, right clicking and hitting add and adding it from there. Once it was there, right clicked on it and went to "open volume control". Go to preferences for each item in the dropdown and check everything. What seems to work is, under HDA ATI SB (Alsa Mixer), the volumes in the recording tab can all be all the way down and the device not set to be a recording device, under the switches tab though, it seems to be pretty important that analog loopback is unchecked. In the options tab, digital input source should be set to digital mic. Under HDA ATI HDMI (Alsa Mixer), IEC958 should be unchecked Under Sigmatel STAC9205 (OSS Mixer), it seems that the in-gain level is not important, as long as it isn't muted. Capture: Monitor Source of ALSA PCM on front:0 with toggle input source from master toggled on, unmuted and turned up Capture: ALSA PCM on front:0 (STAC92xx Analog) .. volume turned up, unmuted and master toggle on. Doesn't seem to matter what the volume level is, but it does matter if it's muted.
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug This e-mail message is generated from?Coghlin Companies Inc. or one of its subsidiaries including, but not limited to, Columbia Electrical Contractors, Inc. d/b/a Columbia Tech; DCI Automation, Inc.d/b/a DCI Engineering Services; Cogmedix, Inc.; and Coghlin Precision, Inc. This message may contain information that is?CONFIDENTIAL, and may also possibly contain information that is being held as a Trade Secret.? The information is intended to be disclosed solely to the addressee(s).? If you are the intended recipient, any information herein is to be held as CONFIDENTIAL pursuant to any Non-Disclosure Agreement applicable between the parties, or as a Trade Secret as applicable.? If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this e-mail information is prohibited.? If you have received this e-mail in error, please notify the sender by return e-mail and delete it from your computer system.
Rich> Thank you all for your assistance. I tried... Rich> Kieran's libao magic got me outputting sound to "ALSA PCM on hw:1 Rich> (pcsp)". This was better than nothing, but it sounds like a Rich> tin-can-and-string phone. Other suggestions I found on the net were dead Rich> ends. Pulseaudio showed rhythmbox sound going to "ALSA PCM on front:0 Rich> (STAC92xx Analog)" but I couldn't get my mixer (right term?) to connect Rich> that to the speakers. Rich> ANYWAY, I went another route, installing ubuntu 8.10 on a Rich> partition on my laptop. It worked out of the box. I finally Rich> heard those bongos! I ran into a problem like this in Ubuntu 9.04 beta for a bit, it took an upgrade to fix. If you have 8.04 with the non-working sound, just upgrade to 8.10 on there and you should be all set, then you can blow away the new and redundant install. John
participants (14)
-
Chuck Anderson -
Conner Finlay -
dulsi＠identicalsoftware.com -
E Johnson -
Gary Hanley -
Gregory Avedissian -
John Stoffel -
Keith Wright -
Kieran O'Callaghan -
kstratton＠fastmail.us -
Ritacco, Alan -
Strazdas, Rich -
Tal Cohen -
Walt