Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Newbie on the way to Gentoo... Hi!
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Mon Apr 11, 2016 1:07 pm    Post subject: Newbie on the way to Gentoo... Hi! Reply with quote

Hi,

This post is to thank the team, say hello, and tell my newbie story...

I decided to switch to Gentoo as main system at home. :D
No boot attempt yet.
I started installation 2 days ago, that's maybe 6-7 hours of work so far, not enough to complain since it's a new process for me.

Also some of my requirements add a little bit of a challenge for a newbie:
- EFI boot
- mount by UUID
- aufs support
- systemd
- metalog
- KDE plasma
- fr locale
- NVidia proprietary drivers (along with Intel integrated graphics)
- dual seat (I'll see that point later)
(and I'll stick to portage for a while, I'm not sure to switch for paludis)

Installation is done from my current Linux Mint 17, on a new drive, but it seems I'll have to boot the System Rescue CD in EFI to install Grub2 with the right variables initialized, no big deal.

Since I started I keep a log of all my commands, problems and docs I read.
Maybe I'll turn that into something useful for next newbie with similar requirements.

The good news: 8)
- emerge is quite exciting, chaining so much compilations is like magic
- I learned a few things that could help me fix the random Linux Mint freezes: I'll rebuild its kernel with the Gentoo advice regarding NVidia driver requirements.

The still on work issues: :?
- finalizing the EFI boot setup (got a clue for this one)
- NVidia drivers (emerge X server leads to strange ABI x86 messages, still searching)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Mon Apr 11, 2016 6:35 pm    Post subject: Reply with quote

blugendoo,

Welcome to Gentoo.

You are trying to eat a whole elephant at one sitting. Don't do that. The one plateful at a time approach works best.
Gentoo is the same. Take a handbook install, customise the filesystem layout if you wish then test it.
Once it works, add things to it. You can always back out your additions when it breaks.
This minimises the problem space you need to search when (not if) it fails.

Switch to systemd after the default openrc works. Then if it used to boot but doesn't after the switch, you know systemd is the issue.

Code:
nVidia proprietary drivers (along with Intel integrated graphics)
Does that mean Optimus or really two completely separate graphics systems?
It matters to your install. If you do an Intel only install to start, you can add the nVidia driver later.
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 9:00 am    Post subject: Reply with quote

Hi NeddySeagoon, thanks for such wise advice. I should have done that.

Well, maybe I'll carry on a little bit just to make it boot. Then, if there's too many problems eating that elephant, I'll start over with a very standard setup and on-board Intel graphics by default.

My hardware: integrated Intel graphic chip, that I do not use yet, and a separate NVidia GeForce 970GTX on PCI express slot as main graphic card. The Intel chip will be used later for another seat (with another keyboard and mouse).

I had one hour more to take care of my Gentoo system:

EFI boot on System Rescue CD is ok, chroot to install Grub with EFI variables is ok now, as expected. 8)

Grub starts at pure EFI boot, it tells me "loading kernel xxxxxxxxxxxx" and "loading initial ramdisk xxxxxxxxxxx", and nothing else happen (blinking cursor). :(
I guess that using an USB adapter for my new system disk wasn't a good idea. A the moment it was simpler for me to try Gentoo, but this could add some problems. :oops:

So I plugged the drive on internal sata, motherboard setup sees it but I can't make it boot Grub anymore. :roll:
I'll try a Grub re-install from Rescue CD as soon as get back to this Gentoo install.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Tue Apr 12, 2016 4:55 pm    Post subject: Reply with quote

blugendoo,

Your quoted text comes from grub, that's a good sign.
Grub exits by jumping to the kernel start address. One of the first things the kernel does is display a message "Decompressing Kernel ...."

Did you see that?

I would have expected your boot to fail when the kernel tried to mount the root filesystem but that would be several screenfuls of kernel messages further on.

Root on usb needs as extra kernel parameter. Normally the kernel tries to mount root before it starts the USB subsystem, thun root on USB is doomed to fail.
However, if you add rootwait to the kernel command line, the kernel will wait (forever) for root to appear.
You are going to need that anyway but it sounds like you have other issues too.
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 6:38 pm    Post subject: Reply with quote

I'm very grateful to your support here, as the intended purpose of my first post was a hello and feedback story.
It turns out that now I need more help, so having direct answers greatly accelerate the debugging of my setup: thanks!

No more USB drive: it's now internal SATA.
As expected, Grub reinstallation from Rescue CD now brings back Grub on EFI boot. 8)

It is still stuck right after displaying "loading initial ramdisk" (in French if I remember well, that's the Gentoo effect of the locale setting :D )
I have no screen flicker, only a blinking cursor. I have no message from kernel decompressing itself. :?

Of course I'm also doing my own research to solve this... :wink:
https://forums.gentoo.org/viewtopic-p-7240690.html
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Tue Apr 12, 2016 6:48 pm    Post subject: Reply with quote

blugendoo,

If grub loads you should see the grub menu and the grub splash screen.
Do you see that?

If not, it may not be grub that is loading your kernel. The kernel can be compiled to be an EFI compliant program, so that its loaded automatically on boot without the use of grub.
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 7:16 pm    Post subject: Reply with quote

Yes, NeddySeagoon: I have Grub menu, etc.

I think it could be a framebuffer issue like here:
https://forums.gentoo.org/viewtopic-t-989210.html (last post)

I have removed many framebuffer options from the kernel config, following those advice for NVidia drivers, kernel KMS
https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers#Kernel_compatibility
https://wiki.gentoo.org/wiki/Xorg/Guide

I'll put some fb support back and test...

EDIT:
I allready had:
Code:
    Console display driver support --->
      <*>  Framebuffer Console Support

But no fb selected for
Code:
-*- Support for frame buffer devices  --->
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Tue Apr 12, 2016 7:28 pm    Post subject: Reply with quote

blugendoo,

Ahhh nvidia-drivers. The nVidia drivers advertise that they do not work with a framebuffer console.
If you try, you will get dire warnings in dmesg.

What is important is that your framebuffer driver of choice does not attempt to control the graphics chip set.
Simple Framebuffer and/or EFI framebuffer may work. VESA framebuffer used to work for me but my video card is too old now, so I no longer use nVidia drivers.

The kernel uses the VGA text console to start with, then switches to a framebuffer console later, if it can.

Its quite possible to build the kernel with no console drivers at all. That gets you black text on a black background, which is hard to read :)

Hmm ... you have two graphics cards. Do you have the grub output on one and the kernel output on the other?
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 7:43 pm    Post subject: Reply with quote

NeddySeagoon wrote:
What is important is that your framebuffer driver of choice does not attempt to control the graphics chip set.
Simple Framebuffer and/or EFI framebuffer may work. VESA framebuffer used to work for me but my video card is too old now, so I no longer use nVidia drivers.

Well... Gentoo wiki reads "Be warned that enabling efifb support in kernel (CONFIG_FB_EFI=y) causes intermittent problems with the initialization of the nvidia drivers."
So I'll try that - better than nothing (kernel compiling...)

NeddySeagoon wrote:
Hmm ... you have two graphics cards. Do you have the grub output on one and the kernel output on the other?

Good idea. I won't be able to try that right now, but if I don't get any improvement I'll be able to check tomorrow morning.
Back to top
View user's profile Send private message
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 8:26 pm    Post subject: Reply with quote

That was it: after adding EFI framebuffer support I'm now able to log in as root.

There's a few odd things I should be able to solve:
Despite the setup I prepared on chrooted environment, I don't have the proper hostname, the fr keyboard, the eth0 on dhcp, ...
I'll work on that. It could be a systemd issue, right ?

But I would apreciate some help for this:

Some messages keep trashing the console I am on (tty0, tty1, ...), it's like
Code:
[172.1315646465] USB Disconnect ...
[172.9855564564] USB new device ...
[173.1315646465] Microsoft Basic Optical Mouse ...
...

with increasing device number, every 10s or so.
I wouldn't mind working with US keyboard on FR, and I can loadkeys if I need, but having the screen jammed so often with a dozen lines is not practical.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Tue Apr 12, 2016 8:32 pm    Post subject: Reply with quote

blugendoo,

Are you actually using systemd?

The default on Gentoo is Openrc. What is the name of PID 1 on your system. I get init.
If you have managed to boot systemd from your first boot, well done!

I can't support systemd as I don't use it. I won't go into why in your topic.
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Tue Apr 12, 2016 8:46 pm    Post subject: Reply with quote

Yes, I thought I would rather go from start to the target system I want (thus the elephant to eat).

So I emerged systemd on chroot, systemd is the init for boot config and in the kernel I only have the systemd support, not the Openrc.

I'm not sure if I should be glad to ear that having the very first boot on Gentoo with systemd is a kind of an achievement.

Anyway, I'll try to fix a few things before sleep...

EDIT:
- no more console jamming: I started metalog. I think that without any log eater the kernel send printk to console, right?
- keyboard ok
Code:
localectl set-locale LANG=fr_FR.utf8
localectl set-keymap fr
localectl set-x11-keymap fr
systemctl enable systemd-networkd.service
systemctl start  systemd-networkd.service
systemctl enable metalog.service
systemctl start  metalog.service

But no result for network and hostname.

That's all for now, thanks again for answering here.

EDIT2:
And yes, process 1 is systemd, so that's a first Gentoo boot on systemd :)

EDIT3:
By the way NeddySeagoon, I noticed your signature:
Quote:
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
I belong to the third group: those who keep losing data at each drive failure :mrgreen:
Back to top
View user's profile Send private message
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Wed Apr 13, 2016 6:56 pm    Post subject: Reply with quote

Network is up! (ping google.com)

It lacked drivers and was badly configured! My first time with systemd, udev rules, ...
So no eth0 but other names.
I've chosen rules so that I now have net0 and net1 as ethernet device names 8)

I'm quite excited.

My next steps will be to get hostname set, at last! I think it's systemd again.
Then my unprivileged user, and graphic environment!

Hum... I just wonder why I wasn't able to simply "startx", since on chroot I emerged world with a KDE Plasma profile. :|
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Wed Apr 13, 2016 8:17 pm    Post subject: Reply with quote

blugendoo,

For startx to just work you need xterm, xclock and twm. That's what startx runs by default.

To make startx start other things, you need to edit your ~/.xinitrc file.
Its missing until you create it.
_________________
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
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Wed Apr 13, 2016 9:40 pm    Post subject: Reply with quote

Quote:
For startx to just work you need xterm, xclock and twm. That's what startx runs by default.

Mmmm... I also need X.org, this is my main concern actually.

This:
Code:
emerge --ask x11-base/xorg-server
is asking many USE changes, from 64 to 32. This is 12 packages out of 43 that would be rebuilt in 32 bits. The others are new.
So I said No.

It reads:
Quote:
The following USE changes are necessary to proceed:
and a dozen like
Quote:
[ebuild R ] x11-libs/libxcb-1.11.1 ABI_X86="32*"
...
>=x11-libs/libxcb-1.11.1 abi_x86_32


For the moment this is the only thing left in my way to Gentoo.
I've done some searches, nothing conclusive, so I'm asking for some help here.
Back to top
View user's profile Send private message
324874
Apprentice
Apprentice


Joined: 26 Jul 2014
Posts: 168

PostPosted: Thu Apr 14, 2016 2:07 pm    Post subject: Newbie on the way to Gentoo... Reply with quote

Hi everyone, welcome to Gentoo, blugendoo !

I take advantage of the title of your thread to share one comment.

1. For me, the most difficult thing is to find where search to understand what I have to do.

search : how to learn things in an effective manner ?

Indeed, a few years ago I hadn't knowledges about information technologies, operating systems, computers, etc.

Best regards,

neoptslap
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Fri Apr 15, 2016 7:27 am    Post subject: Reply with quote

Welcome to Gentoo, blugendoo :-)

You might like these tips collected over the years; I recommend reading "the basics" at least.

Don't forget IRC: chat.freenode.net or .org #gentoo for support and: #gentoo-chat for off-topic witter, with the same standard of moderation as the forums (not OTW.)

Bear in mind that there is a much wider world exposed to you on freenode; #bash is essential, ime, and will teach you an awful lot about the UNIX userland (as well as the implementation language for all ebuilds.)
Similarly ##workingset if you want to learn build-systems (make, toolchain, autotools, cmake, etc.)

#friendly-coders if you're finding IRC a bit overwhelming, or running into someone who is a pain (happens.)
#coding-n00bs if you are really new, and want to witter off-topic as well.

/topic #friendly-coders links to many other coding channels, and is how you find out a bit about a channel before entering with eg: /join #gentoo
Back to top
View user's profile Send private message
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Fri Apr 15, 2016 8:41 am    Post subject: Reply with quote

@steveL thanks for the nice tips collection.
I see there's the EFI-nvidia thread on which I stumble upon recently: a good one.

This is my new issue now that I have X.org emerged. :?

There is a long pause after text login prompt display (with stale cursor), a slight flicker, and then the text cursor for login starts blinking.
Then if I startx, it leads to black screen and monitor goes in power save mode. :roll:
SysRq keys somewhat work to reboot.

I'll do my homework before asking help.
(EDITED)
It seems that many admins will keep having those warnings
Code:
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.


Advice about Gentoo housekeeping are also a must-have, I'll see those a bit later.

EDIT:
NVidia says:
Quote:
The message is a little misleading in UEFI mode. What it means it that the GPU was initialized to a graphical mode using the legacy VGA BIOS, regardless of whether the system was booted in UEFI mode or not. Typically this happens if the Compatibility Support Module (CSM) is enabled in the system BIOS. If you have an option to disable CSM in the SBIOS, please try that.

So I'll try with pure EFI boot, as initially intended. I've kept EFI+CSM compatibility to be able to boot my current Linux Mint system.
EDIT 2: nothing changes with pure EFI boot :|


Last edited by blugendoo on Sat Apr 16, 2016 12:53 pm; edited 2 times in total
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Fri Apr 15, 2016 2:06 pm    Post subject: Reply with quote

blugendoo wrote:
@steveL thanks for the nice tips collection.
I see there's the EFI-nvidia thread on which I stumble upon recently: a good one.

Hey, you're welcome; everything I learnt about maintaining Gentoo, I learnt from other users, here or on IRC.
Most of the tips are NeddySeagoon's anyhow. ;-)

I posted your follow-up to that thread; thanks for the tip. :-)
Back to top
View user's profile Send private message
blugendoo
n00b
n00b


Joined: 11 Apr 2016
Posts: 23

PostPosted: Sat Apr 16, 2016 7:23 pm    Post subject: Reply with quote

Working on those two problems:
1) X.org nvidia crash freeze
2) USB mouse repeatedly disconnect
I deal with the latter on another thread

Regarding nvidia I new it wouldn't be easy.
Here are some kernel log lines related to initial temporary freeze and the crash freeze on X startup:
(can't find a bbcode to fold this)

Code:
Apr 16 20:47:57 [kernel] [    2.670598] nvidia: module license 'NVIDIA' taints kernel.
Apr 16 20:47:57 [kernel] [    2.670600] Disabling lock debugging due to kernel taint
Apr 16 20:47:57 [kernel] [    2.675312] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Apr 16 20:47:57 [kernel] [    2.675364] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
Apr 16 20:47:57 [kernel] [    2.675561] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
...
Apr 16 20:47:57 [kernel] [    2.675574] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  361.28  Wed Feb  3 15:48:04 PST 2016
Apr 16 20:47:58 [kernel] [    3.263203] NVRM: Your system is not currently configured to drive a VGA console
Apr 16 20:47:58 [kernel] [    3.263206] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Apr 16 20:47:58 [kernel] [    3.263207] NVRM: requires the use of a text-mode VGA console. Use of other console
Apr 16 20:47:58 [kernel] [    3.263207] NVRM: drivers including, but not limited to, vesafb, may result in
Apr 16 20:47:58 [kernel] [    3.263208] NVRM: corruption and stability problems, and is not supported.
<======= temporary 34s freeze upon startup (right after text login display) ========>
Apr 16 20:48:32 [kernel] [   24.268724] INFO: rcu_sched self-detected stall on CPU
Apr 16 20:48:32 [kernel] [   24.268726] _3-...: (21000 ticks this GP) idle=cb5/140000000000001/0 softirq=1632/1633 fqs=6998
Apr 16 20:48:32 [kernel] [   24.268727] _ (t=21000 jiffies g=245 c=244 q=31)
Apr 16 20:48:32 [kernel] [   24.268727] Task dump for CPU 3:
Apr 16 20:48:32 [kernel] [   24.268741] nvidia-smi      R  running task    12640  4296   4289 0x00000008
Apr 16 20:48:32 [kernel] [   24.268742]  ffffffff81e42040 ffff88022eb83dd8 ffffffff8107d3ef 0000000000000003
Apr 16 20:48:32 [kernel] [   24.268743]  ffffffff81e42040 ffff88022eb83df0 ffffffff8107f744 0000000000000004
Apr 16 20:48:32 [kernel] [   24.268744]  ffff88022eb83e20 ffffffff810a6186 ffff88022eb96200 ffffffff81e42040
Apr 16 20:48:32 [kernel] [   24.268744] Call Trace:
Apr 16 20:48:32 [kernel] [   24.268749]  <IRQ>  [<ffffffff8107d3ef>] sched_show_task+0xbf/0x120
Apr 16 20:48:32 [kernel] [   24.268750]  [<ffffffff8107f744>] dump_cpu_task+0x34/0x40
Apr 16 20:48:32 [kernel] [   24.268752]  [<ffffffff810a6186>] rcu_dump_cpu_stacks+0x86/0xc0
Apr 16 20:48:32 [kernel] [   24.268754]  [<ffffffff810a9b39>] rcu_check_callbacks+0x489/0x740
Apr 16 20:48:32 [kernel] [   24.268755]  [<ffffffff810bc890>] ? tick_sched_do_timer+0x30/0x30
Apr 16 20:48:32 [kernel] [   24.268766]  [<ffffffff810ae494>] update_process_times+0x34/0x60
Apr 16 20:48:32 [kernel] [   24.268767]  [<ffffffff810bc2f1>] tick_sched_handle.isra.15+0x31/0x40
Apr 16 20:48:32 [kernel] [   24.268768]  [<ffffffff810bc8c8>] tick_sched_timer+0x38/0x70
Apr 16 20:48:32 [kernel] [   24.268769]  [<ffffffff810af13c>] __hrtimer_run_queues+0xec/0x260
Apr 16 20:48:32 [kernel] [   24.268769]  [<ffffffff810af463>] hrtimer_interrupt+0xa3/0x190
Apr 16 20:48:32 [kernel] [   24.268771]  [<ffffffff8103c3e3>] local_apic_timer_interrupt+0x33/0x60
Apr 16 20:48:32 [kernel] [   24.268772]  [<ffffffff8103cf08>] smp_apic_timer_interrupt+0x38/0x50
Apr 16 20:48:32 [kernel] [   24.268774]  [<ffffffff818d470f>] apic_timer_interrupt+0x7f/0x90
Apr 16 20:48:32 [kernel] [   24.268844]  <EOI>  [<ffffffffa0b72a40>] ? nv_rdtsc+0x170/0x270 [nvidia]
Apr 16 20:48:32 [kernel] [   24.268875]  [<ffffffffa06512a9>] ? os_io_write_dword+0x9/0x10 [nvidia]
Apr 16 20:48:32 [kernel] [   24.268933]  [<ffffffffa0b78bfd>] ? _nv018016rm+0x4d4d/0xbd60 [nvidia]
... same nv stuff here ...
Apr 16 20:48:32 [kernel] [   24.269337]  [<ffffffffa0b6e92a>] ? _nv000691rm+0x2ba/0x340 [nvidia]
Apr 16 20:48:32 [kernel] [   24.269394]  [<ffffffffa0b6322a>] ? rm_disable_adapter+0x6a/0x130 [nvidia]
Apr 16 20:48:32 [kernel] [   24.269422]  [<ffffffffa06466ea>] ? nv_close_device+0xea/0x130 [nvidia]
Apr 16 20:48:32 [kernel] [   24.269451]  [<ffffffffa06487d8>] ? nvidia_close+0xc8/0x300 [nvidia]
Apr 16 20:48:32 [kernel] [   24.269479]  [<ffffffffa0646397>] ? nvidia_frontend_close+0x27/0x50 [nvidia]
Apr 16 20:48:32 [kernel] [   24.269480]  [<ffffffff81172d4a>] ? __fput+0xda/0x1e0
Apr 16 20:48:32 [kernel] [   24.269482]  [<ffffffff81172e89>] ? ____fput+0x9/0x10
Apr 16 20:48:32 [kernel] [   24.269483]  [<ffffffff81070481>] ? task_work_run+0x71/0x90
Apr 16 20:48:32 [kernel] [   24.269484]  [<ffffffff81002203>] ? exit_to_usermode_loop+0x83/0xa0
Apr 16 20:48:32 [kernel] [   24.269485]  [<ffffffff81002b02>] ? syscall_return_slowpath+0x92/0x110
Apr 16 20:48:32 [kernel] [   24.269486]  [<ffffffff818d3b27>] ? int_ret_from_sys_call+0x25/0x8f
Apr 16 20:48:32 [kernel] [   24.548746] INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 3-
Apr 16 20:48:32 [kernel] [   24.548746] Task dump for CPU 3:
Apr 16 20:48:32 [kernel] [   24.548748] nvidia-smi      R  running task    12640  4296   4289 0x00000008
Apr 16 20:48:32 [kernel] [   24.548749]  ffff8800c6ab3be8 ffff8800c616afa8 ffffffffa0b72a40 0000000000000000
Apr 16 20:48:32 [kernel] [   24.548750]  00000000000c42d1 00000000000c42d1 00000000038dcf80 0000000000000001
Apr 16 20:48:32 [kernel] [   24.548751]  000000000000e00c 00000000000a0000 000000000000e00c ffffffffa0b729ce
Apr 16 20:48:32 [kernel] [   24.548751] Call Trace:
Apr 16 20:48:32 [kernel] [   24.548828]  [<ffffffffa0b72a40>] ? nv_rdtsc+0x170/0x270 [nvidia]
Apr 16 20:48:32 [kernel] [   24.548887]  [<ffffffffa0b729ce>] ? nv_rdtsc+0xfe/0x270 [nvidia]
... same nv stuff here ...


And crashing when starting X with sddm (recover via sysrq keys to reboot) :
Code:
Apr 16 20:39:13 [kernel] [ 2154.645200] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  361.28  Wed Feb  3 15:15:17 PST 2016
Apr 16 20:39:13 [kernel] [ 2154.645427] nvidia-modeset: Allocated GPU:0 (GPU-6c5ea887-6efd-0959-9ebf-4d22a96b828e) @ PCI:0000:01:00.0
Apr 16 20:39:16 [kernel] [ 2157.724398] nvidia-modeset: WARNING: GPU:0: Lost display notification; continuing.
...
Apr 16 20:44:36 [kernel] [ 2477.833854] kworker/dying (5187) used greatest stack depth: 12360 bytes left
Apr 16 20:44:40 [kernel] [ 2481.833895] kworker/dying (4) used greatest stack depth: 12200 bytes left
Apr 16 20:47:39 [kernel] [ 2660.689676] sysrq: SysRq : Keyboard mode set to system default
Apr 16 20:47:40 [kernel] [ 2661.532804] sysrq: SysRq : Emergency Remount R/O


Maybe a libgl 32 problem:
https://bbs.archlinux.org/viewtopic.php?id=209511&p=2
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat 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