Re: i need my floppy disk drive.

is it safe to upgrade to current when i'm used to -release ?


dmesg:

FreeBSD 5.2.1-RELEASE-p9 #3: Thu Jul  8 16:09:39 CEST 2004
    h_at_insomnia.erathia:/usr/obj/usr/src/sys/INSOMNIA
Preloaded elf kernel "/boot/kernel/kernel" at 0xc09cd000.
Preloaded elf module "/boot/kernel/linux.ko" at 0xc09cd244.
Preloaded elf module "/boot/modules/nvidia.ko" at 0xc09cd2f0.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 1900+ (1595.28-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
  Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
  AMD Features=0xc0400000<AMIE,DSP,3DNow!>
real memory  = 536805376 (511 MB)
avail memory = 511762432 (488 MB)
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 9 entries at 0xc00f7fe0
pcib0: <Host to PCI bridge> at pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pci_cfgintr: 0:13 INTA BIOS irq 10
pci_cfgintr: 0:16 INTA BIOS irq 11
pci_cfgintr: 0:16 INTB BIOS irq 10
pci_cfgintr: 0:16 INTC BIOS irq 10
pci_cfgintr: 0:16 INTD BIOS irq 3
pci_cfgintr: 0:18 INTA BIOS irq 11
agp0: <VIA Generic host to PCI bridge> mem 0xe0000000-0xe3ffffff at device 0.0 
on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci_cfgintr: 0:1 INTA routed to irq 11
pcib1: slot 0 INTA is routed to irq 11
nvidia0: <Unknown> mem 0xd0000000-0xd7ffffff,0xde000000-0xdeffffff irq 11 at 
device 0.0 on pci1
pcm0: <Creative EMU10K1> port 0xe800-0xe81f irq 10 at device 13.0 on pci0
pcm0: <SigmaTel STAC9708/11 AC97 Codec>
uhci0: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 11 at device 16.0 on 
pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 10 at device 16.1 on 
pci0
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 16.2 on 
pci0
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0: <serial bus, USB> at device 16.3 (no driver attached)
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 8235 UDMA133 controller> port 0xfc00-0xfc0f at device 17.1 on 
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xd800-0xd8ff mem 
0xdffffe00-0xdffffeff irq 11 at device 18.0 on pci0
vr0: Ethernet address: 00:e0:18:d3:44:6f
miibus0: <MII bus> on vr0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
orm0: <Option ROM> at iomem 0xc0000-0xcf7ff on isa0
pmtimer0 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: IEEE1284 device found /NIBBLE
Probing for PnP devices on ppbus0:
ppbus0: <Hewlett-Packard LaserJet 4L> HP ENHANCED PCL5,PJL
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0401> can't assign resources (port)
unknown: <PNP0700> can't assign resources (port)
unknown: <PNP0f13> can't assign resources (irq)
Timecounters tick every 10.000 msec
GEOM: create disk ad0 dp=0xc48e1960
ad0: 76324MB <Maxtor 6Y080L0> [155072/16/63] at ata0-master UDMA133
acd0: DVDROM <HL-DT-STDVD-ROM GDR8162B> at ata1-master PIO4
acd1: CDRW <YAMAHA CRW2200E> at ata1-slave PIO4
Mounting root from ufs:/dev/ad0s1a


On Friday 09 July 2004 19:43, you wrote:
> On Fri, Jul 09, 2004 at 03:13:48PM +0200, h wrote:
> > i'm using 5.2.1-RELEASE-p9 but have been told to post to the current
> > mailing list about this issue.
> >
> > several of us from freenode #freebsd have been pulling our hair off
> > trying to get our floppy disk drive to work. at some point jer told he's
> > had the flaw with his machines for over a year since the early 5.1.
> >
> > basically i can't mount my floppy drive. with ACPI on my kernel couldn't
> > even detect the floppy controller. ever since i removed acpi now my
> > kernel sees the controller:
> >
> > # dmesg|grep fd
> > fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port
> > 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
> > fdc0: FIFO enabled, 8 bytes threshold
> >
> > but the fd0 or fdc0 isn't in /dev, there's only a fd/ dir:
> >
> > ls /dev/f*
> > 0       1       2
> >
> > so the floppy disk drive is still invisible. i recently replaced my drive
> > with a drive and its cable known to work on another machine.
>
> Could you provide the whole dmesg?  There should be some sort of error
> if the device made it that far and then didn't show up in /dev since
> /dev is devfs now.
>
> > i have offline machines with no burner for which i need the floppy disk
> > to communicate with. if 4- can do it why wouldn't 5- ?
>
> Overall, it sounds like you have resource allocation or discovery
> problems.  Many of these have been fixed in -current.  You should
> probably try updating.
>
> Do those machines have USB?  If so, a keychain drive is a much better
> option then a floppy.
>
> -- Brooks