Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: ahhl on December 26, 2009, 06:32:19 AM
-
hi
i am new in TCB. Stumbleupon brought me to here. previously i am tring slax. unfortunately does'nt work with my laptop. only manage to boot to text mode. trying XWindows does'nt work
my laptop Toshiba Satellite 1800 using Trident
now i want to try TCL. unfortunately i got stuck too.
ok
i have partition my hard disk into 2. one with XP (C: drive) and one with FAT32 (D" Drive) ready for Slax previously now i've cleanup and use for TCL.
i use unetbootin and install TCL to USB. (my laptop cannot boot from USB and i do not want to waste my CD by burning TCL to it). copy the whole content of USB to D:. ( i do this for Slax too)
using this thread to dual boot
http://forum.tinycorelinux.net/index.php?topic=459.0
my menu.lst content
#color black/cyan yellow/cyan
color cyan/blue white/blue
#timeout 30
#default /default
title winxp
find --set-root /ntldrxp
chainloader /ntldrxp
title TCL
root=(hd0,4)
kernel /boot/bzImage tinycore max_loop=255 tce=hda1 restore=hda1 laptop syslog
initrd /boot/tinycore.gz
boot
i got an error on mounting hda1. it keep saying
mount: mounting /dev/hda1 on mnt/hda1 failed: No such device
unable to mount device hda1
....
TCL detecting my pcmcia
....
then it halt with this message
....
pcmcia_socket pcmcia_socket0: cs : IO port probe 0xa00-0xaff: clean
Marking TSC unstable due to TSC halt in idle.
anyone can help ... ??? :'(
-
Are you sure that the partition (hd0,4) corresponds with hda1? Because it is probably wrong. If you have only 2 partitions, then it is probably (hd0,1) which corresponds to hda2.
Try booting without any boot codes that specify hda1, just delete them. Then look in /etc/fstab to see your partition names, and put that in the boot code. Also try hda2 instead.
Here is a simple boot stanza:
title tinycore
rootnoverify (hd0,6)
kernel /boot/bzImage quiet tce=sda7 max_loop=255
initrd /boot/tinycore.gz
As you can see, there is no tinycore in the boot codes, and the partition name (sda7) is one bigger than the grub name (hd0,6).
sda is used for SATA drives while hda is used for older IDE drives.
-
Under wingrub my partition list as follows
hd0,0 C WinXP
hdo,1 - extended
hd0,4 D Fat32
hd1,0 F Usb
but i am not sure about hda1. i have use this with slax
anyway i'll try
-
With (hd0,4) you need to use hda5 (with sata hard drives sda5).
There are advantages with using the Ext3 filesystem instead of FAT32.
-
ok, it has to be hd0,4 as hd0,6 give error no such partition, sda5 gives no error but it halt at
....
xauth: xreating new authority files /home/tc/.Xauthority
e100:eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin":-2
theres error at the begining that says IO APIC resource cannot be relocated
-
Hm, so it got all the way until Xvesa. Add the bootcode "text" to boot into text mode, from where you can try either Xfbdev or Xorg.
-
thanks curaga, but you have to be slow alot on me as i a just a noob in linux.
ok where should i insert the text command
-
ok i insert
.../bzImage tinycore text ........
i got into boot prompt
tc@box:~$
but a few second this appear
tc@box:~$e100:eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin":-2
i try startx
two lines of this appear than it hang
xauth: xreating new authority files /home/tc/.Xauthority
xauth: xreating new authority files /home/tc/.Xauthority
Xfbdev or Xorg gives not found
i've use this
boot: tinycore tce=hda1 restore=hda1 text vga=788
$ tce-load -w -i Xfbdev.tcz
still doesn't work as mine not connected to internet
-
OK, download ftp://ftp.nluug.nl/pub/metalab/distributions/tinycorelinux/2.x/tcz/Xfbdev.tcz on another machine, put it into your tce directory (/tce on hda1), reboot, and startx should work.
Looks like the firmware-2.6.29.1-tinycore.tcz extension would be useful as well, to get your wired ethernet working.
About vga=788, is the screen 800x600? vga=791 would be 1024x768x16.