Package: linux-2.6
Version: 2.6.29-3
Severity: wishlist

Hi kernel-team,

Please see David Miller's message below, looks like we need to remove
the PROM console driver (CONFIG_PROM_CONSOLE) in order to make the
performance acceptable on Niagara boxes. It would be great if you
could make the newly built kernel with this change available to sparc
folks before upload, so that we can make sure that it does not
introduce any regressions.

----- Forwarded message from David Miller <[email protected]> -----

Date: Thu, 23 Apr 2009 07:09:43 -0700 (PDT)
To: [email protected]
Cc: [email protected], [email protected]
Subject: debian unusable on niagara
From: David Miller <[email protected]>
X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI)
X-Mailing-List: <[email protected]> archive/latest/22353


I really didn't expect this, and then I saw other users complaining
too.

1) Please remove the PROM console driver from the kernel config, it
   does nothing but get in the way.  This will fix the "console slow
   on bootup" problem everyone reports on niagara boxes.

   Putting "console=ttyHV0" on the kernel command line works as a
   workaround but it still clears the screen once using the PROM
   console and even that takes nearly a minute (!).

2) Please fix the GETTY setup so that it properly uses ttyS0 on
   Niagara.  Otherwise people have no console and can't use their
   machine at all after installation.

   Ubuntu does this by making sure there is an /etc/event.d/ttyS0
   file with a line saying "exec /sbin/getty -L ttyS0 9600 vt102"
   or similar.

Between the ultra45 unbootable problem and these, I'm really losing
faith... :-/


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

----- End forwarded message -----

-- 
Jurij Smakov                                           [email protected]
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to