Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: poloxyt on March 21, 2010, 06:18:56 AM
-
Hi everyone
I've got problem with booting over lan. I followed:
http://wiki.tinycorelinux.com/tiki-index.php?page=Netbooting
When i try pxe boot my client show:
(http://img40.imageshack.us/img40/4878/1ed.th.jpg) (http://img40.imageshack.us/i/1ed.jpg/)
Its look like missing bzImage, but this file is in dir. When i typed monualy: bzImage the system begin load, when this come up:
(http://img519.imageshack.us/img519/8016/2ed.th.jpg) (http://img519.imageshack.us/i/2ed.jpg/)
I see nfs mount problem
I'm using ubuntu 9 .10 for server and Tiny Core 2.9 for client
If anyone can help - I'm waiting :D
-
What's your pxelinux.cfg/default config file? Looks like you don't have one, or it isn't found.
Here's what a TC host would have:
DEFAULT tinycore
TIMEOUT 300
LABEL tinycore
KERNEL bzImage
APPEND quiet initrd=tinycore.gz
-
like that in link above:
label ws1
MENU LABEL WS1
kernel /nfs/ws1/bzImage
append initrd=/nfs/ws1/tinycore.gz nfsmount=192.168.1.3:/tftpboot/nfs/ws1 tcplist=192.168.1.3:/nfs/ws1/nfs.list tce=nfs/tce
bzImage and tinycore.gz are in /nfs/ws1/ and also in /tftpboot.
When i change "default" to your version i have the same resultat ;/ my tftpd doesn't share that file
-
Anything in your server logs?
-
nth suspect. I think it could be problem with tftp serv. Later i'll try reinstall it and start from a begining :P
-
If your tftp server is configured with /tftpboot as base, the files should be in
/tftpboot/nfs/ws1/
-
I've got files in both directions /tftpboot and /tftpboot/nfs/ws1/
-
My /tftpboot contain:
pxelinux.0
bzImage - copied diretcly from live boot cd
tinycore.gz - copied diretcly from live boot cd
pxelinux.cfg/default
default now contain:
label ws1
kernel bzImage
append initrd=tinycore.gz
And even with this settings i have the same issue as first. My tftp have to work fine becouse it download pxelinux.0. Any idea?
-
Is it really "default" or "deflaut"?
-
At last!!! :P I changed default:
DISPLAY boot.txt
Default ws1
prompt 1
timeout 10
label ws1
kernel bzImage
append initrd=tinycore.gz,nfs-utils.cpio.gz nfsmount=192.168.1.3:/nfsroot tce=/mnt/nfs/
I dont know why it work but it WORK :P
-
I have another question. It is posible to boot multiple hosts with one pxe server? If I boot eg 2-3 hosts there will be problem witch common filesystem? If I can - HOW? :P
-
Sure, it shouldn't matter how many hosts you netboot. The extensions are mounted readonly.
No changes required.
-
You can also have config file per machine with separate nfs shares.
This allows for different extensions being installed on each workstation.
-
Wouldn't having separate lists on the same NFS share have the same effect?
-
The NFS shares work just like drives.
You can use App Browser to install applications.
You can edit the onboot.lst.
You can run backup to save configuration changes.
Using the same nfs share for multiple workstations is not a good idea.
-
I would like run something like this:
Four computers:
1. 192.168.1.3 server
2. 192.168.1.5 host1
3. 192.168.1.6 host2
4. 192.168.1.7 host3
And each of it should have another filesystem or even another system to boot(tinycore and microcore).
How should I configure my tftp and nfs to do it?
-
Create a PXE config file for each machine, specifying a separate nfs share for each.
http://forum.tinycorelinux.net/index.php?topic=3941.msg20627#msg20627
-
As you said:
The config file is looked for in this order:
1. GUID
2. 01-AA-BB-CC-DD-EE-FF ( MAC address )
3. 89ABCDEF ( IP address in HEX )
4. 89ABCDE ( Start dropping Nybbles )
5. 89ABCD
6. 89ABC
7. 89AB
8. 89A
9. 89
10. 8
11. default
If my hos1 has mac adress 11:00:00:00:00:00:11
If my hos2 has mac adress 22:00:00:00:00:00:22
If my hos3 has mac adress 33:00:00:00:00:00:33
Om my server in tftpboot/pxelinux.cfg/ should i have thhat files:
11-00-00-00-00-00-11
22-00-00-00-00-00-22
33-00-00-00-00-00-33
and that files should be like "default" but for direct host?
-
01- Followed by the 6 hex bytes of your mac address.
Default is the config file used if it finds no match as detailed above.
You can test this almost as fast as you can ask.