[ tilbage ] [ Indhold ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ A ] [ næste ]


Udgivelsesbemærkninger for Debian GNU/Linux 3.1 (`sarge'), Intel x86
Kapitel 5 - Kendte problemer med sarge


5.1 Ændringer i Pythonpakker

Ingen af de python2.x-pakker, der er i sarge, indeholder standardmodulerne 'profile' og 'pstats', da de hører under en licens, der ikke overholder DFSG (se Debian-fejl #293932 for detaljerne). Disse to moduler ligger i pakkerne python-profiler og python2.X-profiler i non-free-delen af Debianarkivet.


5.2 Opgradering til en 2.6-kerne

2.6-kernefamilien indeholder nogle større ændringer i forhold til 2.4-familien. Mange af modulerne har fået nye navne og mange drivere er enten helt eller delvist omskrevne. Opgradering til en 2.6-kerne fra en tidligere version er derfor ikke altid helt ligetil. Dette afsnit vil gøre dig opmærksom på nogle af de problemer, du kan komme ud for.

Du anbefales derfor kraftigt til ikke at opgradere til en 2.6-kerne samtidig med opgraderingen fra woody til sarge. I stedet bør du sikre dig at systemet fungerer korrekt med enten den gamle kerne eller med en 2.4-kerne fra sarge og først derefter foretage opgraderingen til en 2.6-kerne som et selvstændigt projekt.

Hvis du oversætter din egen kerne fra kildekoden, så sørg for at installere module-init-tools inden du genstarter med 2.6-kernen. Denne pakke erstatter modutils for 2.6-kerner. Hvis du installerer en af Debians kernel-image-pakker, vil afhængigheder sørge for at denne pakke bliver installeret automatisk.

Hvis du bruger LVM, skal du også installere lvm2 inden du genstarter, da 2.6-kerner ikke understøtter LVM1 direkte. For at tilgå LVM1-bind, benyttes kompatibilitetslaget (modulet dm-mod) i lvm2. Du kan beholde lvm10 installeret; initialiseringsskripterne vil finde ud af, hvilken kerne, der bruges, og udføre den version, som svarer til.

Hvis du har linjer i filen /etc/modules (listen over moduler, der skal indlæses under systemopstart), skal du vide at nogle modulnavne kan være ændret. I så fald må du opdatere denne fil med de nye modulnavne.

For nogle SATA-diskstyringer er enheden bundet til et drev og dettes partitioner kan blive ændret fra /dev/hdX til /dev/sdX. Hvis det sker, må du ændre opsætningen i din /etc/fstab og opstartsindlæser tilsvarende. Hvis ikke disse ændringer udføres korrekt, kan det ske at dit system ikke kan starte op korrekt.

Når du har installeret din 2.6-kerne, men inden du genstarter, så tjek at du har en reservemetode at starte op med. Sikr dig først at opsætningen af opstartsindlæseren har linjer for både den nye og den gamle, fungerende 2.4-kerne. Du skal også sikre dig at du har en rednings-diskette eller -cdrom ved hånden, for det tilfælde at en fejl i opsætningen af opstartsindlæseren forhindrer dig i at starte den gamle kerne.


5.2.1 Opsætning af tastatur

The most invasive change in the 2.6 kernels is a fundamental change of the input layer. This change 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.

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.

If your console keyboard is affected, you will probably also need to reconfigure your keyboard for the X Window System. You can do this either by running dpkg-reconfigure xserver-xfree86 or by editing /etc/X11/XF86Config-4 directly. Don't forget to read the documentation referred to in Husk inden næste opstart, Section 4.6.

This issue is unlikely to affect the Intel x86 architecture as all PS/2 and most USB keyboards will already be configured as a "normal" PC keyboard.


5.2.2 Opsætning af mus

Again because of the changes in the input layer, you may have to reconfigure the X Window System and gpm if your mouse is not working after upgrading to a 2.6 kernel. The most likely cause is that the device which gets the data from the mouse has changed. You may also need to load different modules.


5.2.3 Opsætning af lyd

For the 2.6 kernel series the ALSA sound drivers are recommended over the older OSS sound drivers. ALSA sound drivers are provided as modules by default. In order for sound to work, the ALSA modules appropriate for your sound hardware need to be loaded. In general this will happen automatically if you have, in addition to the alsa-base package, either the hotplug package or the discover package installed. The alsa-base package also "blacklists" OSS modules to prevent hotplug and discover from loading them. If you have OSS modules listed in /etc/modules, you should remove them.


5.2.4 Skift til 2.6 kan aktivere udev

udev is a userspace implementation of devfs. It is mounted over the /dev directory and will populate that directory with devices supported by the kernel. It will also dynamically add and remove devices as kernel modules are loaded or unloaded respectively, working together with hotplug to detect new devices. udev works only with 2.6 kernels.

As udev is automatically installed as a dependency of e.g. gnome, there is a chance that upgrading to a 2.6 kernel will result in udev being activated.

Although udev has been tested extensively, you may experience minor problems with some devices that will need to be fixed. The most common problems are changed permission and/or ownership of a device. In some cases a device may not be created by default (e.g. /dev/video and /dev/radio).

udev provides configuration mechanisms to deal with these issues. See udev(8) and /etc/udev for further information.


5.3 X Window-systemet kan ikke starte

If after booting your machine, X fails to load and you see an error "missing core pointer" in /var/log/XFree86.0.log, the problem could be that the mouse driver is not loaded fast enough by hotplug (bug #255744). The solution is to add the driver module for your mouse (e.g. psmouse) in /etc/modules.


5.4 X Window-system på Transmeta Crusoe-systemer

The X server shipping in sarge contains optimized code which is not properly executed by many Transmeta(TM) Crusoe(TM) processors. The result of this is that at a certain time (when cached code "morphed" from x86 to Crusoe VLIW instructions in the CPU is in a buggy state), X client applications which connect with it fail with the following error message:

     X Error of failed request:  BadLength
        (poly request too large or internal Xlib length error)
     Major opcode of failed request:  18 (X_ChangeProperty)
     Serial number of failed request:  15
     Current serial number in output stream:  18

In practical terms, this means that after a few hours of operation, applications will suddenly quit in rapid succession; if a display manager is running, that too will repeatedly quit and attempt to restart itself. The state will persist until the buggy VLIW Transmeta code is flushed from the cache.

Since the bug is in the proprietary Transmeta Code Morphing Software (CMS), and the laptop BIOS checks the CMS for a vendor signature at boot time, this can only be fixed in cooperation between Transmeta and the laptop vendor. Further information about this issue can be found at http://www.cs.auc.dk/~fleury/bug_cms/ and Debian bug report #216933.

The workaround for this bug is to install an X server compiled without optimization, such as the xserver-xfree86-dbg package.


[ tilbage ] [ Indhold ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ A ] [ næste ]


Udgivelsesbemærkninger for Debian GNU/Linux 3.1 (`sarge'), Intel x86

$Id: release-notes.da.sgml,v 1.10 2005/06/21 21:36:15 fjp Exp $

Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob Bradford (nuværende), Frans Pop (nuværende)
debian-doc@lists.debian.org