First of all, a fine point of English: "How to" should be followed by an explanation of how to do something, not a question, 'specially if not followed by a question mark. The phrase you are probably looking for is "how do I . . . ?".
(yes, strange thing for me, who has mangled English in many a creative and strange way to gripe about, but this bugs me for some reason) On to your question... Don Jackson wrote: > I have a Tyan S2881 Thunder K8SR motherboard (Opteron), and wd0 is a > SATA hard disk (Western Digital), but I want to boot and run off a > flash card. > > I have an Addonics SATA to CF adaptor, Model ADSACF) > > http://www.addonics.com/products/flash_memory_reader/adsacf.asp oh, interesting...CF to SATA adapter. > The OpenBSD 4.1 installer (booted via PXEboot) seems to have a LOT of > trouble with the flash drive (recognized as WD1). That's going to bite you in the butt eventually, even if nothing else does. You don't want to try to boot from wd1... > How can I make OpenBSD happy with this drive? The actual CF card is a > SanDisk Ultra II 8Gb. > > I had zero problems installing and using a similar SanDisk card in a > Soekris 4801, so I know that it must be possible to make this work. I doubt that it is your CF card that's causing your problems, it's everything OTHER than the card that's suspect: the SATA chip, the SATA->CF adapter, etc. > How do I make OpenBSD happy with the flash disk? Do I need special > BIOS settings? > I had very similar problems with another IDE -> Flash adaptor in a > Pentium machine. due to the lack of details and my sucess doing this, I'm totally ignoring this statement. :) > Here is the log from the installer: > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org > > OpenBSD 4.1-stable (RAMDISK_CD) #1: Sun May 27 13:25:48 PDT 2007 > [EMAIL PROTECTED]:/home/openbsd/4.1/src/sys/arch/i386/compile/RAMDISK_CD ... > pciide0 at pci1 dev 5 function 0 "CMD Technology SiI3114 SATA" rev 0x02: DMA > pciide0: using irq 10 for native-PCI interrupt > pciide0: port 0: device present, speed: 1.5Gb/s > wd0 at pciide0 channel 0 drive 0: <WDC WD2500YS-01SHB0> > wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors > wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 > pciide0: port 1: device present, speed: 1.5Gb/s > wd1 at pciide0 channel 1 drive 0: <SanDisk SDCFH-8192> > wd1: 4-sector PIO, LBA, 7815MB, 16007040 sectors > wd1(pciide0:1:0): using BIOS timings, DMA mode 2 ... > dkcsum: wd0 matches BIOS drive 0x80 > wd1(pciide0:1:0): timeout > type: ata > c_bcount: 512 > c_skip: 0 > pciide0:1:0: bus-master DMA error: missing interrupt, status=0x21 > pciide0 channel 1: reset failed for drive 0 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:1:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 1: reset failed for drive 0 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:1:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 1: reset failed for drive 0 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:1:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 1: reset failed for drive 0 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:1:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 1: reset failed for drive 0 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:1:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 1: reset failed for drive 0 ... 1) As already indicated, if you want to boot from this thing, swap your cables so that it is wd0, not wd1. (YES, you CAN probably do it as wd1, but it will be a maintenance nightmare, and seemingly for no point in your config). Unlikely to fix THIS problem, but will probably fix the next one you ask about. 2) I see the thing is picking up as a "DMA mode 2" device. I've not seen that with the CF devices and adapters I've used...might want to try disabling the DMA on that device. "man 4 wd" 3) Try another OS on your adapter/MoBo combo. You may find your CF adapter and CF module just don't play nice together (or the CF module and the SATA chip set). I've seen some IDE devices that claimed to do DMA and UDMA and were just plain lying, apparently relying on the fact that Windows would fall back silently and never tell you that the thing was completely screwed up. 4) MIGHT want to try running just the CF card, skip the HD until you see what is going on. I have no reason to believe that will change anything, other than a deep skepticism of everything and the general urge to simplify the heck out of a troublesome system until it is working properly. 5) Those SiI chips suck, or at least their ROMS suck. I've solved a lot of problems by literally prying the ROM off the board on some of those things. I don't think that's your problem, I'm just venting here :) (and since you are trying to boot from these devices, DON'T RIP THE ROM off the board. You need it. :) 6) There may be quirks in OpenBSD. You may be the person who has attached the slowest "disk drive" to a SATA controller and attempted to install and run OpenBSD on it. Or it may be fixed already. I'd suggest trying -current to resolve problems like this. Nick.
