On Mon, Apr 18, 2005 at 02:53:32AM -0700, Steve Langasek wrote: > On Mon, Apr 18, 2005 at 11:49:04AM +0200, Peter 'p2' De Schrijver wrote: > > On Sun, Apr 17, 2005 at 06:28:01PM -0700, Steve Langasek wrote: > > > On Mon, Apr 18, 2005 at 03:09:53AM +0200, Peter De Schrijver wrote: > > > > Debian-installer-version: 2005/04/17 rc3 netboot image > > > > uname -a: Linux pisco 2.4.27-2-generic #1 Sat Apr 9 19:43:25 UTC 2005 alpha GNU/Linux > > > > Date: Mon Apr 18 02:59:19 CEST 2005 > > > > Method: netboot from local server. installation from ftp.belnet.be > > > > > 1) Initial boot only worked after I changed the ramdisk size by giving > > > > the ramdisk_size parameter. The image could be configured to give this > > > > parameter automagically. > > > > What was the boot commandline that failed, and what did you set ramdisk_size > > > to in order to get it booting? > > > Ok. I found the problem. The XP1000 SRM by default passes -fl a to the > > boot command which causes aboot to replace the kernel flags by the > > letter 'a'. This is overwrites the default commandline in the netboot > > image :( Workaround is to set boot_osflags to "" before doing a bootp. > > Yep, well-known bug #271180. > It's more subtle then that. aboot treats the contents of booted_osflags differently depending on how it was loaded. When netbooting the contents is passed as kernel parameter, except if it is a single 'i', which causes it to ask for the kernel commandline on the console. When booting from disk or cdrom, the contents is used by aboot to select the aboot.conf entry to boot. (it's somewhat more complicated then what I describe here, look at get_aboot_options in disk.c for full details). A good solution might be to make netboot behaviour similar to disk boot behaviour by including a single entry aboot.conf in the netboot image. Cheers, Peter (p2).
Attachment:
signature.asc
Description: Digital signature