[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Root Device : " prompt on Sparc64



Forgot the dmesg... here it is:

console is /pci_(_at_)_1f,0/isa_(_at_)_7/serial_(_at_)_0,3f8
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2002 OpenBSD. All rights reserved. 
http://www.OpenBSD.org

OpenBSD 3.1 (GENERIC) #51: Sat Apr 13 14:17:56 PDT 2002
   
deraadt_(_at_)_sparc64_(_dot_)_openbsd_(_dot_)_org:/usr/src/sys/arch/sparc64/compile/GENERIC
total memory = 134217728
avail memory = 115023872
using 819 buffers containing 6709248 of memory
bootpath: /pci_(_at_)_1f,0/ide_(_at_)_d,0/disk_(_at_)_2,0
mainbus0 (root): SUNW,UltraAX-i2
cpu0 at mainbus0: SUNW,UltraSPARC-IIe @ 500 MHz, version 0 FPU
cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 256K
external (64 b/l)
psycho0 at mainbus0
SUNW,sabre: impl 0, version 0: ign 7c0 bus range 0 to 0; PCI bus 0
IOTDB: 607c6000 to 60846000
pci0 at psycho0
ebus0 at pci0 dev 7 function 0 "Acer Labs M1543 PCI-ISA" rev 0x00
dma at ebus0 addr 0-ffff ipl 42 not configured
rtc0 at ebus0 addr 70-71: m5819
power at ebus0 addr 2000-2007 ipl 35 not configured
SUNW,lomh at ebus0 addr 8010-8011 ipl 42 not configured
com0 at ebus0 addr 3f8-3ff ipl 43: ns16550a, 16 byte fifo
com0: console
com1 at ebus0 addr 2e8-2ef ipl 43: ns16550a, 16 byte fifo
flashprom at ebus0 addr 0-7ffff not configured
"Acer Labs M7101 Power Mgmt" rev 0x00 at pci0 dev 3 function 0 not
configured
"Acer Labs M7101 Power Mgmt" rev 0x00 at pci0 dev 3 function 0 not
configured
dc0 at pci0 dev 12 function 0 "Davicom Technologies DM9102" rev 0x31:
ivec 3006 address 00:03:ba:16:91:c5
ukphy0 at dc0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x00606e, model 0x0004, rev. 0
dc1 at pci0 dev 5 function 0 "Davicom Technologies DM9102" rev 0x31:
ivec 301c address 00:03:ba:16:91:c6
ukphy1 at dc1 phy 1: Generic IEEE 802.3u media interface
ukphy1: OUI 0x00606e, model 0x0004, rev. 0
ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec 24,
OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: vendor 0x0000 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc3:
DMA, channel 0 configured to native-PCI, channel 1 configured to
native-PCI
pciide0: using ivec 180c for native-PCI interrupt
wd0 at pciide0 channel 1 drive 0: <ST340016A>
wd0: 16-sector PIO, LBA, 38166MB, 16383 cyl, 16 head, 63 sec, 78165360
sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <TEAC, CD-224E, 1.7A> SCSI0 5/cdrom
removable
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4
pcons at mainbus0 not configured
No counter-timer -- using %tick at 500MHz as system clock.
root device : w0d\^H \^H\^H \^Hd0a
swap device (default wd0b): 
root on wd0a
rootdev=0xc00 rrootdev=0x1a00 rawdev=0x1a02

On Fri, 2002-09-27 at 10:28, Phillip Walters wrote:
> Hello,
> 
> I recently installed OpenBSD 3.1 on a Sparc64.  The install went smooth,
> and everything runs fine.  The only problem I've come across is when
> it's booting, I get a prompt asking me for the root and swap devices. 
> Of course, putting that information in makes it work, but I need to be
> able to reboot the machine remotely.
> 
> I looked around Google and the archives and found a couple of other
> people with the same kind of problem.  The solution that they suggested
> was to build a custom kernel with one change in the configuration file:
> 
> config          bsd     swap generic => config          bsd     root on
> wd0a swap on wd0b
> 
> I changed this, but got the following error:
> 
> bash# config NEW
> NEW:19: bsd: can't make root device from `wd0a'
> NEW:19: bsd: can't make swap device from `wd0b'
> NEW has no configurations!
> *** Stop.
> 
> I was wondering if anyone could show me what I was doing wrong, or give
> me some other things that might need checking.  Your help is greatly
> appreciated.  Thanks!
> 
-- 
Phillip Walters
LinkLINE Communications
pwalters_(_at_)_linkline_(_dot_)_com