Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
No X with kernels 4.19.0 and 4.19.1 -- RESOLVED
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Fred Krogh
Veteran
Veteran


Joined: 07 Feb 2005
Posts: 1009
Location: Tujunga, CA

PostPosted: Wed Nov 07, 2018 7:08 pm    Post subject: No X with kernels 4.19.0 and 4.19.1 -- RESOLVED Reply with quote

Kernel 4.18.10 is working just fine, but I'm not able to get X working with 4.19. I've looked at a lot of places where somewhat similar problems are discussed, but have found nothing that works for me.
Some things that may help in pointing to the problem. In ~/.xsessions.errors
Code:
** (xfce4-session:3336): WARNING **: 07:15:37.761: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: 07:15:37.825: couldn't access control socket: /var/run/user/1002/keyring/control: No such file or directory
At one time I was trying to get rid of pam so this may be part of my problem. (I'm on a single user work station.)
In /var/log/Xorg.0.log I'm getting this error several times
Code:
[    27.882] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    27.882] (EE) NVIDIA:     system's kernel log for additional error messages and
[    27.882] (EE) NVIDIA:     consult the NVIDIA README for details.

I see nothing in dmesg that suggests anything about a problem. Is there some place else I should be looking or something I could try? Many Thanks,
Fred

[Moderator edit: changed [quote] tags to [code] tags to preserve output layout. -Hu]


Last edited by Fred Krogh on Wed Nov 14, 2018 11:22 pm; edited 1 time in total
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 6935
Location: almost Mile High in the USA

PostPosted: Thu Nov 08, 2018 12:05 am    Post subject: Reply with quote

If you change kernel versions, you must also rebuild the dynamically loadable kernel modules, of which nvidia-drivers is one.

Make sure your

# eselect kernel list

is pointing to the correct kernel source in /usr/src, and re-emerge nvidia-drivers.

However one problem that comes up frequently is that nvidia-drivers tends to lag latest and greatest kernels, and cannot be recompiled for the newer kernels without surgery to the code. It can be hard to fix due to the binary distribution nature of the driver. As I do not own an nvidia card that requires the use nvidia-drivers, I can't comment about this.

As a few asides:

1 - The error message you posted is a side effect of, or unrelated to, the real problem - not the direct cause.
2 - why do you want to get rid of pam, as long as all components use pam it seems like a good thing ensuring all authentication goes through the same codebase instead of DIY which can cause race conditions if it even applies to your own box... If you don't want authentication I'd look into other methods, you could simply tell pam not to require any credentials when asked. This is still a bad idea IMHO, but personally think pam is a good thing.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
Fred Krogh
Veteran
Veteran


Joined: 07 Feb 2005
Posts: 1009
Location: Tujunga, CA

PostPosted: Thu Nov 08, 2018 12:16 am    Post subject: Reply with quote

I compile the kernel with the following script
Code:
#!/bin/bash
mount /dev/sda1 /boot
if [[ $# == 0 ]]; then
   echo "Argument is appended to end of \"/boot/kernel-4.\""
   echo "Current kernels are"
   ls -l /boot/kern*
else
  make prepare
  make
  make modules_install
  emerge @module-rebuild
  \cp -fv arch/x86_64/boot/bzImage /boot/kernel-4.$1
  \cp -fv .config /boot/config-4.$1
  \cp -fv System.map /boot/
  \cp -fv System.map /
  grub-mkconfig -o /boot/grub/grub.cfg
fi
Which means I never forget the module updates. Pam was asking for a password in a place where it just seemed a bother.
I have frequently picked up a patch for an nvidia-driver, but I haven't bothered to do so for the latest one.
I'm hoping someone can point to where I should be looking for the error message that would help track down the problem.
Thanks for the input.
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 6935
Location: almost Mile High in the USA

PostPosted: Thu Nov 08, 2018 1:25 am    Post subject: Reply with quote

The error messages printed aren't particularly helpful other than possibly pointing at a module version mismatch.

If there's nothing in dmesg, did the module even load? (lsmod after seeing the error?)
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
Ralphred
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2013
Posts: 78

PostPosted: Thu Nov 08, 2018 5:22 am    Post subject: Reply with quote

This may be completely unrelated, but in switching between 4.18 and 4.19 my gfx card changed address on the pci bus.
Back to top
View user's profile Send private message
Fred Krogh
Veteran
Veteran


Joined: 07 Feb 2005
Posts: 1009
Location: Tujunga, CA

PostPosted: Fri Nov 09, 2018 11:20 pm    Post subject: Reply with quote

Sorry, I've just been able to get back to this. The table below summarizes what I have found. I'm hoping this suggest something to somebody. I'm running xorg-server-1.20.3. Thanks,
Code:
                                 Kernel 19.1                           Kernel 18.16
nvidia-drivers-410.66    No nvidia-modules loaded    nvidia-modules: nvidia_modeset nvidia nvidia_drm  works
nvidia-drivers-410.73    No nficia-modules loaded    nvidia-modules: nvidia nvidia drm                 fails
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41719
Location: 56N 3W

PostPosted: Sat Nov 10, 2018 10:20 am    Post subject: Reply with quote

Fred Krogh,

Stand by to wait.

The evil binary blob nvidia-drivers doesn't build on 4.19.x yet.
nvidia need to fix it.

I understand that there may be some user patches around the web.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Fred Krogh
Veteran
Veteran


Joined: 07 Feb 2005
Posts: 1009
Location: Tujunga, CA

PostPosted: Sat Nov 10, 2018 6:38 pm    Post subject: Reply with quote

I'm not sure what to believe, but http://rglinuxtech.com/?p=2415 says the latest nvidia-driver work with kernel 4.19.x. If this is the case something else must be causing my problem.
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5487
Location: Removed by Neddy

PostPosted: Sat Nov 10, 2018 6:42 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Fred Krogh,

Stand by to wait.

The evil binary blob nvidia-drivers doesn't build on 4.19.x yet.
nvidia need to fix it.

I understand that there may be some user patches around the web.
That is not true

Quote:
uname -a && grep nvidia /proc/modules

Linux fluidmotion 4.19.0-gentoo #1 SMP PREEMPT Sat Oct 27 16:20:11 BST 2018 x86_64 AMD Ryzen 5 1600 Six-Core Processor AuthenticAMD GNU/Linux

nvidia_drm 40960 6 - Live 0x0000000000000000 (PO)
nvidia_modeset 1003520 16 nvidia_drm, Live 0x0000000000000000 (PO)
nvidia 16048128 745 nvidia_modeset, Live 0x0000000000000000 (PO)


It however does now need CONFIG_PM set for it to build, which is a present kernel option. Now if people do not like that set or have an opinion that they shouldn't have to that is different... but x11-drivers/nvidia-drivers-410.73 will build against sys-kernel/gentoo-sources-4.19.x without some portage patchfile.

Code:
 grep CONFIG_PM config-4.18.8-gentoo
# CONFIG_PM is not set
# CONFIG_PMIC_OPREGION is not set
# CONFIG_PMBUS is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_PMIC_DA903X is not set
CONFIG_PMC_ATOM=y
# CONFIG_PM_DEVFREQ is not set

fluidmotion /boot # grep CONFIG_PM config-4.19.0-gentoo
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_CLK=y
# CONFIG_PMIC_OPREGION is not set
# CONFIG_PMBUS is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_PMIC_DA903X is not set
CONFIG_PMC_ATOM=y
# CONFIG_PM_DEVFREQ is not set

_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
Fred Krogh
Veteran
Veteran


Joined: 07 Feb 2005
Posts: 1009
Location: Tujunga, CA

PostPosted: Wed Nov 14, 2018 11:22 pm    Post subject: Reply with quote

I've just installed kernel 4.19.2, and X is working. I'll just call this mystery resolved.

Just realized it had to do with using genkernel on a aborted attempt to use systemd. Evidently that took priority, and I just happened to notice that it was always trying to use that kernel. Once I deleted that all works as I expected.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
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