UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

yossarianuk · 2012-06-25 23:00:41

HI.

On every boot (with Nvidia driver installed) in UEFI mode I get the following message

The system 'seems' fine however.

Should I worry about this?

----------------------------------------------------
Jun 25 23:39:52 localhost kernel: [ 19.025370] WARNING: at arch/x86/mm/ioremap.c:102 __ioremap_caller+0x392/0x3a0()
Jun 25 23:39:52 localhost kernel: [ 19.025371] Hardware name: MS-7758
Jun 25 23:39:52 localhost kernel: [ 19.025372] Modules linked in: nls_cp437 snd_hda_codec_hdmi snd_hda_codec_realtek nvidia(PO) snd_hda_intel snd_hda_codec microcode aesni_intel aes_x86_64 aes_generic ghash_clmulni_intel cryptd coretemp crc32c_intel snd_hwdep usbhid hid shpchp mei(C) ppdev parport_pc pci_hotplug parport acpi_cpufreq intel_agp r8169 iTCO_wdt mii iTCO_vendor_support mperf intel_gtt i2c_i801 i2c_core evdev psmouse video button processor pcspkr serio_raw fan thermal snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore vfat fat ext4 crc16 jbd2 mbcache ehci_hcd xhci_hcd usbcore usb_common sr_mod cdrom sd_mod ahci libahci libata scsi_mod
Jun 25 23:39:52 localhost kernel: [ 19.025404] Pid: 537, comm: X Tainted: P C O 3.4.4-2-ARCH #1
Jun 25 23:39:52 localhost kernel: [ 19.025405] Call Trace:
Jun 25 23:39:52 localhost kernel: [ 19.025409] [<ffffffff810515cf>] warn_slowpath_common+0x7f/0xc0
Jun 25 23:39:52 localhost kernel: [ 19.025410] [<ffffffff8105162a>] warn_slowpath_null+0x1a/0x20
Jun 25 23:39:52 localhost kernel: [ 19.025412] [<ffffffff81043092>] __ioremap_caller+0x392/0x3a0
Jun 25 23:39:52 localhost kernel: [ 19.025446] [<ffffffffa0968e45>] ? os_map_kernel_space+0x85/0xf0 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025449] [<ffffffff813526c9>] ? pci_conf1_read+0xc9/0x120
Jun 25 23:39:52 localhost kernel: [ 19.025451] [<ffffffff810430d4>] ioremap_cache+0x14/0x20
Jun 25 23:39:52 localhost kernel: [ 19.025474] [<ffffffffa0968e45>] os_map_kernel_space+0x85/0xf0 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025503] [<ffffffffa0933b0f>] _nv014657rm+0x69/0x85 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025537] [<ffffffffa03957ea>] ? _nv009542rm+0x89/0x140 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025571] [<ffffffffa0395959>] ? _nv014228rm+0xb8/0x102 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025604] [<ffffffffa0395e07>] ? _nv014266rm+0x58/0x9e [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025638] [<ffffffffa0391898>] ? _nv014238rm+0xbe/0x2f0 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025676] [<ffffffffa0391b75>] ? _nv014271rm+0xab/0x174 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025709] [<ffffffffa0391c8e>] ? _nv014237rm+0x50/0x5d [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025744] [<ffffffffa0397db8>] ? _nv014212rm+0x7f0/0x928 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025773] [<ffffffffa09450f1>] ? _nv012457rm+0x174/0x55a [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025801] [<ffffffffa094506f>] ? _nv012457rm+0xf2/0x55a [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025846] [<ffffffffa03ded69>] ? _nv003965rm+0x1b3/0x1999 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.025932] [<ffffffffa071eb2b>] ? _nv003990rm+0x80ed/0xa790 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026016] [<ffffffffa071d5f6>] ? _nv003990rm+0x6bb8/0xa790 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026048] [<ffffffffa036bee5>] ? _nv009839rm+0x25/0x40 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026076] [<ffffffffa0944e03>] ? _nv014712rm+0x7c7/0x941 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026104] [<ffffffffa0945dc1>] ? _nv001084rm+0x523/0x7a2 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026132] [<ffffffffa093e87a>] ? rm_init_adapter+0xac/0x139 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026157] [<ffffffffa095e704>] ? nv_kern_open+0x4b4/0x800 [nvidia]
Jun 25 23:39:52 localhost kernel: [ 19.026161] [<ffffffff81172f5b>] ? chrdev_open+0x9b/0x1c0
Jun 25 23:39:52 localhost kernel: [ 19.026164] [<ffffffff8116c977>] ? __dentry_open+0x227/0x300
Jun 25 23:39:52 localhost kernel: [ 19.026167] [<ffffffff8117a3c0>] ? do_lookup+0x50/0x350
Jun 25 23:39:52 localhost kernel: [ 19.026170] [<ffffffff81172ec0>] ? cdev_put+0x30/0x30
Jun 25 23:39:52 localhost kernel: [ 19.026174] [<ffffffff8116dae1>] ? nameidata_to_filp+0x71/0x80
Jun 25 23:39:52 localhost kernel: [ 19.026177] [<ffffffff8117da38>] ? do_last+0x388/0x970
Jun 25 23:39:52 localhost kernel: [ 19.026180] [<ffffffff8117e23f>] ? path_openat+0xcf/0x3d0
Jun 25 23:39:52 localhost kernel: [ 19.026183] [<ffffffff8117e661>] ? do_filp_open+0x41/0xa0
Jun 25 23:39:52 localhost kernel: [ 19.026186] [<ffffffff8118adf6>] ? alloc_fd+0xd6/0x120
Jun 25 23:39:52 localhost kernel: [ 19.026189] [<ffffffff8116dbdd>] ? do_sys_open+0xed/0x1c0
Jun 25 23:39:52 localhost kernel: [ 19.026192] [<ffffffff811795a2>] ? path_put+0x22/0x30
Jun 25 23:39:52 localhost kernel: [ 19.026194] [<ffffffff8116dcd1>] ? sys_open+0x21/0x30
Jun 25 23:39:52 localhost kernel: [ 19.026198] [<ffffffff8146a8e9>] ? system_call_fastpath+0x16/0x1b
Jun 25 23:39:52 localhost kernel: [ 19.026203] ---[ end trace dd931416d0ba63ac ]---
Jun 25 23:39:52 localhost kernel: [ 19.420830] NVRM: Your system is not currently configured to drive a VGA console
Jun 25 23:39:52 localhost kernel: [ 19.420832] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Jun 25 23:39:52 localhost kernel: [ 19.420834] NVRM: requires the use of a text-mode VGA console. Use of other console
Jun 25 23:39:52 localhost kernel: [ 19.420835] NVRM: drivers including, but not limited to, vesafb, may result in
Jun 25 23:39:52 localhost kernel: [ 19.420836] NVRM: corruption and stability problems, and is not supported.

---------------------------------------------------------------

vwyodajl · 2012-06-26 21:25:10

The kernel panic I am not sure about. But the warnings below is due to Nvidia breaking VESA. You can change GRUB_GFXPAYLOAD_LINUX so that it says

 GRUB_GFXPAYLOAD_LINUX=text

then reboot and that should quiet NVRM. Note this is not a "fix" just a workaround. Nvidia claims to not know why or how VESA broke, and it always has just worked. On console you will get large text using the above command in GRUB2. You can search the MessageBoards for more info or on the forums.

HTH

Last edited by vwyodajl (2012-06-26 21:26:41)

yossarianuk · 2012-07-02 08:07:30

Thanks - i'll try that

mynis01 · 2012-07-05 20:53:15

vwyodajl wrote:

The kernel panic I am not sure about. But the warnings below is due to Nvidia breaking VESA. You can change GRUB_GFXPAYLOAD_LINUX so that it says
 GRUB_GFXPAYLOAD_LINUX=text
then reboot and that should quiet NVRM. Note this is not a "fix" just a workaround. Nvidia claims to not know why or how VESA broke, and it always has just worked. On console you will get large text using the above command in GRUB2. You can search the MessageBoards for more info or on the forums.
HTH

I believe you meant

 GRUB_GFXMODE=text

the GRUB_GFXPAYLOAD_LINUX line is used to instruct the linux kernel to keep the video mode specified in the former. I've tried every configuration known to man and the warning still pops up as long as I'm booting from UEFI. Even manually setting the resolution to 640x480 doesn't help. For now, the (hopefully) temporary solution is to just have a mbr grub installed to another drive that I can boot from when I need high levels of precision from the nvidia driver. VDPAU accelerated video, quaklive, and xonotic all work fine despite the warning as far as I can tell. The one thing that it does affect that I've noticed is high precision GPGPU stuff, like boinc/gpugrid. The other night when booting from UEFI I had a 6 hour job go south, and it had always worked fine when booting from mbr with the proper driver. The newest nvidia driver also seems to break a lot of CUDA 4.2 apps, so I just made a debian testing partition that boots without UEFI.

Edit: Apparently some people actually have made the warning go away using the method vwyodail posted. Odd, because when I do that, my machine boots up in "blind mode" and I can't see any TTY output. I can still type in my username/password and start X normally though, at which point I still have the warning.

Last edited by mynis01 (2012-07-05 21:04:23)

Meyithi · 2012-07-06 12:30:02

https://bbs.archlinux.org/viewtopic.php … 6#p1118476

yossarianuk · 2012-07-06 21:03:24

Thanks - another thing missing from the Nvidia driver......

The Nvidia driver is NOT UEFI compatible as present - FFS! ... As linus himself said " F.U Nvidia !!"

I have in the meantime decided to ger rid of UEFI - it sucks.

Last edited by yossarianuk (2012-07-06 21:07:22)

triplesquarednine · 2012-07-09 14:31:08

mynis01 wrote:

Edit: Apparently some people actually have made the warning go away using the method vwyodail posted. Odd, because when I do that, my machine boots up in "blind mode" and I can't see any TTY output. I can still type in my username/password and start X normally though, at which point I still have the warning.

For me, your method did absolutely nothing. GRUB_GFXPAYLOAD_LINUX=text did however, get rid of the message + gave me a visible console with ugly ginormous fonts (i love it...lol. seriously.)

Interestingly, this error just cropped up in the last couple of days (in dmesg). I haven't updated my nvidia blob (running 302.17, and have been since it was released), nor do i recall any other updates that seemingly would be linked to the issue. weird.

thanks for this thread and the solutions, guys!

cheerz

Arch Linux

#1 2012-06-25 23:00:41

UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#2 2012-06-26 21:25:10

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#3 2012-07-02 08:07:30

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#4 2012-07-05 20:53:15

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#5 2012-07-06 12:30:02

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#6 2012-07-06 21:03:24

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

#7 2012-07-09 14:31:08

Re: UEFI + Nvidia - error on boot + odd NVRM messages (seems fine though)

Board footer