You are not logged in.
Well, since the driver has been dropped, my kernel updated and it is not working anymore
I'm trying to shift to nouveau but it keeps failing and I can't figure out why.
I configured my system so it launches kodi as a service upon start so you can watch your movies/tv shows.
Uninstalled the driver and carefully followed the nouveau wiki page to try and see if i can make it work again, without success....
This is the log generated under /home/kodi/.local/share/xorg/Xorg.0.log
Which is what I can see a reference to on display upon failure.
If you guys need any more info, feel free to suggest.
EDIT: I also tried to run x in verbose mode:
Last edited by Xi0N (2019-06-06 20:43:24)
Offline
I'm guessing everything is actually fine about Xorg and nouveau with regards to your "startx" experiment, it's just your .xinitrc script being broken and not starting anything. The Xorg server seems to manage setting up everything about the card and monitor fine, but then xinit quits and the Xorg server shuts down again.
There are these messages here towards the end of your startx log:
/etc/X11/xinit/xinitrc: line 55: exec: xterm: not found
/etc/X11/xinit/xinitrc: line 54: xterm: command not found
I don't know about Kodi, so no idea about what's going wrong there.
Last edited by Ropid (2019-06-06 20:55:08)
Offline
Installed xterm and still suffering the same issues
Offline
Ropid is right:
[ 57.934] (II) NOUVEAU(0): NVLeaveVT is called.
[ 58.035] (II) Server terminated successfully (0). Closing log file.
Please post your xinitrc.
Offline
I also had the same problem, the solution was to install the driver xf86-video-vesa and remove the file xorg.conf, nouveau always freezes my computer in the boot
Offline
Ropid is right:
[ 57.934] (II) NOUVEAU(0): NVLeaveVT is called. [ 58.035] (II) Server terminated successfully (0). Closing log file.
Please post your xinitrc.
Actually, there's no xinitrc
I use this package:
https://aur.archlinux.org/packages/kodi … e-service/
Which just launches kodi
@WilliCRM -- that package is installed, no luck still
I do, however have a kodi fail log here: https://pastebin.com/UZCyzrcW
Which complains:
2019-06-06 23:57:49.064 T:140446927987904 ERROR: failed to get egl display
2019-06-06 23:57:49.095 T:140446927987904 NOTICE: Using visual 0x21
2019-06-06 23:57:49.097 T:140446927987904 ERROR: CWinSystemX11::XErrorHandler: BadValue (integer parameter out of range for operation), type:0, serial:67, error_code:2, request_code:152 minor_code:3
2019-06-06 23:57:49.097 T:140446927987904 ERROR: GLX Error: Could not create context
glxinfo | grep OpenGL
Error: unable to open display
I went ahead and deleted /etc/X11 and /usr/share/X11 to make sure there's no nvidia leftovers - no luck
Last edited by Xi0N (2019-06-07 04:11:09)
Offline
@WilliCRM, no that simply means you're either still loading the nvidia kernel module or booting nomodeset. Please fix that and loose the vesa package.
deleted /etc/X11 and /usr/share/X11
D'oh. This will break several packages.
pacman -Qkk
Once you fixed that, cut out the kodi thing. Just try to "startx xterm", see whether you get an X11 server and chekc glxinfo there and maybe also starting kodi directly.
Is the fail log from after installing the vesa driver and/or the random delete?
Offline
@WilliCRM, no that simply means you're either still loading the nvidia kernel module or booting nomodeset. Please fix that and loose the vesa package.
deleted /etc/X11 and /usr/share/X11
D'oh. This will break several packages.
pacman -Qkk
Once you fixed that, cut out the kodi thing. Just try to "startx xterm", see whether you get an X11 server and chekc glxinfo there and maybe also starting kodi directly.
Is the fail log from after installing the vesa driver and/or the random delete?
Deleting X11 folder was not a clever move, I panicked... I'm not a smart man.....
this is the output of pacman -Qkk:
Did a redirect to file for that command, yet got this output on my console:
warning: java-runtime-common: /usr/lib/jvm/default (Symlink path mismatch)
warning: java-runtime-common: /usr/lib/jvm/default (Modification time mismatch)
warning: java-runtime-common: /usr/lib/jvm/default-runtime (Symlink path mismatch)
warning: java-runtime-common: /usr/lib/jvm/default-runtime (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.alias (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.alias (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.alias.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.alias.bin (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.builtin.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.dep (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.dep (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.dep.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.dep.bin (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.devname (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.devname (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.softdep (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.symbols (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.symbols (Size mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.symbols.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.1.7-arch1-1-ARCH/modules.symbols.bin (Size mismatch)
warning: netdata: /usr/share/netdata/web (UID mismatch)
warning: netdata: /usr/share/netdata/web (GID mismatch)
warning: netdata: /usr/share/netdata/web/.well-known (UID mismatch)
warning: netdata: /usr/share/netdata/web/.well-known (GID mismatch)
warning: netdata: /usr/share/netdata/web/.well-known/dnt (UID mismatch)
warning: netdata: /usr/share/netdata/web/.well-known/dnt (GID mismatch)
warning: netdata: /usr/share/netdata/web/css (UID mismatch)
warning: netdata: /usr/share/netdata/web/css (GID mismatch)
warning: netdata: /usr/share/netdata/web/fonts (UID mismatch)
warning: netdata: /usr/share/netdata/web/fonts (GID mismatch)
warning: netdata: /usr/share/netdata/web/images (UID mismatch)
warning: netdata: /usr/share/netdata/web/images (GID mismatch)
warning: netdata: /usr/share/netdata/web/lib (UID mismatch)
warning: netdata: /usr/share/netdata/web/lib (GID mismatch)
warning: nfs-utils: /var/lib/nfs/etab (Modification time mismatch)
warning: nfs-utils: /var/lib/nfs/etab (Size mismatch)
warning: nfs-utils: /var/lib/nfs/state (UID mismatch)
warning: nfs-utils: /var/lib/nfs/state (Permissions mismatch)
warning: nfs-utils: /var/lib/nfs/state (Modification time mismatch)
warning: nfs-utils: /var/lib/nfs/state (Size mismatch)
warning: nvidia-340xx-utils: /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf (No such file or directory)
warning: perl-encode-detect: /home/john (UID mismatch)
warning: perl-encode-detect: /home/john (GID mismatch)
warning: perl-encode-detect: /home/john (Permissions mismatch)
warning: perl-encode-detect: /home/john/perl5 (UID mismatch)
warning: perl-encode-detect: /home/john/perl5 (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5 (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5 (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Encode (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Encode (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Encode/Detect (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Encode/Detect (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/man (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/man (GID mismatch)
warning: perl-encode-detect: /home/john/perl5/man/man3 (UID mismatch)
warning: perl-encode-detect: /home/john/perl5/man/man3 (GID mismatch)
warning: samba: /var/lib/samba/private (Permissions mismatch)
warning: systemd: /var/log/journal (GID mismatch)
Bear in mind, this system is ancient and has withstand lots of changes, upgrades and so on and so forth over time: I'm talking maybe 3 or 4 years IIRC....
I'm at the office now (not in front of the monitor) and will try the other tests you suggested once I have some spare time after work.
I have a new ssd for the system that I was planning on installing once I upgrade it (ryzen3 will replace my i7 and the i7 would come to this system, just for video playback) but it had to break 1 month before 7/7... my luck.
I also have snapper and btrfs functional, another solution I'm thinking, even before the "nuclear" solution of reinstalling, would be to revert to a snapshot previous to the nvidia340xx package getting deleted, downgrade linux, zfs, mkinitcpio'ing and try to hold the fort with the result for a month.
Offline
How is eg.
xkeyboard-config: 456 total files, 0 altered files
…
xf86-input-evdev: 21 total files, 0 altered files
…
xf86-input-libinput: 21 total files, 0 altered files
…
xorg-xinit: 17 total files, 0 altered files
possible if you deleted /usr/share/X11 and /etc/X11 ?
Offline
You still have an nvidia package installed, it's showing up in the output of pacman you shared:
nvidia-340xx-utils
Last edited by Ropid (2019-06-07 12:03:39)
Offline
You still have an nvidia package installed, it's showing up in the output of pacman you shared:
nvidia-340xx-utils
Yeah, but it stopped working with current kernel AFAIK
Offline
Yes, and the implication is that if your intention is to swap to nouveau, you should remove that package.
Last edited by V1del (2019-06-07 12:26:59)
Offline
Once you fixed that, cut out the kodi thing. Just try to "startx xterm", see whether you get an X11 server and chekc glxinfo there and maybe also starting kodi directly.
Is the fail log from after installing the vesa driver and/or the random delete?
This is the result: https://pastebin.com/T0UEG0Hi
Same visual effect: the screen flickers three times, and then fails.
I installed plasma and ran: startx with "exec startkde" in my .xinitrc file and i could see the kde desktop: No bars, no nothing else: Just the cursor and a menu on the top right (i think its the actions menu) and that's all
The error mesasge displayed a "Could not resolve keysym Xf86MonBrightnessCycle: Internal error" message....
Offline
Ropid wrote:You still have an nvidia package installed, it's showing up in the output of pacman you shared:
nvidia-340xx-utils
Yeah, but it stopped working with current kernel AFAIK
Did you remove it now before testing further? You also have to reboot, I think.
The bad thing that package does is, it contains a file that blacklists the nouveau kernel module and prevents it from loading. It will do this even if the nvidia module is missing and not loading.
Offline
Yes, and the implication is that if your intention is to swap to nouveau, you should remove that package.
OH MY GOD.... that did it.. at least it does start.. now lets see how iot does perform..
Can't believe it... thanks guys!!
(Will update if I run into any more trouble)
Offline