Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: core.dump on March 14, 2020, 08:26:13 AM
-
Hi all,
I'm fairly new to Tiny Core. I was using a CorePure64 10.1 Xorg 7.7 and everything was fine, but recently I had the need to change my graphics card (I switched from my previous GeForce GT 710 to a newer GTX 1650), and after that I could no longer run Xorg correctly (when you enter the graphical environment, all I see is a confusing image on the screen). I suppose the problem is an incompatibility between the new hardware and the currently installed Nvidia driver (nvidia-390.116-4.19.10-tinycore64), in fact this release doesn't seem to support the 1650 chipset. On the other hand, I can't use Xvesa because it's not packaged for 64-bit, and in any case it does not support the resolution of my screen (already tested in a 32-bit temporary installation).
To solve the problem, I probably need the most recent 440.64 nvidia driver (since it has full support for 16xx chipset series), but I'm not able to create a .tcz package... Is there anyone out there who is able to do that?
Thanks in advance! :)
-
Xvesa is not packaged for 64-bit because it is 32-bit only - have you tried Xfbdev?
I don't know if it would work, but you could try the nouveau driver in tc-11.x CorePure64.
-
Yes, I have tried Xfbdev, and both the -nouveau and -nv with the latest TC 11.x release (CorePure64 of course). The result is I'm not able to start the X server (error in waitforX) :(
-
Hi core.dump
... I'm not able to start the X server (error in waitforX) :(
To get more information, execute the first line in your .xsession file. You can do it like this:
`head -n 1 .xsession`Notice the punctuation at the beginning and end of the command. Those are back ticks ` not single quotes '.
That should provide more error information. Then attach a copy of /var/log/Xorg.0.log to your next post.
-
To get more information, execute the first line in your .xsession file. You can do it like this:
`head -n 1 .xsession`Notice the punctuation at the beginning and end of the command. Those are back ticks ` not single quotes '.
That should provide more error information. Then attach a copy of /var/log/Xorg.0.log to your next post.
Ok, thanks... this is what I obtained:
[ 22.117]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 22.117] Build Operating System: Linux 4.19.10-tinycore64 x86_64
[ 22.117] Current Operating System: Linux box 4.19.10-tinycore64 #1999 SMP Tue Dec 18 15:18:54 UTC 2018 x86_64
[ 22.117] Kernel command line: BOOT_IMAGE=/tce/boot/vmlinuz64 quiet waitusb=5 loglevel=3 home=sda1 tce=sda1 opt=sda1 kmap=qwerty/it showapps waitusb=5:UUID="667747a9-9683-4969-804d-aeb5bce13627" tce=UUID="667747a9-9683-4969-804d-aeb5bce13627" initrd=/tce/boot/corepure64.gz
[ 22.117] Build Date: 04 March 2019 10:59:41AM
[ 22.117]
[ 22.117] Current version of pixman: 0.38.4
[ 22.117] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 22.117] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 22.117] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 14 18:24:41 2020
[ 22.117] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[ 22.118] (==) No Layout section. Using the first Screen section.
[ 22.118] (==) No screen section available. Using defaults.
[ 22.118] (**) |-->Screen "Default Screen Section" (0)
[ 22.118] (**) | |-->Monitor "<default monitor>"
[ 22.121] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 22.121] (**) | |-->Device "Nvidia Card"
[ 22.121] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 22.121] (==) Automatically adding devices
[ 22.121] (==) Automatically enabling devices
[ 22.121] (==) Automatically adding GPU devices
[ 22.121] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 22.121] (WW) The directory "/usr/local/lib/X11/fonts/OTF/" does not exist.
[ 22.121] Entry deleted from font path.
[ 22.121] (WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
[ 22.121] Entry deleted from font path.
[ 22.121] (==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/
[ 22.121] (**) ModulePath set to "/usr/local/lib/modules/4.19.10-tinycore64/kernel/drivers/video,/usr/local/lib/xorg/modules/drivers,/usr/local/lib/xorg/modules"
[ 22.121] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 22.121] (II) Loader magic: 0x5aec60
[ 22.121] (II) Module ABI versions:
[ 22.121] X.Org ANSI C Emulation: 0.4
[ 22.121] X.Org Video Driver: 24.0
[ 22.121] X.Org XInput driver : 24.1
[ 22.121] X.Org Server Extension : 10.0
[ 22.131] (--) PCI:*(101@0:0:0) 10de:1f82:1043:86b9 rev 161, Mem @ 0xd7000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000b000/128, BIOS @ 0x????????/131072
[ 22.131] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 22.131] (II) LoadModule: "glx"
[ 22.132] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 22.147] (II) Module glx: vendor="X.Org Foundation"
[ 22.147] compiled for 1.20.4, module version = 1.0.0
[ 22.147] ABI class: X.Org Server Extension, version 10.0
[ 22.147] (II) LoadModule: "nvidia"
[ 22.148] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so
[ 22.252] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 22.252] compiled for 4.0.2, module version = 1.0.0
[ 22.252] Module class: X.Org Video Driver
[ 22.266] (II) NVIDIA dlloader X Driver 390.116 Sun Jan 27 05:57:42 PST 2019
[ 22.266] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 22.268] (--) using VT number 2
[ 22.284] (II) Loading sub module "fb"
[ 22.284] (II) LoadModule: "fb"
[ 22.285] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[ 22.288] (II) Module fb: vendor="X.Org Foundation"
[ 22.288] compiled for 1.20.4, module version = 1.0.0
[ 22.288] ABI class: X.Org ANSI C Emulation, version 0.4
[ 22.288] (II) Loading sub module "wfb"
[ 22.288] (II) LoadModule: "wfb"
[ 22.288] (II) Loading /usr/local/lib/xorg/modules/libwfb.so
[ 22.310] (II) Module wfb: vendor="X.Org Foundation"
[ 22.310] compiled for 1.20.4, module version = 1.0.0
[ 22.310] ABI class: X.Org ANSI C Emulation, version 0.4
[ 22.310] (II) Loading sub module "ramdac"
[ 22.310] (II) LoadModule: "ramdac"
[ 22.310] (II) Module "ramdac" already built-in
[ 22.790] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 22.790] (EE) NVIDIA: system's kernel log for additional error messages and
[ 22.790] (EE) NVIDIA: consult the NVIDIA README for details.
[ 22.790] (EE) No devices detected.
[ 22.790] (EE)
Fatal server error:
[ 22.790] (EE) no screens found(EE)
[ 22.790] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 22.790] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 22.790] (EE)
[ 22.797] (EE) Server terminated with error (1). Closing log file.
-
Hi core.dump
After X fails to start, see if this provides anything useful:
dmesg | tail -n 25
If you do this:
dmesg | tail -n 25 > dmesg.txtYou'll have a text file with the results you can copy from.
-
Hi Rich,
dmesg returns the following:
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
nvidia-nvlink: Nvlink Core is being initialized, major device number 241
nvidia 0000:65:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem
NVRM: The NVIDIA GPU 0000:65:00.0 (PCI ID: 10de:1f82)
NVRM: installed in this system is not supported by the
NVRM: NVIDIA 390.116 driver release.
NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products'
NVRM: in this release's README, available on the operating system
NVRM: specific graphics driver download page at www.nvidia.com.
nvidia: probe of 0000:65:00.0 failed with error -1
NVRM: The NVIDIA probe routine failed for 1 device(s).
NVRM: None of the NVIDIA graphics adapters were initialized!
nvidia-nvlink: Unregistered the Nvlink Core, major device number 241
nvidia-nvlink: Nvlink Core is being initialized, major device number 241
nvidia 0000:65:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem
NVRM: The NVIDIA GPU 0000:65:00.0 (PCI ID: 10de:1f82)
NVRM: installed in this system is not supported by the
NVRM: NVIDIA 390.116 driver release.
NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products'
NVRM: in this release's README, available on the operating system
NVRM: specific graphics driver download page at www.nvidia.com.
nvidia: probe of 0000:65:00.0 failed with error -1
NVRM: The NVIDIA probe routine failed for 1 device(s).
NVRM: None of the NVIDIA graphics adapters were initialized!
nvidia-nvlink: Unregistered the Nvlink Core, major device number 241
-
Hi core.dump
Uninstall the nvidia-390.116 extension. Install xf86-video-nouveau.tcz and xf86-video-nv.tcz. Reboot and see what's returned
in /var/log/Xorg.0.log and dmesg when you try to start X again.
-
I completely re-installed CorePure64 (11.x) and nouveau driver, it seems to work just fine with Xfbdev. I haven't tested Xorg yet, but Xfbdev is ok for me as it requires less resources than Xorg.
Now I have some other annoying problems:
(1) I use a dual monitor setup, but the image is replicated on each screen and not extended;
(2) Mouse buttons don't swap (~/.mouse_config is ignored)
(3) Numlock is always disabled when the X Server starts
How can I solve?
-
The nouveau driver is not used by Xfbdev.
You'll need Xorg for a dual monitor setup.
-
Hi core.dump
(3) Numlock is always disabled when the X Server starts
Install numlockx.tcz.
Create a file in your .X.d directory called NumlockOn (or any other name of your choosing) containing the following command:
numlockx on &The next time your X Server starts, the numlock should be enabled.
-
Hi core.dump
(3) Numlock is always disabled when the X Server starts
Install numlockx.tcz.
Create a file in your .X.d directory called NumlockOn (or any other name of your choosing) containing the following command:
numlockx on &The next time your X Server starts, the numlock should be enabled.
Hi,
I tried but it doesn't work at all... Well many things don't work in TC, actually... :(
-
Hi core.dump
If you enter this in a terminal:
numlockx on
numlockx off
numlockx on
numlockx off
numlockx onDoes your numlock LED turn on and off?
-
Hi core.dump
If you enter this in a terminal:
numlockx on
numlockx off
numlockx on
numlockx off
numlockx onDoes your numlock LED turn on and off?
No, it doesn't work even in terminal. This problem is very annoying... just like mouse buttons that don't swap >:(
-
Hi core.dump
No, it doesn't work even in terminal. This problem is very annoying... just like mouse buttons that don't swap >:(
We are talking about something like aterm or xterm under X, not in console mode. numlockx only works under X.
-
Hi core.dump
No, it doesn't work even in terminal. This problem is very annoying... just like mouse buttons that don't swap >:(
We are talking about something like aterm or xterm under X, not in console mode. numlockx only works under X.
In fact. I use aterm, and it doesn't work.
-
Hi core.dump
After running numlockx on do any errors show up in dmesg:
dmesg | tail -n 25
If you run:
ldd /usr/local/bin/numlockxdo any of the lines returned say not found?
-
Hi Rich,
this is what I get:
tc@box:~$ ldd /usr/local/bin/numlockx
linux-vdso.so.1 (0x00007ffca29ce000)
libXtst.so.6 => /usr/local/lib/libXtst.so.6 (0x00007efec0b6f000)
libXext.so.6 => /usr/local/lib/libXext.so.6 (0x00007efec0b5d000)
libX11.so.6 => /usr/local/lib/libX11.so.6 (0x00007efec0a3f000)
libc.so.6 => /lib/libc.so.6 (0x00007efec08be000)
libXi.so.6 => /usr/local/lib/libXi.so.6 (0x00007efec08ad000)
libxcb.so.1 => /usr/local/lib/libxcb.so.1 (0x00007efec0887000)
libXau.so.6 => /usr/local/lib/libXau.so.6 (0x00007efec0880000)
libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x00007efec0878000)
libdl.so.2 => /lib/libdl.so.2 (0x00007efec0873000)
/lib/ld-linux-x86-64.so.2 (0x00007efec0d81000)
tc@box:~$
As for dmesg, it doesn't return any numlockx-related message :-\
-
Hi core.dump
I think I found an answer, though it won't be the one you want to hear:
... the current numlockx works as expected as long as I boot into an Xorg. Not helpful I know. If I boot into Xfbdev, numlockx has no effect. ...
Found here:
http://forum.tinycorelinux.net/index.php/topic,18751.msg114906.html#msg114906
-
Great :(
OK, let's pretend it's not that important.
Any ideas for making mouse buttons swap? I looked around for a solution but didn't find anything, tried to manually edit ~/.mouse_config with no success, and the (poor) Xfbdev documentation out there doesn't help me.
-
Hi core.dump
If you enter this while X is running:
xmodmap -e 'pointer = 3 2 1 4 5'Does it swap your mouse buttons or return any errors?
-
Hi core.dump
If you enter this while X is running:
xmodmap -e 'pointer = 3 2 1 4 5'Does it swap your mouse buttons or return any errors?
No, it doesn't swap, but returns no error. Maybe Xfbdev doesn't support this feature...?
-
Hi core.dump
I can't really find anything about using xmodmap with Xfbdev .
If you want to try something, I put together a program to swap the buttons. It reads /dev/input/mouse0 , swaps buttons if one is
pressed, and writes it to a FIFO called /tmp/MouseSwap. When Xfbdev is started, use the -mouse option to tell it the FIFO is
the mouse device.
If you want to try it, first verify your mouse is /dev/input/mouse0:
sudo cat /dev/input/mouse0You should see garbage appear as you move the mouse. Hit Ctrl-C to stop it. If you got no response, we first need to figure
out which device is your mouse.
If your mouse is /dev/input/mouse0 you can build the program:
mkdir Mouse
cd Mouse
# Download the attached file into this directory.
tce-load -w compiletc sstrip
tce-load -i compiletc sstrip
gcc -flto -mtune=generic -Os -pipe -Wall -fno-plt MouseSwap.c -o MouseSwap -Wl,-T/usr/local/lib/ldscripts/elf_x86_64.xbn
The first line in your .xsession file should look similar to this:
/usr/local/bin/Xfbdev -nolisten tcp &
Change it so it first starts MouseSwap. Add the -mouse /tmp/MouseSwap,3 option to the Xfbdev command.
/home/tc/Mouse/MouseSwap &
/usr/local/bin/Xfbdev -mouse /tmp/MouseSwap,3 -nolisten tcp &
Now click the Exit icon (or select exit in the desktop menu) and select Exit to Prompt. Then startx and see if mouse works
and has its buttons swapped.
-
I have tried many times without results. I noticed that whatever I specify on the line sudo cat/dev/input/mouse0 in place of mouse0, nothing changes. The same for first line in .xsession.
Well, I've had enough of xfbdev, too many problems. I'm planning on moving to Xorg (in spite of myself).
Anyway, thanks for all your support. :)
-
Hi core.dump
It's possible your mouse isn't listed as /dev/input/mouse0. We can try to find your mouse if you post the output of:
ls -l /dev/inputand
cat /proc/bus/input/devices
-
Hi core.dump
By the way, I did run Xfbdev with the -mouse /tmp/MouseSwap,3 to confirm it was getting mouse data from my program.
-
Thanks a lot, Rich. Although the mouse problem could be solved, I have had many other problems, including (but not limited to) installing Virtualbox, dual monitor support and other things that work perfectly well in Xorg instead.
I've already switched to Xorg, so we can leave this behind. Thank you so much for your assistance and sorry for the waste of time.
-
Hi core.dump
... Thank you so much for your assistance and sorry for the waste of time.
You are welcome. and I didn't consider it a waste of time. I cobbled up some proof of concept code that showed you could slip
another program into the data path between the mouse and the X server.