From: "Ameer Armaly" <ameer@charter.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: kernel 2.6.9 and framebuffer
Date: Wed, 3 Nov 2004 20:27:17 -0500 [thread overview]
Message-ID: <000a01c4c20d$6c6ca780$0200a8c0@haneyhbmu5pv2g> (raw)
In-Reply-To: <20041104002013.GA5703@tomass.dyndns.org>
Did you see a message about not beeing able to undrstand hardware address
type 801? If so, could you explain what you did to fix it?
---
Life is either tragedy or comedy.
Usually it's your choice. You can whine or you can laugh.
--Animorphs
----- Original Message -----
From: "Thomas Stivers" <stivers_t@tomass.dyndns.org>
To: "Speakup List" <speakup@braille.uwo.ca>
Sent: Wednesday, November 03, 2004 7:20 PM
Subject: kernel 2.6.9 and framebuffer
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all I just upgraded to kernel 2.6.9 in an atempt to get my wifi card
> working and for some reason I can't get the 128x48 screen by using
> vga=791 on the kernel command line. Has anyone else had these problems.?
> I have really been spoiled by all that screen real estate.
>
> I don't think I have changed anything but the kernel version and some
> networking stuf. Thanks for anything.
>
> - --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
> Thomas Stivers e-mail: stivers_t@tomass.dyndns.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
>
> iD8DBQFBiXW95JK61UXLur0RAh5+AJwMpyvG/J3le8U2onvFroNLhV7nHgCfbTkg
> hdtUFO9CGqxoAQezKX2Q2Zc=
> =B+Zz
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas Stivers
` Ameer Armaly [this message]
` Thomas Stivers
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='000a01c4c20d$6c6ca780$0200a8c0@haneyhbmu5pv2g' \
--to=ameer@charter.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).