Sound Server Error

DiZASTiX · 05-12-2003, 09:03 PM

removing append="opl3=0x388" had no effect. That had to do with the sound anyways.

Quote:

Just about half on this thread alone.

lol.

Ya, but this pretty much sucks lol, im sure if i can get it to boot my new kernel the sound would work...maybe if i installed grub???

quietguy47 · 05-12-2003, 09:04 PM

It's worth a try.

DiZASTiX · 05-12-2003, 09:09 PM

ok, here where you come in (again

) got some questions.

1. Do i need to uninstall LILO (if so how)
2. Do i need to recompile
3. Which do i download from here

That it...for now lol

*edit*

yay me, 100 posts

quietguy47 · 05-13-2003, 05:21 AM

ftp://alpha.gnu.org/gnu/grub/grub-0.93.tar.gz
http://new.linuxnow.com/docs/content/LILO/LILO-2.html
I don't think you need to recompile if you want to switch to grub, but, maybe you should give that a try before uninstalling lilo.

DiZASTiX · 05-13-2003, 04:19 PM

Eh, uninstalling lilo is weird and i dont even know if grub will work, i dont think its worth it. just gotta find a way to get rid of that kernel panic crap

Ive searched and it seems to be a very common error but i cant find any solution

DiZASTiX · 05-13-2003, 04:38 PM

I was just thinking, would the:

EXT2-fs: ide0(3,1): couldnt mount because of unsoported optional features (4)

maybe be caused by what the ESS1868 page told me to do with the "make menuconfig" part?

Aussie · 05-13-2003, 05:03 PM

When do you get the kernel panic?
I must have missed that post.

DiZASTiX · 05-13-2003, 05:32 PM

Quote:

Originally posted by DiZASTiX
I think we may be getting somewhere, i did what you said, change root=/dev/hda1 to root=/dev/hda and rebooted...still gave me LI. But then i changed the part that said boot=/dev/hda1 to boot=/dev/hda and Lilo started!!! I had 2 options slack (new) or linux (old) obviously i booted slack but while it was starting i got this error (crushed my hopes lol ):

ds: no socket drivers loaded! (<---- Dont know if that has something to do with it)
kernel panic:VFS: Unable to mount root fs on 03:00.

I have no clue what that means, i was hoping you could help me out?

*edit*

Just found this, maybe it can help?

*edit #2*

Ok, i tried making it so root=/dev/hda1 but boot=/dev/hda. I tried booting slack again and i got a new error:

EXT2-fs: ide0(3,1): couldnt mount because of unsoported optional features (4)
kernel panic:VFS: Unable to mount root fs on 03:01. (note beore it was 03:00)

So now, should i put root= back to /dev/hda or /dev/hda1???

Read the whole thing, at the end (edit 2) is what i get now. And this is my /etc/lilo.conf:

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="op13=0x388"
boot = /dev/hda
message = /boot/boot_message.txt
LBA32
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = slack
read-only
image=/boot/vmlinuz.old
root=/dev/hda1
label=linux
read-only
# Linux bootable partition config ends

Aussie · 05-13-2003, 05:41 PM

Did you get the kernel panic with both kernels or just your new one?

DiZASTiX · 05-13-2003, 05:52 PM

I was never able to boot from lilo with the old one, i always used to use a boot disk.

Aussie · 05-13-2003, 06:01 PM

Then I'd have to say the kernel panic is caused by a misconfigured kernel.

DiZASTiX · 05-13-2003, 06:16 PM

hmm....could you suggest a way to figure out specifically what???

Aussie · 05-13-2003, 06:45 PM

Maybe, it's probably just one setting that you missed, not a hard thing to do considering the number of options available.
Email me your .config and I'll have a quick look to see if I can spot anything obvious.
Now you know why the kernel guide has the vmlinuz.old instructions, so you always have a known working kernel to boot if something goes wrong with your old one.

DiZASTiX · 05-13-2003, 06:51 PM

hehe, ya, well i messed up that .old option

Umm...i would email you my .config...if i knew where it was...

edit: found it, it is on its way

DiZASTiX · 05-14-2003, 02:39 PM

Also that ESS1868 page had what it was supposed to say wen i get it to work, so if i can get to boot from the new kernel, i can find out if the sound actually worked.