Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4
From: Petr Baudis (pasky_at_ucw.cz)
Date: 08/31/03
- Previous message: Dan Kegel: "Re: LMbench as gcc performance regression test?"
- Next in thread: Benjamin Herrenschmidt: "Re: Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4"
- Reply: Benjamin Herrenschmidt: "Re: Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 31 Aug 2003 16:05:53 +0200 To: linux-fbdev-users@lists.sf.net, linux-kernel@vger.kernel.org
Hello,
so I've enthusiastically tried to boot up 2.6.0-test4 even outside of UML,
however I've been hit hard by radeonfb - there're not even slighest signs of it
working. Regardless on the video mode I choose on the command line, setting the
mode fails and I end up with the display showing the BIOS POST screen (that one
with energy star logo in corner, BIOS blabbering smt about disks and so on)
covered with odd-coloured vertical lines. At the top of the screen is something
like the classic textmode stains (red dots grouped to lines; reminded me of the
days of turbopascal ;) and in the top few lines white points which actually
moved around and changed as stuff was been virtually printed onto the screen.
So it looks like the driver got the video RAM coordinates a bit wrong and it
writes stuff into a wrong place - or it forgot to move the frame to point to
where it should (or whatever, I can't say I understand the video stuff newer
than 1996 a lot ;).
I have ATI Radeon 7000 w/ 64M RAM and TV output (unused). The driver
announces itself as:
Aug 30 23:49:45 machine kernel: radeonfb_pci_register BEGIN
Aug 30 23:49:45 machine kernel: radeonfb: ref_clk=2700, ref_div=12, xclk=14300 from BIOS
Aug 30 23:49:45 machine kernel: radeonfb: probed SDR SGRAM 65536k videoram
Aug 30 23:49:45 machine kernel: radeon_get_moninfo: bios 4 scratch = 2000002
Aug 30 23:49:45 machine kernel: radeonfb: ATI Radeon VE QY SDR SGRAM 64 MB
Aug 30 23:49:45 machine kernel: radeonfb: DVI port no monitor connected
Aug 30 23:49:45 machine kernel: radeonfb: CRT port CRT monitor connected
Aug 30 23:49:45 machine kernel: radeonfb_pci_register END
If you need any further additional info, please let me know.
It appears that the 2.6 driver is essentially the old one, without Ben's
patch (which fixed framebuffer for me on 2.4). Is there a version of this
updated driver for 2.6 as well? Is there any reason why it is not integrated
yet?
Thanks in advance,
-- Petr "Pasky" Baudis . Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. -- Antoine de Saint-Exupery . Stuff: http://pasky.ji.cz/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Dan Kegel: "Re: LMbench as gcc performance regression test?"
- Next in thread: Benjamin Herrenschmidt: "Re: Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4"
- Reply: Benjamin Herrenschmidt: "Re: Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- iBook gentoo initialization problem
... I installed gentoo on my ibook 12". ... Sometimes it works fine while loading
macosx but sometimes, ... > usbcore: registered new driver usbfs ... >
radeonfb: Retrieved PLL infos from Open Firmware ... (comp.os.linux.powerpc) - radeon_force_sleep argument to radeonfb
... The Xorg driver for radeon has a problem with power management. ... options
radeonfb force_sleep=1 ... (Fedora) - framebuffer and DDC
... i have isolated an issue with the fb driver. ... i ve got a tft monitor with
both a DVI and a VGA input. ... able to use radeonfb> 640x480. ... maybe
vesafb? ... (alt.os.linux) - Re: linux 2.6.X and dri-trunk
... You can compile in more than one fb driver. ... the radeonfb driver just
won't be used. ... I get a resource busy error. ... Looks like X is not using dri
then. ... (Debian-User) - [PATCH] fbdev: Fix typo in fbmem.c
... A typo in fbmem.c prevents recognition of video= parameter. ... radeonfb
ignores the video= parameter and always run at 1400x1050 (the ... maybe this patch should
go into your hotfixes? ... +#ifndef MODULE ... (Linux-Kernel)