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!
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.
Hey...I've got a MDK9.1 system, and I'm trying to get hotplug up and running. I've got a portable hard drive which uses usb 2.0 (micro-solutions) and I can get the rpm for the driver, but when I try to rpm -i, it says that hotplug 01_17 is needed.
I've tried running a few hotplug 01_17 rpms, but none of them are specifically for mandrake. I tried running a mandrake hotplug rpm (not 01_17) and I still get the error (requires hotplug 01_17)
Hotplug should work out of the box. Try: rpm -qa hotplug and see what it says.
If you really don't have it installed, then see if it is on your Installation Discs - you should be able to use Mandrake Control Center to install it.
Have you tried accessing the drive not using the backpack 'driver'? For example, plug in the device and check to see if it has been found? Plug it in and check the output of dmesg to see if there's been anything about new removably storage devices. If so, then run cdrecord -scanbus to see that it really has been identified. If so, then it'll appear to be a SCSI harddrive, so you can check to see if which partitions are on there with (as root) fdisk -l /dev/sda (I'm presuming you have no other scsi devices). When you know the partition, then mount it as normal.
I think it tries to read the drive, but gets some errors. This is a dmesg output:
Attached scsi removable disk sda at scsi0, channel 0, id 1, lun 0
sda : READ CAPACITY failed.
sda : status = 0, message = 00, host = 0, driver = 28
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
/dev/scsi/host0/bus0/target1/lun0: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 2097144
I/O error: dev 08:00, sector 2097144
I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
ldm_validate_partition_table(): Disk read failed.
I/O error: dev 08:00, sector 0
unable to read partition table
Device not ready. Make sure there is a disc in the drive.
VFS: Disk change detected on device 08:00
sda : READ CAPACITY failed.
sda : status = 0, message = 00, host = 0, driver = 28
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
/dev/scsi/host0/bus0/target1/lun0: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 2097144
I/O error: dev 08:00, sector 2097144
I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
ldm_validate_partition_table(): Disk read failed.
I/O error: dev 08:00, sector 0
Aha! If your zip drive is being reported as scsi on cdrecord -scanbus, then it will be your zip drive that is sda! Try doing the same thing but with sdb! Check your fstab to see which device your zip drive is.
you need the bpck-usb-firmware-1.1-1.noarch.rpm, you can find it off the web, it goes to the vendor site...
however.... while there is no "-17" for mandrake there are later versions that can be accepted...
HOWEVER....
using a later hotplug rpm might knock out your eth0 ability. with me, i always had to issue a 'service network restart' after signing in and i could never figure out why... it appears using a later hotplug was causing me some greif. i tried using the latest and greatest but then i have to install a bunch of shit.... i shouldn't have to do that....
it's tempting to download the source for backpack and try to figure it out from there, but the other problem is that i think, after 5 years of faithful service, my backpack cd-rewriter is starting to konk out on me....
time for a new cdrw i think,
any suggestions on a decent external cd-rw for Linux....?
on rpmfind.net i found a mandrake hotplugger (hotplug-2002_04_01-8mdk.src.rpm) but the backpack driver doesn't like it, it still is asking for 2002_04_01-17
any ideas? does anyone know of a way to manually mount a usb device through mandrake? do I absolutely need this stupid backpack driver?
Also, the drive has a paralell port...how about to manually mount it through a paralell?
Any help would be appreciated...it's been six months and still i've got nothing...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.