No /dev/fd0 after upgrade

Birdman · 2006-10-01 22:01:06

I read the udev readme after the upgrade and have no problems with CDROM, CDRW and USB Key. I do not have a /dev/fd0 though. The default entry in /etc/udev/rules.d/udev.rules is:

# floppy devices
KERNEL=="fd[0-9]*", NAME="fd%n", SYMLINK+="floppy/%n fd%nu1440 fd%nu720 fd%nh120
0 fd%nu360", GROUP="floppy"

And my /etc/fstab has remained unchanged:

/dev/fd0               /mnt/fl   vfat      users,noauto             0      0

What do I need to do to get my floppy back?

Thanks.

Snowman · 2006-10-02 00:31:22

Is the module loaded? I think it's ide-floppy.

Birdman · 2006-10-02 11:10:45

Snowman wrote:

Is the module loaded? I think it's ide-floppy.

I will take a look this evening. Any ideas why it might not be loaded after the upgrade?

Birdman · 2006-10-02 18:14:47

ide_floppy was not loaded. I have added it to the /etc/rc.conf file and rebooted and it is now loaded. Now the bad news - /dev/fd0 is still not being created I assume it is a udev rules thing?

jourdan · 2006-10-03 01:36:26

same problem here.

I couldn't access the floppy through Gnome for the longest time, though prior to this latest upgrade I could still Autofs to it. Now it just plain doesn't exist.

A similar, possibly related problem is accessing my Zip100 drive. With the UDEV defaults, Gnome detects but won't mount. Writing a custom UDEV rule for hdd that creates a symlink to "hdd4" causes Gnome to be able to mount the drive, but it's then registered as a USB disk and I get two icons in Gnome - one for the ZIP and one for the USB. I can mount/unmount by right-clicking the ZIP icon, and I can access the zip disk by double-clicking the USB disk icon (but I can't unmount using the USB icon). It's quite a confusing experience! Autofs works fine on the ZIP drive.

I suspect the floppy problem is a kernel thing, but with my schedule digging into that isn't something I can do right now. Anyone know anything?

Maybe we could kill Gnome's dependency on HAL and just use AutoFS-controlled directories?

jourdan · 2006-10-03 01:49:28

:shock:

Just noticed that the light on my ide floppy is permanently ON, like it's trying to read something. Persists across reboots. This started after the last

pacman -Syu

I've added ide_floppy to the modules array to see what that'll do. The fact that the drive is in a constant "read" state can't be good!

jourdan · 2006-10-03 02:47:08

Update: Adding the 'ide_floppy' module to the modules array in rc.conf caused the light to go out on my ide_floppy drive, which is a good thing to be sure, but otherwise /dev/fd0 still does not appear.

Birdman · 2006-10-03 12:06:15

jourdan wrote:

Update: Adding the 'ide_floppy' module to the modules array in rc.conf caused the light to go out on my ide_floppy drive, which is a good thing to be sure, but otherwise /dev/fd0 still does not appear.

I think we are pretty much in the same position now. I am running KDE, though do have Gnome installed. I don't actually know anything about HAL (does that mean that I am not using it?) and do not use Autofs. I usually mount the floppy either via the icon or via the shell.

Snowman · 2006-10-03 12:53:17

I don't have a floppy drive so I can't test but I think that /dev/fd0 is a symlink pointing to the actual floppy device. You could look in /dev to see if there's a device that looks like a floppy device (from udev rules it should be /dev/floppy/0 or similar). Maybe for some reason udev doesn't create the symlink anymore. Recently udev has changed the way it handles CD/DVD symlinks so perhaps symlinks for floppy was broken.

mico · 2006-10-03 14:22:23

After upgrade, the only thing in /dev that looks (by its filename) something like floppy to me is /dev/fd

# ls -lhd /dev/fd
lrwxrwxrwx 1 root root 13 2006-10-03 13:43 /dev/fd -> /proc/self/fd
# ls -l /dev/fd/
total 4
lrwx------ 1 root root 64 2006-10-03 16:14 0 -> /dev/pts/0
lrwx------ 1 root root 64 2006-10-03 16:14 1 -> /dev/pts/0
lrwx------ 1 root root 64 2006-10-03 16:14 2 -> /dev/pts/0
lr-x------ 1 root root 64 2006-10-03 16:14 3 -> /proc/3879/fd

which is obviously not the floppy device.

As others have noticed, the ide_floppy module is not autoloaded. But even modprobing ide_floppy does not add any file to /dev.

m123 · 2006-10-03 16:37:17

Is the module loaded? I think it's ide-floppy.

I think it is only "floppy" (see http://www.archlinux.org/news/259/).

I generated my mkinitcpio images with that and it works fine under kde and almost fine with the new gnome (although there is a strange behaviour there for which I filed a bug).

CavalierBob · 2006-10-03 17:53:52

Michel F wrote:

Is the module loaded? I think it's ide-floppy.
I think it is only "floppy" (see http://www.archlinux.org/news/259/).
I generated my mkinitcpio images with that and it works fine under kde and almost fine with the new gnome (although there is a strange behaviour there for which I filed a bug).

Thanks for pointing us to the solution Michel F!

I just added 'floppy' to MODULES in rc.conf, reboot, and now my floppy mountable. The floppy doesn't seem to want to automount in Gnome, which I thought would be normal behavior. I have the Preferences set to 'mount removable media when inserted'. Is that related ti the bug you filed?

Bob

Birdman · 2006-10-05 21:27:30

Thanks from me too. I have my floppy back

Slash · 2006-10-11 21:48:16

CavalierBob wrote:

The floppy doesn't seem to want to automount in Gnome, which I thought would be normal behavior. I have the Preferences set to 'mount removable media when inserted'. Is that related ti the bug you filed?
Bob

I don't use Gnome, but I noticed that the permissions of fd0 by default are this:

brw-rw---- 1 root floppy 2, 0 2006-10-11 17:31 /dev/fd0

So your user should probably be added to the "floppy" group (or any user that wants to use the floppy).

gpasswd -a yourusername floppy

Then logout and log back in (which requires you to restart X). I did this and I was able to write to /dev/hd0 (with "dd"... I was writing a floppy image).

Arch Linux

#1 2006-10-01 22:01:06

No /dev/fd0 after upgrade

#2 2006-10-02 00:31:22

Re: No /dev/fd0 after upgrade

#3 2006-10-02 11:10:45

Re: No /dev/fd0 after upgrade

#4 2006-10-02 18:14:47

Re: No /dev/fd0 after upgrade

#5 2006-10-03 01:36:26

Re: No /dev/fd0 after upgrade

#6 2006-10-03 01:49:28

Re: No /dev/fd0 after upgrade

#7 2006-10-03 02:47:08

Re: No /dev/fd0 after upgrade

#8 2006-10-03 12:06:15

Re: No /dev/fd0 after upgrade

#9 2006-10-03 12:53:17

Re: No /dev/fd0 after upgrade

#10 2006-10-03 14:22:23

Re: No /dev/fd0 after upgrade

#11 2006-10-03 16:37:17

Re: No /dev/fd0 after upgrade

#12 2006-10-03 17:53:52

Re: No /dev/fd0 after upgrade

#13 2006-10-05 21:27:30

Re: No /dev/fd0 after upgrade

#14 2006-10-11 21:48:16

Re: No /dev/fd0 after upgrade

Board footer