Re: problem with kernel 2.4.X and qlogic

* "Berg, Bj?rn" <[email protected]> [030128 15:55]:
> 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.
> 
if /boot is on another partition (eg. /dev/sda1) and mounted by fstab, then you
have to create an entry like

4:1/vmlinuz-2.4.20.gz ro root=/dev/sda3

> > 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.

Does sda1 start at the very beginning of your harddisk?
If so, this is wrong. You need to leave some space for the bootcode 
at the beginning of the disk.
(Originally, the third partition was of type 'unused', containing 
the entire disk, therefore it was overlapped by the bootcode,
which has to be accepted by the argument -f3.)
  

> 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

It must be /boot/bootlx, of course.

> 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
> 

-- 
Mit freundlichen Grüssen / With kind regards,

        Stefan Fent
 
SuSE Linux AG,         	Tel:   +49-911-74053559 
Deutschherrnstr.15-19,	Fax:   +49-911-32053477
90429 Nuernberg,       	Email: [email protected]
Germany                	WWW:   http://www.suse.de

 It's reproduceable not-reproduceable
			Thomas Roelz