Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: bmarkus on January 10, 2012, 08:28:40 AM
-
rep: 4.01
upsteram: 4.05
-
Thanks for the heads up :) hopefully they have addressed the bug which prevents booting on some old equipment. Will be looking out for this update
-
4.04 wouldn't even compile, but I'll try to look at 4.05 this weekend
-
posted
-
4.04 wouldn't even compile, but I'll try to look at 4.05 this weekend
Depending on the error, it might have been one I fixed.
-
Oh oh! errors installing :(
When installing or updateing, a switch is required -i -u etc..
Also when
sudo extlinux /mnt/sda1/boot/extlinux
the return is
extlinux /mnt/sda1/boot/extlinux is device /dev/sda1
which is odd because I figured it would have been /mnt/sda1/tce/boot/extlinux ??
Anyhow, extlinux refuses to install to any of those paths
either the app returns the device is /dev/sda1 or not a directory !
However, I do have a copy of Idlinux.sys in /mnt/sda1/boot/extlinux
-
So, this doesn't work?:
Run the extlinux installer on the directory in which you want extlinux installed:
extlinux --install /boot
Specify --install (-i) to install for the first time, or --update (-U) to upgrade a previous installation.
NOTE: this doesn't have to be the root directory of a filesystem.
If /boot is a filesystem, you can do:
mkdir -p /boot/extlinux
extlinux --install /boot/extlinux
... to create a subdirectory and install extlinux in it.
/boot/extlinux is the recommended location for extlinux.
2. The configuration file is called "extlinux.conf", and is expected to be found in the same directory as extlinux is installed in.
Note that EXTLINUX installs in the filesystem partition like a well-behaved bootloader :) Thus, it needs a master boot record in the partition table; the mbr.bin shipped with SYSLINUX should work well.
To install it just do:
cat mbr.bin > /dev/XXX
-
The only method I could accomplish is install or update to /mnt/sda1/boot/extlinux which only placed Idlinux.sys into this location (not sure if a cfg file was intended to be installed there to but there was no cfg file). I then copied Idlinux.sys over to the correct location /mnt/sda1/tce/boot/extlinux am not sure if the mbr was updated or not however the system rebooted with the original cfg file untouched :)
Thanks :)
I used the install instructions from the info file and with the above modification now boots to syslinux 4.05 :) thanks
-
The only method I could accomplish is install or update to /mnt/sda1/boot/extlinux which only placed Idlinux.sys into this location (not sure if a cfg file was intended to be installed there to but there was no cfg file). I then copied Idlinux.sys over to the correct location /mnt/sda1/tce/boot/extlinux am not sure if the mbr was updated or not however the system rebooted with the original cfg file untouched :)
Thanks :)
I used the install instructions from the info file and with the above modification now boots to syslinux 4.05 :) thanks
1) Why bother moving/copying after install? Install to the _correct_ location the first time.
2) The MBR is _not_ touched by the Linux installers.
3) The installer does nothing to touch your config.
-
1) Why bother moving/copying after install? Install to the _correct_ location the first time.
lol yes exactly but tried that and failed, repeatedly. see above.
Just following instructions here, which as you can see does not have the correct path.. and also indicated a change to the config file during install/update..
Howto:
$ sudo mkdir -p /mnt/sda1/boot/extlinux
$ sudo extlinux /mnt/sda1/boot/extlinux
copy and rename config from tinycore iso...
$ sudo cp /path-to-file/isolinux.cfg /mnt/sda1/boot/extlinux/extlinux.conf
----------
-
Output of "/mnt/sda1/boot/extlinux is device /dev/sda1" is perfect. The device (not the file system mount directory) is /dev/sda1.
You say it refused to install but had the ldlinux.sys file. Did you try booting? What were the results?
-
Ok I understand now, the extension installs to the expected directory as per tc 4.1.. Unfortunately this boot directory location has changed in core-plus 4.2.1 to /mnt/sda1/tce/boot/extlinux,
after running " sudo extlinux -u /mnt/sda1/boot/extlinux " we have two instances of ldlinux.sys installed
one copy in /mnt/sda1/boot/extlinux
and the original in /mnt/sda1/tce/boot/extlinux
Where's the consistency in this?
Am I wrong?
-
syslinux.tcz.info should have both examples. 4.0-4.1 using boot/extlinux and 4.2+ using tce/boot/extlinux relative to the file system's root.
coreplayer, if you do the following
sudo extlinux /mnt/sda1/tce/boot/extlinuxdoes it work? (Since the directory and config already exist).
As of Syslinux-4, EXTLINUX as a bootloader has been merged into SYSLINUX with syslinux being the unmounted FAT-only SYSLINUX installer and extlinux being the mounted all-purpose SYSLINUX installer. extlinux.conf now takes priority in SYSLINUX and syslinux.cfg is the secondary config filename for both ISOLINUX and SYSLINUX.
-
syslinux.tcz.info should have both examples. 4.0-4.1 using boot/extlinux and 4.2+ using tce/boot/extlinux relative to the file system's root.
Cool right there, this answers the issue. just that the info file didn't expand on this procedure thanks. Which is why I moved the files manually.
btw I did show the extract from the info file above, right? no mention of the the 4.2 support. so did it manually as explained earlier. but now I know thanks
coreplayer, if you do the following
sudo extlinux /mnt/sda1/tce/boot/extlinuxdoes it work? (Since the directory and config already exist).
fortunately in the end yes it works but not work exactly as described, no big deal just obscure and info file is lacking some guidance is all. I already had it figured out and configured, just it might be disconcerting for some newbies like me :p
Thanks for updating this extension
-
@bmarkus, is there some specific reason(feature/bug) to update? Syslinux is very touchy as I have had newer versions break documented funtionality. If there were good reasons to update, great. Just as long as it doesn't break anything.
-
@bmarkus, is there some specific reason(feature/bug) to update? Syslinux is very touchy as I have had newer versions break documented funtionality. If there were good reasons to update, great. Just as long as it doesn't break anything.
I'm not the maintainer of syslinux.tcz Provide details exactly what is wrong with the current upstream version.
-
I just double-checked this again on a usb stick I wiped clean with fdisk and formatted ext2.
Using syslinux-4.05 and the core-4.2.iso, I see "-i" is now required (info file updated accordingly), but otherwise things work as per the info file example, i.e. : $ sudo mkdir -p /mnt/sda1/boot/extlinux
$ sudo extlinux -i /mnt/sda1/boot/extlinux
$ sudo cp /path-to-file/isolinux.cfg /mnt/sda1/boot/extlinux/extlinux.conf
..and then: $ sudo cp /path-to-file/core.gz /mnt/sda1/boot
$ sudo cp /path-to-file/vmlinuz /mnt/sda1/boot
..and things work without even needing to edit extlinux.conf
-
cool thanks
I think after reading the info file I was not expecting to install to another location which clearly lead to some confusion.. sorry
Works great though, but really need do inject it into the Core-current.iso :) that would be really helpful
-
Oh, that's easy: just replace the isolinux.bin file and recreate the iso with mkisofs.
-
Really? as easy as using the isolinux.bin from tmp/tcloop/syslinux/usr/local/share/syslinux/ ? that's just too easy lol
Thanks
Will give it a test drive asap
-
@tweetyhack, I'm sure myself and others on the Syslinux mailing list would love to hear when things break. At the moment, I'm trying to finish up a new COM32 module to resolve an issue with some NBPs and looking at expanding debug data to diagnose two more issues in PXELINUX, one that I'm experiencing and another that another user is seeing.