Bug 105455

Summary: device node /dev/fd0 missing on x86-64
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Sebastian Vollath <svollath>
Component: HotplugAssignee: Hannes Reinecke <hare>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Major    
Priority: P5 - None CC: dkukawka, ihno, snwint
Version: Beta 2   
Target Milestone: ---   
Hardware: x86-64   
OS: All   
Whiteboard:
Found By: Component Test Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 97395    
Attachments: /var/log/YaST2 directory
hwinfo

Description Sebastian Vollath 2005-08-18 10:40:06 UTC
There is no device /dev/fd0 after installation on x86-64.
Comment 1 Sebastian Vollath 2005-08-18 10:41:24 UTC
Created attachment 46455 [details]
/var/log/YaST2 directory
Comment 2 Klaus Kämpf 2005-08-18 10:41:50 UTC
Dynamic /dev ?!  
 
Please attach output of hwinfo 
Comment 3 Sebastian Vollath 2005-08-18 10:42:23 UTC
Created attachment 46456 [details]
hwinfo
Comment 4 Klaus Kämpf 2005-08-18 10:50:41 UTC
Hmm, hwinfo finds a floppy but it does not appear in the HAL device list at 
the beginning of hwinfo output. 
 
HAL problem ? 
Comment 5 Timo Hoenig 2005-08-18 10:59:57 UTC
Possibly. Can I access the machine?
Comment 6 Sebastian Vollath 2005-08-18 11:03:51 UTC
Yes, you can log on to f100.suse.de, where I already added fd0 with mknod, or
you better use merkur.suse.de, which is still untouched.
Comment 7 Timo Hoenig 2005-08-18 11:14:09 UTC
Looks like an udev issue. 

Once the device is present, hal finds the floppy entries in /sys.
Comment 8 Steffen Winterfeldt 2005-08-18 11:44:06 UTC
Or try f174. 
Comment 9 Timo Hoenig 2005-08-18 11:57:17 UTC
I'm not familiar with udev, yet. I *think* it would be reasonable to debug this problem by enabling 
verbose logging for udev on a x86 machine with a floppy attached and track down the udev rule 
which triggeres the creation of /dev/fdX.  Once this is clear, it should be possible to solve the problem 
on x86_64.
Comment 10 Steffen Winterfeldt 2005-08-18 12:12:29 UTC
Isn't the problem on amd64 that the floppy module is not loaded? 
Or is udev supposed to do that? 
Comment 11 Timo Hoenig 2005-08-18 12:16:13 UTC
Yes.

I suppose you haven't mknod'ed /dev/fd0 on f174 but simply loaded the floppy moule, right?
Comment 12 Steffen Winterfeldt 2005-08-18 12:30:00 UTC
exactly 
Comment 13 Hannes Reinecke 2005-08-18 12:43:20 UTC
It is an udev issue. New version submitted to autobuild.
Comment 14 Timo Hoenig 2005-08-18 12:53:18 UTC
Good.

But one last thing:

Wouldn't it be good having the floppy driver as module on both, x86 and x86_64?

We could probe it once at installation time. Only if a floppy is present we load it afterwards, too.

Since many systems are shipped without a floppy drive these days, I do not see a good reason for 
compiling this driver into the kernel.