From: "James Simmons" <jsimmons-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Administrator-fARf8FLM0JdLN7wammbJVlpr/1R2p/CL@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI and framebuffer related problems with Linux 2.6.1-rc1
Date: Mon, 29 Mar 2004 16:45:44 +0100 [thread overview]
Message-ID: <03f701c415a4$e5bcec00$d100000a@sbs2003.local> (raw)
In-Reply-To: <20040101220615.GA1804-pLH66uKTs7QSl9drg5isYP8+0UxHXcjY@public.gmane.org>
> Secondly, there also is a framebuffer related problem. I have VesaFB in kern
> and pass 'vga=791' to it at boot time. However, at the time when it switched
> to FB in previous versions of Linux, the screen by now simply stays black.
> Is this a known problem and if so is a fix available?
First try my new patch.
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
If that doesn't work send me your config file.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-29 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 22:06 ACPI and framebuffer related problems with Linux 2.6.1-rc1 Martin Loschwitz
[not found] ` <20040101220615.GA1804-pLH66uKTs7QSl9drg5isYP8+0UxHXcjY@public.gmane.org>
2004-01-02 10:29 ` Michael Guntsche
2004-01-05 23:33 ` James Simmons
2004-03-29 15:45 ` James Simmons [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-02 7:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C6E-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-02 11:32 ` Karol Kozimor
2004-01-06 3:34 Yu, Luming
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='03f701c415a4$e5bcec00$d100000a@sbs2003.local' \
--to=jsimmons-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=Administrator-fARf8FLM0JdLN7wammbJVlpr/1R2p/CL@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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