Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: fier on January 11, 2026, 11:09:02 PM
-
I'm trying to use my nvidia graphics with nouveau, but when installing nouveau-6.12.11-tinycore and running:
modprobe nouveau...I just get an error about the wmi module missing. I tried searching for it with the tce command, but no luck.
-
Hi fier
It should be part of the base system. Does it show up here:
ls -l /lib/modules/6.12.11-tinycore/kernel/drivers/platform/x86/wmi*
-
Heya Rich. Sorry for the misunderstanding, I should have read the error more carefully. It says "no such device", the module does exist.
From my research, this could be happening due to my system having no ACPI (I disabled it, as it's buggy). -- As a long shot, I edited the modules.dep file to remove all the dependencies to do with wmi and acpi for nouveau, no dice unfortunately. Same result when specifically defining acpi=off as a boot option.
I tried searching some more, turns out nouveau doesn't seem to necessarily require ACPI, but it does enable some ACPI features if ACPI support is enabled in the kernel. I could not figure out if it was possible to somehow skip those features in the module that was precompiled with ACPI.
Note, I'm not suggesting ACPI be disabled in the kernel, that would be nonsense. I'm just curious if a solution exists.
This thread should probably be moved to TCB Bugs, and renamed appropriately.
-
Hi until you get a better reply as I do not have nvidia chipset and am on 64 bit but you may want to run this command ...SNIP means I am not showing some stuff
modinfo nouveau showing the 64 bit kernel results which may be similar to 32 bit
filename: /lib/modules/6.18.2-tinycore64/kernel.tclocal/drivers/gpu/drm/nouveau/nouveau.ko.gz
author: Nouveau Project
description: nVidia Riva/TNT/GeForce/Quadro/Tesla/Tegra K1+
license: GPL and additional rights
parm: keep_gsp_logging:Migrate the GSP-RM logging debugfs entries upon exit
parm: NVreg_RegistryDwords:A semicolon-separated list of key=integer pairs of GSP-RM registry keys
parm: runpm:disable (0), force enable (1), optimus only default (-1)
parm: atomic:Expose atomic ioctl (default: disabled)
parm: modeset:enable driver (default: auto, 0 = disabled, 1 = enabled, 2 = headless)
parm: noaccel:disable kernel/abi16 acceleration
parm: debug:debug string to pass to driver core
parm: config:option string to pass to driver core
parm: hdmimhz:Force a maximum HDMI pixel clock (in MHz)
parm: duallink:Allow dual-link TMDS (default: enabled)
parm: ignorelid:Ignore ACPI lid status
parm: tv_disable:Disable TV-out detection
parm: mst:Enable DisplayPort multi-stream (default: enabled)
parm: tv_norm:Default TV norm.
Supported: PAL, PAL-M, PAL-N, PAL-Nc, NTSC-M, NTSC-J,
hd480i, hd480p, hd576i, hd576p, hd720p, hd1080i.
Default: PAL
*NOTE* Ignored for cards with external TV encoders.
parm: kms_vram_pushbuf:Place EVO/NVD push buffers in VRAM (default: auto)
parm: vram_pushbuf:Create DMA push buffers in VRAM
alias: pci:v000012D2d*sv*sd*bc03sc*i*
alias: pci:v000010DEd*sv*sd*bc03sc*i*
depends: drm_display_helper,drm,drm_kms_helper,agpgart,ttm,mxm-wmi,drm_gpuvm,gpu-sched,drm_exec,video,wmi,backlight,drm_client_lib,drm_ttm_helper
intree: Y
SNIP not showing any firmware
Now look at the parameters = parm
Notice
modeset
config
duallink
tv_disable
mst
tv_norm
Now the 64 bit TCE contains 2 other modules and if you modinfo those 2 you will see mention of
modinfo ch7006
SNIP
Chrontel ch7006 TV encoder driver
Default: PAL
and above tv_norm we can use that parameter to ntsc if you are not a pal country....if interested
But if you are not interested in tv then you probably might like to disable tv stuff with the parameter
tv_disable=1 (1 means yes so means disable the tv detection)
If you interested in changing away from PAL then the parameter tv_norm can be changed
Now lets look at duallink. ...it mentions TMDS default enabled and looking at the other module we have
modinfo sil164
SNIP
Silicon Image sil164 TMDS transmitter driver
So again, if interested in not that hardware.....you may like to disable TMDS by the parameter
duallink=0
Now according to another distros wiki....this kernel module needs Kernel Mode Setting (KMS)
so it looks like you can not modeset=0 IMHO
Again I do not have your hardware....some people have display port connection to monitor some do not
so looking at parameter mst, which is defaulting to enabled....you may like to try disabling it if not using DP?
mst=0
Obviously....I was hoping to offer advice on boot code for noacpi but I can not spot anything in this module itself
Good luck in testing.
Suggestion....show the full output of command
lsmod
-
above is pretty ugly....and I do not know what kernel modules will depend on your nouveau
Lets pretend none do....must show used by 0
then you can exit to prompt and run.....at the console
sudo rmmod nouveau
sudo modprobe nouveau options <parm-name> with it setting for each parm setting you like to try
eg
sudo modprobe nouveau options duallink=0
Once you know which ones work and improve your visuals....we can then look at automating that with probably
an entry in your /opt/bootlocal.sh
-
Hi fier
... It says "no such device", the module does exist. ...
Maybe it doesn't recognize your video device?
-
I would suggest booting with nothing set onboot and then loading graphics-KERNEL, Xorg-7.7-3d, flwm, aterm and wbar.
Next issue this command: Xorg -nolisten tcp..and check for any error messages.
In addition, after issuing the command above, check /var/log/Xorg.0.log to see if it contains something analogous to this: [ 391.239] (==) Matched intel as autoconfigured driver 0
[ 391.239] (==) Matched modesetting as autoconfigured driver 1
[ 391.239] (==) Matched fbdev as autoconfigured driver 2
[ 391.239] (==) Matched vesa as autoconfigured driver 3..this will let you know which driver your hardware is looking for.
-
Sorry for the late correspondence, I've decided I to stop pursuing this effort for now. Thank you for the help, sorry to waste your time!