Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: CardealRusso on April 23, 2023, 04:11:46 PM
-
Hello, friends. I really like TinyCore. I am looking at using it as my one and only main system.
I have tested both dCore and x86 Pure 64 and have failed to get a proprietary or open source driver installed for my GTX 1650. Can anyone provide me with any assistance?
-
What have you tried so far - Xorg-7.7, Xorg-7.7-3d, nouveau kernel drivers, etc and what happened?
-
What have you tried so far - Xorg-7.7, Xorg-7.7-3d, nouveau kernel drivers, etc and what happened?
Thanks a lot for the help. I'm not very familiar with TinyCore (actually I'm not very faimiar with linux on desktop, usually I just use a remote terminal). Apparently I was installing the wrong packages. After installing:
firmware-nvidia.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
The nouveau driver is now working properly again.
Taking advantage of the help, I would like to have some help on the keys and on the audio.
I installed the kmaps package and added kmap=qwerty/br-abnt2 in grub.cfg, but that wasn't enough to change the keyboard layout, what could I do?
-
What have you tried so far - Xorg-7.7, Xorg-7.7-3d, nouveau kernel drivers, etc and what happened?
Thanks a lot for the help. I'm not very familiar with TinyCore (actually I'm not very faimiar with linux on desktop, usually I just use a remote terminal). Apparently I was installing the wrong packages. After installing:
firmware-nvidia.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
The nouveau driver is now working properly again.
Taking advantage of the help, I would like to have some help on the keys and on the audio.
I installed the kmaps package and added kmap=qwerty/br-abnt2 in grub.cfg, but that wasn't enough to change the keyboard layout, what could I do?
@edit
I somehow managed to change the keyboard by editing the .xsession and adding it to backupt, but i dont wanted to have a backup file
same applied to alsa audio, i also managed to get it to work, it was pretty easy actually, but i needed to create a backup for the alsactl init
-
What have you tried so far - Xorg-7.7, Xorg-7.7-3d, nouveau kernel drivers, etc and what happened?
Thanks a lot for the help. I'm not very familiar with TinyCore (actually I'm not very faimiar with linux on desktop, usually I just use a remote terminal). Apparently I was installing the wrong packages. After installing:
firmware-nvidia.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
The nouveau driver is now working properly again.
Taking advantage of the help, I would like to have some help on the keys and on the audio.
I installed the kmaps package and added kmap=qwerty/br-abnt2 in grub.cfg, but that wasn't enough to change the keyboard layout, what could I do?
While the nouveau its working, it is damn slow. the proprietary driver is needed.
-
Did you check /var/log/Xorg.0.log to see if hardware acceleration is working.
Note also that if you want to avoid using a backup, you can add a configuration file to your local copy of the relevant extension.
-
Did you check /var/log/Xorg.0.log to see if hardware acceleration is working.
Note also that if you want to avoid using a backup, you can add a configuration file to your local copy of the relevant extension.
I can't say if it's being accelerated or not, but it's much faster after I installed the nouveau driver compared to no driver at all but, even with the nouveau driver, the mesa-demos are performing infinitely lower than low cost video cards from 12 years ago! it is exaggeratedly slow.
-
Juanito is the expert here....but my comments are
IMHO your xorg log shows that you have used a boot code vga=791 and the internet suggests that Kernel mode setting KMS does not like that.
The Nouveau kernel module should load automatically on system boot. If it does not happen, then:
Make sure you do not have nomodeset or vga= as a kernel parameter, since Nouveau requires kernel mode-setting.
ref
https://wiki.archlinux.org/title/Nouveau
Do you need UEFI on?
2) Can you download and install inxi please. its a lot easier to understand than reading your log. Your log shows loading and unloading of various video drivers.
tce-load -w inxi
tce-load -i inxi
inxi -Gxxx
I will give you an idea of the load unload going with my results.
NOT OP just example
inxi -Gxxx
Graphics:
Device-1: AMD driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,HDMI-A-2 bus-ID: 26:00.0
chip-ID: 1002:15d8 class-ID: 0300 temp: 37.0 C
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) FULL HD
res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.63")
diag: 551mm (21.7") modes: max: 1920x1080 min: 720x400
API: OpenGL Message: Unable to show GL data. Required tool glxinfo
missing.
so its lot easier IMHO to see that unloaded: fbdev,vesa but inxi does not show any conflicting or blacklisting boot loader settings while Xorg log does!
I can't say if it's being accelerated or not
...if glxgears spins....you have acceleration
-
With the x11 keyboard map problem you may to read this threads.
http://forum.tinycorelinux.net/index.php/topic,25863.msg165846.html#msg165846
-
Your Xorg log shows this:
[ 25.764] (==) Matched nouveau as autoconfigured driver 0
[ 25.764] (==) Matched nv as autoconfigured driver 1
[ 25.764] (==) Matched modesetting as autoconfigured driver 2
[ 25.764] (==) Matched fbdev as autoconfigured driver 3
[ 25.764] (==) Matched vesa as autoconfigured driver 4..meaning its first preference is to use the nouveau driver.
..but it can't find the nouveau module: [ 25.764] (II) LoadModule: "nouveau"
[ 25.764] (WW) Warning, couldn't open module nouveau
[ 25.764] (EE) Failed to load module "nouveau" (module does not exist, 0)
..and so: [ 25.779] (EE) open /dev/dri/card0: No such file or directory..which means 3d hardware acceleration is not being used (fbdev is being used).
The nouveau-KERNEL extension provides nouveau.ko.gz, does "lsmod" show that it is loaded? If not try "sudo modprobe nouveau" and check again.
Is the xf86-video-nouveau extension loaded?
-
...if glxgears spins....you have acceleration
Yes, but they will spin with both software (lavapipe) and hardware acceleration - better to use "glxinfo | grep Accel"
-
...if glxgears spins....you have acceleration
Yes, but they will spin with both software (lavapipe) and hardware acceleration - better to use "glxinfo | grep Accel"
tc@box:~$ glxinfo | grep Accel
Accelerated: no
tc@box:~$ sudo modprobe nouveau
modprobe: module nouveau not found in modules.dep
tc@box:~$ inxi -Gxxx
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "pt_BR"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Graphics:
Device-1: NVIDIA vendor: ASUSTeK driver: N/A arch: Turing pcie:
speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 10de:1f82 class-ID: 0300
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: nouveau,vesa
unloaded: fbdev,modesetting alternate: nv dri: swrast gpu: N/A
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: default res: 1440x900 hz: 77 size: N/A modes: N/A
API: OpenGL v: 4.5 Mesa 22.3.7 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct-render: Yes
I installed everything related to nouveau. The comments by xf86-video-nouveau say that my video card is not supported.
Does the order of the packages matter?
Do you need UEFI on?
Sadly yes. My motherboard is UEFI only. I can't even boot into windows 7.
-
If you get this:
sudo modprobe nouveau
modprobe: module nouveau not found in modules.dep
..it means nouveau-KERNEL is not loaded.
What does this give: tce-status -i | grep nouveau
-
If you get this: sudo modprobe nouveau[code]
modprobe: module nouveau not found in modules.dep
..it means nouveau-KERNEL is not loaded.
What does this give: tce-status -i | grep nouveau
tc@box:~$ tce-status -i | grep nouveau
xf86-video-nouveau
I installed xf86-video-nouveau now after you advise me. I don't know what happened before but the result is apparently the same.
@edit
Maybe I found the problem. Apparently, when I tried to load the driver through the apps, the driver restarted before the files were saved to the USB stick. I just noticed that several files, i2c, nouveau and etc were 0kb. I will update soon.
-
If you get this: sudo modprobe nouveau
modprobe: module nouveau not found in modules.dep
..it means nouveau-KERNEL is not loaded.
What does this give: tce-status -i | grep nouveau
Everything is seems installed correctly. but still no acceleration.
tc@box:~$ sudo modprobe nouveau
tce-status -i | grep nouveau
nouveau-6.1.2-tinycore64
tc@box:~$ glxinfo | grep Accel
Accelerated: no
tc@box:~$ inxi -Gxxx
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "pt_BR"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Graphics:
Device-1: NVIDIA vendor: ASUSTeK driver: nouveau v: kernel arch: Turing
pcie: speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1
bus-ID: 03:00.0 chip-ID: 10de:1f82 class-ID: 0300 temp: 37.0 C
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: modesetting
unloaded: fbdev,vesa alternate: nouveau,nv dri: swrast gpu: nouveau
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HDMI res: 1440x900 hz: 60
dpi: 64 size: 575x323mm (22.64x12.72") modes: max: 1440x900 min: 720x400
API: OpenGL v: 4.5 Mesa 22.3.7 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct-render: Yes
tc@box:~$ glxgears
1895 frames in 5.0 seconds = 378.986 FPS
1878 frames in 5.0 seconds = 375.515 FPS
2035 frames in 5.0 seconds = 406.945 FPS
onboot.lst:
...
Xorg-7.7-3d.tcz
nouveau-6.1.2-tinycore64.tcz
...
-
Can you attach your xorg log after successfully modprobing the nouveau module - you have to start/restart x after loading the module.
Also, what does "dmesg | tail -20" give after loading the module?
-
Can you attach your xorg log after successfully modprobing the nouveau module - you have to start/restart x after loading the module.
Also, what does "dmesg | tail -20" give after loading the module?
nouveau 0000:03:00.0: DRM: BIT table 'L' not found
nouveau 0000:03:00.0: DRM: TMDS table version 2.0
nouveau 0000:03:00.0: DRM: DCB version 4.1
nouveau 0000:03:00.0: DRM: DCB outp 00: 01000f32 04620030
nouveau 0000:03:00.0: DRM: DCB outp 01: 02011f52 00020010
nouveau 0000:03:00.0: DRM: DCB outp 02: 02822f66 04600020
nouveau 0000:03:00.0: DRM: DCB outp 03: 02022f62 00020020
nouveau 0000:03:00.0: DRM: DCB conn 00: 00001031
nouveau 0000:03:00.0: DRM: DCB conn 01: 00010161
nouveau 0000:03:00.0: DRM: DCB conn 02: 00020246
nouveau 0000:03:00.0: DRM: failed to create kernel channel, -22
nouveau 0000:03:00.0: DRM: MM: using COPY for buffer copies
nouveau 0000:03:00.0: DRM: allocated 1440x900 fb: 0x200000, bo 000000002aa9c8b7
fbcon: nouveaudrmfb (fb0) is primary device
Console: switching to colour frame buffer device 180x56
nouveau 0000:03:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[drm] Initialized nouveau 1.3.1 20120801 for 0000:03:00.0 on minor 0
I guess this nouveau is just not compatible with my GPU (GTX 16xx)
I found this on xorg log:
[ 24.241] (II) LoadModule: "vesa"
[ 24.241] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 24.241] (II) Module vesa: vendor="X.Org Foundation"
[ 24.241] compiled for 1.21.1.3, module version = 2.5.0
[ 24.241] Module class: X.Org Video Driver
[ 24.241] ABI class: X.Org Video Driver, version 25.2
[ 24.241] (II) NOUVEAU driver
[ 24.241] (II) NOUVEAU driver for NVIDIA chipset families :
[ 24.241] RIVA TNT (NV04)
[ 24.241] RIVA TNT2 (NV05)
[ 24.241] GeForce 256 (NV10)
[ 24.241] GeForce 2 (NV11, NV15)
[ 24.241] GeForce 4MX (NV17, NV18)
[ 24.241] GeForce 3 (NV20)
[ 24.241] GeForce 4Ti (NV25, NV28)
[ 24.241] GeForce FX (NV3x)
[ 24.241] GeForce 6 (NV4x)
[ 24.241] GeForce 7 (G7x)
[ 24.241] GeForce 8 (G8x)
[ 24.242] GeForce 9 (G9x)
[ 24.242] GeForce GTX 2xx/3xx (GT2xx)
[ 24.242] GeForce GTX 4xx/5xx (GFxxx)
[ 24.242] GeForce GTX 6xx/7xx (GKxxx)
[ 24.242] GeForce GTX 9xx (GMxxx)
[ 24.242] GeForce GTX 10xx (GPxxx)
-
You didn’t go back far enough in dmesg (go back until you don’t see nouveau in the first column), but I’d guess you need to load firmware-nvidia before modprobe nouveau.
-
thanks to inxi output OP has Turing, post 11 and this link is very good timing
https://www.phoronix.com/news/NVIDIA-Turing-Firmware-2023
So should you have run into NVIDIA GeForce GTX 16 / RTX 20 series issues with the Nouveau driver, the new firmware is now in the Linux Firmware Git tree.
I have submitted a TCE called firmware-nvidia-turing.tcz thru the normal email system
it was a rush job so simple downloads and populate allegedly the correct dir with an tce.install script if needed.
It did pass submitqc --libs so fingers crossed eh?
-
Hi
TCE has already hit the main repo but not sure if you are using a mirror, which takes longer. When it appears in Apps pulldown choose Download only please
Please make a backup of your boot list and keep it somewhere safe in case my new fw package causes a bork etc
Can I suggest you do a manual edit of your boot list, if you have not renamed it, likely to be onboot.lst
so that the TCE has no mention of firmware-nvidia.tcz nor graphics-6.1.2-tinycore64.tcz
then order is important....someone correct me if i am wrong, for what I just wrote
firmware-nvidia-turing.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7-3d.tcz
plus other TCEs that you regularly need
full reboot.
try loading inxi and rechecking if driver changes to nouveau
2) if it does....then as per Juanito advice
glxinfo | grep Accel
##############
If its glitchy.....or worse than before, do you know how to use an usb to get back and make changes?
if its glitchy....please save /var/log/Xorg.0.log and make a copy of dmesg via
dmesg > /tmp/dmesg.txt and keep those files please. We may need to see them
Good luck, bed time for me
-
Hi
still the same
Graphics:
Device-1: NVIDIA vendor: ASUSTeK driver: nouveau v: kernel arch: Turing
pcie: speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1
bus-ID: 03:00.0 chip-ID: 10de:1f82 class-ID: 0300 temp: 37.0 C
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: modesetting
unloaded: fbdev,vesa alternate: nouveau,nv dri: swrast gpu: nouveau
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HDMI res: 1440x900 hz: 60
dpi: 64 size: 575x323mm (22.64x12.72") modes: max: 1440x900 min: 720x400
API: OpenGL v: 4.5 Mesa 22.3.7 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct-render: Yes
tc@box:~$ glxinfo | grep Accel
Accelerated: no
-
[ 24.039] (II) LoadModule: "nouveau"
[ 24.039] (WW) Warning, couldn't open module nouveau
[ 24.039] (EE) Failed to load module "nouveau" (module does not exist, 0)
Looks like I had a fallback, nouvea module is not found, again.
...
firmware-nvidia-turing.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7-3d.tcz
despite this error, nouveau appears to be in fact loading?
tc@box:~$ tce-status -i | grep nouveau
nouveau-6.1.2-tinycore64
tc@box:~$ sudo modprobe nouveau
-
Got some results after playing with load order, but still, nothing
[ 21.094] (II) LoadModule: "nouveau"
[ 21.094] (II) Loading /usr/local/lib/xorg/modules/drivers/nouveau_drv.so
[ 21.099] (II) Module nouveau: vendor="X.Org Foundation
...
[ 21.117] (II) [drm] nouveau interface version: 1.3.1
[ 21.117] (EE) Unknown chipset: NV167
[ 21.118] (II) [drm] nouveau interface version: 1.3.1
[ 21.118] (EE) Unknown chipset: NV167
[ 21.118] (II) [drm] nouveau interface version: 1.3.1
[ 21.118] (EE) Unknown chipset: NV167
[ 21.118] (II) [drm] nouveau interface version: 1.3.1
[ 21.118] (EE) Unknown chipset: NV167
[ 21.118] (II) modeset(0): using drv /dev/dri/card0
[ 21.118] (WW) Falling back to old probe method for fbdev
firmware-nvidia.tcz
firmware-nvidia-turing.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
inxi.tcz
nano.tcz
xf86-video-nouveau.tcz
xf86-video-nv.tcz
mesa-demos.tcz
Graphics:
Device-1: NVIDIA vendor: ASUSTeK driver: nouveau v: kernel arch: Turing
pcie: speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1
bus-ID: 03:00.0 chip-ID: 10de:1f82 class-ID: 0300 temp: 37.0 C
Display: server: X.Org v: 1.21.1.6 driver: X:
loaded: modesetting,nouveau,nv unloaded: fbdev,vesa dri: swrast gpu: nouveau
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HDMI res: 1440x900 hz: 60
dpi: 64 size: 575x323mm (22.64x12.72") modes: max: 1440x900 min: 720x400
API: OpenGL v: 4.5 Mesa 22.3.7 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct-render: Yes
Accelerated: no
-
oops my overconfidence I forgot to check if those fw were a match to your actual device.
nouveau 0000:03:00.0: NVIDIA TU117 (167000a1) # from dmesg
[ 21.117] (EE) Unknown chipset: NV167 # from xorg log
my fw is for 102 & 116....sorry about that.
lets start afresh?
NV160 family (Turing)
Code name Official Name
NV162 (TU102) NVIDIA Titan RTX, GeForce RTX 2080 Ti
NV164 (TU104) GeForce RTX (2070 Super, 2080, 2080 Super)
NV166 (TU106) GeForce RTX (2060, 2060 Super, 2070)
NV168 (TU116) GeForce GTX (1650 Super, 1660, 1660 Ti, 1660 Super)
NV167 (TU117) GeForce GTX 1650
I will get the info file for my latest fw updated later, to not mislead any more members during to my poor research
can you confirm you have the 1650?
lspci -k | grep -A 2 -E "(VGA|3D)"
if it is....firmware for 117 has not changed since 2020
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/nvidia/tu117/gr?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
and TU117 was in the firmware-nvidia which you have already tried.
##########################################
@Juanito
its above my pay scale, would you think the link below might help?
https://github.com/NVIDIA/open-gpu-kernel-modules
-
otherwise, maybe OP could look at the info file for sway-dot and sway and see if things work better on sway?
sway can not work with closed source nvidia driver, I know OP does not have it,
but in theory can work with open source nouveau. YMMV
-
oops my overconfidence I forgot to check if those fw were a match to your actual device.
nouveau 0000:03:00.0: NVIDIA TU117 (167000a1) # from dmesg
[ 21.117] (EE) Unknown chipset: NV167 # from xorg log
can you confirm you have the 1650?
Yes, it is gtx 1650 (the gddr6 version, not the gddr5, but i guess they are just the same thing, just changed the memory thing)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1f82 (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 8773
Kernel driver in use: nouveau
-
Hi Rich or Juanito
can the following be added to the info file for
firmware-nvidia-turing
only for chipsets
NV162 (TU102) NVIDIA Titan RTX, GeForce RTX 2080 Ti
NV168 (TU116) GeForce GTX (1650 Super, 1660, 1660 Ti, 1660 Super)
-
Everything seems to be compatible. Am I doing something wrong? Is there anything i need to do other than simply organize the packages?
-
Am I doing something wrong?
I mislead you. if you have not already guessed, please remove from your boot list
firmware-nvidia-turing.tcz but keep firmware-nvidia.tcz
I am not sure what your current boot list is....from top to bottom IMHO it should show
in generic terms
firmware
kernel module
video driver....but I claim that driver is in Xorg-7.7-3d
recently you appear to have
firmware-nvidia.tcz
firmware-nvidia-turing.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
inxi.tcz
nano.tcz
xf86-video-nouveau.tcz
xf86-video-nv.tcz
mesa-demos.tcz
Maybe wait for expert advice....but me thinks xf86* TCEs should be before Xorg to have a benefit if any.
Also Xorg-7.7 is a dep of the 3d TCE
I do not believe graphics TCE has any benefit to you either
http://tinycorelinux.net/14.x/x86_64/tcz/graphics-6.1.2-tinycore64.tcz.list
-
correction.
the graphics TCE has drm modules so please keep it in boot list
-
Hi aus9
firmware-nvidia-turing.tcz.info updated.
-
Hi CardealRusso
I would reorder your onboot.lst to look like this:
firmware-nvidia.tcz
graphics-6.1.2-tinycore64.tcz
nouveau-6.1.2-tinycore64.tcz
xf86-video-nouveau.tcz
xf86-video-nv.tcz
mesa-demos.tcz
Xorg-7.7-3d.tcz
inxi.tcz
nano.tcz
Xorg-7.7.tcz does not need to be in the list. Xorg-7.7-3d.tcz includes
it as a dependency.
-
Maybe the firmware is not being loaded - what does “dmesg | grep nouveau” give?
-
Hi CardealRusso
I would reorder your onboot.lst to look like this:
Thanks, i did this.
Maybe the firmware is not being loaded - what does “dmesg | grep nouveau” give?
Would installing the proprietary driver be too difficult?
nouveau 0000:03:00.0: vgaarb: deactivate vga console
nouveau 0000:03:00.0: NVIDIA TU117 (167000a1)
nouveau 0000:03:00.0: bios: version 90.17.4d.00.b4
nouveau 0000:03:00.0: pmu: firmware unavailable
nouveau 0000:03:00.0: gr: firmware unavailable
nouveau 0000:03:00.0: sec2: firmware unavailable
nouveau 0000:03:00.0: fb: 4096 MiB GDDR6
nouveau 0000:03:00.0: fb: VPR locked, but no scrubber binary!
nouveau 0000:03:00.0: DRM: VRAM: 4096 MiB
nouveau 0000:03:00.0: DRM: GART: 536870912 MiB
nouveau 0000:03:00.0: DRM: BIT table 'A' not found
nouveau 0000:03:00.0: DRM: BIT table 'L' not found
nouveau 0000:03:00.0: DRM: TMDS table version 2.0
nouveau 0000:03:00.0: DRM: DCB version 4.1
nouveau 0000:03:00.0: DRM: DCB outp 00: 01000f32 04620030
nouveau 0000:03:00.0: DRM: DCB outp 01: 02011f52 00020010
nouveau 0000:03:00.0: DRM: DCB outp 02: 02822f66 04600020
nouveau 0000:03:00.0: DRM: DCB outp 03: 02022f62 00020020
nouveau 0000:03:00.0: DRM: DCB conn 00: 00001031
nouveau 0000:03:00.0: DRM: DCB conn 01: 00010161
nouveau 0000:03:00.0: DRM: DCB conn 02: 00020246
nouveau 0000:03:00.0: DRM: failed to create kernel channel, -22
nouveau 0000:03:00.0: DRM: MM: using COPY for buffer copies
nouveau 0000:03:00.0: DRM: allocated 1440x900 fb: 0x200000, bo 000000004c8ac255
fbcon: nouveaudrmfb (fb0) is primary device
nouveau 0000:03:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[drm] Initialized nouveau 1.3.1 20120801 for 0000:03:00.0 on minor 0
-
Would installing the proprietary driver be too difficult?
It won’t be straightforward - if you search these forums, you’ll see that several users have done it.
You might be better off searching the internet on some of the error messages from firmware loading via dmesg.
-
Hi Juanito and CardealRusso
I think I have found a possible reason for quirky missing firmware message reported by OP post 33
nouveau 0000:03:00.0: NVIDIA TU117 (167000a1)
SNIP
nouveau 0000:03:00.0: gr: firmware unavailable
nouveau 0000:03:00.0: sec2: firmware unavailable
I load the module and modinfo
tce-load -i nouveau-6.1.2-tinycore64
modinfo nouveau | grep tu117
firmware: nvidia/tu117/acr/ucode_ahesasc.bin
firmware: nvidia/tu117/acr/bl.bin
firmware: nvidia/tu117/acr/ucode_asb.bin
firmware: nvidia/tu117/acr/ucode_unload.bin
firmware: nvidia/tu117/acr/unload_bl.bin
firmware: nvidia/tu117/nvdec/scrubber.bin
firmware: nvidia/tu117/gr/sw_method_init.bin
firmware: nvidia/tu117/gr/sw_bundle_init.bin
firmware: nvidia/tu117/gr/sw_nonctx.bin
firmware: nvidia/tu117/gr/sw_ctx.bin
firmware: nvidia/tu117/gr/gpccs_sig.bin
firmware: nvidia/tu117/gr/gpccs_data.bin
firmware: nvidia/tu117/gr/gpccs_inst.bin
firmware: nvidia/tu117/gr/gpccs_bl.bin
firmware: nvidia/tu117/gr/fecs_sig.bin
firmware: nvidia/tu117/gr/fecs_data.bin
firmware: nvidia/tu117/gr/fecs_inst.bin
firmware: nvidia/tu117/gr/fecs_bl.bin
firmware: nvidia/tu117/sec2/sig.bin
firmware: nvidia/tu117/sec2/image.bin
firmware: nvidia/tu117/sec2/desc.bin
IMHO it should only hits for fw as per our fw file for 14X
gr/sw_veid_bundle_init.bin
gr/sw_nonctx.bin
gr/sw_method_init.bin
gr/sw_ctx.bin
gr/sw_bundle_init.bin
gr/gpccs_sig.bin
gr/gpccs_inst.bin
gr/gpccs_data.bin
gr/fecs_sig.bin
gr/fecs_inst.bin
gr/fecs_data.bin
and we have a match for the 13 series.
so IMHO all the CardealRusso needs to try before compiling nvidia closed source is...
click on link to download the 13x firmware
as its ramdrive has fw already loaded he can delete existing fw and its md5.txt file
showing as code for copy and paste
rm -rf /etc/sysconfig/tcedir/optional/firmware-nvidia.tcz*
cd /etc/sysconfig/tcedir/optional
wget tinycorelinux.net/13.x/x86_64/tcz/firmware-nvidia.tcz
or click on link and move it to your tcedir and make it over write existing
tinycorelinux.net/13.x/x86_64/tcz/firmware-nvidia.tcz
then full reboot
recheck inxi -Gxxx.....nouveau IMHO should now stay loaded
-
download the 13x firmware
I confess that I tried to follow your instructions without any hope that it would work...
tc@box:~$ glxinfo | grep Accel
Accelerated: yes
BUT IT WORKED! ;D ;D ;D
Dude, thank you so much, you'are sick
tc@box:~$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
9274 frames in 5.0 seconds = 1854.556 FPS
9430 frames in 5.0 seconds = 1885.883 FPS
9569 frames in 5.0 seconds = 1913.663 FPS
Compared to no drivers:
tc@box:~$ glxgears
1895 frames in 5.0 seconds = 378.986 FPS
1878 frames in 5.0 seconds = 375.515 FPS
2035 frames in 5.0 seconds = 406.945 FPS
Graphics:
Device-1: NVIDIA vendor: ASUSTeK driver: nouveau v: kernel arch: Turing
pcie: speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1
bus-ID: 03:00.0 chip-ID: 10de:1f82 class-ID: 0300 temp: 37.0 C
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: modesetting,nouveau
unloaded: fbdev,vesa alternate: nv dri: nouveau gpu: nouveau
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HDMI res: 1440x900 hz: 60
dpi: 64 size: 575x323mm (22.64x12.72") modes: max: 1440x900 min: 720x400
API: OpenGL v: 4.3 Mesa 22.3.7 renderer: NV167 direct-render: Yes
So, someone has just broken the firmware-nvidia file on 14x?
VSYNC IS KILLING ME
For some reason, the whole system, not just glxgear, even the browsers, everything, is kind of buggy, like it's running at just under 30 fps. is it possible to disable vsync? or increase the framerate as my monitor supports 75Hz
Thanks aswell to Juanito, Rich patrikg for the help. We would certainly not have reached this result without everyone's help.
-
I presume this is the best while the proprietary driver is not released. Although it improved the results a lot, glxgears should be able to play more than 30,000 fps with this video card.
nouveau 0000:03:00.0: vgaarb: deactivate vga console
nouveau 0000:03:00.0: NVIDIA TU117 (167000a1)
nouveau 0000:03:00.0: bios: version 90.17.4d.00.b4
nouveau 0000:03:00.0: pmu: firmware unavailable
nouveau 0000:03:00.0: fb: 4096 MiB GDDR6
nouveau 0000:03:00.0: DRM: VRAM: 4096 MiB
nouveau 0000:03:00.0: DRM: GART: 536870912 MiB
nouveau 0000:03:00.0: DRM: BIT table 'A' not found
nouveau 0000:03:00.0: DRM: BIT table 'L' not found
nouveau 0000:03:00.0: DRM: TMDS table version 2.0
nouveau 0000:03:00.0: DRM: DCB version 4.1
nouveau 0000:03:00.0: DRM: DCB outp 00: 01000f32 04620030
nouveau 0000:03:00.0: DRM: DCB outp 01: 02011f52 00020010
nouveau 0000:03:00.0: DRM: DCB outp 02: 02822f66 04600020
nouveau 0000:03:00.0: DRM: DCB outp 03: 02022f62 00020020
nouveau 0000:03:00.0: DRM: DCB conn 00: 00001031
nouveau 0000:03:00.0: DRM: DCB conn 01: 00010161
nouveau 0000:03:00.0: DRM: DCB conn 02: 00020246
nouveau 0000:03:00.0: DRM: MM: using COPY for buffer copies
nouveau 0000:03:00.0: DRM: allocated 1440x900 fb: 0x200000, bo 00000000fed6768e
fbcon: nouveaudrmfb (fb0) is primary device
nouveau 0000:03:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[drm] Initialized nouveau 1.3.1 20120801 for 0000:03:00.0 on minor 0
firmware-nvidia.tcz
nouveau-6.1.2-tinycore64.tcz
xf86-video-nouveau.tcz
Xorg-7.7-3d.tcz
By the way, I gave up playing games in order to become more productive. I decided to abandon Windows because Windows 11 is just undigestable and TinyCore x64 is just enough for me, I don't need more than that. I just need the drivers, browser (I'm already satisfied with bravo, although I wanted ungoggled-chromium) and I'm already used to nano, I don't need anything else.
-
Nouveau cannot upclock most of the new Nvidia cards, so they run at a very low power & low performance. You'd need the proprietary drivers to get the card's full performance.
-
hi
or increase the framerate as my monitor supports 75Hz
Xorg 3d has a command xrandr so run it
xrandrLook at your results. I will use mine as an example
1920x1080 60.00*+ 74.97 59.96 50.00 59.94 59.93
# and lets pretend I wanted to use
1024x768 75.05 60.04 75.03 70.07 60.00
use Apps to download arandr and run it. (there are some errors in my info file for arandr I will fix later)
arandr &GUI appears and I am on hdmi output. I pull down Outputs -> hdmi* -> Resolution -> click the radio button against 1024x768
click apply...screen will blank....and reset to new resolution, for this session only at this stage
Leave arandr open
repeat xrandr command to check you are happy with new results
If happy, save the setting for later sessions. In arandr GUI click the download icon (below outputs).
Choose a file name eg 1024.sh and press enter or click the save button
(if you are going from large to smaller, you may not see the save button)
For next login or next startx we automate it by
echo '$HOME/.screenlayout/1024.sh &' > $HOME/.X.d/monitorNote there are periods in this command for hidden directories.
To test it now, run exittc and exit to prompt and then run startx
If unhappy with results....delete $HOME/.X.d/monitor
exit to prompt and startx to get back to your original settings
Good luck
-
So, someone has just broken the firmware-nvidia file on 14x?
Nope
the info says
Comments: for GPU video chipsets
(update) lots deleted so use old TCE if needed
SNIP
2018/12/24 updated (coreplayer2)
2020/06/20 updated (aus9)
Current: 2023/02/04 updated (aus9) has deletions
The build script is difficult enough for me as it is, bearing in mind I am not as good at coding as coreplayer2, Rich Juanito etc etc
http://tinycorelinux.net/14.x/x86_64/tcz/src/firmware/build-firmware.txt
So the info alerts members that there are deletions for this TCE
members might then click on Files in Apps to see if they lose any firmware.
If so, they keep the existing package.
I am aware, that if you never used 13x, you probably did not read
http://forum.tinycorelinux.net/index.php/topic,26139.0.html
-
Thanks aswell to Juanito, Rich patrikg for the help. We would certainly not have reached this result without everyone's help.
Thank you also for acknowledge the great community like Tiny Core Linux are.