GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Command Line Databases DIA Directories Disks EcoSysL Emacs Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples Internet IOT Java KDE Kernels Keyboard Konqueror KVM Switch LATEX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks Nextcloud Network File System NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Spreadsheet SSH Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

Ganesha Challenges

20201011 Ganesha is a Dell Inspiron 6400. See Section 36.19 for details.

Not working: Suspend, hibernate (although the command s2disk from the uswsusp package seems to work).

Not tested: Modem.

Hard disk was recognised as /dev/hda5 in the installed kernel (2.6.8) and as /dev/sda5 in the upgraded kernel (2.6.16).

Vesa video driver was chosen by default, but i810 should be used (081005 with Etch the 915resolution package is no longer required to get 1680x1050 (wide 8:5) resolution).

Wireless with a kernel version later that 2.6.17 worked out of the box. With a kernel version less than 2.6.17 you need to install the Intel ipw3945 driver, but once installed it works nicely. The network-manager package, under at least kernel version 2.6.18, can handle WPA-PSK and connects no problem.

CD/DVD stopped being found after moving to kernel 2.6.16 since the libata module was claiming the device, but failing to recognise it, and a later led-generic module load could not then claim it. The ATAPI option had to be enabled for the kernel and then the drive started being recognised. Apparently fixed in 2.6.17