LinuxQuestions.org - Is it possible to start Slackware installation using own compiled kernel?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Is it possible to start Slackware installation using own compiled kernel? (https://www.linuxquestions.org/questions/slackware-14/is-it-possible-to-start-slackware-installation-using-own-compiled-kernel-279715/)

Is it possible to start Slackware installation using own compiled kernel?

Is it possible to start Slackware installation using own compiled kernel, say, /boot/myNewImage? I didn't find any way to do that - only from CD/kernels dir. I just want to install 2.6.7 instead of 2.4.26. When I just choose the 2.6.7 during loading, there appear sound and other module's problems. I even couldn't use kppp. That's why I want to use "my own" kernel so that the system will configure everything properly during installation (working with my new 2.6.7).

I still don't really get what you're saying there.. But if you want to always keep a copy of your 'kernel', you can just save its settings into a file (export it). Afterwards, whenever you reinstall, just get the kernel source again, stick in your configs, and recompile..

I used to do that with my desktop.. whenever i screw up anything, i just redownload Kernel 2.4.28 from slack.com, stick in my configs, recompile once, and everything's back to normal.

EDIT: Aah, just understood.. Short answer, Yes, its possible to replace or add stuff to the installation, but its a bit tricky, but there are several documentations and others who asked the question in LQ. Also.. I wonder if its possible to use 'checkinstall' instead of 'make install' when compiling, so that you have a package of your newly configured and compiled kernel which you can stick in a slackware installation cd (iso)... Maby..

Well, I'll try to find... but may be you know how to find similar threads?
____
Can u tell me shortly how ad block works? :)

I had bothered with searching. I type "slackware kernel install" to find, and it displays some Mandy s**t... I would better use my old 2.4.26 :)

After I recompiled kernel I saved it to floppy. Then reinstalled Slack10 and chose to install my floppy image. But when I typed "alsaconf" it recognized my AC'97 and almost installed. Sound works in KDE. But if I try to run alsamixer I get the next: alsamixer: function snd_ctl_open failed for default: No such device. AND EVERY HOUR WHILE xmms is playing oppears a window that tells me to check if no other app blocks sound. I press ok. Then I press play in xmms, it plays. But I never got such message-windows before. Sound errors were earlier, but xmms didn't stop playing - it just waited for sound device. Now it stops. Quite annoying to press play every hour. Any ideas on how to repair it?
__________
I chose ALSA, intel ICH8x0 and OSS as built-ins of the kernel.

Quote:

Originally posted by kornerr
After I recompiled kernel I saved it to floppy. Then reinstalled Slack10 and chose to install my floppy image. But when I typed "alsaconf" it recognized my AC'97 and almost installed. Sound works in KDE. But if I try to run alsamixer I get the next: alsamixer: function snd_ctl_open failed for default: No such device. AND EVERY HOUR WHILE xmms is playing oppears a window that tells me to check if no other app blocks sound. I press ok. Then I press play in xmms, it plays. But I never got such message-windows before. Sound errors were earlier, but xmms didn't stop playing - it just waited for sound device. Now it stops. Quite annoying to press play every hour. Any ideas on how to repair it?
__________
I chose ALSA, intel ICH8x0 and OSS as built-ins of the kernel.

disable arts (kde sound system)

also it's more than recommended to recompile your alsa drivers after a kernel change.

How to recompile alsa drvs?

here is how to rebuild the modules for your kernel, if alsaconf says no card found.

1. go to alsa souncard matrix and find your card:
http://www.alsa-project.org/alsa-doc/

2.dl the version of alsa-driver from the alsa-project site, same version of whatever you have installed currently (check the version of the packages in pkgtool if you have too)

3. compile the drivers according to the website , run alsaconf, then alsamixer, and wala!!

for example************************************************************
lspci tells me:
Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)

I find out from kpackage or pkgtool that i currently have alsa-1.0.7 installed (just done a swaret)

so i go to ftp://ftp.alsa-project.org/pub/driver/
and dl alsa-driver-1.0.7.tar.bz2

then i look up my card in the alsa matrix (link above) I find CMedia in the dropdown list. It takes me to a table with my chipset CMI8738. then i see in that table it uses the cmipci module http://www.alsa-project.org/alsa-doc...C-Media#matrix
i click on the cmipci module and it takes me to here:

http://www.alsa-project.org/alsa-doc...&module=cmipci

then i follow the instructions as per the page:

Code:

cd <to directory where i dl the alsa-driverpackage>

bunzip2 alsa-driver-xxx

        tar -xf alsa-driver-xxx

        cd alsa-driver-xxx

        ./configure --with-cards=cmipci --with-sequencer=yes;make;make install

I run:
alsaconf
**note** ::some cases you'll have to reboot after this::
and:
alsamixer

make sure i do a
alsactl store
so it will keep my alsamixer settings

that is all there is to it, this should work for new compiled kernels too. Try it!!

Thanks for such a GOOD answer! Will follow someday :)
___________
Cold silence has...
A tendency to...
Atrophy any...
Sense of compassion... - "Tool"