| View previous topic :: View next topic |
| Author |
Message |
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
 Posted: Wed Feb 03, 2021 5:35 am Post subject: cannot startx as my normal user [SOLVED] |
 |
|
This is embarrassing.
I took xdm (lightdm) out of default, stopped xdm, logged out (even rebooted), but cannot startx as my normal user.
The exact same .xinitrc that works perfectly on my other box, brings me to either a blank gray or black screen with a mouse cursor but no controls, or a black screen with no mouse. I can use CTRL/ALT/BACKSPACE to stop X and go back to the login shell, but that's it.
I ssh from other box, start xdm, and login prompt and desktop work fine as normal. I'm stumped. I'm not the only one having startx as user problems, as I've been following this thread here: https://forums.gentoo.org/viewtopic-t-1129155.html Xorg.0.log does not show any meaningful errors or warnings.
| Code: | [ 1523.722] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1523.722] (WW) Warning, couldn't open module fbdev
[ 1523.723] (WW) Falling back to old probe method for modesetting
[ 1523.723] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
|
I get these same errors in Xorg.0.log running from xdm also. It's actually running radeon module.
| Code: | lspci -v ...
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] (prog-if 00 [VGA controller])
Subsystem: Pegatron Turks PRO [Radeon HD 7570]
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fe620000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
...
|
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi
Last edited by figueroa on Sun Apr 04, 2021 2:03 pm; edited 1 time in total |
|
| Back to top |
|
 |
nathanlkoch
Apprentice
Joined: 31 Jan 2021
Posts: 163
Location: Earth / Sol
|
| Posted: Wed Feb 03, 2021 7:09 am Post subject: |
|
|
| figueroa wrote: | This is embarrassing.
I took xdm (lightdm) out of default, stopped xdm, logged out (even rebooted), but cannot startx as my normal user.
The exact same .xinitrc that works perfectly on my other box, brings me to either a blank gray or black screen with a mouse cursor but no controls, or a black screen with no mouse. I can use CTRL/ALT/BACKSPACE to stop X and go back to the login shell, but that's it.
I ssh from other box, start xdm, and login prompt and desktop work fine as normal. I'm stumped. I'm not the only one having startx as user problems, as I've been following this thread here: https://forums.gentoo.org/viewtopic-t-1129155.html Xorg.0.log does not show any meaningful errors or warnings.
| Code: | [ 1523.722] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1523.722] (WW) Warning, couldn't open module fbdev
[ 1523.723] (WW) Falling back to old probe method for modesetting
[ 1523.723] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
|
I get these same errors in Xorg.0.log running from xdm also. It's actually running radeon module.
| Code: | lspci -v ...
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] (prog-if 00 [VGA controller])
Subsystem: Pegatron Turks PRO [Radeon HD 7570]
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fe620000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
...
|
|
Has your kernel changed or have you applied something that would change your initramfs. I have only been using Gentoo for a few days but I have learned that if you don't modify genkernel or dracut to apply certain settings or grab a previous kernel config it will build on default options. If you have any kernel mods. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Feb 03, 2021 2:15 pm Post subject: |
|
|
| figueroa wrote: | | This is embarrassing.... |
Had this trouble the other day in stable amd64. I cloned an amd64 system that has an nvidia card and built-in radeon graphics to a computer newly built with new drives, case, and power supply plus odds and ends including a different brand k10 mobo with built-in radeon graphics only. Only the original system, the kerel builds both modules, nouveau and radeon and I black list radeon. So on the clone I blacklisted nouveau and instead of radeon, but X wouldn't start, complaining that it can't find the nouveau driver. It turned out that there was an explicit nouveau listed in xorg,conf.d/15-video I merely commented that out of 15-video, leaving a blank file and on reboot Xorg found radeon and came up. It did have the gray screen but there were no Xorg errors or xdm errors. It's intende4d as a headless video recorder anyway so I just deleted xdm and xdm-setup from rc-update.
The point is to check your /etc/X11/xorg.conf.d for anything forced that may not be right or blocking a fallback.
BTW, I'm two weeks behind on syncing so I appreciate this thread very much. It led me to add everything X to my local overlay so I am not caught without an X display on the workstations.
Am I understanding that xdm is going away or, as the ebuild suggests, only the the openrc init scripts are being changed and renamed? |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Wed Feb 03, 2021 2:29 pm Post subject: |
|
|
| figueroa wrote: | | The exact same .xinitrc that works perfectly on my other box, brings me to either a blank gray or black screen with a mouse cursor but no controls, or a black screen with no mouse. I can use CTRL/ALT/BACKSPACE to stop X and go back to the login shell, but that's it. |
Does changing to tty2 with Ctrl + Alt + F2 work while the blank screen is showing? If yes, post the output of ps axf -o pid,args. You can omit everything that isn't the process tree rooted at your login shell.
The ouput of loginctl just before running startx as your regular user would be helpful, as well as your whole Xorg.0.log.
| figueroa wrote: | | Code: | lspci -v ...
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] (prog-if 00 [VGA controller])
Subsystem: Pegatron Turks PRO [Radeon HD 7570]
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fe620000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
...
|
|
That's the kernel module. The X11 video driver will be shown in Xorg.0.log.
EDIT to add:
| Tony0945 wrote: | | Am I understanding that xdm is going away or, as the ebuild suggests, only the the openrc init scripts are being changed and renamed? |
The latter.
Last edited by GDH-gentoo on Wed Feb 03, 2021 2:54 pm; edited 1 time in total |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Wed Feb 03, 2021 2:33 pm Post subject: |
|
|
| Tony0945 wrote: | | It led me to add everything X to my local overlay so I am not caught without an X display on the workstations. |
Nothing of that kind is going to happen.............
| Tony0945 wrote: | | Am I understanding that xdm is going away or, as the ebuild suggests, only the the openrc init scripts are being changed and renamed? |
xorg-server[-systemd] is pulling in the required d-m-i package anyway, for the foreseeable future, then the dependency will likely be transferred to the DMs. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Feb 03, 2021 2:38 pm Post subject: |
|
|
| asturm wrote: | | xorg-server[-systemd] is pulling in the required d-m-i package anyway, for the foreseeable future, then the dependency will likely be transferred to the DMs. |
Thank you for the quick answer. |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Thu Feb 04, 2021 3:59 am Post subject: |
|
|
| GDH-gentoo wrote: | | figueroa wrote: | | The exact same .xinitrc that works perfectly on my other box, brings me to either a blank gray or black screen with a mouse cursor but no controls, or a black screen with no mouse. I can use CTRL/ALT/BACKSPACE to stop X and go back to the login shell, but that's it. |
Does changing to tty2 with Ctrl + Alt + F2 work while the blank screen is showing? If yes, post the output of ps axf -o pid,args. You can omit everything that isn't the process tree rooted at your login shell. |
Thanks for asking.
Yes, Ctrl+Alt+F2 through F6 show me a login prompt. Ctrl+Alt+F1 takes me back to gray screen with mouse pointer. Ctrl+Alt+F7 takes to to back screen. I'm logged in now temporarily by starting xdm with sudo.
I'm not sure how to OMIT what isn't the "process tree rooted at your login shell" so here is the entire output of "ps axf -o pid,args" which is just before entering startx.
| Code: |
PID COMMAND
2 [kthreadd]
3 \_ [rcu_gp]
4 \_ [rcu_par_gp]
5 \_ [kworker/0:0-events]
6 \_ [kworker/0:0H-kblockd]
7 \_ [kworker/u16:0-events_unbound]
8 \_ [mm_percpu_wq]
9 \_ [ksoftirqd/0]
10 \_ [rcu_sched]
11 \_ [migration/0]
12 \_ [cpuhp/0]
13 \_ [cpuhp/1]
14 \_ [migration/1]
15 \_ [ksoftirqd/1]
16 \_ [kworker/1:0-events]
17 \_ [kworker/1:0H-kblockd]
18 \_ [cpuhp/2]
19 \_ [migration/2]
20 \_ [ksoftirqd/2]
21 \_ [kworker/2:0-events]
22 \_ [kworker/2:0H-kblockd]
23 \_ [cpuhp/3]
24 \_ [migration/3]
25 \_ [ksoftirqd/3]
26 \_ [kworker/3:0-events_freezable_power_]
27 \_ [kworker/3:0H-kblockd]
28 \_ [cpuhp/4]
29 \_ [migration/4]
30 \_ [ksoftirqd/4]
31 \_ [kworker/4:0-events]
32 \_ [kworker/4:0H-kblockd]
33 \_ [cpuhp/5]
34 \_ [migration/5]
35 \_ [ksoftirqd/5]
36 \_ [kworker/5:0-events]
37 \_ [kworker/5:0H]
38 \_ [cpuhp/6]
39 \_ [migration/6]
40 \_ [ksoftirqd/6]
41 \_ [kworker/6:0-events]
42 \_ [kworker/6:0H-kblockd]
43 \_ [cpuhp/7]
44 \_ [migration/7]
45 \_ [ksoftirqd/7]
46 \_ [kworker/7:0-events_power_efficient]
47 \_ [kworker/7:0H-kblockd]
48 \_ [kdevtmpfs]
49 \_ [netns]
50 \_ [kworker/u16:1-events_unbound]
54 \_ [kworker/3:1-events_freezable_power_]
58 \_ [kauditd]
62 \_ [kworker/u16:2-events_unbound]
67 \_ [kworker/u16:3-events_unbound]
70 \_ [kworker/6:1-events]
76 \_ [kworker/0:1-events]
77 \_ [kworker/7:1-events]
93 \_ [kworker/u16:4-events_unbound]
104 \_ [kworker/5:1-mm_percpu_wq]
109 \_ [kworker/4:1-events_power_efficient]
200 \_ [kworker/2:1-events]
444 \_ [kworker/1:1-events]
445 \_ [oom_reaper]
446 \_ [writeback]
448 \_ [kcompactd0]
449 \_ [khugepaged]
459 \_ [cryptd]
473 \_ [kblockd]
633 \_ [ata_sff]
648 \_ [edac-poller]
663 \_ [watchdogd]
760 \_ [rpciod]
761 \_ [kworker/u17:0]
762 \_ [xprtiod]
815 \_ [kswapd0]
928 \_ [nfsiod]
992 \_ [acpi_thermal_pm]
1021 \_ [ttm_swap]
1085 \_ [scsi_eh_0]
1086 \_ [scsi_tmf_0]
1090 \_ [scsi_eh_1]
1091 \_ [scsi_tmf_1]
1094 \_ [scsi_eh_2]
1095 \_ [scsi_tmf_2]
1098 \_ [scsi_eh_3]
1099 \_ [scsi_tmf_3]
1102 \_ [scsi_eh_4]
1103 \_ [scsi_tmf_4]
1106 \_ [scsi_eh_5]
1107 \_ [scsi_tmf_5]
1110 \_ [kworker/u16:5-events_unbound]
1111 \_ [kworker/u16:6-events_unbound]
1112 \_ [kworker/u16:7-events_unbound]
1114 \_ [kworker/u16:8-events_unbound]
1133 \_ [kworker/u16:9-events_unbound]
1181 \_ [kworker/3:2-mm_percpu_wq]
1223 \_ [kworker/7:2-pm]
1227 \_ [kworker/7:3-events]
1268 \_ [kworker/7:4-events]
1279 \_ [kworker/7:5]
1282 \_ [kworker/5:2-pm]
1296 \_ [kworker/5:3-events]
1297 \_ [kworker/5:4-events]
1298 \_ [kworker/5:5-pm]
1312 \_ [kworker/3:1H-kblockd]
1314 \_ [kworker/0:1H-kblockd]
1315 \_ [kworker/4:1H-kblockd]
1320 \_ [kworker/4:2-usb_hub_wq]
1359 \_ [kworker/0:2-events]
1363 \_ [kworker/6:1H-kblockd]
1369 \_ [jbd2/sda1-8]
1370 \_ [ext4-rsv-conver]
1375 \_ [kworker/7:1H-kblockd]
1382 \_ [kworker/2:1H-kblockd]
1420 \_ [kworker/6:2-events]
1428 \_ [scsi_eh_6]
1429 \_ [scsi_tmf_6]
1430 \_ [usb-storage]
1456 \_ [kworker/1:1H-kblockd]
1511 \_ [kworker/1:2-mm_percpu_wq]
1512 \_ [kworker/5:1H-kblockd]
2146 \_ [iprt-VBoxWQueue]
2147 \_ [iprt-VBoxTscThr]
2153 \_ [kworker/2:2-mm_percpu_wq]
2202 \_ [kworker/3:3-events]
2203 \_ [kworker/3:4-events_freezable_power_]
2204 \_ [kworker/3:5-events_freezable_power_]
2205 \_ [kworker/3:6]
2264 \_ [firewire]
2271 \_ [firewire_ohci]
2283 \_ [cfg80211]
2496 \_ [uas]
2673 \_ [jbd2/sda2-8]
2674 \_ [ext4-rsv-conver]
2675 \_ [jbd2/sda3-8]
2676 \_ [ext4-rsv-conver]
2677 \_ [jbd2/sda5-8]
2678 \_ [ext4-rsv-conver]
1 init [3]
2068 /sbin/udevd
2801 /usr/bin/dbus-daemon --system
2830 elogind-daemon
3098 metalog [MASTER]
3099 \_ metalog [KERNEL]
3127 /usr/sbin/acpid
3457 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf -P /run/apcupsd/apcupsd.pid
3519 /usr/sbin/crond
3547 avahi-daemon: running [bethel.local]
3548 \_ avahi-daemon: chroot helper
3582 /usr/sbin/cupsd -f -c /etc/cups/cupsd.conf -s /etc/cups/cups-files.conf
3638 /sbin/rpcbind
3670 /sbin/rpc.statd --no-notify
3731 /usr/sbin/rpc.idmapd
3827 /usr/sbin/ntpd -p /var/run/ntpd.pid -g
3968 /usr/libexec/postfix/master -w
3969 \_ pickup -l -t unix -u
3970 \_ qmgr -l -t unix -u
3999 /usr/bin/rsync --daemon
4032 /usr/sbin/saned -a saned
4033 \_ /usr/sbin/saned -a saned
4062 /usr/sbin/smartd -p /run/smartd.pid
4095 sshd: /usr/sbin/sshd -o PidFile=/run/sshd.pid -f /etc/ssh/sshd_config [listener] 0 of 10-100 startups
4128 /usr/bin/perl /usr/sbin/x2gocleansessions
4164 /bin/login --
4206 \_ -bash
4629 \_ ps axf -o pid,args
4165 /sbin/agetty 38400 tty2 linux
4167 /sbin/agetty 38400 tty3 linux
4168 /sbin/agetty 38400 tty4 linux
4169 /sbin/agetty 38400 tty5 linux
4170 /sbin/agetty 38400 tty6 linux
4323 /usr/sbin/gpm -m /dev/input/mice -t ps2
|
| GDH-gentoo wrote: | | The ouput of loginctl just before running startx as your regular user would be helpful, as well as your whole Xorg.0.log. |
| Code: |
SESSION UID USER SEAT TTY
1 1000 figueroa seat0 tty1
1 sessions listed.
|
And full Xorg.0.log:
https://dpaste.com/8FB5TW34E
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
nathanlkoch
Apprentice
Joined: 31 Jan 2021
Posts: 163
Location: Earth / Sol
|
| Posted: Thu Feb 04, 2021 4:16 am Post subject: |
|
|
| figueroa wrote: | | GDH-gentoo wrote: | | figueroa wrote: | | The exact same .xinitrc that works perfectly on my other box, brings me to either a blank gray or black screen with a mouse cursor but no controls, or a black screen with no mouse. I can use CTRL/ALT/BACKSPACE to stop X and go back to the login shell, but that's it. |
Does changing to tty2 with Ctrl + Alt + F2 work while the blank screen is showing? If yes, post the output of ps axf -o pid,args. You can omit everything that isn't the process tree rooted at your login shell. |
Thanks for asking.
Yes, Ctrl+Alt+F2 through F6 show me a login prompt. Ctrl+Alt+F1 takes me back to gray screen with mouse pointer. Ctrl+Alt+F7 takes to to back screen. I'm logged in now temporarily by starting xdm with sudo.
I'm not sure how to OMIT what isn't the "process tree rooted at your login shell" so here is the entire output of "ps axf -o pid,args" which is just before entering startx.
| Code: |
PID COMMAND
2 [kthreadd]
3 \_ [rcu_gp]
4 \_ [rcu_par_gp]
5 \_ [kworker/0:0-events]
6 \_ [kworker/0:0H-kblockd]
7 \_ [kworker/u16:0-events_unbound]
8 \_ [mm_percpu_wq]
9 \_ [ksoftirqd/0]
10 \_ [rcu_sched]
11 \_ [migration/0]
12 \_ [cpuhp/0]
13 \_ [cpuhp/1]
14 \_ [migration/1]
15 \_ [ksoftirqd/1]
16 \_ [kworker/1:0-events]
17 \_ [kworker/1:0H-kblockd]
18 \_ [cpuhp/2]
19 \_ [migration/2]
20 \_ [ksoftirqd/2]
21 \_ [kworker/2:0-events]
22 \_ [kworker/2:0H-kblockd]
23 \_ [cpuhp/3]
24 \_ [migration/3]
25 \_ [ksoftirqd/3]
26 \_ [kworker/3:0-events_freezable_power_]
27 \_ [kworker/3:0H-kblockd]
28 \_ [cpuhp/4]
29 \_ [migration/4]
30 \_ [ksoftirqd/4]
31 \_ [kworker/4:0-events]
32 \_ [kworker/4:0H-kblockd]
33 \_ [cpuhp/5]
34 \_ [migration/5]
35 \_ [ksoftirqd/5]
36 \_ [kworker/5:0-events]
37 \_ [kworker/5:0H]
38 \_ [cpuhp/6]
39 \_ [migration/6]
40 \_ [ksoftirqd/6]
41 \_ [kworker/6:0-events]
42 \_ [kworker/6:0H-kblockd]
43 \_ [cpuhp/7]
44 \_ [migration/7]
45 \_ [ksoftirqd/7]
46 \_ [kworker/7:0-events_power_efficient]
47 \_ [kworker/7:0H-kblockd]
48 \_ [kdevtmpfs]
49 \_ [netns]
50 \_ [kworker/u16:1-events_unbound]
54 \_ [kworker/3:1-events_freezable_power_]
58 \_ [kauditd]
62 \_ [kworker/u16:2-events_unbound]
67 \_ [kworker/u16:3-events_unbound]
70 \_ [kworker/6:1-events]
76 \_ [kworker/0:1-events]
77 \_ [kworker/7:1-events]
93 \_ [kworker/u16:4-events_unbound]
104 \_ [kworker/5:1-mm_percpu_wq]
109 \_ [kworker/4:1-events_power_efficient]
200 \_ [kworker/2:1-events]
444 \_ [kworker/1:1-events]
445 \_ [oom_reaper]
446 \_ [writeback]
448 \_ [kcompactd0]
449 \_ [khugepaged]
459 \_ [cryptd]
473 \_ [kblockd]
633 \_ [ata_sff]
648 \_ [edac-poller]
663 \_ [watchdogd]
760 \_ [rpciod]
761 \_ [kworker/u17:0]
762 \_ [xprtiod]
815 \_ [kswapd0]
928 \_ [nfsiod]
992 \_ [acpi_thermal_pm]
1021 \_ [ttm_swap]
1085 \_ [scsi_eh_0]
1086 \_ [scsi_tmf_0]
1090 \_ [scsi_eh_1]
1091 \_ [scsi_tmf_1]
1094 \_ [scsi_eh_2]
1095 \_ [scsi_tmf_2]
1098 \_ [scsi_eh_3]
1099 \_ [scsi_tmf_3]
1102 \_ [scsi_eh_4]
1103 \_ [scsi_tmf_4]
1106 \_ [scsi_eh_5]
1107 \_ [scsi_tmf_5]
1110 \_ [kworker/u16:5-events_unbound]
1111 \_ [kworker/u16:6-events_unbound]
1112 \_ [kworker/u16:7-events_unbound]
1114 \_ [kworker/u16:8-events_unbound]
1133 \_ [kworker/u16:9-events_unbound]
1181 \_ [kworker/3:2-mm_percpu_wq]
1223 \_ [kworker/7:2-pm]
1227 \_ [kworker/7:3-events]
1268 \_ [kworker/7:4-events]
1279 \_ [kworker/7:5]
1282 \_ [kworker/5:2-pm]
1296 \_ [kworker/5:3-events]
1297 \_ [kworker/5:4-events]
1298 \_ [kworker/5:5-pm]
1312 \_ [kworker/3:1H-kblockd]
1314 \_ [kworker/0:1H-kblockd]
1315 \_ [kworker/4:1H-kblockd]
1320 \_ [kworker/4:2-usb_hub_wq]
1359 \_ [kworker/0:2-events]
1363 \_ [kworker/6:1H-kblockd]
1369 \_ [jbd2/sda1-8]
1370 \_ [ext4-rsv-conver]
1375 \_ [kworker/7:1H-kblockd]
1382 \_ [kworker/2:1H-kblockd]
1420 \_ [kworker/6:2-events]
1428 \_ [scsi_eh_6]
1429 \_ [scsi_tmf_6]
1430 \_ [usb-storage]
1456 \_ [kworker/1:1H-kblockd]
1511 \_ [kworker/1:2-mm_percpu_wq]
1512 \_ [kworker/5:1H-kblockd]
2146 \_ [iprt-VBoxWQueue]
2147 \_ [iprt-VBoxTscThr]
2153 \_ [kworker/2:2-mm_percpu_wq]
2202 \_ [kworker/3:3-events]
2203 \_ [kworker/3:4-events_freezable_power_]
2204 \_ [kworker/3:5-events_freezable_power_]
2205 \_ [kworker/3:6]
2264 \_ [firewire]
2271 \_ [firewire_ohci]
2283 \_ [cfg80211]
2496 \_ [uas]
2673 \_ [jbd2/sda2-8]
2674 \_ [ext4-rsv-conver]
2675 \_ [jbd2/sda3-8]
2676 \_ [ext4-rsv-conver]
2677 \_ [jbd2/sda5-8]
2678 \_ [ext4-rsv-conver]
1 init [3]
2068 /sbin/udevd
2801 /usr/bin/dbus-daemon --system
2830 elogind-daemon
3098 metalog [MASTER]
3099 \_ metalog [KERNEL]
3127 /usr/sbin/acpid
3457 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf -P /run/apcupsd/apcupsd.pid
3519 /usr/sbin/crond
3547 avahi-daemon: running [bethel.local]
3548 \_ avahi-daemon: chroot helper
3582 /usr/sbin/cupsd -f -c /etc/cups/cupsd.conf -s /etc/cups/cups-files.conf
3638 /sbin/rpcbind
3670 /sbin/rpc.statd --no-notify
3731 /usr/sbin/rpc.idmapd
3827 /usr/sbin/ntpd -p /var/run/ntpd.pid -g
3968 /usr/libexec/postfix/master -w
3969 \_ pickup -l -t unix -u
3970 \_ qmgr -l -t unix -u
3999 /usr/bin/rsync --daemon
4032 /usr/sbin/saned -a saned
4033 \_ /usr/sbin/saned -a saned
4062 /usr/sbin/smartd -p /run/smartd.pid
4095 sshd: /usr/sbin/sshd -o PidFile=/run/sshd.pid -f /etc/ssh/sshd_config [listener] 0 of 10-100 startups
4128 /usr/bin/perl /usr/sbin/x2gocleansessions
4164 /bin/login --
4206 \_ -bash
4629 \_ ps axf -o pid,args
4165 /sbin/agetty 38400 tty2 linux
4167 /sbin/agetty 38400 tty3 linux
4168 /sbin/agetty 38400 tty4 linux
4169 /sbin/agetty 38400 tty5 linux
4170 /sbin/agetty 38400 tty6 linux
4323 /usr/sbin/gpm -m /dev/input/mice -t ps2
|
| GDH-gentoo wrote: | | The ouput of loginctl just before running startx as your regular user would be helpful, as well as your whole Xorg.0.log. |
| Code: |
SESSION UID USER SEAT TTY
1 1000 figueroa seat0 tty1
1 sessions listed.
|
And full Xorg.0.log:
https://dpaste.com/8FB5TW34E |
Can you startx as a nonroot user? say "startx /usr/bin/startfluxbox"? Have you tried disabling xdm in "rc-service xdm stop" "rc-update del xdm default" and use the new display-manager option? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Thu Feb 04, 2021 4:29 am Post subject: |
|
|
| Anathonous wrote: |
...
Can you startx as a nonroot user? say "startx /usr/bin/startfluxbox"? Have you tried disabling xdm in "rc-service xdm stop" "rc-update del xdm default" and use the new display-manager option? |
That's the whole point of the post. I cannot startx as my user. I can startx as root. I can run from xdm (with lightdm). I did not try the new display manager option. I don't think that's a discriminator.
So, for the time being till I figure this out, I'm stuck with using the display manager.
I note that there are a lot of posts recently, even today, from users who cannot startx as an ordinary user.
Note: It's not necessary to quote another users entire huge post in order to reply. It's a kindness to edit your work.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
nathanlkoch
Apprentice
Joined: 31 Jan 2021
Posts: 163
Location: Earth / Sol
|
| Posted: Thu Feb 04, 2021 5:47 am Post subject: |
|
|
| figueroa wrote: | | Anathonous wrote: |
...
Can you startx as a nonroot user? say "startx /usr/bin/startfluxbox"? Have you tried disabling xdm in "rc-service xdm stop" "rc-update del xdm default" and use the new display-manager option? |
That's the whole point of the post. I cannot startx as my user. I can startx as root. I can run from xdm (with lightdm). I did not try the new display manager option. I don't think that's a discriminator.
So, for the time being till I figure this out, I'm stuck with using the display manager.
I note that there are a lot of posts recently, even today, from users who cannot startx as an ordinary user.
Note: It's not necessary to quote another users entire huge post in order to reply. It's a kindness to edit your work. |
you have to "rc-update add elogind boot" make sure its not running as default "rc-update del elogind default" do del first. then add. Give that a try.
I should ask you first, are you using systemd or initd? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Thu Feb 04, 2021 6:20 am Post subject: |
|
|
I'm not using systemd and I'm not new at this. elogind starts in boot. My almost identical but older x86 box does not use a display manager and runs startx without issue. This amd64 box used to do so also. I've been running startx for 25 years so I'm a bit frustrated.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Thu Feb 04, 2021 1:23 pm Post subject: |
|
|
| figueroa wrote: | | Yes, Ctrl+Alt+F2 through F6 show me a login prompt. [...] I'm not sure how to OMIT what isn't the "process tree rooted at your login shell" so here is the entire output of "ps axf -o pid,args" which is just before entering startx. |
Can you repeat that after startx, and after changing to a different tty while the blank screen is showing? Also, change the command to ps axf -o pid,tty,args for better readability.
By the "process tree rooted at your login shell" I mean, for example, something like this:
| Code: | $ ps axf -o pid,tty,args
PID TT COMMAND
[...]
485 tty2 /bin/login --
722 tty2 \_ -bash
724 tty2 \_ ps axf -o pid,tty,args
[...]
491 tty1 /bin/login --
540 tty1 \_ -bash
542 tty1 \_ /bin/sh /usr/bin/startx
559 tty1 \_ xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth...
560 tty1 \_ /usr/bin/X -nolisten tcp -keeptty :0 -auth /tmp/serverauth.... vt1
566 tty1 \_ /bin/sh /etc/X11/Sessions/openbox
628 tty1 \_ /usr/bin/openbox --startup /usr/libexec/openbox-autostart OPENBOX |
The idea is being able to see how many of the processes that startx should launch actually start.
| figueroa wrote: | | Code: |
SESSION UID USER SEAT TTY
1 1000 figueroa seat0 tty1
1 sessions listed.
|
|
OK.
| Code: | [ 614.416] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[...]
[ 614.416] (II) RADEON: Driver for ATI/AMD Radeon chipsets: |
OK, the radeon video driver it is. Huh, there is still some code path there that wants to run xf86EnableIO(), but it shouldn't be the same one as for the r128 driver...
| Code: | | [ 614.418] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) |
That may or may not be the problem. I guess you don't have that line in the Xorg.0.log file produced when you use a display manager, right? Do you see any other differences between the logs? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Thu Feb 04, 2021 3:38 pm Post subject: |
|
|
| GDH-gentoo wrote: | | Can you repeat that after startx, and after changing to a different tty while the blank screen is showing? Also, change the command to ps axf -o pid,tty,args for better readability. |
Thanks for asking again. Here it is:
| Code: |
24658 tty1 /bin/login --
24708 tty1 \_ -bash
27907 tty1 \_ /bin/sh /usr/bin/startx
27924 tty1 \_ xinit /home/figueroa/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.Qkv4hffe5V
27925 tty1 \_ /usr/bin/X -nolisten tcp -keeptty :0 -auth /tmp/serverauth.Qkv4hffe5V vt1
27934 tty1 \_ sh /home/figueroa/.xinitrc
27940 tty1 \_ /usr/bin/openbox --startup /usr/libexec/openbox-autostart OPENBOX
25993 tty2 /bin/login --
28048 tty2 \_ -bash
28087 tty2 \_ ps axf -o pid,tty,args
27943 tty1 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/openbox-session
27944 ? /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
27956 tty1 lxpanel
27957 tty1 pcmanfm --desktop
27958 tty1 xscreensaver
27959 tty1 conky -d
27966 ? /usr/libexec/gvfsd
|
| GDH-gentoo wrote: | Huh, there is still some code path there that wants to run xf86EnableIO(), but it shouldn't be the same one as for the r128 driver...
| Code: | | [ 614.418] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) |
That may or may not be the problem. I guess you don't have that line in the Xorg.0.log file produced when you use a display manager, right? Do you see any other differences between the logs? |
Yes, running under xdm (lightdm), I don't see that at all. I confirm that "xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)" is persistent in the Xorg.0.log files (old and new) in .local/share/xorg/.
For comparison, here is the same running under xdm (lightdm):
| Code: |
ps axf -o pid,tty,args
...
24658 tty1 /bin/login --
24708 tty1 \_ -bash
28232 tty2 /sbin/agetty 38400 tty2 linux
28574 ? /usr/sbin/lightdm
28587 tty7 \_ /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nol
28636 ? \_ lightdm --session-child 13 20
28672 ? \_ /usr/bin/openbox --startup /usr/libexec/openbox-autostart
28680 ? /usr/bin/dbus-launch --exit-with-session /usr/bin/openbox-session
28681 ? /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-addres
28693 ? lxpanel
28796 ? \_ /usr/lib64/thunderbird/thunderbird --name thunderbird
28942 ? | \_ /usr/lib64/firefox/firefox --name firefox http://forums.g
29021 ? | \_ /usr/lib64/firefox/firefox -contentproc -childID 1 -i
29087 ? | \_ /usr/lib64/firefox/firefox -contentproc -childID 2 -i
29139 ? | \_ /usr/lib64/firefox/firefox -contentproc -childID 3 -i
29205 ? | \_ /usr/lib64/firefox/firefox -contentproc -childID 4 -i
29731 ? \_ sakura
29736 pts/0 \_ /bin/bash
31957 pts/0 \_ ps axf -o pid,tty,args
28694 ? pcmanfm --desktop
28695 ? xscreensaver
28701 ? /usr/libexec/at-spi-bus-launcher
28707 ? \_ /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi
28702 ? conky -d
28713 ? /usr/libexec/gvfsd
28757 ? \_ /usr/libexec/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_sp
28734 ? /usr/libexec/menu-cache/menu-cached /run/user/1000/menu-cached-:0
28751 ? /usr/libexec/gvfs-udisks2-volume-monitor
28765 ? /usr/libexec/at-spi2-registryd --use-gnome-session
28937 ? /usr/libexec/notification-daemon
|
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Thu Feb 04, 2021 11:15 pm Post subject: |
|
|
| figueroa wrote: | | Code: | 24658 tty1 /bin/login --
24708 tty1 \_ -bash
27907 tty1 \_ /bin/sh /usr/bin/startx
27924 tty1 \_ xinit /home/figueroa/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.Qkv4hffe5V
27925 tty1 \_ /usr/bin/X -nolisten tcp -keeptty :0 -auth /tmp/serverauth.Qkv4hffe5V vt1
27934 tty1 \_ sh /home/figueroa/.xinitrc
27940 tty1 \_ /usr/bin/openbox --startup /usr/libexec/openbox-autostart OPENBOX
25993 tty2 /bin/login --
28048 tty2 \_ -bash
28087 tty2 \_ ps axf -o pid,tty,args
27943 tty1 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/openbox-session
27944 ? /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
27956 tty1 lxpanel
27957 tty1 pcmanfm --desktop
27958 tty1 xscreensaver
27959 tty1 conky -d
27966 ? /usr/libexec/gvfsd |
|
So everything is actually running. Xorg, Openbox, lxpanel, PCManFM, etc. You just can't see anything drawn on the screen.
| figueroa wrote: | | I confirm that "xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)" is persistent in the Xorg.0.log files (old and new) in .local/share/xorg/. |
That might be a harmless error in this case. It looks like it's actually caused by the vesa driver —which is later unloaded because it is not used—.
| Code: | [ 614.416] (==) Matched vesa as autoconfigured driver 4
[...]
[ 614.416] (II) LoadModule: "vesa"
[ 614.416] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 614.416] (II) Module vesa: vendor="X.Org Foundation"
[ 614.416] compiled for 1.20.10, module version = 2.5.0
[ 614.416] Module class: X.Org Video Driver
[ 614.416] ABI class: X.Org Video Driver, version 24.1
[...]
[ 614.418] (II) VESA: driver for VESA chipsets: vesa
[...]
[ 614.562] (II) UnloadModule: "vesa"
[ 614.562] (II) Unloading vesa |
You probably have it installed as a consequence of having vesa in VIDEO_CARDS. I get that message too if the driver is installed, but everything still works fine. If you set VIDEO_CARDS so that x11-drivers/xf86-video-vesa gets depcleaned, the error should go away.
So I'm not sure what isn't working, sorry. Did you find any other difference between the startx Xorg.0.log and the LightDM Xorg.0.log? Does the "almost identical but older x86" box that does not use a display manager and runs startx without issue also use the radeon driver? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Fri Feb 05, 2021 2:57 am Post subject: |
|
|
| GDH-gentoo wrote: | You probably have it installed as a consequence of having vesa in VIDEO_CARDS. I get that message too if the driver is installed, but everything still works fine. If you set VIDEO_CARDS so that x11-drivers/xf86-video-vesa gets depcleaned, the error should go away.
So I'm not sure what isn't working, sorry. Did you find any other difference between the startx Xorg.0.log and the LightDM Xorg.0.log? Does the "almost identical but older x86" box that does not use a display manager and runs startx without issue also use the radeon driver? |
Yes, I have forever kept vesa in my setup as a fall-back. At your suggestion, I removed vesa from VIDEO_CARDS, rebuilt xorg-server, depcleaned away xf86-video-vesa.
The IOPL error goes away, but startx still gives me a gray screen with a mouse pointer on TTY1 and a black screen with a blinking cursor in the upper left hand corner on TTY7.
I'm scandalized and my reputation is shot!
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Fri Feb 05, 2021 4:38 am Post subject: |
|
|
| GDH-gentoo wrote: | | Does the "almost identical but older x86" box that does not use a display manager and runs startx without issue also use the radeon driver? |
Another part of your questions.
The "older x86" box was my primary desktop until a couple of years ago. When I picked up a discarded better system, I installed Gentoo just like the old box except made it amd64. The old box is now relegated to server duties.
I used lightdm on the older box until a couple of months ago since no user is actually using it. Taking xdm out of default was uneventful and startx always works with xfce, lxde, and openbox which is my new go-to desktop. It is also Radeon, but with a much older built-in video card.
| Code: | 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GA-MA78GM-S2H Motherboard
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at ee00 [size=256]
Memory at fdfe0000 (32-bit, non-prefetchable) [size=64K]
Memory at fde00000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
|
The make.conf also has vesa and even still has nouveau from a video card that I removed because it's cooling fan died. It also throws the IOPL for I/O error, just isn't a problem.
~/.xinitrc are also identical.
Most of my Linux life, which is long, I've used startx. I started using lightdm a couple of years ago after configuring systems for others. It's kind of funny that I'm currently stuck using the display manager.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Fri Feb 05, 2021 1:13 pm Post subject: |
|
|
| figueroa wrote: | | It's kind of funny that I'm currently stuck using the display manager. |
LightDM spawns Xorg as root (you can check with ps -p <PID of X> -o pid,euser,args); if that's what is working around the problem here, emerge --onseshot x11-base/xorg-server with USE="-elogind suid" should also make startx work. |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Fri Feb 05, 2021 1:22 pm Post subject: |
|
|
| figueroa wrote: | | Code: | $ cat .xinitrc
...
export XDG_MENU_PREFI=lxde- |
|
Is this typo actually in the file? (Should be XDG_MENU_PREFIX) |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6098
Location: Dallas area
|
| Posted: Fri Feb 05, 2021 2:10 pm Post subject: |
|
|
startx by itself (no parms) will first try and X on tty7, if that's used it goes to tty8, etc.
IF you are running non-root X and you're using startx then try
startx -- vt1 -keeptty (assuming you're on console #1 in the first place)
Otherwise you get weird results, as you found out.
Note: One can also play with permissions on tty7 and tty group.
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1530
Location: South America
|
| Posted: Fri Feb 05, 2021 2:42 pm Post subject: |
|
|
| Anon-E-moose wrote: | startx by itself (no parms) will first try and X on tty7, if that's used it goes to tty8, etc.
IF you are running non-root X and you're using startx then try
startx -- vt1 -keeptty (assuming you're on console #1 in the first place) |
This is already taken care of by Gentoo's /etc/X11/xinit/xserverrc, as shown by figueroa's ps output.
| figueroa wrote: | | Code: | 27924 tty1 \_ xinit /home/figueroa/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.Qkv4hffe5V
27925 tty1 \_ /usr/bin/X -nolisten tcp -keeptty :0 -auth /tmp/serverauth.Qkv4hffe5V vt1 |
|
|
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6098
Location: Dallas area
|
| Posted: Fri Feb 05, 2021 3:07 pm Post subject: |
|
|
The preferred method is to pass it to startx, I think part of the reason is that startx tries to figure out the proper vt to use and makes decisions on that, including what to pass to xinit. (the ps listing chops off at vt1, so who knows what parms if any are later, I'm thinking it's probably also passing vt7, so some things are looking at tty1 and others at tty7.
Just try what I recommend and see if it works. If not no harm done, if it works then problem solved.
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Fri Feb 05, 2021 3:49 pm Post subject: |
|
|
| GDH-gentoo wrote: | | figueroa wrote: | | Code: | $ cat .xinitrc
...
export XDG_MENU_PREFI=lxde- |
|
Is this typo actually in the file? (Should be XDG_MENU_PREFIX) |
I've often wondered about that, but openbox and openbox-menu work fine. Searching on the web shows ALL examples with PREFIX, so I'm changing it.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Fri Feb 05, 2021 3:57 pm Post subject: |
|
|
| GDH-gentoo wrote: | | figueroa wrote: | | It's kind of funny that I'm currently stuck using the display manager. |
LightDM spawns Xorg as root (you can check with ps -p <PID of X> -o pid,euser,args); if that's what is working around the problem here, emerge --onseshot x11-base/xorg-server with USE="-elogind suid" should also make startx work. |
Tried that. Didn't work. Also tried startx first stopping elogind and still didn't work the same as before.
Started xdm and I'm back in the desktop. elogind started with xdm or one of the spawned processes.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2964
Location: Edge of marsh USA
|
| Posted: Fri Feb 05, 2021 4:02 pm Post subject: |
|
|
Thanks, Anon-E-moose
| Anon-E-moose wrote: | startx by itself (no parms) will first try and X on tty7, if that's used it goes to tty8, etc.
IF you are running non-root X and you're using startx then try
startx -- vt1 -keeptty (assuming you're on console #1 in the first place)
|
No luck. I keep getting the same results with startx.
Last night I even did a world update with -N and rebuilt 130 packages hoping one of them might make a difference. Nope. Same results. I'm counting my blessings that xdm/lightdm works as solid as ever.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
