Michael wrote: > On Saturday, 22 June 2024 19:13:42 BST Dale wrote: >> Dale wrote: >>> Michael wrote: > >> root@Gentoo-1 ~ # xrandr --verbose >> Can't open display >> root@Gentoo-1 ~ # >> >> >> That's after I started display-manager but this time, it did nothing. >> The screen stayed on a console. I did move the cable to another port >> before booting up. > The xerver is not running. >
How do I start it? I did a /etc/init.d/ <tab twice> and I see display-manager and xdm. I been using display-manager. I have sddm set for display-manager. Like this. root@Gentoo-1 ~ # cat /etc/conf.d/xdm # We always try and start X on a static VT. The various DMs normally default # to using VT7. If you wish to use the xdm init script, then you should ensure # that the VT checked is the same VT your DM wants to use. We do this check to # ensure that you haven't accidentally configured something to run on the VT # in your /etc/inittab file so that you don't get a dead keyboard. CHECKVT=7 # What display manager do you use ? [ xdm | gdm | sddm | gpe | lightdm | entrance ] # NOTE: If this is set in /etc/rc.conf, that setting will override this one. DISPLAYMANAGER="sddm" root@Gentoo-1 ~ # >> This is the other info except nothing xorg there, just wayland. See >> below for more on that. >> >> >> root@Gentoo-1 ~ # cat /home/dale/.local/share/sddm/wayland-session.log > I thought you said you were having a problem starting a X session, not > starting a Wayland session. What desktop session are you selecting in your > SDDM? > > [snip ...] That made me think. After a few attempts, I got the sddm login screen to come up. I checked and it was logging me into a KDE wayland session, as a default. I changed it to x11. The first time, it logged in but nothing plasma showed up. No panel at the bottom and a black screen for the background. The only thing there was gkrellm. I leave it there so I can tell if it is working, to some degree at least. Otherwise, it is just a black screen. >> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Successfully >> activated service 'org.freedesktop.portal.Documents' >> fuse: device not found, try 'modprobe fuse' first >> error: fuse init failed: Can't mount path /run/user/1000/doc > It can't find the path /run/user/1000/ for your user to be able to set up > desktop environment variables, user authentication and other desktop related > files. Is your fs mounted fully? > > [snip ...] As far as I know. Here's some info. root@Gentoo-1 ~ # mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=10240k,nr_inodes=8218422,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,mode=755) /dev/nvme0n1p2 on / type ext4 (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) /dev/nvme0n1p3 on /var type ext4 (rw,relatime) tmpfs on /var/tmp/portage type tmpfs (rw,noatime,size=41943040k) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=6576248k,nr_inodes=1644062,mode=700) root@Gentoo-1 ~ # >> No backend specified, automatically choosing drm >> kwin_wayland_drm: No suitable DRM devices have been found > [snip ...] > > It should have found and listed your video card here ^^^^ and its drivers. > > Can it not detect your card at all? :-/ > I have no idea. The lspci command shows it. 0a:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P1000] (rev a1) >> The Wayland connection broke. Did the Wayland compositor die? >> The Wayland connection broke. Did the Wayland compositor die? >> The Wayland connection broke. Did the Wayland compositor die? >> qt.qpa.wayland: Creating a fake screen in order for Qt not to crash >> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activated service >> 'org.freedesktop.impl.portal.desktop.kde' failed: Process >> org.freedesktop.impl.portal.desktop.kde exited with status 1 >> >> (/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **: >> 03:20:14.512: Failed to create settings proxy: Error calling >> StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Process >> org.freedesktop.impl.portal.desktop.kde exited with status 1 >> >> (/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **: >> 03:20:14.512: No skeleton to export >> kdeinit5: Communication error with launcher. Exiting! >> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating >> service name='org.freedesktop.impl.portal.desktop.kde' requested by >> ':1.5' (uid=1000 pid=2787 comm="/usr/libexec/xdg-desktop-portal" >> label="kernel") >> Error: could not determine $DISPLAY. >> Error: Can not contact kdeinit5! >> org.kde.startup: "kdeinit5_shutdown" () exited with code 255 >> startplasma-wayland: Shutting down... >> startplasmacompositor: Shutting down... >> startplasmacompositor: Done. >> root@Gentoo-1 ~ # >> >> >> Since it complains about DRM. Here's this. >> >> >> root@Gentoo-1 ~ # lsmod >> Module Size Used by >> nvidia_drm 102400 0 >> nvidia_modeset 1544192 1 nvidia_drm >> nvidia 59744256 1 nvidia_modeset >> root@Gentoo-1 ~ # > I have no experience with Nvidia to know what modules are needed. That module list is the same as my main rig. I've seen that list many times. That is normal. The DRM module is there tho. If that is what it is complaining about. Could be some other DRM. > >> What's that about fuse??? > It seems it can't find the fs containing the /run directory and it tries to > launch fuse to probe & mount block devices. No idea about fuse. I thought that was a driver for windoze ntfs stuff. The mount does show /run mounted twice above tho. > >> To add to this, this is a new video card. It's a P1000, Nvidia of >> course. Could it be a bad card that works to a point but then dies? I >> got a older PCIe V2 card I'm going to try. That was the card that was >> in during the early stages. The P1000 was the one that got hung up by >> the post office and arrived days late. I'm going to test the other >> slower card shortly, got to remember to downgrade nvidia-drivers to >> tho. ;-) > You may want to walk through the Gentoo wiki for Nvidia to make sure you have > all necessary drivers installed. Then you may be more productive if you try > to solve either Xorg, or Wayland desktop session problems separately. > > If the problem is with your hardware, neither desktop session type will work. I think the problem may be deeper. I feel that when one is solved, everything is going to work. I think I missed something really basic, maybe even a package that KDE and such doesn't pull in directly but the GUI needs. > >> On the above wayland info, I recall some having issues with wayland. I >> tried to disable wayland by putting -wayland in make.conf and >> rebuilding. Since it wanted to rebuild a lot, I removed everything GUI >> related from the world file and then ran --depclean to clean house. >> Then I emerge everything I removed from the world file again, while I >> napped. The output above could be old but may still provide a clue. If >> I could figure out how to go back to KDE V5 instead of the new V6, I >> would, to eliminate a wayland issue if nothing else. I removed >> everything from /etc/portage/package.keyword file but I think KDE V6 is >> stable now. The odd part, right now, even sddm isn't coming up. > kde-plasma/plasma-meta-6.1.0 is still in testing - I sync'ed earlier today: > > ~ $ eshowkw kde-plasma/plasma-meta > Keywords for kde-plasma/plasma-meta: > | | u | > | a a p s l r a | n | > | m r h p p i o i s l m m | e u s | r > | d a m p p c a x a o s 3 p 6 i | a s l | e > | 6 r 6 p p 6 r 8 6 n c 9 h 8 p | p e o | p > | 4 m 4 a c 4 c 6 4 g v 0 a k s | i d t | o > --------------+-------------------------------+-------+------- > [I]5.27.11-r1 | + ~ + o o ~ o + o ~ ~ o o o o | 8 o 5 | gentoo > --------------+-------------------------------+-------+------- > 6.1.0 | ~ o o o o o o o o o o o o o o | 8 o 6 | gentoo > I see some qt stuff that is version 6. KDE has gotten pretty confusing. It depends on qt so much that KDE depends heavily on versions matching up somehow. Is there a guide about installing the GUI parts, including KDE? I found a Xorg guide. I'm good all the way down to startx. At that point, nothing. I installed xterm just so startx should show some windows on the screen. Nothing. Monitor goes to sleep. When I did a install for the NAS box, I didn't have this type of trouble. I'm pretty sure I did this new rig the same way except for the EFI and NVME drive stuff. The NAS box works fine. I haven't used the GUI much but I did leave it on a while on a few occasions. Resolution was OK too. This is why I think I missed something, maybe something small, that makes this work. I just can't figure out what it is. I'm hoping a second pair of eyes will see something and know what I missed. Given I did the partitions wrong when installing, EFI and /boot mix up, I'm thinking about saving a few key files, kernel and config, world and maybe a couple other things and just starting over. Maybe I won't miss whatever it is the second time. LOL OK. I been going through several guides on the wiki since I typed in the above. I checked all sorts of settings and also checked some kernel config options that I don't recall checking before. With my memory, it doesn't mean I didn't do them tho. Still, I made some kernel config changes. I can't think of anything else as far as guides go to look at. When I rebooted into the new kernel, KDE came up. It ran for a little bit with the plasma running, panel thingy at the bottom and a background image. I did manage to make sure all power off options were disabled. When the monitor goes off, it isn't due to power saving settings. About that time, the monitor screen went blank and the monitor went to sleep, due to no signal. It has done this on two video cards now. If there are no more ideas, I may go the starting over route. Maybe whatever I missed will get done the second time. Plus I get to fix my drive partition boo boo. ;-) Dale :-) :-)
