I'm trying to configure a new Slackware install
to accept a different kernel. (9.0 "full installation").

I have 5 HDDs:
hda = Debian
hdb = fat32 (data)
hdc = Wintendo
sda = Slackware
sdb = ext3 (data)

GRUB boots Debian and Wintendo just fine.
From Debian I can read/write the scsi drives perfectly,
so the controller card is OK.

GRUB boots the Slackware kernel but it panics :-(
I presume it panics because it's the vmlinuz-ide-2.4.20
instead of *the one with which I installed the system* (adaptec.s).
When I try to "CONFIGURE" the Slackware install from the ncurses
menu ("setup" at the root prompt after booting from CD), it seems to accept
my choice to install a new kernel from the cd-rom (I choose adaptec.s), and
the configuration closes without errors but the kernel remains the ide-
2.4.20 :-(
How can I change which kernel Slackware boots from if I can't boot it up?
Throw me a clue? TIA!

hi me wrote:
> GRUB boots the Slackware kernel but it panics :-(
> I presume it panics because it's the vmlinuz-ide-2.4.20

probably, because your slack is on a scsi disc, but this kernel probably
doesn't have scsi support.

> instead of *the one with which I installed the system* (adaptec.s).
> When I try to "CONFIGURE" the Slackware install from the ncurses
> menu ("setup" at the root prompt after booting from CD), it seems to accept
> my choice to install a new kernel from the cd-rom (I choose adaptec.s), and
> the configuration closes without errors but the kernel remains the ide-
> 2.4.20 :-(
> How can I change which kernel Slackware boots from if I can't boot it up?

well, slack uses lilo as boot manager, but i assume that you skip that part
of the setup because you use grub. what you'll need to do is configure grub
to boot the adaptec.s kernel. since i've never used grub, i have no idea
how to do that, but i assume it involves modifying grub's config file. ;-)

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

On Thu, 08 Apr 2004 01:41:28 +0000, Joost Kremers wrote:
>> GRUB boots the Slackware kernel but it panics :-(
>> I presume it panics because it's the vmlinuz-ide-2.4.20
>
> probably, because your slack is on a scsi disc, but this kernel probably
> doesn't have scsi support.

Also, the BIOS has to be able to read the media on which the kernel
resides. If the BIOS can't boot the SCSI device, the adaptec.s kernel
must be on media that the BIOS *can* read. That may mean copying the
Slackware kernel to another distro's (or Windows) filesystem.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

"/dev/rob0" <rob0@gmx.co.uk> wrote in
newsan.2004.04.08.02.44.17.25551@gmx.co.uk:

> On Thu, 08 Apr 2004 01:41:28 +0000, Joost Kremers wrote:
>>> GRUB boots the Slackware kernel but it panics :-(
>>> I presume it panics because it's the vmlinuz-ide-2.4.20
>>
>> probably, because your slack is on a scsi disc, but this kernel probably
>> doesn't have scsi support.
>
> Also, the BIOS has to be able to read the media on which the kernel
> resides. If the BIOS can't boot the SCSI device, the adaptec.s kernel
> must be on media that the BIOS *can* read. That may mean copying the
> Slackware kernel to another distro's (or Windows) filesystem.

The BIOS can read the media just fine...
The problem is that the wrong kernel is trying
to boot on sda. So how do I install the adaptec.s kernel?

Joost Kremers <joostkremers@yahoo.com> wrote in
news:slrnc79ben.qj.joostkremers@j.kremers4.news.ar nhem.chello.nl:

> hi me wrote:
>> GRUB boots the Slackware kernel but it panics :-(
>> I presume it panics because it's the vmlinuz-ide-2.4.20
>
> probably, because your slack is on a scsi disc, but this kernel
> probably doesn't have scsi support.

^Right. No scsi support in this kernel. I need to install
the *adaptec.s* kernel. I installed the system with the adaptec.s kernel,
and am mystified as to why I ended up with the ide kernel.
Q: How do I now install the adaptec.s kernel?
+
>
>> instead of *the one with which I installed the system* (adaptec.s).
>> When I try to "CONFIGURE" the Slackware install from the ncurses
>> menu ("setup" at the root prompt after booting from CD), it seems to
>> accept my choice to install a new kernel from the cd-rom (I choose
>> adaptec.s), and the configuration closes without errors but the
>> kernel remains the ide- 2.4.20 :-(
>> How can I change which kernel Slackware boots from if I can't boot it
>> up?
>
> well, slack uses lilo as boot manager, but i assume that you skip that
> part of the setup because you use grub. what you'll need to do is
> configure grub to boot the adaptec.s kernel. since i've never used
> grub, i have no idea how to do that, but i assume it involves
> modifying grub's config file. ;-)
>

The adaptec.s kernel is not installed on the Slackware disk. If it was,
I could have GRUB boot it......
Q: How do I now install the adaptec.s kernel?
Thank you.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, hi me dared to utter,
> Q: How do I now install the adaptec.s kernel?

Just copy it into place. Boot off the installation cd, the moutn
Slackware's / partition on something like /mnt. Now copy the adaptec.s
kernel from your cd to /mnt/boot/vmlinuz. You'll maybe have to muck
with grub, I'm not sure about it since everyone here uses LILO.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAdXZKL3KiNGOqr6ERArFFAKCLKbK559ZbeRDU5hyfdC 2Wdt/xkACfeWGs
iXi+yUspQFlwjmTCN63fl64=
=8NUJ
-----END PGP SIGNATURE-----

hi me <not@this.bin> wrote:
> ^Right. No scsi support in this kernel. I need to install
> the *adaptec.s* kernel. I installed the system with the adaptec.s kernel,
> and am mystified as to why I ended up with the ide kernel.
> Q: How do I now install the adaptec.s kernel?

Boot on any CD that _has_ the adaptec.s kernel (you already did so).
After the boot, mount the CD (if needed, I forgot).
Now go - on that CDrom - to /cdrom/kernels/adaptec.s
Als mount your - to be - root disk, say under /mnt

In "adaptec.s" you'll see:
bzImage copy this to /mnt/boot/vmlinuz
config " /mnt/boot/config
System.map.gz " /mnt/boot/System.map.gz
you may want to decompress the latter, but I'm not sure if that is needed.

Now finally run "lilo -r /mnt" (assuming you use lilo and its config
points to "/boot/vmlinuz"), or whatver you have to do to get grub
working ON that "just copied" vmlinuz file.

And, of course, after you booted up, you probably want to make your
own scsi kernel, with just the drivers you really need "built-in"
and not ALL Adaptec ones, like this one is.
So make sure that you install the kernel-sources package too, and
use the just copied "config" as a start TO make your own...
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote in
news:c53t65$jrp$1@news.tudelft.nl:
<<snip>>
> In "adaptec.s" you'll see:
> bzImage copy this to /mnt/boot/vmlinuz
> config " /mnt/boot/config
> System.map.gz " /mnt/boot/System.map.gz
> you may want to decompress the latter, but I'm not sure if that is
> needed.

Wow! I was actually going to try something _that crazy_! It
actually works -Thank you! I bet if I tried that on Debian, dpkg
would blow a gasket ;-)
It was not neccessary to expand System.map.gz. I had renamed
all files that were initially in /boot before I copied the files
from /adaptec.s. Amazing.

>
> Now finally run "lilo -r /mnt" (assuming you use lilo and its config
> points to "/boot/vmlinuz"), or whatver you have to do to get grub
> working ON that "just copied" vmlinuz file.
>
> And, of course, after you booted up, you probably want to make your
> own scsi kernel, with just the drivers you really need "built-in"
> and not ALL Adaptec ones, like this one is.
> So make sure that you install the kernel-sources package too, and
> use the just copied "config" as a start TO make your own...

Hmm... After I got the system to boot, and played around a bit,
I copied linux 2.4.25 source (.bz2 I think) to /usr/src, and made the
kernel the same way I did for the Debian install (but of course without the
Debian tools), being careful to include
my scsi controllers' kernel support. The new kernel booted (was found by
GRUB since I used the same names for everything), but it panicked again-
this time after trying to load something about "../modules(?)" (sorry for
slim info). But I disallowed the modular function of the kernel at compile
time! I am sure that all the options I selected were "built-in".
There must be a little *modules daemon* hanging around demanding his
modules?!?
(BTW, the kernel source I used was not "Debianized"- it came from
kernel.org). Hmm... maybe I'll try copying /boot from the Debian partition
to /boot on Slack :P
Confused again, but many Thanks for the great info!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, hi me dared to utter,
> The new kernel booted (was found by
> GRUB since I used the same names for everything), but it panicked again-
> this time after trying to load something about "../modules(?)" (sorry for
> slim info).

Then go back and copy what info you see (by hand if neccessary) and
tell us what you've got exactly.

Also, you may wish to use the .config file for adaptec.s as a starting
point, and just remove what you don't want. You could even use the same
..config (just use make oldconfig) to upgrade to the latest kernel.
Honestly stripping things out of that kernel really isn't going to do
you a whole lot of good, but IIRC there are some local exploits for
kernels prior to 2.4.25.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD4DBQFAdw2qL3KiNGOqr6ERAuOoAJkBhjwnACXlKHzgniUYUJ SYlyMd8QCVHsel
tkiPR6qR1e4VdLwoLwO9Cw==
=QPCO
-----END PGP SIGNATURE-----

"Alan Hicks" <alan@lizella.netWORK> wrote in message
news:40770db2$1_2@127.0.0.1...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, hi me dared to utter,
> > The new kernel booted (was found by
> > GRUB since I used the same names for everything), but it panicked again-
> > this time after trying to load something about "../modules(?)" (sorry
for
> > slim info).
>
> Then go back and copy what info you see (by hand if neccessary) and
> tell us what you've got exactly.

I don't know if this is apropos anything, but when I've wanted to see
some message from that boot sequence that scrolls away instantly (which
I'm guessing is what's happening here) I sprinkle "read" statements in
strategic spots in my rc.* scripts. Usually with an "Echo this-n-that"
type statement. Found that I could learn all _kinds_ of neat stuff
about how the system boots!

Cheers!
Rich