Re: Problem booting from wd0

2005-06-15 Thread Uwe Heinz Rudi Dippel
OP?  What is OP?

Original Post, sorry.


In any case, I'm curious to know the outcome,

Uwe



Re: Problem booting from wd0

2005-06-15 Thread Tobias Weingartner
On Thursday, June 16, Uwe Dippel wrote:
> > 
> > It installs your PBR boot block, IE: your partition boot block.
> 
> Thanks for the info ! - But still, I don't see how this comes into view:
> the kernel was looking 'broken' at loading in the OP;

OP?  What is OP?


> then he wiped the MBR.
> 
> Should he not better
> fdisk -u wd0
> to get the MBR back ?

That's one way.

--Toby.



Re: Problem booting from wd0

2005-06-15 Thread Uwe Dippel
On Wed, 15 Jun 2005 13:07:06 -0600, Tobias Weingartner wrote:

>> > Use dd form /dev/zero to wipe MBR and start of disk.

>> what does installboot do here ? Maybe I'm simply lost or stupid.?
> 
> It installs your PBR boot block, IE: your partition boot block.

Thanks for the info ! - But still, I don't see how this comes into view:
the kernel was looking 'broken' at loading in the OP;
then he wiped the MBR.

Should he not better
fdisk -u wd0
to get the MBR back ?

Trying to understand ...

Uwe



Re: Problem booting from wd0

2005-06-15 Thread Tobias Weingartner
On Wednesday, June 15, Uwe Dippel wrote:
> On Tue, 14 Jun 2005 12:06:14 -0500, arf wrote:
> 
> > Use dd form /dev/zero to wipe MBR and start of disk.
> > Check Bios settings - AMI Bios set to "Auto" shows 
> > LBA mode and DMA, etc.
> 
> > boot: /mnt/boot
> > proto: /usr/mdec/biosboot
> > device: /dev/rwd0c
> > /usr/mdec/biosboot: entry point 0 proto bootblock
> > size 512
> > /mnt/boot is 3 blocks x 16384 bytes fs block shift 2;
> > part offset 63; inode block 24, offset 1704
> > using MBR partition 0: type 166 (0xa6) offset 63 (0x3f)
> 
> what does installboot do here ? Maybe I'm simply lost or stupid.?

It installs your PBR boot block, IE: your partition boot block.
You need an MBR...  fdisk can do that for you if you wish...

--Toby.



Re: Problem booting from wd0

2005-06-15 Thread Uwe Dippel
On Tue, 14 Jun 2005 12:06:14 -0500, arf wrote:

> Use dd form /dev/zero to wipe MBR and start of disk.
> Check Bios settings - AMI Bios set to "Auto" shows 
> LBA mode and DMA, etc.

I'm not so sure here; what this would be good for.

> Downloaded June 10 snapshot and checked md5 sums.
> 
> Installed without problems. The installboot output
> was:
> boot: /mnt/boot
> proto: /usr/mdec/biosboot
> device: /dev/rwd0c
> /usr/mdec/biosboot: entry point 0 proto bootblock
> size 512
> /mnt/boot is 3 blocks x 16384 bytes fs block shift 2;
> part offset 63; inode block 24, offset 1704
> using MBR partition 0: type 166 (0xa6) offset 63 (0x3f)

what does installboot do here ? Maybe I'm simply lost or stupid.?

You're doing a fresh install, or what ?
How's your disk layout ?
(And, as Nick pointed out, does it boot from diskette / CD ?)
http://www.openbsd.org/faq/faq8.html#Bootloader

http://www.openbsd.org/faq/faq14.html#Boot386
scroll down to 
What can go wrong
and understand how to recreate the MBR.

HTH,

Uwe,

who runs a 160GB hard disk without any hassle on a 1995 P100 MB with a
limit of 8GB hard disk; and a root partition of 150 MB at 'a'. With the
completely wrong geometry. I guess, as long as the '/' is found somehow,
the rest is taken over from the BIOS.



Re: Problem booting from wd0

2005-06-14 Thread Nick Holland
arf wrote:
> Thanks for all the suggestions. It appears to be a
> problem with disk block mapping even though LBA mode
> is used. 

huh?  What is the evidence?

> In light of the suggestions, this is what I
> did today:
> 
> Use dd form /dev/zero to wipe MBR and start of disk.
> Check Bios settings - AMI Bios set to "Auto" shows 
> LBA mode and DMA, etc.
> 
> Downloaded June 10 snapshot and checked md5 sums.
> 
> Installed without problems. The installboot output
> was:
> boot: /mnt/boot
> proto: /usr/mdec/biosboot
> device: /dev/rwd0c
> /usr/mdec/biosboot: entry point 0 proto bootblock
> size 512
> /mnt/boot is 3 blocks x 16384 bytes fs block shift 2;
> part offset 63; inode block 24, offset 1704
> using MBR partition 0: type 166 (0xa6) offset 63 (0x3f)
> 
> When I attempted to reboot from disk, the system hung at:
> Searching for Boot Record from IDE-0..OK

that's worse.
It didn't even manage to load the MBR boot loader.
Previously, you got the MBR, the partition boot record (PBR), and /boot
loaded, it died loading the kernel.

That's consistant with having zeroed the MBR (though since you didn't
say HOW you did it, I'm not going to say anything is "final" there), but
didn't properly restore it (and since you didn't indicate how you did
that, I think that's a very safe bet).

Let's step back a bit here.
If you boot from the CDROM (or floppy), you get to a cdrom> or boot>
prompt.  What happens if you, at that prompt, tell it
   boot hd0a:/bsd

If it boots properly there, that means your boot code is hosed.  Well,
actually, I'm convinced your boot code is hosed, it would be nice to see
something actually working, though, right?

If using the boot floppy or CD that way DOESN'T work, you have multiple
problems.

Nick.



Re: Problem booting from wd0

2005-06-14 Thread arf
Thanks for all the suggestions. It appears to be a
problem with disk block mapping even though LBA mode
is used. In light of the suggestions, this is what I
did today:

Use dd form /dev/zero to wipe MBR and start of disk.
Check Bios settings - AMI Bios set to "Auto" shows 
LBA mode and DMA, etc.

Downloaded June 10 snapshot and checked md5 sums.

Installed without problems. The installboot output
was:
boot: /mnt/boot
proto: /usr/mdec/biosboot
device: /dev/rwd0c
/usr/mdec/biosboot: entry point 0 proto bootblock
size 512
/mnt/boot is 3 blocks x 16384 bytes fs block shift 2;
part offset 63; inode block 24, offset 1704
using MBR partition 0: type 166 (0xa6) offset 63 (0x3f)

When I attempted to reboot from disk, the system hung at:
Searching for Boot Record from IDE-0..OK

The dmesg from the CD boot is:
OpenBSD 3.7-current (RAMDISK_CD) #686: Fri Jun 10 15:02:20 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: AMD Duron(tm)  ("AuthenticAMD" 686-class, 64KB L2 cache) 1.62 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 637050880 (622120K)
avail mem = 574648320 (561180K)
using 4278 buffers containing 31956992 bytes (31208K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 04/09/04, BIOS32 rev. 0 @ 0xfdb10
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf7c90/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:02:0 ("SIS 85C503 System" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "SIS 741 PCI" rev 0x03
ppb0 at pci0 dev 1 function 0 "SIS 648FX AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SIS 6330 VGA" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 "SIS 85C503 System" rev 0x25
pciide0 at pci0 dev 2 function 5 "SIS 5513 EIDE" rev 0x00: 741: DMA, channel 0 
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 38166MB, 78165360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  SCSI0 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
"SIS 7012 AC97" rev 0xa0 at pci0 dev 2 function 7 not configured
ohci0 at pci0 dev 3 function 0 "SIS 5597/5598 USB" rev 0x0f: irq 10, version 
1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: SIS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 3 function 1 "SIS 5597/5598 USB" rev 0x0f: irq 10, version 
1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: SIS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0 at pci0 dev 3 function 2 "SIS 7002 USB" rev 0x00: irq 10
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: SIS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
sis0 at pci0 dev 4 function 0 "SIS 900 10/100BaseTX" rev 0x90: irq 10, address 
00:0b:6a:60:41:8a
rlphy0 at sis0 phy 1: RTL8201L 10/100 PHY, rev. 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask ffe5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
wd0: no disk label
root on rd0a
rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02

Thanks for any suggestions.



Re: Problem booting from wd0

2005-06-13 Thread Nick Holland
arf wrote:
> I am trying to install 3.7 on a cheap PC.

heh.  I could use some "cheap" PCs of that caliber. :)

> The system boots fine from the CD and installs
> without problems. However, when I try to reboot
> from disk, I only get:
> 
> booting hd0a:/bsd: 4729760read text: Invalid argument
>  failed(22). will try /obsd

looks like you got a bad kernel there.  That's too early in the boot
process for a simple compatability problem...that message indicates the
kernel didn't load properly...it wasn't even trying to be executed at
that point.

Either a kernel in mid-upgrade on the FTP servers, or a kernel (and
possibly *.tgz?) from a wrong platform (yeah, I've done that), a kernel
downloaded to a Windows machine using the (default) ASCII transfer mode
or something similar.  I suppose a bad spot on the hard disk could cause
that, too...

In short: be thinking something really basic is wrong.

Nick.



Problem booting from wd0

2005-06-13 Thread arf
I am trying to install 3.7 on a cheap PC.
The system boots fine from the CD and installs
without problems. However, when I try to reboot
from disk, I only get:

booting hd0a:/bsd: 4729760read text: Invalid argument
 failed(22). will try /obsd

I am trying to use a recent snapshot; here is the
dmesg from a CD boot:
OpenBSD 3.7-current (RAMDISK_CD) #669: Wed Jun  1 14:41:52 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: AMD Duron(tm)  ("AuthenticAMD" 686-class, 64KB L2 cache) 1.62 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 637050880 (622120K)
avail mem = 574648320 (561180K)
using 4278 buffers containing 31956992 bytes (31208K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 04/09/04, BIOS32 rev. 0 @ 0xfdb10
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf7c90/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:02:0 ("SIS 85C503 System" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "SIS 741 PCI" rev 0x03
ppb0 at pci0 dev 1 function 0 "SIS 648FX AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SIS 6330 VGA" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 "SIS 85C503 System" rev 0x25
pciide0 at pci0 dev 2 function 5 "SIS 5513 EIDE" rev 0x00: 741: DMA, channel 0 
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 38166MB, 78165360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  SCSI0 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
"SIS 7012 AC97" rev 0xa0 at pci0 dev 2 function 7 not configured
ohci0 at pci0 dev 3 function 0 "SIS 5597/5598 USB" rev 0x0f: irq 10, version 
1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: SIS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 3 function 1 "SIS 5597/5598 USB" rev 0x0f: irq 10, version 
1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: SIS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0 at pci0 dev 3 function 2 "SIS 7002 USB" rev 0x00: irq 10
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: SIS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
sis0 at pci0 dev 4 function 0 "SIS 900 10/100BaseTX" rev 0x90: irq 10, address 
00:0b:6a:60:41:8a
rlphy0 at sis0 phy 1: RTL8201L 10/100 PHY, rev. 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask ffe5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
root on rd0a
rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02

Thanks for any suggestions.