Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
did you edit your grub.conf or lilo.conf file to tell it where to find that initrd.img file? if you scroll down in that EXCELLENT guide you will notice a section about editing your bootloader configuration file. don't forget to save and update grub/lilo with /sbin/grub-install or /sbin/lilo.
Finally I modified my lilo conf so that the entry for the new kernel was identical to the default one for 'linux' (as provided by my Mandrake 10.0 installation), naturally modified so that it pointed to the new kernel and gave the new kernel a new label in lilo.conf.
This removed the problem of kernel panic, but I do have new problems since updating to the 2.6.6 kernel from 2.6.3.
The new problems are:
1) I have two ethernet cards, in my 2.6.3 config they were (as you'd expect) named eth0 and eth1. In the 2.6.6 config there are now eth0, eth1 and eth2. eth0 fails to initialise on startup, though after the system has booted it appears to have the same IP as eth1, eth2 starts up OK (this used to be eth1 in 2.6.3). Things work but I don't know why it happened and that concerns me - any advice would be appreciated!
2) My DVD-ROM drive (the only optical drive in the system) no longer mounts disks in the 2.6.6 config (though it does if I go back to 2.6.3). I've no idea why this is happening but it is very frustrating - again advice would be appreciated. If I try to manually mount, I get:
mount: wrong fs type, bad option, bad superblock on /dev/hdg, or too many mounted file systems
please check and/or post your /proc/filesystems file. this is where you will find the filesystems that your system supports. if your system does not recognize cd's it is most likely that you did not include support for the iso9660 filesystem which is what most cd-roms use. you might have included this as a module, rather than compiled in, which wouldn't be too bad, as you could set it up to load when you boot (if you don't really feel like recompiling, which i understand).
I viewed the /proc/filesystems file (I can still post it if that will help) and found that iso9660 only appears in the file when a CD is actually mounted which seems a bit strange.
On the CDROM support side of things I compiled ISO9660 support directly into the kernel , under File systems->CD-ROM/DVD Filesystems->ISO 9660 CDROM file system support - I actually added everything under that option to the kernel (rather than as modules).
I've since compiled Kernel 2.6.7 and have the same issues but...
The command line you suggested did allow me to mount a CD on 2.6.6 and 2.6.7, I modified it slightly to be:
mount -t iso9660 -r /dev/hdg /mnt/cdrom
In the 2.6.3 config, if I insert a CD-ROM it gets mounted automatically, but doesn't on 2.6.6/2.6.7 (presumably due to whatever I've done to make the standard mount command not work). Should I be editing my fstab to allow automounting again, and if so how? the current entry for the DVD drive is as follows:
/dev/hdg /mnt/cdrom auto user,iocharset=iso8859-15,codepage=850,noauto,ro,exec 0 0
part of the entry from the DVD's entry in /etc/fstab and now mounting/automounting seems to work fine.
I would be very interested to know why this made a difference (what does/should codepage=850 actually do?) and why it worked with the shipping 2.6.3 kernel but not the 2.6.6/2.6.7 ones that I compiled? I'm just curious now and its an opportunity to learn if anyone knows the answer.
The networking issue is still there, but again is more of a curiosity thing now since it works - just a bit odd that there is a 'phantom' interface.
2 * linux/fs/nls_cp850.c
4 * Charset cp850 translation tables.
5 * Generated automatically from the Unicode and charset
6 * tables from the Unicode Organization (www.unicode.org).
7 * The Unicode to charset table has only exact mappings.
this is from nls_cp850.c from the kernel sources. i've also found this link where a guy seems to have the same problem with a 2.6 kernel and gets the same error message. if you read through the thread he eventually finds that he compiled cp852 and not cp850, so the codepage=850 returned an error.