Klaus Knopper is the creator of Knoppix and co-founder of the LinuxTag expo. He currently works as a teacher, programmer, and consultant. If you have a configuration problem, or if you just want to learn more about how Linux works, send your questions to: firstname.lastname@example.org
Rogue Screen Resolution
I need your help to overcome a problem with a rogue screen resolution using Ubuntu 8.04.
I might have caused the problem by pressing the ESC key when the Splash Screen was showing. This was in a doomed attempt to see what was loading, and thus learn some more about the problem.
The LCD screen I'm using supports a resolution of 1280x1024, but after I pressed ESC, the resolution changed to 1280x768 for the User/Password window and for all three of my user windows. I have looked at /etc/X11/xorg.conf, which now has a reasonable set of resolutions (1280x1024, 1280x960, 1152x864, 1024x768, 832x624, 800x600, 720x400, and 640x480).
However, in System | Preferences | Screen Resolution, the monitor is shown as UNKNOWN despite the name in xorg.conf being PLE1900 (for the iiyama E1900S LCD monitor), and the list of resolutions now reads 1280x1024, 1280x960, 1280x800, 1280x768, 1024x768, 800x600, and 640x480, though when things went wrong, 1280x1024 disappeared. The refresh rate is 60Hz.
Where is the system picking up these resolutions, and how can I eliminate the 1280x768?
I used sudo displayconfig-gtk and was able to select 1280x1024, and now two of my three users are OK, but although my root primary user desktop is now 1280x1024, it has white bars on the left and right of the screen, as well as the normal white bars on the top and bottom. The User/Password screen cannot be changed from a resolution that is vertically stretched, so a circle becomes an ellipse with the longer axis vertical. (I think the resolution here is 1280x768.) The Splash screen has remained OK with no distortion.
Can you please tell me what is happening and how to correct the fault? I have read that Ubuntu will soon abandon xorg.conf. How will I be able to control things under the new configuration system?
I don't think that switching back from the boot splash screen to the readable text console by hitting ESC really caused a problem for the X server, unless it uses the framebuffer driver and is thus staying with the textmode resolution on the console.
The default and setup resolutions depend on your version of Xorg. I'm not sure which version of Xorg is used with your distribution, but if it is not older than about half a year, it should be using the randr extension, which means:
- the X server can (and will) make its own choice for the best resolution for your card/monitor combination,
- any Modes settings in /etc/X11/xorg.conf will probably be ignored, and
- runtime resolution setup is done by desktop tools (usually running in the desktop panel), such as kandrtray or lxandr, which remember your last setting (hence the difference between different user logins).
Please check to see whether such a desktop tool is running in your desktop panel. If it isn't, try starting, for example, krandrtray of KDE, which will place a small monitor settings applet in your desktop panel that you can control with left- or right-button mouse clicks. I believe your desktop configuration manager also uses the X server randr extension and stores a setting somewhere that will get activated on login.
The good news is that you don't have to change your X server configuration anymore. The bad news is, if you try, your attempt will probably be ignored.
You can force a specific resolution for a randr-enabled X server by using the xrandr utility as follows:
xrandr --output LVDS -s 1280x1024
xrandr --output LVDS --mode 1280x1024
One of these two commands should work.
You can also change resolutions for external monitors by using --output VGA instead of LVDS.
If you have problems with cut off borders of the screen, the most convenient way to fix these problems might be updating the Xorg server and the Xorg video chipset-specific modules needed for your card, rather than trying to set different options in /etc/X11/xorg.conf. Widescreen displays have much better support in newer Xorg versions.
On the main drive, I have a small boot partition (akin to a boot CD) with vmlinuz/initrd installed in the /boot directory. Using grub's configuration file menu.lst, I specify the root device as /dev/sdbx for a distro installed on /dev/sdbx. But so far this only works with Ubuntu Ibex. Fedora and SUSE fail – why?
You have to make sure that either the initial ramdisk or the kernel contains all USB drivers necessary to operate a USB-storage device. The necessary components include:
- uhci-hcd and/or ohci-hcd (the USB controller chips used on most computer boards),
- optionally, ehci-hcd for full USB 2.0 speed,
- usb-storage (the main "USB hard/flash disk" module), and
- the generic sd module for scsi-like removable disks. This module is necessary in order to handle USB storage devices the same way as SCSI hard disks.
Depending on the kernel configuration, you might have to load dependencies, such as the USB device white/blacklists, as well. You can check modules with the modinfo modulename command to uncover such dependencies, though all modules might not fully support this command. If you have the opportunity to get some kind of emergency shell when the USB hard disk doesn't mount, check dmesg for a missing module load attempt.
In most cases, the initramfs-tools will take care of module dependencies in the initial ramdisk, but sometimes you have to help by adding them manually to /etc/initramfs-tools/modules prior to calling mkinitramfs or update-initramfs.
Also, the /dev/sd* device files should be included in the initial ramdisk, so that the disks actually get mounted.
In some cases, accessing a USB hard drive is simply a timing problem. The USB controller needs some time for detecting and activating a device – up to 20 seconds. If you have access to the boot scripts used with your distro, adding a sleep 10 before any mount attempt might help. Booting with kernel append= option:
might produce the necessary delay on the kernel side when USB storage is compiled in.
Laptop Sound Card
I recently installed Ubuntu 8.10 on my Medion MD 98300 laptop in an effort to get rid of the Windows Vista disaster that was delivered with my system. Almost everything works perfectly, but I am experiencing a few annoying problems. The biggest problem for the moment is the sound. Playing music from my external hard drive is no problem, but the music only plays through the built-in speakers. From the moment I plug into a jack (with the cable going to my stereo-system), I have no line out.
I tried to find a solution on the Ubuntu documentation pages, but the proposed remedies (like upgrading to the most recent ALSA driver) had no result. I can't use a headphone or line out.
I looked on several forums to find people with similar problems, but so far I haven't found a solution. I wonder whether you could give me any advice to get rid of this sound problem. (The sound card is Intel HDA with a Realtek ALC 883 audio-chip.)
Your sound card might suffer from a faulty internal mixer configuration. I have seen this many times for the chipset you mention. The problem is that no matter which value you set for the line out volume, it does not change anything. In fact, this also sometimes happens with the Master and PCM settings.
The cause for this problem is often switched channels. In other words, the PCM or line out channel isn't really doing what the mixer program says it is doing. Instead, some other control on the mixer governs the function you are looking for. Often igain or phone out (really!) sets the value you would have expected to change when moving the line out slider.
To solve the problem, first start the mixer tool of your choice. The more buttons and sliders of different channels it has, the better. I usually try aumix or its graphical equivalent aumix-gtk first, but kmixer from KDE should do fine as well.
Now play a sound file with the output socket attached to the speakers. (I assume you did not accidentally plug the speakers into the microphone or line-in socket.) Set Master, PCM, and line out to significant values (80 percent should be sufficient), which will probably not solve the problem yet, and then also increase all other output channels to higher values.
Be careful with any so-called monitor or feedback settings, which could cause ugly noises when your laptop microphone starts picking up sound from the speakers.
If you have increased all output channel settings and still nothing happens, try the effect or amplifiers settings next. One of these settings might really be the output level control you are searching for. As a last resort, also try the input level settings, but be aware of the aforementioned loud resonance effects this can cause, especially when unplugging your stereo cable with the volume still set to maximum and the music still playing.
If these steps do not bring up the sound, you might really need a newer driver (or rather, kernel) for this sound card; however, it is rare for the internal speakers to work and the line out to fail. In most cases, sound cards simply don't work at all when drives or interrupts are not auto-detected correctly.
Another possibility is that the socket is simply broken, but this would cause problems when you are using other operating systems in addition to Linux.
Sometimes you can get fooled by an additional sound card (like a webcam with a mic), which claims to have the primary mixer setting. (In other words, you are just working on the wrong sound device.)
In that case, you will have to use a mixer that can handle more than a single sound card and switch settings to the real output device.
Buy this article as PDF
Kernel king admits his tone has alienated volunteers, but says the demands of the process require directness.
New flaw in an old encryption scheme leaves the experts scrambling to disable SSL 3
Lennart Poettering wants to change the way Linux developers talk to each other.
Enterprise giant frees itself from ink and home PCs (and visa versa).
Mozilla’s product think tank sinks silently into history.
TODO group will focus on open source tools in large-scale environments.
New tool will look like GParted but support a wider range of storage technologies.
New public key pinning feature will help prevent man-in-the-middle attacks.
Carnegie Mellon researchers say 3 million pages could fall down the phishing hole in the next year.
The US government rolls new best-practice rules for protecting SSH.