Tiny Core Linux

Tiny Core Extensions => TCE Q&A Forum => Topic started by: SeventhSin on June 25, 2019, 03:17:27 PM

Title: TC & NVidia
Post by: SeventhSin on June 25, 2019, 03:17:27 PM
Hello,

Core-current (10.x, 32 bit)

1. On a laptop with embedded Radeon video, all I have to do to is type tce-load -wi firmware-radeon graphics-4.19.10-tinycore ... and Bob's your uncle.
2. On a laptop with embedded Intel video, all I have to do is type tce-load -wi graphics-4.19.10-tinycore ... and Bob's your uncle.

However, I am unable to generate a "Bob's your uncle" scenario for NVidia adapters.

tce-load -wi xf86-video-nouveau => no luck ( various forum posts suggest it has been disabled (?!) )
tce-load -wi xf86-video-nv => no luck ( couple of KB, seems more like a shim, can't really be expected to work by itself (?!) )
tce-load -wi xf86-video-nv graphics-4.19.10-tinycore => no luck

The way I see it:

- no proprietary NVidia driver in the repositories because ... reasons ...
- nouveau is present, but ain't working because ... reasons ...

How does one generate a "Bob's your uncle" scenario for NVidia adapters on Core?
Title: Re: TC & NVidia
Post by: Juanito on June 25, 2019, 04:39:03 PM
Try the NVidia machine with graphics-KERNEL and check the Xorg log to see which video drivers it’s trying to load.
Title: Re: TC & NVidia
Post by: SeventhSin on June 25, 2019, 05:16:19 PM
Thank you for the suggestions, Juanito.

I haven't installed Xorg. I'm testing on a vanilla Core (the 11 MB shell only incarnation). graphics-KERNEL resolves to graphics-4.19.10-tinycore.tcz

After installing graphics-KERNEL on the Radeon/Intel machines, the screen goes black for a second and then come back @ max resolution. However, tce-load -wi kernel-GRAPHICS on the NVidia machines results in packages being downloaded, appropriate OKs everywhere but then, nothing happens. No new module loaded by the kernel, nada
Title: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 12:02:03 AM
Hello
Maybe you can tell us the model of NVIDIA card ?


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 02:24:21 AM
Does anything show up in dmesg after graphics-KERNEL is loaded on the nvidia machine?
Title: Re: TC & NVidia
Post by: curaga on June 26, 2019, 03:21:34 AM
Quote from: SeventhSin on June 25, 2019, 03:17:27 PM
- no proprietary NVidia driver in the repositories because ... reasons ...
- nouveau is present, but ain't working because ... reasons ...

How does one generate a "Bob's your uncle" scenario for NVidia adapters on Core?
Extensions are user contributed. Nobody has yet contributed the proprietary nvidia drivers for 10.x x86, some previous versions have those. If you need that, why not make it yourself?

Nouveau is too unstable, just as staging drivers or many third-party drivers. As such it is not enabled by default. If someone builds it and sends a separate extension, it will be accepted; as a separate extension, it needs a separate action from the user to enable, and so is clear opt-in to whatever issues may happen.

xf86-video-nv should work, but it does not support the most recent nvidias.
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 09:25:12 AM
Quote from: coreplayer2 on June 26, 2019, 12:02:03 AM
Hello
Maybe you can tell us the model of NVIDIA card ?


Sent from my iPhone using Tapatalk

Tested on machines with NVIDIA GeForce GT 740 and NVIDIA Geforce GT 430. Pretty old cards.

Quote from: Juanito on June 26, 2019, 02:24:21 AM
Does anything show up in dmesg after graphics-KERNEL is loaded on the nvidia machine?

Nothing in dmesg.

Quote from: curaga on June 26, 2019, 03:21:34 AM
If you need that, why not make it yourself?

I am here at the behest of my company. We wish to identify a suitable base for our custom platform. My job is to research and secure the component technologies. For the past 4 months or so I have been thoroughly testing various Linux distributions for suitability to purpose. I have chosen TinyCore Linux and now I'm in the process of mapping what works, what doesn't and what's missing. Our goal is to contribute to the upstream (TC) by contracting (short-medium term) and even hiring (medium-long term) from within the community as opposite to "in-house cooking".

Quote from: curaga on June 26, 2019, 03:21:34 AM
xf86-video-nv should work, but it does not support the most recent nvidias.

Based on my observations none of the xf86-video-* packages works by itself. For example, on a laptop with ATI Trinity [Radeon HD 7640G] integrated graphics:

tce-load -wi firmware-radeon xf86-video-ati => doesn't do anything
tce-load -wi firmware-radeon graphics-KERNEL => Bob's your uncle

Right now I'm not sure if the issue I'm experiencing with NVIDIA cards is due to

a) me testing in console only without Xorg
b) me not doing something appropriately or
c) NVIDIA is not supposed to work anyway due to missing proprietary drivers.
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 09:39:01 AM
Here's what I get with intel hardware when booting to the console prompt and then loading graphics-KERNEL.

Note that the console is already in uefi gfx fb mode.

Code: [Select]
$ tce-load -i graphics-KERNEL
$ dmesg
...
Linux agpgart interface v0.103
[drm] VT-d active for gfx access
checking generic (e0000000 410000) vs hw (e0000000 10000000)
fb: switching to inteldrmfb from EFI VGA
Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] DMAR active, disabling use of stolen memory
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 170x48
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
I would have thought you would see something analgous with nvidia hardware with perhaps an error message?
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 09:43:06 AM
..and if that doesn't come up with anything, I would suggest loading Xorg-7.7, "startx" and checking the xorg log for something analagous to:
Code: [Select]
[   241.729] (==) Matched intel as autoconfigured driver 0
[   241.729] (==) Matched modesetting as autoconfigured driver 1
[   241.729] (==) Matched fbdev as autoconfigured driver 2
[   241.729] (==) Matched vesa as autoconfigured driver 3
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 09:52:12 AM
Quote from: Juanito on June 26, 2019, 09:39:01 AM
Here's what I get with intel hardware when booting to the console prompt and then loading graphics-KERNEL.

Note that the console is already in uefi gfx fb mode.

Code: [Select]
$ tce-load -i graphics-KERNEL
$ dmesg
...
Linux agpgart interface v0.103
[drm] VT-d active for gfx access
checking generic (e0000000 410000) vs hw (e0000000 10000000)
fb: switching to inteldrmfb from EFI VGA
Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] DMAR active, disabling use of stolen memory
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 170x48
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
I would have thought you would see something analgous with nvidia hardware with perhaps an error message?

I too have copious dmesg messages on the Intel and Radeon machines. Just tested again on the NVIDIA Geforce GT 430 PC and I get the line with "Linux agpgart interface v0.103", but there is no more output after that.
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 10:18:18 AM
Quote from: Juanito on June 26, 2019, 09:43:06 AM
..and if that doesn't come up with anything, I would suggest loading Xorg-7.7, "startx" and checking the xorg log for something analagous to:
Code: [Select]
[   241.729] (==) Matched intel as autoconfigured driver 0
[   241.729] (==) Matched modesetting as autoconfigured driver 1
[   241.729] (==) Matched fbdev as autoconfigured driver 2
[   241.729] (==) Matched vesa as autoconfigured driver 3

Tested with

tce-load -wi graphics-KERNEL Xorg-7.7

startx => screen flickers a couple of times, I can see the TinyCore desktop background 2-3 times for about 300 ms in between flickers, then screen goes dark and stays that way, end of party, must reboot. Same behavior on both NVIDIA machines.

I get the sense that the graphics-KERNEL extension should setup the appropriate driver for the NVIDIA cards, however for some obscure reason it doesn't. Maybe there is an issue with the extension itself ?
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 10:34:08 AM
Quote from: SeventhSin on June 26, 2019, 09:52:12 AM
...
Code: [Select]
[drm] Driver supports precise vblank timestamp query.
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 170x48
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device[/code]
...
NVIDIA Geforce GT 430

BTW, It looks like your PC has an On-Chip Intel graphics?  you might have to disable this to force the Nvidia hardware.

There is no Nvidia driver in the current TC-10 repo which supports your hardware.

Meanwhile, you might be in luck, since a resent driver 390.87 supports both your GT 430 and my GTX 1060 machines.    I say this because Nvidia only allow compiling their proprietary driver on PC's with supporting hardware and TC-9x was the last Version with Nvidia support using nvidia-390.77 driver  http://tinycorelinux.net/9.x/x86/tcz/nvidia-390.77-4.14.10-tinycore.tcz.info and since no one has requested latest Nvifia driver I haven't submitted an extension for TC-10.x yet, standby I'll try to built the extension today
Code: [Select]
NVIDIA TITAN Series
NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN, GeForce GTX TITAN X, GeForce GTX TITAN Black, GeForce GTX TITAN Z
GeForce MX100 Series (Notebook)
GeForce MX150, GeForce MX130, GeForce MX110
GeForce 10 Series
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030
GeForce 10 Series (Notebooks)
GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050
GeForce 900 Series
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950
GeForce 900M Series (Notebooks)
GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M, GeForce 920M, GeForce 910M
GeForce 800M Series (Notebooks)
GeForce GTX 880M, GeForce GTX 870M, GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M, GeForce 825M, GeForce 820M, GeForce 810M, GeForce 800M
GeForce 700 Series
GeForce GTX 780 Ti, GeForce GTX 780, GeForce GTX 770, GeForce GTX 760, GeForce GTX 760 Ti (OEM), GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745, GeForce GT 740, GeForce GT 730, GeForce GT 720, GeForce GT 710, GeForce GT 705
GeForce 700M Series (Notebooks)
GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GT 755M, GeForce GT 750M, GeForce GT 745M, GeForce GT 740M, GeForce GT 735M, GeForce GT 730M, GeForce GT 720M, GeForce GT 710M, GeForce 720M, GeForce 710M, GeForce 705M
GeForce 600 Series
GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 645, GeForce GT 645, GeForce GT 640, GeForce GT 635, GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce 605
GeForce 600M Series (Notebooks)
GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 675M, GeForce GTX 670MX, GeForce GTX 670M, GeForce GTX 660M, GeForce GT 650M, GeForce GT 645M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 635M, GeForce GT 630M, GeForce GT 625M, GeForce GT 620M, GeForce 610M
GeForce 500 Series
GeForce GTX 590, GeForce GTX 580, GeForce GTX 570, GeForce GTX 560 Ti, GeForce GTX 560 SE, GeForce GTX 560, GeForce GTX 555, GeForce GTX 550 Ti, GeForce GT 545, GeForce GT 530, GeForce GT 520, GeForce 510
GeForce 500M Series (Notebooks)
GeForce GTX 580M, GeForce GTX 570M, GeForce GTX 560M, GeForce GT 555M, GeForce GT 550M, GeForce GT 540M, GeForce GT 525M, GeForce GT 520M, GeForce GT 520MX
GeForce 400 Series
GeForce GTX 480, GeForce GTX 470, GeForce GTX 465, GeForce GTX 460 SE v2, GeForce GTX 460 SE, GeForce GTX 460, GeForce GTS 450, GeForce GT 440, GeForce GT 430, GeForce GT 420
GeForce 400M Series (Notebooks)
GeForce GTX 485M, GeForce GTX 480M, GeForce GTX 470M, GeForce GTX 460M, GeForce GT 445M, GeForce GT 435M, GeForce GT 425M, GeForce GT 420M, GeForce GT 415M, GeForce 410M

Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 10:40:19 AM
Quote from: coreplayer2 on June 26, 2019, 10:34:08 AM
BTW, It looks like your PC has an On-Chip Intel graphics?  you might have to disable this to force the Nvidia hardware.

That is a quote from Juanito's message, it's not my output.

I do have a testing device with both Intel HD Graphics 530 and NVIDIA GeForce GTX 970M and installing graphics-KERNEL results in the extension setting up the Intel adapter (as I would expect). I haven't tested it yet, but turning off the Intel Video would probably result in the same behavior as on my other 2 NVIDIA only machines: nothing will happen.
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 10:45:03 AM
Quote from: SeventhSin on June 26, 2019, 10:18:18 AM
end of party, must reboot. Same behavior on both NVIDIA machines.

<ctl-alt-f1> and then "sudo killall Xorg" doesn't work (this would allow you to access the xorg log)?
Title: Re: TC & NVidia
Post by: Rich on June 26, 2019, 10:45:44 AM
Hi SeventhSin
Quote from: SeventhSin on June 26, 2019, 10:18:18 AM
... startx => screen flickers a couple of times, I can see the TinyCore desktop background 2-3 times for about 300 ms in between flickers, then screen goes dark and stays that way, end of party, must reboot. Same behavior on both NVIDIA machines. ...
After the screen goes dark, you could try hitting  Ctrl-Alt-F1  to see if it kicks you back into the console.
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 10:52:43 AM
To sum it up, I have the following setups:

1. PC with NVIDIA GeForce GT 740 card only => tce-load -wi graphics-KERNEL : no dmseg messages after "Linux agpgart interface v0.103", screen resolution doesn't change (fail)
2. PC with NVIDIA GeForce GT 430 card only => tce-load -wi graphics-KERNEL : no dmseg messages after "Linux agpgart interface v0.103", screen resolution doesn't change (fail)
3. Laptop with integrated Radeon HD 7640G only => tce-load -wi firmware-radeon graphics-KERNEL : screen resolution changes to max (success)
4. Laptop with integrated Intel HD Graphics 530 AND NVIDIA GeForce GTX 970M => tce-load -wi graphics-KERNEL : Intel driver loaded, screen resolution changes to max (success)

Note: tested on Core x86 (bare bone).
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 11:07:04 AM
Quote from: Rich on June 26, 2019, 10:45:44 AM
Hi SeventhSin
After the screen goes dark, you could try hitting  Ctrl-Alt-F1  to see if it kicks you back into the console.

Quote from: Juanito on June 26, 2019, 10:45:03 AM
<ctl-alt-f1> and then "sudo killall Xorg" doesn't work (this would allow you to access the xorg log)?

To be honest I didn't go that far. The lack of dmesg messages suggested to me that there is something the graphics-KERNEL extension doesn't do as expected.

Now, looking at the Xorg log I see that it does the following:

a) it searches for nouveau first => fail
b) it searches for nv => fail
c) it searches for fbdev => fail

It then defaults to vesa apparently.
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 11:17:25 AM
Both xf86-video-nv and xf86-video-nouveau are in the repo.
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 11:43:41 AM
Quote from: Juanito on June 26, 2019, 11:17:25 AM
Both xf86-video-nv and xf86-video-nouveau are in the repo.

Just run another battery of tests on the NVIDIA only machines.

tce-load -wi xf86-video-nouveau graphics-KERNEL Xorg-7.7
and
tce-load -wi xf86-video-nv graphics-KERNEL Xorg-7.7

In both cases the appropriate driver seems to be loaded, however following a long list of supported cards, there comes:

...
(WW) NV/Nouveau: Ignoring unsupported device _HEX_DEVICE_ID_GIBBERISG_ at HEX_OFFSET_GIBBERISH
(EE) open /dev/dri/card0: No such file or directory
(WW) Falling back to old probe method for modsetting
(EE) open /dev/dri/card0: No such file or directory
...

And the behavior is the same as before (screen flickering a bit then going black). Basically with or without installing xf86-video-nv|nouveau the end result is the same. If you guys think it's needed, I can SSH into the machines and pull the full Xorg logs. Let me know.
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 11:47:54 AM
The “dri/card0” message would disappear with Xorg-7.7-3d, the “unsupported_device” message doesn’t look promising though..
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 12:07:32 PM
Hello SeventhSin,

Please, you're just chasing your tail here...

Now the truth is coming to light....  You are in fact testing on three different machines with various types of hardware, but as far as I can tell we don't know which architecture you're using (eg:  TC -10 x86 or Tinycorepure64)?

NVIDIA GeForce GT 430
NVIDIA GeForce GT 740
NVIDIA GeForce GTX 970M

These are all fairly recent Nvidia Video cards which are not supported by either nouveau or nv drivers, these drivers are far too old, forget them.
However, In TC-10 these cards should be supported by the generic Xvesa (in TC-10 x86) and Xorg-7.7 (in TC-10 x86_64, I mean corepure64)

Additionally at least the GeForce GT 740 and GeForce GTX 970M have proprietary Nvidia driver support in TC-9  x86 and corepure64, am not sure about the 430 model

For TC-10 x86
My Geforce GTX 1060 video card at native resolution (and likely yours too) is supported by Xvesa extension
this is my onboot.lst (with personal extensions removed) which supports my Geforce GTX 1060 graphics card (without on chip i915 graphics)

Code: [Select]
fltk-1.3.tcz
freetype.tcz
imlib2-bin.tcz
imlib2.tcz
libfontenc.tcz
libICE.tcz
libjpeg-turbo.tcz
libpng.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libxcb.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXrender.tcz
libXt.tcz
Xlibs.tcz
Xprogs.tcz
Xvesa.tcz
wbar.tcz
libXrandr.tcz
libXpm.tcz
libXmu.tcz
libXi.tcz
libnl.tcz
libiw.tcz
aterm.tcz
hackedbox.tcz

For TC-10 x86_64 (tinycorepure64)
I currently use Xorg-7.7 which supports my Geforce GTX 1060 graphics card (without on chip i915 graphics) using this onboot.lst (with personal extensions removed)
Code: [Select]
aterm.tcz
fltk-1.3.tcz
freetype.tcz
glib2.tcz
harfbuzz.tcz
imlib2-bin.tcz
imlib2.tcz
libffi.tcz
libfontenc.tcz
libICE.tcz
libjpeg-turbo.tcz
libpng.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libxcb.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz
libXrender.tcz
libXt.tcz
pcre.tcz
wbar.tcz
Xlibs.tcz
Xorg-fonts.tcz
Xprogs.tcz
graphics-4.19.10-tinycore64.tcz
Xorg-7.7.tcz
firmware-rtl_nic.tcz
firmware-iwl8000.tcz
wifi.tcz
pciutils.tcz
hackedbox.tcz
aspell.tcz

Resulting Xorg log
Code: [Select]
[    46.673] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[    46.674] (II) Module vesa: vendor="X.Org Foundation"
[    46.674] compiled for 1.20.0, module version = 2.4.0
[    46.674] Module class: X.Org Video Driver
[    46.674] ABI class: X.Org Video Driver, version 24.0
[    46.674] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    46.674] (II) VESA: driver for VESA chipsets: vesa
[    46.674] (--) using VT number 2

[    46.678] (EE) open /dev/dri/card0: No such file or directory
[    46.678] (WW) Falling back to old probe method for modesetting
[    46.678] (EE) open /dev/dri/card0: No such file or directory
[    46.678] (EE) Screen 0 deleted because of no matching config section.
[    46.678] (II) UnloadModule: "modesetting"
[    46.678] (II) Loading sub module "vbe"
[    46.678] (II) LoadModule: "vbe"
[    46.678] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[    46.680] (II) Module vbe: vendor="X.Org Foundation"
[    46.680] compiled for 1.20.4, module version = 1.1.0
[    46.680] ABI class: X.Org Video Driver, version 24.0
[    46.680] (II) Loading sub module "int10"
[    46.680] (II) LoadModule: "int10"
[    46.681] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[    46.688] (II) Module int10: vendor="X.Org Foundation"
[    46.688] compiled for 1.20.4, module version = 1.0.0
[    46.688] ABI class: X.Org Video Driver, version 24.0
[    46.688] (II) VESA(0): initializing int10
[    46.689] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    46.718] (II) VESA(0): VESA BIOS detected
[    46.718] (II) VESA(0): VESA VBE Version 3.0
[    46.718] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[    46.718] (II) VESA(0): VESA VBE OEM: NVIDIA
[    46.718] (II) VESA(0): VESA VBE OEM Software Rev: 134.6
[    46.718] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[    46.718] (II) VESA(0): VESA VBE OEM Product: GP106 Board
[    46.718] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev   
[    46.767] (II) VESA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[    46.767] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[    46.767] (==) VESA(0): RGB weight 888
[    46.767] (==) VESA(0): Default visual is TrueColor
[    46.767] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[    46.767] (II) Loading sub module "ddc"
[    46.767] (II) LoadModule: "ddc"
[    46.767] (II) Module "ddc" already built-in
[    46.768] (II) VESA(0): VESA VBE DDC supported
[    46.768] (II) VESA(0): VESA VBE DDC Level 2
[    46.768] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
[    46.784] (II) VESA(0): VESA VBE DDC read successfully
[    46.784] (II) VESA(0): Manufacturer: LGD  Model: 46f  Serial#: 0
[    46.784] (II) VESA(0): Year: 2016  Week: 0
[    46.784] (II) VESA(0): EDID Version: 1.4
[    46.784] (II) VESA(0): Digital Display Input
[    46.784] (II) VESA(0): 6 bits per channel
[    46.784] (II) VESA(0): Digital interface is DisplayPort
[    46.784] (II) VESA(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[    46.784] (II) VESA(0): Gamma: 2.20
[    46.784] (II) VESA(0): DPMS capabilities: StandBy Suspend Off
[    46.784] (II) VESA(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[    46.784] (II) VESA(0): First detailed timing is preferred mode
[    46.784] (II) VESA(0): Preferred mode is native pixel format and refresh rate
[    46.784] (II) VESA(0): redX: 0.640 redY: 0.345   greenX: 0.335 greenY: 0.625
[    46.784] (II) VESA(0): blueX: 0.150 blueY: 0.052   whiteX: 0.313 whiteY: 0.329
[    46.784] (II) VESA(0): Manufacturer's mask: 0
[    46.784] (II) VESA(0): Supported detailed timing:
[    46.784] (II) VESA(0): clock: 138.7 MHz   Image Size:  344 x 194 mm
[    46.784] (II) VESA(0): h_active: 1920  h_sync: 1968  h_sync_end 2000 h_blank_end 2080 h_border: 0
[    46.784] (II) VESA(0): v_active: 1080  v_sync: 1083  v_sync_end 1088 v_blanking: 1111 v_border: 0
[    46.785] (II) VESA(0):  LG Display
[    46.785] (II) VESA(0):  LP156WF6-SPB6
[    46.785] (II) VESA(0): EDID (in hex):
[    46.785] (II) VESA(0): 00ffffffffffff0030e46f0400000000
[    46.785] (II) VESA(0): 001a010495221378eadc95a35855a026
[    46.785] (II) VESA(0): 0d505400000001010101010101010101
[    46.785] (II) VESA(0): 0101010101012e3680a070381f403020
[    46.785] (II) VESA(0): 350058c21000001a0000000000000000
[    46.785] (II) VESA(0): 00000000000000000000000000fe004c
[    46.785] (II) VESA(0): 4720446973706c61790a2020000000fe
[    46.785] (II) VESA(0): 004c503135365746362d535042360076
[    46.785] (II) VESA(0): EDID vendor "LGD", prod id 1135
[    46.785] (II) VESA(0): Printing DDC gathered Modelines:
[    46.785] (II) VESA(0): Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)

For now you can try any of the above
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 12:51:27 PM
One more thing..   Xfbdev extension works well on Nvidia Geforce GTX 1060 graphics card on TinyCorePure64, don't for get to add the appropriate bootcode (see info file) to load with correct resolution.
Title: Re: TC & NVidia
Post by: curaga on June 26, 2019, 01:06:35 PM
xf86-video-nv and the proprietary Nvidia driver will not affect the console resolution, they are both for Xorg only. So that part was expected.
Your cards are too new for xf86-video-nv like coreplayer2 mentions, so you should use the proprietary driver, if/when someone builds it.
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 01:26:16 PM
Quote from: coreplayer2 on June 26, 2019, 12:07:32 PM

Please, you're just chasing your tail here...


That is possible but not very probable. I am in fact well on my way of achieving my initial goal: ascertain if supporting NVIDIA cards on Core is something to be avoided.

Quote from: coreplayer2 on June 26, 2019, 12:07:32 PM
Now the truth is coming to light....  You are in fact testing on three different machines with various types of hardware, but as far as I can tell we don't know which architecture you're using (eg:  TC -10 x86 or Tinycorepure64)?

It's ok to miss that (forum threads tend to get swampy), but I do mention in the beginning of the thread and in some subsequent posts that I am testing on Core x86.

Quote from: coreplayer2 on June 26, 2019, 12:07:32 PM

NVIDIA GeForce GT 430
NVIDIA GeForce GT 740
NVIDIA GeForce GTX 970M

These are all fairly recent Nvidia Video cards which are not supported by either nouveau or nv drivers, these drivers are far too old, forget them.

The NVIDIA GeForce GT 430 is almost a decade old. I agree with you that the other two can be considered fairly recent (4-5 years old).

Thank you for the tips and for posting your configs. I'll be referring to these posts in the future if need arises.

I'm not aware of the advantages of Xvesa vs Nouveau. Is it more stable than Nouveau, or more performant, or both? Could you comment on your own experience on the subject?

 
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 01:29:38 PM
Quote from: curaga on June 26, 2019, 01:06:35 PM
xf86-video-nv and the proprietary Nvidia driver will not affect the console resolution, they are both for Xorg only. So that part was expected.

I wasn't aware of that, thank you @curaga.

Quote from: curaga on June 26, 2019, 01:06:35 PM
Your cards are too new for xf86-video-nv like coreplayer2 mentions, so you should use the proprietary driver, if/when someone builds it.

Yes, the cards not being supported in the current extension incarnations has indeed become salient, due to the input I've been receiving. Thank you again.
Title: Re: TC & NVidia
Post by: Juanito on June 26, 2019, 01:34:51 PM
Quote from: SeventhSin on June 26, 2019, 01:26:16 PM
I'm not aware of the advantages of Xvesa vs Nouveau. Is it more stable than Nouveau, or more performant, or both? Could you comment on your own experience on the subject?

Xvesa is a tiny x server, less performant than Xorg and nothing to do with the nouveau driver
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 02:57:11 PM
Hello SeventhSin

Quote
It's ok to miss that (forum threads tend to get swampy), but I do mention in the beginning of the thread and in some subsequent posts that I am testing on Core x86.
There's a lot of confusion here because while you've mentions once or twice "testing on core"  your first post asked for support for AMD and Nvidia Graphics drivers.  For many folks Core if often used as a starting platform to build a system with a desktop.

Quote from: SeventhSin on June 25, 2019, 03:17:27 PM
Hello,
Core-current (10.x, 32 bit)

For the most part Core runs in the frame buffer and is hardware independent.     Unless you have other intentions full 3D graphic support for all the above hardware is not required.  Otherwise it's better to compile the proprietary driver and extract only the required components for your specific usage.

Maybe better to state your goals?
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 04:00:59 PM
Quote from: SeventhSin on June 26, 2019, 01:26:16 PM
The NVIDIA GeForce GT 430 is almost a decade old. I agree with you that the other two can be considered fairly recent

[emoji112]

At its best the Nouveau open source driver was quite unreliable back 15+ years ago..

If you really need an NVIDIA driver there’s some good news, as a recent NVIDIA GeForce 390.87 driver appears to support all your NVIDIA hardware.

https://www.geforce.com/drivers/results/137275

The latest driver doesn’t support the GT 430
 Video card

Will attempt to build the 390.87 driver for TC-10


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 05:27:12 PM
Quote from: Juanito on June 26, 2019, 01:34:51 PM
Quote from: SeventhSin on June 26, 2019, 01:26:16 PM
I'm not aware of the advantages of Xvesa vs Nouveau. Is it more stable than Nouveau, or more performant, or both? Could you comment on your own experience on the subject?

Xvesa is a tiny x server, less performant than Xorg and nothing to do with the nouveau driver

I wrote that in a hurry and now that I'm able to glance again over my post, it does indeed look like a horrendous choice of words. Yes, XVesa is a tiny X server which "talks" to hardware via one driver only (the so called Vesa Bios Extension) as opposite to the more modular Xorg who can "talk" to hardware via multiple drivers.

What I meant was: how does Xvesa (Vesa BIOS Extensions) fare versus Xorg (with Nouveau as driver of choice).
Title: Re: TC & NVidia
Post by: SeventhSin on June 26, 2019, 05:40:03 PM
Quote from: coreplayer2 on June 26, 2019, 02:57:11 PM

For the most part Core runs in the frame buffer and is hardware independent.     Unless you have other intentions full 3D graphic support for all the above hardware is not required.  Otherwise it's better to compile the proprietary driver and extract only the required components for your specific usage.

Maybe better to state your goals?

Yes, you are right, I should state my goals more clearly. Have to run now, but I'll post tomorrow with a couple of clarifications.
Title: Re: TC & NVidia
Post by: coreplayer2 on June 26, 2019, 10:43:14 PM
Hello SeventhSin

Each year there's always some glitch that makes building Nvidia drivers challenging, this year it was just a couple of missing or renamed dependencies;
libelf-dev and
procps-ng


In the end "NVIDIA x86_64 Driver 390.87" which should support all your NVIDIA hardware was successful

From Xorg Log
Code: [Select]
[  1104.992]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[  1104.992] Build Operating System: Linux 4.19.10-tinycore64 x86_64
[  1104.992] Current Operating System: Linux box 4.19.10-tinycore64 #1999 SMP Tue Dec 18 15:18:54 UTC 2018 x86_64
[  1104.992] Kernel command line: BOOT_IMAGE=/boot/vmlinuz64-41910 noswap tz=GMT loglevel=3 waitusb=5:UUID=b313c2c4-fedf-4c44-bf42-6a6fca54b311 tce=UUID=b313c2c4-fedf-4c44-bf42-6a6fca54b311/tc10-x86_64 opt=UUID=b313c2c4-fedf-4c44-bf42-6a6fca54b311 home=UUID=b313c2c4-fedf-4c44-bf42-6a6fca54b311
[  1104.992] Build Date: 04 March 2019  10:59:41AM
...
[  1104.998] (II) LoadModule: "glx"
[  1104.999] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[  1105.007] (II) Module glx: vendor="NVIDIA Corporation"
[  1105.007] compiled for 4.0.2, module version = 1.0.0
[  1105.007] Module class: X.Org Server Extension
[  1105.007] (II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
[  1105.007] (II) LoadModule: "nvidia"
[  1105.008] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so
[  1105.008] (II) Module nvidia: vendor="NVIDIA Corporation"
[  1105.008] compiled for 4.0.2, module version = 1.0.0
[  1105.008] Module class: X.Org Video Driver
[  1105.009] (II) NVIDIA dlloader X Driver  390.87  Tue Aug 21 15:44:49 PDT 2018
[  1105.009] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  1105.009] (--) using VT number 2

[  1105.017] (II) Loading sub module "fb"
[  1105.017] (II) LoadModule: "fb"
[  1105.017] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[  1105.018] (II) Module fb: vendor="X.Org Foundation"
[  1105.018] compiled for 1.20.4, module version = 1.0.0
[  1105.018] ABI class: X.Org ANSI C Emulation, version 0.4
[  1105.018] (II) Loading sub module "wfb"
[  1105.018] (II) LoadModule: "wfb"
[  1105.018] (II) Loading /usr/local/lib/xorg/modules/libwfb.so
[  1105.021] (II) Module wfb: vendor="X.Org Foundation"
[  1105.021] compiled for 1.20.4, module version = 1.0.0
[  1105.021] ABI class: X.Org ANSI C Emulation, version 0.4
[  1105.021] (II) Loading sub module "ramdac"
[  1105.021] (II) LoadModule: "ramdac"
[  1105.021] (II) Module "ramdac" already built-in
[  1105.040] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[  1105.040] (==) NVIDIA(0): RGB weight 888
[  1105.040] (==) NVIDIA(0): Default visual is TrueColor
[  1105.040] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  1105.040] (**) NVIDIA(0): Enabling 2D acceleration
[  1106.017] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[  1106.017] (--) NVIDIA(0):     DFP-0
[  1106.017] (--) NVIDIA(0):     DFP-1
[  1106.017] (--) NVIDIA(0):     DFP-2 (boot)
[  1106.017] (--) NVIDIA(0):     DFP-3
[  1106.017] (--) NVIDIA(0):     DFP-4
[  1106.017] (--) NVIDIA(0):     DFP-5
[  1106.020] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1060 (GP106-B) at PCI:1:0:0 (GPU-0)
[  1106.020] (--) NVIDIA(0): Memory: 3145728 kBytes
[  1106.020] (--) NVIDIA(0): VideoBIOS: 86.06.3e.00.08
[  1106.020] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  1106.020] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  1106.020] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[  1106.020] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[  1106.020] (--) NVIDIA(GPU-0):
[  1106.021] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  1106.021] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  1106.021] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  1106.021] (--) NVIDIA(GPU-0):
[  1106.021] (--) NVIDIA(GPU-0): LGD (DFP-2): connected
[  1106.021] (--) NVIDIA(GPU-0): LGD (DFP-2): Internal DisplayPort
[  1106.021] (--) NVIDIA(GPU-0): LGD (DFP-2): 1440.0 MHz maximum pixel clock
[  1106.021] (--) NVIDIA(GPU-0):
[  1106.021] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  1106.021] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  1106.021] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  1106.021] (--) NVIDIA(GPU-0):
[  1106.021] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  1106.021] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[  1106.021] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[  1106.021] (--) NVIDIA(GPU-0):
[  1106.021] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  1106.021] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[  1106.021] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[  1106.021] (--) NVIDIA(GPU-0):
[  1106.022] (==) NVIDIA(0):
[  1106.022] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[  1106.022] (==) NVIDIA(0):     will be used as the requested mode.
[  1106.022] (==) NVIDIA(0):
[  1106.022] (II) NVIDIA(0): Validated MetaModes:
[  1106.022] (II) NVIDIA(0):     "DFP-2:nvidia-auto-select"
[  1106.022] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[  1106.024] (--) NVIDIA(0): DPI set to (143, 144); computed from "UseEdidDpi" X config
[  1106.024] (--) NVIDIA(0):     option
[  1106.024] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[  1106.024] (II) NVIDIA:     access.
[  1106.058] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  1106.058] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  1106.058] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  1106.058] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  1106.058] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  1106.058] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  1106.058] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  1106.058] (II) NVIDIA(0):     Config Options in the README.
[  1106.073] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[  1107.016] (==) NVIDIA(0): Disabling shared memory pixmaps
[  1107.016] (==) NVIDIA(0): Backing store enabled
[  1107.016] (==) NVIDIA(0): Silken mouse enabled
[  1107.016] (**) NVIDIA(0): DPMS enabled
[  1107.016] (II) Loading sub module "dri2"
[  1107.016] (II) LoadModule: "dri2"
[  1107.017] (II) Module "dri2" already built-in
[  1107.017] (II) NVIDIA(0): [DRI2] Setup complete
[  1107.017] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[  1107.017] (II) Initializing extension Generic Event Extension
[  1107.017] (II) Initializing extension SHAPE
[  1107.017] (II) Initializing extension MIT-SHM
[  1107.017] (II) Initializing extension XInputExtension
[  1107.017] (II) Initializing extension XTEST
[  1107.017] (II) Initializing extension BIG-REQUESTS
[  1107.017] (II) Initializing extension SYNC
[  1107.017] (II) Initializing extension XKEYBOARD
[  1107.017] (II) Initializing extension XC-MISC
[  1107.017] (II) Initializing extension XFIXES
[  1107.017] (II) Initializing extension RENDER
[  1107.017] (II) Initializing extension RANDR
[  1107.017] (II) Initializing extension COMPOSITE
[  1107.017] (II) Initializing extension DAMAGE
[  1107.017] (II) Initializing extension MIT-SCREEN-SAVER
[  1107.017] (II) Initializing extension DOUBLE-BUFFER
[  1107.017] (II) Initializing extension RECORD
[  1107.017] (II) Initializing extension DPMS
[  1107.017] (II) Initializing extension Present
[  1107.017] (II) Initializing extension DRI3
[  1107.017] (II) Initializing extension X-Resource
[  1107.017] (II) Initializing extension XVideo
[  1107.017] (II) Initializing extension XVideo-MotionCompensation
[  1107.017] (II) Initializing extension XFree86-VidModeExtension
[  1107.017] (II) Initializing extension XFree86-DGA
[  1107.017] (II) Initializing extension XFree86-DRI
[  1107.017] (II) Initializing extension DRI2
[  1107.017] (II) Initializing extension GLX
[  1107.017] (II) Initializing extension GLX
[  1107.017] (II) Indirect GLX disabled.
[  1107.017] (II) Initializing extension NV-GLX
[  1107.017] (II) Initializing extension NV-CONTROL
[  1107.017] (II) Initializing extension XINERAMA
...
[  1189.642] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[  1189.642] (--) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[  1189.642] (--) NVIDIA(GPU-0):
[  1189.642] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  1189.642] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  1189.642] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  1189.642] (--) NVIDIA(GPU-0):
[  1189.642] (--) NVIDIA(GPU-0): LGD (DFP-2): connected
[  1189.642] (--) NVIDIA(GPU-0): LGD (DFP-2): Internal DisplayPort
[  1189.642] (--) NVIDIA(GPU-0): LGD (DFP-2): 1440.0 MHz maximum pixel clock
[  1189.642] (--) NVIDIA(GPU-0):
[  1189.643] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  1189.643] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  1189.643] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  1189.643] (--) NVIDIA(GPU-0):
[  1189.643] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  1189.643] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[  1189.643] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[  1189.643] (--) NVIDIA(GPU-0):
[  1189.643] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  1189.643] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[  1189.643] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[  1189.643] (--) NVIDIA(GPU-0):

Will tackle the x86 version tomorrow
Title: Re: TC & NVidia
Post by: coreplayer2 on June 27, 2019, 01:45:57 AM
Ok we’re getting ready to submit to the repo
But I don’t think you need all the X support modules as it make the extension huge

(https://uploads.tapatalk-cdn.com/20190627/164d2dd9df140180a533f5a387305a15.jpg)


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: curaga on June 27, 2019, 03:07:04 AM
Vesa is limited to certain resolutions, and has no 2d acceleration. Nouveau has accel, but it's unstable and not able to reclock many nvidia cards. So it depends on any particular card if it's even faster than vesa.
Title: Re: TC & NVidia
Post by: SeventhSin on June 27, 2019, 08:45:43 AM
Quote from: curaga on June 27, 2019, 03:07:04 AM
Vesa is limited to certain resolutions, and has no 2d acceleration. Nouveau has accel, but it's unstable and not able to reclock many nvidia cards. So it depends on any particular card if it's even faster than vesa.

Thank you for clarifying, curaga.

Quote from: coreplayer2 on June 27, 2019, 01:45:57 AM
Ok we’re getting ready to submit to the repo


Fantastic coreplayer2 ! Great news. Thank you for investing your time to build this. Could you please clarify for me what you mean by:

Quote from: coreplayer2 on June 27, 2019, 01:45:57 AM
But I don’t think you need all the X support modules as it make the extension huge

Namely, what support modules are you referring to ?
Title: Re: TC & NVidia
Post by: SeventhSin on June 27, 2019, 09:12:39 AM
Quote from: coreplayer2 on June 26, 2019, 02:57:11 PM
For the most part Core runs in the frame buffer and is hardware independent.     Unless you have other intentions full 3D graphic support for all the above hardware is not required.  Otherwise it's better to compile the proprietary driver and extract only the required components for your specific usage.

Maybe better to state your goals?

As promised, I shall better clarify my goals (and subsequently the purpose of the thread):

I am building a platform with Core x86|x64 as its base. It is not meant to be a (Tiny)Core spin off, but rather vanilla Core with a minimum number of built-in tweaks necessary to enable dynamic on the fly configuration of the system according to variables detected at run-time. Since the system will be PXE booted, the size of the base image is very important, that is why I am performing all my testing on Core as opposite to TinyCore (GUI version).

Currently I'm in the process of getting used to (Tiny)Core's graphics subsystem. My goal at this stage is to identify how many graphics systems (cards) "work" with whatever is present in the repos right now. Because my goal is not to "get a specific card to work", I am testing on different hardware.

I hope this clarifies it a bit.
Title: Re: TC & NVidia
Post by: coreplayer2 on June 27, 2019, 04:43:13 PM
Quote from: SeventhSin on June 27, 2019, 08:45:43 AM
Namely, what support modules are you referring to ?
Hello [emoji112]
Hmmm...  while the kernel module is still relatively large even in compressed form, the GLX, OpenGL modules supporting Xorg make up 80% of the 40+mb size of the NVIDIA extension. 
I’ve already separated OpenCL, Cuda and documentation into their own extensions.
I’m suspecting you’ll need to separate the kernel modules for your needs.

Anyhow 32bit and 64bit NVIDIA extensions are complete, will upload to submissions ASAP



Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: SeventhSin on June 27, 2019, 04:57:45 PM
Quote from: coreplayer2 on June 27, 2019, 04:43:13 PM
Anyhow 32bit and 64bit NVIDIA extensions are complete, will upload to submissions ASAP

Awesome coreplayer2 !

What will I be looking for in the repo ? Something like nvidia-390.87-4.19.10-tinycore.tcz & friends ?

Title: Re: TC & NVidia
Post by: Rich on June 27, 2019, 05:08:44 PM
Hi coreplayer2
Quote from: coreplayer2 on June 27, 2019, 04:43:13 PM
Hmmm...  while the kernel module is still relatively large even in compressed form, the GLX, OpenGL modules supporting Xorg make up 80% of the 40+mb size of the NVIDIA extension. ...
OK, I'll ask the obvious question. Did you  strip  the binaries?
Title: Re: TC & NVidia
Post by: coreplayer2 on June 27, 2019, 05:37:34 PM
Hello Rich
Not yet stripped but that occurs with submitqc --fix

then final testing
Title: Re: TC & NVidia
Post by: coreplayer2 on June 27, 2019, 06:19:21 PM
Hi Rich

checking the Nvidia pre-compiled binaries I find they're all stripped

Code: [Select]
/mnt/sdb3/tc10-x86/optional/nvidia-390.87-4.19.10-tinycore/usr/lib $ file *.so.390.87
libEGL_nvidia.so.390.87:       ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libGLESv1_CM_nvidia.so.390.87: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libGLESv2_nvidia.so.390.87:    ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libGLX_nvidia.so.390.87:       ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-cfg.so.390.87:       ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-eglcore.so.390.87:   ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-encode.so.390.87:    ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-fbc.so.390.87:       ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-glcore.so.390.87:    ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-glsi.so.390.87:      ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-gtk2.so.390.87:      ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-gtk3.so.390.87:      ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-ifr.so.390.87:       ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
libnvidia-ml.so.390.87:        ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
/mnt/sdb3/tc10-x86/optional/nvidia-390.87-4.19.10-tinycore/usr/local/lib/xorg/modules/drivers $ file *.so.390.87
nvidia_drv.so: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped
/mnt/sdb3/tc10-x86/optional/nvidia-390.87-4.19.10-tinycore/usr/local/lib/xorg/modules/extensions $ file *.so.390.87
libglx.so.390.87: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped

Next up to strip the kernel compatible binaries but iirc I haven't always had the best results stripping those...   will check
Code: [Select]
/mnt/sdb3/tc10-x86/optional/nvidia-390.87-4.19.10-tinycore/usr/local/lib/modules/4.19.10-tinycore/kernel/drivers/video $ file *.ko
nvidia-modeset.ko: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), BuildID[sha1]=52d5cd9261667170ef0936e57cf8dd23210e1758, stripped
nvidia.ko:         ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), BuildID[sha1]=7d6a4024414054768f07c704dc79964f8badd8d0, stripped
Title: Re: TC & NVidia
Post by: coreplayer2 on June 27, 2019, 07:12:34 PM
Hello Rich

Now I remember..

Code: [Select]
/mnt/sdb3/tc10-x86/optional/nvidia-390.87-4.19.10-tinycore/usr/local/lib/modules/4.19.10-tinycore/kernel/drivers/video $ file *.ko
nvidia-modeset.ko: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), BuildID[sha1]=52d5cd9261667170ef0936e57cf8dd23210e1758, stripped
nvidia.ko:         ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), BuildID[sha1]=7d6a4024414054768f07c704dc79964f8badd8d0, stripped
Stripped to the maximum extent as shown above where file reports "Stripped" renders the binary unusable.  However --strip-unneeded strips the minimum whilst maintaining usability. 
So that's currently where we're at!
Title: Re: TC & NVidia
Post by: SeventhSin on June 28, 2019, 07:04:09 AM
@coreplayer2

Would it be possible to have the extension bump the screen resolution to max before startx ? If there isn't any compelling reason not to do it, this would be useful on "X-less" Core x86. It would also make behavior more consistent across video extensions (check: http://forum.tinycorelinux.net/index.php/topic,22991.0.html (http://forum.tinycorelinux.net/index.php/topic,22991.0.html)).

RIGHT NOW:
tce-load -wi graphics-KERNEL : immediate screen resolution bump, before startx
tce-load -wi xf86-video-intel : immediate screen resolution bump, before startx

DESIRABLE:
tce-load -wi graphics-KERNEL : immediate screen resolution bump, before startx
tce-load -wi xf86-video-intel : immediate screen resolution bump, before startx
tce-load -wi nvidia-390.87-4.19.10-tinycore : immediate screen resolution bump, before startx
Title: Re: TC & NVidia
Post by: Juanito on June 28, 2019, 07:43:55 AM
xf86-video-intel is an xorg driver and thus will not change anything before "startx" - it has graphics-KERNEL.tcz as a dep, which is what changes the resolution.
Title: Re: TC & NVidia
Post by: SeventhSin on June 28, 2019, 08:24:02 AM
Quote from: Juanito on June 28, 2019, 07:43:55 AM
xf86-video-intel is an xorg driver and thus will not change anything before "startx" - it has graphics-KERNEL.tcz as a dep, which is what changes the resolution.

Yes, the post linked above mentions this fact. Please have a look.
Title: Re: TC & NVidia
Post by: curaga on June 28, 2019, 01:05:06 PM
It is not possible for the proprietary Nvidia drivers to change the console resolution. That would require Nvidia to have a change of heart and release the drivers as open source.
Title: Re: TC & NVidia
Post by: coreplayer2 on June 28, 2019, 01:33:54 PM
Hi
I think the Boot Manager like Grub2 cantrol the resolution from the beginning then pass the resolution to the kernel..?
Title: Re: TC & NVidia
Post by: SeventhSin on June 28, 2019, 04:56:07 PM
Quote from: coreplayer2 on June 28, 2019, 01:33:54 PM
Hi
I think the Boot Manager like Grub2 cantrol the resolution from the beginning then pass the resolution to the kernel..?

What I'm trying to achieve is reliably set-up the display @ native resolution. I think Grub2 is able to detect the native resolution of the screen and pass that to the KERNEL in the case of an UEFI boot.

Unfortunately I can't make use of that. Boot-wise, my requirements are:

a) IPXE boot-loader
b) support non-UEFI systems.
Title: Re: TC & NVidia
Post by: coreplayer2 on June 28, 2019, 08:14:02 PM
Hello
I think Grub2 can handle resolution with either EFI or legacy MBR based boot.  However the unknown is PXE ??


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: SeventhSin on June 29, 2019, 01:26:11 PM
Quote from: coreplayer2 on June 28, 2019, 08:14:02 PM
Hello
I think Grub2 can handle resolution with either EFI or legacy MBR based boot.  However the unknown is PXE ??

I am as certain as humanly possible that IPXE can't achieve that.
Title: Re: TC & NVidia
Post by: coreplayer2 on June 29, 2019, 01:29:45 PM
Quote from: SeventhSin on June 29, 2019, 01:26:11 PM
Quote from: coreplayer2 on June 28, 2019, 08:14:02 PM
Hello
I think Grub2 can handle resolution with either EFI or legacy MBR based boot.  However the unknown is PXE ??

I am as certain as humanly possible that IPXE can't achieve that.
Only one way to find out
[emoji12]


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: coreplayer2 on July 01, 2019, 06:18:14 PM
Quote from: SeventhSin on June 27, 2019, 04:57:45 PM
Quote from: coreplayer2 on June 27, 2019, 04:43:13 PM
Anyhow 32bit and 64bit NVIDIA extensions are complete, will upload to submissions ASAP

Awesome coreplayer2 !

What will I be looking for in the repo ? Something like nvidia-390.87-4.19.10-tinycore.tcz & friends ?
Both x86 and x86_64 repos have NVIDIA driver extensions now.  While I previously separated Cuda & OpenCL modules,  separating accelerated 3D GLX & OpenGL binaries for Xorg is still a work in progress.. 
when finished the kernel and Xorg modules will be:
nvidia-390.87-4.19.10-tinycore.tcz
nvidia-390.87-4.19.10-tinycore64.tcz

And significantly smaller (a 75% reduction is expected)
Until then you’ll get the full Xorg supporting binaries.  Im interested to know if all your Nvidia devices are supported?

Regards




Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: hiro on July 03, 2019, 01:31:10 AM
Quote from: curaga on June 28, 2019, 01:05:06 PM
It is not possible for the proprietary Nvidia drivers to change the console resolution. That would require Nvidia to have a change of heart and release the drivers as open source.
I seem to disagree with the wishes of most people taking part of this thread...

In my opinion the console shouldn't switch to high resolutions for *any* graphics card.
Ever since this kms stuff got introduced there was nothing but problems.

additional reason: imagine you need to debug something where not even Xorg comes up any more, and you add a (low-resolution) monitor (let's say you are on some consumer device without serial line).

if you really want high resolution you're going to be using xorg anyway, please leave the console alone, so there's at least *something* left that works!

not like you guys are at fault here, i'd have to talk to the linux people, intel, amd. but just in case you have any reach or say, please keep it in mind. thank you :)
Title: Re: TC & NVidia
Post by: PDP-8 on July 03, 2019, 02:59:50 AM
Hiro - I like the console too, so I know exactly where you are coming from..

And I'm lovin' life with only Xfbdev running full-resolution in X with Terminus bitmap fonts.  They look *great* at native resolution.

BUT, If I crash even the tiny-x server, and I want a better looking font for debugging, I'll reboot and use the "nomodeset" bootcode.  That usually results in a better looking console font for debugging.  Maybe not great, but big enough to be useful.  Or maybe just remove the graphics driver from onboot.lst

But back to Terminus - I never compiled the terminus-fonts.tcz with the ability to do console fonts - just the X server only.

Sooo ... in other systems where you may still be running at native resolution, but virtual terminal consoles basically are invisible, I like to add the terminus fonts package from their repos and set the console font

dpkg-reconfigure setconsolefont

Debian, Slackware, Raspbian etc etc similar and choose Terminus.  Now you can run at native res, but STILL have nice large good looking console fonts.

Unfortunately, I wasn't skilled enough to include console fonts in Terminus - maybe some other skilled user could take that on?  hint-hint :)
Title: Re: TC & NVidia
Post by: SeventhSin on July 03, 2019, 06:32:32 AM
Quote from: hiro on July 03, 2019, 01:31:10 AM
additional reason: imagine you need to debug something where not even Xorg comes up any more, and you add a (low-resolution) monitor (let's say you are on some consumer device without serial line).

I can't help but wonder what are the odds for such an edge case to become manifest. Quite a number of "stars" need to align to make it possible:

a) some mega-issue pops its ugly head up
b) the device has no serial line
c) the device has no form of remote-ing available
d) the default monitor is unusable so that one needs to add
e) an ancient monitor that is so low resolution it is unusable due to high console resolution
f) the device can't be booted from from CD, USB or PXE, hence impossible to boot from another (Tiny)Core image and peek @ the logs and/or troubleshoot from there

Id does seem like a misuse of the imagination IMO.  :o
Title: Re: TC & NVidia
Post by: PDP-8 on July 03, 2019, 03:43:48 PM
Well, a mega-issue to cause this can be done by moving, deleting or misconfiguring the location of your tce directory.  Which dumps you to the command prompt.

Although rebooting in even this borked condition for debugging the fix, the console fonts have some weird quirks - like doing a long dmesg listing - and having the screen scroll the file just half-way down the screen.

This is where rebooting with the
nomodeset
bootcode can come in handy.  Now you'll have the default vga font AND working the way one expects.

I think Hiro was facing the same dilemna as I was a few years ago when starting to use high-resolution screens, but now the virtual terminals are teensy-weensy.

The simplest solution is to just add a console-font to the system, like Terminus, (although the one in the apps repo is for x-only) and use a utility to set that font and size for the virtual consoles.
Title: Re: TC & NVidia
Post by: SeventhSin on July 03, 2019, 03:59:34 PM
The NVIDIA proprietary driver extension doesn't bump the screen resolution to native pre-X anyway.

xf86-video-intel was doing it by default and this thread http://forum.tinycorelinux.net/index.php/topic,22991.0.html (http://forum.tinycorelinux.net/index.php/topic,22991.0.html) details why xf86-video-ati & xf86-video-radeon have been tweaked by Juanito to do the same. IMO there isn't any reason to worry.
Title: TC & NVidia
Post by: coreplayer2 on July 03, 2019, 04:38:51 PM
Quote from: SeventhSin on July 03, 2019, 03:59:34 PM
The NVIDIA proprietary driver extension doesn't bump the screen resolution to native pre-X anyway.
More interesting to me is if the prop driver supports all your test hardware ?


Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: SeventhSin on July 03, 2019, 04:47:34 PM
Quote from: coreplayer2 on July 03, 2019, 04:38:51 PM
Quote from: SeventhSin on July 03, 2019, 03:59:34 PM
The NVIDIA proprietary driver extension doesn't bump the screen resolution to native pre-X anyway.
More interesting to me is if the prop driver supports all your test hardware ?


Sent from my iPhone using Tapatalk

I have a battery of tests planned for tomorrow morning. I will test your extension on all the hardware available and let you know.
Title: Re: TC & NVidia
Post by: SeventhSin on July 05, 2019, 11:10:39 AM
Quote from: coreplayer2 on July 03, 2019, 04:38:51 PM
More interesting to me is if the prop driver supports all your test hardware ?

Core 10.1, testing on the NVIDIA GeForce GT 740 graphics card only machine, no other embedded VGA available.

tce-load -wi flwm_topside wbar mc nano pci-utils lxterminal Xorg-7.7-3d nvidia-390.87-4.19.10-tinycore

startx fails as expected, there is no Xorg.conf file available set-up for NVIDIA. Cool, maybe try and generate one:

sudo nvidia-xconfig => fail:

Code: [Select]
WARNING: Unable to locate/open X configuration file.
ps: invaild option --'c'
The above is followed by a bunch of BusyBox related gibberish, followed by:

Code: [Select]
sh: pkg-config: not found

ERROR: Unable to write to directory '/etc/X11'

Installing pkg-config and the above becomes:

Code: [Select]
Package xorg-server was not found in the pkg-config search path.

Perhaps you should add the directory containing 'xorg-server.pc'.
No package 'xorg-server' found.

ERROR: Unable to write to directory '/etc/X11'

I also tested on another machine with embedded graphics. Here I get X. Of course, launching the nvidia app leads to a pop-up suggesting to run nvidia-xconfig as root and restart X. Doing that leads to the same behavior as above, so no difference there.

Here's what I got up to now. Don't have more time to play with this until later this evening.

Suggestions & fixes welcome, of course.
Title: Re: TC & NVidia
Post by: coreplayer2 on July 05, 2019, 12:52:03 PM
Quote from: SeventhSin on July 05, 2019, 11:10:39 AM
...
sudo nvidia-xconfig => fail:
...
Suggestions & fixes welcome, of course.

Great, but did you read all the install notes within the info file first?
http://tinycorelinux.net/10.x/x86/tcz/nvidia-390.87-4.19.10-tinycore.tcz.info

In tinycore it is expected to read the extension info file before installing,  indeed it is the default action of tce-ab from the command line to view the "extension_name.info" file before installing

I have previously considered installing a generic /etc/X11/xorg.conf file if one didn't exist via the extension install file but am not sure a generic conf file would work an any scenario.. Which brings us back to the "On first install" routine.

 
Title: Re: TC & NVidia
Post by: SeventhSin on July 05, 2019, 01:47:40 PM
Quote from: coreplayer2 on July 05, 2019, 12:52:03 PM
Great, but did you read all the install notes within the info file first?
http://tinycorelinux.net/10.x/x86/tcz/nvidia-390.87-4.19.10-tinycore.tcz.info

Code: [Select]
Or use "nvidia-xconfig", you may need to install
these additional dependencies:
Xorg-7.7-3d-dev.tcz
xorg-server-dev.tcz
pkg-config.tcz
autoconf.tcz
bash.tcz.
run "mkdir -p /etc/X11"
run "sudo nvidia-xconfig"
run "startx"
then add /etc/X11/xorg.conf to your backup
Oopsie... busted!  :o

My initial working assumption was that the extension would configure the system fully. My noggin automatically made it, because as a developer I follow the fundamental principle of never trusting the user and naturally I thought everybody follows it too.  My bad.  ::)

I'll test again after my machines are done building. I think I have a couple of suggestions, but I want to test my assumptions first. In the interim, I'm thinking (out-loud):

a) Maybe the simplest and safest path would be to add the nvidia-xconfig dependencies to the driver extension as well?
b) Maybe saving a couple of MB is not worth the trouble of optimizing too much, because...

Quote from: coreplayer2 on July 05, 2019, 12:52:03 PM
In tinycore it is expected to read the extension info file before installing,  indeed it is the default action of tce-ab from the command line to view the "extension_name.info" file before installing

... the above expectation will be probably violated time and time again.  :-X
Title: Re: TC & NVidia
Post by: PDP-8 on July 05, 2019, 03:20:04 PM
Just a reminder : don't forget to evaluate our related project, dCore, for your project needs.

It might reduce some of the toolkit-approach to getting your X needs / drivers together, yet at the same time seem to have much the same overall objectives as TinyCore.  The same, but different. :)

Skills learned in one benefit the other, and one may end up being a better fit for your project.  All without leaving the fold so to speak...
Title: Re: TC & NVidia
Post by: Rich on July 05, 2019, 04:41:24 PM
Hi SeventhSin
Quote from: SeventhSin on July 05, 2019, 01:47:40 PM
... b) Maybe saving a couple of MB is not worth the trouble of optimizing too much, because...

Quote from: coreplayer2 on July 05, 2019, 12:52:03 PM
In tinycore it is expected to read the extension info file before installing,  indeed it is the default action of tce-ab from the command line to view the "extension_name.info" file before installing

... the above expectation will be probably violated time and time again.  :-X

From  http://tinycorelinux.net/welcome.html:
Quote
The user has complete control over which applications and/or additional hardware to have supported, be it for a desktop, a netbook, an appliance, or server, selectable by the user by installing additional applications from online repositories, or easily compiling most anything you desire using tools provided.

From http://tinycorelinux.net/intro.html:
Quote
Not a 'turnkey' operating system. Tiny Core can help you do what you need to do, but Tiny Core stays tiny by not including tools like a browser or word processor (but Tiny Core can help you download and install those really quickly).


Not for everyone. Tiny Core is fast, powerful, and flexible. You can use Tiny Core without much technical knowledge, but, like any strong tool, Tiny Core becomes really useful if you know how to use it. Great starter skills could include command line usage, simple shell scripting, and Linux file and permission management, and some reasonably fast typing skills.
Based on those quotes, I would suggest reading is always a requirement when using a distro such as this. Of course, you would
have had to read the quoted pages in the first place to realize that. :)
Title: Re: TC & NVidia
Post by: SeventhSin on July 05, 2019, 05:02:12 PM
Quote from: Rich on July 05, 2019, 04:41:24 PM
Based on those quotes, I would suggest reading is always a requirement when using a distro such as this. Of course, you would
have had to read the quoted pages in the first place to realize that. :)

Am I in the process of getting ... politically spanked?  :o
Title: Re: TC & NVidia
Post by: coreplayer2 on July 05, 2019, 05:28:29 PM
LOL

Sorry it wasn't meant that way, just showing where to look for install instructions.

Meanwhile Xorg doesn't necessarily need an /etc/X11/Xorg.conf file any more.   However Xorg loads appropriate drivers if it know where to look.   So I created a default Xorg.conf.d nvidia config file which appears to work as expected.

I've added code to the Nvidia extension startup script to create this default Xorg Nvidia config file, meanwhile you may try this script
Code: [Select]
#!/bin/sh

if [ ! -e /usr/local/share/X11/xorg.conf.df/20-Nvidia.conf ]; then
sudo touch /usr/local/share/X11/xorg.conf.d/20-Nvidia.conf
sudo chmod a=rw /usr/local/share/X11/xorg.conf.d/20-Nvidia.conf
cat <<EOF >/usr/local/share/X11/xorg.conf.d/20-Nvidia.conf

Section "Device"
        Identifier "Nvidia Card"
        Driver "nvidia"
        VendorName "NVIDIA Corporation"
EndSection


EOF

fi


Usual procedure: create an executable file where you can execute it on next boot,  copy and save the above code to the it.   Run the script before running " startx "

Results may depend on your hardware, but I think you'll be successful with this.


But please don't forget this on 32bit installations,
Quote
NOTE: Some Nvidia cards require to specify a vmalloc limit on 32bit kernels therefore consider
      adding vmalloc=256MB to your boot config command line otherwise the driver may fail to load
      eg "linux /boot/vmlinuz vmalloc=256MB"
YMMV try 256MB first, 384MB works best for my system
Title: Re: TC & NVidia
Post by: SeventhSin on July 05, 2019, 06:31:20 PM
Quote from: coreplayer2 on July 05, 2019, 05:28:29 PM
LOL

Sorry it wasn't meant that way, just showing where to look for install instructions.

@coreplayer2, no need to be sorry, you are perfectly right to pinpoint that there are in fact installation instructions and those should be read. I was addressing Rich, who seemed willing to give me a good spanking for skipping release notes.  ::)

Going to test the proprietary extension ASAP. Keep you posted.
Title: Re: TC & NVidia
Post by: coreplayer2 on July 05, 2019, 09:06:09 PM
Oooops my bad, I just noticed a typo in this script

Corrected
Code: [Select]
#!/bin/sh

if [ ! -e /usr/local/share/X11/xorg.conf.d/20-Nvidia.conf ]; then
sudo touch /usr/local/share/X11/xorg.conf.d/20-Nvidia.conf
sudo chmod a=rw /usr/local/share/X11/xorg.conf.d/20-Nvidia.conf
cat <<EOF >/usr/local/share/X11/xorg.conf.d/20-Nvidia.conf

Section "Device"
        Identifier "Nvidia Card"
        Driver "nvidia"
        VendorName "NVIDIA Corporation"
EndSection


EOF

fi




Sent from my iPhone using Tapatalk
Title: Re: TC & NVidia
Post by: coreplayer2 on July 07, 2019, 04:05:53 PM
hello SeventhSin

Regarding the Nvidia 32bit repo extensions,  nvidia-390.87-4.19.10-tinycore.tcz and nvidia-390.87-4.19.10-tinycore64.tcz (for Core64 only) have been updated with
1. separation of unneeded GLX/OpenGL files, reducing the extension size considerably
2. creation of config file to assist Xorg detect and use Nvidia driver without need to run nvidia-xconfig

see http://forum.tinycorelinux.net/index.php/topic,23026.msg143908.html#msg143908


nextup: Nvidia extensions for corepure64

regards
Title: Re: TC & NVidia
Post by: hiro on July 07, 2019, 05:30:49 PM
hey, i don't have any nvidia card right now. but this sounds good, so if i get to make a choice soon about new hardware i'll remember there's a lightweight driver for nvidia as part of tc. thanks coreplayer2 ;)

(i have an aversion to create Xorg config files, so i'm happy i would not need to do that, haha)
Title: Re: TC & NVidia
Post by: SeventhSin on July 08, 2019, 08:10:19 AM
Quote from: coreplayer2 on July 07, 2019, 04:05:53 PM
hello SeventhSin

Regarding the Nvidia 32bit repo extensions,  nvidia-390.87-4.19.10-tinycore.tcz and nvidia-390.87-4.19.10-tinycore64.tcz (for Core64 only) have been updated with
1. separation of unneeded GLX/OpenGL files, reducing the extension size considerably
2. creation of config file to assist Xorg detect and use Nvidia driver without need to run nvidia-xconfig

see http://forum.tinycorelinux.net/index.php/topic,23026.msg143908.html#msg143908


nextup: Nvidia extensions for corepure64

regards

Hey coreplayer2. That sounds great, thank you for this!

I was actually about to start the tests, but I will wait for the 64 bit extension to pop-up in it's final form in the repo. That way I can test both x86-32 & x86-64 with the latest enhancements in one go.
Title: Re: TC & NVidia
Post by: coreplayer2 on July 31, 2019, 03:18:42 AM
Hello SeventhSin

Nvidia drivers updated to 390.116 and posted

In x86 repo
nvidia-390.116-4.19.10-tinycore.tcz
nvidia-390.116-4.19.10-tinycore64.tcz  (core64 version)

In x86_64 repo
nvidia-390.116-4.19.10-tinycore64.tcz  (corepure64 version)

http://forum.tinycorelinux.net/index.php/topic,23026.msg144532.html#msg144532

hope those work for you,  remember the 32 version will likely require " vmalloc=256MB " bootcode
Title: Re: TC & NVidia
Post by: wilzyy on August 10, 2019, 02:36:36 AM
Thanks on the guide it works for me!
Title: Re: TC & NVidia
Post by: mutantape on April 30, 2020, 04:29:28 PM
Thanks a lot, with these extensions i've been able to see TC in full screen for the first time ever, years after i first came to know it. And it makes a huge difference in readibility.( not to mention the potential problems with screen burn)

I am using an Nvidia GT520 card.
In Tc 10.0, i just load
nvidia-390.116-4.19.10-tinycore.tcz
Xorg-7.7.tcz
and it works, after Ctrl/Alt/Backspace then startx...Well,almost, since i have a french keyboard, i have to add an xorg.conf file like the one below (in /etc/X11, that i have to make persistent):

Did you also see those sites stating it is possible to change the scaling in Vesa Bios using code such as :
Code: [Select]
mov ax,4F14h ;VESA VBE OEM function
    mov bl,2     ;Subfunction 02 = Set Panel Expansion/Centering
    mov bh,1     ;00 = Return Current Setting, 01 = Set Centering/Expansion
    mov cx,0001h ;Exp. mode: 00 = Scaled, 01 = Centered 1:1, 02 = Left Corner 1:1
    int 10h      ;call VGA/VBE servicehttps://www.tonymacx86.com/threads/nvidia-how-to-get-rid-of-the-black-border.121519/

This suggests it could work with Xvesa, provided this code can be executed early enough in the boot.


Code: [Select]
# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.
Load        "dbe"  # Double buffer extension

EndSection

# **********************************************************************
# Files section.  This allows default font paths to be set
# **********************************************************************

Section "Files"

# Multiple FontPath entries are allowed
FontPath   "/usr/share/X11/fonts/misc/"
FontPath   "/usr/share/X11/fonts/Type1/"
FontPath   "/usr/share/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Enables mode switching with xrandr
Option "RandR" "on"

# With this, Xorg talks to udev to add evdev devices
Option "AutoAddDevices" "true"

# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...
Option "DontZap" "false"

EndSection

# ===============================================================

Section "InputClass"
Identifier "keyboard-all"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver      "evdev"
Option      "XkbRules" "evdev"
Option      "XkbModel" "pc104" #xkbmodel0
Option      "XkbLayout" "fr"
Option      "XkbVariant" "" #xkbvariant0
Option      "XkbOptions" "terminate:ctrl_alt_bksp" #xkboptions0
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName    "Monitor Model"
EndSection

Section "Modes"
Identifier "Modes0"
EndSection

Section "Device"
Identifier     "Device0"
Driver         "nvidia"
VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device     "Card0"
Monitor    "Monitor0"
EndSection

Section "ServerLayout"
Identifier     "X.org config"
Screen         "Screen0"
EndSection
    [EDIT]: Added code tags.  Rich
Title: Re: TC & NVidia
Post by: Rich on April 30, 2020, 05:05:03 PM
Hi mutantape
Welcome to the forum.

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

Quote
[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:
Code: [Select]
[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.
Title: Re: TC & NVidia
Post by: mutantape on April 30, 2020, 05:11:32 PM
Unfortunately, i am no closer to my goal of having qemu + kvm working on a full screen TC.

qemu + qvm seem to work very well on TC 6.4, but then this version does not have those magic nvidia drivers->black borders
TC 10.0 has the nvidia drivers so is full screen, but then qemu +kvm seem to be broken on this one.
Qemu+ kvm seem to work better on TC 11.1, though perhaps full screen is a bit strange, but again with no nvidia drivers.
(all of that on the same physical machine exactly, always using the 32 bit versions though the machine can take 64).

I've tried to compile the 390.116 for TC 11.1, but there are compilation errors, it does not seem to be able to adjust to the new kernel.
I've been able to compile and install the 390.132 (Nvidia still lists my card in this one), but when i go startx i get a black screen and the machine is completely stuck, it is not even possible to exit the Gui with Ctrl Alt Backspace. Blindly typing sudo reboot or poweroff has no effect.

I start TC 11.1 with boot option nvidia-drm.setmode=1, then i load
i2c-5.4.3-tinycore.tcz
graphics-5.4.3-tinycore.tcz (without those two i get an nvidia-drm.ko load error)
Xorg-7.7.tcz (need the various related folder to put nvidia files)
compiletc.tcz
linux-kernel-sources-env.tcz
Then i do the cliorx command suggested in linux-kernel-sources-env info which apparently starts the full kernel compilation.
Since i have no memory left in rootfs after that i move the resulting linux tree to /dev/shm, then run the
NVIDIA-Linux-x86-390.132.run with --kernel-source-path option, specifying my new path in shm.
It builds ok there is a long pause where nothing happens, then it proceeds to files installation, and loads modules to memory.
Every message seems  Ok, and the installer exits.
startx->fall into the black hole.
Anyone with more luck or talent in these matters ?

By the way is there a magic TC tool to automatically extract new files added in the rootfs by such an installer ? There seems to be no way to do a simple make install to a folder.  I am thinking of a
ls -lR > file.txt before and after, then a diff and a small bash script to copy based on the info, but surely TC developers must already have something for  this ?


Title: Re: TC & NVidia
Post by: mutantape on April 30, 2020, 05:18:12 PM
Thanks for the code tags info,  i wondered about that, but did not feel like hunting for the way to do it...
Title: Re: TC & NVidia
Post by: Rich on April 30, 2020, 07:47:59 PM
Hi mutantape
Quote from: mutantape on April 30, 2020, 05:11:32 PM
... but when i go startx i get a black screen and the machine is completely stuck, it is not even possible to exit the Gui with Ctrl Alt Backspace. ...
Ctrl-Alt-F1  should get you back to the console. From there, running:
Code: [Select]
ps aux | grep -i xshould allow you to find which  PID  X  was assigned so you can kill it.
Title: Re: TC & NVidia
Post by: Juanito on May 01, 2020, 01:33:39 AM
Quote from: mutantape on April 30, 2020, 05:11:32 PM
By the way is there a magic TC tool to automatically extract new files added in the rootfs by such an installer ? There seems to be no way to do a simple make install to a folder.

If you cannot use $DESTDIR, you could try this:
Code: [Select]
$ tce-load -i findutils
$ touch mymarker
$ sudo make install
$ sudo find / -not -type 'd' -cnewer mymarker | grep -v "\/proc\/" | grep -v "^\/sys\/" | tee files
$ vi files