Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
You could try the following:
- check the output of "dmesg"; here you find which devices are recognized at boot time
- check if bios settings are OK for this drive (some people actually forget this when they install other drives...)
- Is floppy disk support enabled in the kernel? (think it's somewhere under block device drivers in the menu)
- is the /dev/fd0 special file present? Since you get this "invalid arg." message, maybe it's missing...
... ide-floppy driver 0.99.newide
microcode: No suitable data for cpu 0
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected inserting floppy driver for 2.6.7 Floppy drive(s): fd0 is 1.2M
FDC 0 is a post-1991 82077
8139too Fast Ethernet driver 0.9.27
divert: allocating divert_blk for eth0
BIOS Settings.... i did check'em twice... now a third time...!!
/dev/fd0 special file present... i guess it is because it reads
the disk but it won't mount it because of the block device
i believe the floppy is supported in the kernel... but i'm checking again...
when i try to mount the drive, the led turns on...
and then the shell gives me the error...
>> does the drive's LED light up when you try mounting the disk?
yes it does...
>> try dd'ing a few bytes out?
how do i do this!??
>> Does it show any sign of activity?
yes, it spins... when accessing the drive!!
btw, i forgot to mention that the cable that goes to the mb is not
a regular floppy one, the connector that goes to the M/B it does looks
like a floppy but at the other end it looks like a pci connector(not really)...
is this causing a problem!?? and on the old pc that i removed the drive
from it has all the pins on the floppy connector while my M/B(ASUS) is
missing one pin you know the standard...