Bug 75687
Summary: | Running standard RH 8.0 kernel-2.4.18-14 on ASUS P4T-E motherboard. dmesg reports "Floppy drive(s): fd0 is 1.44M floppy0: no floppy controllers found" Can access floppy using kernel rebuilt with floppy as a module. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael Kearey <mutk> | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 8.0 | CC: | haxor86, manschke, pward | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2003-03-07 05:37:07 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Michael Kearey
2002-10-11 02:35:17 UTC
Created attachment 79884 [details]
Output of dmidecode for my ASUS P4T-E motherboard
I have identical issue - RH 8.0, P4T-E, floppy controller not found, even though it was recognised during install - I created a boot disk The same happens with me; note, SuSE does the same, but Mandrake will work (even though you have to get oss for the built in sound mobo's)! Reason unknown... The new kernel-2.4.18-26.8.0 *appears* to resolve the problem. I am happy now that I can run the out of box RH kernel and access floppy drive now... oh? I just upgraded my kernel in hopes of it working, but I still have no floppy support. Sure you didn't do anything special? mount /dev/fd0 /mnt/floppy mount: /dev/fd0 is not a valid block device (P4T-E Socket 478 P4 Motherboard; Intel 850 Chipset) Definately "WORKSFORME". Although I did get the "mount: /dev/fd0 is not a valid block device" error once, changed to a known good floppy, and it was ok. Note the original problem is that kernel would not recognise or find a floppy controller. ie you would be getting "floppy0: no floppy controllers found" line in dmesg. Also, instead of "mount: /dev/fd0 is not a valid block device" you would be getting "mount: can't find /mnt/floppy in /etc/fstab or /etc/mtab" - as if there is no floppy drive at all. I suspect that you have a bad floppy disk. Try changing to a known good one, or format the floppy again. Current Kernel: uname -a Linux XXXXXXXX 2.4.18-26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 GNU/Linux dmidecode is as per attachement of original bug post. mount /mnt/floppy/ mount /dev/hda2 on / type ext3 (rw) none on /proc type proc (rw) usbdevfs on /proc/bus/usb type usbdevfs (rw) /dev/hda1 on /boot type ext3 (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /dev/shm type tmpfs (rw) /dev/fd0 on /mnt/floppy type vfat (rw,nosuid,nodev) ls /mnt/floppy/ boot.msg initrd.img options.msg rescue.msg splash.lss syslinux.png general.msg ldlinux.sys param.msg snake.msg syslinux.cfg vmlinuz It works ... Cheers, Michael |