All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: boot errors in kernels 2.6.17-mm6 plus 2.6.18-rc1
Date: Fri, 07 Jul 2006 14:45:52 +0200	[thread overview]
Message-ID: <20060707124552.9650@gmx.net> (raw)

Hi Roman, hi John Stultz,
Andrew told me that you were working on that issue.

I use Debian Etch in connection with latest kernel-headers and kernels.
My system is a Pentium 4, the graphics card is an ATI Rage 128 Pro with 32 MB RAM.
When I compile both mentioned kernels, I can activate FB and FB_VESA.
But if I add „vga=791“ to menu.lst (i. e. as an additional parameter for the kernel to boot) two bugs happen:
1. The kernel takes an eternity to boot, taking about 4 long breaks to come up at all
2. the AT keyboard (atkbd.c) is not functional (i. e. I type in one letter at boot prompt and this letter is being duplicated for about 50 times

If I leave out the kernel parameter (vga=791) evrything is working fine so far without any faults.

Would you please fix this in the above mentioned kernels, so that I can use my system again with a startup screen including the small little penguin at startup?

Regards

Uwe

P. S. 1: This issue is not, as I thought first, a atkbd.c issue for Dmitry Torokhov, but a pure framebuffer issue.
P. S. 2: Is that email OK so far or should I open an entry at kernel.bugzilla?

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

             reply	other threads:[~2006-07-07 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 12:45 Uwe Bugla [this message]
2006-07-07 18:55 ` boot errors in kernels 2.6.17-mm6 plus 2.6.18-rc1 john stultz
2006-07-07 19:54   ` Andrew Morton

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=20060707124552.9650@gmx.net \
    --to=uwe.bugla@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.