Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: SeventhSin on July 01, 2019, 04:33:45 PM
-
Hello all,
As per Subject. Frugal install from TinyCorePure64 (there is no TinyCorePlusPure64 ISO available for download), results in X not being started. The reason for this is a missing entry from /mnt/sda1/tce/onboot.lst , namely: Xvesa.
Attempts to install Xvesa (tce-load -wi xvesa | tce-load -wi Xvesa | tce-load -wi xvesa.tcz | tce-load -wi Xvesa.tcz) all fail with:
Connecting to mirror blah-blah-blah (tested a handful)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: Xvesa.tcz.md5.tcz: No such file or directory
Error on Xvesa.tcz
Furthermore, I have notice that although I allow the "Apps" extension to probe for the fastest mirror on first run, upon installation the /opt/tcemirror file defaults to repo.tinycorelinux. I don't find this behavior optimal, but do what you will with that.
-
Hello all,
As per Subject. Frugal install from TinyCorePure64 (there is no TinyCorePlusPure64 ISO available for download), results in X not being started. The reason for this is a missing entry from /mnt/sda1/tce/onboot.lst , namely: Xvesa.
Plus? no.. but did you look here for a default onboot.list which uses Xfbdev video?
http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso
Attempts to install Xvesa (tce-load -wi xvesa | tce-load -wi Xvesa | tce-load -wi xvesa.tcz | tce-load -wi Xvesa.tcz) all fail with:
Connecting to mirror blah-blah-blah (tested a handful)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: Xvesa.tcz.md5.tcz: No such file or directory
Error on Xvesa.tcz
tinycorepure64 uses Xfddev (plus vga=xxx bootcode) or Xorg
Furthermore, I have notice that although I allow the "Apps" extension to probe for the fastest mirror on first run, upon installation the /opt/tcemirror file defaults to repo.tinycorelinux. I don't find this behavior optimal, but do what you will with that.
I always use tinycorelinux.net for the most up to date repo
-
Hi SeventhSin
Regarding Xvesa:
Forgot to ask: Why no xvesa for 64bit?
It's not possible to execute VESA bios calls in 64-bit mode. Xorg's vesa driver has an emulator, so it is able to do it nowadays.
Also, your understanding of the lists is correct. The ISOs just have a different setup you'd usually have.
-
tinycorepure64 uses Xfddev (plus vga=xxx bootcode) or Xorg
Right, I was comparing with a TinyCore (x86) setup. The issue still stands though. I am testing in a VMWare VM: booting the TinyCorePure64.iso image => I successfully end up with a desktop. However, installing to the VM drive, results in the error mentioned in the Subject: failed in waitforX. The /mnt/sda1/tce/onboot.lst seems identical with /mnt/sd0/cde/onboot.lst from before installation.
I know I can just install open-vm-tools-desktop and be done with it, however I want to understand what's going on here.
-
It's not possible to execute VESA bios calls in 64-bit mode. Xorg's vesa driver has an emulator, so it is able to do it nowadays.
My bad, I was comparing 2 different ISO's (TinyCore & TinyCorePure64). Thanks for claryfing the Xvesa issue, I didn't know that.
-
dmesg shows nothing suspicious and /var/log contains only autologin & wtmp.
-
Hi SeventhSin
... Thanks for claryfing the Xvesa issue, I didn't know that.
You're not the first, you won't be the last. :)
-
Xfbdev can't start without a framebuffer; does your 64-bit install have the vga=xxx bootcode?
-
Xfbdev can't start without a framebuffer; does your 64-bit install have the vga=xxx bootcode?
@curaga, you nailed it! This is in fact the issue: on TinyCorePure64 boot ISO, the boot loader includes vga=791 boot code. Although absolutely required by Xfbdev the installation app makes no effort to check & add a vga=xxx boot code in case none is provided.
Suggestion:
Update the installer to set up the boot loader with a most necessary vga=xxx in case the user doesn't specify any during installation. Skip if a vga=xxx boot code is present.