mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Linux 2.6.3-rc3
Date: 15 Feb 2004 10:17:00 +0100	[thread overview]
Message-ID: <m2znbk4s8j.fsf@p4.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0402141931050.14025@home.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

> 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:

    $ cat 263r3.dmesg | egrep -A 1 'Console:|radeon'
    Console: colour VGA+ 80x25
    Memory: 254460k/261632k available (2532k kernel code, 6388k reserved, 879k data, 148k init, 0k highmem)
    --
    radeonfb: Invalid ROM signature 0 should be 0xaa55
    radeonfb: Retreived PLL infos from BIOS
    radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=250.00 Mhz, System=183.00 MHz
    Non-DDC laptop panel detected
    radeonfb: Monitor 1 type LCD found
    radeonfb: Monitor 2 type no found
    radeonfb: panel ID string: Samsung LTN150P1-L02    
    radeonfb: detected LVDS panel size from BIOS: 1400x1050
    radeondb: BIOS provided dividers will be used
    radeonfb: Power Management enabled for Mobility chipsets
    radeonfb: ATI Radeon LW  DDR SGRAM 64 MB
    SBF: Simple Boot Flag extension found and enabled.
    --
    Console: switching to colour frame buffer device 175x65
    pty: 1024 Unix98 ptys configured
    --
    Console: switching to colour frame buffer device 175x65
    input: PC Speaker

The same configuration works correctly using 2.6.3-rc2 and dmesg
reports:

    $ cat 263r2.dmesg | egrep -A 1 'Console:|radeon'
    Console: colour VGA+ 80x25
    Memory: 254544k/261632k available (2457k kernel code, 6304k reserved, 878k data, 144k init, 0k highmem)
    --
    radeonfb_pci_register BEGIN
    radeonfb: ref_clk=2700, ref_div=12, xclk=18300 from BIOS
    radeonfb: probed DDR SGRAM 65536k videoram
    radeon_get_moninfo: bios 4 scratch = 1000004
    radeonfb: panel ID string: Samsung LTN150P1-L02    
    radeonfb: detected DFP panel size from BIOS: 1400x1050
    radeonfb: ATI Radeon M7 LW DDR SGRAM 64 MB
    radeonfb: DVI port LCD monitor connected
    radeonfb: CRT port no monitor connected
    radeonfb_pci_register END
    SBF: Simple Boot Flag extension found and enabled.
    --
    Console: switching to colour frame buffer device 175x65
    pty: 1024 Unix98 ptys configured
    --
    Console: switching to colour frame buffer device 175x65
    input: PC Speaker

The FB related parts of my .config look like this:

    $ cat .config | egrep '_FB_|_CONSOLE|_FONT|_VIDEO' | egrep -v '^#'
    CONFIG_VT_CONSOLE=y
    CONFIG_HW_CONSOLE=y
    CONFIG_VIDEO_DEV=m
    CONFIG_VIDEO_SELECT=y
    CONFIG_FB_RADEON=y
    CONFIG_VGA_CONSOLE=y
    CONFIG_DUMMY_CONSOLE=y
    CONFIG_FRAMEBUFFER_CONSOLE=y
    CONFIG_PCI_CONSOLE=y
    CONFIG_FONT_8x8=y
    CONFIG_FONT_8x16=y

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

  parent reply	other threads:[~2004-02-15  9:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15  3:33 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 ` Peter Osterlund [this message]
2004-02-15  9:54   ` Linux 2.6.3-rc3 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
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
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=m2znbk4s8j.fsf@p4.localdomain \
    --to=petero2@telia.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®