Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
EFI/NVidia won't work with proprietary or nouveau
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 2:48 pm    Post subject: EFI/NVidia won't work with proprietary or nouveau Reply with quote

Hi!

I've tried just about every permutation I can imagine but I can't get X started when using either the nvidia proprietary driver nor with the nouveau driver.

stable amd64
Kernel 3.16.5
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) (prog-if 00 [VGA controller])

From what I've read, I believe the problem may be caused by the fact I am booting my kernel directly from the EFI firmware, without grub or any other bootloader.

In this case, there (apparently) is no VGA text-mode console created and this appears to cause problems with both drivers.

I CAN get X started when using the uvesa driver but there is no acceleration.

Does anyone know how to get around this problem?
Are there others using EFI-direct kernel booting that have gotten this to work?

Thanks
Back to top
View user's profile Send private message
peter4
Guru
Guru


Joined: 19 Jul 2005
Posts: 359
Location: Wroclaw, Poland

PostPosted: Wed Dec 31, 2014 4:02 pm    Post subject: Reply with quote

I have a 660Ti, I'm booting directly from EFI and I have no problem with the binary driver. My kernel config: http://pastebin.com/n8Z9dWPh
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 7:14 pm    Post subject: Reply with quote

Our kernels are practically the same, accounting for the different versions (3.16.5 and 3.18.1) and hardware.

Whichever driver I attempt to set up, it fails.

Nouveau:

Quote:
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (II) NOUVEAU driver
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (II) NOUVEAU driver for NVIDIA chipset families :
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: RIVA TNT (NV04)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: RIVA TNT2 (NV05)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 256 (NV10)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 2 (NV11, NV15)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 4MX (NV17, NV18)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 3 (NV20)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 4Ti (NV25, NV28)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce FX (NV3x)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 6 (NV4x)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 7 (G7x)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce 8 (G8x)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce GTX 200 (NVA0)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: GeForce GTX 400 (NVC0)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (++) using VT number 7
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE) [drm] KMS not enabled
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE) No devices detected.
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: Fatal server error:
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE) no screens found(EE)
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE)


The NVidia driver complains about there not being a VGA console.

My kernel config
http://pastebin.com/7BGuSPjb
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Wed Dec 31, 2014 7:36 pm    Post subject: Reply with quote

Progman3K,

Code:
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE) [drm] KMS not enabled

Tells that the Xorg nouveau driver loaded but could not find its kernel counterpart. Thats also called nouveau and you need both parts.

The nVidia binary blob does not require a VGA text console. vesafb works too.
The bottow line is that any console other that VGA is not supported. Most framebuffer drivers will prevent the blob from starting as they both try to setup the hardware.
Two drivers one piece oy hardware usually ends in tears.

Lastly, you cannot configure the kernel to support nouveau and nvidia-dgivers at the same time.

Pick one and post back.
_________________
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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 7:53 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Progman3K,

Code:
Dec 31 12:50:29 localhost gdm-Xorg-:5[274]: (EE) [drm] KMS not enabled

Tells that the Xorg nouveau driver loaded but could not find its kernel counterpart. Thats also called nouveau and you need both parts.


If I enable the Nouveau kernel module
CONFIG_DRM_NOUVEAU=y
Then the computer locks up upon loading the kernel.
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 8:06 pm    Post subject: Reply with quote

Oops, wait,

The machine DOESN'T lock up, it merely appears to be frozen for much longer than its usual boot-time...

When using the uvesa driver, from the moment the kernel loads until the desktop appears takes about 3 seconds.

When using Nouveau and enabling its kernel-mode, the display never shows anything and I cannot ssh into the box for a minute or so, but then I CAN.

Related question: How do I get the journalctl to NOT use the pager? I'd like to paste the boot-output here but invoking journalctl always starts less to view the events...

EDIT: It's journalctl --no-pager

Here's my boot sequence WITH the Nouveau kernel driver in place:

http://pastebin.com/Jc2fnHTJ
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6194

PostPosted: Wed Dec 31, 2014 10:10 pm    Post subject: Reply with quote

To deal with the potentially easier to fix case: for nouveau, are both CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_EFI_FB set ?
The later is one of those rare few that shouldn't interfere with KMS.
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 10:40 pm    Post subject: Reply with quote

VoidMage wrote:
To deal with the potentially easier to fix case: for nouveau, are both CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_EFI_FB set ?
The later is one of those rare few that shouldn't interfere with KMS.


Yes CONFIG_FRAMEBUFFER_CONSOLE is set but
I had CONFIG_FB_VESA set and CONFIG_FB_EFI was NOT set.

With the recommended changes:

CONFIG_FRAMEBUFFER_CONSOLE=y
#CONFIG_FB_VESA=not set
CONFIG_FB_EFI=y

there are kernel messages written on the screen during boot, which end in
Fb: switching to nouveaufb from EFI VGA

Then the machine apparently hangs but If I wait a minute or so, I can SSH to it. Here's the log output
http://pastebin.com/Qh3xXFjg

The relevant portions: (tried to remove lines that did not have anything to do with video)

Dec 31 17:28:59 localhost kernel: efifb: probing for efifb
Dec 31 17:28:59 localhost kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90007600000, using 8100k, total 8100k
Dec 31 17:28:59 localhost kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
Dec 31 17:28:59 localhost kernel: efifb: scrolling: redraw
Dec 31 17:28:59 localhost kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Dec 31 17:28:59 localhost kernel: Console: switching to colour frame buffer device 240x67
Dec 31 17:28:59 localhost kernel: fb0: EFI VGA frame buffer device
Dec 31 17:28:59 localhost kernel: [drm] Initialized drm 1.1.0 20060810
Dec 31 17:28:59 localhost kernel: checking generic (f1000000 7e9000) vs hw (e0000000 10000000)
Dec 31 17:28:59 localhost kernel: checking generic (f1000000 7e9000) vs hw (f0000000 2000000)
Dec 31 17:28:59 localhost kernel: fb: switching to nouveaufb from EFI VGA
Dec 31 17:28:59 localhost kernel: Console: switching to colour dummy device 80x25
Dec 31 17:28:59 localhost kernel: nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x117000a2
Dec 31 17:28:59 localhost kernel: nouveau [ DEVICE][0000:01:00.0] Chipset: GM107 (NV117)
Dec 31 17:28:59 localhost kernel: nouveau [ DEVICE][0000:01:00.0] Family : NV110
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] checking PROM for image...
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] using image from PROM
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] BIT signature found
Dec 31 17:28:59 localhost kernel: nouveau [ VBIOS][0000:01:00.0] version 82.07.32.40.69
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: irq 41 for MSI/MSI-X
Dec 31 17:28:59 localhost kernel: nouveau [ PMC][0000:01:00.0] MSI interrupts enabled
Dec 31 17:28:59 localhost kernel: nouveau [ PFB][0000:01:00.0] RAM type: GDDR5
Dec 31 17:28:59 localhost kernel: nouveau [ PFB][0000:01:00.0] RAM size: 2048 MiB
Dec 31 17:28:59 localhost kernel: nouveau [ PFB][0000:01:00.0] ZCOMP: 0 tags
Dec 31 17:28:59 localhost kernel: nouveau [ CLK][0000:01:00.0] 07: core 405 MHz memory 810 MHz
Dec 31 17:28:59 localhost kernel: nouveau [ CLK][0000:01:00.0] 0f: core 270-1306 MHz memory 5400 MHz
Dec 31 17:28:59 localhost kernel: nouveau [ CLK][0000:01:00.0] --: core 405 MHz memory 810 MHz
Dec 31 17:28:59 localhost kernel: nouveau [ PGRAPH][0000:01:00.0] using external firmware
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Dec 31 17:28:59 localhost kernel: nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
Dec 31 17:28:59 localhost kernel: nouveau E[ DEVICE][0000:01:00.0] failed to create 0x18000717, -22
Dec 31 17:28:59 localhost kernel: nouveau E[ DRM] failed to create 0x80000080, -22
Dec 31 17:28:59 localhost kernel: nouveau: probe of 0000:01:00.0 failed with error -22

Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (II) NOUVEAU driver
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (II) NOUVEAU driver for NVIDIA chipset families :
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: RIVA TNT (NV04)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: RIVA TNT2 (NV05)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 256 (NV10)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 2 (NV11, NV15)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 4MX (NV17, NV18)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 3 (NV20)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 4Ti (NV25, NV28)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce FX (NV3x)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 6 (NV4x)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 7 (G7x)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce 8 (G8x)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce GTX 200 (NVA0)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: GeForce GTX 400 (NVC0)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (++) using VT number 7
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) [drm] KMS not enabled
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) No devices detected.
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE)
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: Fatal server error:
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) no screens found(EE)
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 11:22 pm    Post subject: Reply with quote

Maybe it's the kernel version I am using. Will try a more recent one...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Wed Dec 31, 2014 11:27 pm    Post subject: Reply with quote

Progman3K,

Its not the kernel version, its kernel nouveau support.
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) [drm] KMS not enabled.

Direct firmware load failed means taht you need linux-firmware to provide the firmware for the card.
_________________
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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 11:42 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Progman3K,

Its not the kernel version, its kernel nouveau support.
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) [drm] KMS not enabled.

Direct firmware load failed means taht you need linux-firmware to provide the firmware for the card.


OK, I emerged linux-firmware and rebooted but still no change.

Something may be preventing the firmware from loading but I don't think it was the fact that linux-firmware was not installed, otherwise the nouveau X driver maintainer would have put a dependency there, I believe.

I believe I might be encountering this bug
http://lists.freedesktop.org/archives/nouveau/2014-September/018681.html

Which can cause this problem when two displays are present.

I do not currently have two displays connected to the graphics card but it IS a model that supports having two video display connected to it.
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Wed Dec 31, 2014 11:50 pm    Post subject: Reply with quote

Also, the file /etc/portage/savedconfig/sys-kernel/linux-firmware-20140902
installed by linux-firmware does not mention nouveau at all
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 12:19 am    Post subject: Reply with quote

Hmm... Nope, the reported bug apparently doesn't have anything to do with this.
Makes sense because the nvidia-proprietary driver behaves the same way.

I'm stuck. I guess trying a more recent kernel that was reported to work by peter4 is the thing to try.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jan 01, 2015 12:26 am    Post subject: Reply with quote

Progman3K,

NeddySeagoon wrote:
Progman3K,

Its not the kernel version, its kernel nouveau support.
Dec 31 17:28:59 localhost gdm-Xorg-:5[273]: (EE) [drm] KMS not enabled.


If you still get that error you still have
Code:
  │ │     <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)  --->  │ │ 
  │ │         I2C encoder or helper chips  --->                                      │ │ 
  │ │     < > PTN3460 DP/LVDS bridge                                                 │ │ 
  │ │     < > 3dfx Banshee/Voodoo3+                                                  │ │ 
  │ │     < > ATI Rage 128                                                           │ │ 
  │ │     < > ATI Radeon                                                             │ │ 
  │ │     <*> Nouveau (NVIDIA) cards   
missing from your running kernel.

Nouveau provides a free framebuffer, so all other framebuffer drivers must be off.
_________________
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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 1:43 am    Post subject: Reply with quote

With the EFI_FB unset, booting gives no output at all but I can still log into the box after waiting for a minute or so.

Here's the config

Code:
zcat /proc/config.gz |grep _FB
Quote:
CONFIG_DRM_KMS_FB_HELPER=y
CONFIG_FB=y
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y

# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_AUO_K190X is not set
# CONFIG_FB_SIMPLE is not set
and
Code:
zcat /proc/config.gz |grep NOUVEAU
Quote:
CONFIG_DRM_NOUVEAU=y
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y


I'm certain the Nouveau kernel framebuffer driver (and no other) is present, the error messages above seem to bear this out

but something is making the kernel driver initialization abend.
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6194

PostPosted: Thu Jan 01, 2015 1:39 pm    Post subject: Reply with quote

First of all, leave CONFIG_FB_EFI on - it's almost certainly not the source of the problem. That way, you'll at least see the early boot.
Now,
Quote:
Code:
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2


this, combined with the long boot delay, sounds like the standard timeout problem due to missing firmware, combined with KMS not working without that firmware.

So, obviously, you need to check which firmware files are missing and install them where kernel expects them.
Quote:
Code:
Dec 31 17:28:59 localhost kernel: nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c

That's most likely the name of the missing firmware.


Last edited by VoidMage on Thu Jan 01, 2015 1:59 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jan 01, 2015 1:57 pm    Post subject: Reply with quote

Progman3K,

As you have CONFIG_DRM_NOUVEAU=y, the corresponddng firmware needs to be in the kernel too.
The firmware in /lib/firmware is on the root filesystem, which is not yet mounted.
Code:
Dec 31 17:28:59 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
is no longer helpful.
That used to be udev but firmware loading functionality was removed some time ago.

dmesg normally tells the firmware file name it failed to load too.

This page is worth reading.
_________________
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
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6194

PostPosted: Thu Jan 01, 2015 2:04 pm    Post subject: Reply with quote

NeddySeagoon wrote:
As you have CONFIG_DRM_NOUVEAU=y, the corresponddng firmware needs to be in the kernel too.

Right - missed that. So, either the above or switch that to a module, then firmware should get properly loaded too.
Back to top
View user's profile Send private message
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 11:05 pm    Post subject: Reply with quote

Building Nouveau as a module and setting EFI_FB make the boot display proceed farther.

It isn't a problem of the root filesystem not being mounted yet though because looking in the journal, first I see

[...]
Jan 01 17:13:00 localhost systemd-fsck[120]: /dev/sda2: clean, 682558/27181056 files, 5474450/108723456 blocks
[...]
Jan 01 17:13:00 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
[...]
Jan 01 17:13:00 localhost kernel: EXT4-fs (sda2): re-mounted. Opts: (null)

and later still
[...]
Jan 01 17:13:01 localhost kernel: fb: switching to nouveaufb from EFI VGA
Jan 01 17:13:01 localhost kernel: Console: switching to colour dummy device 80x25
Jan 01 17:13:01 localhost kernel: nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x117000a2
Jan 01 17:13:01 localhost kernel: nouveau [ DEVICE][0000:01:00.0] Chipset: GM107 (NV117)
Jan 01 17:13:01 localhost kernel: nouveau [ DEVICE][0000:01:00.0] Family : NV110
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] checking PROM for image...
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] using image from PROM
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] BIT signature found
Jan 01 17:13:01 localhost kernel: nouveau [ VBIOS][0000:01:00.0] version 82.07.32.40.69
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: irq 45 for MSI/MSI-X
Jan 01 17:13:01 localhost kernel: nouveau [ PMC][0000:01:00.0] MSI interrupts enabled
Jan 01 17:13:01 localhost kernel: nouveau [ PFB][0000:01:00.0] RAM type: GDDR5
Jan 01 17:13:01 localhost kernel: nouveau [ PFB][0000:01:00.0] RAM size: 2048 MiB
Jan 01 17:13:01 localhost kernel: nouveau [ PFB][0000:01:00.0] ZCOMP: 0 tags
Jan 01 17:13:01 localhost kernel: nouveau [ CLK][0000:01:00.0] 07: core 405 MHz memory 810 MHz
Jan 01 17:13:01 localhost kernel: nouveau [ CLK][0000:01:00.0] 0f: core 270-1306 MHz memory 5400 MHz
Jan 01 17:13:01 localhost kernel: nouveau [ CLK][0000:01:00.0] --: core 405 MHz memory 810 MHz
Jan 01 17:13:01 localhost kernel: nouveau [ PGRAPH][0000:01:00.0] using external firmware
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Jan 01 17:13:01 localhost kernel: nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
Jan 01 17:13:01 localhost kernel: nouveau E[ DEVICE][0000:01:00.0] failed to create 0x18000717, -22
Jan 01 17:13:01 localhost kernel: nouveau E[ DRM] failed to create 0x80000080, -22
Jan 01 17:13:01 localhost kernel: nouveau: probe of 0000:01:00.0 failed with error -22

The major difference being that if EFI_FB is enabled, the
Jan 01 17:13:01 localhost kernel: fb: switching to nouveaufb from EFI VGA
message appears later, after more messages appear on the console.

Also, even if the console seems to display properly, I can never log in by tty0, anything I do must be done over ssh.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jan 01, 2015 11:17 pm    Post subject: Reply with quote

Progman3K,

Code:
Jan 01 17:13:01 localhost kernel: nouveau [ PGRAPH][0000:01:00.0] using external firmware
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
but still no firmware.

Did you read the link in my last post?
Particularly under the heading 3D-accel Firmware

Not logging in is probably not related.
_________________
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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 11:25 pm    Post subject: Reply with quote

I changed the debug-tracing levels in the Nouveau driver to 7, which is the maximum, hoping for some additional insight.

Unfortunately, this only appears to dump register values during the module's init phase and ends with the same cryptic error -22 message, so no help there.

In case anyone would like to take a look, here it is:

http://pastebin.com/fZWLG1Na
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jan 01, 2015 11:31 pm    Post subject: Reply with quote

Progman3K,

Read this page and try the instructions related to Gentoo.

Tell us the PIC Vendor and Device ID of your video card too. lspci -k will do.
lspci -k :
01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)
   Subsystem: ZOTAC International (MCO) Ltd. Device 4056
   Kernel driver in use: nouveau

_________________
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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 11:31 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Progman3K,

Code:
Jan 01 17:13:01 localhost kernel: nouveau [ PGRAPH][0000:01:00.0] using external firmware
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Direct firmware load failed with error -2
Jan 01 17:13:01 localhost kernel: nouveau 0000:01:00.0: Falling back to user helper
but still no firmware.

Did you read the link in my last post?
Particularly under the heading 3D-accel Firmware


Yes, following the recommendation in the guide you provided, I tried building the driver as a module first to see if I could avoid having to perform extra steps of getting it packaged into the initramfs.
Seeing as how that does not work, I will try the alternative method.

Which is odd because I have a second computer with a traditional BIOS/MBR combo that is up to date and using the Nouveau driver, built-in to the kernel, without any problems.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jan 01, 2015 11:37 pm    Post subject: Reply with quote

Progman3K,

We have managed to cross post. Your dmesg says the system you are working on now needs external firmware.
The page I linked to first, says it has to be taken from the nvidia-drivers package and describes how to do it.
The link above gives you an emerge command.

However, depending on your chipset, you still may need to do it the hard way.

Not all cards need external firmware. My 6 year old GeForce 9800 GT is fine without it.
I suspect thats why your other system does not need firmware for nouveau 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
Progman3K
l33t
l33t


Joined: 03 Jan 2004
Posts: 665

PostPosted: Thu Jan 01, 2015 11:37 pm    Post subject: Reply with quote

According to the Nouveau guide, the first thing to try is to set
CONFIG_FIRMWARE_IN_KERNEL=y
in the kernel config.

This is already set in the kernel config I am using, so that method does not seem to work.
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
Goto page 1, 2  Next
Page 1 of 2

 
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