Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: egency on May 16, 2018, 01:03:50 AM
-
So I really have no real idea what or where the problem is so I'll start by sketching out what I've done, what I have, and what I'm hoping to achieve.
After more than a month of struggling to get a USB to boot anything other than Mint or the like I finally managed to hack together a grub-efi thing on a GPT partition covering the whole USB. It's a thorough hack, but that's a topic I'll start later. I manage to get TinyCore to boot to a prompt even! :)
After hacking at things I don't really understand I managed get TC to load the extensions in the /tce dir. This is quite weird as I couldn't get them to load using "tce-load -i" previously. It's also a bit of a hack as I just set "tce=sdb1", but again, I'll deal with that later.
At this point TC decides to just start mocking me and I'm running really thin on ideas. Rather than booting to a console (or anything else), it briefly flashes something about loading extensions and then just displays a non-blinking cursor (an underscore type text cursor) in the top left corner and refuses to respond to anything short of a hard reset...
I don't know what this means nor what to do about it. Mostly what I'm hoping to achieve is just getting all the base functionality to work so I can start using it and figuring out how it works.
Incidentally I've also downloaded the broadcom (bcm43xx) firmware which I /believe/, though am by no means sure, will be required to get networking started. That's also in the /tce directory for when I get to the point where figuring out how to get that working becomes a thing.
This is really frustrating as I'm really keen on TinyCore, it very closely mirrors my own design for an ideal Linux.
Any advice about where to poke next to figure this out would be hugely appreciated!
-
Most likely X hung, Xvesa if you haven't installed Xorg or Xfbdev, or just failed to display. When it happens, try pressing ctrl-alt-backspace, the X-killing key combo. Alternatively, add the "text" bootcode to your grub config file to boot to cli to test things out.
-
If you have Windows, search Sourceforge for core2usb. USB must be formatted first and empty. It even includes tc-install GUI, if you want to install to the PC's disk.
-
@NewUser unfortunately I don't currently have access to a windows machine.
@curaga Given where in the boot it crashed I suspected similar, the ctrl-alt-backspace you suggested didn't do anything though so I'm not sure whether that indicates anything. It's a touch late now but I'll try adding the text boot option tomorrow. I was also thinking of turning the loading of some of the files off to see if I can't narrow it down that way.
-
FYI
How to make a legacy bios/uefi dual boot usb stick with grub2 (http://forum.tinycorelinux.net/index.php/topic,19364.0.html)
How to make a legacy bios/uefi dual boot usb stick with syslinux (http://forum.tinycorelinux.net/index.php/topic,20939.0.html)
-
Thanks polikuo! I'll come camp your thread once I have a bit of a better grip on my system. :)
So, definitely an X issue as it happens whenever startx is run as well. Don't know what to do about it, so I'll be searching the forums so long to see the prior art. :)
I forgot to add, it's obviously an Intel mac, I'm not sure what the exact hardware is yet as TC doesn't seem to have lspci (and I don't know of any other way to check) so I need to ferret that over. Incidentally, TCZ packages are exceedingly convenient, they're even sneakernet compatible. :)
-
Hi egency
... TC doesn't seem to have lspci (and I don't know of any other way to check) ...
Have tried installing pci-utils.tcz ?
-
I am planning to (thanks for the name, that helps), but I first need to remember where I lost the repository. I haven't figured out how to get networking to work yet so I'm copying the files over on USB.
The lack of networking is partly because I'm not sure how to actually get the bcm firmware into the kernel, and I'm still seeing whether I can find the networking section of the wiki as I can connect my phone via USB but need to work out how to setup routes and the like.
-
Hi egency
I am planning to (thanks for the name, that helps), but I first need to remember where I lost the repository. ...
Was it the ibiblio site:
http://distro.ibiblio.org/tinycorelinux/9.x/x86/tcz/
You didn't mention version or architecture but that is 32 bit version of TC9.
-
It's an ignorant stab in the dark, but I have a laptop (no CD drive or hard disk even) that wouldn't boot TC to the desktop off a USB stick until Xorg 7.7 was installed.
I booted another computer into TC from CD, then used TC Install to format the USB stick there. After that Apps gives you the option of installing extensions to the USB stick rather than the boot box. The laptop would boot to a prompt with the basic TCL install on the USB, but not to the desktop without Xorg.
Don't know if any of this relates to your issue. Good luck.
-
@thane, I'm sort of heading towards installing Xorg I think. Unfortunately I don't currently have another machine that works so that method is unavailable to me currently. However what you're saying about Apps giving the option of installing extensions to USB is very useful. It should greatly ease future installs. :)
@Rich It was indeed the ibilbio site. I had it bookmarked somewhere, but misplaced the bookmark...
So, with my newfound power of lspci:
02:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M] (rev b1)
So, would I be correct in guessing that I just need to install Xorg-7 along with the xf86-nouveau drivers? Perhaps synaptics given the touchpad. I never was any good with figuring out Xorg stuff, black magic that... :/
Also, I've noticed that even though the broadcom firmware gets loaded on boot I still can't get my wifi device to come up. I poked around some trying to modprobe it, however the firmware doesn't have any .ko files so it doesn't seem to be a kernel module thing. I'm not sure what I'm missing? The package doesn't list any dependencies either.
-
So I went ahead and got Xorg and all it's dependencies (as per Xorg-7.7.tcz.tree). I dumped the lot into /tce/optional, added them to onboot.lst and booted. When running startx however it gives and error stating something like "failed on waitforX".
Anybody have any ideas?
-
...
Incidentally I've also downloaded the broadcom (bcm43xx) firmware which I /believe/, though am by no means sure, will be required to get networking started. That's also in the /tce directory for when I get to the point where figuring out how to get that working becomes a thing.
Hello egency, you might have better luck with broadcomm wifi if you download both firmware-getB43.tcz and wifi.tcz extensions and all their dependencies while connected via ethernet using "tce-ab, or tce-load -wi" at the console then add wifi.tcz to onboot.lst. Still while connected, load and run firmware-getB43.tcz to download the correct wifi firmware. Add the resulting firmware extension to onboot.lst before wifi.tcz. Remember to remove all other broadcomm firmware from onboot.lst
You only need to load the main extension, all dependencies are installed from the main extensioin's dep file
You need drivers for the video card, but meanwhile try Xvesa extension
-
So I went ahead and got Xorg and all it's dependencies (as per Xorg-7.7.tcz.tree). I dumped the lot into /tce/optional, added them to onboot.lst and booted. When running startx however it gives and error stating something like "failed on waitforX".
If you enter the following command manually, you will see an error messages that will indicate the source of the problem: $ Xorg -nolisten tcp
-
You might need graphics-KERNEL (graphics-4.14.10-tinycore64) extension. ;)
-
Have network, will travel! Thanks coreplayer2! It went smoothly, for a moment I thought I did something wrong when it initially believed I had no wifi card, but after a reboot it worked just perfectly. :) About your suggestion about the Xvesa extension, isn't it already loaded? I mean, it loads an Xvesa extension on boot...
So far what I've tried: installing xf86 nouveau driver, which didn't help the situation any for either Xvesa or Xorg, installed the graphics-KERNEL packages, which likewise didn't change the errors at all. I did however do the "Xorg -nolisten tcp" thingy which pointed me at the log file:
[ 310.957] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -19
[ 310.957] (EE) open /dev/dri/card0: No such file or directory
[ 310.957] (WW) Falling back to old probe method for modesetting
[ 310.957] (EE) open /dev/dri/card0: No such file or directory
[ 310.958] (EE) Screen 0 deleted because of no matching config section.
[ 310.958] (II) UnloadModule: "modesetting"
[ 310.958] (II) Loading sub module "vbe"
[ 310.958] (II) LoadModule: "vbe"
[ 310.958] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[ 310.958] (II) Module vbe: vendor="X.Org Foundation"
[ 310.958] compiled for 1.19.5, module version = 1.1.0
[ 310.958] ABI class: X.Org Video Driver, version 23.0
[ 310.958] (II) Loading sub module "int10"
[ 310.958] (II) LoadModule: "int10"
[ 310.958] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[ 310.958] (II) Module int10: vendor="X.Org Foundation"
[ 310.958] compiled for 1.19.5, module version = 1.0.0
[ 310.958] ABI class: X.Org Video Driver, version 23.0
[ 310.958] (II) VESA(0): initializing int10
[ 310.959] (EE) VESA(0): V_BIOS address 0xd00 out of range
[ 310.960] (II) UnloadModule: "vesa"
[ 310.960] (II) UnloadSubModule: "int10"
[ 310.960] (II) Unloading int10
[ 310.960] (II) UnloadSubModule: "vbe"
[ 310.960] (II) Unloading vbe
[ 310.960] (EE) Screen(s) found, but none have a usable configuration.
[ 310.960] (EE)
Fatal server error:
[ 310.960] (EE) no screens found(EE)
Which /appears/ to mean that there's a configuration error? The BIOS out of range thing is also peculiar. When I ran "Xvesa -modelist" it gave a similar error about something out of range ROM, which I stupidly forgot to note down... ::)
-
If the modesetting driver was unloaded, it probably means that the graphics-KERNEL extension was not loaded
-
If the only graphics card is a Nvidia (and no Intel?), try installing Nvidia proprietary drivers.
-
@Juanito according to tce-ab graphics-KERNEL is loaded. I don't know what else to check?
@curaga I rechecked and there's only a Nvidia card, I noted that some other people had issues with multi-card setups. I tried loading firmware-nvidia but that didn't seem to help. I couldn't find any other package mentioning Nvidia, only the nouveau xf86 driver. Am I missing something?
I found this: https://www.redhat.com/archives/rhl-devel-list/2009-December/msg00372.html which seems to be related... I'm not sure what to do with it however but I thought it may give someone more knowledgeable an idea of what's wrong.
-
egency, are you able to boot all the way to any desktop? or are you only able to boot to the console ?
-
egency, Just to recap: there are three extensions which may provide graphics allowing a boot to a desktop environment.
Xfbdev.tcz
Xvesa.tcz
Xorg.tcz
Only Xorg will require a driver, either one of it's own like modesetting driver or an Nvidia proprietary driver like the one I'm using for my GeForce GTX 1060 graphics card. If you need help with building one for your system I try to help with that.
If you haven't tried Xfbdev.tcz yet, then I suggest you try that for now. remember that which ever of the above three extensions you are using it's important to remove the remaining two graphics extensions from the onboot.lst before the next boot.
I have found corepure64 boots and runs better on macbooks and the like, but tinycore should run perfectly on most macbooks too
-
coreplayer2, haven't managed to boot anything to desktop, only to console. Xfbdev.tcz complained about fonts for some reason when I tried it. However I didn't know that one should unload the other extensions first...
As an aside, what does the graphics-KERNEL package do exactly anyway?
So, I'm going to start from scratch and try Xfbdev and report back with the results.
-
Before I forget yet again, everytime on boot the little TnyCore image popped up so atleast on the kernel side the frame buffer works fine.
I tried CorePure and it loads Xvesa just fine. Although its really slow and touchpad handling is quite bad (seems to be a configuration issue). So thats a start. :) Incidentally CorePure seems to use Xfbdev instead of Xvesa.
Going to test Xorg next.
-
Incidentally CorePure seems to use Xfbdev instead of Xvesa.
corepure64 or coreplus ? One is the pure x86_64, the other is tinycore installer with many drivers included
I didn't know that one should unload the other extensions first...
The last extension to load will take precedence. Therefore as with other extensions load only the extension you want to run, remove any other conflicting extensions from onboot.lst
Sometimes you'll find it better to boot to the console and load your desired extension manually
tce-load -i xxx.tcz
-
CorePure64, not CorePlus. I tried Xorg on CorePure64 and it gave me exactly the same issue as TinyCore
-
CorePure64, not CorePlus. I tried Xorg on CorePure64 and it gave me exactly the same issue as TinyCore
OK so you'll be using Xfbdev or Xorg
-
Yes, and Xfbdev does boot to desktop on CorePure64, however it's extremely slow. Xorg fails with exactly the same error as TinyCore (I posted it earlier in this thread).
-
If or when you install Xfbdev to a USB or HDD remember to add the VGA= bootcode to grub or syslinux config file, see http://tinycorelinux.net/faq.html or the core book for more info