YAYAY! My Slack Server is up and running!!!!!!! But, when I start KDE I get an EAR SPLITTING high pitched noise. So now I have to run alsaconf on every bootup to make it go away... Any ideas?

And I need help with fstab, I have a DVD-ROM drive that Slack reads as a CD-ROM drive. And it doesn't read my CD-RW at all.

One more thing, for duel-booters: You know how WinXP hibernates? It shuts off but when you turn it on it has all your stuff the way you left it before you shut down? Can Slack do that, if so, how?

ALSA:
After configuring ALSA, run as normal user "alsamixer" and use the m key to unmute your channels. Then run as root "alsactl store" to save your settings.

For the CD-RW you must have generic scsi in the kernel. If you've got the standard bare.i install it's there. Now you need to add "hdx=ide-scsi" to lilo.conf for your drive, where x is the drive letter for the CD-RW.

My DVD+-RW is recognized by the 2.4.26 kernel and read appropriately. Issue as root "cdrecord -scanbus" and post what it shows your drives to be in there.

Can't help much with hibernate, as I disable that in Windoze and avoid it in Slack; but I think that's part of ACPI. Can you be more specific in that question? Are you trying to get your Slack box to hibernate or does it already hibernate but return with different settings?

EDIT: Your thread said one question but you asked four... ;-)

No I'm trying to GET IT to hibernate

Can't help you there. You might try looking in these Linux doc HOWTO's as they have one for ACPI, amongst many others.

Found out the hibernate thing. BUT:

root@kyl3whatoneone:~# apmsleep
apmsleep: missing argument.
Usage:

apmsleep [+]hh:mm

Example:
apmsleep +1:15 will suspend for one hour and 15 minutes
apmsleep 8:00 will suspend until 8:00 am

Bugs: Daylight saving jumps are not taken into account.
Modem ring detection may trigger early wake-up.
Does not work with Suspend to Disk.
Bug reports to author Peter Englmaier <ppe@mpe.mpg.de>.
root@kyl3whatoneone:~# apmsleep 8:00
apmsleep: Your kernel does not support APM.
apmsleep: Recompile kernel with APM and /dev/rtc support
root@kyl3whatoneone:~#

Can I do this without a format? If yes, how?

Yes, you can do it without reformatting, but you will have to recompile your kernel for APM support. I don't know for sure, but I thought that ACPI was newer and better. I really wish somebody with this experience would post and help you. However...

These are the two guides I recommend for compiling your kernel.

Kernel-Build-HOWTO

Newbie Guide To Compiling A Kernel!

Before you start, you are required to read these guides all the way through, and to print them for reference. You are also required to backup your present kernel so that if you make a mistake, you can still boot your system. You can use the same kernel you're running now, but just add the APM support. Since you've install Slackware 10.0 you have kernel 2.4.26. If you're not sure, just issue "uname -r" as user. I would recommend that you stick with that kernel, and do not get a 2.6.x series kernel if you're not running one now. There are other issues which might jump up and bite you. ;-)

Btw - how are your other three problems - ALSA, CD-RW, DVD?

Aftwer toying with it ALSA and the dvd rom are better. cdrw is ok i dont mind... thanks! But like what do i put into my kernel? I know how to compile one, its what I have to select I have issues with.


Edit: I guess my toyed alsamixer setting only lasted one bootup.

Edit AGAIN: That earsplitting noise that wont go away till alsaconf is run will even stay there when I logout (runlevel 4)

How did you toy with it? What did you do? You want "better" or "correct?"
What do you mean by it's okay? Issue as root "cdrecord -scanbus" and post what it shows...
Put in the kernel for the CD-RW, for APM, or what?
Did you run "alsactl store" as root? That saves them.
What do you mean by "logout?" As the current user? Runlevel 4 throws init into a loop that keeps your load avg at least 1 all the time. So I guess the current user logging out isn't going to shutdown your procs.

Perhaps you got a volume level peaked in alsamixer? Try turning them all to about 75% and see what happens. There are different mixers that conflict, i.e. mic and/or mic boost too high produces feedback for me...

Oops! I'm sorry I meant my cdrw DOESN't work and I dont mind. And the APM thing is what I meant by put in the kernel. AND CD-RW also. And about the runlevel thing.... I meant like I'm root right... and I get that noise. Then when I logout, at the GDM screen I can still hear the noise. And yes, I did do alsactl store.


And:

root@kyl3whatoneone:~# cdrecord -scanbus
Cdrecord 2.00.3 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

I installed my old ALSA stuff from my 9.1 discs (cause thats when everything was good, and now, ALSA can't find my SB: Live! And it is compiled as a module in my kernel!

I d/led and installed ALSA from the website, all went fine, except now, even AFTER I run alsaconf the noise is there...

Did you run alsaconf then alsamixer and then alsactl store. If you don't save the changes, it may cause that sound to keep coming back. -It sound like you are getting to much feedback, as well.

I've ran alsamixer, I dunno what to change, but to test it, I muted the master volume and did alsactl store. Only lasted one bootup.

How do I check if I am running Alsa?

I am also having some problems with the sound. What I found was that if I turned off the sound system on KDE, the alsaconf settings would stick. Pretty bad., but I haven't found a better solution, any suggestions welcomed.