Skip to content.

Scientific Linux

Sections
Personal tools
You are here: Home » Distributions » 5x » Features » Limitations

Limitations

Even Scientific Linux has limitations

We strive for perfection. Any goal less than that is sortof silly. But we are also realistic. Not everything is going to be perfect. This page documents what we know is broken, or not living up to it's potential.

ipw2100, ipw2200, ipw3945

Wireless driver, firmware and deamon for the Intel ipw3945 wireless chipset
Limitation : Does not work in the installer.

ftp installs

Limitation : Currently, during an ftp install when it get's the the graphical section, there is a long pause (close to a minute) when it sits at a blank screen. It is NOT frozen, it is just searching for files that are not there. Give it a couple minutes and it will continue.

NVIDIA motherboard chipsets

Limitation : May need to use
linux noapic
to install.

Intel 965 motherboard chipset

Limitation : May need to use
linux all-generic-ide
if you have pata hardware (usually your cd-rom, or dvd drive)

(SL 5.1)MegaRAID


Host bus adapters that use the MegaRAID driver must be set to operate in "Mass Storage" emulation mode, not in "I2O" emulation mode.
Earlier Scientific Linux releases generally do not attempt to load the I2O driver before the MegaRAID driver.

(SL 5.1)nVidia CK804 chipset


When running Scientific Linux 5 on a machine with a nVidia CK804 chipset, you may see the following message:

 kernel: assign_interrupt_mode Found MSI capability
 kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
These messages mean that some PCI-E ports are not requesting IRQs. These messages do not affect the operation of the machine.

(SL 5.1)Root and auto-mounting


In Gnome, removable storage devices (such as CDs and DVDs) do not automatically mount when you are logged in as root. You will have to manually mount it through the graphical file manager.

(SL 5.1)Virtual Installs and CD's


When installing a fully virtualized Proprietary guest from a CD, the second stage of the guest install might not see the CD after reboot.
To work around this problem you have to edit the xen configuration file (/etc/xen/) and add an entry for the CD or DVD.
For this example, the name of the guest machine is winxp, we are installing it to a file called /opt/images/winxp.img, and the CD drive is /dev/hdc.
Normally, the configuration file disk line looks like
disk = [ 'file:/,hda,w']
And you would change it to be
disk = [ 'file:/,hda,w', 'phy:/,hdc:cdrom,r']
So, if we look at our example, our disk line in /etc/xen/winxp will look like
disk = [ 'file:/opt/images/winxp.img,hda,w', 'phy:/dev/hdc,hdc:cdrom,r']

Virtulization

Xen based virtualization is fully supported. However, Xen-based virtualization requires a different version of the kernel to function. The KVM hypervisor can only be used with the regular (non-Xen) kernel.

While Xen and KVM may be installed on the same system, the default networking configuration for these are different. Users are strongly recommended to only install one hypervisor on a system.

Automounting

Removable storage devices (such as CDs and DVDs) do not automatically mount when you are logged in as root, or in a non graphical enviroment. If you are in a graphical enviroment, you will need to manually mount the device through the graphical file manager.

Alternatively, you can run the following command to mount a device to /media:

mount /dev/[device name] /media

X resolution

When running the bare-metal (non-Virtualized) kernel, the X server may not be able to retrieve EDID information from the monitor. When this occurs, the graphics driver will be unable to display resolutions highers than 800x600.

To work around this, add the following line to the ServerLayout section of /etc/X11/xorg.conf:

Option "Int10Backend" "x86emu"

Freeradius2

The freeradius and freeradius2 packages share common files, and cannot be installed together on the same system.

postgresql84

postgresql84 and postgresql packages cannot be installed concurrently on the same system, with the exception that the postgresql-libs package can remain in place in parallel with postgresql84. The postgresql-libs package contains client-side library code to which existing applications may be linked. These libraries will still work with the newer server.

As 8.4.x also has on-disk data format differences from 8.1.x, it is not possible to upgrade an existing 8.1.x PostgreSQL database to 8.4.x merely by replacing the packages. Instead, first dump the contents of the existing database using the pg_dumpall command, then shut down the old server and remove the database files (under /var/lib/pgsql/data). Next, remove the old packages and install the new ones; start the new server; and finally restore the data from the pg_dumpall output.

while postgresql84 packages are provided, rebuilding other packages with this new version is not supported. If a package using postgresql-devel is to be rebuilt, a downgrade from postgresql84 to postgresql is necessary.

Created by dawson
Last modified 2010-05-19 10:37 AM
 

Powered by Plone

This site conforms to the following standards: