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

Re: Bug#717511: Kernel does not start up on Pegasos-2



Hello, Karoly.

21 июля 2013 г., 22:34:12, you wrote:


> Just for the record, I've installed Wheezy successfully on two Pegasos
> IIs, one is a rev 2B1 board, which was installed from scratch, and worked
> without major glitches, apart from the fact that the installer required an
> installation to MBR partitioned disks, because with RDB disks it said
> "Fatal error: Out of memory", when it tried to create the main partition
> on an 80GB ATA disk. :)

 I am sorry for the false alarm...
 After  posting  this message i decided to reinstall the system...
 The  story  begins  with  the  fact  that until now i used single EXT
partition  for  Linux. In the far past it used to be EXT2, then when i
upgraded to Etch it became EXT3. There was no separate /boot partition
because Pegasos firmware was perfectly able to read that partition.
 But  now,  first  i  decided  to  use  EXT4  (yes,  i performed clean
reinstall).  Firmware  did  not  know  what is EXT4 and could not read
/boot directory. Fault.
 I  reinstalled  again,  this  time i used EXT3. But... Hah! This EXT3
appears  to  be  somehow incompatible with my older EXT3. The firmware
was not able to read it.
 But,  fortunately,  MorphOS  was able to. I quickly extracted vmlinux
file  from  /boot directory, copied it to SFS partition (where MorphOS
lives), and booted it from there.
 But this time i decided to do everything in a good way. I cut a small
120MB  piece from my old Linux partition and decided to use it as EXT2
/boot.   The   rest   became   EXT4   again.  I  reinstalled  in  this
configuration,  and...  In  /boot  i saw two images. One had "vmlinux"
name  and  another  had  "vmlinuz"  name. I ran vmlinuz and everything
worked fine! :)
 So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
 So,  we  can  close  this,  probably with a notification to Installer
guys.

-- 
Kind regards,
 Pavel                          mailto:pavel_fedin@mail.ru


Reply to: