From: "Steven Barnhart" <sbarn03@softhome.net>
To: linux-kernel@vger.kernel.org
Subject: Re: fbcon breakage?
Date: Wed, 01 Jan 2003 23:43:50 -0500 [thread overview]
Message-ID: <pan.2003.01.02.04.43.48.195510@softhome.net> (raw)
In-Reply-To: 200301012327.18244.arodland@noln.com
On Wed, 01 Jan 2003 23:27:18 +0000, Andrew Rodland wrote:
> Hi!
>
> I'm using a Dell Latitude CPi A laptop, with a Neomagic 2200 graphics chip in
> it.
> Since earlier today, I can't get it to work with neofb; I get a really nasty
> oops early in the boot, right after neofb initialized.
> I changed more than a few things today, but I changed everything back,
> around, and in circles, and it still seems to come down to neofb.
>
> Anyway, I manually copied down the oops and ran it through ksymoops.
> Output follows.
>
> Please Cc:, as I read the list through GMANE.
>
> Thanks
> --hobbs
Excuse the off topic, hello Andrew, ltns :)
Steven
sbarn03@softhome.net
next prev parent reply other threads:[~2003-01-02 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 4:27 fbcon breakage? Andrew Rodland
2003-01-02 4:43 ` Steven Barnhart [this message]
2003-01-06 21:50 ` 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=pan.2003.01.02.04.43.48.195510@softhome.net \
--to=sbarn03@softhome.net \
--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