Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: philip_rhoades on December 28, 2015, 06:36:30 AM
-
People,
This is the only thing I have been able to find so far on this topic:
http://forum.tinycorelinux.net/index.php/topic,19313.msg119077
and although it works - the netbook only boots to a text mode screen (the same iso boots all the way to a GUI as a VM with qemu-kvm). I presume I am missing something or there is a step I can take at the text prompt to start X? Has anyone got a working Grub2 entry that I could try?
Thanks,
Phil.
-
I guess you're missing the iso= boot code.
menuentry "Tiny Core - iso" --class core --class gnu-linux --class gnu {
set isofile="CorePlus-5.0.iso"
echo Loading ${isofile} ...
loopback loop (hd0,msdos2)/boot/tce-5.x/boot/${isofile}
echo Loading Kernel ...
linux (loop)/boot/vmlinuz iso=/mnt/sda4/boot/tce-5.x/boot/${isofile} loglevel=3 cde showapps nozswap
echo Loading RAM-Image ...
initrd (loop)/boot/core.gz
echo Booting ...
}
Adopt to your partitioning, file locations / names etc.
-
Hopefully Misalf's advice solves the issue, otherwise paste your exact grub2 entry. The example you linked needs to be modified for your use case. It contained the boot code desktop=fluxbox, not on the default TC iso. If it can't find the desktop it will boot to text. That example was also for a frugal install, not an iso boot.
-
People,
No luck - still booting to text - here is my modified version of Misalf's entry (I have the iso in the Fedora "boot" partition):
menuentry "Tiny Core - iso" --class core --class gnu-linux --class gnu {
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
set isofile="CorePlus-current.iso"
echo Loading ${isofile} ...
loopback loop /${isofile}
echo Loading Kernel ...
linux (loop)/boot/vmlinuz iso=/${isofile} loglevel=3 cde showapps nozswap
echo Loading RAM-Image ...
initrd (loop)/boot/core.gz
echo Booting ...
}
Which was not that different from what I have tried before:
menuentry "Core" {
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
loopback loop /CorePlus-current.iso
# linux (loop)/boot/vmlinuz isofrom=/CorePlus-current.iso noisapnp
linux (loop)/boot/vmlinuz nozswap showapps tce=sda4 desktop=fluxbox
initrd (loop)/boot/core.gz
}
Could it be hardware problems with the netbook? (I wouldn't have thought so - the GUI works with Fedora and xPUD 0.9.2).
Thanks,
Phil.
-
Any reason you can't install it properly? Instead of an iso file, it would be a couple files in a directory.
-
curaga,
Yes, because it turns into a major PITA:
- I don't have a CD drive on the NetBook
- unetbootin doesn't work on the latest Fedora
- there are more, slower, steps than just booting the iso from Grub
- booting from Grub should be able to work - why doesn't it?
.
.
-
Try adding the full path in the iso= bootcode.
menuentry "Tiny Core - iso" --class core --class gnu-linux --class gnu {
set isofile="CorePlus-current.iso"
loopback loop (hd0,msdos1)/${isofile}
linux (loop)/boot/vmlinuz iso=/mnt/sda1/${isofile} cde
initrd (loop)/boot/core.gz
}
Edit: Meaning the path as Tiny Core will see it.
-
I think " cde " in command line is key, otherwise it will only boot to terminal
Sent from my iPhone using Tapatalk
-
- I don't have a CD drive on the NetBook
You could mount the iso and copy the files you need or, alternatively, use the distribution section of the release - usually core.gz or rootfs.gz is all you need to upgrade.
-
I think " cde " in command line is key, otherwise it will only boot to terminal
That was already there - see above . .
- I don't have a CD drive on the NetBook
You could mount the iso and copy the files you need or, alternatively, use the distribution section of the release - usually core.gz or rootfs.gz is all you need to upgrade.
But I am multi-booting a number of isos and I would still need a Grub2 entry anyway - it is cleaner to just boot on the iso of choice I think but if no one can find a solution then I will have to do the file extraction etc I guess . .
Thanks.
-
but if no one can find a solution then I will have to do the file extraction etc I guess . .
I extracted the files and used this Grub2 entry:
menuentry "Tinycore" {
set root='hd0,msdos1'
linux /tinycore/vmlinuz waitusb=5 blacklist=pcspkr nozswap nodhcp cde
initrd /tinycore/core.gz
}
- but it still only boots to text mode . .
-
Hi philip_rhoades
Copy the cde directory to the root of the drive. Rename it to tce. Remove the cde boot code.
-
Rich.
Hi philip_rhoades
Copy the cde directory to the root of the drive. Rename it to tce. Remove the cde boot code.
That works! - Thanks . . but does that mean it is not possible to boot the iso from Grub2 to graphics mode?
P.
-
Specify your window manager as the desktop=* bootcode, example:
linux /tinycore/vmlinuz waitusb=5 blacklist=pcspkr nozswap nodhcp cde desktop=fluxbox
-
. . but does that mean it is not possible to boot the iso from Grub2 to graphics mode?
I use this and it works for me, all the way up to graphics mode.
http://forum.tinycorelinux.net/index.php/topic,18177.msg110261.html#msg110261
-
People,
Thanks for suggestions - this is now working for me:
menuentry 'Tiny Core - iso' --class core --class gnu-linux --class gnu {
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
set isofile="CorePlus-current.iso"
echo Loading ${isofile} ...
loopback loop /${isofile}
echo Loading Kernel ...
linux (loop)/boot/vmlinuz iso=/${isofile} loglevel=3 showapps nozswap waitusb=5 blacklist=pcspkr nodhcp cde desktop=fluxbox
echo Loading RAM-Image ...
initrd (loop)/boot/core.gz
echo Booting ...
}
The next step is now to try and get the wifi working - I have had a lot of trouble with the Broadcom B43 driver in Fedora over the years and it is not currently working with this TC - even after a bit of fiddling - but I guess that is a question for a new post . .
Thanks to everyone,
Phil.
-
Hi philip_rhoades
Go to the search page:
http://forum.tinycorelinux.net/index.php?action=search
Set the search order to Most recent topics first and search for Broadcom B43
-
You need to install the firmware. There are firmware-broadcom_43xx and firmware-openfwwf extensions that you should install "onboot".
That might be all you need.