Tiny Core Base > CorePlus
Please help with X
Rich:
Hi t18
Pinging the repo will temporarily lock you out:
--- Quote from: curaga on December 20, 2021, 03:05:47 AM --- ... About the ping, that's part of the port scanning protection. You essentially blocked yourself for a short time.
--- End quote ---
Also, check that your tcemirror file is correct:
--- Code: ---tc@E310:~$ cat /opt/tcemirror
http://repo.tinycorelinux.net/
--- End code ---
curaga:
You can also set a mirror manually in the file Rich mentioned:
http://wiki.tinycorelinux.net/doku.php?id=wiki:mirrors
t18:
--- Quote from: Rich on June 02, 2024, 08:21:47 AM ---Also, check that your tcemirror file is correct:
--- Code: ---tc@E310:~$ cat /opt/tcemirror
http://repo.tinycorelinux.net/
--- End code ---
--- End quote ---
This was the problem. That file was blank. Fixed. :D
And now...
--- Quote from: Juanito on May 29, 2024, 03:48:12 AM ---Assuming you are using tc-15.x x86.
Boot without loading any extensions then:
--- Code: ---tce-load -i Xorg-7.7 flwm aterm wbar
startx
--- End code ---
..and x should work.
--- End quote ---
GRRREEEAT WORK!!! Congrats and thank you so much my gurus!!!
It works! Now I'd like to fine-tune it like in Xvesa.
At the moment the resolution is 800x600 while should be 1024x768 and the touchpad can't double click on its pad, I have to use buttons.
Are there any more extensions to install to do that?
Attached is the Xorg.0.log file, it has some errors.
Rich:
Hi t18
--- Quote from: t18 on May 29, 2024, 03:35:27 AM --- ... and have built the latest siliconmotion driver, but it doesn't work. ...
--- End quote ---
Your Xorg.log file shows it's looking for it but can't find it:
--- Code: ---[ 355.463] (==) Matched siliconmotion as autoconfigured driver 0
[ 355.463] (==) Matched modesetting as autoconfigured driver 1
[ 355.463] (==) Matched fbdev as autoconfigured driver 2
[ 355.463] (==) Matched vesa as autoconfigured driver 3
[ 355.463] (==) Assigned the driver to the xf86ConfigLayout
[ 355.463] (II) LoadModule: "siliconmotion"
[ 355.466] (WW) Warning, couldn't open module siliconmotion
[ 355.466] (EE) Failed to load module "siliconmotion" (module does not exist, 0)
--- End code ---
After you built the driver, what did you do with it?
t18:
--- Quote from: Rich on June 02, 2024, 11:26:29 PM ---Hi t18
--- Quote from: t18 on May 29, 2024, 03:35:27 AM --- ... and have built the latest siliconmotion driver, but it doesn't work. ...
--- End quote ---
Your Xorg.log file shows it's looking for it but can't find it:
--- Code: ---[ 355.463] (==) Matched siliconmotion as autoconfigured driver 0
[ 355.463] (==) Matched modesetting as autoconfigured driver 1
[ 355.463] (==) Matched fbdev as autoconfigured driver 2
[ 355.463] (==) Matched vesa as autoconfigured driver 3
[ 355.463] (==) Assigned the driver to the xf86ConfigLayout
[ 355.463] (II) LoadModule: "siliconmotion"
[ 355.466] (WW) Warning, couldn't open module siliconmotion
[ 355.466] (EE) Failed to load module "siliconmotion" (module does not exist, 0)
--- End code ---
After you built the driver, what did you do with it?
--- End quote ---
--- Quote from: t18 on June 01, 2024, 12:36:17 PM ---...
Had to reinstall from scratch and now TC is in /dev/sda3, bootable partition.
...
--- End quote ---
I've reinstalled TC from scratch and kept the basic system, as Juanito suggested.
I haven't rebuilt nor reinstalled anything.
The above matches are part of the Xorg process, I've seen them on other distros.
And I wonder why it looks for the correct module and doesn't have it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version