On Mon, Jul 26, 2004 at 05:12:33PM -0700, Nate Lawson wrote: > Marcel Moolenaar wrote: > >On Mon, Jul 26, 2004 at 03:20:35PM -0700, Nate Lawson wrote: > > > >>Ok, below is a patch to address this. There are two things this fixes. > >>The first, which I think Marcel's laptop had from the dmesg I saw, is > >>that _FDI is not required so a system may have child devices of FDC that > >>lack an _FDI method. > > > >Yup. That seems to be resolved: > > > >fdc0: <floppy drive controller (FDE)> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 > >on acpi0 > > > >However, no fd0. Hence no /dev/fd0. With FDC_DEBUG I get: > > : > >[0x3->FDDATA][0xdf->FDDATA][0x2->FDDATA][0x10->FDDATA][FDDATA->0x90] > > : > >[fdc0 IDLE] > > : > > > >And that's it... > > That's weird. Is your floppy drive plugged in? But you're saying that > the fd0 enumeration is fixed (i.e. devinfo shows fd0 present)? > > Perhaps the drive type is not being probed correctly? Drive is plugged in. fd0 enumeration is not fixed. From devinfo: fdc0 pnpinfo _HID=PNP0700 _UID=0 at handle=\_SB_.PCI0.LPC0.FDC_ Interrupt request lines: 0x6 DMA request lines: 2 I/O ports: 0x3f0-0x3f5 0x3f7 fd4 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.LPC0.FDC_.FDD_ >From acpidump: : Device (FDC) { Name (_HID, EisaId ("PNP0700")) Name (MCD, 0x11) : Device (FDD) { Name (_ADR, 0x00) Name (_EJD, "_SB.DOCK") : } } : -- Marcel Moolenaar USPA: A-39004 marcel_at_xcllnt.netReceived on Mon Jul 26 2004 - 22:33:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:03 UTC