Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: t18 on May 29, 2024, 03:35:27 AM
-
Hello,
Tiny Core is new to me. I think it gives old hardware a wonderful chance to come back to life. I want to say thank to all the TC staff.
I've successfully installed it on my Pentium II laptop with 160 Mb RAM, Xvesa works pretty fine. Only Xmms is noisy while I switch among windows while it's running.
But I'd like to install at least software like Abiword, Gnumeric and Gimp, and they need X.
So I installed Xorg but unsuccessfully. Other than xvesa I installed:
- graphics
Xorg
Xorg-dev
Xorg-3D
Xorg-3D-dev
flwm
Xorg-jwm
compiletc
automake
and have built the latest siliconmotion driver, but it doesn't work.
Any way to get X working? Many thanks.
-
Assuming you are using tc-15.x x86.
Boot without loading any extensions then:
tce-load -i Xorg-7.7 flwm aterm wbar
startx
..and x should work.
-
Thank you so much for your reply, Juanito.
Had to reinstall from scratch and now TC is in /dev/sda3, bootable partition.
The network is up and I can ping any website but can't download+install anything.
Tce-load gives me the error " wget: bad address ' ' ".
What did I forget, please?
-
After booting tinycore with a wired network connection does this work:
ping -c2 repo.tinycorelinux.net
-
Hi t18
I just checked, the repo is down. That's why you are getting that error.
-
Hi t18
The repo is back up. tce-load should now work for you.
-
Many thanks Rich, but just now (abt 07:00 GMT) it doesn't work.
"2 packets transmitted, 0 received, 100% loss".
Might it be down again?
-
The firewall blocks pings. Please ping google.com instead.
-
Pinging Google works, downloading from the Tc repo doesn't.
-
It's working for me:
tce-load -w 9vx
Downloading: 9vx.tcz
Connecting to repo.tinycorelinux.net (128.127.66.77:80)
saving to '9vx.tcz'
9vx.tcz 100% |*********************************************************************************************| 1780k 0:00:00 ETA
'9vx.tcz' saved
9vx.tcz: OK
-
Hi t18
Pinging the repo will temporarily lock you out:
... About the ping, that's part of the port scanning protection. You essentially blocked yourself for a short time.
Also, check that your tcemirror file is correct:
tc@E310:~$ cat /opt/tcemirror
http://repo.tinycorelinux.net/
-
You can also set a mirror manually in the file Rich mentioned:
http://wiki.tinycorelinux.net/doku.php?id=wiki:mirrors
-
Also, check that your tcemirror file is correct:
tc@E310:~$ cat /opt/tcemirror
http://repo.tinycorelinux.net/
This was the problem. That file was blank. Fixed. :D
And now...
Assuming you are using tc-15.x x86.
Boot without loading any extensions then:
tce-load -i Xorg-7.7 flwm aterm wbar
startx
..and x should work.
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.
-
Hi t18
... and have built the latest siliconmotion driver, but it doesn't work. ...
Your Xorg.log file shows it's looking for it but can't find it:
[ 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)
After you built the driver, what did you do with it?
-
Hi t18
... and have built the latest siliconmotion driver, but it doesn't work. ...
Your Xorg.log file shows it's looking for it but can't find it:
[ 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)
After you built the driver, what did you do with it?
...
Had to reinstall from scratch and now TC is in /dev/sda3, bootable partition.
...
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.
-
It’s normal for xorg to look for its preferred driver for your hardware, but in your case the siliconmotion driver is a separate package that would need to be compiled.
You could try the modesetting driver, which is included, like this: tce-load -i graphics-KERNEL Xorg-7.7-3d flwm aterm wbar
startx ..but Xorg-7.7-3d might not work with a pentium II.
The resolution can be changed via an Xorg.conf snippet - if you search the forum you should find an example.
-
xf86-video-siliconmotion added to the tc-15.x x86 repo.
So: tce-load -i xf86-video-siliconmotion Xorg-7.7 flwm aterm wbar
startx
-
Unfortunately that driver doesn't work: the screen stays blank and no Xorg.log is created.
I know that many people have had problems with it in the past decades (this is dated 2010-12: https://bugs.freedesktop.org/show_bug.cgi?id=45634), so I'd look for alternative configurations (unless to find a way for it to work properly).
Do you think it would be possible?
-
The silicon motion driver looks to be from 2023.
Did you try the modesetting driver (graphics-KERNEL + Xorg-7.7-3d)?
Why not use Xorg-7.7 on its own with a conf snippet to change the resolution?
-
The silicon motion driver looks to be from 2023.
Yes, it's the latest version but on other distros gives errors like the previous ones.
Did you try the modesetting driver (graphics-KERNEL + Xorg-7.7-3d)?
It seems certain things haven't changed since 2014:
"xf86-video-modesetting definitely won't work, it requires a KMS driver, and there's no such driver for siliconmotion. "
https://bbs.archlinux.org/viewtopic.php?id=187477
Why not use Xorg-7.7 on its own with a conf snippet to change the resolution?
I'll try that and report it to you asap.
-
Hi t18
You can have Xorg create an xorg.conf file for you.
Click the Exit icon
Select Exit to Prompt
Then:
sudo su
Xorg -configure
mv /root/xorg.conf.new /home/tc/
chmod 666 /home/tc/xorg.conf.new
chown tc:staff /home/tc/xorg.conf.new
exit
cp -a /home/tc/xorg.conf.new /home/tc/xorg.conf
startx
editor xorg.confThe screen resolution is usually set somewhere near the
end of the file. Try changing it to 1024x768 and save the file.
Then:
Click the Exit icon
Select Exit to Prompt
sudo mkdir /etc/X11
sudo cp xorg.conf /etc/X11
startx
-
Hi Rich and all,
first I want to point out that using the default Xorg (that works at 800x600), when I "exit to prompt" probably the system does that but the screen remains blank and I don't see the prompt.
I have to reboot via ctrl+alt+canc.
Then tried the "Xorg -configure" but it gives errors, please see the attached log.
Finally I tried "X -config ./xorg.conf" using my conf file put together from previous attempts on other distros, please see it attached.
It doesn't load nor creates any log file.
-
Here's a conf snippet I've used to change the resolution on my laptop - it is placed in /usr/local/share/X11/xorg.conf.d and you can call it 50-resolution or similar:
Section "Device"
Identifier "Intel HD4400"
Driver "intel"
Option "monitor-eDP1" "eDP1"
EndSection
Section "Monitor"
Identifier "eDP1"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Intel HD4400"
Monitor "eDP1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768" "1366x768" "640x384"
EndSubSection
EndSection
You would need to substitute the correct driver and monitor from those you see used in your Xorg.0.log
-
Thank you Juanito, unfortunately that file gets ignored unless I put 8 or 16 depth.
I'd be tempted to switch back to Xvesa if I can run Abiword and Gimp on it.
-
Either on Xvesa and Xorg I get some "trap invalid opcode" errors when starting Gimp or Vlc or Cmus.
Any way to fix them?
-
That means your cpu is too old to run them. Sometimes the package requires a higher processor, sometimes it's just a flag adjustment when compiling.
-
Hi t18
... I get some "trap invalid opcode" errors ...
That's like saying:
Some warning light lit on my dashboard. Why doesn't my car work?
The purpose of an error message is to help pinpoint the source of
the error. By generalizing instead of reporting the exact error
message you defeat its purpose.
"invalid opcode" means your CPU encountered an instruction it
does not support. The rest of the error message includes where
the instruction originated from. It could be from vlc or one of its
dependencies. It's probably from qt-5, but without the complete
message we can't be sure.
You can try capturing the complete message into a file like this:
vlc > vlc.txt 2>&1 Then copy the file to another machine so you can copy/paste
the contents to your next post.
Also, be aware your machine might not have the horsepower or
enough RAM to run some of those programs.
You can also try running the ncurses or command line versions
of vlc:
nvlcor
cvlc
-
That means your cpu is too old to run them. Sometimes the package requires a higher processor, sometimes it's just a flag adjustment when compiling.
I think is a bit old, definitely. I wonder if rebuilding from scratch may be a solution.
Hi t18
... I get some "trap invalid opcode" errors ...
That's like saying:
Some warning light lit on my dashboard. Why doesn't my car work?
The purpose of an error message is to help pinpoint the source of
the error. By generalizing instead of reporting the exact error
message you defeat its purpose.
"invalid opcode" means your CPU encountered an instruction it
does not support. The rest of the error message includes where
the instruction originated from. It could be from vlc or one of its
dependencies. It's probably from qt-5, but without the complete
message we can't be sure.
You can try capturing the complete message into a file like this:
vlc > vlc.txt 2>&1 Then copy the file to another machine so you can copy/paste
the contents to your next post.
Also, be aware your machine might not have the horsepower or
enough RAM to run some of those programs.
You can also try running the ncurses or command line versions
of vlc:
nvlcor
cvlc
The "2>&1" command only gives "Illegal option".
The dmesg output is below:
traps: cmus[3149] trap invalid opcode ip:806cae7 sp:bf91d110 error:0 in cmus[8052000+23000]
traps: gimp[7793] trap invalid opcode ip:b75c43fd sp:bfbb5f50 error:0 in libbabl-0.1.so.0.181.1[b75b1000+21000]
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002186-0x0000000000002186 (\SM06) (20230628/utaddress-204)
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002185-0x0000000000002185 (\SM05) (20230628/utaddress-204)
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002184-0x0000000000002184 (\SM04) (20230628/utaddress-204)
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002183-0x0000000000002183 (\SM03) (20230628/utaddress-204)
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002182-0x0000000000002182 (\SM02) (20230628/utaddress-204)
ACPI Warning: SystemIO range 0x0000000000002180-0x0000000000002188 conflicts with OpRegion 0x0000000000002180-0x0000000000002180 (\SM00) (20230628/utaddress-204)
ACPI: OSL: Resource conflict; ACPI support missing from driver?
traps: vlc-cache-gen[10625] trap invalid opcode ip:b2fbcdc3 sp:bf9ff900 error:0 in libQt5Core.so.5.15.10[b2f87000+1d2000]
-
I think is a bit old, definitely. I wonder if rebuilding from scratch may be a solution.
Babl, gimp and qt-5.x were all built with march=i486.
-
this thread reminded of a recent read of an ancient install:
http://www.infekt.com/ilsa/onesandzeros/amity.html
also it would be nice to know OP machine specs(make/model/version/etc) and any aftermarket modifications/parts/etc.
keywords:
libretto
neomagic
20240605-1426pm-cdt-usa-modified: added some keywords
-
I'll have to head to older software.
I've installed wine on Xvesa (I know it requires Xorg) and everything seems to work but the keyboard. Any trick to enable it?
-
Not sure that the relevant error is "failed to load libgntls".
-
Hi t18
... "failed to load libgntls".
Did you mean libgnutls.so ?
Is gnutls3.6.tcz installed?
It provides:
/usr/local/lib/libgnutls.so
/usr/local/lib/libgnutls.so.30
/usr/local/lib/libgnutls.so.30.26.2Did the error message mention any of those files?
-
Removed audacious and tried again.
The gnutls are installed and I don't see that error any more but the problem persists: the keyboard doesn't work.
Also the Control Panel icons don't work but that could be a problem of wine. I had seen it on older versions of wine.