search for: nouveaufb

...bit of trouble getting it running. In particular, when I modprobe "nouveau," the display goes black (but doesn't enter power saving, so there's a signal of some sort). After doing some searching, I found http://nouveau.freedesktop.org/wiki/KernelModeSetting If I unbind the nouveaufb driver, the console starts working again. If I re-bind it, it freezes. Other than the display not showing anything, the system seems to run properly. So clearly, this seems like a handover problem. Any suggestions for things I should try? I am using plain VGA right now, which should work a...

https://bugs.freedesktop.org/show_bug.cgi?id=35133 Summary: nouveaufb messing UTF-8 characters on tty Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedeskto...

I think we had the wrong culprit: I just tried PCI-disabling the NVAC card (and keeping the NV96 one), and it just works: no garbage screen, and moreover, I get no hangs nor errors when enabling acceleration! I'll spend some time comparing both outputs (without NVAC, and without NV96) to find out what the NVAC is doing wrong. Pierre > On 31 Jan 2014, at 23:58, Ilia Mirkin <imirkin at

...dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate. # dmesg | grep -i chipset # Not true anymore I guess. What is the 'GP' in 'GP107' if 'NV...' are the code names? # dmesg | grep -i nouveau > [ 2.171473] fb: switching to nouveaufb from VESA VGA > [ 2.171595] nouveau 0000:01:00.0: NVIDIA GP107 (137000a1) > [ 2.286501] nouveau 0000:01:00.0: bios: version 86.07.39.80.5e > [ 2.287672] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5 > [ 3.573113] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB > [ 3.573114] nouve...

...eems to be the problem? I think you forgot to include a description of the issues you're seeing. On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 [ 2.816427] nouveau 0000:01:00.0: bios: OOB 1 22234d20 22234d20 [ 2.816431] nouveau 0...

...image to show up briefly, rendering the Fedora sign-in screen at something like one frame per ten seconds. But then I got all kinds of garbage, and I see: [ 719.300820] nouveau 0000:09:00.0: disp: outp 04:0006:0f44: link training failed dmesg |grep nouveau says: [ 10.053162] fb: switching to nouveaufb from EFI VGA [ 10.053349] nouveau 0000:09:00.0: NVIDIA GM206 (126010a1) [ 10.174033] nouveau 0000:09:00.0: bios: version 84.06.0d.00.01 [ 10.174854] nouveau 0000:09:00.0: disp: dcb 15 type 8 unknown [ 10.178375] nouveau 0000:09:00.0: fb: 2048 MiB GDDR5 [ 10.202108] nouveau 0000:09:00.0: D...

...en if I don't want to use nouveau under X: unless nouveau be blacklisted in /etc/modprobe.d/blacklist.conf at startup, - when using one of the VESA modes at startup after a while screen goes blank and I get a warning in syslog e.g: Apr 2 18:58:56 darkstar kernel: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver, - no problem when using a VGA mode (text only), this disregarding which X driver I use afterwards (I always start in console mode). But according to this page: http://nouveau.freedesktop.org/wiki/KernelModeSetting I thought nouveaufb shouldn't conflict w...

gp104 refuses to switch to "graphic" mode and show anything past this line: fb0: switching to nouveaufb from EFI VGA Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it normally. 5.5 is OK. 5.6 is broken. Bisecting is kinda painful with miscompilation and init/main.c breakage. BTW do I need all those megabytes of firmware? [ 0.923273] fb0: switching to nouveaufb from EFI VGA [...

...gt;> >> On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: >> >>> Hello looks like the device is not supported, the logs are as >>> follows: >>> >>> --- >>> # dmesg | grep nouve >>> [ 2.789899] fb: switching to nouveaufb from VESA VGA >>> [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) >>> [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 >>> [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 >>> [ 2.816427] nouveau 0000:01:00.0: bi...

...el.org> wrote: > On 02/01/2017 10:40 AM, Phil Turmel wrote: >> Hi All, >> >> I've been running Gentoo on a ZBook with great success for a couple years, >> but I've been stymied in my attempts to implement SecureBoot by an >> apparent problem with efifb to nouveaufb handoff, but only when external >> monitors are attached. The handoff works without issue when the BIOS is >> in Mixed EFI mode, with and without external monitors, and >> works in Native EFI mode without external monitors. > > Sorted by nouveau.config=NvForcePost=1 Bleh....

...d_hda_codec_realtek hdaudioC0D0: inputs: [ 9.369165] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 9.434609] nouveau 0000:03:00.0: DRM: MM: using M2MF for buffer copies [ 9.529103] nouveau 0000:03:00.0: DRM: allocated 1920x1080 fb: 0x50000, bo ffff8800baac3000 [ 9.529521] fbcon: nouveaufb (fb0) is primary device [ 10.595960] input: HDA NVidia Mic as /devices/pci0000:00/0000:00:08.0/sound/card0/input9 [ 10.596707] input: HDA NVidia Headphone as /devices/pci0000:00/0000:00:08.0/sound/card0/input10 [ 16.284253] Console: switching to colour frame buffer device 240x67 [ 16.287137...

.../drivers/gpu/drm/nouveau/nouveau_drm.c +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c @@ -697,7 +697,8 @@ static int nouveau_drm_probe(struct pci_dev *pdev, nvkm_device_del(&device); /* Remove conflicting drivers (vesafb, efifb etc). */ - ret = remove_conflicting_pci_framebuffers(pdev, "nouveaufb"); + if (IS_ENABLED(CONFIG_FBDEV)) + ret = remove_conflicting_pci_framebuffers(pdev, "nouveaufb"); if (ret) return ret; -- 2.26.2

Hello, Running Archlinux x86_64, kernel 3.4.9, xf86-video-nouveau-git and mesa-full No matter what I do, X freezes. Here is the kernel log as regards nouveau : [ 1.147790] [drm] nouveau 0000:01:00.0: Detected an NVc0 generation card (0x0c8000a1) [ 1.148583] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver [ 1.151874] [drm] nouveau 0000:01:00.0: Checking PRAMIN for VBIOS [ 1.251089] [drm] nouveau 0000:01:00.0: ... appears to be valid [ 1.251090] [drm] nouveau 0000:01:00.0: Using VBIOS from PRAMIN [ 1.251092] [drm] nouveau 0000:01:00.0: BIT BIOS found...

...e controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) -------------- next part -------------- [ 15.210273] nouveau 0000:00:05.0: setting latency timer to 64 [ 15.210326] [drm] nouveau 0000:00:05.0: Detected an NV40 generation card (0x04e000a2) [ 15.211087] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver [ 15.218667] [drm] nouveau 0000:00:05.0: Checking PRAMIN for VBIOS [ 15.261581] [drm] nouveau 0000:00:05.0: ... appears to be valid [ 15.261586] [drm] nouveau 0000:00:05.0: Using VBIOS from PRAMIN [ 15.261594] [drm] nouveau 0000:00:05.0: BIT BIOS found...

...mPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 -[drm] nouveau 0000:00:05.0: Load detected on output B -[drm] nouveau 0000:00:05.0: allocated 1280x1024 fb: 0x49000, bo ffff880034ea0cd8 +[drm] nouveau 0000:00:05.0: allocated 1280x1024 fb: 0x49000, bo ffff880034ea8cd8 fbcon: nouveaufb (fb0) is primary device [drm] nouveau 0000:00:05.0: Setting dpms mode 0 on vga encoder (output 0) [drm] nouveau 0000:00:05.0: Output VGA-1 is running on CRTC 0 using output B -[drm] nouveau 0000:00:05.0: Setting dpms mode 0 on TV encoder (output 2) -[drm] nouveau 0000:00:05.0: Output TV-1 is runn...

Hey! This is quick email to notify you that with 4.10-rc2 I can actually see graphic cursor in X making graphic environment usable. fb: switching to nouveaufb from EFI VGA nouveau 0000:01:00.0: NVIDIA GP104 (134000a1) nouveau 0000:01:00.0: bios: version 86.04.1e.00.01 nouveau 0000:01:00.0: fb: 8192 MiB GDDR5 nouveau 0000:01:00.0: priv: HUB0: 00d054 00000007 (1e408216) nouveau 0000:01:00.0: DRM: VRAM: 8192 MiB nouveau 0000:01:00.0: DRM: GART: 1048576 MiB...

Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 [ 2.816427] nouveau 0000:01:00.0: bios: OOB 1 22234d20 22234d20 [ 2.816431] nouveau 0...

..., while NVIDIA came up with names like G70, G72, GT215, GK104, etc. However we're mostly back to the NVIDIA way now. GP stands for the Pascal generation. (G = Generation? GeForce? Graphics? GPU? Whatever you like...) > > # dmesg | grep -i nouveau > > [ 2.171473] fb: switching to nouveaufb from VESA VGA > > [ 2.171595] nouveau 0000:01:00.0: NVIDIA GP107 (137000a1) > > [ 2.286501] nouveau 0000:01:00.0: bios: version 86.07.39.80.5e > > [ 2.287672] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5 > > [ 3.573113] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB >...

...au 0000:01:00.0: DRM: DCB conn 02: 00020246 [ 50.130985] nouveau 0000:01:00.0: DRM: DCB conn 03: 01000331 [ 50.192971] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies [ 50.484265] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x60000, bo ffff880401a4f000 [ 50.484398] fbcon: nouveaufb (fb0) is primary device [ 50.944161] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device [ 50.969789] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 My old dmesg | grep nouveau [ 0.000000] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.4.8-hardened-r1...

This changes the fb name from "nouveaufb" to "nouveaudrmfb". Aside: I wonder whether the in_interrupt() check is good enough for the nouveau acceleration. Cargo-cult says drm_can_sleep() is needed, which isn't actually working if you pick a .config without PREEMPT. For the generic fbdev defio support we've gone wit...