[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[patch] Sarge Release Notes : Kernel update and Sparc issues



Please consider the attached patches for the Release Notes for Sarge.

The first patch ("_all") warns users about an issue that they may 
encounter when upgrading from a 2.4 series kernel to a 2.6 series kernel 
because of the changes in the kernel's input layer.
Unawareness of this issue may result in a non-working keyboard after 
rebooting with the new kernel.

The second patch ("_sparc") covers two issues that are specific to new 
installations on Sparc systems.

TIA,
Frans Pop
--- release-notes.en.sgml.sv	2005-03-29 16:45:34.000000000 +0200
+++ release-notes.en.sgml	2005-04-10 14:11:42.505502473 +0200
@@ -226,7 +256,40 @@
           <p><em>No changes yet reported.</em></p>
         
         </sect1>
-        
+
+<![ %not-s390 [
+        <sect1 id="kernel_update">
+        <heading>Keyboard issues on upgrade from 2.4 to 2.6 kernels</heading>
+
+          <p>After the upgrade to Sarge, you may have 2.6 kernel images
+          available for installation. There is an important change in the
+          input layer for 2.6 kernels that you should be aware of before you
+          attempt to switch from using a 2.4 to a 2.6 kernel.</p>
+
+          <p>The change in the input layer makes all keyboards look like
+          "normal" PC keyboards. This means that if you currently have a
+          different type of keyboard selected (e.g. a USB-MAC or Sun
+          keyboard), you will very likely end up with a non-working keyboard
+          after rebooting with the new 2.6 kernel.</p>
+          
+          <p>If you can SSH into the box from another system, you can resolve
+          this issue by running 'dpkg-reconfigure console-data', choosing
+          the option "Select keymap from full list" and selecting a "pc"
+          keyboard.</p>
+
+<![ %i386 [
+          <p>This issue is unlikely to affect the &arch-title; architecture
+          as all PS/2 and most USB keyboards will already be configured as
+          a "normal" PC keyboard.</p>
+]]>
+<![ %not-i386 [
+          <p>Note that if you are using a USB keyboard, this may be configured
+          as either a "normal" PC keyboard or as a USB-MAC keyboard. In the
+          first case you will not be affected by this issue.</p>
+]]>
+        </sect1>
+]]>
+
         </sect>
         <sect id="backup"><heading>Preparing for the Upgrade</heading>
 
--- release-notes.en.sgml.sv	2005-03-29 16:45:34.000000000 +0200
+++ release-notes.en.sgml	2005-04-10 14:11:42.505502473 +0200
@@ -183,7 +183,37 @@
         <p>The old &debian; installation system called
         <prgn>boot-floppies</prgn> has been replaced by a new componentized and
         more powerful installation system called <prgn>debian-installer</prgn>.</p>
-      
+
+<![ %sparc [ 
+      <sect id="sparc_kbd"><heading>Issues with keyboards on &arch-title;</heading>
+
+        <p>There are several issues with keyboard selection during installation.</p>
+
+        <p>The first issue is with USB keyboards by Sun as used on for example
+        SunBlade systems. These are incorrectly "recognized" by the installer
+        as regular Sun keyboards. A workaround is documented in the Installation
+        Guide (see link above, chapter "Using the Debian Installer").</p>
+
+        <p>The second issue is kernel related. Kernels in the 2.6 series use
+        a different input layer that makes all keyboards look like "normal"
+        PC keyboards. This means that if you boot the installer with a 2.4
+        kernel and configure it for a Sun or USB keyboard and later (in expert
+        mode) select a 2.6 kernel for the new system, you will very likely end
+        up with a non-working keyboard after reboot.</p>
+
+      </sect>
+
+      <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
+
+        <p>Because of display problems on some systems, framebuffer support is
+        disabled by default for &arch-title;. This can result in ugly display on
+        systems that do properly support the framebuffer, like those with ATI
+        graphical cards. If you see display problems in the installer, you can try
+        booting the installer with parameter "debian-installer/framebuffer=true".</p>
+
+      </sect>
+]]>
+
       </chapt>
 
 

Attachment: pgpYwxPWOSutZ.pgp
Description: PGP signature


Reply to: