From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: x86_64 64bit kernel rivafb broke between 2.6.8.1 and linus bk as of today
Date: Wed, 17 Nov 2004 00:01:47 +0000 [thread overview]
Message-ID: <200411170001.47327.andrew@walrond.org> (raw)
In-Reply-To: <200411162244.37709.andrew@walrond.org>
x>
> I just upgraded my kernel to linus latest bk head, booting with a built in
> rivafb as usual, but I get a corrupted display.
>
> 2.6.8.1 worked just fine.
>
> The two pengiun logos seem fine (but ontop of garbage), but the text is
> totally screwed and spread all over the screen in little chunks
>
> Before I start hunting down the problem, has anybody got any ideas/fixes?
>
> This is a 64bit kernel on a dual opteron system.
>
2.6.8.1 through to 2.6.10-rc1 work fine
2.6.10-rc2 is broken
I'll do some more digging tomorrow unless somebody knows what's up.
Andrew
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-17 0:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 22:44 x86_64 64bit kernel rivafb broke between 2.6.8.1 and linus bk as of today Andrew Walrond
2004-11-16 23:29 ` Andrew Walrond
2004-11-17 0:01 ` Andrew Walrond [this message]
2004-11-17 0:15 ` Antonino A. Daplas
2004-11-17 0:33 ` Andrew Walrond
2004-11-17 11:07 ` Andrew Walrond
2004-11-17 11:11 ` Geert Uytterhoeven
2004-11-17 11:34 ` Andrew Walrond
2004-11-17 22:23 ` Antonino A. Daplas
2004-11-17 22:28 ` Antonino A. Daplas
2004-11-17 22:50 ` Andrew Walrond
2004-11-18 0:02 ` Antonino A. Daplas
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=200411170001.47327.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.