SCSI devices and SMP kernels

SCSI devices and SMP kernels

Post by Pierre Vignera » Sun, 31 Dec 1899 09:00:00






> > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

> > > I am trying to set up a right out of the box RPM package with a SMP
> > > kernel (the same version non SMP is already running)...when I boot, I
> > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > something like that....

> > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > kernels...is that a fact?

> > you can't have scsi support as a module if you want to boot from a scsi
> > disc
> > it must be compiled into your kernel

> this is not quite true.  you can put the scsi module on an initial
> ramdisk (initrd).  this is what most distributions do because
> compiling every possible scsi driver into their kernel would be a bit
> much.

> however, i agree that it is a damned good recommendation.  if you can
> compile yourself a kernel, by all means build the scsi driver into it.

That's what i did, but i got a
"kernel panic" too : "unable to mount on /dev/sda2".

I did compile the scsi drive into the kernel.
And moreover, i have :


Root device /dev/sda2

which is the current root device :


/dev/sda2 /

Running lilo show :


LILO version 21, Copyright 1992-1998 Werner Almesberger

Reading boot sector from /dev/sda
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.2.12-20smp
Mapping RAM disk /boot/initrd-2.2.12-20smp.img
Added linux *
Boot image: /boot/vmlinuz-2.2.12-20
Mapping RAM disk /boot/initrd-2.2.12-20.img
Added linux-up
Boot image: /boot/vmlinuz-2.2.14smp
Added new
/boot/boot.0800 exists - no backup copy made.
Writing boot sector.

But booting my new kernel is always a kernel panic !
i don't understand why !
I suppose the redhat ramdisk as set a strange /boot/map:


total 10781
drwxr-xr-x   2 root     root         1024 May 10 09:33 .
drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
System.map 2.2.12-20
-rw-r--r--   1 root     root       191102 Sep 27  1999
System.map-2.2.12-20
-rw-r--r--   1 root     root       182834 Sep 27  1999
System.map-2.2.12-20BOOT
-rw-r--r--   1 root     root       202226 Sep 27  1999
System.map-2.2.12-20smp
-rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
-rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
-rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
-rw-r--r--   1 root     root       313673 Feb 11 18:26
initrd-2.2.12-20.img
-rw-r--r--   1 root     root       314036 Feb 11 18:26
initrd-2.2.12-20smp.img
-rw-r--r--   1 root     root       308009 Jul  9  1999
initrd-2.2.5-15.img
-rw-r--r--   1 root     root       308488 Jul  9  1999
initrd-2.2.5-15smp.img
lrwxrwxrwx   1 root     root           22 Jul 31  1999
initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
-rw-r--r--   1 root     root       695162 Jul 31  1999
kernel-2.2.5-22smp.my
-rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
-rw-------   1 root     root        30720 May 10 09:33 map
lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
module-in o-2.2.12-20
-rw-r--r--   1 root     root        11773 Sep 27  1999
module-info-2.2.12-20
-rw-r--r--   1 root     root        11773 Sep 27  1999
module-info-2.2.12-20smp
-rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
-rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
-rwxr-xr-x   1 root     root      1469971 Sep 27  1999
vmlinux-2.2.12-20BOOT
-rwxr-xr-x   1 root     root      1647660 Sep 27  1999
vmlinux-2.2.12-20smp
lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
vmlinuz-2.2.1 -20
-rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
-rw-r--r--   1 root     root       592397 Sep 27  1999
vmlinuz-2.2.12-20BOOT
-rw-r--r--   1 root     root       647807 Sep 27  1999
vmlinuz-2.2.12-20smp
-rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
-rw-r--r--   1 root     root       709302 Jul 23  1999
vmlinuz-2.2.5-15smp.new
-rw-r--r--   1 root     root       695161 Aug  6  1999
vmlinuz-2.2.5-22smp.new

Can i remove some of this files (System.map*) ?? What are their use (i
know ps use it, for its WCHAN field, but is there another use ??) ? What
are module-info* files ? Can i remove some of this files ?

Here my /etc/lilo.conf :


boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux

image=/boot/vmlinuz-2.2.12-20smp
        label=linux
        initrd=/boot/initrd-2.2.12-20smp.img
        read-only
        root=/dev/sda2

image=/boot/vmlinuz-2.2.12-20
        label=linux-up
        initrd=/boot/initrd-2.2.12-20.img
        read-only
        root=/dev/sda2

image=/boot/vmlinuz-2.2.14smp
        label=new
        read-only
        root=/dev/sda2
        vga=ask


My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
describe above).

--
Pierre Vignras
http://dept-info.labri.u-bordeaux.fr/~vigneras/

Equipe systmes et objets distribus
http://jccf.labri.u-bordeaux.fr/jodo/

LaBRI
http://dept-info.labri.u-bordeaux.fr/

  vigneras.vcf
< 1K Download
 
 
 

SCSI devices and SMP kernels

Post by Eric » Sun, 31 Dec 1899 09:00:00


Just to make sure: you didn't make the partition where the kernel
resides (possibly in /boot) too large so it crosses the 1024th cylinder?

Eric





> > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

> > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > something like that....

> > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > kernels...is that a fact?

> > > you can't have scsi support as a module if you want to boot from a scsi
> > > disc
> > > it must be compiled into your kernel

> > this is not quite true.  you can put the scsi module on an initial
> > ramdisk (initrd).  this is what most distributions do because
> > compiling every possible scsi driver into their kernel would be a bit
> > much.

> > however, i agree that it is a damned good recommendation.  if you can
> > compile yourself a kernel, by all means build the scsi driver into it.

> That's what i did, but i got a
> "kernel panic" too : "unable to mount on /dev/sda2".

> I did compile the scsi drive into the kernel.
> And moreover, i have :


> Root device /dev/sda2

> which is the current root device :


> /dev/sda2 /

> Running lilo show :


> LILO version 21, Copyright 1992-1998 Werner Almesberger

> Reading boot sector from /dev/sda
> Merging with /boot/boot.b
> Boot image: /boot/vmlinuz-2.2.12-20smp
> Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> Added linux *
> Boot image: /boot/vmlinuz-2.2.12-20
> Mapping RAM disk /boot/initrd-2.2.12-20.img
> Added linux-up
> Boot image: /boot/vmlinuz-2.2.14smp
> Added new
> /boot/boot.0800 exists - no backup copy made.
> Writing boot sector.

> But booting my new kernel is always a kernel panic !
> i don't understand why !
> I suppose the redhat ramdisk as set a strange /boot/map:


> total 10781
> drwxr-xr-x   2 root     root         1024 May 10 09:33 .
> drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
> lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
> System.map 2.2.12-20
> -rw-r--r--   1 root     root       191102 Sep 27  1999
> System.map-2.2.12-20
> -rw-r--r--   1 root     root       182834 Sep 27  1999
> System.map-2.2.12-20BOOT
> -rw-r--r--   1 root     root       202226 Sep 27  1999
> System.map-2.2.12-20smp
> -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
> -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
> -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
> -rw-r--r--   1 root     root       313673 Feb 11 18:26
> initrd-2.2.12-20.img
> -rw-r--r--   1 root     root       314036 Feb 11 18:26
> initrd-2.2.12-20smp.img
> -rw-r--r--   1 root     root       308009 Jul  9  1999
> initrd-2.2.5-15.img
> -rw-r--r--   1 root     root       308488 Jul  9  1999
> initrd-2.2.5-15smp.img
> lrwxrwxrwx   1 root     root           22 Jul 31  1999
> initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
> -rw-r--r--   1 root     root       695162 Jul 31  1999
> kernel-2.2.5-22smp.my
> -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
> -rw-------   1 root     root        30720 May 10 09:33 map
> lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
> module-in o-2.2.12-20
> -rw-r--r--   1 root     root        11773 Sep 27  1999
> module-info-2.2.12-20
> -rw-r--r--   1 root     root        11773 Sep 27  1999
> module-info-2.2.12-20smp
> -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
> -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
> -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
> vmlinux-2.2.12-20BOOT
> -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
> vmlinux-2.2.12-20smp
> lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
> vmlinuz-2.2.1 -20
> -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
> -rw-r--r--   1 root     root       592397 Sep 27  1999
> vmlinuz-2.2.12-20BOOT
> -rw-r--r--   1 root     root       647807 Sep 27  1999
> vmlinuz-2.2.12-20smp
> -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
> -rw-r--r--   1 root     root       709302 Jul 23  1999
> vmlinuz-2.2.5-15smp.new
> -rw-r--r--   1 root     root       695161 Aug  6  1999
> vmlinuz-2.2.5-22smp.new

> Can i remove some of this files (System.map*) ?? What are their use (i
> know ps use it, for its WCHAN field, but is there another use ??) ? What
> are module-info* files ? Can i remove some of this files ?

> Here my /etc/lilo.conf :


> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux

> image=/boot/vmlinuz-2.2.12-20smp
>         label=linux
>         initrd=/boot/initrd-2.2.12-20smp.img
>         read-only
>         root=/dev/sda2

> image=/boot/vmlinuz-2.2.12-20
>         label=linux-up
>         initrd=/boot/initrd-2.2.12-20.img
>         read-only
>         root=/dev/sda2

> image=/boot/vmlinuz-2.2.14smp
>         label=new
>         read-only
>         root=/dev/sda2
>         vga=ask


> My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
> describe above).

> --
> Pierre Vignras
> http://dept-info.labri.u-bordeaux.fr/~vigneras/

> Equipe systmes et objets distribus
> http://jccf.labri.u-bordeaux.fr/jodo/

> LaBRI
> http://dept-info.labri.u-bordeaux.fr/

>   ------------------------------------------------------------------------

>                          Name: vigneras.vcf
>    vigneras.vcf          Type: VCard (text/x-vcard)
>                      Encoding: 7bit
>                   Description: Card for Pierre Vigneras


 
 
 

SCSI devices and SMP kernels

Post by Pierre Vignera » Sun, 31 Dec 1899 09:00:00


You're right :

[root@moucheron /boot]# sfdisk -l /dev/sda

Disk /dev/sda: 8715 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from
0

   Device Boot Start     End   #cyls   #blocks   Id  System
/dev/sda1          0+    512     513-   525296   82  Linux swap
/dev/sda2        513    4513    4001   4097024   83  Linux
/dev/sda3       4514    8714    4201   4301824    c  Win95 FAT32 (LBA)
/dev/sda4          0       -       0         0    0  Empty
[root@moucheron /boot]#

But, why can i boot with a ramdisk and not with my new kernel ?

Can anyone answer to questions about the /boot/* files (see below...) ?

Eric wrote:

> Just to make sure: you didn't make the partition where the kernel
> resides (possibly in /boot) too large so it crosses the 1024th cylinder?

> Eric

> Pierre Vigneras wrote:

> > Johan Kullstam wrote:

> > > Eric <scare.c...@oz.lan> writes:

> > > > Henrique Seganfredo wrote:

> > > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

> > > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > > something like that....

> > > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > > kernels...is that a fact?

> > > > you can't have scsi support as a module if you want to boot from a scsi
> > > > disc
> > > > it must be compiled into your kernel

> > > this is not quite true.  you can put the scsi module on an initial
> > > ramdisk (initrd).  this is what most distributions do because
> > > compiling every possible scsi driver into their kernel would be a bit
> > > much.

> > > however, i agree that it is a damned good recommendation.  if you can
> > > compile yourself a kernel, by all means build the scsi driver into it.

> > That's what i did, but i got a
> > "kernel panic" too : "unable to mount on /dev/sda2".

> > I did compile the scsi drive into the kernel.
> > And moreover, i have :

> > [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
> > Root device /dev/sda2
> > [root@moucheron /boot]#

> > which is the current root device :

> > [root@moucheron /boot]# rdev
> > /dev/sda2 /
> > [root@moucheron /boot]#

> > Running lilo show :

> > [root@moucheron /boot]# lilo -v
> > LILO version 21, Copyright 1992-1998 Werner Almesberger

> > Reading boot sector from /dev/sda
> > Merging with /boot/boot.b
> > Boot image: /boot/vmlinuz-2.2.12-20smp
> > Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> > Added linux *
> > Boot image: /boot/vmlinuz-2.2.12-20
> > Mapping RAM disk /boot/initrd-2.2.12-20.img
> > Added linux-up
> > Boot image: /boot/vmlinuz-2.2.14smp
> > Added new
> > /boot/boot.0800 exists - no backup copy made.
> > Writing boot sector.
> > [root@moucheron /boot]#

> > But booting my new kernel is always a kernel panic !
> > i don't understand why !
> > I suppose the redhat ramdisk as set a strange /boot/map:

> > [root@moucheron /boot]# ls -al
> > total 10781
> > drwxr-xr-x   2 root     root         1024 May 10 09:33 .
> > drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
> > lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
> > System.map 2.2.12-20
> > -rw-r--r--   1 root     root       191102 Sep 27  1999
> > System.map-2.2.12-20
> > -rw-r--r--   1 root     root       182834 Sep 27  1999
> > System.map-2.2.12-20BOOT
> > -rw-r--r--   1 root     root       202226 Sep 27  1999
> > System.map-2.2.12-20smp
> > -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
> > -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
> > -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
> > -rw-r--r--   1 root     root       313673 Feb 11 18:26
> > initrd-2.2.12-20.img
> > -rw-r--r--   1 root     root       314036 Feb 11 18:26
> > initrd-2.2.12-20smp.img
> > -rw-r--r--   1 root     root       308009 Jul  9  1999
> > initrd-2.2.5-15.img
> > -rw-r--r--   1 root     root       308488 Jul  9  1999
> > initrd-2.2.5-15smp.img
> > lrwxrwxrwx   1 root     root           22 Jul 31  1999
> > initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
> > -rw-r--r--   1 root     root       695162 Jul 31  1999
> > kernel-2.2.5-22smp.my
> > -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
> > -rw-------   1 root     root        30720 May 10 09:33 map
> > lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
> > module-in o-2.2.12-20
> > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > module-info-2.2.12-20
> > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > module-info-2.2.12-20smp
> > -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
> > -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
> > -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
> > vmlinux-2.2.12-20BOOT
> > -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
> > vmlinux-2.2.12-20smp
> > lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
> > vmlinuz-2.2.1 -20
> > -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
> > -rw-r--r--   1 root     root       592397 Sep 27  1999
> > vmlinuz-2.2.12-20BOOT
> > -rw-r--r--   1 root     root       647807 Sep 27  1999
> > vmlinuz-2.2.12-20smp
> > -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
> > -rw-r--r--   1 root     root       709302 Jul 23  1999
> > vmlinuz-2.2.5-15smp.new
> > -rw-r--r--   1 root     root       695161 Aug  6  1999
> > vmlinuz-2.2.5-22smp.new
> > [root@moucheron /boot]#

> > Can i remove some of this files (System.map*) ?? What are their use (i
> > know ps use it, for its WCHAN field, but is there another use ??) ? What
> > are module-info* files ? Can i remove some of this files ?

> > Here my /etc/lilo.conf :

> > [root@moucheron /boot]# cat /etc/lilo.conf
> > boot=/dev/sda
> > map=/boot/map
> > install=/boot/boot.b
> > prompt
> > timeout=50
> > default=linux

> > image=/boot/vmlinuz-2.2.12-20smp
> >         label=linux
> >         initrd=/boot/initrd-2.2.12-20smp.img
> >         read-only
> >         root=/dev/sda2

> > image=/boot/vmlinuz-2.2.12-20
> >         label=linux-up
> >         initrd=/boot/initrd-2.2.12-20.img
> >         read-only
> >         root=/dev/sda2

> > image=/boot/vmlinuz-2.2.14smp
> >         label=new
> >         read-only
> >         root=/dev/sda2
> >         vga=ask

> > [root@moucheron /boot]#

> > My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
> > describe above).

> > --
> > Pierre Vignras
> > http://dept-info.labri.u-bordeaux.fr/~vigneras/

> > Equipe systmes et objets distribus
> > http://jccf.labri.u-bordeaux.fr/jodo/

> > LaBRI
> > http://dept-info.labri.u-bordeaux.fr/

> >   ------------------------------------------------------------------------

> >                          Name: vigneras.vcf
> >    vigneras.vcf          Type: VCard (text/x-vcard)
> >                      Encoding: 7bit
> >                   Description: Card for Pierre Vigneras

--
Pierre Vignras
http://dept-info.labri.u-bordeaux.fr/~vigneras/

Equipe systmes et objets distribus
http://jccf.labri.u-bordeaux.fr/jodo/

LaBRI
http://dept-info.labri.u-bordeaux.fr/

  vigneras.vcf
< 1K Download
 
 
 

SCSI devices and SMP kernels

Post by Eric » Sun, 31 Dec 1899 09:00:00


The bootmap may be correct, but since the bios cannot see any discspace
beyond cylinder 1024,(or lilo since it uses the bios info) you may have
bad luck. All depends on the actual physical location of your kernel
image, so a previous image may have booted (out of pure luck being
allocated below cylinder 1024) but your new kernel isn't located on such
a place.
BTW. You can get the new lilo from the web which doesn't suffer from
this limit.

Eric

Pierre Vigneras wrote:

> You're right :

> [root@moucheron /boot]# sfdisk -l /dev/sda

> Disk /dev/sda: 8715 cylinders, 64 heads, 32 sectors/track
> Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from
> 0

>    Device Boot Start     End   #cyls   #blocks   Id  System
> /dev/sda1          0+    512     513-   525296   82  Linux swap
> /dev/sda2        513    4513    4001   4097024   83  Linux
> /dev/sda3       4514    8714    4201   4301824    c  Win95 FAT32 (LBA)
> /dev/sda4          0       -       0         0    0  Empty
> [root@moucheron /boot]#

> But, why can i boot with a ramdisk and not with my new kernel ?

> Can anyone answer to questions about the /boot/* files (see below...) ?

> Eric wrote:

> > Just to make sure: you didn't make the partition where the kernel
> > resides (possibly in /boot) too large so it crosses the 1024th cylinder?

> > Eric

> > Pierre Vigneras wrote:

> > > Johan Kullstam wrote:

> > > > Eric <scare.c...@oz.lan> writes:

> > > > > Henrique Seganfredo wrote:

> > > > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

> > > > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > > > something like that....

> > > > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > > > kernels...is that a fact?

> > > > > you can't have scsi support as a module if you want to boot from a scsi
> > > > > disc
> > > > > it must be compiled into your kernel

> > > > this is not quite true.  you can put the scsi module on an initial
> > > > ramdisk (initrd).  this is what most distributions do because
> > > > compiling every possible scsi driver into their kernel would be a bit
> > > > much.

> > > > however, i agree that it is a damned good recommendation.  if you can
> > > > compile yourself a kernel, by all means build the scsi driver into it.

> > > That's what i did, but i got a
> > > "kernel panic" too : "unable to mount on /dev/sda2".

> > > I did compile the scsi drive into the kernel.
> > > And moreover, i have :

> > > [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
> > > Root device /dev/sda2
> > > [root@moucheron /boot]#

> > > which is the current root device :

> > > [root@moucheron /boot]# rdev
> > > /dev/sda2 /
> > > [root@moucheron /boot]#

> > > Running lilo show :

> > > [root@moucheron /boot]# lilo -v
> > > LILO version 21, Copyright 1992-1998 Werner Almesberger

> > > Reading boot sector from /dev/sda
> > > Merging with /boot/boot.b
> > > Boot image: /boot/vmlinuz-2.2.12-20smp
> > > Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> > > Added linux *
> > > Boot image: /boot/vmlinuz-2.2.12-20
> > > Mapping RAM disk /boot/initrd-2.2.12-20.img
> > > Added linux-up
> > > Boot image: /boot/vmlinuz-2.2.14smp
> > > Added new
> > > /boot/boot.0800 exists - no backup copy made.
> > > Writing boot sector.
> > > [root@moucheron /boot]#

> > > But booting my new kernel is always a kernel panic !
> > > i don't understand why !
> > > I suppose the redhat ramdisk as set a strange /boot/map:

> > > [root@moucheron /boot]# ls -al
> > > total 10781
> > > drwxr-xr-x   2 root     root         1024 May 10 09:33 .
> > > drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
> > > lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
> > > System.map 2.2.12-20
> > > -rw-r--r--   1 root     root       191102 Sep 27  1999
> > > System.map-2.2.12-20
> > > -rw-r--r--   1 root     root       182834 Sep 27  1999
> > > System.map-2.2.12-20BOOT
> > > -rw-r--r--   1 root     root       202226 Sep 27  1999
> > > System.map-2.2.12-20smp
> > > -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
> > > -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
> > > -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
> > > -rw-r--r--   1 root     root       313673 Feb 11 18:26
> > > initrd-2.2.12-20.img
> > > -rw-r--r--   1 root     root       314036 Feb 11 18:26
> > > initrd-2.2.12-20smp.img
> > > -rw-r--r--   1 root     root       308009 Jul  9  1999
> > > initrd-2.2.5-15.img
> > > -rw-r--r--   1 root     root       308488 Jul  9  1999
> > > initrd-2.2.5-15smp.img
> > > lrwxrwxrwx   1 root     root           22 Jul 31  1999
> > > initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
> > > -rw-r--r--   1 root     root       695162 Jul 31  1999
> > > kernel-2.2.5-22smp.my
> > > -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
> > > -rw-------   1 root     root        30720 May 10 09:33 map
> > > lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
> > > module-in o-2.2.12-20
> > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > module-info-2.2.12-20
> > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > module-info-2.2.12-20smp
> > > -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
> > > -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
> > > -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
> > > vmlinux-2.2.12-20BOOT
> > > -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
> > > vmlinux-2.2.12-20smp
> > > lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
> > > vmlinuz-2.2.1 -20
> > > -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
> > > -rw-r--r--   1 root     root       592397 Sep 27  1999
> > > vmlinuz-2.2.12-20BOOT
> > > -rw-r--r--   1 root     root       647807 Sep 27  1999
> > > vmlinuz-2.2.12-20smp
> > > -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
> > > -rw-r--r--   1 root     root       709302 Jul 23  1999
> > > vmlinuz-2.2.5-15smp.new
> > > -rw-r--r--   1 root     root       695161 Aug  6  1999
> > > vmlinuz-2.2.5-22smp.new
> > > [root@moucheron /boot]#

> > > Can i remove some of this files (System.map*) ?? What are their use (i
> > > know ps use it, for its WCHAN field, but is there another use ??) ? What
> > > are module-info* files ? Can i remove some of this files ?

> > > Here my /etc/lilo.conf :

> > > [root@moucheron /boot]# cat /etc/lilo.conf
> > > boot=/dev/sda
> > > map=/boot/map
> > > install=/boot/boot.b
> > > prompt
> > > timeout=50
> > > default=linux

> > > image=/boot/vmlinuz-2.2.12-20smp
> > >         label=linux
> > >         initrd=/boot/initrd-2.2.12-20smp.img
> > >         read-only
> > >         root=/dev/sda2

> > > image=/boot/vmlinuz-2.2.12-20
> > >         label=linux-up
> > >         initrd=/boot/initrd-2.2.12-20.img
> > >         read-only
> > >         root=/dev/sda2

> > > image=/boot/vmlinuz-2.2.14smp
> > >         label=new
> > >         read-only
> > >         root=/dev/sda2
> > >         vga=ask

> > > [root@moucheron /boot]#

> > > My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
> > > describe above).

> > > --
> > > Pierre Vignras
> > > http://dept-info.labri.u-bordeaux.fr/~vigneras/

> > > Equipe systmes et objets distribus
> > > http://jccf.labri.u-bordeaux.fr/jodo/

> > > LaBRI
> > > http://dept-info.labri.u-bordeaux.fr/

> > >   ------------------------------------------------------------------------

> > >                          Name: vigneras.vcf
> > >    vigneras.vcf          Type: VCard (text/x-vcard)
> > >                      Encoding: 7bit
> > >                   Description: Card for Pierre Vigneras

> --
> Pierre Vignras
> http://dept-info.labri.u-bordeaux.fr/~vigneras/

> Equipe systmes et objets distribus
> http://jccf.labri.u-bordeaux.fr/jodo/

> LaBRI
> http://dept-info.labri.u-bordeaux.fr/

>   ------------------------------------------------------------------------

>                          Name: vigneras.vcf
>    vigneras.vcf          Type: VCard (text/x-vcard)
>                      Encoding: 7bit
>                   Description: Card for Pierre Vigneras

 
 
 

SCSI devices and SMP kernels

Post by Pierre Vignera » Sun, 31 Dec 1899 09:00:00


Thanks very much for your help, really :-).

Nevertheless, i really don't understand something :
my version of Lilo is :

[root@moucheron /root]# lilo -V
LILO version 21
[root@moucheron /root]#

Is there a more recent version ?

Moreover, the lilo doc talked about this 1024 cylinders limits :

[root@moucheron /root]# cd /usr/doc/lilo-0.21/doc/
[root@moucheron doc]# cat user.tex

[...]

\subsubsection{BIOS restrictions}
\label{broken}

Nowadays, an increasing number of systems is equipped with comparably
large
disks or even with multiple disks. At the time the disk interface of the
standard PC BIOS has been designed (about 16 years ago), such
configurations
were apparently considered to be too unlikely to be worth supporting.

The most common BIOS restrictions that affect \LILO\ are the limitation
to
two hard disks and the inability to access more than 1024 cylinders per
disk. \LILO\ can detect both conditions, but in order to work around the
underlying problems, manual intervention is necessary.

The drive limit does not exist in every BIOS. Some modern motherboards
and disk controllers are equipped with a BIOS that supports more
(typically
four) disk drives. When attempting to access the third, fourth, etc.
drive,
\LILO\ prints a warning message but continues. Unless the BIOS really
supports more than two drives, the system will \emphasize{not} be able
to
boot in that case.\footnote{However, if only ``unimportant'' parts of
the
system are located on the ``high'' drives, some functionality may be
available.}

The cylinder limit is a very common problem with IDE disks. There, the
number of cylinders may already exceed 1024 if the drive has a capacity
of more than 504 MB. Many SCSI driver BIOSes present the disk geometry
in a way that makes the limit occur near 1 GB. Modern disk controllers
may even push the limit up to about 8 GB. All cylinders beyond the
1024th are inaccessible for the BIOS. \LILO\ detects this problem and
aborts the installation (unless the \craw{linear} option is used, see
section \ref{cfgglo}).

Note that large partitions that only partially extend into the
``forbidden
zone'' are still in jeopardy even if they appear to work at first,
because
the file system does not know about the restrictions and may allocate
disk space from the area beyond the 1024th cylinder when installing new
kernels. \LILO\ therefore prints a warning message but continues as long
as no imminent danger exists.

[...]

Lilo should output a warning message. But, as you can see below, it's
not the case.

Supposing Lilo don't really see the problem and don't print a warning,
how can i see where the data block allocated to store my new kernel
image file is (in terms of cylinders...) ?

Is there a command for it (like stat...) ?

One other (stupid ?) question :

Can i remove some files in /boot/ so copying a new kernel image in
/boot/ will allocate the blocks in the good regions (below the 1024
bound) to store it ?

I can't see a solution to my problem, with my configuration(see below).

Please help !

Eric wrote:

> The bootmap may be correct, but since the bios cannot see any discspace
> beyond cylinder 1024,(or lilo since it uses the bios info) you may have
> bad luck. All depends on the actual physical location of your kernel
> image, so a previous image may have booted (out of pure luck being
> allocated below cylinder 1024) but your new kernel isn't located on such
> a place.
> BTW. You can get the new lilo from the web which doesn't suffer from
> this limit.

> Eric

> Pierre Vigneras wrote:

> > You're right :

> > [root@moucheron /boot]# sfdisk -l /dev/sda

> > Disk /dev/sda: 8715 cylinders, 64 heads, 32 sectors/track
> > Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from
> > 0

> >    Device Boot Start     End   #cyls   #blocks   Id  System
> > /dev/sda1          0+    512     513-   525296   82  Linux swap
> > /dev/sda2        513    4513    4001   4097024   83  Linux
> > /dev/sda3       4514    8714    4201   4301824    c  Win95 FAT32 (LBA)
> > /dev/sda4          0       -       0         0    0  Empty
> > [root@moucheron /boot]#

> > But, why can i boot with a ramdisk and not with my new kernel ?

> > Can anyone answer to questions about the /boot/* files (see below...) ?

> > Eric wrote:

> > > Just to make sure: you didn't make the partition where the kernel
> > > resides (possibly in /boot) too large so it crosses the 1024th cylinder?

> > > Eric

> > > Pierre Vigneras wrote:

> > > > Johan Kullstam wrote:

> > > > > Eric <scare.c...@oz.lan> writes:

> > > > > > Henrique Seganfredo wrote:

> > > > > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

> > > > > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > > > > something like that....

> > > > > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > > > > kernels...is that a fact?

> > > > > > you can't have scsi support as a module if you want to boot from a scsi
> > > > > > disc
> > > > > > it must be compiled into your kernel

> > > > > this is not quite true.  you can put the scsi module on an initial
> > > > > ramdisk (initrd).  this is what most distributions do because
> > > > > compiling every possible scsi driver into their kernel would be a bit
> > > > > much.

> > > > > however, i agree that it is a damned good recommendation.  if you can
> > > > > compile yourself a kernel, by all means build the scsi driver into it.

> > > > That's what i did, but i got a
> > > > "kernel panic" too : "unable to mount on /dev/sda2".

> > > > I did compile the scsi drive into the kernel.
> > > > And moreover, i have :

> > > > [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
> > > > Root device /dev/sda2
> > > > [root@moucheron /boot]#

> > > > which is the current root device :

> > > > [root@moucheron /boot]# rdev
> > > > /dev/sda2 /
> > > > [root@moucheron /boot]#

> > > > Running lilo show :

> > > > [root@moucheron /boot]# lilo -v
> > > > LILO version 21, Copyright 1992-1998 Werner Almesberger

> > > > Reading boot sector from /dev/sda
> > > > Merging with /boot/boot.b
> > > > Boot image: /boot/vmlinuz-2.2.12-20smp
> > > > Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> > > > Added linux *
> > > > Boot image: /boot/vmlinuz-2.2.12-20
> > > > Mapping RAM disk /boot/initrd-2.2.12-20.img
> > > > Added linux-up
> > > > Boot image: /boot/vmlinuz-2.2.14smp
> > > > Added new
> > > > /boot/boot.0800 exists - no backup copy made.
> > > > Writing boot sector.
> > > > [root@moucheron /boot]#

> > > > But booting my new kernel is always a kernel panic !
> > > > i don't understand why !
> > > > I suppose the redhat ramdisk as set a strange /boot/map:

> > > > [root@moucheron /boot]# ls -al
> > > > total 10781
> > > > drwxr-xr-x   2 root     root         1024 May 10 09:33 .
> > > > drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
> > > > lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
> > > > System.map 2.2.12-20
> > > > -rw-r--r--   1 root     root       191102 Sep 27  1999
> > > > System.map-2.2.12-20
> > > > -rw-r--r--   1 root     root       182834 Sep 27  1999
> > > > System.map-2.2.12-20BOOT
> > > > -rw-r--r--   1 root     root       202226 Sep 27  1999
> > > > System.map-2.2.12-20smp
> > > > -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
> > > > -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
> > > > -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
> > > > -rw-r--r--   1 root     root       313673 Feb 11 18:26
> > > > initrd-2.2.12-20.img
> > > > -rw-r--r--   1 root     root       314036 Feb 11 18:26
> > > > initrd-2.2.12-20smp.img
> > > > -rw-r--r--   1 root     root       308009 Jul  9  1999
> > > > initrd-2.2.5-15.img
> > > > -rw-r--r--   1 root     root       308488 Jul  9  1999
> > > > initrd-2.2.5-15smp.img
> > > > lrwxrwxrwx   1 root     root           22 Jul 31  1999
> > > > initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
> > > > -rw-r--r--   1 root     root       695162 Jul 31  1999
> > > > kernel-2.2.5-22smp.my
> > > > -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
> > > > -rw-------   1 root     root        30720 May 10 09:33 map
> > > > lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
> > > > module-in o-2.2.12-20
> > > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > > module-info-2.2.12-20
> > > > -rw-r--r--   1 root     root        11773 Sep 27  1999
> > > > module-info-2.2.12-20smp
> > > > -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
> > > > -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
> > > > -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
> > > > vmlinux-2.2.12-20BOOT
> > > > -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
> > > > vmlinux-2.2.12-20smp
> > > > lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
> > > > vmlinuz-2.2.1 -20
> > > > -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
> > > > -rw-r--r--   1 root     root       592397 Sep 27  1999
> > > > vmlinuz-2.2.12-20BOOT
> > > > -rw-r--r--   1 root     root       647807 Sep 27  1999
> > > > vmlinuz-2.2.12-20smp
> > > > -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
> > > > -rw-r--r--   1 root     root       709302 Jul 23  1999
> > > > vmlinuz-2.2.5-15smp.new
> > > > -rw-r--r--   1 root     root       695161 Aug  6  1999
> > > > vmlinuz-2.2.5-22smp.new
> > > > [root@moucheron

...

read more »

  vigneras.vcf
< 1K Download
 
 
 

SCSI devices and SMP kernels

Post by Ben Walk » Sun, 31 Dec 1899 09:00:00


You need to have the SCSI disk driver (sd) as well as the adapter driver
compiled directly into the kernel, not as a module.  You might check to make
sure the SCSI disk driver is indeed compiled into the kernel.
In article <3919169C.DE102...@oz.land>, Eric  <scare.c...@oz.land> wrote:
>Just to make sure: you didn't make the partition where the kernel
>resides (possibly in /boot) too large so it crosses the 1024th cylinder?

>Eric

>Pierre Vigneras wrote:

>> Johan Kullstam wrote:

>> > Eric <scare.c...@oz.lan> writes:

>> > > Henrique Seganfredo wrote:

>> > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

>> > > > I am trying to set up a right out of the box RPM package with a SMP
>> > > > kernel (the same version non SMP is already running)...when I boot, I
>> > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
>> > > > a problem loading the aic7xxx.o module....no, its not a version issue or
>> > > > something like that....

>> > > > ...some dudes told me that I can't use some SCSI drivers with SMP
>> > > > kernels...is that a fact?

>> > > you can't have scsi support as a module if you want to boot from a scsi
>> > > disc
>> > > it must be compiled into your kernel

>> > this is not quite true.  you can put the scsi module on an initial
>> > ramdisk (initrd).  this is what most distributions do because
>> > compiling every possible scsi driver into their kernel would be a bit
>> > much.

>> > however, i agree that it is a damned good recommendation.  if you can
>> > compile yourself a kernel, by all means build the scsi driver into it.

>> That's what i did, but i got a
>> "kernel panic" too : "unable to mount on /dev/sda2".

>> I did compile the scsi drive into the kernel.
>> And moreover, i have :

>> [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
>> Root device /dev/sda2
>> [root@moucheron /boot]#

>> which is the current root device :

>> [root@moucheron /boot]# rdev
>> /dev/sda2 /
>> [root@moucheron /boot]#

>> Running lilo show :

>> [root@moucheron /boot]# lilo -v
>> LILO version 21, Copyright 1992-1998 Werner Almesberger

>> Reading boot sector from /dev/sda
>> Merging with /boot/boot.b
>> Boot image: /boot/vmlinuz-2.2.12-20smp
>> Mapping RAM disk /boot/initrd-2.2.12-20smp.img
>> Added linux *
>> Boot image: /boot/vmlinuz-2.2.12-20
>> Mapping RAM disk /boot/initrd-2.2.12-20.img
>> Added linux-up
>> Boot image: /boot/vmlinuz-2.2.14smp
>> Added new
>> /boot/boot.0800 exists - no backup copy made.
>> Writing boot sector.
>> [root@moucheron /boot]#

>> But booting my new kernel is always a kernel panic !
>> i don't understand why !
>> I suppose the redhat ramdisk as set a strange /boot/map:

>> [root@moucheron /boot]# ls -al
>> total 10781
>> drwxr-xr-x   2 root     root         1024 May 10 09:33 .
>> drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
>> lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
>> System.map 2.2.12-20
>> -rw-r--r--   1 root     root       191102 Sep 27  1999
>> System.map-2.2.12-20
>> -rw-r--r--   1 root     root       182834 Sep 27  1999
>> System.map-2.2.12-20BOOT
>> -rw-r--r--   1 root     root       202226 Sep 27  1999
>> System.map-2.2.12-20smp
>> -rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
>> -rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
>> -rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
>> -rw-r--r--   1 root     root       313673 Feb 11 18:26
>> initrd-2.2.12-20.img
>> -rw-r--r--   1 root     root       314036 Feb 11 18:26
>> initrd-2.2.12-20smp.img
>> -rw-r--r--   1 root     root       308009 Jul  9  1999
>> initrd-2.2.5-15.img
>> -rw-r--r--   1 root     root       308488 Jul  9  1999
>> initrd-2.2.5-15smp.img
>> lrwxrwxrwx   1 root     root           22 Jul 31  1999
>> initrd-2.2.5-22smp.img -  initrd-2.2.5-15smp.img
>> -rw-r--r--   1 root     root       695162 Jul 31  1999
>> kernel-2.2.5-22smp.my
>> -rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
>> -rw-------   1 root     root        30720 May 10 09:33 map
>> lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
>> module-in o-2.2.12-20
>> -rw-r--r--   1 root     root        11773 Sep 27  1999
>> module-info-2.2.12-20
>> -rw-r--r--   1 root     root        11773 Sep 27  1999
>> module-info-2.2.12-20smp
>> -rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
>> -rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
>> -rwxr-xr-x   1 root     root      1469971 Sep 27  1999
>> vmlinux-2.2.12-20BOOT
>> -rwxr-xr-x   1 root     root      1647660 Sep 27  1999
>> vmlinux-2.2.12-20smp
>> lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
>> vmlinuz-2.2.1 -20
>> -rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
>> -rw-r--r--   1 root     root       592397 Sep 27  1999
>> vmlinuz-2.2.12-20BOOT
>> -rw-r--r--   1 root     root       647807 Sep 27  1999
>> vmlinuz-2.2.12-20smp
>> -rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
>> -rw-r--r--   1 root     root       709302 Jul 23  1999
>> vmlinuz-2.2.5-15smp.new
>> -rw-r--r--   1 root     root       695161 Aug  6  1999
>> vmlinuz-2.2.5-22smp.new
>> [root@moucheron /boot]#

>> Can i remove some of this files (System.map*) ?? What are their use (i
>> know ps use it, for its WCHAN field, but is there another use ??) ? What
>> are module-info* files ? Can i remove some of this files ?

>> Here my /etc/lilo.conf :

>> [root@moucheron /boot]# cat /etc/lilo.conf
>> boot=/dev/sda
>> map=/boot/map
>> install=/boot/boot.b
>> prompt
>> timeout=50
>> default=linux

>> image=/boot/vmlinuz-2.2.12-20smp
>>         label=linux
>>         initrd=/boot/initrd-2.2.12-20smp.img
>>         read-only
>>         root=/dev/sda2

>> image=/boot/vmlinuz-2.2.12-20
>>         label=linux-up
>>         initrd=/boot/initrd-2.2.12-20.img
>>         read-only
>>         root=/dev/sda2

>> image=/boot/vmlinuz-2.2.14smp
>>         label=new
>>         read-only
>>         root=/dev/sda2
>>         vga=ask

>> [root@moucheron /boot]#

>> My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
>> describe above).

>> --
>> Pierre Vignras
>> http://dept-info.labri.u-bordeaux.fr/~vigneras/

>> Equipe systmes et objets distribus
>> http://jccf.labri.u-bordeaux.fr/jodo/

>> LaBRI
>> http://dept-info.labri.u-bordeaux.fr/

>>   ------------------------------------------------------------------------

>>                          Name: vigneras.vcf
>>    vigneras.vcf          Type: VCard (text/x-vcard)
>>                      Encoding: 7bit
>>                   Description: Card for Pierre Vigneras

 
 
 

SCSI devices and SMP kernels

Post by David Cazie » Sun, 31 Dec 1899 09:00:00


I think you should add the option "linear" in your lilo.conf to boot from
some scsi disk. (see man page)

> Anybody here knows about the behaviour of SMP kernels with SCSI drivers?
> I am trying to set up a right out of the box RPM package with a SMP
> kernel (the same version non SMP is already running)...when I boot, I
> get "kernel panic" cause the root fs (on sda1) could not be mounted due
> a problem loading the aic7xxx.o module....no, its not a version issue or
> something like that....

> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux
> image=/boot/vmlinuz-2.2.12-20smp
>         label=linux
>         initrd=/boot/initrd-2.2.12-20smp.img
>         read-only
>         root=/dev/sda2

> image=/boot/vmlinuz-2.2.12-20
>         label=linux-up
>         initrd=/boot/initrd-2.2.12-20.img
>         read-only
>         root=/dev/sda2

> image=/boot/vmlinuz-2.2.14smp
>         label=new
>         read-only
>         root=/dev/sda2
>         vga=ask

 
 
 

SCSI devices and SMP kernels

Post by Eric » Sun, 31 Dec 1899 09:00:00



> Thanks very much for your help, really :-).

> Nevertheless, i really don't understand something :
> my version of Lilo is :


> LILO version 21

> Is there a more recent version ?

> Moreover, the lilo doc talked about this 1024 cylinders limits :

<SNIP>

The most recent version from lilo is 21.4.3 (IIRC)
Still, if you use this, your bios must have support for the LBA32 calls
else you will still be out of luck. I don't know of any way you can use
to find the physical location of a file on disc, but you are probably
better of by ensuring that the kernel images never will get written
beyond the 1024th cylinder boundary (ie. if lilo 21.4.3 doesn't work for
you). try making a /boot partition that is entirely below cylinder 1024,
it doesn't have to be large (20 MB is enough) but it will be a working
solution.

another thing you may try is making a bootfloppy, try booting the new
kernel from there, just to make sure the kernel image is ok.

Eric

 
 
 

SCSI devices and SMP kernels

Post by Michael Borgwar » Sun, 31 Dec 1899 09:00:00




Quote:> you). try making a /boot partition that is entirely below cylinder 1024,
> it doesn't have to be large (20 MB is enough) but it will be a working
> solution.

20MB? If you aren't going to be kernel-hacking madly, 5MB is plenty for
/boot!

--
Michael "Brazil" Borgwardt --- Member of #WASHU# and Her would-be guinea-pig.
        Untiring defender of Washu-chan, Asuka-chan and Elektra-chan.
   A Homepage for Elektra: http://www.informatik.tu-muenchen.de/~borgward/
     ANT - Animeclub fuer Deutschland: http://www.anime.no.tomodachi.de/
--------------- Let`s shake the dew off this lily, shall we ? ---------------

 
 
 

SCSI devices and SMP kernels

Post by Johan Kullsta » Sun, 31 Dec 1899 09:00:00





> > you). try making a /boot partition that is entirely below cylinder 1024,
> > it doesn't have to be large (20 MB is enough) but it will be a working
> > solution.

> 20MB? If you aren't going to be kernel-hacking madly, 5MB is plenty for
> /boot!

a 13GB eide drive costs us$130 these days.  that's a penny a
megabyte.  20 cents for 20MB is chump change.

--
johan kullstam l72t00052

 
 
 

SCSI devices and SMP kernels

Post by Juergen Pfan » Sun, 31 Dec 1899 09:00:00






> > > you). try making a /boot partition that is entirely below cylinder 1024,
> > > it doesn't have to be large (20 MB is enough) but it will be a working
> > > solution.

> > 20MB? If you aren't going to be kernel-hacking madly, 5MB is plenty for
> > /boot!

> a 13GB eide drive costs us$130 these days.  that's a penny a
> megabyte.  20 cents for 20MB is chump change.

As most large drives use (in LBA mode) 255 heads/63 sectors logical
mappings, I'd suggest (for partitioning issues) to think in cylinders
of 8 megs each, cause that would be the boundaries of fdisk anyway.
So to me, neither 5 nor 20 MB seems sensible, but 8, 16, or 24,
for example.

Just my 2c

Juergen

 
 
 

1. SCSI devices and SMP kernels

Anybody here knows about the behaviour of SMP kernels with SCSI drivers?

I am trying to set up a right out of the box RPM package with a SMP
kernel (the same version non SMP is already running)...when I boot, I
get "kernel panic" cause the root fs (on sda1) could not be mounted due
a problem loading the aic7xxx.o module....no, its not a version issue or
something like that....

...some dudes told me that I can't use some SCSI drivers with SMP
kernels...is that a fact?

thanks,

--
Henrique Seganfredo (Segao)


computer programmer - hardware geek
guitar - scouting - drawing - AFS student

"Quanto mais aprendo, menos eu sei"
"The more I learn, the less I know"

2. Problem getting my flat screen to work with XFree86

3. Kernel not detecting SCSI devices, but stock kernel DOES...?

4. New Napster Pgm??

5. Device Driver Interrupts on SMP using kernel 2.4

6. alas! another IP masq question

7. Pentium Pro SMP - scsi disks timing out at boot, only with SMP

8. which tool to debug?

9. Kernel 2.4.19 having trouble booting, using a on board SCSI Controller on SMP machine

10. Boot halted during dev mount / fsck process (RH 6.1, SMP kernel, SCSI system)

11. Booting SMP kernel on non-SMP machines?

12. Reproducible SMP kernel deadlock in SCSI generic driver (sg)

13. Anyone aware of known issues with the scsi driver in kernel-smp-2 .4.2-2?