Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
greetings all, the problem I am having is with my western digital 250gig firewire drive. I'm running slackware 10.0 and everything except this works great. Slackware is installed on the main HD, it's just a slack box, no dual booting. When I installed slack from the ISO images, I can cfdisk /dev/sda and it sees the firewire drive, I can also install onto the drive so I know that it can see it, and it works. However, once I was done installing everything on the main drive, and rebooted, logged in etc. linux can't see the firewire drive anymore. it says
FATAL ERROR: Cannot open disk drive. Press any key to exit cfdisk.
the firewire disk is formatted in ext2 so it's not that. Is there a command that can probe the drive, or check if the modules are working currently. insmod yields this
Code:
root@toast:/home/mike# insmod ieee1394
Using /lib/modules/2.4.26/kernel/drivers/ieee1394/ieee1394.o.gz
insmod: a module named ieee1394 already exists
and
Code:
root@toast:/home/mike# insmod ohci1394
Using /lib/modules/2.4.26/kernel/drivers/ieee1394/ohci1394.o.gz
insmod: a module named ohci1394 already exists
so they are there, just don't know why it does not see it. any ideas?
msober; from the two codes seems that they be in conflict with each other.
according to what ur post says, exit cfdisk, meaning close it & ieee1394, ohci 1394 already exist, take a close look at them again see which one could be disabled or deleted without disturbing dependancies.
Thank you for the response. Although I have not been able to get the firewire drive working on the 2.4.* kernel, I am running it fine w/ the 2.6.7 kernel.
There is something mysterious about the Maxtor 200GB firewire drive. This is my fstab file, Note that FC2 will not mount or even recognize the firewire connection. When I mount sda1 the terminal window freezes and I have to kill the thread manually. Knoppix and Mandrake recognized immediately and auto mounted. Any ideas?
misterfixit; the ends of listings on post appear not to have permission
0 believe should have a value. that comes from ur root giving permission to r-w-x. whcih non is indicated. ???? why not may have overlooked entering those permissions? check that out.
Originally posted by penguin4 misterfixit; the ends of listings on post appear not to have permission
0 believe should have a value. that comes from ur root giving permission to r-w-x. whcih non is indicated. ???? why not may have overlooked entering those permissions? check that out.
penguin4 -- as you know the fstab file specifies which partitions should be automatically mounted at bootup time, and you should also know that in terms of controlling which access permissions are granted, there really only 2 mount options that are used: ro and rw. "ro" stands for read-only, and "rw" stands for read-write. Your reply indicated that the "r-w-x" option should have been specified, and implied that the fstab file should be modified. This is an interesting recommendation and I'm curious as to what your fstab file looks like. Can you post it here? Does it include the same permission settings that you are recommending? -- J.W.
Misterfixit: What kernel are you using? 2.4.x kernel does not have firewire added by default. (on slack) so you may have to recompile before it works. Also, have you tried unplugging and then replugging the drive then type
Code:
dmesg | less
this is my fstab for the firewire hd (mine is a WD 250gig)
jw; from the original post of msober, didn,t mention fstab. so only suggested what was posted originally. attempted to point where to begin undoing & redoing what poster missed.
so from no on will not attempt to assist any body if not familiar with
question nor know answer! thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.