Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 50 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff vt0: not probed (disabled) isa_probe_children: probing PnP devices adv1: Invalid baseport of 0x80 specified. Nearest valid baseport is 0x100. Failing probe. From: Jun Kuriyama [EMAIL PROTECTED] To: Stephane Raimbault [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R Date: Tue, 04 Nov 2003 07:53:18 +0900 At Mon, 3 Nov 2003 17:47:59 + (UTC), Stephane Raimbault wrote: autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... I meant to use -v at above. Hit any key at this 10 seconds waiting, and type boot -v and enter at prompt. -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photospgmarket=en-caRU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
floppies
anyone else having trouble with floppies? I tried a bunch of different disks in two different machines (5.1-CURRENT with brand new drive, 4.9-PRERELEASE with an older but presumed-good drive) and all I get are I/O errors; fdformat sometimes works and sometimes doesn't, and any attempt to actually read or write data fails. # uname -a FreeBSD ada.des.no 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Fri Sep 5 22:56:22 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/ada i386 # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing fdformat: ioctl(FD_FORM): Input/output error # dd if=/dev/zero of=/dev/fd0c dd: /dev/fd0c: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 2.634334 secs (0 bytes/sec) and the console shows: fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0 last message repeated 2 times fd0: recal failed ST0 78abnrml,seek_cmplt,equ_chck,drive_notrdy cyl 0 fd0c: hard error writing fsbn 0 (No status) on -CURRENT: # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing VEVV done. Errors encountered: Cyl Head Sect Error 661 12 wrong cylinder (format mismatch) (although a previous run succeeded) I'm having a hard time believing this is a hardware problem, although there might conceivably be an environmental factor which affects both systems since they are in the same room. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: floppies
No problem with formatting or writing floppies here under heavy system load and even though this message--fdc0: cmd 3 failed at out byte 1 of 3--has been output twice at boot for probably over a year. The floppies I used even came from a dusty pile of old driver disks. :-) Pete... Dag-Erling Smørgrav wrote: anyone else having trouble with floppies? I tried a bunch of different disks in two different machines (5.1-CURRENT with brand new drive, 4.9-PRERELEASE with an older but presumed-good drive) and all I get are I/O errors; fdformat sometimes works and sometimes doesn't, and any attempt to actually read or write data fails. # uname -a FreeBSD ada.des.no 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Fri Sep 5 22:56:22 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/ada i386 # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing fdformat: ioctl(FD_FORM): Input/output error # dd if=/dev/zero of=/dev/fd0c dd: /dev/fd0c: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 2.634334 secs (0 bytes/sec) and the console shows: fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0 last message repeated 2 times fd0: recal failed ST0 78abnrml,seek_cmplt,equ_chck,drive_notrdy cyl 0 fd0c: hard error writing fsbn 0 (No status) on -CURRENT: # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing VEVV done. Errors encountered: Cyl Head Sect Error 661 12 wrong cylinder (format mismatch) (although a previous run succeeded) I'm having a hard time believing this is a hardware problem, although there might conceivably be an environmental factor which affects both systems since they are in the same room. DES ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: floppies
On Monday 03 November 2003 09:50, Dag-Erling Smørgrav wrote: anyone else having trouble with floppies? I tried a bunch of different disks in two different machines (5.1-CURRENT with brand new drive, 4.9-PRERELEASE with an older but presumed-good drive) and all I get are I/O errors; fdformat sometimes works and sometimes doesn't, and any attempt to actually read or write data fails. I can confirm that. See this attached posting from 13. October 2003 -Harry # uname -a FreeBSD ada.des.no 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Fri Sep 5 22:56:22 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/ada i386 # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing fdformat: ioctl(FD_FORM): Input/output error # dd if=/dev/zero of=/dev/fd0c dd: /dev/fd0c: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 2.634334 secs (0 bytes/sec) and the console shows: fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0 last message repeated 2 times fd0: recal failed ST0 78abnrml,seek_cmplt,equ_chck,drive_notrdy cyl 0 fd0c: hard error writing fsbn 0 (No status) on -CURRENT: # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing VEVV done. Errors encountered: Cyl Head Sect Error 661 12 wrong cylinder (format mismatch) (although a previous run succeeded) I'm having a hard time believing this is a hardware problem, although there might conceivably be an environmental factor which affects both systems since they are in the same room. DES ---BeginMessage--- Hi all, dmesg doesn't show anything unusual but trying to mount disks known to be good results in mount: /dev/fd0: Input/output error. Also fdformat does not work. It shows me every sector bad. Btw: How can I format a floppydisk in a USB-drive? fdformat /dev/da0 doesn't work. The USB-drive is fine, also is the standard floppy drive. I'm running FreeBSD 5.1-CURRENT #20: Sun Oct 12 23:31:45 CEST 2003 Thanks, -Harry pgp0.pgp Description: signature ---End Message--- pgp1.pgp Description: signature
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
at device 2.0 (no driver attached) pci3: network, ethernet at device 2.1 (no driver attached) pcib4: PCIBIOS PCI-PCI bridge at device 3.0 on pci0 pci4: PCI bus on pcib4 pci4: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib5: PCIBIOS PCI-PCI bridge at device 29.0 on pci4 pci5: PCI bus on pcib5 pci4: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib6: PCIBIOS PCI-PCI bridge at device 31.0 on pci4 pci6: PCI bus on pcib6 pci_cfgintr: 6:1 INTA BIOS irq 12 asr0: Adaptec Caching SCSI RAID mem 0xfc00-0xfdff,0xfb00-0xfbff,0xf840-0xf84f irq 12 at device 1.0 on pci6 asr0: major=154 asr0: ADAPTEC 2010S FW Rev. 3B05, 2 channel, 256 CCBs, Protocol I2O uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x2000-0x201f irq 11 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x2020-0x203f irq 10 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x2040-0x205f irq 5 at device 29.2 on pci0 usb2: Intel 82801CA/CAM (ICH3) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib7: PCIBIOS PCI-PCI bridge at device 30.0 on pci0 pci7: PCI bus on pcib7 pci_cfgintr: 7:1 INTA BIOS irq 11 pci7: display, VGA at device 1.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 UDMA100 controller port 0x2060-0x206f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: serial bus, SMBus at device 31.3 (no driver attached) orm0: Option ROMs at iomem 0xe-0xe3fff,0xdc000-0xd,0xc9000-0xcefff,0xc8000-0xc8fff,0xc-0xc7fff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 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 fd0: 1440-KB 3.5 drive on fdc0 drive 0 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 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Thanks, Stephane. From: Jun Kuriyama [EMAIL PROTECTED] To: Stephane Raimbault [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R Date: Sat, 01 Nov 2003 15:41:36 +0900 At Fri, 31 Oct 2003 16:56:43 + (UTC), Stephane Raimbault wrote: Does anyone have any thoughts regarding this? I would like to get 5.1 on this server. How about trying with -v at boot? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcommpgmarket=en-caRU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
At Mon, 3 Nov 2003 17:47:59 + (UTC), Stephane Raimbault wrote: autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... I meant to use -v at above. Hit any key at this 10 seconds waiting, and type boot -v and enter at prompt. -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
Does anyone have any thoughts regarding this? I would like to get 5.1 on this server. Thank you, Stephane Raimbault. - Original Message - From: Stephane Raimbault [EMAIL PROTECTED] Newsgroups: mailing.freebsd.current Sent: Wednesday, October 29, 2003 4:07 PM Subject: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R Hi, I'm trying to install 5.1-R or 5.1-C from floppies redirected output to = serial port and it won't boot to the install screen. 4.9-R floppies = with output redirected to serial port works and installs properly. This = is what I get on my serial console when I try to boot on 5.1-C (similar = to 5.1-R) seems to hang after the vga0 shows up during boot. Is there anything I can do or provide to resolve my install problem? Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 633kB/4061120kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Wed Oct 29 04:14:01 GMT 2003) include /boot/device.hints set hint.fdc.0.at=3Disa set hint.fdc.0.port=3D0x3F0 set hint.fdc.0.irq=3D6 set hint.fdc.0.drq=3D2 set hint.fd.0.at=3Dfdc0 set hint.fd.0.drive=3D0 set hint.fd.1.at=3Dfdc0 set hint.fd.1.drive=3D1 set hint.ata.0.at=3Disa set hint.ata.0.port=3D0x1F0 set hint.ata.0.irq=3D14 set hint.ata.1.at=3Disa set hint.ata.1.port=3D0x170 set hint.ata.1.irq=3D15 set hint.adv.0.at=3Disa set hint.adv.0.disabled=3D1 set hint.bt.0.at=3Disa set hint.bt.0.disabled=3D1 set hint.aha.0.at=3Disa set hint.aha.0.disabled=3D1 set hint.aic.0.at=3Disa set hint.aic.0.disabled=3D1 set hint.atkbdc.0.at=3Disa set hint.atkbdc.0.port=3D0x060 set hint.atkbd.0.at=3Datkbdc set hint.atkbd.0.irq=3D1 set hint.atkbd.0.flags=3D0x1 set hint.psm.0.at=3Datkbdc set hint.psm.0.irq=3D12 set hint.vga.0.at=3Disa set hint.sc.0.at=3Disa set hint.sc.0.flags=3D0x100 set hint.vt.0.at=3Disa set hint.vt.0.disabled=3D1 set hint.apm.0.disabled=3D1 set hint.apm.0.flags=3D0x20 set hint.pcic.0.at=3Disa set hint.pcic.0.port=3D0x3e0 set hint.pcic.0.maddr=3D0xd set hint.pcic.1.at=3Disa set hint.pcic.1.irq=3D11 set hint.pcic.1.port=3D0x3e2 set hint.pcic.1.maddr=3D0xd4000 set hint.pcic.1.disabled=3D1 set hint.sio.0.at=3Disa set hint.sio.0.port=3D0x3F8 set hint.sio.0.flags=3D0x10 set hint.sio.0.irq=3D4 set hint.sio.1.at=3Disa set hint.sio.1.port=3D0x2F8 set hint.sio.1.irq=3D3 set hint.sio.2.at=3Disa set hint.sio.2.disabled=3D1 set hint.sio.2.port=3D0x3E8 set hint.sio.2.irq=3D5 set hint.sio.3.at=3Disa set hint.sio.3.disabled=3D1 set hint.sio.3.port=3D0x2E8 set hint.sio.3.irq=3D9 set hint.ppc.0.at=3Disa set hint.ppc.0.irq=3D7 set hint.ed.0.at=3Disa set hint.ed.0.disabled=3D1 set hint.ed.0.port=3D0x280 set hint.ed.0.irq=3D10 set hint.ed.0.maddr=3D0xd8000 set hint.cs.0.at=3Disa set hint.cs.0.disabled=3D1 set hint.cs.0.port=3D0x300 set hint.sn.0.at=3Disa set hint.sn.0.disabled=3D1 set hint.sn.0.port=3D0x300 set hint.sn.0.irq=3D10 set hint.ie.0.at=3Disa set hint.ie.0.disabled=3D1 set hint.ie.0.port=3D0x300 set hint.ie.0.irq=3D10 set hint.ie.0.maddr=3D0xd set hint.fe.0.at=3Disa set hint.fe.0.disabled=3D1 set hint.fe.0.port=3D0x300 set hint.le.0.at=3Disa set hint.le.0.disabled=3D1 set hint.le.0.port=3D0x300 set hint.le.0.irq=3D5 set hint.le.0.maddr=3D0xd set hint.lnc.0.at=3Disa set hint.lnc.0.disabled=3D1 set hint.lnc.0.port=3D0x280 set hint.lnc.0.irq=3D10 set hint.lnc.0.drq=3D0 load /kernel /kernel text=3D0x23b500 data=3D0x2f024+0x4bedc / echo \007\007 echo Please insert MFS root floppy and press enter: Please insert MFS root floppy and press enter: read load -t mfs_root /mfsroot set hint.acpi.0.disabled=3D1 set driver_floppy=3DYES set module_path=3D/modules;/dist echo \007\007 autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... 131072K of memory above 4GB ignored Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 5.1-CURRENT-20031029-JPSNAP #0: Wed Oct 29 04:30:49 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOOTMFS Preloaded elf kernel /kernel at 0xc0af1000. Preloaded mfs_root /mfsroot at 0xc0af12c0. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin =3D GenuineIntel Id =3D 0xf25 Stepping =3D 5 = Features=3D0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PG= E,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory =3D 4160225280 (3967 MB) avail memory =3D 4043710464 (3856 MB) Pentium Pro MTRR support enabled md0: Preloaded image /mfsroot 4423680 bytes
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
At Fri, 31 Oct 2003 16:56:43 + (UTC), Stephane Raimbault wrote: Does anyone have any thoughts regarding this? I would like to get 5.1 on this server. How about trying with -v at boot? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
Hi, I'm trying to install 5.1-R or 5.1-C from floppies redirected output to serial port and it won't boot to the install screen. 4.9-R floppies with output redirected to serial port works and installs properly. This is what I get on my serial console when I try to boot on 5.1-C (similar to 5.1-R) seems to hang after the vga0 shows up during boot. Is there anything I can do or provide to resolve my install problem? Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 633kB/4061120kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Wed Oct 29 04:14:01 GMT 2003) include /boot/device.hints set hint.fdc.0.at=isa set hint.fdc.0.port=0x3F0 set hint.fdc.0.irq=6 set hint.fdc.0.drq=2 set hint.fd.0.at=fdc0 set hint.fd.0.drive=0 set hint.fd.1.at=fdc0 set hint.fd.1.drive=1 set hint.ata.0.at=isa set hint.ata.0.port=0x1F0 set hint.ata.0.irq=14 set hint.ata.1.at=isa set hint.ata.1.port=0x170 set hint.ata.1.irq=15 set hint.adv.0.at=isa set hint.adv.0.disabled=1 set hint.bt.0.at=isa set hint.bt.0.disabled=1 set hint.aha.0.at=isa set hint.aha.0.disabled=1 set hint.aic.0.at=isa set hint.aic.0.disabled=1 set hint.atkbdc.0.at=isa set hint.atkbdc.0.port=0x060 set hint.atkbd.0.at=atkbdc set hint.atkbd.0.irq=1 set hint.atkbd.0.flags=0x1 set hint.psm.0.at=atkbdc set hint.psm.0.irq=12 set hint.vga.0.at=isa set hint.sc.0.at=isa set hint.sc.0.flags=0x100 set hint.vt.0.at=isa set hint.vt.0.disabled=1 set hint.apm.0.disabled=1 set hint.apm.0.flags=0x20 set hint.pcic.0.at=isa set hint.pcic.0.port=0x3e0 set hint.pcic.0.maddr=0xd set hint.pcic.1.at=isa set hint.pcic.1.irq=11 set hint.pcic.1.port=0x3e2 set hint.pcic.1.maddr=0xd4000 set hint.pcic.1.disabled=1 set hint.sio.0.at=isa set hint.sio.0.port=0x3F8 set hint.sio.0.flags=0x10 set hint.sio.0.irq=4 set hint.sio.1.at=isa set hint.sio.1.port=0x2F8 set hint.sio.1.irq=3 set hint.sio.2.at=isa set hint.sio.2.disabled=1 set hint.sio.2.port=0x3E8 set hint.sio.2.irq=5 set hint.sio.3.at=isa set hint.sio.3.disabled=1 set hint.sio.3.port=0x2E8 set hint.sio.3.irq=9 set hint.ppc.0.at=isa set hint.ppc.0.irq=7 set hint.ed.0.at=isa set hint.ed.0.disabled=1 set hint.ed.0.port=0x280 set hint.ed.0.irq=10 set hint.ed.0.maddr=0xd8000 set hint.cs.0.at=isa set hint.cs.0.disabled=1 set hint.cs.0.port=0x300 set hint.sn.0.at=isa set hint.sn.0.disabled=1 set hint.sn.0.port=0x300 set hint.sn.0.irq=10 set hint.ie.0.at=isa set hint.ie.0.disabled=1 set hint.ie.0.port=0x300 set hint.ie.0.irq=10 set hint.ie.0.maddr=0xd set hint.fe.0.at=isa set hint.fe.0.disabled=1 set hint.fe.0.port=0x300 set hint.le.0.at=isa set hint.le.0.disabled=1 set hint.le.0.port=0x300 set hint.le.0.irq=5 set hint.le.0.maddr=0xd set hint.lnc.0.at=isa set hint.lnc.0.disabled=1 set hint.lnc.0.port=0x280 set hint.lnc.0.irq=10 set hint.lnc.0.drq=0 load /kernel /kernel text=0x23b500 data=0x2f024+0x4bedc / echo \007\007 echo Please insert MFS root floppy and press enter: Please insert MFS root floppy and press enter: read load -t mfs_root /mfsroot set hint.acpi.0.disabled=1 set driver_floppy=YES set module_path=/modules;/dist echo \007\007 autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... 131072K of memory above 4GB ignored Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT-20031029-JPSNAP #0: Wed Oct 29 04:30:49 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOOTMFS Preloaded elf kernel /kernel at 0xc0af1000. Preloaded mfs_root /mfsroot at 0xc0af12c0. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf25 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 4160225280 (3967 MB) avail memory = 4043710464 (3856 MB) Pentium Pro MTRR support enabled md0: Preloaded image /mfsroot 4423680 bytes at 0xc06b7400 npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 29 entries at 0xc00fddf0 pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:29 INTA BIOS irq 11 pci_cfgintr: 0:29 INTB BIOS irq 10 pci_cfgintr: 0:29 INTC BIOS irq 5 pci0: unknown at device 0.1 (no driver attached) pcib1: PCIBIOS PCI-PCI bridge at device 2.0 on pci0 pci1: PCI bus on pcib1 pci1: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: PCIBIOS PCI-PCI bridge at device 29.0 on pci1 pci2: PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
On Wed, Oct 29, 2003 at 04:07:27PM -0700, Stephane Raimbault wrote: Hi, I'm trying to install 5.1-R or 5.1-C from floppies redirected output to serial port and it won't boot to the install screen. 4.9-R floppies with output redirected to serial port works and installs properly. This is what I get on my serial console when I try to boot on 5.1-C (similar to 5.1-R) seems to hang after the vga0 shows up during boot. Is there anything I can do or provide to resolve my install problem? Don't you have to tell the kernel to use an alternate system console? Kris pgp0.pgp Description: PGP signature
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
I followed the instructions found in the handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-advanced.html I've used this method for all my SuperMicro 6013P-8 servers some running 5.1-R and others 4.8-R Thanks, Stephane. - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Stephane Raimbault [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 4:11 PM Subject: Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
On Wed, Oct 29, 2003 at 04:15:00PM -0700, Stephane Raimbault wrote: I followed the instructions found in the handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-advanced.html I've used this method for all my SuperMicro 6013P-8 servers some running 5.1-R and others 4.8-R I didn't see you do 'boot -h' in the log you posted. Kris pgp0.pgp Description: PGP signature
Re: Please test: USB floppies
On Thu, 28 Aug 2003, Harald Schmalzbauer wrote: On Thursday 28 August 2003 21:35, Nate Lawson wrote: On Tue, 26 Aug 2003, Harald Schmalzbauer wrote: On Monday 25 August 2003 23:19, Nate Lawson wrote: If anyone has a USB floppy drive that is giving them problems, please let me know. Hello, this one needs NO_SYNC I think. Played a bit some time ago but had no luck (I'm no programmer) port 1 addr 2: full speed, power 500 mA, config 1, NEC USB UF000x(0x0040), NEC(0x0409), rev 1.23 *SNIP* Have you tried it again since early August? Also, what is the exact behavior when you try to mount or read it? Mounting, reading writing and umounting is working without errors, just these warnings. Here are the one from today's world: umass0: NEC NEC USB UF000x, rev 1.10/1.23, addr 4 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: NEC USB UF000x 1.23 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 While annoying, if your device doesn't hang or fail to operate, it does not need a quirk. So far, I have had no reports of USB devices with old quirks actually failing when their quirks were disabled. Once again, anything under DA_OLD_QUIRKS will be removed after the release. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Please test: USB floppies
On Tue, 26 Aug 2003, Harald Schmalzbauer wrote: On Monday 25 August 2003 23:19, Nate Lawson wrote: If anyone has a USB floppy drive that is giving them problems, please let me know. Hello, this one needs NO_SYNC I think. Played a bit some time ago but had no luck (I'm no programmer) port 1 addr 2: full speed, power 500 mA, config 1, NEC USB UF000x(0x0040), NEC(0x0409), rev 1.23 ___ Here's some log: umass0: NEC NEC USB UF000x, rev 1.10/1.23, addr 2 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: NEC USB UF000x 1.23 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 Have you tried it again since early August? Also, what is the exact behavior when you try to mount or read it? -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Please test: USB floppies
On Wed, 28 Aug 2003, Larry Baird wrote: Nate, When umount-ing I get the following: umass: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 And this is repeated twice. This message is harmless in the absence of other problems. But no problems like the drive hanging after multiple mount/umounts or writing problems or anything? Here is a report on another USB floppy drive. On my Sony VAIO using SOny's Y-E DATA USB-FDU 1.28 floppy I am also seeing the same message as above. But I see it everytime I access the floppy. Repeated mounts/ unmounts and I/O to the floppy appear to work fine. No hangs, nothing odd other than the above message. I think I have some other USB floppy drives at work. I'll try and give them a test drive as well in the next few days. I re-enabled some floppy quirks that I'm unsure are needed but I had to do it for the upcoming 4.9R just in case. So your results don't help at this point. Could you put an #if 0 and #endif around the section marked: /* USB floppy devices supported by umass(4) */ Alternatively, cvsup sys/cam/scsi/scsi_da.c to rev 1.42.2.42 and test the floppy again. Thanks, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Please test: USB floppies
On Thursday 28 August 2003 21:35, Nate Lawson wrote: On Tue, 26 Aug 2003, Harald Schmalzbauer wrote: On Monday 25 August 2003 23:19, Nate Lawson wrote: If anyone has a USB floppy drive that is giving them problems, please let me know. Hello, this one needs NO_SYNC I think. Played a bit some time ago but had no luck (I'm no programmer) port 1 addr 2: full speed, power 500 mA, config 1, NEC USB UF000x(0x0040), NEC(0x0409), rev 1.23 *SNIP* Have you tried it again since early August? Also, what is the exact behavior when you try to mount or read it? Mounting, reading writing and umounting is working without errors, just these warnings. Here are the one from today's world: umass0: NEC NEC USB UF000x, rev 1.10/1.23, addr 4 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: NEC USB UF000x 1.23 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 cale:/mnt# Thanks, -Harry -Nate pgp0.pgp Description: signature
Re: Please test: USB floppies
On Tue, 26 Aug 2003, Gunnar Flygt wrote: On Mon, Aug 25, 2003 at 02:19:03PM -0700, Nate Lawson wrote: If anyone has a USB floppy drive that is giving them problems, please let me know. I have a Compaq Evo N800c running 5.1-CURRENT (date 8 Aug) The usb floppy is working, I tried with a M$-dos floppy and I can mount and read it. I get a lot of error messages though, When running `mount_msdosfs /dev/da0 /mnt` I get the following: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) This is fine. I assume you only get one message like this. It means that the media (floppy) in the drive has changed, the old capacity info is invalidated, and that CAM should attempt to retry the command to get the new data. That's exactly what it says even the strange English in line 4 The floppy is readable i,e I can run `ls -l` on it. That is good. When umount-ing I get the following: umass: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 And this is repeated twice. This message is harmless in the absence of other problems. But no problems like the drive hanging after multiple mount/umounts or writing problems or anything? -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Please test: USB floppies
On Monday 25 August 2003 23:19, Nate Lawson wrote: If anyone has a USB floppy drive that is giving them problems, please let me know. Hello, this one needs NO_SYNC I think. Played a bit some time ago but had no luck (I'm no programmer) port 1 addr 2: full speed, power 500 mA, config 1, NEC USB UF000x(0x0040), NEC(0x0409), rev 1.23 ___ Here's some log: umass0: NEC NEC USB UF000x, rev 1.10/1.23, addr 2 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: NEC USB UF000x 1.23 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 and more log: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 Thanks, Thank you, -Harry Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: signature
Please test: USB floppies
If anyone has a USB floppy drive that is giving them problems, please let me know. Thanks, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
release and floppies
How to fix problem with floppies 1457664 bytes? P.S. please, CC me ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: release and floppies
+ Anton Yudin [EMAIL PROTECTED]: | How to fix problem with floppies 1457664 bytes? By not downloading a new release before it's announced. Just wait, a corrected version of 4.8-RELEASE without this problem will appear. Wait a little longer, for the official announcement. Then get it. OK? - Harald ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: release and floppies
+ Anton Yudin [EMAIL PROTECTED]: | How to fix problem with floppies 1457664 bytes? By not downloading a new release before it's announced. Just wait, a corrected version of 4.8-RELEASE without this problem will appear. Wait a little longer, for the official announcement. Then get it. OK? but i'm building 5.0-CURRENT, not STABLE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.0-RELEASE panics during the floppies boot
Hello FreeBSD 5.0-RELEASE panics during the floppies boot with following messages: panic: inthand_add: Can't initialize ICU syncing disks, buffers remaining... panic: bdwrite: buffer is not busy The box have two ISA PnP cards - a NIC based on UMC UM9008/F chip and Creative SB16 based on ViBRA16 chip. There are no PCI cards although there are 4 PCI slots. The video card is ATI XPERT 98 AGP based on ATI RAGE XL chip. There is also one non-PnP ISA card - a hardware 33600bps modem based on Rockwell chip. The BIOS have PnP OS option that can be set to No or Yes. If it set to No the BIOS initialize all PnP devices, including ISA PnP devices. Before the MBR loading (boot0) BIOS prints on the screen a diagnostic information about all initialized PnP devices, including choosen to them resurces (IRQs, DMA channels). In my case it choose IRQ 10 for my ISA PnP NIC and IRQ 5 with DMA channel 0 and 1 for my ISA PnP Creative SB16. Currently installed OS-es are FreeBSD 4.7-RELEASE and Win98SE. Win98SE get to know that BIOS already initialized all ISA PnP devices. Win98SE use the same resurces that BIOS choose. The resurces are IRQ 10 and I/O port range 0x0240-0x025F for the NIC and IRQ 5 with DMA channels 0 and 1 for the SB16. Port ranges of SB16 are not so interesting for us, so I don't tell they. FreeBSD 4.7-RELEASE don't know that or don't use PnP BIOS features. Instead 4.7 re-initialize all of my ISA PnP devices with different resurces' parameters. For example, it use IRQ 5 and I/O port range 0x0200-0x021F for the NIC. FreeBSD 5.0-RELEASE (when I do floppies boot) try to use IRQ 2 and same I/O port range for the NIC. It prints following line just before the panic: ed1: ISA PLUG PLAY Ethernet Card at port 0x200-0x21f irq 2 on isa0 If I set in my BIOS the PnP OS option to Yes I don't get this line but FreeBSD 5.0-RELEASE still panics during the boot. The panic messages are exactly the same. So, we have two problems: 1. FreeBSD (all versions) do not know about BIOS's PnP devices configuration support (at least for ISA PnP devices). 2. When FreeBSD 5.0 try to configure PnP devices (at least ISA PnP devices) it do it wrong way. FreeBSD 4.7 do it better but not perfect. I think that future FreeBSD releases must be able to work better with PnP BIOS features. Plug and Play configuration capability must be improved too, especially in 5.X. P.S. The same panic was already discussed about a year and half before. This is the link to archived copy of one that discussion member: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=471741+0+archive/2001/freebsd-current/20010930.freebsd-current __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release fails building floppies ...
I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: if [ -d /R/stage/driversfd ]; then sh -e /usr/local/5.0/src/release/scripts/doFS.sh /R/stage/floppies/drivers.flp /R/stage /mnt 1440 /R/stage/driversfd 4 fd1440; cd /R/stage/driversfd awk -f /usr/local/5.0/src/release/scripts/driver-desc.awk *.dsc /R/stage/floppies/DRIVERS.TXT; fi /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 2 cylinder groups of 1.22MB, 312 blks, 32 inodes. super-block backups (for fsck -b #) at: 32, 2528 1871 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 1391 987 40471% 3329 53% /mnt *** Filesystem is 1440 K, 404 left *** 4 bytes/inode, 29 left sh -e /usr/local/5.0/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 /dev/md3c: 4.2MB (8640 sectors) block size 4096, fragment size 512 using 4 cylinder groups of 1.06MB, 271 blks, 160 inodes. super-block backups (for fsck -b #) at: 32, 2200, 4368, 6536 6496 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 4175 3309 86679% 96 542 15% /mnt *** Filesystem is 4320 K, 866 left *** 8000 bytes/inode, 542 left mfsroot: 67.4% /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 1 cylinder groups of 1.41MB, 360 blks, 32 inodes. super-block backups (for fsck -b #) at: 32 /mnt: write failed, filesystem is full cp: /mnt/mfsroot.gz: No space left on device *** Error code 1 I ran 'make release' as: make relesae \ CHROOTDIR=/usr/local/release \ BUILDNAME=vaio \ [EMAIL PROTECTED]:/home/ncvs \ RELEASETAG=RELENG_5_0 \ NODOC=YES \ KERNEL_FLAGS=-j 5 \ NOPORTS=YES \ WORLD_FLAGS=-j 5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release fails building floppies ...
* De: Marc G. Fournier [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: make release fails building floppies ... ] I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: This is probably my fault, since tunefs(8) needs libufs now. Converting other things that could use it that are on the floppies to use libufs would be a start. My newfs changes might be enough. -- Juli Mallett [EMAIL PROTECTED] AIM: BSDFlata -- IRC: juli on EFnet. OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release fails building floppies ...
got it ... figured out how the mfsfd/modules is generated, and just trim'd down the driver.conf file to the bare essentials ... On Thu, 23 Jan 2003, Juli Mallett wrote: * De: Marc G. Fournier [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: make release fails building floppies ... ] I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: This is probably my fault, since tunefs(8) needs libufs now. Converting other things that could use it that are on the floppies to use libufs would be a start. My newfs changes might be enough. -- Juli Mallett [EMAIL PROTECTED] AIM: BSDFlata -- IRC: juli on EFnet. OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002 17:11:42 -, [EMAIL PROTECTED] (Robert Watson) wrote: This is not actually DP2, it's about a week earlier. That said, I'm not sure that bug was fixed in the missing week. If you can, try booting off of the 5.0-DP2 ISOs found at: ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-i386/5.0-DP2 Or using the floppies: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/5.0-DP2/floppies OK thanks for the correction. Using these floppies I can get much further. I get this during the boot: unknown: PNP0c02 can't assign resources (port) unknown: PNP0303 can't assign resources (port) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0400 can't assign resources (port) Then I get into sysinstall OK, partition the disk, set up the network via DHCP and choose to install via passive FTP from ftp.freebsd.org. All goes well until I get Extracting base into / directory then Write failure on transfer. Wrote -1 bytes of 240640 and at the bottom of the screen /mnt: write failed, filesystem is full. Alt-F2 shows: pid 85 (cpio) uid 0, inumber 5278 on /mnt: filesystem full /stand/cpio: write error: No space left on device /stand/gunzip: failed fwrite I think I saw something about that in a recent posting so I guess the fix hasn't made it into the floppies yet. jim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Fri, 22 Nov 2002 14:31:04 -, [EMAIL PROTECTED] (local.freebsd.current) wrote: Alt-F2 shows: pid 85 (cpio) uid 0, inumber 5278 on /mnt: filesystem full /stand/cpio: write error: No space left on device /stand/gunzip: failed fwrite I think I saw something about that in a recent posting so I guess the fix hasn't made it into the floppies yet. But of course the fact that I had only given / 50Mb might have had something to do with it :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
Hi, On Fri, Nov 22, 2002 at 02:30:34PM -, local.freebsd.current wrote: All goes well until I get Extracting base into / directory then Write failure on transfer. Wrote -1 bytes of 240640 and at the bottom of the screen /mnt: write failed, filesystem is full. I had exactly the same problems with 4.x recently; and it turned out that the problem was caused by a bad floppy. dd hat written all the data without reporting errors, but when I tried to boot from the floppy... b00m. Try to read the floppy back on the system where you created it, i.e. dd if=/dev/fd0 of=verify.dat and then compare the md5 checksums of the original .flp file and this file. If they do not match or if dd aborts with an error message, you know where your problems are coming from. /s/Udo -- The only reasonable alternative we can come up with is to close off the Internet to America Online users until they have passed an entrance test. But that would break federal laws that prohibit discrimination against the intellectually challenged. - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems with DP2 install floppies ... ?
Since I finally succeded in installing DP2 booting from floppy, I thought I might answer. On 19-Nov-2002 Marc G. Fournier wrote: 'K, that is what I did ... One final issue on this first attempt ... when I go into 'partition' an existing drive, how do I get it to 'mount' my existing swap device? rightnow, I just deleted and created it, but that just doesn't sound ... safe ... I did the same. A bit strange (why would we need a swap during installation anyway), but not dangerous, since you're not formatting anything. On Tue, 19 Nov 2002, John Baldwin wrote: On 19-Nov-2002 Marc G. Fournier wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... Did you try to restart your install via Ctrl-C? If so, don't, the restart stuff doesn't really work right. This may be related to Ctrl-C, but considering the time it takes to reboot, I'm willing to take the risk... Finally I could locate the problem: go to the options screen and set the installation root to /mnt. For some reason it is /, which seems wrong. After that I could install... but failed after the install finished for some other reason I don't remember. I couldn't do the post-install configuration, but since it was enough to boot, I just did it after reboot. And now, after compiling the packages that are not available, I have a nice running system. Is the floppy network install really working if you don't hit Ctrl-C? I seem to remember it was failing anyway, but I might be wrong. Aside question: I realized that the compiler sets -mcpu=pentiumpro by default. Is it the correct option for a Crusoe CPU? --- Jacques Garrigue Kyoto University garrigue at kurims.kyoto-u.ac.jp A HREF=http://wwwfun.kurims.kyoto-u.ac.jp/~garrigue/JG/A To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-mcpu and CPUTYPE (Re: Problems with DP2 install floppies ... ?)
On Wed, Nov 20, 2002 at 07:32:43PM +0900, Jacques Garrigue wrote: Aside question: I realized that the compiler sets -mcpu=pentiumpro by default. Is it the correct option for a Crusoe CPU? -mcpu doesn't change instruction set generated by the compiler, it affects instruction layout (i.e. the code still runs on a 386). Your question is really about what value of CPUTYPE to set in /etc/make.conf. I don't know the exact answer to that question for your CPU, but a vague answer is whatever instruction set architecture that chip emulates (i.e. pentium3, pentium/mmx, etc). Kris msg46989/pgp0.pgp Description: PGP signature
DP2 (I think!) crash booting from floppies
I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 fault code = user read, page not present instruction pointer= 0xf000:0x8c3e stack pointer = 0x0:0xfcc frame pointer = 0x0:0xfd4 code segment = base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags = interrupt enabled, resume, vm86, IOPL = 0 current process= 0 () trap number= 12 panic: page fault Uptime: 1s The same floppies work fine on another machine, up to the point of launching sysinstall. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002 11:32:29 -, [EMAIL PROTECTED] (local.freebsd.current) wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies / and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. I've now tried a third machine, one whose disk I can overwrite. This is a PII/400 (MSI 6119 board) with two IDE drives, an IDE CD, a Kingston (Realtek) NIC and ATI graphics. I can get as far as FDISK but when I hit A to use the entire disk, nothing happens. It doesn't respond to the keyboard at all. Numlock still toggles the light so *something* is there, but not a lot. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
local.freebsd.current wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 instruction pointer= 0xf000:0x8c3e Patch which was never integrated. Build a new kernel. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
This is not actually DP2, it's about a week earlier. That said, I'm not sure that bug was fixed in the missing week. If you can, try booting off of the 5.0-DP2 ISOs found at: ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-i386/5.0-DP2 Or using the floppies: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/5.0-DP2/floppies Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Wed, 20 Nov 2002, local.freebsd.current wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 fault code = user read, page not present instruction pointer= 0xf000:0x8c3e stack pointer = 0x0:0xfcc frame pointer = 0x0:0xfd4 code segment = base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags = interrupt enabled, resume, vm86, IOPL = 0 current process= 0 () trap number= 12 panic: page fault Uptime: 1s The same floppies work fine on another machine, up to the point of launching sysinstall. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On 20-Nov-2002 local.freebsd.current wrote: On Wed, 20 Nov 2002 11:32:29 -, [EMAIL PROTECTED] (local.freebsd.current) wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies / and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. I've now tried a third machine, one whose disk I can overwrite. This is a PII/400 (MSI 6119 board) with two IDE drives, an IDE CD, a Kingston (Realtek) NIC and ATI graphics. I can get as far as FDISK but when I hit A to use the entire disk, nothing happens. It doesn't respond to the keyboard at all. Numlock still toggles the light so *something* is there, but not a lot. Can you use Alt-F2 to switch to the debug terminal and see if there is any output? You probably want to switch before you do the fdisk, then switch again afterwards to see if there is any new output. You can get back to the main screen from the debug terminal by using Alt-F1. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002, Terry Lambert wrote: local.freebsd.current wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 instruction pointer= 0xf000:0x8c3e Patch which was never integrated. Build a new kernel. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current Can someone get the memory detection (int 12) back to stable? The conservative approach seems to only have the limitation of losing 640k whereas the experimental approach causes panics. Can we take such critical experiments out of the base system and let them mature as a patch? I heard something about a release coming up or something like that. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
Hi, On Wed, 20 Nov 2002, Terry Lambert wrote: local.freebsd.current wrote: I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 instruction pointer= 0xf000:0x8c3e Patch which was never integrated. Build a new kernel. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current Can someone get the memory detection (int 12) back to stable? The conservative approach seems to only have the limitation of losing 640k whereas the experimental approach causes panics. Can we take such critical experiments out of the base system and let them mature as a patch? I heard something about a release coming up or something like that. I already got the memory detection (int 12) back to STABLE and CURRENT. After all, nothing had changed there except for having new loader tunable. If you find 'Fatal trap 12: page fault while in vm86 mode' message at early kernel boot stage, your BIOS probably has broken INT 12H (in my case, it was not implemented by BIOS writer). The loader tunable 'hw.hasbrokenint12' is workaround for it. Try this at loader prompt: ok set hw.hasbrokenint12=1 Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Thu, 21 Nov 2002, Mitsuru IWASAKI wrote: Nate Lawson wrote: Can someone get the memory detection (int 12) back to stable? The conservative approach seems to only have the limitation of losing 640k whereas the experimental approach causes panics. Can we take such critical experiments out of the base system and let them mature as a patch? I heard something about a release coming up or something like that. I already got the memory detection (int 12) back to STABLE and CURRENT. After all, nothing had changed there except for having new loader tunable. If you find 'Fatal trap 12: page fault while in vm86 mode' message at early kernel boot stage, your BIOS probably has broken INT 12H (in my case, it was not implemented by BIOS writer). The loader tunable 'hw.hasbrokenint12' is workaround for it. Try this at loader prompt: ok set hw.hasbrokenint12=1 Ah, thank you very much. I didn't know this had been reverted. The tunable should be documented in the errata section as I'm sure other users would appreciate that. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Booting from floppies
My guess is that nobody use 1.44 floppies any more to boot.
But when I wanted to fire up an old box which only has a floppy
it did not grock the msfroot floppy:
'/mfsroot not found'
Which is IMHO correct since the mfsroot-floppy contains 'mfsroot.gz'
probably an easy fix if you know where to look.
It happened first with de 5.0-DP1, but also with the most recent ones build on 16-11.
Regards,
--WjW
N
'²æìr¸zǧvf¢Új:+v¨· è® ¶§²æìr¸yúÞy» rêëz{bØ^nr¡ûazg¬±¨
Re: Booting from floppies
On Tue, 19 Nov 2002 12:42:18 +0100 Willem Jan Withagen [EMAIL PROTECTED] wrote: Hi, My guess is that nobody use 1.44 floppies any more to boot. But when I wanted to fire up an old box which only has a floppy it did not grock the msfroot floppy: '/mfsroot not found' I just had that problem last week booting a -STABLE jpsnap. Having had bad experiences with floppy disks reliability I just dd'ed it again, just in case. The second time it worked. Could be a faulty disk. FWIW I think a lot of people use boot floppies to do net installs. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problems with DP2 install floppies ... ?
Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems with DP2 install floppies ... ?
On 19-Nov-2002 Marc G. Fournier wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... Did you try to restart your install via Ctrl-C? If so, don't, the restart stuff doesn't really work right. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problems with DP2 install floppies ... ?
In freebsd.current, you wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? I have seen this out of space errors with the floppy install and a fresh formatted 8G Harddisk and default partition sizes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems with DP2 install floppies ... ?
'K, that is what I did ... One final issue on this first attempt ... when I go into 'partition' an existing drive, how do I get it to 'mount' my existing swap device? rightnow, I just deleted and created it, but that just doesn't sound ... safe ... On Tue, 19 Nov 2002, John Baldwin wrote: On 19-Nov-2002 Marc G. Fournier wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... Did you try to restart your install via Ctrl-C? If so, don't, the restart stuff doesn't really work right. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems with DP2 install floppies ... ?
On 19-Nov-2002 Marc G. Fournier wrote: 'K, that is what I did ... One final issue on this first attempt ... when I go into 'partition' an existing drive, how do I get it to 'mount' my existing swap device? rightnow, I just deleted and created it, but that just doesn't sound ... safe ... Hmm, not sure. I don't think we currently support that. On Tue, 19 Nov 2002, John Baldwin wrote: On 19-Nov-2002 Marc G. Fournier wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... Did you try to restart your install via Ctrl-C? If so, don't, the restart stuff doesn't really work right. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Cannot install FreeBSD-current 9/10 and 9/17 from floppies
Hi, I bought a second machine to install FreeBSD-current, so that I can learn how to do kernel debugging via a serial cable. I cannot install FreeBSD-current on this machine. The machine is an IBM PIII-450 Here is what I did: (1) Obtained kern.flp and mfsroot.flp floppy images from the 9/17 and 9/10 snapshots of FreeBSD-current. I obtained these from ftp://current.freebsd.org/ (2) After booting from the first floppy (kern.flp), I insert mfsroot.flp. The install hangs at: === Mounting root from ufs:/dev/md0c md0c: raw partition size != slice size md0c: start 0, end 5087, size 5088 md0c: truncating raw partition md0c: rejecting partition in BSD label: it isn't entirely within the slice md0c: start 0, end 5087, size 5088 md0ca: start 0, end 8639, size 8640 spec_getpages: (md0c) I/O read failure: (error=22) bp 0x2031dc vp 0xc0e39000 size: 4096 resid: 4096, a_count: 4096 valid: 0x0 nread: 0, reqpage: 0, pindex: 575, pcount: 1 === Any ideas what the cause of this is? I tried disabling things like PNP in the BIOS, but that didn't fix anything. I had the same problems with the 9/17 and 9/10 floppy images. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Cannot install FreeBSD-current 9/10 and 9/17 from floppies
Hi, Just to follow up, I tried a few other floppy images, and succeeded with the floppy images that are part of the 8/31 -CURRENT snapshot. I can't figure out what the problem was with the newer floppy images. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] On Tue, Sep 17, 2002 at 08:53:39PM -0400, Craig Rodrigues wrote: Hi, I bought a second machine to install FreeBSD-current, so that I can learn how to do kernel debugging via a serial cable. I cannot install FreeBSD-current on this machine. The machine is an IBM PIII-450 Here is what I did: (1) Obtained kern.flp and mfsroot.flp floppy images from the 9/17 and 9/10 snapshots of FreeBSD-current. I obtained these from ftp://current.freebsd.org/ (2) After booting from the first floppy (kern.flp), I insert mfsroot.flp. The install hangs at: === Mounting root from ufs:/dev/md0c md0c: raw partition size != slice size md0c: start 0, end 5087, size 5088 md0c: truncating raw partition md0c: rejecting partition in BSD label: it isn't entirely within the slice md0c: start 0, end 5087, size 5088 md0ca: start 0, end 8639, size 8640 spec_getpages: (md0c) I/O read failure: (error=22) bp 0x2031dc vp 0xc0e39000 size: 4096 resid: 4096, a_count: 4096 valid: 0x0 nread: 0, reqpage: 0, pindex: 575, pcount: 1 === Any ideas what the cause of this is? I tried disabling things like PNP in the BIOS, but that didn't fix anything. I had the same problems with the 9/17 and 9/10 floppy images. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: high-density floppies
Joel Wilsson [EMAIL PROTECTED] wrote: fd0: hard error reading fsbn 0 (ST0 40abnrml ST1 1no_am ST2 0 cyl 0 hd 0 sec 1) So, I thought I'd try using a raw device configured for higher density disks. That wouldn't help you. It's already failing at the very first sector, by not finding any address mark at all. Thus using one of the »over-formatted« (like fd0.1720) devices wouldn't help. The reason I think they might NOT be damaged is that they are all of the same type (different type from the floppies I could read), and they are all double density floppies. Well, if you really mean double density, it wouldn't require a higher density device but a /lower/ density one. The default device is using high density (200 bytes raw medium capacity), while DD media were 100 bytes raw. So you could try using /dev/fd0.720. My question is, how can I do the equivalent of opening, for example, /dev/fd0.1720 (in -stable) under -current? You just open it, and it will magically appear in /dev. :-) [I've got a huge patchset here that will autodetect DD vs. HD floppies, but before i'm going to commit it, i have to upgrade my box first to -current. This will also change the policy regarding additional /dev/fd* devices, and i'll eventually upgrade the man page as well.] -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
high-density floppies
Hi, I'm copying in some tar-files, which are written directly to floppy disks. It worked fine for normal floppies, but now I have 7 floppies that fail (when I use dd if=/dev/fd0 of=diskN.tar) with: fd0: hard error reading fsbn 0 (ST0 40abnrml ST1 1no_am ST2 0 cyl 0 hd 0 sec 1) For the first floppies that got this error, I assumed they had been damaged. The reason I think they might NOT be damaged is that they are all of the same type (different type from the floppies I could read), and they are all double density floppies. So, I thought I'd try using a raw device configured for higher density disks. However, I can't find any such device; I only have /dev/fd0, but without devfs (in -stable) I had /dev/fd*.number which is described in fdc(4) The fdc man page seem to be out of date. My question is, how can I do the equivalent of opening, for example, /dev/fd0.1720 (in -stable) under -current? Thanks, Joel Wilsson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does floppies work with 384MByte RAM ?
On Wed, Nov 15, 2000 at 10:38:29PM -0500, Louis A. Mamakos wrote: I've got a Dell dual-Pentium-III XEON system at work that I was running -current on. Some time ago (didn't notice when exactly, sigh) when building new kernels, I started getting isa_dmainit(foo, bar) failed For me it is a ASUS P2B-DS with 512M RAM. I see the same isa_dmainit failed with full ram utilized. With MAXMEM set to MAXMEM="(464*1024)" it is working under current. With 480M it is failing. I looked through the sources and found that contigousmalloc can't find a page of physical ram under the 16M margin. But I am not vm wizzard enough, to understand what the difference is with MAXMEM set to some lower value than the real amount of memory. Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Does floppies work with 384MByte RAM ?
I have two reports about machines with 384MB RAM panicing when the floppies are accessed. I don't have the message right now except for a report that "it said something about bouncebuffers" Can somebody with 384MB ram check if the floppy works under current ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does floppies work with 384MByte RAM ?
Poul-Henning Kamp wrote: I have two reports about machines with 384MB RAM panicing when the floppies are accessed. I don't have the message right now except for a report that "it said something about bouncebuffers" Can somebody with 384MB ram check if the floppy works under current ? works fine on my current, i tried a mount, cp files in, rm files, and then a umount, all work normally. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does floppies work with 384MByte RAM ?
I have two reports about machines with 384MB RAM panicing when the floppies are accessed. I don't have the message right now except for a report that "it said something about bouncebuffers" I apologize for the vagueness of this response, but perhaps it might help shed some light. I've got a Dell dual-Pentium-III XEON system at work that I was running -current on. Some time ago (didn't notice when exactly, sigh) when building new kernels, I started getting isa_dmainit(foo, bar) failed messages during the booting process for both the fdc device as well as my CS423x sound device. A cursory examination revealed that this was while trying to allocate bounce buffers for both the floppy and sound device DMA channels. On a lark, I rebuilt a kernel with MAXMEM=(256*1024) (the system has 512M of memory installed), and the isa_dmainit() failures stopped happening. Recently, I installed 4.1.1-STABLE on this machine because, well, I needed a stable system and didn't need to track the -current bleeding edge. It's probably hard for me currently to reproduce this problem myself right now. I'd suggest the MAXMEM hack to see if this mirrors my experience. Certainly this system was working just fine until sometime around the SMPNG milestone; but I can't really attribute the failure to any particular change. Again, sorry for the lack of detail; hope this might provide a hint. louie Can somebody with 384MB ram check if the floppy works under current ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No kezboard with any -current snap floppies...
Howdy. I tried booting from a pair of kern/mfsroot floppies downloaded from current.freebsd.org, and no go. the kbd attach fails with 6. This also happens with grabbing the most current pair of floppies from today, as well as the beginning of Aug floppies, so this seems to be b0rken for quite some time, spanning the range of available snaps. This is on an HP NetSwerver LPr, and I had no problems with a pair of NetBSD floppies on the same hardware. Anyone else sees this, or do I need to copy down some info before the boot dmesg disappears? Be happy to do this if nobody sees the same thing. Otherwise, I'll probably try some different hardware just to get something happening... thanks barry bouwsma, all-purpose nobody (reply-to is valid) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No kezboard with any -current snap floppies...
On 2585 Sep 1993 [EMAIL PROTECTED] wrote: I tried booting from a pair of kern/mfsroot floppies downloaded from current.freebsd.org, and no go. the kbd attach fails with 6. This What is more, now that I've had success on some other hardware, is that what I thought was a New Feature is probably related, if not the reason. On the NetSwerver, it totally skips the kernel config screen that I expected to see and that turns out to be there after all, well before the attempt to attach the kezboard. If needed, I'll provide more info... barry bouwsma, all-purpose nobody (reply-to is valid) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3 install floppies: panic: resource_list_alloc: resource entry is busy
It seems Hans Ottevanger wrote: Hi folks, I just tried to boot the RC3 install floppies on my Pentium 66 testbox. It gets through the config stage without trouble, but then panics immediately with: ... pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible port 0 x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy I am also having this problem with 4.0-CURRENT kernels since February 18, both with my own custom kernel config and GENERIC. I have to revert to the ata driver of February 17 or earlier to get the system booting again, and then it runs perfectly. Hmm, seems to be a resource conflict problem, question is what is causing this. Could you do a verbose boot both with the old working kernel, and the new failing one ? This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte RAM, Matrox Millenium II, two Western Digital disks, and it ran all previous FreeBSD releases perfectly for almost five years. Yeah I notice the RZ 1000 chips in there, BE CAREFULL, I wouldn't use this for anything I cared about... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3 install floppies: panic: resource_list_alloc: resource entry is busy
Soren Schmidt wrote: [...] Hmm, seems to be a resource conflict problem, question is what is causing this. Could you do a verbose boot both with the old working kernel, and the new failing one ? Attached are two files. Both kernels used are built from the same config file, which is mostly GENERIC with devices removed that I do not have. The file "new" results from booting a kernel built completely from sources cvsupped yesterday. For "old" I replaced the contents of /sys/dev/ata by the files of February 17, i.e. before the major changes. I must remark that this is one of the machines that reports its IDE IRQ as 0 when asked for it. About two months ago there were problems when the ata driver took the timer interrupt. This was fixed by a special clause in ata-all.c, at least up to February 17. Maybe the current problem is related. This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte RAM, Matrox Millenium II, two Western Digital disks, and it ran all previous FreeBSD releases perfectly for almost five years. Yeah I notice the RZ 1000 chips in there, BE CAREFULL, I wouldn't use this for anything I cared about... For serious work I now have two BP6 based machines, this became just a testmachine. I know about the possible data corruption problems with RZ1000 chips, but I have never seen them with FreeBSD, despite the fact that I did a "make world" every other week for more than two years. However, if you run Linux or Solaris on this machine, and forget to switch off the EIDE prefetch buffers, the results can be quite dramatic... Kind regards, Hans SMAP type=01 base= len= 0009fc00 SMAP type=01 base= 0010 len= 03f0 SMAP type=02 base= fffc len= 0004 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Mar 10 21:43:07 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Calibrating clock(s) ... TSC clock: 66643091 Hz, i8254 clock: 1300543 Hz 1300543 Hz differs from default of 1193182 Hz by more than 1% Timecounter "i8254" frequency 1193182 Hz TSC clock: 48650664 Hz (Method B) Timecounter "TSC" frequency 48650664 Hz CPU: Pentium/P5 (48.65-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping = 7 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x002d1000 - 0x03ff7fff, 64122880 bytes (15655 pages) avail memory = 62267392 (60808K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0120 bios32: Entry = 0xf145c (c00f145c) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1440 pnpbios: Found PnP BIOS data at 0xc00f0130 pnpbios: Entry = f:1245 Rev = 1.0 Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc02b8000. Intel Pentium detected, installing workaround for F00F bug pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=04a38086) npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 54761513 bytes/sec bzero() bandwidth = 27416038 bytes/sec pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=04a38086) pcib0: Host to PCI bridge on motherboard found- vendor=0x8086, dev=0x04a3, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x1042, dev=0x1000, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base 01f0, size 3 map[14]: type 1, range 32, base 03f4, size 2 found- vendor=0x8086, dev=0x0484, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base a000, size 24 map[14]: type 1, range 32, base a100, size 14 map[18]: type 1, range 32, base a180, size 23 found- vendor=0x10b7, dev=0x9200, revid=0x74 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base
Re: ata, DMA and the install floppies
It seems John Hay wrote: Hi, I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? It should back down after 3 retries... But is is 3 retries pr request, so say it gets through on the 2 retry each time this will continue.. I dont know if there is access to the sysctl knobs from the emergency shell, but that would be a solution... Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 Hmm, wierd, did this hardware run FreeBSD before ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
| ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ... | | It seems that it is just going on and on. Shouldn't it back down to non | DMA mode after a while? Is there a way to disable the DMA on the install | floppies? How many times did it retry? It looks like everything is in place to default to PIO mode in this case, but you have allow it to try 3 times before it fallbacks to PIO. From ata-disk.c log: revision 1.59 date: 2000/03/05 16:52:23; author: sos; state: Exp; lines: +24 -24 [...] Update the timeout code to try fallback to PIO if problems arise in DMA mode. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
On Thu, 9 Mar 2000, Samuel Tardieu wrote: This looks exactly like the problem I was having with my Compaq laptop, which could run 3.4 boot disks just fine but not 4.0 kernels. I was probably too lazy to wait until it reaches the 3 attempts, so I will try again :) What model laptop may I ask? I'm running 4.0-current since 1/11/2000 (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? It should back down after 3 retries... But is is 3 retries pr request, so say it gets through on the 2 retry each time this will continue.. I dont know if there is access to the sysctl knobs from the emergency shell, but that would be a solution... Well it is been doing fsck for more than an hour now. :-) This is before the emergency shell is opened, but if I remember correctly, sysctl is not part of tools available. Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 Hmm, wierd, did this hardware run FreeBSD before ?? A similar system did run FreeBSD-3.4, but I never enabled DMA on it. I'll try to install 3.4 on this one and see. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
| What model laptop may I ask? I'm running 4.0-current since 1/11/2000 | (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Armada V300. I sent the full details here a few days ago. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
Ran into an odd problem tring to install the 3/7 release of 4.0 onto my VAIO PCG-Z505HS. The install hung while probing for plug and play devices. I had the BIOS set to non plug and play OS. So just for grins I turned plug and play OS on in the bios and tried again. Installed without a hitch. Of course I had to then go back into the BIOS and turn off plug and play OS to get by USB devices working after the install. (-: Any thoughts? Larry -- Larry Baird| HTTP://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: [EMAIL PROTECTED] | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3 install floppies: panic: resource_list_alloc: resource entry is busy
Hi folks, I just tried to boot the RC3 install floppies on my Pentium 66 testbox. It gets through the config stage without trouble, but then panics immediately with: ... pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible port 0 x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy I am also having this problem with 4.0-CURRENT kernels since February 18, both with my own custom kernel config and GENERIC. I have to revert to the ata driver of February 17 or earlier to get the system booting again, and then it runs perfectly. This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte RAM, Matrox Millenium II, two Western Digital disks, and it ran all previous FreeBSD releases perfectly for almost five years. Anybody else having this problem ? And before I start digging, any idea where to look for a solution, if it makes sense at all ? Kind regards, Hans To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
In message [EMAIL PROTECTED] Larry Baird writes: : then go back into the BIOS and turn off plug and play OS to get : by USB devices working after the install. (-: : : Any thoughts? You should have turned off PNP OS in the BIOS to start with. That's the only setting that is supported. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
On Thu, 9 Mar 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Larry Baird writes: : then go back into the BIOS and turn off plug and play OS to get : by USB devices working after the install. (-: : : Any thoughts? You should have turned off PNP OS in the BIOS to start with. That's the only setting that is supported. Yes, but he said this caused the system to panic at boot. Thats why he turned it off :) Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
Hello, I was getting the same error, I have two HD's on a Addladin TXpro Chipset and two CD-ROM drives. I get ad1: READ command timeout -resetting ata0: resetting devices .. done ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA BUT I have no ATA hard drives. Another thing I noticed with the install, is when it is probing for devices, it was trying to find PC_card0: but I had disable PC Card support in the kernel config (the install conflict screen for the install floppies) Anyways, other then that, things are going ok with my 4.0 RC3 install. Cheers Shaun On Thu, 9 Mar 2000, John Hay wrote: Hi, I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FINAL: Installation floppies and USB
On Mon, 6 Mar 2000, John Daniels wrote: Oops: That's kudos for John *Baldwin,* NOT "Barton." A thousand pardons... Hey... calling him Barton is a _compliment_! :) Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: FINAL: installation floppies and USB
On 07-Mar-00 John Daniels wrote: Hi: My installation problem has been solved. For those of you who have not been following "Installation floppies and USB," I have written a short synopsis after my description of the resolution and conclusion. Good, glad you got your system working. 4- Although I was disappointed that FreeBSD did not support USB out-of-the-box, I did not expect a lot of support (like I had as a paying customer of RedHats). NetBSDs installation floppy did work and that was my backup but I was encouraged to continue looking into my USB problem because I found that FreeBSD developers were willing to be helpful. This is especially true of John Barton, who first volunteered to help, but also of John Reynolds who elevated my problem to -current and Nick Hibma who responded quickly and cogently. This does need to be rectified. I still want to build a USB-enabled release and try to get it tested, or at least some custom boot floppies. If I get these built, I might ask to have you test them for me if you could. The thing is, while you may have been fortunate to find some PS/2 ports, a lot of new motherboads are USB only. I know because I have been looking at getting an Athlon, and most of the Athlon motherboards are USB only. Part of the problem is that apparently USB cannot be compiled directly into the kernel. Instead, doing so results in an unstable kernel. Instead, USB needs to be loaded via kld's, which complicates the boot disks somewhat. 5- Perhaps I am naïve, but stating that an OS supports a device is confusing when that support has to be compiled in. There should be a sharper distinction between support out-of-the-box (in GENERIC) and otherwise. Part of the confusion stems from the fact that USB seems so basic. For example, almost any PC will support a hard disk and a printer but most people would expect a hard disk to come with the machine. In fact, hardware.txt states: The FreeBSD kernel on the install floppy contains drivers for every piece of hardware that could conceivably be used to install the rest of the system with. As mentioned above, this is a definite concern that needs to be addressed. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FINAL: Installation floppies and USB
Oops: That's kudos for John *Baldwin,* NOT "Barton." A thousand pardons... John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FINAL: installation floppies and USB
Hi: My installation problem has been solved. For those of you who have not been following "Installation floppies and USB," I have written a short synopsis after my description of the resolution and conclusion. SOLUTION: I discovered that my Acer Aspire (model 6140) has two PS/2 ports (for keyboard and floppy). I purchased a PS/2 mouse and keyboard and I no longer get the "keyboard:no" message (instead it says: keyboard:yes)! (in fact, under W98, my USB keyboard and mouse, and my PS/2 keyboard and mouse all work simultaneously.) DISCUSSION: I have not seen any messages about this problem, since it turned into a BIOS discussion with the recommendation that I change the BIOS parameter "PnP OS" from YES to NO. FYI: Changing this parameter made no difference to the installation before or after I hooked up the PS/2 keyboard and mouse. It may make a difference at some later point. The PS/2 ports are hidden by a two different coverings: 1- a plastic molding that is screwed on and, 2- a plastic sheet that is glued on. No consumer-oriented documentation mentions the PS/2 ports. I only found out about them from: 1- a somewhat confusing email in which it was unclear if the writer had the same model and what the exact location of the ports were, 2- the motherboard specs which happened to be on the Acer Aspire website, which prompted a more through searching of my system. I had previously looked at the Acer website and knew it to have very little information. The Acer site doesnt even have a search function. I only went back hoping to find if there were any BIOS updates (there were none). Two previous calls to Acer support describing my problems installing a new operation system ended with the response: "we don't support Linux or FreeBSD" -- with no mention of the possibility of using the PS/2 ports. As far as BIOS updates: I finally found that Acer Germany provided them (www.acer.de/support/techinfo/bios.htm) -- and one of these BIOS updates was specifically for Linux support! (this might also be needed for FreeBSD but I have not downloaded this because I dont want to fool with my BIOS unless absolutely necessary.) I called Acer USA again but they had no idea that this site existed or why there was a BIOS update for Linux (even though the technician told me that he ran Linux (at home?)) I came to FreeBSD because I had learned that it supported USB but like Linux, USB support must be compiled in after installing the GENERIC kernel/system. I had purchased RedHat (before I found FreeBSD), but when I called RedHat support and described my system (with USB keyboard and mouse), I was told only that Linux doesnt support USB. CONCLUSIONS: 1- -Dh at the boot loaders boot: allowed the boot loader to load FreeBSD but when the FreeBSD GENERIC kernel was booted, the system may have been looking for input from the PS/2 port. (which I had no knowledge of!). Somehow NetBSDs GENERIC kernel recognized my USB keyboard, because: 1- it could use the same mechanism as the boot loader (whatever that may be), 2- it has a better ability for finding devices dynamically (at least for keyboards), or 3- it supports USB. 2-Acer needs to provide better documentation. 3-Major Linux vendors, like RedHat, which have aspirations for Linux as a consumer "desktop" OS should have already come across this problem with Acer machines (along with quirkiness of other machines/manufacturers). I would have also liked to see a willingness on their part to find a solution, instead of just spouting policy. There was no willingness from RH or SuSE to provide a boot disk with a recompiled kernel (SuSE sponsored the backport that enables USB support in Linuxs STABLE kernel) 4- Although I was disappointed that FreeBSD did not support USB out-of-the-box, I did not expect a lot of support (like I had as a paying customer of RedHats). NetBSDs installation floppy did work and that was my backup but I was encouraged to continue looking into my USB problem because I found that FreeBSD developers were willing to be helpful. This is especially true of John Barton, who first volunteered to help, but also of John Reynolds who elevated my problem to -current and Nick Hibma who responded quickly and cogently. 5- Perhaps I am naïve, but stating that an OS supports a device is confusing when that support has to be compiled in. There should be a sharper distinction between support out-of-the-box (in GENERIC) and otherwise. Part of the confusion stems from the fact that USB seems so basic. For example, almost any PC will support a hard disk and a printer but most people would expect a hard disk to come with the machine. In fact, hardware.txt states: The FreeBSD kernel on the install floppy contains drivers for every piece of hardware that could conceivably be used to install the rest of the system with. SYNOPSIS OF PRO
BIOS settings (was Instrallation floppies and USB)
Plug and Play OS [Yes] Should be No. How does this setting effect traditional ISA, PNP ISA, PCI cards. __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIOS settings (was Instrallation floppies and USB)
On Fri, Mar 03, 2000 at 08:50:07PM +0900, Takanori Watanabe wrote: In message [EMAIL PROTECTED], Navan Carson wrote: Plug and Play OS [Yes] Should be No. How does this setting effect traditional ISA, PNP ISA, PCI cards. This setting tells BIOS not to set any PnP setting, because OS itself want to set it arbitary. And any version FreeBSD ever have been released expects BIOS to set PnP setting. Well, what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIOS settings (was Instrallation floppies and USB)
In message [EMAIL PROTECTED], Nikolai Saoukh wrote: And any version FreeBSD ever have been released expects BIOS to set PnP setting. Well, what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current? They can 1. reads PnP setting from ISA PnP system. 2. write PnP setting as User specified. And there is no *automatic* PnP setting capability yet ,as far as I know. Takanori Watanabe a href="http://www.planet.kobe-u.ac.jp/~takawata/key.html" Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIOS settings (was Instrallation floppies and USB)
Plug and Play OS [Yes] Should be No. How does this setting effect traditional ISA, PNP ISA, PCI cards. Some might not be initiased. The basic point is that FreeBSD does not do the device enumeration and therefore any device that has not been configured by the BIOS or the previous OS (like Windows) is not accessable. Sometimes the BIOS wipes the configuration upon reboot and in that case the settings Windows has left behind are no longer available. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIOS settings (was Instrallation floppies and USB)
In message [EMAIL PROTECTED] Nikolai Saoukh writes: : what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current? That just deals with the isa pnp expansion cards. the PnP BIOS setting to "no" means that the BIOS will enable all the PnP (not just ISA add on cards) devices before passing control to the os. With it set to yes, the OS has to do this activation, and FreeBSD doesn't do that yet. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Instrallation floppies and USB
[Just a quick response, some things to try will follow this evening.] Configuration Table[Disabled] PCI IRQ setting[Auto] PCI IRQ sharing[No] should be Yes. Plug and Play OS [Yes] Should be No. I thought that PCI IRQ sharing might allow for dynamic assignment of IRQs, but changing this to 'Yes' had no effect. It should be on anyway. FreeBSD supports. In the future you might add more hardware which makes you run out of IRQs I thought that Reset Resource Assignments might enable the OS to set resouces (IRQ, etc) but everytime I looked at this after I had chosen 'Yes,' it had been set back to 'No.' Acer support tells me that all this does is reset the resources back to their original values. You'll see a message saying 'Updating ESCD...' etc. 1. When I try to boot the kern.flp disk, I get the message: /boot.config: -P Keyboard: no Booting continues but the keyboard is unusable unless I immmediately hit the space bar then type '-Dh' at the 'boot:' prompt as described in the TROUBLE.TXT document in the -CURRENT snapshot directory. NOTE: That document says that the '-Dh' workaround is meant for older systems with an 84-key keyboard, but it is working for my 1999 Acer Asprire with a 102-key USB keyboard! That means the BIOS emulates a XT/AT style keyboard. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Hi: One more *possible* "clue." Just before the kernel configuration screen appears (this screen fills up the screen, replacing diagnostic/bootup messages), I get a one-line message that includes the terms "timer" and "frequency" along with some numbers (that may be in hexadecmial). This maybe normal boot-up behavior but I searched the mailing list archives and noticed that the timer was rewritten for 3.0 and that there were some messages/problems concerning the timer in the archives. See: http://www.freebsd.org/releases/3.0R/notes.html Which states: " The timeout(9) system in the kernel has been overhauled. This gives O(1) insertion and removal of callouts and an O(hash chain length) amount of work to be performed in softclock. The original paper is at: http://www.cs.berkeley.edu/~amc/research/timer/ " John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Hi: I apologize for another post. This note should have been included in my last post. I wanted to point out that the description of the timer (at the URL provided) lists a couple of known problems, with an explanation as to why the developer could not fix them. I don't know if they have been fixed since that description, or how relevent these problems may be to my situation. John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Phoenix wrote: If it is the same kind of acer as I have you may be in luck, hidden away on the back panel hidden behind a sticker and a metal knockout there are 2 ps/2 style connectors. Pull the top off of your box and see if you have them (near the parrellel port) I have been running -current on this box for a month with no problems other than having to use a normal keyboard for the install. I have an Acer Aspire model 6140 (a PIII 450 system). The system has plastic molding in the back that covers 2 serial ports (only one of which is supposed to work), and a game port. I pulled off the metal case for the system as a whole but did not see any ps/2 ports or other ports. I have looked for an ISA or PCI card that might have a ps/2 or AT-style port for a keyboard but I have not been able to find one. I have also tried to find a keyboard that would use a COM port but that is also non-existant. Anyway, thanks for your input. __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Phoenix wrote: If it is the same kind of acer as I have you may be in luck, hidden away on the back panel hidden behind a sticker and a metal knockout there are 2 ps/2 style connectors. Pull the top off of your box and see if you have them (near the parrellel port) I have been running -current on this box for a month with no problems other than having to use a normal keyboard for the install. I have an Acer Aspire model 6140 (a PIII 450 system). The system has plastic molding in the back that covers 2 serial ports (only one of which is supposed to work), and a game port. I pulled off the metal case for the system as a whole but did not see any ps/2 ports or other ports. I have looked for an ISA or PCI card that might have a ps/2 or AT-style port for a keyboard but I have not been able to find one. I have also tried to find a keyboard that would use a COM port but that is also non-existant. Anyway, thanks for your input. John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Instrallation floppies and USB
Hi: I looked in BIOS setup to see if there were any settings that I could try changing to make the boot floopies work. The only ones that I found that seemed to apply were (defaults in brackets): Configuration Table[Disabled] PCI IRQ setting[Auto] PCI IRQ sharing[No] Plug and Play OS [Yes] Reset Resource Assignments [No] I thought that the Configuration Table might provide the ability to change settings (IRQ, etc.) but it only summarized system specs. (Among these, it showed USB 'enabled') I didn't change PCI IRQ setting. I thought that PCI IRQ sharing might allow for dynamic assignment of IRQs, but changing this to 'Yes' had no effect. Disabling Plug and Play had no effect I thought that Reset Resource Assignments might enable the OS to set resouces (IRQ, etc) but everytime I looked at this after I had chosen 'Yes,' it had been set back to 'No.' Acer support tells me that all this does is reset the resources back to their original values. In sum, I was not able to change anything with the changes that I made. I also went to the Acer support site to see if there were any BIOS or device updates for my system. I didn't find any. I am registered with Acer support and I would be happy to provide the information needed (Toll free phone number, system serial number, my customer id #, etc.) for Nick Hibma or another developer to contact them if that would be helpful. FYI, I also have a 160Kbps DSL connection so if anyone wants me to test reconstructed boot disks/kernels, I can do that. (I believe that John Baldwin has been looking into this.) To summarize the problem and the clues that we now have: 1. When I try to boot the kern.flp disk, I get the message: /boot.config: -P Keyboard: no Booting continues but the keyboard is unusable unless I immmediately hit the space bar then type '-Dh' at the 'boot:' prompt as described in the TROUBLE.TXT document in the -CURRENT snapshot directory. NOTE: That document says that the '-Dh' workaround is meant for older systems with an 84-key keyboard, but it is working for my 1999 Acer Asprire with a 102-key USB keyboard! 2. The installation boots the kernel but immediately after the kernel config screen appears (with 3 options: no config, full screen, CLI), the system becomes unusable. 3. The floppy drive light remains on, as though the floopy is awaiting instructions or has been interrupted in data transfer. 4. I have provided my complete system specs and resource usage in an earlier post. It appears that there may be some resource conflicts. My system uses IRQ 11 for the Intel 82371AB/EB PCI to USB Universal Host Controller, while FreeBSD uses IRQ 11 for an adaptec SCSI Controller. My keyboard and FreeBSD's use of IRQ12 and IOMem 0060h may also be a problem. (This is not an exhaustive list of possible conflicts) 5. I can boot the NetBSD installation disk and use my keyboard to select options (e.g. configure my NIC) so this may provide some additional info or a possible roadmap to a solution. For example, does it dynamically find resources for more devices than FreeBSD (especially the Adaptec SCSI controller and keyboards/mice)? Does NetBSD provide support for USB keyboards in their installation kernel? Etc. John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
If it is the same kind of acer as I have you may be in luck,
hidden away on the back panel hidden behind a sticker and a
metal knockout there are 2 ps/2 style connectors. Pull the
top off of your box and see if you have them (near the parrellel
port) I have been running -current on this box for a month
with no problems other than having to use a normal keyboard for
the install.
also Nick Himba
Seeing that your USB controller fails to work properly when the FreeBSD
kernel takes over, I bet somewhere there is a problem with shared
interrupts.
Because a USB keyboard here works either with USB support or without USB
support compiled in.
I had the same problem on my box, Ie. the usb controler wont do
emulation at boot under freebsd, strangly the same box ran linux
for 6 months witout the usb stack loaded and the keyboard worked
fine, it just broke when I loaded the stack. works fine now as
long as my freebsd kernel has usb enabled.
Bob
On Feb 28, The Matrix made John Reynolds~ say,
[forwarded from -questions to the above groups because this seems to be a
legit "problem" and I wanted the "right eyes" in -current to see it. ]
--- start of forwarded message ---
From: "John Daniels" [EMAIL PROTECTED]
Subject: Installation floppies and USB
Date: Sun, 27 Feb 2000 21:19:50 EST
I have a system with only a *USB* keyboard port (no PS/2 or AT-style ports).
When I boot the installation floppies I get the message:
keyboard:no
After reading errata,release notes, etc., I learned that I should hit
'enter' and type '-Dh' at the prompt, which I did. Now the installation
proceeds until the kernel is booted and the kernel configuration menu is
displayed (with 3 options: skip config, full-screen, CLI-mode). At that
point my keyboard becomes unusable. I believe that this may be because the
kernel ('GENERIC'?) doesn't include USB support. USB support is supposed to
be compiled in *after* an install.
For my system, this is unacceptable. I now have a catch-22: I can't get USB
support until the kernel is recompiled, and I can't recompile the kernel
unless I can use the keyboard to install FreeBSD.
My system was created by a major PC Manufacturer (Acer) and I'm sure that
they have sold thousands like it. I'm sure that they are not/will not be
the only manufacturer to create USB-only systems. My system uses Human
Interface Devices (HID) USB. It is *CRUCIAL* that USB keyboards be
recognized "out-of-the-box" for current and future systems that only support
USB keyboards.
QUESTION: Are there work currently andy arounds/solutions in FreeBSD? When
can USB be available "out-of-the-box?" (I was hoping it would be in 4.0)
Lastly, the NetBSD install floppy recognizes my keyboard and lets me use it
during the install. Is there any possible workaround that includes booting
the NetBSD install disk, or installing FreeBSD over/after NetBSD?
NOTE: There has already been at least one other FreeBSD newbie who has
encountered this problem (also with an Acer box), and there seems to be a
fair amount of USB questions/discussion online.
Any info/help is greatly appreciated
John
[EMAIL PROTECTED]
__
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
--- end of forwarded message ---
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds WCCG, CCE, Higher Levels of Abstraction |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 |
| [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Installation floppies and USB
[forwarded from -questions to the above groups because this seems to be a
legit "problem" and I wanted the "right eyes" in -current to see it. ]
--- start of forwarded message ---
From: "John Daniels" [EMAIL PROTECTED]
Subject: Installation floppies and USB
Date: Sun, 27 Feb 2000 21:19:50 EST
I have a system with only a *USB* keyboard port (no PS/2 or AT-style ports).
When I boot the installation floppies I get the message:
keyboard:no
After reading errata,release notes, etc., I learned that I should hit
'enter' and type '-Dh' at the prompt, which I did. Now the installation
proceeds until the kernel is booted and the kernel configuration menu is
displayed (with 3 options: skip config, full-screen, CLI-mode). At that
point my keyboard becomes unusable. I believe that this may be because the
kernel ('GENERIC'?) doesn't include USB support. USB support is supposed to
be compiled in *after* an install.
For my system, this is unacceptable. I now have a catch-22: I can't get USB
support until the kernel is recompiled, and I can't recompile the kernel
unless I can use the keyboard to install FreeBSD.
My system was created by a major PC Manufacturer (Acer) and I'm sure that
they have sold thousands like it. I'm sure that they are not/will not be
the only manufacturer to create USB-only systems. My system uses Human
Interface Devices (HID) USB. It is *CRUCIAL* that USB keyboards be
recognized "out-of-the-box" for current and future systems that only support
USB keyboards.
QUESTION: Are there work currently andy arounds/solutions in FreeBSD? When
can USB be available "out-of-the-box?" (I was hoping it would be in 4.0)
Lastly, the NetBSD install floppy recognizes my keyboard and lets me use it
during the install. Is there any possible workaround that includes booting
the NetBSD install disk, or installing FreeBSD over/after NetBSD?
NOTE: There has already been at least one other FreeBSD newbie who has
encountered this problem (also with an Acer box), and there seems to be a
fair amount of USB questions/discussion online.
Any info/help is greatly appreciated
John
[EMAIL PROTECTED]
__
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
--- end of forwarded message ---
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds WCCG, CCE, Higher Levels of Abstraction |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 |
| [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
John Reynolds~ [EMAIL PROTECTED] wrote: [forwarded from -questions to the above groups because this seems to be a legit "problem" and I wanted the "right eyes" in -current to see it. ] I have a system with only a *USB* keyboard port (no PS/2 or AT-style ports). When I boot the installation floppies I get the message: My machine has "USB keyboard support" in BIOS menu. If your BIOS is AWARD's one, check your bios. Maybe it's in Chipset Features Setup section. BIOS uses USB keyboards as legacy. --- MAEKAWA Masahide [EMAIL PROTECTED] --- URL: http://kerberos.math.sci.kobe-u.ac.jp/~maekawa/ --- Kobe University (Faculty of Science, Department of Mathematics) --- Powered by BSD/OS, FreeBSD, NetBSD, OpenBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation floppies and USB
Seeing that your USB controller fails to work properly when the FreeBSD
kernel takes over, I bet somewhere there is a problem with shared
interrupts.
Because a USB keyboard here works either with USB support or without USB
support compiled in.
The only solution for you would be to compile a new kernel on a
different system that includes USB support, or use a module that you
load before the kernel is booted.
And yes, USB only machines will be supported at some stage. But at the
moment the USB kernel is too flakey to be in GENERIC.
Nick
On Mon, 28 Feb 2000, John Reynolds~ wrote:
[forwarded from -questions to the above groups because this seems to be a
legit "problem" and I wanted the "right eyes" in -current to see it. ]
--- start of forwarded message ---
From: "John Daniels" [EMAIL PROTECTED]
Subject: Installation floppies and USB
Date: Sun, 27 Feb 2000 21:19:50 EST
I have a system with only a *USB* keyboard port (no PS/2 or AT-style ports).
When I boot the installation floppies I get the message:
keyboard:no
After reading errata,release notes, etc., I learned that I should hit
'enter' and type '-Dh' at the prompt, which I did. Now the installation
proceeds until the kernel is booted and the kernel configuration menu is
displayed (with 3 options: skip config, full-screen, CLI-mode). At that
point my keyboard becomes unusable. I believe that this may be because the
kernel ('GENERIC'?) doesn't include USB support. USB support is supposed to
be compiled in *after* an install.
For my system, this is unacceptable. I now have a catch-22: I can't get USB
support until the kernel is recompiled, and I can't recompile the kernel
unless I can use the keyboard to install FreeBSD.
My system was created by a major PC Manufacturer (Acer) and I'm sure that
they have sold thousands like it. I'm sure that they are not/will not be
the only manufacturer to create USB-only systems. My system uses Human
Interface Devices (HID) USB. It is *CRUCIAL* that USB keyboards be
recognized "out-of-the-box" for current and future systems that only support
USB keyboards.
QUESTION: Are there work currently andy arounds/solutions in FreeBSD? When
can USB be available "out-of-the-box?" (I was hoping it would be in 4.0)
Lastly, the NetBSD install floppy recognizes my keyboard and lets me use it
during the install. Is there any possible workaround that includes booting
the NetBSD install disk, or installing FreeBSD over/after NetBSD?
NOTE: There has already been at least one other FreeBSD newbie who has
encountered this problem (also with an Acer box), and there seems to be a
fair amount of USB questions/discussion online.
Any info/help is greatly appreciated
John
[EMAIL PROTECTED]
__
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
--- end of forwarded message ---
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds WCCG, CCE, Higher Levels of Abstraction |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 |
| [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Floppies and laptops
In message 4.1.19990426221303.00924...@216.67.14.69 Forrest Aldrich writes: : mfsroot that would be more apt to find your PCMCIA card? Would be a really : handy tool/option to have. More generally, it would be nice to have support for pccards on the boot disk. There is work in progress to make this happen. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Floppies and laptops
In article 199904271419.iaa17...@harmony.village.org, Warner Losh i...@harmony.village.org wrote: More generally, it would be nice to have support for pccards on the boot disk. There is work in progress to make this happen. Yes! We need this. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Floppies and laptops
In message 199904271921.maa05...@vashon.polstra.com John Polstra writes: : Yes! We need this. I have the sysinstall patches from the PAO people. Plus I've started working on an all kernel design for what pccardd is now doing. This should obviate the need for pccardd on the floppies. There may be more hacking to sysinstall needed to get it to rescan devices, since it would be nice to be able to plug in devices at anytime, just just right after you booted the floppy. However, this is long term stuff. The short term plans I have are getting the pcic stuff working in the newbus framework, as well as including the initial patches from PAO to pccardd and sysinstall to at least give the snaps something that is easier to install on laptops. I had to jump through too many to get my machine up and running. Once I get the pccard stuff working, I may go after cardbus. Geeze, all of this so I can get the pccard support working in Soren's new driver so I can read/write compact flash cards on my FreeBSD machine so I can put them into a WinCE palmtop I have Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Floppies and laptops
I realize there are only so many drivers you can crunch on a floppy... with that in mind, and with the advent of many laptops comnig about that people would like to net-install, would it not be more practical to provide an alternate mfsroot that would be more apt to find your PCMCIA card? Would be a really handy tool/option to have. -F To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
From: John W. DeBoskey j...@unx.sas.com Date: Thu, 21 Jan 1999 00:54:36 -0500 (EST) If you really want to make things easier for the beginner, why not provide a DOS boot program. Then you wouldn't even have to worry about boot floppies. Tell new folks to copy the boot program to the DOS partition and run it from DOS. Case closed. No boot floppy required. I can imagine half a dozen ways to make this work. Although I'll cheerfully admit that I'm probably in the minority in this respect, such an approach would do me not one whit of good, since, given a desired objective, I have no idea how to make MS-DOS accomplish it. (I'm coming at FreeBSD with no background in PCs at all, about 12+ years working with UNIX, about 12 years as an IBM mainframe (MVS) systems programmer, and some years before that of various other types of systems. In my (somewhat limited) experience, when I've tried to use MS-DOS for anything, more than half the time either the application or the machine would hang or crash; thus, I'd be hard-pressed to advocate reliance upon that mechanism for anything of perceived importance.) Cheers, david -- David Wolfskill UNIX System Administrator d...@whistle.comvoice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
Well, FWIW, I've been modifying my local 'make release' to produce
a 2.88M boot floppy, which I then use as the boot image when I burn a
CD of the SNAP. Works like a champ.
Thus, the isofs creation is a straight run of the code in
examples/worm and cdrecord:
sh /usr/share/examples/worm/makecdfs.sh \
-b ${SNAP} /cdwork/disc1 /cdwork/cd1.image \
${SNAP} (c) FreeBSD \
cd /cdwork cdrecord dev=5,0 speed=4 -v cd1.image
If I hop on my soapbox, I'd really like to see a single floppy
network install which supports nfs(which I also re-enable on the
normal boot.flp since it fits on the 2.88M image).
oh well,
John
Mike Smith wrote:
This sounds like booting/installing from CD-ROM is currently
impossible as well ???
That's correct. We're looking at having to move to a harddisk
emulation mode to get this back on track.
Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is
it too much work?
- --
Drew Derbyshire UUPC/extended e-mail: softw...@kew.com
Telephone: 617-279-9812
I get by with a little help from my friends . . . - Lennon/McCartney
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
--
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
If I hop on my soapbox, I'd really like to see a single floppy network install which supports nfs(which I also re-enable on the normal boot.flp since it fits on the 2.88M image). The problem is that there are too many people standing on too many different soapboxes. Each and every one of you wants a different combination of stuff on the One True Boot Floppy. I'm sure you can see what's wrong with this picture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
hi, Hang on a second... I think you might be putting words in my mouth... I'm not saying that the nfs boot floppy is the One True Boot Floppy. I see no reason why we can't have a netboot.flp and a dskboot.flp created. If you really want to make things easier for the beginner, why not provide a DOS boot program. Then you wouldn't even have to worry about boot floppies. Tell new folks to copy the boot program to the DOS partition and run it from DOS. Case closed. No boot floppy required. I can imagine half a dozen ways to make this work. However, I don't really want the above. I'd simply like to see a netboot.flp become a standard part of the distribution. There are others on the list besides myself who have said they would like to see this. It's simple to do, just a few extra commands in the release.8 target. Unfortunately, I'm not a committer, and it really isn't a technical question... It's a political issue... FreeBSD seems to want 'The One True Floppy'... Oh well, Thanks for listening! John I said: If I hop on my soapbox, I'd really like to see a single floppy network install which supports nfs(which I also re-enable on the normal boot.flp since it fits on the 2.88M image). and Mike replied: The problem is that there are too many people standing on too many different soapboxes. Each and every one of you wants a different combination of stuff on the One True Boot Floppy. I'm sure you can see what's wrong with this picture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
Hang on a second... I think you might be putting words in my mouth... I'm not saying that the nfs boot floppy is the One True Boot Floppy. I see no reason why we can't have a netboot.flp and a dskboot.flp created. The slicing that's being contemplated at the moment is actually install from CDROM and install from anywhere else. The CDROM support actually covers a reasonable amount of code (although there are some angsty issues about ATAPI ZIP/LS120 disks still). If you really want to make things easier for the beginner, why not provide a DOS boot program. Then you wouldn't even have to worry about boot floppies. Tell new folks to copy the boot program to the DOS partition and run it from DOS. Case closed. No boot floppy required. I can imagine half a dozen ways to make this work. Please read everything that Robert Nordier has written about how it's not possible to boot once DOS has started. Or take it from me - we have canned support for that mode of operation and we're not going back. Unfortunately, I'm not a committer, and it really isn't a technical question... It's a political issue... FreeBSD seems to want 'The One True Floppy'... Not really; and if you have diffs that let us split into a couple of cleanly separated floppies with no missing cases then we would enthusiastically leap onboard. But net/no-net isn't enough of a dividing line. We're pretty much resigned to the death of one true floppy. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
I've been taking the last few days off, but I intend to get to this this week and fix whatever's broken. Don't panic. :) On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote: Hi ! Bad news, make release still produces non bootable floppies. I cvsupped yesterday evening at 8pm and did a make world and make release Now I tried the boot.flp image from the ftp subdir in /R/ First error message No /boot/loader Then the typical boot banner 2nd error message No /kernel When typing ? . .. kernel.gz When typing kernel.gz to load this kernel invalid format Of course, it's gzipped. Well, there is _still_ something wron, believe me. The single-floppy install is broken. Use the two-floppy install as I've been encouraging people to do now since the 12th. This sounds like booting/installing from CD-ROM is currently impossible as well ??? Andreas /// -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
Mike Smith wrote: This sounds like booting/installing from CD-ROM is currently impossible as well ??? That's correct. We're looking at having to move to a harddisk emulation mode to get this back on track. Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is it too much work? -- Drew Derbyshire UUPC/extended e-mail: softw...@kew.com Telephone: 617-279-9812 I get by with a little help from my friends . . . - Lennon/McCartney To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation I've read states that this should be supportable on machines that understand 2.88MB floppies Or, have we outgrown that already? -Brian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release produces unbootable boot floppies, no boot loader, no /kernel
Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation I've read states that this should be supportable on machines that understand 2.88MB floppies Or, have we outgrown that already? How many systems have you seen with 2.88MB floppy drives? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
