My problem booting the Sun V210 isn't fixed by this.

Previously you said:

> please try latest klibc-utils and libklibc from incoming.debian.org
> or later this evening in unstable, calling update-initramfs -u
> will get those on your initramfs.

but I see:

# update-initramfs -u -k 2.6.15-1-sparc64
/boot/initrd.img-2.6.15-1-sparc64 was been altered.  Cannot update.

I removed the linux-image-2.6.15-1-sparc64 package and reinstalled.
It used mkinitramfs:

  ...
  Running depmod.
  Finding valid ramdisk creators.
  Using mkinitramfs to build the ramdisk.
  ...
  
Booting the result still gives this:

  ...
  SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB)
  SCSI device sda: drive cache: write through               
  SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB)
  SCSI device sda: drive cache: write through               
   sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7   
  sd 0:0:0:0: Attached scsi disk sda      
  hda: ATAPI 24X DVD-ROM drive, 256kB Cache
  Uniform CD-ROM driver Revision: 3.20     
  Done.                               
  Begin: Mounting root file system ...
  Begin: Running /scripts/local-top ...
  Done.
  Begin: Running /scripts/local-premount ...
  Done.
  kjournald starting.  Commit interval 5 seconds
  EXT3-fs: mounted filesystem with ordered data mode.
  Begin: Running /scripts/log-bottom ...             
  Done.
  Done.
  Begin: Running /scripts/init-bottom ...
  Done.
  run-init: statfsKernel panic - not syncing: Attempted to kill init!
   /: Invalid argu ment                                              
  <0>Press Stop-A (L1-A) to return to the boot prom

Using yaird to build initrd, it fails with:

  Checking all file systems...
  fsck 1.37 (21-Mar-2005)
  fsck.ext3: No such file or directory while trying to open /dev/sda1
  /dev/sda1: 
  The superblock could not be read or does not describe a correct ext2
  filesystem.  If the device is valid and it really contains an ext2
  filesystem (and not swap or ufs or something else), then the superblock
  is corrupt, and you might try running e2fsck with an alternate superblock:
      e2fsck -b 8193 <device>
  
I do have the same kernel package booting OK on a Sunblade 100 (which
is IDE only) using yaird.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to