PXE boot / NFS

freeindy · 03-04-2008, 04:49 AM

Hi,

I'm crawling slowly to success on booting my linux system (Montavista 4.0.1) to the target hardware.

I've managed now to get a ip address on the target via dhcp server on the hostside: 192.168.0.5.

I have managed to load the kernel (i think):

Code:

Intel(R) Boot Agent FE v4.1.18                                                  
Copyright (C) 1997-2005, Intel Corporation                                      
                                                                                
Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 084)                           
Copyright (C) 1997-2005, Intel Corporation                                      
                                                                                
CLIENT MAC ADDR: 00 A0 A5 5D AD 81  GUID: 00020003 0004 0005 0006 000700080009  
CLIENT IP: 192.168.0.5  MASK: 255.255.255.0  DHCP IP: 192.168.0.254             
GATEWAY IP: 192.168.0.1                                                         
                                                                                
PXELINUX 2.04 2003-04-16  Copyright (C) 1994-2003 H. Peter Anvin                
UNDI data segment at:   0008B1B0                                                
UNDI data segment size: 94B0                                                    
UNDI code segment at:   00084660                                                
UNDI code segment size: 2220                                                    
PXE entry point found (we hope) at 9466:0106                                    
My IP address seems to be C0A80005 192.168.0.5                                  
ip=192.168.0.5:192.168.0.254:192.168.0.1:255.255.255.0                          
TFTP prefix:                                                                    
Trying to load: pxelinux.cfg/C0A80005                                           
Loading vmlinuz-x86-pl1337-x86_pentium4.........................................
...............Ready.

And this is where the trouble is now. It hangs just here. I don't know if it's pxe setting or nfs setting that is causing it. The message from the /var/log/messages on the host side is:

Code:

Mar  4 11:45:14 AccServer kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Down
Mar  4 11:45:52 AccServer kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Mar  4 11:46:31 AccServer dhcpd: DHCPDISCOVER from 00:a0:a5:5d:ad:81 via eth1
Mar  4 11:46:31 AccServer dhcpd: DHCPOFFER on 192.168.0.5 to 00:a0:a5:5d:ad:81 via eth1
Mar  4 11:46:33 AccServer dhcpd: DHCPREQUEST for 192.168.0.5 (192.168.0.254) from 00:a0:a5:5d:ad:81 via eth1
Mar  4 11:46:33 AccServer dhcpd: DHCPACK on 192.168.0.5 to 00:a0:a5:5d:ad:81 via eth1
Mar  4 11:46:33 AccServer xinetd[4798]: START: tftp pid=5363 from=192.168.0.5
Mar  4 11:46:33 AccServer in.tftpd[5364]: tftp: client does not accept options 
Mar  4 11:46:35 AccServer kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Down
Mar  4 11:46:37 AccServer kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Mar  4 11:47:16 AccServer dhcpd: BOOTREQUEST from 00:a0:a5:5d:ad:81 via eth1
Mar  4 11:47:16 AccServer dhcpd: BOOTREPLY for 192.168.0.5 to cb5 (00:a0:a5:5d:ad:81) via eth1
Mar  4 11:47:18 AccServer mountd[4985]: authenticated mount request from 192.168.0.5:800 for /opt/os_images/mv_cge_4.0.1/cge/devkit/x86/pentium4/target (/opt/os_images/mv_cge_4.0.1/cge/devkit/x86/pentium4/target)

Any idea?

Thanks again. I don't know how I would survive without this site. Always appreciated.

Indy

freeindy · 03-04-2008, 07:34 AM

Sorry.

I solved it. It DOESN'T hang. I have the target connected to the serial port and didn't realise that I had to add the kernel parameter console=ttyS0,xxxx to see what actually is going on.

Indy

lsteacke · 03-04-2008, 08:27 AM

Wow, thats quite a catch, how did you manage to figure out you needed that kernel parameter, just curious.

freeindy · 03-06-2008, 04:40 AM

Well, I was googling about it and I saw the console parameter option somewhere. So I thought maybe that's just it. I don't get the boot information. So I pinged the machine and and actually got response. That made me realise that the machine IS up and running, I must be just lacking the information. I also then raised the question to myself: how does the boot procedure know where to send the actual data for the view To tty or ttyS or whatever? What is default?

And voila. a bit of more googling about console parameter and tesing I got it working.

Indy