Date: Mon, 02 Apr 2001 21:08:34 +0200 From: Michael Bretterklieber <mbretter@inode.at> To: small@freebsd.org Subject: Re: problems with DiskOnChip ... Message-ID: <3AC8CE32.C9F33B34@inode.at> References: <3AC8C147.950B1F41@aurora.regenstrief.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gunther Schadow schrieb: > 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: <M-Systems DiskOnChip 8MB> > 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: I use 4 an 8 MB DiskOnChip. I modified the build-scripts from PicoBSD to produce dump-able images. - build-script: ca. Line 289: dialog --menu "Set floppy size" 15 70 5 \ 1440 "1.44MB" 1720 "1.72MB" \ 2880 "2.88MB" 3944 "DOC 4MB" 7960 "DOC 8MB" 2> ${RISU} || rm ${RISU} - stage1-script: ca. Line 181: if [ ${FLOPPY_SIZE} = "3944" ]; then disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn0 doc2k4 || \ fail $? disklabel elif [ ${FLOPPY_SIZE} = "7960" ]; then disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn0 doc2k8 || \ fail $? disklabel else disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn0 fd1440 || \ fail $? disklabel fi Here are my /etc/disktab entries: doc2k4|DiskOnChip 2000 4MB Chip:\ :dt=ESDI:ty=winchester:se#512:nt#512:nt#8:ns#1:nc#986:\ :pa#7888:oa#0:ba#0:fa#0:ta=4.2BSD:\ :pc#7888:oc#0:bc#0:fc#0: doc2k8|DiskOnChip 2000 8MB Chip:\ :dt=ESDI:ty=winchester:se#512:nt#512:nt#16:ns#1:nc#995:\ :pa#15920:oa#0:ba#0:fa#0:ta=4.2BSD:\ :pc#15920:oc#0:bc#0:fc#0: It works great, but I found, if the gziped mfs-tree exceeds a significant size, weird things happen with the boot-loader. First the loader can not read the loader.rc-file. It seems, that the file ist empty, but it isn't. If the mfs-tree image grows more and more, than the loader produces DiskErrors. I use PicoBSD based on 3.5.1, but after FreeBSD 4.3 is released, I try PicoBSD based this and maybe this error does'nt exist any more (I hope so). bye, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AC8CE32.C9F33B34>