search for: fb0

...d, how do you change the terminal resolution problem seems solved via boot param). The old way(that I used) was to just wrap whatever in fbterm, but fbterm is missing. I can compile and package and install it no problem, but apparently there's no longer a framebuffer for it to attach to - /dev/fb0 is gone - so it can't actually run. There doesn't appear to be anything that would create /dev/fb0 either - It looks like nothing was compiled into the default kernel. The vga16fb module is available if you install a xen kernel from centos-xen, but it's 16 colors. vmwgfx doesn't s...

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 nouv...

...down some stability issues with my Xen system, and in the course of doing so, I''ve found a few things that are probably unrelated, but things I''d like to clean up nonetheless. I have a Xen guest instance running my Xen0 kernel. When it boots I get: Jul 29 01:31:37 loki kernel: fb0: VGA16 VGA frame buffer device Jul 29 01:31:37 loki kernel: c48c9dd3 Jul 29 01:31:37 loki kernel: [<c01b6ddc>] take_over_console+0x63/0x389 Jul 29 01:31:37 loki kernel: [<c48c92f4>] fbcon_takeover+0x5c/0x8a [fbcon] Jul 29 01:31:37 loki kernel: [<c4853231>] init_module+0x56/0x5a...

...?? ? ? > ??/sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/drm/card0/card0-VGA-1 > ?? ???? ? ??? [MASTER] drm:card0-VGA-1 > ??/sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/drm/renderD128 > ?? ???? ? ? drm:renderD128 > ??/sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/graphics/fb0 > ?? ???? ? ? graphics:fb0 "nouveaudrmfb" > > So it will be: > > loginctl attach seat1 /sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/drm/card0/card0-VGA-1 > > For the seat1 (the VGA d-sub output for seat1 and the other HDMI output for > seat0) and of course...

...onvergence integrated media GmbH (c) 2002-2004 convergence GmbH ----------------------------------------------------------- (*) DirectFB/Core: Single Application Core. (2006-10-17 10:09) (*) Direct/Memcpy: Using MMX optimized memcpy() (!) Direct/Util: opening ''/dev/fb0'' failed --> No such device (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize ''system'' core! --> Initialization er...

Een ingesloten tekst met niet-gespecificeerde tekenset is van het bericht gescrubt ... Naam: niet beschikbaar Url: https://stat.ethz.ch/pipermail/r-help/attachments/20071029/b29e9bd5/attachment.pl

Hi, my test box won't boot 5.8-rc1 all the way but stops at ... fb0: switching to nouveaufb from EFI VGA <-- EOF I've bisected it to the commit in $Subject, see below. Unfortunately, it doesn't revert cleanly so I can't really do the final test of reverting it ontop of 5.8-rc1 to confirm that this one is really causing it. Any ideas? GPU is: [...

...f8801b6e81c0c c6 kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900229b2118 c6 kernel: radeon 0000:00:01.0: radeon: using MSI. c6 kernel: [drm] radeon: irq initialized. c6 kernel: [drm] Radeon Display Connectors c6 kernel: fbcon: radeondrmfb (fb0) is primary device c6 kernel: radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device c6 kernel: radeon 0000:00:01.0: registered panic notifier c6 kernel: [drm] Initialized radeon 2.37.0 20080528 for 0000:00:01.0 on minor 0 c6 kernel: powernow-k8: Found 1 AMD A6-3600 APU with Radeon(tm) HD Graphi...

...44431] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies > [ 3.983733] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 122124 [ IBUS ] > [ 4.091733] nouveau 0000:01:00.0: DRM: allocated 1920x1200 fb: 0x200000, bo (____ptrval____) > [ 4.160682] fbcon: nouveaufb (fb0) is primary device > [ 4.160758] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device > [ 4.192044] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 # tail /var/log/Xorg.0.log > [ 2798.820] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage > [ 27...

Ilia Mirkin wrote: > I suspect the fb0 issue is because you disabled > CONFIG_DRM_FBDEV_EMULATION? Does the freeze also happen with 4.3? Any > chance you could bisect? I saw this config option, but I didn't realize that. The issue also occurs with 4.3. I even tried 4.3-rc1 with the same results. Would the DRM_FBDEV_EMULATIO...

...ice_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [ 2.899146] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies [ 2.947414] nouveau 0000:01:00.0: DRM: allocated 1366x768 fb: 0x70000, bo ffff98488129b800 [ 2.948762] fbcon: nouveaufb (fb0) is primary device [ 2.948872] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device [ 2.996667] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 [ 49.592176] nouveau 0000:01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2 [ 49.592197] nouvea...

..._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] nou...

...Y for buffer copies [ 10.478561] nouveau 0000:09:00.0: priv: GPC0: 419df4 00000000 (1e40820e) [ 10.478578] nouveau 0000:09:00.0: priv: GPC1: 419df4 00000000 (1e40820e) [ 10.607100] nouveau 0000:09:00.0: DRM: allocated 3840x2160 fb: 0x60000, bo ffff88044aad7400 [ 10.607276] fbcon: nouveaufb (fb0) is primary device [ 10.607576] nouveau 0000:09:00.0: fb0: nouveaufb frame buffer device [ 10.617064] [drm] Initialized nouveau 1.3.1 20120801 for 0000:09:00.0 on minor 0 [ 719.282184] nouveau 0000:09:00.0: disp: outp 04:0006:0f44: link training failed [ 719.300820] nouveau 0000:09:00.0: disp...

...le difference between the old open-coded logic and the helper, they were supposed to be identical. Cheers, -ilia On Thu, Jun 18, 2020 at 4:09 PM Borislav Petkov <bp at alien8.de> wrote: > > Hi, > > my test box won't boot 5.8-rc1 all the way but stops at > > ... > fb0: switching to nouveaufb from EFI VGA > <-- EOF > > I've bisected it to the commit in $Subject, see below. Unfortunately, it > doesn't revert cleanly so I can't really do the final test of reverting > it ontop of 5.8-rc1 to confirm that this one is really causing it. &g...

...RM: DCB conn 03: 01000331 [ 1.126100] nouveau 0000:05:00.0: DRM: failed to create kernel channel, -22 [ 1.126364] nouveau 0000:05:00.0: DRM: MM: using COPY for buffer copies [ 1.481589] nouveau 0000:05:00.0: DRM: allocated 1680x1050 fb: 0x200000, bo (____ptrval____) [ 1.481807] fbcon: nouveaudrmfb (fb0) is primary device [ 1.672191] nouveau 0000:05:00.0: fb0: nouveaudrmfb frame buffer device [ 1.672362] [drm] Initialized nouveau 1.3.1 20120801 for 0000:05:00.0 on minor 1 Kernel Config is attached. Looking forward to any help or reply. I went back to version 5.5 of the Kernel (recompiled after...

...ic 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 running o...

Does NOUVEAU support mmaping a double-sized Framebuffer? When attempting to run, where fd refers to "/dev/fb0": mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); I get back an invalid argument error. This doesn't happen if I only request a single screensize. Is this a limitation of the driver? -------------- next part -------------- An HTML attachment was scrubbed... URL:...

...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 root=...

Please keep me in the CC. I am not subscribed to this list. When booting 4.4.0 on one of my systems, when nouveau loads, the screen goes into powersave. It doesn't appear to register the fb0 device. When X starts up, the screen comes back and I'm able to login. When launching anything that accesses 3D, the screen freezes. Nothing is logged in either X or dmesg. This same system works with 4.2.6. I understand that the version in 4.3 was a rewrite. System: Gigabyte EP45-DS3R, NV...

...mon_device_register_with_info(). >>> [ 2.899146] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer >>> copies >>> [ 2.947414] nouveau 0000:01:00.0: DRM: allocated 1366x768 fb: >>> 0x70000, bo ffff98488129b800 >>> [ 2.948762] fbcon: nouveaufb (fb0) is primary device >>> [ 2.948872] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer >>> device >>> [ 2.996667] [drm] Initialized nouveau 1.3.1 20120801 for >>> 0000:01:00.0 on minor 0 >>> [ 49.592176] nouveau 0000:01:00.0: Direct firmware load f...