Recent changes to bugs

uvesafb refuses to work on native i586

Elmar Stellnberger (AT/K) — Mon, 12 Dec 2022 11:57:44 -0000

I am debugging/testing glx and suspend issues on an i586 computer. With the vesa driver suspend works and there are no glx problems (since it does not support glx). However it only allows for 800x600 instead of 1024x768 and no external monitor. Now I thought that a framebuffer based solution would work best on this computer. However if I want to

modprobe uvesafb
uvesafb: failed to execute /sbin/v86d
uvesafb: getting VBE info block failed (eax=0x4f00, err=-2)
uvesafb: vbe_init failed with -22

There is no sense to have an v86d on an i586 system since you would not like to emulate code that is running natively on this machine, isn´t it!
If I modprobe nouveau with modesetting there is a /dev/fb0 device. However the fbdev Xorg driver does not run with it: Xorg.log: FBIOPUT_VSCREENINFO: Invalid argument - mode initialization failed

Regarding my debugging/testing efforts you may wanna have a look at:
https://bugs.mageia.org/show_bug.cgi?id=31227

use typesafe __io on ARM

H Hartley Sweeten — Mon, 27 Apr 2009 16:40:27 -0000

Currently all the framebuffer io with ARM is not typesafe.
The __raw_{read/write} macros should be used instead of
(*(volatile u{8/16/32/64} *) for all io.

Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>

nvidiafb: Doesn't Initialize/Recognize GeForce8600GT

Anonymous — Thu, 29 May 2008 00:50:00 -0000

Please forgive me if I'm making a fool of myself. I've never submitted a bug before...

nvidiafb: Doesn't Initialize/Recognize GeForce8600GT (0x0401). All I get is:

Device ID: 10dec0401
Unknown NV_ARCH

Or something really close to that (I'm not at my computer right now).

I've attempted to edit nvidia.c to add the hex device ID in, but it still doesn't initialize the board. Additionally, I've forced a return of NV_ARCH_40, which DID attempt to initialize the board, but upon initialization, I ended up with a frozen computer displaying the normal startup messages on a green background.

Let me know what else I can do to assist.

-Oscilated
oscilated <at> hotmail <dot> com

radeonfb: no graphics, only garbage characters

Arvid — Wed, 11 Jul 2007 15:37:33 -0000

Configuring the kernel as follows (no vesafb):

Device drivers ->
Graphics support ->
<*> Support for frame buffer devices
<*> ATI Radeon display support
[*] DDC/I2C for ATI Radeon support
Console display driver support --->
< > Framebuffer Console support

and using no kernel parameters, udev loads radeonfb successfully, but it takes awhile, perhaps 10 seconds.

When using /dev/fb0 for graphics output, for example with fbi -d /dev/fb0 some_jpg.jpg, the only result is garbage characters being printed on the screen (it never enters graphics mode). The system is still responsive using fbi (ESC returns to the console), but when I try to run GTK+ on top of DirectFB the system hangs after displaying some garbage characters.

The garbage looks different depending on what is trying to get displayed on the screen.

Some system info:

$ uname -a
Linux shuttle 2.6.20-gentoo-r8 #31 Wed Jul 11 17:20:50 CEST 2007 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux

# lspci
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc R420 JI [Radeon X800PRO]
01:00.1 Display controller: ATI Technologies Inc Unknown device 4a69
02:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
02:08.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)

Arvid

radeonfb: system hang with black screen on boot

Arvid — Wed, 11 Jul 2007 13:25:26 -0000

Trying to use radeonfb gives a black screen and system hang on boot.

If "DDC/I2C for ATI Radeon support" is enabled in the kernel config, the hang occurs at the first printk called after the #ifdef CONFIG_FB_RADEON_I2C block in radeon_monitor.c (line 580).

"i2c_adapter i2c-2: unable to read EDID block." is displayed three times during execution of the block mentioned, and any subsequent call to printk gives a quick flash of the printk parameter string, and then a black screen. Alt-SysRq-b does not reboot the computer.

If "DDC/I2C for ATI Radeon support" is disabled the hang occurs at call to fb_notifier_call_chain() (fbmem.c:1328), call stack as far as I have been able to figure out is:

fb_notifier_call_chain() (declared extern in fb.h:543, called from fbmem.c:1328)
register_framebuffer() (fbmem.c:1285, declared extern in fb.h:896, called from radeon_base.c:2339)
radeonfb_pci_register() (radeon_base.c:2140)

System info:

$ uname -a
Linux shuttle 2.6.20-gentoo-r8 #6 Tue Jul 10 14:05:30 CEST 2007 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux

$ sudo lspci
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc R420 JI [Radeon X800PRO]
01:00.1 Display controller: ATI Technologies Inc Unknown device 4a69
02:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
02:08.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)

Framebuffer kernel config:
Device drivers ->
Graphics support ->
<*> Support for frame buffer devices
<*> VESA VGA Graphics support
VESA driver type (vesafb) --->
<*> ATI Radeon display support
[*] DDC/I2C for ATI Radeon support
Console display driver support --->
<*> Framebuffer Console support

Arvid

savagefb: vsync for twisterP

Mark Pustjens — Fri, 30 Jun 2006 06:42:19 -0000

This patch add support to the savagefb driver for
waiting for vsync for the TwisterP chipset.

The patch adds an ioctl FBIO_WAITFORVSYNC just like the
matroxfb driver.

The patch has only been tested with kernel 2.6.15.6 and
probably needs some work.

Please let me know what you think.

platinumfb - video display problem

Tomasz Grzegurzko — Mon, 22 May 2006 05:24:13 -0000

Hi all,

I managed to get my hands on a PowerMac 7200 and am
trying to boot. I (cross) compiled a kernel of
2.6.16.16 from a gentoo x86 box, and serially connected
the machine to view the console output results. I have
stripped out basically everything (no IDE, SCSI, USB)
except serial, framebuffer, console and ADB.

The framebuffer won't enable using the platinumfb for
the life of me when using BootX from a MacOS 7.6.1
installation on another hard drive. I've dropped a new
AHA2940 (bios flashed to OpenFirmware) SCSI card with
another attached hard drive to it (8GB of SCSI
goodness) so I can hack away at the MacOS to my hearts
content.

I have a successful installation of Debian 3.1 on this
HDD from a previously successful attempt some months
ago using the miboot boot/root install set from:
http://people.debian.org/~luther/d-i/sid/images/daily/
The daily builds I tried were 18-20 May 2006, and while
I believe the kernel has booted okay (since I can
insert the root floppy and hit enter and it does
something) I can't see anything on the screen.

I have a native mac monitor, MacOS runs at 640x480
happily. I can boot the debian/woody kernel (2.2)
series with the platinumfb driver, and zapola
everything is okay. I get screen output. I can boot off
one of my custom built 2.6.x kernels, specifying the
serial console as a the console=... parameter and sure
enough the system comes up without a hitch except that
the monitor is in 'off' mode. I have tried kernels
2.6.17-rc4, 2.6.16, 2.6.15, 2.6.14 (cross-)compiled
from sources without any luck.

Using
http://www.jonh.net/lppcfom-serve/cache/1043.html, I
have tried to give also several boot paramters
(thankfully I'm using BootX to try this stuff out now,
because trying to recreate the miboot debian floppies
would not have made for easy testing), also without
luck. Some examples of failed boots follow:
video=platinumfb
video=platinumfb:vmode:6,cmode:8
video=platinumfb:vmode:13,cmode:8
.. all with the same end result: no video.

Can I work with anyone on fixing this? It would be nice
to have some working miboots again, but unfortunately I
can't remember which daily build I downloaded when I
actually installed sarge some months ago. I *think* it
was 2.6.15, but I can't follow the same steps now
because the other modules can't be downloaded from
package repositories as sid is in 2.6.16-land now. I
have also tried the video=ofonly options when that
option is compiled in to the kernel (by the way, I am
always statically compiling the fb devices in), the
ofonlyboot image from the miboot series, also without
any joy. In my own compilations, I only ever use either
the platinumfb or the ofonly framebuffer devices
compiled in, not both at once.

-Tomasz

rivafb: PCI id for Alladin TNT2 in arch detection

Anonymous — Sat, 29 Jan 2005 13:21:02 -0000

For my Alladin TNT2 (Riva TNT2) card, i have to apply this patch to the riva_get_arch function in fbdev.c

aty128fb doesn't support 565

Michel Dänzer — Thu, 14 Jun 2001 14:02:11 -0000

Reproducible by running XFree86 4.x using fbdev in
depth 16 or with fbset -depth 16 -rgba 5650 .

I've almost fixed it, I hope I can finish it looking
at Geert's 565 patch for atyfb and will submit a
patch to the devel list on success.

riva fb broken since 2.4.1ac1...

Anonymous — Wed, 04 Apr 2001 19:12:56 -0000

hello,

i have been having a great deal of difficulty with
my Nvidia Geforce2MX (by MSI) with the fb drivers for
kernels greater than 2.4.1.

i set my vga=791 from the lilo.conf file. upon
booting, the system attempts to change to this mode,
but fails and reverts to the standard mode (80x25),
but with a tux logo at the top left. other modes
(vga=6) for example fail similarly.

the fun doesn't stop there. my machine locks up
completely if i start X, switch to tty1-6 and then try
to get back into X (tty7).

this problem doesn't happen with v2.4.1 of the
kernel. can anyone help me out here?

cheers,
twkonefal

ps. please cc: me -> twkonefal at yahoo.ca