AW: AW: AW: AW: problem with kernel 2.4.X and qlogic

Hi again,

there were some things in your last mail which confused me, maybe you
can lighten me up:

> -----Ursprüngliche Nachricht-----
> Von: Marcus Gellert [mailto:[email protected]]
> Gesendet: Dienstag, 28. Januar 2003 13:32
> An: Berg, Björn
> Betreff: Re: AW: AW: AW: [suse-axp] problem with kernel 2.4.X 
> and qlogic

> Then you should copy the System.map file from the source directory to
> the /boot directory and change the name to System.map-'uname -r' (the
> new kernel version of course!)

That's clear. As normal as if you have compiled the kernel on an
Intel-box.

> Now you edit the aboot.conf and add the new kernel. And if 
> you use the SRM

Here comes the first problem. I read the SRM Howto and the things SuSE
described in its Technical guide. I have created an entry, like
4:3/boot/vmlinuz-2.4.20.gz ro root=/dev/sda3
which is detected in the aboot menu. This seems to be okay, it is the
fourth entry and using partition three to boot from.

> console do a 'swriteboot -f3 /dev/sda /dev/sda3' (replace 
> /dev/sda with
> your boot device and /dev/sda3 with your root partition) - but I think
> you already know this (see also the man page).

Here comes another problem. The swriteboot-command as written above
creates an error: bootcode overlaps with partition #1. If you really
want to do this use -f1.
Another thin is, why do you use /dev/sda3 instead of /boot/bootlx as
mentioned in the TG? This was not described in the manual of swriteboot
and was really confusing for me, because the command was executed.
Nevertheless the kernel does not boot. And more and more I am of the
opinion that it is not aboot, but the kernel itself...

- Bjoern