From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clone root from HDD to SSD causes no video with NVIDIA driver
Date: Mon, 15 Jun 2020 16:19:40 +0200 [thread overview]
Message-ID: <5383829.DvuYhMxLoT@eve> (raw)
In-Reply-To: <AM0PR10MB2436118577FBC8EB92ECDABDF79C0@AM0PR10MB2436.EURPRD10.PROD.OUTLOOK.COM>
On Monday, June 15, 2020 9:56:39 AM CEST Raffaele BELARDI wrote:
> * From: Dale <rdalek1967@gmail.com>
> * Sent: Wednesday, June 10, 2020 08:02
> * To: gentoo-user@lists.gentoo.org<mailto:gentoo-user@lists.gentoo.org>
> * Subject: Re: [gentoo-user] clone root from HDD to SSD causes no video
> with NVIDIA driver
>
> * Raffaele BELARDI wrote:
> * nomodeset did not change anything, but adding EFI_FB to the kernel
> finally got me a functional console.
* But if I startx from there I am
> back again to the same point, no X, no console switching with CTR-ALT-Fn, *
> no crash in syslog, I have to SSH to get to a working shell. I'm not
> getting anywhere, I think I'll better install from stage3.
>
> * Odds are, if you start from stage3, you will get the same problem
> again unless you do something different.
* When I first stated using
> Gentoo, I didn't realize that one can restart a install pretty much
> anywhere in the install. * Starting over doesn't get you anything
> different if you repeat the same steps.
> Just to update: I tried all the hints received here with no luck. Since
> others on this list managed to get uefifb working with the NVIDIA driver I
> believe the problem could be my mobo/UEFI FW/GPU combination. I found some
> rather old posts ([1], [2]) supporting this hypothesis. For the moment I
> switched to nouveau.
> Thanks again to all,
>
> raffaele
>
> [1]
> https://forums.developer.nvidia.com/t/uefi-nvidia-vga-console-complaints/37
> 690
[2]
> https://forums.developer.nvidia.com/t/nvidia-devs-any-eta-on-fbdev-console->
mode-setting-implementation/47043
Personally, I would not expect this to be related to mainboard firmware/bios
issues as I have not had any issues with efifb and nvidia-drivers on several
systems.
What is your kernel-commandline?
Mine is really simple:
$ cat /proc/cmdline
root=/dev/nvme0n1p3
I get the following in my dmesg for "efifb":
====
[ 8.717047] efifb: probing for efifb
[ 8.717061] efifb: framebuffer at 0xd1000000, using 3072k, total 3072k
[ 8.717062] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 8.717064] efifb: scrolling: redraw
[ 8.717065] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 8.719748] fb0: EFI VGA frame buffer device
====
Which is nowhere near the real resolution my screen can handle, but for
emergencies, this is definitely sufficient.
For completeness, these are the entries for nvidia:
====
$ dmesg | grep -i nvidia
[ 11.222893] nvidia: loading out-of-tree module taints kernel.
[ 11.222908] nvidia: module license 'NVIDIA' taints kernel.
[ 11.241368] nvidia-nvlink: Nvlink Core is being initialized, major device
number 240
[ 11.241687] nvidia 0000:01:00.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=none:owns=io+mem
[ 11.283229] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 440.82 Wed Apr
1 20:04:33 UTC 2020
[ 11.287732] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for
UNIX platforms 440.82 Wed Apr 1 19:41:29 UTC 2020
[ 11.289189] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 11.289191] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on
minor 0
[ 11.861737] input: HDA NVidia HDMI/DP,pcm=3 as /devices/
pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input28
[ 11.862152] input: HDA NVidia HDMI/DP,pcm=7 as /devices/
pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input29
[ 11.979061] input: HDA NVidia HDMI/DP,pcm=8 as /devices/
pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input30
[ 11.979134] input: HDA NVidia HDMI/DP,pcm=9 as /devices/
pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input31
====
On a side-note, anyone know how to prevent these sound-devices from appearing?
I never use these on this system.
--
Joost
next prev parent reply other threads:[~2020-06-15 14:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:02 [gentoo-user] clone root from HDD to SSD causes no video with NVIDIA driver Raffaele BELARDI
2020-06-08 16:07 ` Neil Bothwick
2020-06-08 18:07 ` Raffaele BELARDI
2020-06-08 23:42 ` Neil Bothwick
2020-06-08 16:14 ` tuxic
2020-06-08 18:20 ` Raffaele BELARDI
2020-06-09 3:43 ` tuxic
2020-06-09 3:51 ` Ashley Dixon
2020-06-09 17:10 ` Raffaele BELARDI
2020-06-09 6:23 ` J. Roeleveld
2020-06-09 6:38 ` tuxic
2020-06-09 17:04 ` Raffaele BELARDI
2020-06-10 14:28 ` J. Roeleveld
2020-06-10 5:47 ` Raffaele BELARDI
2020-06-10 6:02 ` Dale
2020-06-10 7:00 ` Raffaele BELARDI
2020-06-10 16:07 ` J. Roeleveld
2020-06-15 7:56 ` Raffaele BELARDI
2020-06-15 14:19 ` J. Roeleveld [this message]
2020-06-16 7:13 ` Raffaele BELARDI
2020-06-10 10:02 ` Wols Lists
2020-06-09 17:13 ` Raffaele BELARDI
2020-06-10 11:56 ` tuxic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5383829.DvuYhMxLoT@eve \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox