A Linrad Starter CD

-by W3SZ

Image


The steep learning curve for Linux has been a stumbling block for many of us who have been eager to try Linrad. Those of us who have toughed it out and have gotten Linux to work with our computer hardware have been ecstatic when we've seen the results that Linrad delivers.

I was impressed with the 'Hardware Detection Engine' that Knoppix uses. It is second only to Fedora Core 3+ in terms of its ability to properly configure the hardware over a wide range of computers. But even it is not a panacea; some user intervention may be [probably will be] necessary to get things to run. If you already HAVE Linrad working then there is no need to mess with this. You have already achieved the endpoint this project hopes to achieve. But if you have not been able to get Linrad to work, this project MAY help you.

Most of this document describes what I did to set up a system so that I could crank out Knoppix-CD's with Linad and svgalib on them, in case you want to do that too.

However, first, here is a description of what you need to do to use the KNOPPIX CD that I made with Linrad and svgalib already on it.

You can download this CD from here: http://www.sm5bsz.com/w3sz/knoppixlink.htm

Here is the md5sums file

----------------------------------------



Here is an unformatted text file of this page

Here is a Word Document formatted file of this page



Here is what you need to do to use this CD:

1.Make sure your computer is setup to boot from CDROM if present. Find out by putting in the CD and rebooting. If your computer doesn't at least try to come up in Linux, but goes straight to Windows [for example], then reboot and go to CMOS Setup and change the drive boot order so that CDROM is first.

2.Put the CDROM in and boot off of it. Near the end of the boot process, before XWindows is started, you will be asked if you want to try Linrad before trying to configure svgalib [which is located at /UNIONFS/etc/vga/libvga.config]. If you answer 'y' or 'Y', then the Linrad directory Linrad-01.33 will be written to /UNIONFS/home/ knoppix and linrad will be automatically started. You can leave Linrad by hitting the 'esc' key. Bootup will then proceed, and you will enter XWindows if Knoppix is able to set it up properly. Once there you can edit libvga.conf at the location just given, or run Linrad by opening a terminal window and going to its directory [/UNIONFS/home/knoppix/linrad-01.33/] and typing './linrad', or by going to /UNIONFS/home/knoppix and typing './lin'. Once you are in the XWindows environment, you need to become superuser by typing 'su' at the command prompt for Linrad or any svgalib task to run. If the video in Linrad is messed up, the first thing I'd recommend trying is going to libvga.config and uncommenting the VESA driver line so that the VESA drivers are used. Also, You may need to change the default Horizontal and Vertical Sync ranges from the frequencies I have chosen. Also, the mouse type may need to be reset.

3.If you come up in XWindows, great! If not you have two options: leave it like that and run Linrad and everything else from the command prompt [which is what Leif recommends anyway], or try to get Xwindows to work. You can always avoid XWindows completely by typing 'knoppix 2' at the very first boot prompt you get when the CD is first booted, before anything loads except for the initial Knoppix screen backgound. If Xwindows doesn't work but you want to try to get it working, boot up staying in command-line mode by typing "knoppix 2" at the initial prompt during boot up as just noted, and then when the command prompt comes up after leaving Linrad, type:

"dpkg-reconfigure xserver-xfree86" and you will go thru a 'DOS'-like set of setup screens that allow you to reconfigure the XServer. For most of them you can probably just hit 'enter'. I found that setting the color depth to 16 or even 8 bits was necessary for some of my older machines to work.

4. If you get to XWindows you can set the network up if its not working by clicking on the Big Fat Penguin on the bottom Left and then selecting 'Network/ Internet' and then 'Network Card Configuration' and then making the appropriate choices.

5. If sound doesn't work for you and if it turns out it has something to do with the CD, let me know and I'll modify it.

6. you can make a persistent home with your configuration settings and home image file so that you don't need to reset all system parameters each time you boot up. If you have gotten XWindows to work, this is also done by clicking on the Big Fat Penguin and selecting the correct choices.

Here's the line in my grub file that tells knoppix where they are. The knoppix CD finds them when it boots and asks me if I want to use them.

boot: knoppix myconf=/dev/hda5 home=/dev/hda5/knoppix.img

I have the files knoppix.img, knoppix.sh, and configs.tbz in this directory.

Good luck!

----------------------------------------

This text describes how I made a bootable Knoppix CD with svgalib-1.9.21 and Linrad-01.33 installed on the CD as well. This required the creation of a permanent hard-drive Knoppix installation. The system was already dual-boot for Windows98 and Debian Linux, and it was convenient to work from Debian when creating the CD from the Knoppix HD filesystem.
The Knoppix CD that I created uses Knoppix 3.8.1, and Kernel 2.6.11.
My system has the following drives and partitions:
The following are temporary mount points that are created when needed, using loops:
/mnt/iso where the image of the newest knoppix CD is placed for review
/mnt/iso-old where the image of the original knoppix CD is placed for review
---------------------------------------------------------------------------

My grub file for this computer is at /boot/grub/menu.lst on hdc1:
If you want to skip the grub file go to here
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout10

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# titleWindows 95/98/NT/2000
# root(hd0,0)
# makeactive
# chainloader+1
#
# titleLinux
# root(hd0,1)
# kernel/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdc1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd2,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

titleDebian GNU/Linux, kernel 2.6.8-2-386
root(hd2,0)
kernel/boot/vmlinuz-2.6.8-2-386 root=/dev/hdc1 ro
initrd/boot/initrd.img-2.6.8-2-386
savedefault
boot

titleDebian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root(hd2,0)
kernel/boot/vmlinuz-2.6.8-2-386 root=/dev/hdc1 ro single
initrd/boot/initrd.img-2.6.8-2-386
savedefault
boot

titleDebian GNU/Linux, kernel 2.4.27-2-386
root(hd2,0)
kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hdc1 ro
initrd/boot/initrd.img-2.4.27-2-386
savedefault
boot

titleDebian GNU/Linux, kernel 2.4.27-2-386 (recovery mode)
root(hd2,0)
kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hdc1 ro single
initrd/boot/initrd.img-2.4.27-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

titleKnoppix-HD
root(hd2,02)
kernel/boot/vmlinuz root=/dev/hdc3 ro lang=us
initrd/boot/initrd.img
boot: knoppix myconf=/dev/hda5 home=/dev/hda5/knoppix.img

title Memory test
kernel (hd0,04)/boot/knoppix.381/memtest

title Windows 98 SE
rootnoverify (hd0,0)
chainloader +1


---------------------------------------------------------------------------


Once the above disk architecture was set up, I did the following

I placed in the /root directory several scripts:

createcompressedfs creates the compressed filesystem for knoppix
its contents are:

#!/bin/bash
# This script creates a knoppix compressed filesystem using /mnt/knoppix as the basis and puts the compressed file at /mnt/rem-isos/knoppix/knx-remaster

rm /mnt/knoppix/etc/X11/XF86Config-4.old

rm /mnt/knoppix/etc/X11/XF86Config.old

cp /mnt/knoppix/etc/X11/XF86Config-4 /mnt/knoppix/etc/X11/XF86Config-4.old

cp /mnt/knoppix/etc/X11/XF86Config /mnt/knoppix/etc/X11/XF86Config.old

rm /mnt/knoppix/etc/X11/XF86Config-4

rm /mnt/knoppix/etc/X11/XF86Config

rm /mnt/rem-isos/knoppix/knx-remaster/KNOPPIX/KNOPPIX

mkisofs -R -U -V "KNOPPIX.net filesystem" -P "KNOPPIX www.knoppix.net" -hide-rr- moved -cache-inodes -no-bak -pad /mnt/knoppix | nice -5 /mnt/knoppix/usr/bin/ create_compressed_fs - 65536 > /mnt/rem-isos/knoppix/knx-remaster/KNOPPIX/KNOPPIX


createmd5sum creates the md5sums file
its contents are:

#!/bin/bash

cd /mnt/rem-isos/knoppix/knx-remaster

rm -f KNOPPIX/md5sums

find -type f -not -name md5sums -not -name boot.cat -exec md5sum {} \; >> KNOPPIX/md5sums


createiso creates the KNOPPIX.iso file
its contents are:

#!/bin/bash

rm /mnt/rem-isos/knoppix/knx-iso/KNOPPIX.iso

mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 -boot-info- table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -hide-rr-moved -o / mnt/rem-isos/knoppix/knx-iso/KNOPPIX.iso /mnt/rem-isos/knoppix/knx-remaster

rm /mnt/win/knoppix/knx-iso/KNOPPIX.iso

cp /mnt/rem-isos/knoppix/knx-iso/KNOPPIX.iso /mnt/win/knoppix/knx-iso/


looper creates the mnt/iso directory from the KNOPPIX.iso file
its contents are:

#!/bin/bash

mount -o loop -t iso9660 /mnt/rem-isos/knoppix/knx-iso/KNOPPIX.iso /mnt/iso


Before making the compressed file using createcompressedfs it is necessary to rename the Xfree86 configuration files so that they don't interfere with installation on other machines. This function is included in the createcompressedfs script. They can be restored after the KNOPPIX.iso file is made by running the script:

restore-x11

This file restores:

/mnt/knoppix/etc/X11/XF86Config-4 from /mnt/knoppix/etc/X11/XF86Config-4.old
and
/mnt/knoppix/etc/X11/XF86Config from /mnt/knoppix/etc/X11/XF86Config.old

To get Knoppix up and running in this manner I:

1.set up the partitions as above, using a combination of parted, qtparted, fdisk, and PartitionMagic [don't ask].

2.got debian installed

3.ran the original knoppix cd

4.once in knoppix, set up my network using the 'Configure' menu.

5. got to a terminal window and ran 'sudo knoppix-installer', and put lilo in a partition rather than in the MBR, as I wanted to use grub and not lilo.

6.I rebooted into debian and installed svgalib-1.9.21 and linrad-01.33 from the /mnt/knoppix/home/knoppix directory and made sure they worked. I used the no svgalib_helper option when installing svgalib [found in the Makefile.cfg file, look for 'NO_HELPER=y' and uncomment it].

7.I went to /root in debian and ran ./createcompressedfs

8. I stayed in /root and ran ./createmd5sum

9.I stayed in /root and ran ./createiso

10.I stayed in root and ran ./restore-x11

11.I stayed in root and ran ./looper

12.I stayed in debian and put the original knoppix CDROM in the CDROM drive and after it was mounted compared its contents with the contents of /mnt/iso. The same files should be present in both directories.

13. I made a CDROM image of the KNOPPIX.iso file by going to Windows and using Nero.

HA! Windows saved the day!

 

Be sure to check out Rein W6/PA0ZN's Linrad Data Base at: http://www.nitehawk.com/linrad_dat/ for lots of excellent information!


Copyright 1997-2007 COPYRIGHT Roger Rehr W3SZ. All Rights Reserved

Brought to you by the folks at W3SZ