WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tinycores, Macbooks, USBs and misery  (Read 7276 times)

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #15 on: May 18, 2018, 11:59:55 AM »
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:

Code: [Select]
[   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...  ::)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: Tinycores, Macbooks, USBs and misery
« Reply #16 on: May 19, 2018, 12:24:28 AM »
If the modesetting driver was unloaded, it probably means that the graphics-KERNEL extension was not loaded

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
Re: Tinycores, Macbooks, USBs and misery
« Reply #17 on: May 19, 2018, 12:51:38 AM »
If the only graphics card is a Nvidia (and no Intel?), try installing Nvidia proprietary drivers.
The only barriers that can stop you are the ones you create yourself.

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #18 on: May 19, 2018, 08:33:51 AM »
@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.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Tinycores, Macbooks, USBs and misery
« Reply #19 on: May 19, 2018, 08:56:58 AM »
egency, are you able to boot all the way to any desktop?  or are you only able to boot to the console ?

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Tinycores, Macbooks, USBs and misery
« Reply #20 on: May 19, 2018, 09:16:46 AM »
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

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #21 on: May 19, 2018, 10:09:36 AM »
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.

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #22 on: May 19, 2018, 11:02:44 AM »
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.
« Last Edit: May 19, 2018, 11:25:16 AM by egency »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Tinycores, Macbooks, USBs and misery
« Reply #23 on: May 19, 2018, 12:21:14 PM »
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


Quote
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
Code: [Select]
tce-load -i xxx.tcz
« Last Edit: May 19, 2018, 12:40:58 PM by coreplayer2 »

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #24 on: May 19, 2018, 12:38:06 PM »
CorePure64, not CorePlus. I tried Xorg on CorePure64 and it gave me exactly the same issue as TinyCore

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Tinycores, Macbooks, USBs and misery
« Reply #25 on: May 19, 2018, 12:42:26 PM »
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

Offline egency

  • Newbie
  • *
  • Posts: 12
Re: Tinycores, Macbooks, USBs and misery
« Reply #26 on: May 19, 2018, 12:55:53 PM »
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).

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Tinycores, Macbooks, USBs and misery
« Reply #27 on: May 19, 2018, 03:04:15 PM »
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
« Last Edit: May 19, 2018, 03:11:15 PM by coreplayer2 »