From: Petr Baudis <pasky@ucw.cz>
To: linux-fbdev-users@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4
Date: Sun, 31 Aug 2003 16:05:53 +0200 [thread overview]
Message-ID: <20030831140553.GC5106@pasky.ji.cz> (raw)
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/
next reply other threads:[~2003-08-31 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 14:05 Petr Baudis [this message]
2003-08-31 15:40 ` Total radeonfb failure on both 2.6.0-test4 and 2.6.0-test4-mm4 Benjamin Herrenschmidt
2003-09-01 8:52 ` [Linux-fbdev-users] " Geert Uytterhoeven
2003-09-01 11:17 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030831140553.GC5106@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=linux-fbdev-users@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox