linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claas Langbehn <claas@rootdir.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0: atyfb broken
Date: Tue, 30 Dec 2003 22:26:09 +0100	[thread overview]
Message-ID: <20031230212609.GA4267@rootdir.de> (raw)

Hello,

I have got an HP omnibook 4150B. When booting with atyfb,
the kernel messages look great:

atyfb: 3D RAGE Mobility (PCI) [0x4c4d rev 0x64] 8M SDRAM, 29.498928 MHz XTAL, 230 MHz PLL, 50 Mhz MCLK
fb0: ATY Mach64 frame buffer device on PCI

But either the screen is black and I see only the cursor and Background
colors (CONFIG_FRAMEBUFFER_CONSOLE disabled), but X11 starts fine.


With CONFIG_FRAMEBUFFER_CONSOLE enabled it does not work at all:
I get a completely broken picture that is not syncing and blinking and so on.
Its completely useless. X11 will not work either :(


I enabled in the kernel config:
CONFIG_FB_ATY, CONFIG_FB_ATY_CT and CONFIG_FB_ATY_XL_INIT


lspci -v:
01:00.0 VGA compatible controller: 
    ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA])
    Subsystem: Hewlett-Packard Company: Unknown device 000a
    Flags: bus master, stepping, medium devsel, latency 66, IRQ 10
    Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
    I/O ports at e800 [size=256]
    Memory at fedfe000 (32-bit, non-prefetchable) [size=4K]
    Expansion ROM at <unassigned> [disabled] [size=128K]
    Capabilities: [50] AGP version 1.0
    Capabilities: [5c] Power Management version 1

According to dmesg and to the omnibook's manual the card shall have 8 MB
memory and not 16 MB as lspci is saying.



Regards, claas

             reply	other threads:[~2003-12-30 21:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 21:26 Claas Langbehn [this message]
2003-12-31  4:06 ` 2.6.0: atyfb broken Andrew Morton
2003-12-31  4:33   ` Benjamin Herrenschmidt
2004-01-05 23:33     ` James Simmons
2004-01-05 23:44       ` Benjamin Herrenschmidt
2004-03-29 15:45       ` Benjamin Herrenschmidt
2004-03-29 15:45     ` James Simmons
2004-01-01 18:55 ` Geert Uytterhoeven
2004-01-01 21:53   ` Claas Langbehn
2004-01-02 12:44     ` Geert Uytterhoeven
2004-01-02 15:36       ` Daniël Mantione
2004-01-03 23:37         ` Claas Langbehn
2004-01-04  0:27           ` Daniël Mantione
2004-01-04  0:52             ` Claas Langbehn
2004-01-04  9:40               ` Daniël Mantione
     [not found]               ` <Pine.LNX.4.44.0401041040480.28807-402000@deadlock.et.tudelft.nl>
     [not found]                 ` <20040104110941.GA983@rootdir.de>
     [not found]                   ` <20040104121019.GB1073@rootdir.de>
2004-01-04 16:35                     ` Claas Langbehn
2004-01-05 22:32 ` James Simmons
2004-01-06 18:16   ` Ralf Hildebrandt
2004-01-07  1:01     ` James Simmons

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=20031230212609.GA4267@rootdir.de \
    --to=claas@rootdir.de \
    --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;
as well as URLs for NNTP newsgroup(s).