From: Andreas Unterkircher <unki@netshadow.at>
To: Armin <Zoup@zoup.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: FrameBuffer Problem With 2.6.0
Date: Thu, 18 Dec 2003 10:35:26 +0100 [thread overview]
Message-ID: <1071740125.852.69.camel@winsucks> (raw)
In-Reply-To: <200312181254.23501.Zoup@zoup.org>
I had similar the same Problem... i fixed it when i also put the
compiled fonts in the kernel (vga fonts).
greetings, andi
Am Don, den 18.12.2003 schrieb Armin um 22:54:
> Hi list ,
>
> im unble to get Framebuffer ( vesa fb ) working under 2.6 on 1024x768 ( 791 ,
> 790 , 731 and ... ) my card is ati mach64 , but frame buffer for this are not
> working too ...
>
> can anyone give me some tips about it ? everything but framebuffer are working
> perfectly ! many thanks .
next prev parent reply other threads:[~2003-12-18 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 21:54 FrameBuffer Problem With 2.6.0 Armin
2003-12-18 9:35 ` Andreas Unterkircher [this message]
2003-12-19 8:29 ` Armin
2003-12-18 23:22 ` Davidlohr Bueso A.
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 12:29 Petr Vandrovec
2003-12-20 21:41 ` Zwane Mwaikambo
2003-12-20 22:54 ` Armin
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=1071740125.852.69.camel@winsucks \
--to=unki@netshadow.at \
--cc=Zoup@zoup.org \
--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