Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: bbmak on October 23, 2011, 08:18:21 PM
-
Noob to TC, and my laptop has no usb boot and optical drive. All I can do is PXE boot. Can somebody upload the 2 patched files of TC 4 ?
-
You don't need any patched files. Just read the wiki.
-
You don't need any patched files. Just read the wiki.
wiki:netbooting
[quoteIf you are running TC or MC prior to Version 2.5 you will need to patch two files in tinycore.gz or microcore.gz.][/quote]
So if 2.5 prior release, I have to patch; however, 2.5 after, I don't have to do anything to the files?
-
Hi bbmak
That's correct. Current release is 4.0.2.
-
Hi bbmak
That's correct. Current release is 4.0.2.
thank you guys.
-
I got TC 4.2 boot, but right after the boot message, my laptop screen goes blank, nothing show up, but a "-" blinking. Anybody knows why?
-
Hi bbmak
While I can't help you with PXE, I can offer some advice. When asking a question, you should provide
some information relating to your problem. What you did to set up the server you are booting
from. Config file? Boot codes used? In order for someone to help you they will need to know what
you did.
-
Hi bbmak
While I can't help you with PXE, I can offer some advice. When asking a question, you should provide
some information relating to your problem. What you did to set up the server you are booting
from. Config file? Boot codes used? In order for someone to help you they will need to know what
you did.
I am booting from a Windows 2003 RIS server.
/i386/templates/pxelinux.0
/i386/templates/pxelinux.sif
/i386/templates/boot/tinycore.gz
/i386/templates/boot/vmlinuz
/i386/templates/pxelinux.cfg/default <-isolinux.cfg rename from default. I didn't modify the file.
I can see TC is booting b/c I see the boot message for like 3 seconds. However, after it boots, nothing show up, except a '-' blinking.
I try to jump to CLI by pressing CTRL+ALT+F1-F7. However, CLI does not show up.
=====================================================
Update:
I try to boot it with vmware. it works. it boots up okay. I guess it is my graphic card problem. :(
any help how to modify the isolinux.cfg file to make it to work?
-
Hi bbmak
See if CTRL+ALT+Backspace gives you a CLI.
You can also search the forum for blinking cursor
-
Update:
I try to boot it with vmware. it works. it boots up okay. I guess it is my graphic card problem. :(
any help how to modify the isolinux.cfg file to make it to work?
[/quote]
hi bbmak,
I think you should append this boot option 'xsetup' to your isolinux.cfg just right after the kernel /vmlinuz.
I hope this would help.
BTW, what did you use in your PXE booting? I'm also trying to boot from the network here. I'm using Etherboot
because my network card is not capable of booting through the network. I could see that my client computer receives an ip add. but probably it couldn't find my kernel so it timed out.
Would you mind posting you're 'default.cfg'? i'll just compare it to mine?
thanks in advance,
Ruel
-
And, oh. BTW, i'm trying to use tc-terminal-server here.
-
Hi all,
A directory /netboot was automatically generated when i fired up terminal server.
/netboot
pxelinux.0
pxelinux.0y
pxelinux.cfg/
default
tinycore.gz
udhcpd.conf
vmlinuz
default (automatically generated no change is done)
DEFAULT tinycore
TIMEOUT 300
LABEL tinycore
KERNEL vmlinuz
APPEND quiet initrd=tinycore.gz
udhcpd.conf (automatically generated)
# The start and end of the IP lease block
start 192.168.0.30
end 192.168.0.60
# The interface that udhcpd will use
interface eth0
opt dns 212.119.64.3
option subnet 255.255.255.0
opt router 192.168.1.1
option lease 864000 # 10 days of seconds
option tftp 198.9.1.111
option bootfile /netboot/pxelinux.0
Here is the output from my client computer using Etherboot.
net0:00:50:22:40:1a:4d on PCI00:0d.0 (open)
[linkup, TX:0 TX:00 RX:0 RXE:0
DHCP (net0 00:50:22:40:1a:4d)...ok
net0:192.168.0.30/255.255.255.0 gw 192.168.1.1
Booting from filename "/netboot/pxelinux.0"
ftp://0.0.0.0//netboot/pxelinux.0..............connection timed out(0x4c126035)
no more network devices
gpxe>
could anybody tell me what is wrong here? I'm still trying to learn networking specially network booting.
ruel
-
See how the server it uses is 0.0.0.0?
That is a bug in gpxe, I think I filed it over two years ago when it was still called etherboot.
IIRC the DHCP spec has two options for the tftp server, we default to one that the spec says should be preferred over the other.
I don't recall what the other option was called, but if you put the tftp server with that option, gpxe should work.
-
hi bbmak,
I think you should append this boot option 'xsetup' to your isolinux.cfg just right after the kernel /vmlinuz.
I hope this would help.
BTW, what did you use in your PXE booting? I'm also trying to boot from the network here. I'm using Etherboot
because my network card is not capable of booting through the network. I could see that my client computer receives an ip add. but probably it couldn't find my kernel so it timed out.
Would you mind posting you're 'default.cfg'? i'll just compare it to mine?
thanks in advance,
Ruel
My Laptop is Portege 2000
@ru60hz
I am booting from lan(tftp from Windows RIS).
For the default.cfg, I just rename the isolinux.cfg -> default. I didn't change anything inside. Regarding to your timeout, I think it due to your tinycore.gz & vmlinuz path from the pxelinux.cfg/default file. It points to /boot/tinycore.gz & /boot/vmlinuz. You need to add a directory in your /netboot folder or edit the path of the cfg file.
/netboot/boot/tinycore.gz
/netboot/boot/vmlinuz.
Yes, I'll post my default file later. I am unable to access my server box now.
Update:
==========================
Yes I just got myself to the CLI, and I am trying to change the vga mode. I use the 'tinycore vga=ask' command, but I am still unsure which mode am I in. :(
Update: For ru60hz, here is my pxelinux.cfg/default file, I didn't change anything.
==========================
display boot.msg
default tinycore
label tinycore
kernel /boot/vmlinuz
append initrd=/boot/tinycore.gz quiet
label tc
kernel /boot/vmlinuz
append initrd=/boot/tinycore.gz quiet
implicit 0
prompt 1
timeout 300
F1 boot.msg
F2 f2
F3 f3
F4 f4
=================================
-
See how the server it uses is 0.0.0.0?
That is a bug in gpxe, I think I filed it over two years ago when it was still called etherboot.
IIRC the DHCP spec has two options for the tftp server, we default to one that the spec says should be preferred over the other.
I don't recall what the other option was called, but if you put the tftp server with that option, gpxe should work.
Yes, i notice that also. what i did try is to change it 192.168.1.111 on ethrboot config but no chance. Could you recommend floppy boot image i can use to boot from tc-terminal-server? I read somewhre that grub2 could network boot but i could'nt remember.
My Laptop is Portege 2000
@ru60hz
I am booting from lan(tftp from Windows RIS).
For the default.cfg, I just rename the isolinux.cfg -> default. I didn't change anything inside. Regarding to your timeout, I think it due to your tinycore.gz & vmlinuz path from the pxelinux.cfg/default file. It points to /boot/tinycore.gz & /boot/vmlinuz. You need to add a directory in your /netboot folder or edit the path of the cfg file.
/netboot/boot/tinycore.gz
/netboot/boot/vmlinuz.
Yes, I'll post my default file later. I am unable to access my server box now.
Update:
==========================
Yes I just got myself to the CLI, and I am trying to change the vga mode. I use the 'tinycore vga=ask' command, but I am still unsure which mode am I in. :(
thanks,
i will try that.
i'm glad you made it to the CLI.
-
Once you get to the gpxe shell, you should be able to continue manually. I'm afraid I can't help with the exact commands. I don't know of any floppy images either.
-
I was assigned to Yanbu for 3 days but before I left Jeddah, I got the opportunity to test
a laptop capable of pxe booting. Tried it to boot from tiny core terminal server but it didn't
boot also, using direct lan connection.
tiny core terminal server output
tftpd:can't open file
tftpd:can't open file
tftpd:can't open file
So, to check if the said laptop is really working, I setup up a tftp server on windows xp using
tftpd32. copy vmlinuz and tinycore.gz on it's boot directory like this;
D:\pxeserver\
tftproot\
boot\
menu.c32
pxelinux.0
pxelinux.cfg\
default
tinycore.gz
vmlinuz
And it work! I was able to boot tiny core from windows xp using pxe boot laptop.
-
By the way, I use crossover (Cross crimped RJ45) cable on the said test.
And also, here is what i did on tiny core terminal server;
Boot device?/dev/sda2
cp:can't stat /mnt/sda2/bzimage: no such file or directory
So, I copied vmlinuz manually to /netboot/boot
First ip? 192.168.0.30
Last ip? 192.168.0.35
Netcard to use? eth0
Dns Server?
Subnet of shared ip's? 255.255.255.0
Gateway to share?
Any additonal options?
Please leave this terminal open
I just want to know if this is all that needs to be done in setting up a
tc terminal server.
-
Hi ru60hz
I think this thread may have some helpful information:
http://forum.tinycorelinux.net/index.php/topic,8049.msg43254.html#msg43254 (http://forum.tinycorelinux.net/index.php/topic,8049.msg43254.html#msg43254)
-
We're aware that the script had the older kernel name. 4.1rc1 contains a fix.
-
We're aware that the script had the older kernel name. 4.1rc1 contains a fix.
Upgraded to 4.1rc1.
Hi ru60hz
I think this thread may have some helpful information:
http://forum.tinycorelinux.net/index.php/topic,8049.msg43254.html#msg43254 (http://forum.tinycorelinux.net/index.php/topic,8049.msg43254.html#msg43254)
Thanks,
'option bootfile //netboot/pxelinux.0"
works for me.
and this one also.
start 10.0.2.2
end 10.0.2.50
lease_file /netboot/leases
boot_file /netboot/pxelinux.0
interface eth1
option subnet 255.255.255.0
option lease 864000
option tftp 10.0.2.1
It gives me an idea, i'll have to go back to
etherboot diskette because i don't own this laptop.
i'm planning to use my pentium II as a terminal.
again thanks.
Ruel