Tiny Core Base > CorePlus

Configure LILO to boot Tiny Core Plus

<< < (2/3) > >>

GNUser:

--- Quote from: Len E. on February 12, 2020, 12:00:16 AM ---The "sudo update-grub" command on Bodhi won't pick up the
CorePlus partition.

--- End quote ---

Len E, try putting this in Bodhi's /boot/grub/custom.cfg (create the file if it doesn't exist):

--- Code: ---menuentry 'TinyCore' {
set root=(hd0,msdos3)
linux /boot/vmlinuz
initrd /boot/core.gz
}
--- End code ---
grub is hardwired to parse custom.cfg at boot time--no need for sudo update-grub

Note that you may need to change hd0 to ahci0 depending on your hardware. Also, the number may be different than zero (e.g., hd1) if you have more than one hard drive.

Len E.:
Hi GNUser:
 In following through on your suggestion,   I checked the contents of grub.cfg in
Bodhi, and found that the drive designations were consistent with your example,
so I entered it as is.

On rebooting, TinyCore appeared on the boot list, but on selecting it, the following
messages came up.                   error:   file "/boot/vmlinuz" not found.
                                                       error:    you need to load the kernel first.

Because  vmlinuz and core.gz  normally reside in /mnt/sda3/tce/boot,  I've never been
clear on whether  the menuentry  /boot/vmlinuz would be resolved correctly or not.
As a hedge, on CorePlus,    I've created the directory /boot, made it persistent in
.filetool.lst,  and copied the entire contents of /mnt/sda3/tce/boot into it.

Given this approach, I'm not sure why the error just encountered did occur.

Len. E.

GNUser:

--- Quote from: Len E. on February 12, 2020, 01:26:03 PM ---Because  vmlinuz and core.gz  normally reside in /mnt/sda3/tce/boot...
--- End quote ---

I put boot, opt, and tce directories at the root of my TCL partition. If your boot directory is inside your tce directory, then this is what you need in custom.cfg:


--- Code: ---menuentry 'TinyCore' {
set root=(hd0,msdos3)
linux /tce/boot/vmlinuz
initrd /tce/boot/core.gz
}
--- End code ---

GNUser:
In general, a good way to troubleshoot grub issues is to go to the grub command line. For example:

1. At the grub menu, press c to get a grub command prompt
2. Type ls to check how grub sees your disks and partitions
3. To temporarily set a particular partition as grub's root, type this for example: set root=(hd0,msdos3)
4. At this point, you can type ls / or ls /boot/ or (in your case) ls /tce/boot/ to check what grub sees inside those directories
5. When you're done exploring and want to return to the grub menu, just press Escape

Now you have the information you need to create a working custom.cfg

GNUser:

--- Quote from: Len E. on February 12, 2020, 01:26:03 PM ---I've created the directory /boot, made it persistent in
.filetool.lst,  and copied the entire contents of /mnt/sda3/tce/boot into it.
Given this approach, I'm not sure why the error just encountered did occur.

--- End quote ---
The error occurs because when you create /boot this way (inside a running TCL), you are creating it in RAM--and it's only restored (from tce/mydata.tgz) after TCL has booted.

vmlinuz and core.gz need to exist somewhere on your harddrive where grub can find them. If they are hiding inside mydata.tgz then grub will be a sad panda.

Navigation

[0] Message Index

[#] Next page

[*] Previous page