Subject: Re: File system image
To: Luke Mewburn <lukem@netbsd.org>
From: Brian Rose <saider@gate.net>
List: netbsd-users
Date: 02/09/2003 22:19:33
Luke Mewburn wrote:

>On Sat, Feb 08, 2003 at 11:46:32PM -0500, Brian Rose wrote:
>  | I go back to the kernel conf file and change the MEMORY_DISK_ROOT_SIZE 
>  | from 2880 (1.44M) to 32768 (16M). I rebuild and go through the same 
>  | process and the kernel does not boot. I tried explicitly setting the 
>  | size with the -s option on makefs and setting the kernel image size with 
>  | 'mdsetimage -s'. No (good) luck.
>
>Have you tried gzipping the kernel before boot?
>
>There could also be a kernel-size limitation in the bootblocks that
>you're using; try using the bootblocks from -current, which may have
>resolved this problem (since they've had a rewrite recently).
>
>Luke.
>  
>
I discovered that by making a 4M image instead of a 16M image, I could 
get everything to work.

I also tried gzipping the 16M ramdisk kernel, and it still failed. The 
gzipped kernel was around 2M. My guess at this point is that there is 
not enough RAM for the kernel and the ramdisk to run in. So what is a 
good way to get a detailed report as to how the RAM is being used? The 
dmesg output below indicates that a typical 1.6.0 kernel will have about 
24M free. This sounds like it should be enough for the 16M ramdisk, plus 
any overhead.

For Perry, below is the dmesg output. I don't even see the DiskOnChip in 
there. If I recall, it is only active if the primary IDE drive is not 
present. Since I have a 2.5" IDE drive plugged in, I can't see the DOC. 
I'm going to scrounge for a floppy drive, so I can boot a kernel and see 
if the DOC shows up in the dmesg output. For reference, this is a AAEON 
PCM-5894 single board computer. I got it about 5 years ago when I went 
to a training class. The specsheet is here.
ftp://data.aaeon.com.tw/download/MANUAL/PCM-5894Manual.pdf

The DOC should look like the primary master drive and so I would guess 
that it would show up as wd0. But I need to unplug my IDE drive first. 
But since I don't have a floppy plugged in, I would have no way to boot 
the machine.

Again, thanks for all the help.

Brian


dmesg (for the normal kernel on IDE hard disk):
-------------------------------------------------
NetBSD 1.6 (GENERIC) #0: Sun Sep  8 19:43:40 UTC 2002
    
autobuild@tgm.daemon.org:/autobuild/i386/OBJ/autobuild/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium/MMX (586-class), 200.47 MHz
cpu0: features 8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
cpu0: features 8001bf<MMX>
total memory = 32380 KB
avail memory = 23568 KB
using 430 buffers containing 1720 KB of memory
BIOS32 rev. 0 found at 0xfb330
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: Silicon Integrated System 5597/5598 host bridge (rev. 0x02)
pcib0 at pci0 dev 1 function 0
pcib0: Silicon Integrated System 85C503 or 5597/5598 ISA bridge (rev. 0x01)
pciide0 at pci0 dev 1 function 1: Silicon Integrated System 5597/5598 
IDE controller (rev. 0xd0)
pciide0: bus-master DMA support present
pciide0: primary channel configured to compatibility mode
wd0 at pciide0 channel 0 drive 0: <TOSHIBA MK1002MAV>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 1033 MB, 2100 cyl, 16 head, 63 sec, 512 bytes/sect x 2116800 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel configured to compatibility mode
pciide0: secondary channel ignored (disabled)
ohci0 at pci0 dev 1 function 2: Silicon Integrated System 5597/5598 USB 
host controller (rev. 0x10)
ohci0: interrupting at irq 11
ohci0: OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: Silicon Integra OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
rtk0 at pci0 dev 11 function 0: RealTek 8139 10/100BaseTX
rtk0: interrupting at irq 15
rtk0: Ethernet address 52:54:4c:74:37:15
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vga1 at pci0 dev 13 function 0: Chips and Technologies 65554 (rev. 0xc2)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
lpt0 at isa0 port 0x378-0x37b irq 7
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
isapnp0: no ISA Plug 'n Play devices found
biomask 6f65 netmask ef65 ttymask ffe7
Kernelized RAIDframe activated
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)