no boot over nfs

[Altera_Forum]

Hello! 

 My configuration worked well with initramfs. Now i like to boot over NFS. I did everything like in "NFSFileSystem" and I can mount the NFS in the linux booted with initramfs. Further I had to enabled in Networking "IP: kernel level autoconfiguration" and Network File Systems "Root file system on NFS" to get the system booting over nfs.  First I had an error like "can not open initial console" because "/dev" was empty. So I created the device nodes defined in "romfs_list".  Now I have the following error:  IP-Config: Complete: device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=255.255.255.255, host=nios2, domain=, nis-domain=(none), bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath= Looking up port of RPC 100003/2 on 192.168.1.2 Looking up port of RPC 100005/1 on 192.168.1.2 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 56k freed (0x176000 - 0x183000) Kernel panic - not syncing: Attempted to kill init!   When I trac the traffic with wireshark, I can see that "rc" is executed and "inittab" (which is empty) is called. After that call the traffic stops followed by an ARP.  can anybody help me?

[Altera_Forum]

Hi! 

 If I add the line "ttyS0:vt100:/bin/sh" to the inittab I get a console and no Kernel panic anymore. But the welcome screen from rc (/etc/motd) is not shown.  When I boot with initramfs, inittab is empty but I still get a console and the welcome screen is shown. I use the normal UART and not the JTAG UART.   Do i have to set the std_out somewhere? Or has anybody an other idea?  thanks for your help!  glattchr

[Altera_Forum]

which console device do you use ? jtag or rs232? 

 In kernel menuconfig, you should select either jtag uart or serial uart for console device (but not both).  Device Drivers ---> Character devices ---> Serial drivers --->  if you use jtag uart (with a USB Blaster cable) on a nios2-terminal, [ ] Nios serial support [*] Altera JTAG UART support [*] Support for console on Altera JTAG UART  if you use serial uart (with a 9-pin RS-232C cable) on a terminal emulator such as minicom or ckermit, [*] Nios serial support [*] Support for console on Nios UART [ ] Altera JTAG UART support  The console device will use /dev/console node.  Yes, you need to create all /dev nodes or copy them from initamfs.  Do you get the shell prompt?

[Altera_Forum]

I tried again nfsroot and updated the NFS wiki page. Please check.

[Altera_Forum]

Hello Hippo 

 Thanks for your help!  I disabled the sysfs support as you told me. I had both UARTs enabled in the Nios, but only the "normal" (not JTAG) in the kernel. After recomiling the Nios with only one UART, I got the "welcome screen" also when booting over NFS. But with the empty inittab, I've got still a kernel panic, with the "ttyS0:vt100:/bin/sh" line, it works.  Do you know if the initramfs does some further initialisation which I don't get when boot over NFS?  best regards  glattchr

[Altera_Forum]

Yes, you should not enable both jtag and uart as "support for console" in kernel config. 

You should choose only one of them. see the wiki, http://nioswiki.jot.com/wikihome/operating...nux/linuxconfig (http://nioswiki.jot.com/wikihome/operatingsystems/%c2%b5clinux/linuxconfig) <div class='quotetop'>QUOTE </div>  --- Quote Start ---  if you use serial uart (with a 9-pin RS-232C cable) on a terminal emulator such as minicom or ckermit, [*] Nios serial support [*] Support for console on Nios UART [ ] Altera JTAG UART support[/b]  --- Quote End ---    Do you have /dev/console ? I uploaded a rootfs which I used for the test. http://nioswiki.jot.com/wikihome/operating...s-nios2.tar.bz2 (http://nioswiki.jot.com/wikihome/operatingsystems/%c2%b5clinux/nfsfilesytem/rootfs-nios2.tar.bz2)  In user config, Core Applications --->  [*] init [*] enable console shell  Then the init will open /dev/console for a shell.  If you do not select "enable console shell " or you do not have /dev/console, then you have to add a terminal to inittab.