Total Newbie

[drbfunk]

OK, I've spent all day trying to get this thing to work. I really want to like Linux systems. They appear to be miles ahead of Windows.

I just installed Knoppix 3.3 11-19 version. I accidetally booted from the backup floppy I created when I did the initial install. It works fine, but it won't detect USB devices and I don't think I can do things I should. I restarted without the bootdisk and it displays "no operating system found." I partitioned the HD myself (probably problem #1) giving partition #1 to a Windows Fat 32 system. Partitions 2 and 3 are Linus root and swap respectively.

I've spent a considerable amount of time looking in the FAQ's, but can't seem to find the right questions.

Questions:
1) If I can boot without a disk, will my USB problem clear up?

2) How do I boot without a disk?
By disk I mean 3.5' floppy. I have the CD-Rom and can boot from that, but would rather have this Knoppix as my primary operating system.

Please have pity on a very first time Windows convert.
Dr. B

[Stephen]

OK, I've spent all day trying to get this thing to work. I really want to like Linux systems. They appear to be miles ahead of Windows.

I just installed Knoppix 3.3 11-19 version. I accidetally booted from the backup floppy I created when I did the initial install. It works fine, but it won't detect USB devices and I don't think I can do things I should. I restarted without the bootdisk and it displays "no operating system found." I partitioned the HD myself (probably problem #1) giving partition #1 to a Windows Fat 32 system. Partitions 2 and 3 are Linus root and swap respectively.

I've spent a considerable amount of time looking in the FAQ's, but can't seem to find the right questions.

Questions:
1) If I can boot without a disk, will my USB problem clear up?

2) How do I boot without a disk?
By disk I mean 3.5' floppy. I have the CD-Rom and can boot from that, but would rather have this Knoppix as my primary operating system.

Please have pity on a very first time Windows convert.
Dr. B

It looks like lilo did not get installed properly to the MBR. To fix the usb problem I believe you will need a line:

none            /proc/bus/usb   usbdevfs        defaults        0       0

In the file /etc/fstab you will have to edit the file as root to do this open a console window (clam shell icon on the taskbar) and type in su then the enter key type in the root password enter key again next type gvim /etc/fstab then enter key to open the file for editing and put the above on a line by itself and save the file. To fix the lilo problem if the file /etc/lilo.conf is configured correctly but not installed properly all you have to do is type /sbin/lilo -v and enter this would be done as root still in the console window and example of a properly configured lilo.conf:

vga=791
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
#       prompt
#       single-key
#       delay=100
#       timeout=100

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"

# Boot up Linux by default.
#
default=Linux

image=/boot/vmlinuz-2.4.22-xfs
        label=Linux
        initrd=/boot/initrd.gz
        read-only
#       restricted
#       alias=1

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3
other=/dev/hda1
  label="Windows"

When you open the file to check the contents before running the lilo command above it should look similar to this the only things that you should really have to check for is the boot=/dev/hda this is where lilo will be installed in this case the MBR (hda) and the root=/dev/hda3 that are near the top of the file (the windows entry is the other= line at the bottom of the file) in this example I am showing you make sure it is set for your / to check if they match before opening the file do fdisk -l which will tell you the partitions on the disk you would have one Win95 FAT32, one Linux swap and just Linux this is the one you want to match the root= line so after having checked that the file is correct quit without making changes run the lilo command to write to the MBR if not correct then make the change save the file and run the lilo command next you would reboot for both changes to take effect and you should be able to boot into either windows or linux from the lilo screen and hopefully the usb will work also. If these steps do not work can you post the contents of the /etc/lilo.conf, /etc/fstab and the output of fdisk -l, lsmod and some details on the usb devices.

[rickenbacherus]

Boot the Knoppix cd like so:

knoppix 2

Then you need to mount the partition that you installed Knoppix to. If it were hda3 then:

mount /dev/hda3

chroot /mnt/hda3

mcedit /etc/fstab

Now for USB to work you just need to add a new line to /etc/fstab like so:

mcedit /etc/fstab

At the bottom add the following:

usbdevfs /proc/bus/usb usbdevfs defaults 0 0

Hit F2 to save and F10 to exit.

Now for the boot loader:

mcedit /etc/lilo.conf

You need to make these 2 entries look like so:

boot=/dev/hda

root=/dev/hda3

Then you need an entry for M$ like so:

other=/dev/hda1
label="wienerdoze"

Hit F2 to save it then F10 to exit.

/sbin/lilo

It should say *something* like:

Added Linux
Added wienerdoze

If it spits an error guess what?? When you get no errors then do CTRL+D to exit chroot. Reboot.

What that does is installs LILO to MBR and points it to your /root partition so that the next stage of the bootloader can take over. This should get you booting into Knoppix or windows. And hotplugging for USB should also work.

[drbfunk]

Thank you guys. I'm still very new so I really appreciate you talking me through with kid gloves.

[drbfunk]

Looks like I spoke too soon. When I do the gvim /etc/fstab function I can add the code in the window. BUT, the usbdevfs is highlighted in red. The line of code looks like this (with colors in parenthesis)

none (light green) /proc/bus/usb(black) usbdevfs (highlighted red) defaults (dark green) 0 0 (pink)

Also, my USB thumb drive will not appear on the desktop as the hdb2 partition and other things do. The drive is an PNY thumbdrive 128 MB 1.1 USB. I'm sorry to be so juvenile in this, are there places that explain the code so I could better learn this on my own? The lilo problem has been solved. Thanks a bunch.

Dr. B

[Bartman]

Try plugging in the USB bar, open a console and enter:

mount /dev/sda1 /mnt

Your USB bar should be recognised as a SCSI device by Knoppix, which is why you use /dev/sda1 (assuming you have no SCSI hard drives on your system. I do, so I have to use /dev/sdb1 instead).

If this does not produce an error, you should be able to see the contents of your USB bar by entering:

cd /mnt
ls

in the terminal. If this does not work, post back with the errors you get.

Bartman

[drbfunk]

Thanks Bartman. It's been awhile since I've checked back because the site seemed to be down for a couple days.

Anyway. I did the commands and they worked; I got the contents of the usb drive to display in the shell konsole. But I stilll cannot access the contents from my desktop. And, in the gvim /etc/fstab the word usbdevfs still appears as red. Am I correct in assuming that this word is foriegn to the OS?

thanks,
Dr. B

[Stephen]

Thanks Bartman. It's been awhile since I've checked back because the site seemed to be down for a couple days.

Anyway. I did the commands and they worked; I got the contents of the usb drive to display in the shell konsole. But I stilll cannot access the contents from my desktop. And, in the gvim /etc/fstab the word usbdevfs still appears as red. Am I correct in assuming that this word is foriegn to the OS?

thanks,
Dr. B

The colours would be the syntax highlighting in gvim. To get access to the device from the desktop you would edit the /etc/fstab and put a line in it for the /dev/sda1 to be able to make a shortcut on the desktop.

/dev/sda1       /pendrive     auto      rw,noauto,user     0     0

Now I am not sure of this line I do not have any device to test it with so someone may have a better solution. For this to even have a chance to work you have to use mkdir /pendrive as root to make a directory for the mount point /pendrive you can call this whatever you want too you would just put your choice in the /etc/fstab line in the pendrive's place. Now you should be able to create a shortcut on the desktop by right clicking and choosing create new then Hard Disc and in the device tab choose the /dev/sda1 and make sure the read only is unchecked name the shortcut as you want it to appear on the desktop and save the shortcut. Now plug in the drive and see if you can access it through the shortcut.

[drbfunk]

it seems that all has worked so far. creating the pendrive went well. Now, when I try to mount, I use the code:

mount /dev/sda1 /pendrive

Is this right? How do I access it if it is? Should I type something in the line right after I write that code?

Please forgive my little knowledge

[drbfunk]

a little more info:

when I click on the icon on the desktop, it opens file:/pendrive but nothing is shown

when I'm in the konsole, I type

cd /pendrive
ls

and I can see the contents of my thumbdrive in the konsole. The contents are linux programs I want to install to my new system.
Where is the communication issue?
Thanks for all your help already
B