Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: Daniel on August 11, 2011, 04:16:22 AM
-
Yes, i've got the MD5SUM problem.
After reboot, i've tried to dowload an other .tcz : ok.
Problem again with syslinux.tcz.
And ok with an other .tcz after.
Daniel.
[Edit] Need to remove and try again to succed.
-
When i'm trying to use syslinux, i've got the error "mount: could not find any free loop device".
-
I've add max_loop=256 on the kernel command line.
Starting direcly to upload syslinux.tcl after booting : MD5 error.
If i press Remove and try again button i've got "mount: could not find any free loop device" ...
I am under the 3.8rc2 Tiny Core version.
D.
-
When i'm using my syslinux program (V4.04) compiled under TCL, i've got the error :"sh: mcopy not found" and it fails to create ldlinux.sys.
D.
-
Seems to be ok with TCL 3.8rc3.
D.
-
There was a conflict with coreutils and util-linux, should be working in 3.8 final too.
-
Conclusion : solved.
Thanks
Daniel.
-
RE OPEN:
In fact, the syslinux doesn't run OK.
After "syslinux /dev/sda1 --install" (or update), the syslinux line appears half a second and nothing more.
If i do syslinux (V4.02) under Ubuntu on the same usk key, boot is ok.
(if i do again the same under TCL, boot is KO).
When i'm using my syslinux program (V4.04) compiled under TCL, i've got the error :"sh: mcopy not found" and it fails to create ldlinux.sys.
What can i do ?
Thanks
Daniel.
-
If you build syslinux yourself, use the no-mtools variant. I'm not sure if that's a config option, or if it's in a different dir in syslinux 4.0.
-
syslinux v3.8 or Grub4dos are the best fixes for all the syslinux 4.xx bugs ;D
-
After a first look, i'm not sure mtools can be not used.
On an other side, i install mtools.tcz.
But i have errors:
Error converting to codepage 850 Invalid argument
Cannot initizlise 'S:'
Bad target s:/ldlinux.sys
./syslinux: failed to create ldlinux.sys
D.
-
Due to an unrelated subject I've discovered that the Error converting to codepage 850 Invalid argument error will most likely be resolved if you install the glibc_gconv.tcz extension. Whether that also helps to resolve the other errors is unknown to me, but I'm sure you'll find out yourself.
I don't believe that 'glibc_gconv.tcz' should be made a direct dependency of 'mtools.tcz', but it would probably a good idea to include a hint in 'mtools.tcz.info'.
-
With 'glibc_gconv.tcz', my syslinux 4.04 is running (tested ok!).
The TCL syslinux 4.01 is running to (i don't try booting after).
Thank you very mutch, maro! :D
Daniel.
-
not sure why - never could get syslinux to fly under tce
and can only get grub4dos to work WITH tce (won't work in DOS or a Windows prompt)
As for syslinux - when I type
sudo syslinux -s /dev/sdc1
it returns a message UNKNOWN OPTION -s - and a list of options which INCLUDE the -s ???????
and if I type
sudo syslinux /dev/sdc1
it returns a message POSSIBLY UNSAFE /TMP/ PERMISSIONS
???????
sdc1 is a USB Flash Drive, with a spanking new partition and formatted mkdosfs -F 32 and WILL accept:
1. a grub4dos bootlace command when done by TCE
and
2. a syslinux -m -a -s F: - when done on a Windows PC
This error has been "forever" ... and I wonder if syslinux is bad? md5sum checks out ok.
??????????? HELP !!!!!!!!!!!!!!!!!!!!!!
-
What happens if you try something like this:
$ sudo syslinux --directory /boot/syslinux/ --install /dev/sdb1
-
same error (thank goodness - I copied your command exactly and if it had worked I would have whacked the functional grub4dos on that sdb1 usb flash drive...my main boot)
...am hacking on /mnt/sdc1 ;)
-
This appears to have worked:
$ sudo fdisk /dev/sdc
[Changed system type of partition 1 to b (W95 FAT32)]
$ sudo mkfs.vfat /dev/sdc1
$ sudo mount -t vfat /dev/sdc1 /mnt/sdc1
$ sudo mkdir -p /mnt/sdc1/boot/syslinux
$ sudo syslinux --directory /boot/syslinux/ --install /dev/sdc1
$ ls /mnt/sdc1/boot/syslinux
ldlinux.sys
..though I didn't add a syslinux.cfg and try to boot
Edit: corrected mkfs.vfat line
-
got error mkfs.vfat not found
thought it was mkdosfs
?
FOUND IT - tce-load -i mkisofs-tools
same error message
"possible unsafe /tmp/ permissions"
have found effective "work around" using (ahem) W2K Installation CD and QEMU...works well.
Wine under TC can't seem to get er done either, but W2K/QEMU combination
has been fairly painless and reliable.