SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Within slack disk 2 /extras is the directory /udev-alternate-versions...
the answer maybe within the README file...
Quote:
From the desk of Patrick Volkerding, Mon Aug 7 16:08:08 CDT 2006.
Hello,
Some people have reported problems with the newer style udev, and I've seen
some myself. However, newer kernels are about to require a very recent udev
so it was time to upgrade to the latest, in spite of the possible pain.
One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.
In some cases where you want to run udev it might be easier to run one of
these old versions than to fight with it. Feel free to try them if you run
into problems with the latest. Just "upgrade" to one of these with
upgradepkg, copy rc.S and rc.M over the ones in /etc/rc.d/, and finally
go into /etc/rc.d and move rc.udev.new to rc.udev (and make sure that it
is executable). Also, check to make sure that there aren't new config or
rules files that need to be moved into place. You can find these with:
find /etc -name "*.new"
Good luck! :-)
Pat
I was thinking of copying the appropriate module for the cdrom drive from the 2.4 kernel to the 2.6. Any thoughts anyone...
It's the same no matter what cdrom I have in the drive...at the moment it's slack disk 2.
Since I can mount the drive with the 2.4 kernel, I think it maybe using the wrong driver for 2.6. I have no idea as yet on how to rectify this or where to begin.
One way to determine if the wrong module is being loaded is to boot the working kernel and do a lsmod and then the nonworking one and compare it's lsmod to the original to spot any differences.
You seem to be getting nowhere fast, so I will offer up a wild-ass guess.
One difference between 2.4 and 2.6 kernels in slackware 11.0 is that hotplug runs with 2.4 and not with 2.6 kernels (udev only). I suggest booting with 2.4.33.3 and print out the output of lsmod. Then boot with 2.6 and compare loaded modules. You may note a difference that you can create a work around for when booting with a 2.6 kernel and no hotplug.
Along these lines:
Quote:
One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.
I do not think that copying a module as you seem to be suggesting will work.
Needing a experts help here to dicipher the above. I am looking for the module used in conjunction with my cdrom drive, bearing in mind this is a laptop. Any help will be welcomed.
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
where is ro in the /dev/sr0 line??
do you have 2 seperate cd drives???
IF U HAVE 1 CD DRIVE
scsi emulation made /dev/sr0 and the corresponding divice is changed. so you need to mount /mnt/cdrecorder, not /mntcdrom
(always remove unwanted links in /dev)
when you were using 2.4 kernel u need scsi emu and your devices has to be changed, if there is only one drive tehn, do
rm -rf /dev/cdrom
ln -sf /dev/sr0 /dev/cdrom
(this has to be done in 2.4 kernel, if you have a single cd drive)
also while using a 2.6 kernel, you dont need append line in lilo remove that for 2.6 kernel section
i got you.
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
where is ro in the /dev/sr0 line??
dev/sr0 is a cdrw drive...it is the one that works okay in both 2.4 and 2.6
do you have 2 seperate cd drives???
YES...
I have a laptop, with a cdrom drive module in place, this works in 2.4, but not in 2.6.
I also have a usb iomegaZIP cdrw drive attached, which works in both 2.4 and 2.6.
sorry i cant help more but some suggestions, actually i didnt ment the earlier commands . really it was"$ls -al /dev |grep -i hdc"
do "$dmesg |grep -i hdc" without any cd inserted.
do "$dmesg |grep -i cd" that msut endup within 2-3 lines as it is for sr0
Quote:
All very well, but this would have to be repeated every time I boot into 2.6.
when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.
Quote:
Tried it once, and guess what it made no difference.
it is because your fstab has correct device entry not simlinks.
ur problem is not that. i went through yur dmesg, and i hope u were trying to mount a cd made from windows.
is there any append line in lilo. like append "hdc = ide-scsi"?? i dont think so.
try some more and i am givenup
1.try mount as root
2.put your slack cd and try!!
mount -t iso9660 /dev/hdc /mnt/cdrom
3.try oounting to some other moutn point like /home/name/mycd
mount -t iso9660 /dev/hdc /home/name/mycd
4.try mountin /dev/sr0 to /mnt/cdrom manually(just to check the permission)
i think $dmesg |grep -i hdc without any cd must give some info
when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.
I also edited /dev by deleting all symlinks pointing to hdc and sr0, I then added my own links to the appropriate drives. Unfortunately, after a reboot, the new kernel recreates the old symlinks and permissions, so therefore I have to go through the whole process again.
Quote:
it is because your fstab has correct device entry not simlinks.
ur problem is not that. i went through yur dmesg, and i hope u were trying to mount a cd made from windows.
is there any append line in lilo. like append "hdc = ide-scsi"?? i dont think so.
I do not know exactly what you mean here. fstab points to the correct symlinks I created in dev. More than likely the cd I am trying to mount will have been burned using software running under windows, including the slack install disks. There is no append line in lilo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
