Two days workshop on Working with Open source technologies & BOSS
Document Actions
Issues
Issues to be aware of for tejas
Sometimes, changes have side-effects we cannot reasonably avoid, or we expose bugs somewhere else. We document here the issues we are aware of. Please also read the relevant packages' documentation, bug reports etc.,
On some older systems, shutdown -h may not power off the system anymore (but just stop it). This happens because apm needs to be used there. Adding “linux pci=nommconf” to the kernel's command line, e.g. in grub or lilo configuration files should fix this issue.
Asynchronous network initialization may cause unpredictable behavior
On systems which use udev to load drivers for network interfaces, it is possible due to the asynchronous nature of udev that the network driver will not be loaded before /etc/init.d/networking runs on system boot. Although including allow-hotplug to /etc/network/interfaces (in addition to auto) will ensure that the network interface is enabled once it becomes available, there is no guarantee that this will finish before the boot sequence begins to start network services, some of which may not behave correctly in the absence of the network interface.
Sound stops working
In rare cases the sound might stop working. If this happens, go through the alsa checklist: run alsaconf as root user, add your user to the audio group, use alsamixer and make sure levels are up and it is unmuted, make sure arts or esound stopped, make sure OSS modules unloaded, make sure speakers are on,
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.
/etc/X11/xorg.conf directly. 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.
Again because of the changes in the input layer, you may have to reconfigure the X Window System if your mouse is not working. 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.
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.