From: Andy Lutomirski <luto@myrealbox.com>
To: Jason Harrison <jharrison@linuxbs.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 blank console display
Date: Thu, 08 Apr 2004 02:04:48 -0700 [thread overview]
Message-ID: <407515B0.6070803@myrealbox.com> (raw)
In-Reply-To: <fa.jla2q0h.1ok41rf@ifi.uio.no>
I might have the same problem. I switched from 2.6.5-rc1 (I think) to 2.6.5 and
lost my console. Unfortunately I don't have the old config handy, but I'm
pretty sure I had the framebuffer console off. The only was I got my console
back was to enable fbcon. This is on x86_64 with a generic 32MB SiS card.
Any useful information I could send?
--Andy
Jason Harrison wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings,
>
> I have upgraded to 2.6.5 from 2.6.4 after which I have no console display. I
> have used my 2.6.4 .config (which worked fine) to configure 2.6.5. I have
> all the usual settings compiled into the kernel for virtual terminals and
> such to work. Is there any options at all that I might somehow be missing?
> Are there any new options I need that were introduced in 2.6.5? I really
> want to get this sorted out.
>
> Thank you all for your time and help.
>
> Regards,
> Jason Harrison
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFAc2Q/pEWPjYSBsRERAs7lAKDHBNo+q6qZlLDRaU1D0W3DWQeNMQCgjlNq
> rvwym7zPln6EOGkOIWX1x5k=
> =NZbP
> -----END PGP SIGNATURE-----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-04-08 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.jla2q0h.1ok41rf@ifi.uio.no>
2004-04-08 9:04 ` Andy Lutomirski [this message]
2004-04-07 2:15 Jason Harrison
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=407515B0.6070803@myrealbox.com \
--to=luto@myrealbox.com \
--cc=jharrison@linuxbs.dyndns.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
Powered by JetHome