Bug#335852: ltsp-server: Unable to boot sid client with 2.6 kernel

2005-10-27 Thread Vagrant Cascadian
 Package:  ltsp-server
 Version:  0.58debian2
 Severity: important
 
 When building a sid client (ltsp-build-client --dist sid), the client
 finally build successfully, but it is unable to boot.  The client do
 at the moment end up with a 2.6.12 kernel

 
 The client then loads the kernel, and hangs with this error message:
 
   [...]
   TCP: Hash tables configured (established 8192 bind 8192)
   RAMDISK: Couldn't find valid RAM disk image starting at 0.
   VFS: Cannot open root device nfs or unknown-block(0,255)
   Please append a correct root= boot option
   Kernel panic - not syncing: VFS: Unable to mount root fs on
 unknown-block(0,255)
 
 I'm not sure what is wrong, but suspect the kernel is without NFS
 support because it failed to load the initrd file.

i suspect this is a duplicate of a bug against initrd-netboot-tools: 

#335254: initrd-netboot-tools: incompatible with linux-image-2.6.12-1-386

live well,
  vagrant


signature.asc
Description: Digital signature


Bug#335852: ltsp-server: Unable to boot sid client with 2.6 kernel

2005-10-26 Thread Petter Reinholdtsen

Package:  ltsp-server
Version:  0.58debian2
Severity: important

When building a sid client (ltsp-build-client --dist sid), the client
finally build successfully, but it is unable to boot.  The client do
at the moment end up with a 2.6.12 kernel, and give an error when
booting using qemu.  I start qemu like this, making a dummy disk to
get qemu in sarge to start at all:

  createdisk /tmp/hda 16
  qemu -kernel /opt/ltsp/i386/boot/vmlinuz-2.6.12-1-386 \
-initrd /opt/ltsp/i386/boot/initrd.img-2.6.12-1-386 \
-user-net -hda /tmp/hda \
-append ip=dhcp root=/dev/nfs nfsroot=/opt/ltsp/i386/

The client then loads the kernel, and hangs with this error message:

  [...]
  TCP: Hash tables configured (established 8192 bind 8192)
  RAMDISK: Couldn't find valid RAM disk image starting at 0.
  VFS: Cannot open root device nfs or unknown-block(0,255)
  Please append a correct root= boot option
  Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,255)

I'm not sure what is wrong, but suspect the kernel is without NFS
support because it failed to load the initrd file.


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