SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Hi guys I recently recompiled my kernel to 2.6.9 and I noticed that some devices were missing, hdd, sda2-5, and a few others, and I am constantly haveing to create another symbolice link to hdc for my dvd drive, please someone tell how I fix this problem? It seems that everytime I reboot the symbolic link is gone. So What do I do?
I am assuming that you are coming from a
2.4 series kernel. The 2.6 series uses udev
to manage /dev (granted if you do not have
the udev package, they it will use devfs). udev
manages /dev dynamically from userspace,
which is great. When you plug /dev/sdaX
in, then udev will create a device node for
that device. Good Luck
How is such devices connected to your system ?
Primary ide master/slave or did you pur it on the secondary channel?
If you're not using ide-scsi emulation it should be the same as with the 2.4 series kernel.
Hope this helps
I was under the impression that ide-scsi was broken in 2.6.9 (unless you have patched your kernel sources before compiling). As that is the case, your devices that are not being recognised as SCSI may have been assigned hdX device nodes?
Ok well device sr0 is what I used before to mount my second drive, but THERE IS NO SUCH FILE! All I know is that is what I used to mount it before and now it is gone. And the device that I also used to mount it /dev/hdd is also gone! Im lost guys what do I do?
The first thing is to do as urka58 said: go back through and tell us what devices are, and are not, mounting, and how they are physically plugged into the system.
(e.g. Primary IDE Channel: Hard drive with X partitions (hda),
Secondary IDE Channel: CD is the primary drive, etc...)
Unfortunately, sda2-5 isn't very helpful, as it doesn't tell me what the device is that's not being seen?
If they're not being seen, then the chances are that you may be missing something in your kernel, or the devices may have been assigned differently under udev (as tank728 said, udev only creates nodes that actually exist, unlike devfs in the 2.4 series, which just has lots of nodes pre-created and don't always mean anything).
Oh, and a quick thought does come to mind - do you have a line in /etc/lilo.conf to deal with the SCSI emulation (e.g. 'append=hdc- ide-scsi' or something vaguely similiar to that)? If so, try commenting it out with a '#' in front, run /sbin/lilo, restart and see if your drive is seen then as hdX (X being something like d in your case I presume, I can't say exactly what without knowing how your drives are physically connected)?
Well ok I am pretty sure my second drive is Primary slave, that help? And I will try removing that line to see if that makes a difference, the only thing im worried about is that I wont be able to use ccdrecord if I do that but owell.
I wont be able to use ccdrecord if I do that but owell.
You don't need SCSI emulation in the 2.6 kernels for CD burning. ide-SCSI is deprecated, unmaintained and considered broken. For cdrecord, just specify the device you're burning to as 'dev=/dev/hdX' (X being whatever the device is).
Excuse me and I also rebooted.
You did run /sbin/lilo after you updated /etc/lilo.conf and before rebooting, and it didn't give any unusual errors?
If so and /dev/hdd still isn't seen, I'm at a bit of a loss. Your earlier posts suggest /dev/hdc is a DVD-ROM drive, and if that's seen, I can't see any reason for /dev/hdd not to be seen (you must have compiled in IDE/ATAPI CDROM support for your DVD-ROM drive to be supported), unless there's another file I've forgotten about that has to be edited to stop ide-scsi running? (I'm still certain it's something about the ide-scsi setup that's stopping the drive being seen properly if /dev/hdc can be seen)
Not to worry. I had the same problem when I first upgraded my kernel.
For future reference, if you update your kernel, or make any change to /etc/lilo.conf, you *must* run /sbin/lilo before you restart, otherwise the changes are not used by LILO, and with a kernel change, you won't be able to boot your new kernel (e.g. building a 2.6.10 kernel, then rebuilding it, perhaps to add a missing option, and copying that to /boot, you still need to run /sbin/lilo)
Also, if you are running a vanilla Slackware 10.0 install (aside from having update the kernel), you may find that 'man'/'less' don't work. This is a udev problem, see my post on this page for the fix (I've not encountered the problem, but many others have, so I thought it worth recommending for the FAQ): http://www.linuxquestions.org/questi...5&pagenumber=3