Quote:
Originally Posted by Chex
So, I'm having two problems at once and figured it would be best to just make one thread ...
I just installed SUSE yesterday (!) and I've really been liking it so far. The only problem is that I can't get it to play any sounds at all. I've checked volume and all that ...
All I've really tried so far is going to "Control Center" and from there to "Sound & Multimedia" and then "Sound System" -- when I go to Sound System, I get an error that says "Unable to start the sound server to retrieve possible I/O methods. Only automatic detection will be avaialable."
I have no idea what I'm doing, so any advice as to how I can get my sound working would be appreciated!
And my other problem is with the GRUB boot loader. When I turn on the computer, GRUB will load just fine, but when I try to select SUSE (the only OS on there, haha) it gives me GRUB error 22, "No such partition."
The GRUB manual says "This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk." but I have no idea what that actually means??
How do I make this error go away? (So far I've been having to boot from the DVD ... it works just fine that way, but I'd really rather not, you know?)
Anyway, I'm currently pretty ignorant about computers but having a lot of fun mucking about and learning. Any advice/help for a hopeful newbie is much appreciated.
Cheers!
|
For sound to work in X.org and its recently lost brother xfree86, you'll need a sound daemon of some kind. I dont use suse, so I dont know what its default tries to be, but usualy there is a simple tk style applet for changing them around.. The actual problem will be either failure of the sound drivers to work properly with your windows manager (WM) or with your kernel modules (i.e. the devices compatibilty with the code is questionable somewhere down the line)
ALSA, OSS, and ESD are the main drivers for common use, see if you cant dig up some chipset info for your sound card and see what other forums have to say.
Grub on the other hand, will be quicker to fix. There are a lot of tutorials available on it but if you just need to know where its done this may help:
: ls -al /boot/grub
device.map fat_stage1_5 menu.lst minix_stage1_5 stage1 xfs_stage1_5
e2fs_stage1_5 jfs_stage1_5 menu.lst~ reiserfs_stage1_5 stage2
on some systems there will be different hiding spots for grub's conf files, look in places like /etc/grub.conf /etc/grub /boot , etc..
(open text editor of your choice, i.e. vi)
--
vi /etc/grub/boot/menu.1st
read the commented (#) stuff to get an explination of what grub's config file is all about, otherwise you'll be wanting to consider this part:
title Ubuntu, kernel 2.6.12-9-k7
root (hd1,1)
kernel /boot/vmlinuz-2.6.12-9-k7 root=/dev/hdb2 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-k7
savedefault
boot
title Ubuntu, kernel 2.6.12-9-k7 (recovery mode)
root (hd1,1)
kernel /boot/vmlinuz-2.6.12-9-k7 root=/dev/hdb2 ro single
initrd /boot/initrd.img-2.6.12-9-k7
boot
title Ubuntu, memtest86+
root (hd1,1)
kernel /boot/memtest86+.bin
boot
Each 'title' is a menu entry during boot up. For non selectable lines (such as when grouping with a label) the minimum entry is:
title All OS's are as listed:
root
the order of entries is f.i.f.o.
my windows entry:
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1
makeactive is neccesary because newer win systems require it. Its is not strictly neccesary for *nix.
Good luck!