SUSE 10.0 Yast sound bombs on compaq
I have an 'old' Compaq 1260 laptop which has an ESS18xx sound chip. It works fine up to an including suse 9.3. I've installed 10.0 and all works fine except for the sound. Using YAST I tell it to search for the old chips and it goes into the chip found/ configure dialog. I select the ESS 18xx and click edit and poof goes the dialog and I'm back to the opening YAST dialog. I've updated, installed all that I can find but still the audio setup bombs. Can anyone point me toward a solution??? How to setup Sound without YAST? Thanks Richard
hi,
On 27/10/05, Richard Atcheson
I have an 'old' Compaq 1260 laptop which has an ESS18xx sound chip. It works fine up to an including suse 9.3.
I've installed 10.0 and all works fine except for the sound. Using YAST I tell it to search for the old chips and it goes into the chip found/ configure dialog. I select the ESS 18xx and click edit and poof goes the dialog and I'm back to the opening YAST dialog.
I've updated, installed all that I can find but still the audio setup bombs. Can anyone point me toward a solution??? How to setup Sound without YAST?
Have you also tried alsconf? This is a console-based tool (it needs root privileges) which can work well configuring older sound cards (such as ISA... is yours one?) After YaST crashes you could check /var/log/YaST2/y2log (assuming that's where YaST still stores its logs files - I haven't tried 10.0 yet). It might give some clues to what action is being performed when the crash occurs. Check dmesg too (just execute dmesg in a console) for possibly useful hardware-related messages. -- /Paul "It's not about the ending, it's about the journey." - Lex Luthor
On Thu October 27 2005 4:18 pm, Paul wrote:
Have you also tried alsconf? This is a console-based tool (it needs root privileges) which can work well configuring older sound cards (such as ISA... is yours one?) # alsconf bash: alsconf: command not found
-- Paul Cartwright Registered Linux user # 367800
* Paul Cartwright
# alsconf bash: alsconf: command not found
would probably work better if you spelled it correctly, alsaconf -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
hi,
On 27/10/05, Patrick Shanahan
* Paul Cartwright
[10-27-05 16:20]: # alsconf bash: alsconf: command not found
would probably work better if you spelled it correctly, alsaconf
Oops, I should read mails carefully before I send them. -- /Paul "It's not about the ending, it's about the journey." - Lex Luthor
On Thu October 27 2005 5:23 pm, Patrick Shanahan wrote:
bash: alsconf: command not found
would probably work better if you spelled it correctly, alsaconf well, after removing all the snd* using rmmod, then rebooting, then adding my sound card back in, at least I can use alsaconfig. now, mplayer crashes and I can't play mp3 files. so I ran YaST and found it hadn't installed mplayer ( I thought it was installed) so I ran YaST and installed mplayer-1.0pre7-pm.3.i586
ok, I can now play MPG videos! BUT, I can't play MP3 files. what's next? -- Paul Cartwright Registered Linux user # 367800
Paul Cartwright wrote: 9SNIP)
so I ran YaST and found it hadn't installed mplayer ( I thought it was installed) so I ran YaST and installed mplayer-1.0pre7-pm.3.i586
ok, I can now play MPG videos! BUT, I can't play MP3 files. what's next?
How would we know? Mplayer outputs like a ton of data when it tries to play something and all that valuable information you are keeping from us. Regards, -- Jos van Kan registered Linux user #152704
On Friday 28 October 2005 06:23, Paul Cartwright wrote:
On Thu October 27 2005 5:23 pm, Patrick Shanahan wrote:
bash: alsconf: command not found
would probably work better if you spelled it correctly, alsaconf
well, after removing all the snd* using rmmod, then rebooting, then adding my sound card back in, at least I can use alsaconfig. now, mplayer crashes and I can't play mp3 files. so I ran YaST and found it hadn't installed mplayer ( I thought it was installed) so I ran YaST and installed mplayer-1.0pre7-pm.3.i586
ok, I can now play MPG videos! BUT, I can't play MP3 files. what's next?
mp3 is proprietary, it is not legal for suse to add it (without having paid for it.) use OGG, it is better anyway. for mp3, install the missing stuff. i think there are other posts with a list already. HTH, Matt
-- Paul Cartwright Registered Linux user # 367800
On Fri October 28 2005 11:51 am, Matt T. wrote:
mp3 is proprietary, it is not legal for suse to add it (without having paid for it.)
right, I knew that.
use OGG, it is better anyway.
I use it when the songs have that extension, I'm not going to convert 20 gigs of MP3's to OGG any time soon:)
for mp3, install the missing stuff. i think there are other posts with a list already
thanks, but that post was not JUST for MP3 info, it was a "super list" including a bunch of apps to burn/work with DVDs, taken from this post: There IS a performance gain with this release, a nice bonus! Now, for anyone using SUSE 10.0, don't have the multimedia files needed to play DVDs, etc., and don't know what files to get from http://packman.links2linux.org/, here is a list of the files you will need, including what is needed to rip a DVD. You could call this a "super" list for multimedia. ;) 10.0-libdvdcss2-1.2.9-1.i386.rpm divx4linux-20030428-0.pm.0.i586.rpm dvdbackup-0.1.1-0.pm.0.i586.rpm kaffeine-0.7.1-3.pm.0.i686.rpm kaffeine-mozilla-0.2-0.pm.1.i686.rpm kdvdbackup-0.5-1.pm.1.i586.rpm libdvdcss2-1.2.8-0.pm.2.i686.rpm libdvdread-0.9.4-149.pm.0.i686.rpm libmpeg3-1.6-0.pm.0.i686.rpm libxine1-1.1.0-12.pm.1.i686.rpm mjpegtools-1.8.0-0.pm.1.i686.rpm speex-1.1.10-0.pm.0.i686.rpm w32codec-all-20050412-0.pm.0.i586.rpm xine-ui-0.99.4-5.pm.1.i686.rpm -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.bellsouth.net/p/PWP-pcartwright/key.asc
On Thursday 27 October 2005 03:18 pm, Paul wrote:
hi,
On 27/10/05, Richard Atcheson
wrote: I have an 'old' Compaq 1260 laptop which has an ESS18xx sound
Have you also tried alsconf? This is a console-based tool (it needs root privileges) which can work well configuring older sound cards (such as ISA... is yours one?)
After YaST crashes you could check /var/log/YaST2/y2log (assuming that's where YaST still stores its logs files - I haven't tried 10.0 yet). It might give some clues to what action is being performed when the crash occurs. Check dmesg too (just execute dmesg in a console) for possibly useful hardware-related messages.
Thanks Paul, Paul, Patrick, Sunny and Matt! Alsaconf was the answer. The old brick now plays sounds. It took me a little while to make the fix as I'm sharing the powersupply with my LCD monitor and have to switch between the two. The laptop has the typical non-functioning battery since it was 6 months old. Thanks for the help. Richard
On Thursday 27 October 2005 15:10, Richard Atcheson wrote:
I have an 'old' Compaq 1260 laptop which has an ESS18xx sound chip. It works fine up to an including suse 9.3.
I've installed 10.0 and all works fine except for the sound. Using YAST I tell it to search for the old chips and it goes into the chip found/ configure dialog. I select the ESS 18xx and click edit and poof goes the dialog and I'm back to the opening YAST dialog.
I've updated, installed all that I can find but still the audio setup bombs. Can anyone point me toward a solution??? How to setup Sound without YAST?
Thanks Richard
I have a similar problem with an old machine with ISA sound card. The detection acts exactly as you see it, and YaST crashes. I have filed a bug report here: https://bugzilla.novell.com/show_bug.cgi?id=117688 Looks like that ISA is not a target for support, and most probably they are not going to fix it. I guess, if more users confirm the bug, thus showing that this support is still needed, they may put some efforts :) Anyway, I'll try the other suggestions from the list and use alsaconf, and I'll report back. Cheers Sunny
On Friday 28 October 2005 00:50, Sunny wrote:
On Friday 28 October 2005 00:31, Sunny wrote:
Anyway, I'll try the other suggestions from the list and use alsaconf, and I'll report back.
YESSSSSSSSSSSSSSS. It works. I wish I had knew this 3 weeks earlier :)
Thanks guys
Too bad. 2 new problems: 1. After reboot, no sound. I needed to run again alsaconf. Then the sound works. Strange, as alsaconf have made the changes in /etc/modprobe.d/sound. I guess I have to disable the hotplug (or coldplud) for the sound card. I remember reading somewhere something, but I can not find this any more. Any pointers? 2. mplayer started as a user does not play sound. If I start it as root, the sound is there. All devices in /dev/snd/, /dev/dsp and /dev/rtc has rw-rw---- permissions with owner root:audio. And my user is member of audio. The strange thing is, that if I run mplaer as root, it says that it uses OSS as audio output?!?!? And if it not root, it fails when tries OSS output, saying permission problems on /dev/dsp. Any help solving this are highly appreciated. Cheers Sunny
On Friday 28 October 2005 14:35, Sunny wrote:
On Friday 28 October 2005 00:50, Sunny wrote:
On Friday 28 October 2005 00:31, Sunny wrote:
Anyway, I'll try the other suggestions from the list and use alsaconf, and I'll report back.
YESSSSSSSSSSSSSSS. It works. I wish I had knew this 3 weeks earlier :)
Thanks guys
Too bad. 2 new problems: 1. After reboot, no sound. I needed to run again alsaconf. Then the sound works. Strange, as alsaconf have made the changes in /etc/modprobe.d/sound. I guess I have to disable the hotplug (or coldplud) for the sound card. I remember reading somewhere something, but I can not find this any more. Any pointers?
probably the modules do not get loaded automatically. yast would have arranged that, normally at least... do a lsmod when all works, and a lsmod after a fresh reboot. some snd* related modules will be missing, reload them manually (as root, "modprobe xyz"). If you know them all, then try putting the modprobe's in /etc/init.d/boot.local or similar. and do not forget to check alsamiver, sound might get played, but muted, you need to unmute manually. Especially pcm related stuff.. Once the volumes are ok, do a "alsactl store" (as root). HTH, Matt
2. mplayer started as a user does not play sound. If I start it as root, the sound is there. All devices in /dev/snd/, /dev/dsp and /dev/rtc has rw-rw---- permissions with owner root:audio. And my user is member of audio. The strange thing is, that if I run mplaer as root, it says that it uses OSS as audio output?!?!? And if it not root, it fails when tries OSS output, saying permission problems on /dev/dsp.
Any help solving this are highly appreciated.
Cheers Sunny
On 10/28/05, Matt T.
On Friday 28 October 2005 00:50, Sunny wrote: 1. After reboot, no sound. I needed to run again alsaconf. Then the sound works. Strange, as alsaconf have made the changes in /etc/modprobe.d/sound. I guess I have to disable the hotplug (or coldplud) for the sound card. I remember reading somewhere something, but I can not find this any more. Any pointers?
probably the modules do not get loaded automatically. yast would have arranged that, normally at least...
do a lsmod when all works, and a lsmod after a fresh reboot. some snd* related modules will be missing, reload them manually (as root, "modprobe xyz"). If you know them all, then try putting the modprobe's in /etc/init.d/boot.local or similar.
and do not forget to check alsamiver, sound might get played, but muted, you need to unmute manually. Especially pcm related stuff.. Once the volumes are ok, do a "alsactl store" (as root).
HTH, Matt
Yes, the modules are not loaded. I just wanted to avoid boot.local stuff, and to do it SuSE way. Reading the docs, hwup should check what's in /etc/modprobe.d/sound and load it. All these modules are in /etc/modprobe.d/sound. And there is a file in /etc/sysconfig/hardware/hwcfg- for the card as well. I just can not figure it out how to change these files so the hwup script picks them up. Any help? And ... for the second problem - I found out, that if I do not use alsaconf for a second time, but just modprobe the module, mplayer works OK. So, for now I just would like to do the right stuff to load modules upon startup. Cheers -- Svetoslav Milenov (Sunny)
Hi all! I have just installed the SUSE 10.0 Linux on my PC. I found it very easy to install, even for an amateur in Linux, like myself. The only problem so far is related to my USB modem. Yast Control Center recognizes the modem and says that its 'name' is /dev/ttyACM0 However, in kppd, no /dev/ttyACM0 is given as an option. Only /dev/usb/ttyACM0 (which seems correct because my modem is a USB one). If i go like: mkdir /dev/usb mknod /dev/usb/ttyACM0 -c 166 0 and I choose /dev/ttyACM0 in kppp, there is no answer hwen I wuery my modem, and , in Yast Control center, the modem's name remains /dev/ttyACM0. Any ideas on how to solve the problem? Kostas __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
hi,
I have just installed the SUSE 10.0 Linux on my PC. I found it very easy to install, even for an amateur in Linux, like myself. The only problem so far is related to my USB modem. Yast Control Center recognizes the modem and says that its 'name' is /dev/ttyACM0
This is the device name and what a dialer will use to "talk" to it. Check that the modem can be talked to by using each of the following commands on two different consoles: cat /dev/ttyACM0 echo "AT" > /dev/ttyACM0 If I remembe correctly... so, on the console with the cat command you should see the modem's reply, if any...
However, in kppd, no /dev/ttyACM0 is given as an option. Only /dev/usb/ttyACM0 (which seems correct because my modem is a USB one).
If i go like: mkdir /dev/usb mknod /dev/usb/ttyACM0 -c 166 0
and I choose /dev/ttyACM0 in kppp, there is no answer hwen I wuery my modem, and , in Yast Control center, the modem's name remains /dev/ttyACM0.
Have you tried configuring it in YaST and then using kinternet? YaST will allow the use of /dev/ttyACM0 directly. But anyway, why don't you just make a symlink between /dev/ttyACM0 and /dev/usb/ttyACM0? -- /Paul "It's not about the ending, it's about the journey." - Lex Luthor
participants (8)
-
Jos van Kan
-
Kostas Tsirigos
-
Matt T.
-
Patrick Shanahan
-
Paul
-
Paul Cartwright
-
Richard Atcheson
-
Sunny