Tiny Core Linux
Tiny Core Extensions => TCE Corepure64 => Topic started by: mark123 on June 09, 2019, 06:43:13 AM
-
Has anyone successfully installed Gnome Desktop on CorePure64 10? If so what guidelines did you follow and whare are they located. I have had no success trying to install Gnome and boot to the desktop!
-
Yes - you need to install the gnome-session extension and follow the instructions in the info file - note that it will start a wayland session by default and you will need graphics-KERNEL and Xorg-7.7-3d installed.
Edit: I just double-checked: $ xdg-user-dirs-update
$ sudo /usr/local/etc/init.d/dbus start
$ sudo /usr/local/etc/init.d/networkmanager start
$ sudo /usr/local/lib/elogind/elogind --daemon
$ su - tc
$ gnome-session
..works fine
Note also that the locale needs to be set for gnome-terminal to work
-
Thanks Juanito - I will try again!
-
Juanito,
xdg-user-dirs-update (not found in system)
-
You need to load the xdg-user-dirs extension - the gnome-session info file mentions that this is optional
-
This command is not found - sudo /usr/local/etc/init.d/networkmanager start
-
Hi mark123
It's in networkmanager.tcz. Use the Apps utility to check for missing dependencies.
-
How did you install gnome-session? If you used the apps gui all the dependencies should be downloaded.
-
I had forgot to install gnome-session.
The command gnome-session produced a lot of errors about gnome-keyring among others. Perhaps it is my NVIDIA Card.
If I try 32 Bit TinyCore 10 do I use TinyCore or MicroCore as a starting point? I just want to see what the gnome display looks like as I need higher quality text than FLTK can produce.
Can you send a screen shot of your CorePure64 Gnome setup?
-
Hi mark123
... The command gnome-session produced a lot of errors about gnome-keyring among others. Perhaps it is my NVIDIA Card. ...
Did you read:
http://tinycorelinux.net/10.x/x86_64/tcz/gnome-keyring.tcz.info
It says:
Howto:
$ cat ~/.X.d/gnome-keyring
/usr/local/bin/gnome-keyring-daemon --start --components=gpg
/usr/local/bin/gnome-keyring-daemon --start --components=pkcs11
/usr/local/bin/gnome-keyring-daemon --start --components=secrets
/usr/local/bin/gnome-keyring-daemon --start --components=ssh
Which suggests you should create the file ~/.X.d/gnome-keyring containing those 4 lines. Those commands will then execute
right after X starts.
-
Using Gnome will not change what the text looks like in FLTK apps. Each app will keep its look in different environments, and you can use any app in any environment (with some exceptions).
-
The command gnome-session produced a lot of errors about gnome-keyring among others.
OK, but did gnome start? gnome-session will autostart any gnome-keyring daemons it needs.
If I try 32 Bit TinyCore 10 do I use TinyCore or MicroCore as a starting point?
gnome-session is only available in CorePure64
Can you send a screen shot of your CorePure64 Gnome setup?
see attached
-
Juanito,
I appreciate all of your help on this.
No, gnome did not start.
I replaced my NVIDIA 610 with a simpler PCI Video Card NVIDIA GEForce 6200 and tried again.
The command "sudo /usr/local/etc/init.d/networkmanager start" failed.
When I ran the command "su - tc" the system went to the TinyCore Background Screen and I had no menus or a way to exit.
Here is my procedure:
1. Install CorePure64 with no GUI to a 1GB FlashDisk
2. tce-load -wi gnome-session
3. tce-load -wi xdg-user-dirs.
4. tce-load -wi graphics-KERNEL
5. tce-load -wi Xorg-7.7-3d
$ xdg-user-dirs-update (THIS WORKS)
$ sudo /usr/local/etc/init.d/dbus start (THIS WORKS)
$ sudo /usr/local/etc/init.d/networkmanager start (THIS FAILS)
$ sudo /usr/local/lib/elogind/elogind --daemon (THIS WORKS)
$ su - tc (THIS FAILS to a TinyCore GUI Background Screen with NO means to exit)
$ gnome-session (COULD NOT TRY THIS)
-
$ su - tc (THIS FAILS to a TinyCore GUI Background Screen with NO means to exit)
You need to execute all of the commands from the console prompt, not from a gui terminal window.
-
I used CorePure64 so I was using the console prompt! I have no GUI Installed.
Is my written procedure correct? Something must be missing!
-
I don't understand how the command "su - tc" fails to a gui background screen if no gui is running?
In addition, networkmanager is a recursive dependency of gnome-session, so if gnome-session is loaded, then "sudo /usr/local/etc/init.d/networkmanager start" should work.
Rather than setting the various extensions "onboot" by using "tce-load -wi", I suggest you load them like this: $ tce-load -i graphics-KERNEL Xorg-7.7-3d alsa-config gnome-session xdg-user-dirs
$ tce-status -i | grep networkmanager [to check if networkmanager is loaded]
-
Hi, it looks like I have run into similar condition.
I'm using an old laptop ASUS A8JR.
I boot with bootcode
base norestore quiet multivt laptop lang='zh_TW.utf8'
Then, after booting
tce-setdrive
tce-load -i mylocale firmware-iwlwifi firmware-radeon graphics-KERNEL xdg-user-dirs gnome-session
xdg-user-dirs-update
sudo /usr/local/etc/init.d/dbus start
sudo /usr/local/etc/init.d/networkmanager start
sudo /usr/local/lib/elogind/elogind --daemon
su - tc
(Xorg-7.7-3d is a part of gnome-session's dependence)
It looks like the gnome-session is automatically started right after 'su - tc'
This gives me a blank default "core" background with nothing at all.
No cursor, no responses to clicks on the mouse.
If I type <Ctrl> + <Alt> + (<F1> ~ <F7>) randomly,
sometimes a glitchy gnome environment may pop up,
but still no control over anything. (see the photo in attachment)
The notification message says:
Screen Lock disabled
Screen Locking requires the GNOME display manager
Note that I load the firmware-radeon because graphics-KERNEL is yelling for it.
BTW, this is what I got with "networkmanager start" before "elogind --daemon"
Starting Network Manager daemon...
ModemManager[23107]: <info> ModemManager (version 1.6.12) starting in system bus...
ModemManager[23107]: <info> Couldn't check support for device at '/sys/devices/pci:0000:00/0000:00:1c.0/0000:02:00.0': not supported by any plugin
ModemManager[23107]: <info> Couldn't check support for device at '/sys/devices/pci:0000:00/0000:00:1c.2/0000:03:00.0': not supported by any plugin
-
Hi, polikuo!
Do You login not as tc user name? But I don't see "noautologin" bootcode. Do You boot as "tc", then exit and login as another username? Otherwise what is the purpose of su - tc?
-
Hi, polikuo!
Do You login not as tc user name? But I don't see "noautologin" bootcode. Do You boot as "tc", then exit and login as another username? Otherwise what is the purpose of su - tc?
No, I never add any other user.
The boot code is all there, plain and simple.
Load all the extensions I just downloaded.
Then type only the commands I mention above.
-
After “su - tc” you should have to enter “gnome-session”, which will start a wayland session.
Does the wayland weston compositor work for you?
-
After “su - tc” you should have to enter “gnome-session”, which will start a wayland session.
Does the wayland weston compositor work for you?
Yes, weston is working.
boot with base norestore
tce-load -i firmware-radeon graphics-KERNEL weston
XDG_RUNTIME_DIR=/run/user/$(id -u) weston-launch
-
Hi, I'm retrying gnome-session with X11 mode.
I replace "wayland" with "X11" in /usr/local/bin/gnome-session like the info says.
Start the dbus, log out and log in to refresh variables
When the gnome starts, it says
Oh no! Something has gone wrong.
A problem has occured and the system can't recover. Please contact a system administrator
Is there any way to tell gnome to log the errors for troubleshooting ?
Update:
It looks like the string should be in lowercase: "x11"
Please update the info file. :)
Still no wayland, though...
gnome-session x11 is running but glitchy like the photo I uploaded.
However, if I change the background to some other pics, some of them are fine.
Corrupt files ? but the {md5}s look fine
-
info file updated.
In an x11 session, you'll see a certain amount of error messages in /tmp/wm_errors - in a wayland session you'll see a certain amount of error messages on the console when you exit.
You can add "--debug" to the command line in /usr/local/bin/gnome-session, which gives a bunch of output in /tmp/wm_errors or on the console.
Edit: I'm posting this from a gnome wayland session using networkmanager to connect to wifi. I wonder if your error is graphics hardware related?
-
info file updated.
In an x11 session, you'll see a certain amount of error messages in /tmp/wm_errors - in a wayland session you'll see a certain amount of error messages on the console when you exit.
You can add "--debug" to the command line in /usr/local/bin/gnome-session, which gives a bunch of output in /tmp/wm_errors or on the console.
Edit: I'm posting this from a gnome wayland session using networkmanager to connect to wifi. I wonder if your error is graphics hardware related?
Results in system crash with no other mean than hard reset...
The keyboard wouldn't work, the cursor doesn't appear, no way to check /tmp/wm_errors
-
OK, managed to save the file with some scripting
The message exceeds the maximum allowed length (20000 characters).
-
I'd say the problem is here:
(gnome-shell:25677): mutter-WARNING **: 09:55:26.524: Failed to create backend: Could not get session ID: User 1001 has no sessions
gnome-session-binary[25610]: DEBUG(+): GsmAutostartApp: (pid:25677) done (status:1)
gnome-session-binary[25610]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
..which would seem to be a problem with elogind.
To simplify things, does this work from the console prompt: $ tce-load -i graphics-KERNEL gnome-session xdg-user-dirs shadow [you may need to add something for your graphics hardware]
$ xdg-user-dirs-update [not strictly necessary, this should happen automatically]
$ sudo /usr/local/etc/init.d/dbus start
$ sudo /usr/local/lib/elogind/elogind --daemon
$ su - tc
$ gnome-session
on my laptop it takes several seconds for the wayland session to start
-
Hi, I still can't get gnome working in wayland mode on my laptop.
Occasionally, I could see reports of missing libraries.
libwavpack.so
libmp3lame.so
libdv.so
libx265.so
libIlmImf-2_2.so
libopenal.so
libneon.so
libfdk-aac.so
libfaad.so
libfaac.so
libssh2.so
libass.so
libcdda_interface.so
These shared objects can be found in
wavpack.tcz
lame.tcz
libdv.tcz
x265.tcz
openexr.tcz
openal.tcz
neon.tcz
fdk-aac.tcz
faad.tcz
faac.tcz
libssh2.tcz
libass.tcz
cdparanoia.tcz
But even if I load these packages, gnome just wouldn't run.
Thought about the possibility of failing hardware, I borrowed a Ryzen 3 PC and started fresh on it.
This time the system freezes whenever the graphics-KERNEL loads.
I tried running gnome without graphics-KERNEL, still no luck. :-\
-
Those extensions are optional deps of gst-plugins-* and should not influence gnome-session startup.
gnome-session will not run without 3d acceleration, so graphics-KERNEL is required.
You could try running /usr/local/lib/gnome-session/gnome-session-check-accelerated to see if that gives any clues.