Tiny Core Extensions > TCE Corepure64

Gnome Desktop

<< < (4/6) > >>

Juanito:
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:
--- Code: ---$ 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]
--- End code ---

polikuo:
Hi, it looks like I have run into similar condition.

I'm using an old laptop ASUS A8JR.

I boot with bootcode

--- Code: ---base norestore quiet multivt laptop lang='zh_TW.utf8'
--- End code ---

Then, after booting

--- Code: ---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

--- End code ---
(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:

--- Code: ---             Screen Lock disabled
Screen Locking requires the GNOME display manager

--- End code ---

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"

--- Code: ---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

--- End code ---

jazzbiker:
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
--- Code: ---su - tc
--- End code ---
?

polikuo:

--- Quote from: jazzbiker on November 04, 2020, 11:17:14 AM ---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
--- Code: ---su - tc
--- End code ---
?

--- End quote ---

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.

Juanito:
After “su - tc” you should have to enter “gnome-session”, which will start a wayland session.

Does the wayland weston compositor work for you?

Navigation

[0] Message Index

[#] Next page

[*] Previous page