I just bought an ASUS AT3IONT-I motherboard. This is a Mini-ITX ion board with a Realtek NIC.
I am trying to boot it using NFS. Here is my pxelinux config file:
APPEND ro root=/dev/nfs ip=dhcp nfsroot=192.168.1.2:/export/services/minimyth
The same config file, NFS server, etc boots another front end so I am sure they are working.
When it tries to boot I get the following error:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Pid: 1, comm: swapper Not tainted 18.104.22.168 #1
[<c12d6694>] ? panic+0x4d/0x130
[<c1402ab0>] ? mount_block_root+0x159/0x16d
[<c1402c30>] ? mount_root+0xa7/0xd6
[<c1402d9c>] ? prepare_namespace+0x13d/0x163
[<c140282f>] ? kernel_init+0x174/0x17f
[<c14026bb>] ? kernel_init+0x0/0x17f
[<c1002b56>] ? kernel_thread_helper+0x6/0x10
From looking at the mailing wiki, it looks like this could be a problem of not having a working network driver for this NIC.
Booting Fedora rescue, I can see the PCIID is 10ec:8168 if that helps.
Any suggestions? The ram_disk entry doesn't seem applicable since that is only for machines booting with a ram disk.
If you do a RAM root file system boot rather than a NFS root file system boot, then does it work?
I have never used the ram version. I have always done NFS.
booting with ram does seem to work. I wonder why NFS doesn't.
It could be that I broke something in the NFS kernel settings. I will see whether or not booting an NFS root file system works for me.
I am booting b3 on my other frontend using NFS just fine if that helps at all.
There is good news and bad news.
The good news is b4 now boots just fine ( to a point ) on this motherboard. I am not sure if you modified anything for this issue in b4.
The bad news is NFS mounting of other shares is not working, but I will start a new thread for that.