I've upgraded one machine to 2.0.32 5 days ago, and have been testing
it. It appears that the floppy drive functions are fixed, and I haven't
seen (yet) any of the other "glitches" that others have seen with the
new kernel.
(cross my fingers)
I have noticed that sometimes, I still get a DMA error with the floppy
and it says /dev/fd0 isn't a valid block device. However, I can execute
the same command right away and it will work the second time (and a
third and a forth, etc).
Still not as reliable as 2.0.29 was, but better than 2.0.30.
Brian
P.S. If that's not enough reason to change kernels, 2.0.32 fixed a lot
of the memory allocation problems too I've seen. And Apache runs much
better now. Whether you go forward or backwards, I'd advise moving off
of 2.0.30.
Mike Bristow wrote:
>
> Hi,
>
> On 26-Nov-97 Sam wrote:
> [snip]
> > Well, I've been running 2.0.30 fine, and with my previous motherboard this
> > has never happened. If I wait about 10-15 minutes, I can access the
> > floppy again, so a reboot is not necessary.
>
> Are you using the floppy stuff as a module? If so a rmmod floppy as root might
> reduce the waiting time somewhat.
>
> ---
> Mike Bristow - mike@shivan.demon.co.uk
>
> Linux! Guerrilla UNIX Development Venimus, Vidimus, Dolavimus.
> (By mah@ka4ybr.com, Mark A. Horton KA4YBR)