thr3ads.net - Syslinux - [syslinux] pxe linux [Apr 2004]

If this information is useful, please help other people find it:
Share via:

Manu Abraham

2004-Apr-16 08:31 UTC

[syslinux] pxe linux

Hi,
		I have setup pxelinux like this,

default linux
    label=linux
    kernel linux
    append initrd=rootfs.img
    ipappend 1

I have my dhcpd.conf like this,

	allow booting;
	allow bootp;

	group{
        	filename "pxelinux.cfg/pxelinux.0";
        	host deploy
       		{
            		next-server 192.168.1.254;
            		hardware ethernet 00:0E:A6:22:28:21;
            		fixed-address 192.168.1.235;
        	}
	}



My client is on a 3C940 network adapter LanOnMotherboard. When BIOS is set to 
bootstrap using PXE,

	Searches for a DHCP server ------ works fine,
	Looks for a TFTP server ---------- works fine,
	Downloads PXElinux -------- works fine,
	Downloads Kernel ----------- works fine,

after that
		VFS: Cannot open root device "" or 03:02
		Please append a correct "root=" boot option...
		Kernel Panic: VFS: unable to mount root fs on 03:02

My rootfs.img (uncompressed) is 64M big with the kernel options changed to 
accept a 64MB ramdisk. Compressed it is around 11M. 

	My /etc/fstab contains 
	/dev/ram0 / ext2 defaults
	/proc /proc proc defaults


In my /var/log/messages i notice a following line...

	Apr 15 17:39:27 zeus in.tftpd[3110]: tftp: client does not accept options


	Is there something that i'm doing wrong ? Could somebody help me out ?

Regards,
Manu

Manu Abraham

2004-Apr-19 05:13 UTC

head link

[syslinux] pxe linux

Hi,
		I have setup pxelinux like this,

default linux
    label=linux
    kernel linux
    append initrd=rootfs.img
    ipappend 1

I have my dhcpd.conf like this,

	allow booting;
	allow bootp;

	group{
        	filename "pxelinux.cfg/pxelinux.0";
        	host deploy
       		{
            		next-server 192.168.1.254;
            		hardware ethernet 00:0E:A6:22:28:21;
            		fixed-address 192.168.1.235;
        	}
	}



My client is on a 3C940 network adapter LanOnMotherboard. When BIOS is set to 
bootstrap using PXE,

	Searches for a DHCP server ------ works fine,
	Looks for a TFTP server ---------- works fine,
	Downloads PXElinux -------- works fine,
	Downloads Kernel ----------- works fine,

after that
		VFS: Cannot open root device "" or 03:02
		Please append a correct "root=" boot option...
		Kernel Panic: VFS: unable to mount root fs on 03:02

My rootfs.img (uncompressed) is 64M big with the kernel options changed to 
accept a 64MB ramdisk. Compressed it is around 11M. 

	My /etc/fstab contains 
	/dev/ram0 / ext2 defaults
	/proc /proc proc defaults


In my /var/log/messages i notice a following line...

	Apr 15 17:39:27 zeus in.tftpd[3110]: tftp: client does not accept options


	Is there something that i'm doing wrong ? Could somebody help me out ?

Regards,
Manu

Manu Abraham

2004-Apr-20 08:54 UTC

head link

[syslinux] pxe linux

Hi,
		I found no reply to my query on the list, hence resneding it. Is any body 
else having this problem ? I have setup pxelinux like this,

default linux
    label=linux
    kernel linux
    append initrd=rootfs.img
    ipappend 1

I have my dhcpd.conf like this,

	allow booting;
	allow bootp;

	group{
        	filename "pxelinux.cfg/pxelinux.0";
        	host deploy
       		{
            		next-server 192.168.1.254;
            		hardware ethernet 00:0E:A6:22:28:21;
            		fixed-address 192.168.1.235;
        	}
	}



My client is on a 3C940 network adapter LanOnMotherboard. When BIOS is set to 
bootstrap using PXE,

	Searches for a DHCP server ------ works fine,
	Looks for a TFTP server ---------- works fine,
	Downloads PXElinux -------- works fine,
	Downloads Kernel ----------- works fine,

after that
		VFS: Cannot open root device "" or 03:02
		Please append a correct "root=" boot option...
		Kernel Panic: VFS: unable to mount root fs on 03:02

My rootfs.img (uncompressed) is 64M big with the kernel options changed to 
accept a 64MB ramdisk. Compressed it is around 11M. 

	My /etc/fstab contains 
	/dev/ram0 / ext2 defaults
	/proc /proc proc defaults


In my /var/log/messages i notice a following line...

	Apr 15 17:39:27 zeus in.tftpd[3110]: tftp: client does not accept options


	Is there something that i'm doing wrong ? Could somebody help me out ?

Regards,
Manu

Baurzhan Ismagulov

2004-Apr-20 09:45 UTC

head link

[syslinux] pxe linux

Hello, Manu!

On Tue, Apr 20, 2004 at 12:54:35PM +0400, Manu Abraham
wrote:> 		VFS: Cannot open root device "" or 03:02
> 		Please append a correct "root=" boot option...
> 		Kernel Panic: VFS: unable to mount root fs on 03:02
Perhaps "append initrd=rootfs.img root=/dev/ram0" in pxelinux config?

With kind regards,
Baurjan.

Josef Siemes

2004-Apr-20 16:31 UTC

head link

[syslinux] pxe linux

Hi,

manu at kromtek.com schrieb am 16.04.04 14:21:13:> 		I have setup pxelinux like this,
> 
> default linux
>     label=linux
>     kernel linux
>     append initrd=rootfs.img
>     ipappend 1
Remove the '=' in the label-line. Spaces divide commands from arguments.
(but leave
it in at the initrd=rootfs, this is parsed by the kernel ...).

Regards,

Josef
_____________________________________________________________________
Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P!
Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157

Josef Siemes

2004-Apr-20 17:17 UTC

head link

[syslinux] pxe linux

Hi,

manu at kromtek.com schrieb am 20.04.04 19:10:09:> 	My configuration now contains only so much. But still what i get on the 
> client is the same command line BOOT_IMAGE=linux auto
> 
> #Pxe configuration
> 
> kernel linux
> append initrd=rootfs.img ramdisk_size=65536 root=/dev/ram0
You are still missing the 'label linux' line. So in total this would be:

-- snip
#Pxe configuration
label linux
kernel linux
append initrd=rootfs.img ramdisk_size=65536 root=/dev/ram0
-- snip

Regards,

Josef
_____________________________________________________________________
Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P!
Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157

Manu Abraham

2004-Apr-21 06:23 UTC

head link

[syslinux] pxe linux

Hello Josef,
	As per the suggestion i made the changes to /tftpboot/pxelinux.cfg/default 
like this

#Pxe configuration

default tux
label tux
kernel linux
append initrd=rootfs.img ramdisk_size=65536 root=/dev/ram0


	Still i get the same Kernel command line: BOOT_IMAGE=linux auto. No changes 
in that. I don't know where my append seems to be going...


Regards,
Manu


> manu at kromtek.com schrieb am 20.04.04 19:46:48:
> > On Tuesday 20 Apr 2004 9:17 pm, you wrote:
> > > manu at kromtek.com schrieb am 20.04.04 19:10:09:
> > > > 	My configuration now contains only so much. But still what
i get on
> > > > the client is the same command line BOOT_IMAGE=linux auto
> > > >
> > > > #Pxe configuration
> > > >
> > > > kernel linux
> > > > append initrd=rootfs.img ramdisk_size=65536 root=/dev/ram0
> > >
> > > You are still missing the 'label linux' line. So in total
this would
> > > be:
> > >
> > > -- snip
> > > #Pxe configuration
> > > label linux
> > > kernel linux
> > > append initrd=rootfs.img ramdisk_size=65536 root=/dev/ram0
> > > -- snip
> >
> > 	With the label line, there is no difference, whether it is there or
not,
> > i get the same error.
>
> Test it again. Without this you won't get any kernel command line, and
the
> default for pxelinux is to load kernel 'linux' without any
arguments.
> That's what you see here (the BOOT_IMAGE is added by pxelinux itself
btw.).
>
> Perhaps you should really switch over to:
>
> - snip
> default tux
> label tux
> kernel linux
> append <insert appends>
> - snip
>
> or even rename your kernel to something more useful (eg. tux.img). Seems
> you have problems with the automagic file selection pxelinux does, and with
> this you wouldn't have problems (or: Get warned/errored by pxelinux:
file
> not found etc.pp.).
>
> Regards,
>
> Josef
> _______________________________________________________________________
> ... and the winner is... WEB.DE FreeMail! - Deutschlands beste E-Mail
> ist zum 39. Mal Testsieger (PC Praxis 03/04) http://f.web.de/?mc=021191

Baurzhan Ismagulov

2004-Apr-21 08:09 UTC

head link

[syslinux] pxe linux

On Tue, Apr 20, 2004 at 09:00:05PM +0400, Manu Abraham
wrote:> 	My configuration now contains only so much. But still what i get on the 
> client is the same command line BOOT_IMAGE=linux auto
No idea. I would try using tcpdump to see what is going on in general.
Specifically, which config file gets loaded by the client.


Besides, what does pxelinux say? On my system, I see the following
messages:

Broadcom UNDI PXE-2.1 (build 082) v6.2.11
Copyright (C) 2000-2003 Broadcom Corporation
Copyright (C) 1997-2000 Intel Corporation
All rights reserved.

Intel Base-Code, PXE-2.1 (build 083)
Copyright (C) 1997-2001, Intel Corporation

CLIENT MAC ADDR: 00 E0 81 51 D9 2B  GUID: 00020003-0004-0005-0006-000700080009
CLIENT IP: 192.168.0.101  MASK: 255.255.255.0  DHCP IP: 192.168.0.10

PXELINUX 2.06 0x3f46af85  Copyright (C) 1994-2003 H. Peter Anvin
UNDI data segment at:   000948C0
UNDI data segment size: 4C50
UNDI code segment at:   00099510
UNDI code segment size: 4804
PXE entry point found (we hope) at 9951:00D6
PXELINUX 2.06 0x3f46af85  Copyright (C) 1994-2003 H. Peter Anvin
boot:
Loading vmlinuz-2.4.21-186-smp.........................
Loading
rootfs.ext2.gz......................................................................................................................................................................................................................
Ready.
ok
Bootdata ok (command line is initrd=rootfs.ext2.gz ramdisk_size=65536
root=/dev/ram0 console=tty0 console=ttyS0,115200
BOOT_IMAGE=vmlinuz-2.4.21-186-smp auto)
Linux version 2.4.21-186-smp (root at x86_64.suse.de) (gcc version 3.2.2 (SuSE
Linux)) #1 SMP Mon Feb 2 17:10:45 UTC 2004
BIOS-provided physical RAM map:

Which pxelinux version are you using? Do you see rootfs.img loaded?


With kind regards,
Baurjan.

Seemingly Similar Threads

Search for more seemingly similar threads

Syslinux - Apr 2004 - pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

[syslinux] pxe linux

Seemingly Similar Threads