FedoraThis forum is for the discussion of the Fedora Project.
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.
where the 'sda1' is different because windows is on hda1? This used to work, now it doesn't. How can I tell if my usb port is working? I plug my flash drive in and it keeps saying 'sda1 is not a valid block device'. What do I need to do?
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Well after you plug in the USB device as root check the /var/log/messages file;
tail /var/log/messages
Adjust the /etc/fstab entry as needed. If you do not get any report about the USB drive being connected then make sure the usb drivers are being loaded;
Hi and thanks for the reply.
I'm still having trouble with this. Checking messages showed no change, and indeed the light on the flash drive doesn't go on like it should. I'm guessing the drivers for some reason aren't installed?(they worked before)The 'cat' commanded just returned a line; no results I guess. What can I do now? I think yum showed I have usbutils and others installed...
ps. the fstab i have: /dev/sda1 /mnt/flash vfat noauto,owner,kudzo 0 0 It is sometimes overwritten(erased) when I reboot though :/
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Turn off the service kudzu, it causes more problems then it solves.
chkconfig --level 345 kudzu off
Your /etc/fstab entry would be better if changed slightly;
/dev/sda1 /mnt/flash vfat noauto,user,rw 0 0
The drive light should work if the usb port has power and nothing else is wrong. This is true even if the usb modules do not load. Check you BIOS maybe the usb ports are disabled, maybe the usb port(s) or usb interface(s) on the motherboard have gone bad. It might be something related to the usb interface of the usb enclosure.
Thanks for the reply. The drive light works in windows and even lights up when I run the linux rescue disk. So it has to be related to the drivers or something like that once FC2 loads.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Why are you still running FC2, it is old and has no support??? Any good reason to????
As a suggestion try something that is supported like CentOS or SL. both are freely available 100% binary compatible 'clones' of RHEL.
With that said try manually loading the usb modules before attaching the usb device;
modprobe -v <usb_module_name_here>
Use the typed command 'sbin/lspci -v' minus the single quotemarks to assist you with which usb interfaces you have. The kernel module names can be found in the directory /lib/modules/<kernel-version-number-here>/kernel/drivers/usb/host
At this point I just want to get the stupid USB flash working so I can save my info and then,
yes I'll upgrade. Thanks for hanging in there with me. I'll try these new suggestions and get back with ya.
I did watch the boot up closer and it does indeed appear that the usb controller doesn't load properly(says it fails), though I know it worked earlier and works fine in Windows.
After issuing the lspci command I found:
00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB (rev 06) (prog-if 10 [OHCI])
Flags: bus master, medium devsel, latency 16, IRQ 10
Memory at febff000 (32-bit, non-prefetchable)
Under usb folder:
ls
atm class host image input media misc net serial storage
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Please run (exactly as provided, feel free to cut and paste) the command I provided from the console or xterm session, it will tell you if the ohci-hcd kernel module is present or not. If you get nothing back then something is wrong, then re-install the kernel;
rpm -ivh kernel-<the_rest>.rpm --force
The kernel module is in the last updated kernel for FC2, for example;
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Your welcome, but it not really fixed. It would be a good idea to find out why the kernel module is not being loaded at boot time. Start by checking the /etc/modprobe.d/modprobe.conf.dist and /etc/modprobe.conf for any recent changes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.