Tiny Core Base > TCB Talk
Booting 32bit TC from 64bit efi boots to blank screen with underscore
coreplayer2:
In my mind this “burn to a usb” installation is not valid.
But putting that aside because you can boot to a command line..
What is the output of “showbootcodes” ?
And what is the result of
tce-load-i Xvesa ?
Assuming a network connection, try installing
Xorg
tce-ab search Xorg-7.7
or
tce-load -wi Xorg-7.7
And let us know results
Sent from my iPhone using Tapatalk
jimmyjohn:
Since @curaga suggested an xvesa incompatability, I swapped it out for xfbdev and updated onboot.lst accordingly. That fix worked! I now have a gui TC desktop with the 32bit variant.
My next issue is to get WiFi working since I do not have Ethernet on this device. I had it working in CorePure64, but I think I must have missed one or more of the dependencies when getting them for the 32bit version. ** EDIT: I just confirmed, I am not missing any dependencies from the .tree file and made sure that the firmware is loaded first in the order of things**
Then my last issue before I will be able to frugal install to the Mini-PC is to figure out what I need to get TC to see and be able to mount both the onboard eMMC as well as the built in memory card reader; right now it isn't detecting either!
Thanks for your help so far! I suppose I may need to start a separate thread on the eMMC issue, but if not, any additional help would be greatly appreciated. The only thing I have tried on that so far was to boot with the waitusb=5 option
BTW, in case you still want it the output of showbootcodes is: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 cde vga=791"
That output matches what I have in grub.cfg
coreplayer2:
--- Quote from: jimmyjohn on July 06, 2019, 04:11:59 PM ---...
BTW, in case you still want it the output of showbootcodes is: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 cde vga=791"
That output matches what I have in grub.cfg
--- End quote ---
We still need to know how you
“burned the image to usb”
That is not a normal installation.
More importantly the only reason to use a CDE bootcode is if you’re booting from a CD or an ISO
Also missing is waitusb bootcode
In a typical frugal installation to a USB the extensions directory must be tce not cde and the bootcodes will reflect this along with waitusb=
My view is that almost all problems result from the method of installation.
Sent from my iPhone using Tapatalk
jimmyjohn:
I haven't actually installed anything yet, I am just booting from a live USB and am trying to get things to work before I proceed with an installation. I basically just copied and pasted the contents of the ISO to the USB and have been booting it.
coreplayer2:
Copying the contents of the ISO is in fact one method of installing. But know that when you copy the contents of cde directory you must change the name to tce otherwise TC will not find or load your extensions
Sent from my iPhone using Tapatalk
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version