Monitor Video Out of Range problems occur primarily with LCD Monitors. A monitor able to handle a 1280 1024 at 75 Hz will fail because it will be preset to an 85 Hz refresh rate/vertical frequency that that the monitor cannot manage. Similarly, a 15-inch monitor able to handle 1024 768 at 70 Hz will fail because the preset resolution is 1280 1024 at 75 Hz.

To prevent these problems, during installation, select 1024 768 or 800 600 temporarily, depending on the capacity of your monitor, by pressing F2. You will then see a menu of different resolutions to use. Use your arrow keys on your keyboard to select the resolution you want.

After the software packages are installed, the automatic (SaX2) hardware configuration will set your monitor to VESA 1280 1024 at 75 or 85 Hz, depending on whether the monitor is 19, 17, or 15 inches. You will want to change resolution at this stage, or the monitor will run out of range when rebooting to the graphical login screen.

On reboot, if the monitor encounters the out-of-range problem, it shows a black screen. But you can solve this without a cumbersome re-installation.

After rebooting Linux, at the point when the display goes black and gray just before the graphical login screen is supposed to start up, select Alt-F1 from the keyboard, followed by the Enter key. This breaks the startup of the graphical login screen, and presents a text-based command line login instead. Log in as root with root password.

Next, enter the following command

               init 3

followed by the Enter key. At the # prompt that again appears, enter:

               sax2 -l

to start the SaX2 graphical configuration tool in a low resolution mode.

Now it is possible in SaX2 to change the monitor and resolution settings. Test it and customize the size and position before saving the configuration.

Reboot the system. The graphical login screen should now be displayed properly.

The ATI Radeon IGP 345M requires Xfree86 Version 4.3.

Run X-version from the command line. You will see the following information:

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Date: 25 March 2004
Module Loader present
To resolve the problem, add these sections to your /etc/X11/XF86Config-4 file: 
Section "Device"
Identifier "ATI"
Driver "radeon"
VendorName "ATI"
BoardName "Mobility U1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Run the following command as root:

dd if=/dev/cdrom of=/dev/null

If the media is fine, you should get a result such as the following:

linux:~ # dd if=/dev/cdrom of=/dev/null
1316996+0 records in
1316996+0 records out

If a physical defect on the media prevents the data from being successfully read, you will get an error message.

If you do not receive an error, your system may be slowed down by the capacity of the CPU. Wait a little longer—on some machines the decompress and timeouts are excessively long on this package install.

Wireless LAN cards may or may not work in JDS. Unfortunately, this is a general Linux problem, not isolated to JDS. Several projects exist to help resolve the problems depending on the type of LAN card you own.

A commercial solution comes from Linuxant which you can find at http://www.linuxant.com/driverloader/.

Linuxant supports chipsets from the following manufacturers:

Free solutions may be found at: