From owner-freebsd-small Mon Apr 2 11:13:36 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id B379B37B71D for ; Mon, 2 Apr 2001 11:13:30 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f32IFsA30127 for ; Mon, 2 Apr 2001 13:15:54 -0500 Message-ID: <3AC8C147.950B1F41@aurora.regenstrief.org> Date: Mon, 02 Apr 2001 18:13:27 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: problems with DiskOnChip ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, please lend me a hand with DiskOnChip. I have one stone with 8 MB, it's got MD-2800-008 printed on the chip. I got FreeBSD-4.2-RELEASE. Configured as device fla0 at isa? and properly detected as in: fla0 at iomem 0xc8000-0xc9fff on isa0 fla0: fla0: 7.8MB (15920 sectors), 995 cyls, 16 heads, 1 S/T, 512 B/S Getting a disklabel onto them was a pain. But I have had a hard time with disklabeling since the old days of 386BSD were past. Someone's being too smart now :-). Anyway, I finally got the disklabel on, but it was pure luck. Playing around with whether or not to write the boot blocks etc. Once the disklabel was right I could newfs. But in disklabel and mount operations I get a bunch of stray interrupt (#7) warnings and it says that partition size != filesystem size or something. But I can read and write just fine. Except during boot. This is what happens: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)kernel.gz boot: ? . .. bin sbin usr mnt etc dev stand boot.config kernel.config kernel.gz var boot kernel (so it appears to be able to access the disk, reading the label from it) But when I try to boot I get this: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)? boot: kernel Disk error 0x1 (lba=0x1768) Invalid format Strange enough, I will get the same when I then try to boot from floppy instead: >> FreeBSD/i386 BOOT Default: 0:fd(0,a)? boot: 0:fd(0,a)? . .. kernel.gz fs.PICOBSD.gz boot etc kernel.config boot.config config.tar.gz >> FreeBSD/i386 BOOT Default: 0:fd(0,a)? boot: 0:fd(0,a)kernel.gz Invalid format So, may be the boot sector is still no good. Oh man, that means back to the argument with Mr. Disklabel :-( Here are dumps from fdisk and disklabel: ngigw1>fdisk fla0 ******* Working on device /dev/fla0 ******* parameters extracted from in-core disklabel are: cylinders=995 heads=16 sectors/track=1 (16 blks/cyl) parameters to be used for BIOS calculations are: cylinders=995 heads=16 sectors/track=1 (16 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 ngigw1>disklabel -r fla0 # /dev/fla0c: type: unknown disk: fla0s1 label: ngigw2-root flags: bytes/sector: 512 sectors/track: 1 tracks/cylinder: 16 sectors/cylinder: 16 cylinders: 995 sectors/unit: 15920 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 15919 0 4.2BSD 512 4096 5 # (Cyl. 0 - 994*) c: 15919 0 unused 0 0 # (Cyl. 0 - 994*) And this is what happens when I mount: ngigw1>mount /dev/fla0a /mnt stray irq 7 fla0: raw partition size != slice size fla0: start 0, end 15919, size 15920 stray irq 7 fla0c: start 0, end 15918, size 15919 Isn't this weird? The partition entry always slips from the first to the fourth partition. Trying to configure without a proper partition table (i.e., use raw disk) doesn't work either... What should I do, what's wrong here? Anybody having more luck with this? Any help is much appreciated! -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message