On Wed, Oct 12, 2005 at 11:41:05PM +0200, Francesco Poli wrote: > On Wed, 12 Oct 2005 15:41:27 +0900 Horms wrote: > > > On Sun, Oct 09, 2005 at 07:10:24PM +0200, Francesco Poli wrote: > [...] > > > # mount -t ext2 /dev/fd0 /media/floppy/ > > > mount: /dev/fd0 is not a valid block device > > > # ls -altrF /dev/fd0 > > > brw-rw---- 1 root floppy 2, 0 Feb 26 2005 /dev/fd0 > > > # tail -3 /var/log/kern.log > > > [...] oldbox kernel: inserting floppy driver for 2.6.8-2-386 > > > [...] oldbox kernel: Floppy drive(s): fd0 is 1.44M > > > [...] oldbox kernel: floppy0: Floppy io-port 0x03f2 in use > > > > > > But io-port 0x03f2 does not seem to be in use: > > > > > > # cat /proc/ioports > [...] > > Are you sure that the drive is actually at 0x03f2? > > How can I check this? > Is that a hardware setting (such as a jumper or something) you're > referring to?
It is usually set in the BIOS IIRC. > [...] > > > What can I do? > > > > It seems like a fairly specialised problem, but fortunately due > > to the beuaty of free software you have all the information > > you need to resolve the problem yourself. > > The beauty of free software is also a community of users helping each > other... :-/ > Unfortunately IANAKH (I Am Not A Kernel Hacker) and thus I'm afraid I > don't have enough knowledge to solve the problem all by myself... :-( Indeed, we are all helping each other :-) > Any suggestions on what I could look for (so that I don't have to review > every and each line of code of the Debian sarge base system)? Well, its almost certainly a kernel/hardware interaction. So you can safely stick to looking at the kernel. A good place to start would be to compare the information you posted on a working kernel, with the non-working one. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
