Dmesg NVRM / VGA mode?

Kilzool · 2012-06-18 15:08:17

# dmesg | tail

[ 15.458823] NVRM: Your system is not currently configured to drive a VGA console
[ 15.458830] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 15.458834] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 15.458838] NVRM: drivers including, but not limited to, vesafb, may result in
[ 15.458841] NVRM: corruption and stability problems, and is not supported.

# cat /boot/grub/menu.lst (kernel line)
kernel /vmlinuz-linux root=/dev/sdb3 ro quiet vga=795 5

# uname -a

Linux desktop 3.4.2-2-ARCH #1 SMP PREEMPT Tue Jun 12 07:19:42 UTC 2012 i686 GNU/Linux

# lspvi -v
01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9400 GT] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 1413
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at fea00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel driver in use: nvidia

# pacman -Ss nvidia | grep installed

extra/libvdpau 0.4.1-2 [installed]
extra/nvidia 302.17-1 [installed]
extra/nvidia-utils 302.17-1 [installed]

Last edited by Kilzool (2012-06-18 15:54:12)

paulb787 · 2012-06-19 08:54:47

let me take a guess you are booting UEFI?

skunktrader · 2012-06-19 09:15:23

paulb787 wrote:

let me take a guess you are booting UEFI?

I have the same error/message and there is no UEFI

Gusar · 2012-06-19 09:18:51

http://mailman.archlinux.org/pipermail/ … 27243.html

kjell · 2012-06-19 13:14:19

Got same error (im back on older kernel +nvidia due to other issues) but this didnt seem to cause any problems, in the short time I did run it..

paulb787 · 2012-06-19 16:30:31

My story is i got this error with uefi and grub2 and nvividia and a framebufer . it related to the console resoultion and the framebuffer i believe. nvidia is not supoorting a console framebuffer with UEFI booting.

Remove vga=xxx and see if that removes the message

Last edited by paulb787 (2012-06-19 16:33:11)

Kilzool · 2012-06-20 05:20:44

paulb787 wrote:

My story is i got this error with uefi and grub2 and nvividia and a framebufer . it related to the console resoultion and the framebuffer i believe. nvidia is not supoorting a console framebuffer with UEFI booting.

Remove vga=xxx and see if that removes the message

No on UEFI booting.
When leaving out the vga=xxx it does not give that error... but that creates very large fonts when booting and/or switching to another getty (ALT-F2, etc)
It doesn't seem to create a problem when I use vga=795, it just causes that warning in the dmesg | tail.

Thanks for replying.

Last edited by Kilzool (2012-06-20 05:29:28)

Gusar · 2012-06-20 08:51:59

Another one of those weird phenomenons I observe every now and then...

Why are so many people association this with UEFI?

Ypnose · 2012-09-25 17:01:57

I got these errors with a non UEFI system. Got vga=792 on my boot line too (with syslinux).

Last edited by Ypnose (2012-09-25 17:17:14)

Gusar · 2012-09-25 19:09:02

Ypnose wrote:

Got vga=792 on my boot line too (with syslinux).

That's exactly why you get the message.

Ypnose · 2012-09-25 19:14:50

Yes, I know it. But before Nvidia driver 30x, we didn't have any warnings. Even if it's not very serious, I prefer removing "vga=792" and keep my logs clean.
The drawback is a tty with a poor resolution.

hugogee · 2013-01-31 20:12:23

Solved, thanks to the nice people in #archlinux

Add following to the end of kenel line in /boot/grub/grub.cfg

video=vesa:off vga=normal

e.g.
linux /vmlinuz-linux root=/dev/mapper/vgroup-root ro cryptdevice=/dev/sda2:vgroup quiet video=vesa:off vga=normal

Last edited by hugogee (2013-01-31 20:13:38)

cinelli · 2013-01-31 20:19:26

hugogee wrote:

Solved, thanks to the nice people in #archlinux
Add following to the end of kenel line in /boot/grub/grub.cfg
video=vesa:off vga=normal
e.g.
linux /vmlinuz-linux root=/dev/mapper/vgroup-root ro cryptdevice=/dev/sda2:vgroup quiet video=vesa:off vga=normal

Glad that I could help.

::edit::
Please mark as [solved]

Last edited by cinelli (2013-01-31 20:29:19)

beta990 · 2013-01-31 21:08:56

Sorry for replying to this topic. I still have this message and I'm booting in UEFI. rEFInd is what I use, so I don't think the grub-edits don't work. Any solution?

[    2.673959] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  313.18  Wed Jan  9 17:02:09 PST 2013
[    4.697485] NVRM: Your system is not currently configured to drive a VGA console
[    4.697487] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[    4.697489] NVRM: requires the use of a text-mode VGA console. Use of other console
[    4.697490] NVRM: drivers including, but not limited to, vesafb, may result in
[    4.697491] NVRM: corruption and stability problems, and is not supported.

Last edited by beta990 (2013-01-31 21:10:25)

Gusar · 2013-02-01 08:10:47

The driver officially supports only a standard VGA text console. But with EFI that one doesn't exist, there's only efifb.

beta990 · 2013-02-01 11:25:55

OK, thanks for the info.

When searching I found these kernel flags, is this the way to get it to work with rEFInd? (not showing the debug-message)
pci=nocrs
video=efifb

Last edited by beta990 (2013-02-01 11:26:15)

Gusar · 2013-02-01 16:00:10

What exactly is the problem? Do you just get that message (which is not an error as such, just a warning that things might not work), or does the driver not work at all? The driver does not officially support EFI, so it wouldn't be weird if it doesn't, but I've seen reports that it does anyway.

If the driver doesn't work, boot the machine in BIOS mode, or switch to the nouveau driver.

Last edited by Gusar (2013-02-01 16:01:07)

beta990 · 2013-02-01 20:57:24

Gusar wrote:

What exactly is the problem? Do you just get that message (which is not an error as such, just a warning that things might not work), or does the driver not work at all? The driver does not officially support EFI, so it wouldn't be weird if it doesn't, but I've seen reports that it does anyway.
If the driver doesn't work, boot the machine in BIOS mode, or switch to the nouveau driver.

The driver works without any problems. Although I seem to get some problem with DVD-playback/divx in VLC, but that might be a codec problem.

Is there no way to remove the (debug) message?

Gusar · 2013-02-01 23:30:01

beta990 wrote:

Is there no way to remove the (debug) message?

Well, there's the loglevel kernel parameter. But why would you need to remove it? OCD?

Last edited by Gusar (2013-02-01 23:42:08)

beta990 · 2013-02-04 10:32:58

Gusar wrote:

beta990 wrote:
Is there no way to remove the (debug) message?
Well, there's the loglevel kernel parameter.

Thanks, I will leave the log-message as it is.

walderich · 2013-02-08 19:48:31

Again sorry to post here, but I also get this warning message after switching from nouveau to nvidia driver.
My problem is, that I don't use a graphical login manager, and my screen stays black until logged into X.

I already tried the "video=vesa:off vga=normal" option, but without success. Any other suggestions?

MrCode · 2013-02-08 19:55:58

I get this same message on a BIOS lappy, and all it means is that they don't support a framebuffer console in their driver, and using e.g. vesafb is unsupported, but may work. It shouldn't have anything to do with X. Console framebuffer works for me, but at a limited resolution that only closely matches the native resolution of the display panel (1360x768; native is 1366x768).

walderich · 2013-02-08 20:45:46

But in my case, the framebuffer does not work. The display only shows up,
after X was (blindly) started. The dmesg output says:

[ 0.410599] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[ 0.410600] vesafb: scrolling: redraw
[ 0.410602] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.411380] vesafb: framebuffer at 0xe9000000, mapped to 0xffffc90005000000, using 8128k, total 8128k

So it actually detects the native display resolution correctly, but still no
picture. What I do see are the status messages, only the login is "hidden".
Switching to another TTY doesn't help either. But after X was started,
switching back to any TTY works again.

blackout23 · 2013-02-08 22:00:23

I remember this message from the first time i played around with the vga= kernel option long time ago. There is basically now way around it and I'm not sure if it does produce any problems afterall.

On my laptop I can only get what my bios allows as resolution (1024x768x32) on a 1280x800 display. Only way to get true native resolution is with nouveau and KMS.

Tried uvesafb and everything in the wiki but simply can't get any high than 1024x768. Syslinux Hardware Detection Tools also only listes this has the highest possible vga mode and provides the appropriate number for it.

Let's hope that NVIDA will support KMS in the future. Not only for prettier ttys but also for wayland.
Also like to use KMSCON in the future as kernel console replacement. Anti-Aliased hardware accelerated FullHD console Hello!
kmscon-git is already in the AUR.

Last edited by blackout23 (2013-02-08 22:02:34)

xCh12i5 · 2018-09-12 09:53:35

Hello,

sorry for bumping this old post. Yesterday I switched from legacy boot to UEFI on my system and run into exactly this issue. Because I'm not using a graphical login manager, after booting I have to have a TTY. My system is up to date and the nvidia driver is also installed.

UEFI configuration details:

cat /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=/dev/sda2:lvm root=/dev/mapper/luks-root quiet rw

Details about kernel modules:

cat /etc/mkinitcpio.conf | grep -iP "^modules.*"
MODULES=(nvidia nvidia-dkms)

I've append at the end of the options line in /boot/loader/entries/arch.conf the following parameter:

nomodset
pci=nocrs video=efifb
video=vesa:off vga=normal
vga=792

Unfortunately none of them succeeded. Before editing the MODULES section of /etc/mkinitcpio.conf after booting the system the screen remained black, but as typing blind and executing startx everything has worked fine. Any ideas, what I've overlooked? Or is switching back to legacy boot the only option I have?

Kind regards
xCh12i5

Arch Linux

#1 2012-06-18 15:08:17

Dmesg NVRM / VGA mode?

#2 2012-06-19 08:54:47

Re: Dmesg NVRM / VGA mode?

#3 2012-06-19 09:15:23

Re: Dmesg NVRM / VGA mode?

#4 2012-06-19 09:18:51

Re: Dmesg NVRM / VGA mode?

#5 2012-06-19 13:14:19

Re: Dmesg NVRM / VGA mode?

#6 2012-06-19 16:30:31

Re: Dmesg NVRM / VGA mode?

#7 2012-06-20 05:20:44

Re: Dmesg NVRM / VGA mode?

#8 2012-06-20 08:51:59

Re: Dmesg NVRM / VGA mode?

#9 2012-09-25 17:01:57

Re: Dmesg NVRM / VGA mode?

#10 2012-09-25 19:09:02

Re: Dmesg NVRM / VGA mode?

#11 2012-09-25 19:14:50

Re: Dmesg NVRM / VGA mode?

#12 2013-01-31 20:12:23

Re: Dmesg NVRM / VGA mode?

#13 2013-01-31 20:19:26

Re: Dmesg NVRM / VGA mode?

#14 2013-01-31 21:08:56

Re: Dmesg NVRM / VGA mode?

#15 2013-02-01 08:10:47

Re: Dmesg NVRM / VGA mode?

#16 2013-02-01 11:25:55

Re: Dmesg NVRM / VGA mode?

#17 2013-02-01 16:00:10

Re: Dmesg NVRM / VGA mode?

#18 2013-02-01 20:57:24

Re: Dmesg NVRM / VGA mode?

#19 2013-02-01 23:30:01

Re: Dmesg NVRM / VGA mode?

#20 2013-02-04 10:32:58

Re: Dmesg NVRM / VGA mode?

#21 2013-02-08 19:48:31

Re: Dmesg NVRM / VGA mode?

#22 2013-02-08 19:55:58

Re: Dmesg NVRM / VGA mode?

#23 2013-02-08 20:45:46

Re: Dmesg NVRM / VGA mode?

#24 2013-02-08 22:00:23

Re: Dmesg NVRM / VGA mode?

#25 2018-09-12 09:53:35

Re: Dmesg NVRM / VGA mode?

Board footer