[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#357065: linux-image-2.6-r4k-ip22 immediately reboots on Indy 200MHz R4400

Hash: SHA1


On 2006-03-15 17:12, Thiemo Seufer wrote:
> Could you retry with the upcoming 2.6.16 which is currently in
> preparation and includes support for mips/ip22? (As found in
> http://lists.debian.org/debian-mips/2006/01/msg00050.html )

I've tried 2.6.16-rc6[1] now, and get the following message at the end
of the kernel boot process:

EXT3-fs: mounted filesystem with ordered date mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 308k freed
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to
 <0>Rebooting in 120 seconds..

That was the clue I needed: I then looked at the partition numbering and
found that the new kernel enumerates numbers partitions differently (my
root partition was /dev/sda5 with 2.4) and assigns numbers that
correspond to those listed by fdisk -l.

But when I try to boot with root=/dev/sda7, activating swap and mounting
of the boot partition doesn't work and also keyboard input is ignored
when I'm dropped to the maintenance prompt.

I'll provide my parition table as printed by fdisk here to make my
comments above clearer:

# fdisk -l /dev/sda

Disk /dev/sda (SGI disk label): 64 heads, 32 sectors, 8748 cylinders
Units = cylinders of 2048 * 512 bytes

- ----- partitions -----
Pt#    Device  Info     Start       End   Sectors  Id  System
 1: /dev/sda1  boot       130      6229  12492800   a  SGI xfs
 2: /dev/sda2  swap         2       129    262144   3  SGI raw
 5: /dev/sda3            6359      6422    131200  83  Linux native
 6: /dev/sda4            6231      6358    262400  82  Linux swap
 7: /dev/sda5            6423      8747   4761600  83  Linux native
 9: /dev/sda6               0         1      4096   0  SGI volhdr
11: /dev/sda7               0      8748  17916240   6  SGI volume
- ----- Bootinfo -----
Bootfile: /unix
- ----- Directory Entries -----
 0: sgilabel   sector    4 size     512
 1: arcboot    sector    5 size   80472
 2: sash       sector  163 size  343040
 3: ide        sector  833 size  343040
 4: arcboot2   sector 1503 size   67392
 5: arcboott   sector 1635 size   67592

It seems from the boot prompt of the 2.6 kernel, that the following
numbers are then used:

sda1 sda2 sda5 sda6 sda7 sda9 sda11

I'm not sure, but this seems to be a good idea, if it wasn't for the
lack of backwards compatibility. So perhaps it would be smart to have
some boot option to switch from one numbering scheme to the other, to
allow for a smooth transition?

Please comment. But with non-working PS/2 keyboard and non-working
/etc/fstab for both kernel version, the 2.6.16 image is pretty worthless
to me at this moment.

I assume that my problems with 2.6.12 where for the same reason, but
that I didn't even notice the root filesystem (which indeed is the boot
partition) was mounted and the kernel rebooted immediately when no init
is found.

Ciao, Thomas Jahns

[1] the following packages are installed
# dpkg -l '*2.6.16*'
linux-image-2.6.16-rc6-r4k-ip22   2.6.15+2.6.16-rc6-0experimental.1
Linux kernel 2.6.16 image on SGI IP22 machines
- -- 
"Computers are good at following instructions,
 but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9
Version: GnuPG v1.4.2.2 (GNU/Linux)


Reply to: