From: Jonathan Brown <jbrown@emergence.uk.net>
To: Peter Osterlund <petero2@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.3-rc3
Date: Sun, 15 Feb 2004 15:03:59 +0000 [thread overview]
Message-ID: <402F8A5F.5060902@emergence.uk.net> (raw)
In-Reply-To: <m2znbk4s8j.fsf@p4.localdomain>
Peter Osterlund wrote:
>>Benjamin Herrenschmidt:
>> o New radeonfb
>> o Fix a link conflict between radeonfb and the radeon DRI
>> o Fix incorrect kfree in radeonfb
>
>
> It doesn't seem to work on my x86 laptop. The screen goes black when
> the framebuffer is enabled early in the boot sequence. The machine
> boots normally anyway and I can log in from the network or log in
> blindly at the console. I can then start the X server which appears to
> work correctly, but switching back to a console still gives me a black
> screen. Running "setfont" doesn't fix it. Here is what dmesg reports
> when running 2.6.3-rc3:
I also get a black screen on boot on my IBM X31, but pressing Fn+F7 a
couple of times brings it up. Fn+F7 switches between LCD, monitor and
both. Here is my dmesg:
radeonfb: Invalid ROM signature 0 should be 0xaa55
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=144.00 Mhz,
System=144.00 MHz
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: 1024x768
radeonfb: detected LVDS panel size from BIOS: 1024x768
radeondb: BIOS provided dividers will be used
radeonfb: Power Management enabled for Mobility chipsets
radeonfb: ATI Radeon LY DDR SGRAM 16 MB
next prev parent reply other threads:[~2004-02-15 15:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 3:33 Linux 2.6.3-rc3 Linus Torvalds
2004-02-15 7:41 ` 2.6.3-rc3: twice defined symbols with new radeonfb Adrian Bunk
2004-02-15 7:47 ` Benjamin Herrenschmidt
2004-02-15 13:22 ` Adrian Bunk
2004-02-15 19:19 ` Roman Zippel
2004-02-15 9:17 ` Linux 2.6.3-rc3 Peter Osterlund
2004-02-15 9:54 ` Benjamin Herrenschmidt
2004-02-15 10:25 ` Benjamin Herrenschmidt
2004-02-15 10:51 ` Peter Osterlund
2004-02-15 11:11 ` Benjamin Herrenschmidt
2004-02-15 11:21 ` Geert Uytterhoeven
2004-02-15 10:33 ` Peter Osterlund
2004-02-15 15:03 ` Jonathan Brown [this message]
2004-02-15 16:05 ` Tomas Szepe
2004-02-15 16:44 ` Onur Kucuk
2004-02-16 15:58 ` Moritz Muehlenhoff
2004-02-17 16:29 ` Moritz Muehlenhoff
2004-02-15 19:52 ` Ernst Herzberg
2004-02-15 20:11 ` Peter Osterlund
2004-02-15 21:52 ` Ernst Herzberg
2004-02-15 22:29 ` Benjamin Herrenschmidt
[not found] ` <200402152357.25751.earny@net4u.de>
2004-02-15 23:08 ` Benjamin Herrenschmidt
[not found] ` <200402160033.43438.earny@net4u.de>
2004-02-15 23:54 ` Benjamin Herrenschmidt
2004-02-16 0:29 ` Ernst Herzberg
2004-02-16 0:38 ` Ernst Herzberg
2004-02-16 0:43 ` Benjamin Herrenschmidt
2004-02-16 1:18 ` Ernst Herzberg
2004-02-16 1:47 ` Benjamin Herrenschmidt
2004-02-16 0:41 ` Benjamin Herrenschmidt
[not found] ` <124101c3f435$9a66d3a0$1225a8c0@kittycat>
2004-02-16 2:37 ` Benjamin Herrenschmidt
2004-02-15 22:27 ` Benjamin Herrenschmidt
[not found] ` <200402160005.47892.anib@uni-paderborn.de>
2004-02-15 23:11 ` Benjamin Herrenschmidt
2004-02-16 19:18 ` Linux 2.6.3-rc3 (compile stats) John Cherry
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 6:15 Linux 2.6.3-rc3 Jonathan Brown
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=402F8A5F.5060902@emergence.uk.net \
--to=jbrown@emergence.uk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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