Sound Server Error

quietguy47 · 05-07-2003, 07:41 PM

I like your attitude, I wish I had more of it

This link may help with configuring isapnp.
http://tldp.org/HOWTO/Sound-HOWTO/x320.html

DiZASTiX · 05-07-2003, 09:18 PM

lol, well whats the fun in using a computer if you never come across a problem!

Well, thanks a bunch quiteguy and aussie for the help, i guess now i know what to do, just got to do it now! Thanks again, when i get the sound to work i will let you know

(oh ya, how come my threads are always pages long lol, my last thread lasted 4 pages!

)

Aussie · 05-07-2003, 09:34 PM

Slackware 9.0 now includes hotplug, and it detected my SB Live! 5.1 at the first boot, if you want to get true 5.1 sound you need to do a bit of tweaking, but for a two speaker setup you should be fine.

DiZASTiX · 05-11-2003, 10:11 AM

Ok, well after a while i got isapnp installed, now what do i do with it lol ???

quietguy47 · 05-11-2003, 10:45 AM

Awesome, you've made progess.
You may need to recompile your kernel now. Just remember to compile sound as a module.

DiZASTiX · 05-11-2003, 10:55 AM

Ok, im not sure how to compile the kernel...would i have to look at the kernel howto or something??? (because i have looked at this and i couldnt understand!!!) Also, must i download a new kernel and how would i enable the sound module

So many questions. Thanks for any more help

(BTW, must i configure isapnp, cuz all i did was install (./configure, make , make install thats it))

quietguy47 · 05-11-2003, 11:09 AM

I thought you might not like the idea so I found this.

http://www.netspace.net.au/~bmiller/...s1868-2.4.html
A guide to compiling.
http://www.linuxquestions.org/questi...?s=&forumid=14

DiZASTiX · 05-11-2003, 11:20 AM

thanks a lot quietguy47, u have helped me a lot through this (you to Aussie!!!) i will keep you updated on my progress...thanks again!!!

DiZASTiX · 05-11-2003, 12:46 PM

Quick question, the kernel newbie guide on here says to:

make menuconfig
make dep
make clean
make bzImage
make
make install
make modules
make modules_install

and the ESS1868 one says:

make dep
make clean
make bzImage

So im confused, should i run those extra commands:

make
make install
make modules
make modules_install

or not?

DiZASTiX · 05-11-2003, 01:07 PM

i tried it without the extra commands and it didnt work

Ok, well im not giving up!!!

I got some more questions:

1) Do i have to run those extra commands (see previous post)

2) On the kernel newbie guide it says add .old for the image and label in the /etc/lilo.conf file, after i do this, what do i save it as /etc/lilo.conf and overwrite it or /etc/lilo.conf.old or something?

3) On the ESS1868 Page it says :

Code:

You will also have to modify yout /etc/lilo.conf file so that a new 
kernel parameter is passed in. The following line will have to be 
added up near the top before the first kernel images are listed as 
the Yamaha FM synthesizer MIDI driver isn't PnP aware:


append="opl3=0x388"

Huh? Where do i add that append="opl3=0x388" and do i do it after i compile or before?

Thanks!

quietguy47 · 05-11-2003, 02:06 PM

In /etc/lilo.conf, place this just below # Start Lilo global section
append="opl3=0x388".
Place this below the original and chnge the label on the original to whatever you want.
image = /boot/vmlinuz.old
root = /dev/hda2
label = Linux
read-only
Do not run #/sbin/lilo
to compile:
#cd /usr/src/linux
#make mrproper
#make config(I like this one because it's text based and easier I think)
be sure to follow the instructions from the ESS 1868 page. Also, anytime you need an explination of something while your compiling, just press H and enter.
#make dep
#make clean
#make bzImage
#make install
#make modules
#make modules install
After all this, reboot and you should have a choice of two kernels at the boot prompt. Boot your new kernel(whatever you named it)

Good Luck!

DiZASTiX · 05-11-2003, 02:10 PM

I understand everything you just said but when i add that .old part to /etc/lilo.conf do i save it as /etc/lilo.conf or /etc/lilo.conf.backup or something. Bascially im asking, do i create another lilo.conf or just edit the on there is?

quietguy47 · 05-11-2003, 02:14 PM

Just edit the one you have. You don't need or want two /etc/lilo.conf files

DiZASTiX · 05-11-2003, 03:38 PM

DAMN!!!

I did everything...EVERYTHING and it all went smooth, then when i started up my computer at the lilo screen it says LI insted of LILO, im searching the net to see what this meens, and i dont even see how i could fix it, i have a boot disk, but it is of my old kernel.

i didnt make a new boot disk after i did all the stuff. Damn this sucks!!!

DiZASTiX · 05-11-2003, 03:41 PM

I found this

Quote:

From The Linux Gazette
In the documentation for LILO there is a description of this problem. The LILO boot loader prints each of the characters: "L ... I ... L ... O" (LILO) at a different point in the processs of reading/parsing the partition table, loading the secondary boot loader code, locating and loading its maps (which it uses to locate and load kernels and optionally a initial ram disk --- initrd--- images).
When the system stops at LI then that tells you that the process failed before it could reach the part of that sequence where it would have printed the second "L".
Usually this means that you have a mismatch in the way that LILO and the BIOS are trying to access specific parts of a drive. One may be using CHS (cylinder, head, sector) co-ordinates while the other might be expecting LBA (linear block address) offsets. So, try adding the "linear" directive to the global section of your /etc/lilo.conf (and re-running the /sbin/lilo command to build and install a new boot loader from that conf file, of course).
Alternatively, try changing your PCs CMOS Setup options. Look for an option like "LBA" or "UDMA" mode and disable it. Note that this may not work with newer large capacity drives.
Search the back issues of LG on the term "LILO" for many other discussions of this sort of issue and explanations about what LBA and CHS mean, and some commentary on the historical reasons why IDE has evolved through all these EIDE, LBA, UDMA iterations.
Also note that it's still a good idea to make a small (16 - 32 Mb) "boot" partition at or near the beginning of any hard drive on which you install Linux. That should be entirely below the 1024 cylinder line. Newer versions of LILO can work around that infamous limit in most cases --- but it's still a good idea. Most people mount this partiton on /boot. It is the best place to put your kernels, initrd images, and their System.map files. (If you have MS-DOS or some other Microsoft OS installed in a large partition at the beginning of a drive, such that you can't put a small partition below cylinder 1024, consider using LOADLIN.EXE instead of LILO).
It may also be a good time to look at GRUB (the GNU grand unified bootloader). I haven't played with this yet; but I've heard that some people are very happy with it.
You can find out more about GRUB at its home page on the Free Software Foundation's (FSF) web pages:
http://www.gnu.org/software/grub/grub.en.html

If i boot with my old bootdisk, do all the stuff again and then make a bootdisk and run from the bootdisk will it work? because i have no idea how i could fix this, is my new kernel still there or did all my settings get erased?[I]From