Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-05 Thread Stuart Henderson
On 2009/07/04 23:04, Brynet wrote:
 Stuart Henderson wrote:
  some of the Atom boards seem to need APIC; if you want to stick with
  4.5 then try the GENERIC.MP kernel (bsd.mp); otherwise try a -current
  snapshot (where APIC is used in GENERIC as well as GENERIC.MP).
 
 Hi sthen,
 
 OpenBSD 4.5 shipped with APIC/IOAPIC in the SP kernel, it's not longer
 needed to boot MP kernels. :-)

Ah, you're right, I thought it was more recent than that.



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-05 Thread Otto Moerbeek
On Sat, Jul 04, 2009 at 07:44:16PM -0400, Hendrickson, Kenneth wrote:

 This is a very disappointing result!!! :-(
 
 I am trying to recover old data from a ccd device, on a
 Promise hard drive controller card.
 
 If I cannot use the Promise HDD controller card, then I
 cannot recover my data.

Use another system that's booting ok and put the promise cards with
its disks into it. 

-Otto

 
 If I must use another PCI video card, then I will not be
 able to use the Promise HDD controller card, because my
 motherboard has only 1 PCI slot.
 
 So this will defeat the entire purpose!
 
 If anybody else has any suggestions, please let me know!
 
 Thanks,
 Kenneth J. Hendrickson
 
 
 
 -Original Message-
 From: Mike Belopuhov [mailto:mi...@lucifier.net]
 Sent: Sat 7/4/2009 6:39 PM
 To: Hendrickson, Kenneth
 Subject: Re: Cannot Boot with Intel D201GLY Motherboard
 
 
 you have to put a PCI video card in. it's SiS video that blows things up.
 though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody
 has figured out what's actually is a problem because of the lack of this
 hardware.
 
 On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote:
  Cannot Boot with Intel D201GLY Motherboard
 
  Disk is 120GB PATA IDE
 
  dmesg, fdisk output, and disklabel output are all attached
  OpenBSD.PDR is also attached
 
  I have Googled for problems/answers, and still run into a dead end.
 
  There must be a requirement which is not stated in the documentation,
  which I am not following.  Please help.
 
  (I am an experienced OpenBSD user, having used OpenBSD continuously
  since 1998, and having built my own kernels/userland, and also have
  built OpenBSD for embedded systems.)
 
  The instructions for booting from NTLDR (Windows 2000) do not work.
  As soon as the messages get to the CPU, the system reboots.  Booting
  never works, either from the OpenBSD partition, or from NTLDR from
  Windows 2000.  I have included my OpenBSD.PDR file for examination.
 
  Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
  partition, and had both #1 and #4 set to a6 for OpenBSD.  That
  didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
  and #4 partition was set to da for No Filesystem.  That also
  didn't work.  Please note that my entire OpenBSD / filesystem is
  within the 1024 cylinder boundary.  The /boot file is totally
  contained within the 1024 cylinder boundary.  It still won't boot.
  It won't boot on its own, nor will it boot from the Windows 2000
  NTLDR bootloader.
 
  Also note that while my fdisk and disklabel indicates Linux
  partitions, none of them have yet been installed.  I installed
  Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
  to boot, I have not yet installed Linux.
 
  Please help if you can.
 
  Thank you,
  Kenneth J. Hendrickson
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of dmesg]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of fdisk]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of disklabel]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-05 Thread Hendrickson, Kenneth
 perhaps the geometry reported by the pciide(4)
 driver differs from the one determined by the BIOS,

Nope.  I cannot get OpenBSD to boot on my D201GLY motherboard even without the
Promise IDE controller plugged in.  (I've tried both with and without the
Promise IDE controller.)

 However, the best option would be to simply acquire an
 old beige box and install OpenBSD and back up the files
 to another system on your network.

Unfortunately, this seems to be my only option.  It is not good that OpenBSD
will not boot on the D201GLY motherboard.  :-(

Thanks,
Kenneth J. Hendrickson



Re: Cannot Boot with Intel D201GLY Motherboard [dmesg, fdisk, disklabel]

2009-07-05 Thread Hendrickson, Kenneth
 Unfortunately I cannot see your attachments..
 as the lists do not permit them.

I will post them in this message.
However, I cannot post OpenBSD.PBR because it is a binary file.

 As this is a strictly a recovery operating,

I would like to run OpenBSD on my D201GLY motherboard.
It is not strictly a recovery operation.

During booting, the kernel dies very shortly after printing cpu0 at
mainbus0.
However, it boots just fine from the install CD.

-- 8 --

OpenBSD 4.5 (RAMDISK_CD) #1112: Sat Feb 28 15:06:26 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Celeron(R) CPU 220 @ 1.20GHz (GenuineIntel 686-class) 1.21
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR
real mem  = 935886848 (892MB)
avail mem = 898048000 (856MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/22/07, SMBIOS rev. 2.4 @ 0xe4da0 (23
entries)
bios0: vendor Intel Corp. version LY66210M.86A.0122.2007.0822.2001 date
08/22/2007
bios0: Intel Corporation D201GLY
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 14, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P1)
bios0: ROM list: 0xc/0x1 0xd/0xa000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 SiS 662 PCI rev 0x01
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 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 SiS 964 ISA rev 0x36
pciide0 at pci0 dev 2 function 5 SiS 5513 EIDE rev 0x01: 964: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: WDC WD1200AB-00CBA1
wd0: 16-sector PIO, LBA, 114473MB, 234441648 sectors
atapiscsi0 at pciide0 channel 0 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: CDRW, 52X32X, TA32 ATAPI 5/cdrom removable
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
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: apic 4 int 20
(irq 11), version 1.0, legacy support
ohci1 at pci0 dev 3 function 1 SiS 5597/5598 USB rev 0x0f: apic 4 int 21
(irq 10), version 1.0, legacy support
ohci2 at pci0 dev 3 function 2 SiS 5597/5598 USB rev 0x0f: apic 4 int 22
(irq 11), version 1.0, legacy support
ehci0 at pci0 dev 3 function 3 SiS 7002 USB rev 0x00: apic 4 int 23 (irq
10)
ehci0: timed out waiting for BIOS
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 SiS EHCI root hub rev 2.00/1.00 addr 1
sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91: apic 4 int 19
(irq 11), address 00:1c:c0:26:8a:c3
ukphy0 at sis0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI
0x0050ef, model 0x0007
pciide1 at pci0 dev 5 function 0 SiS 181 SATA rev 0x01: DMA
pciide1: using apic 4 int 17 (irq 10) for native-PCI interrupt
ppb1 at pci0 dev 31 function 0 SiS PCI-PCI rev 0x00
pci2 at ppb1 bus 2
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
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: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 SiS OHCI root hub rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 SiS OHCI root hub rev 1.00/1.00 addr 1
usb3 at ohci2: USB revision 1.0
uhub3 at usb3 SiS OHCI root hub rev 1.00/1.00 addr 1
rd0: fixed, 3800 blocks
American Power Conversion Back-UPS RS 900 FW:9.o2 .D USB FW:o2 rev 1.10/1.06
addr 2 at uhub2 port 2 not configured
softraid0 at root
root on rd0a swap on rd0b dump on rd0b

-- 8 --

Disk: wd0   geometry: 232581/16/63 [234441648 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
-
--
 0: A6  0   1   1 -495  15  63 [  63:  499905 ] OpenBSD
*1: 07496   0   1 -  13393  15  63 [  499968:13001184 ]
HPFS/QNX/AUX
 2: 05  13394   0   1 - 202759  15  63 [13501152:   190880928 ] Extended
DOS
 3: DA 202760   0   1 - 232580  15  63 [   204382080:30059568 ] Unknown
ID
Offset: 13501152Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]

Re: Cannot Boot with Intel D201GLY Motherboard [dmesg, fdisk, disklabel]

2009-07-05 Thread Mark Kettenis
 Date: Sun, 5 Jul 2009 07:30:58 -0400
 From: Hendrickson, Kenneth khend...@harris.com
 
  Unfortunately I cannot see your attachments..
  as the lists do not permit them.
 
 I will post them in this message.
 However, I cannot post OpenBSD.PBR because it is a binary file.
 
  As this is a strictly a recovery operating,
 
 I would like to run OpenBSD on my D201GLY motherboard.
 It is not strictly a recovery operation.
 
 During booting, the kernel dies very shortly after printing cpu0 at
 mainbus0.
 However, it boots just fine from the install CD.

Given the fact that the machine boots just fine from the CD you could
try the following:

1. Boot from CD; interrupt the bootloader.

2. type boot hd0a:/bsd

If that doesn't work, you can try disabling device drivers.

1. Boot from disk; interrupt the bootloader.

2. type boot /bsd -c

3. at the UKC prompt type disable driver

I'd start with disabling all the ACPI crap:

acpitimer
acpihpet
acpiac
acpibat
acpibtn
acpicpu
acpidock
acpiec
acpivideo
acpivout
acpipwrres

Other drivers that are worth trying are:

azalia
ohci
ehci



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-05 Thread Constantine A. Murenin
2009/7/5 Hendrickson, Kenneth khend...@harris.com:
 However, the best option would be to simply acquire an
 old beige box and install OpenBSD and back up the files
 to another system on your network.

 Unfortunately, this seems to be my only option.  It is not good that
OpenBSD
 will not boot on the D201GLY motherboard.  :-(

You are using i386?  Have you tried amd64?  I have D201GLY2, and IIRC,
with OpenBSD 4.5, the i386 kernel seemed to have been resetting the
box right during the boot process, whereas the amd64 kernel worked
(and still works) without a single problem.

C.



Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
Cannot Boot with Intel D201GLY Motherboard

Disk is 120GB PATA IDE

dmesg, fdisk output, and disklabel output are all attached
OpenBSD.PDR is also attached

I have Googled for problems/answers, and still run into a dead end.

There must be a requirement which is not stated in the documentation,
which I am not following.  Please help.

(I am an experienced OpenBSD user, having used OpenBSD continuously
since 1998, and having built my own kernels/userland, and also have
built OpenBSD for embedded systems.)

The instructions for booting from NTLDR (Windows 2000) do not work.
As soon as the messages get to the CPU, the system reboots.  Booting
never works, either from the OpenBSD partition, or from NTLDR from
Windows 2000.  I have included my OpenBSD.PDR file for examination.

Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
partition, and had both #1 and #4 set to a6 for OpenBSD.  That
didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
and #4 partition was set to da for No Filesystem.  That also
didn't work.  Please note that my entire OpenBSD / filesystem is
within the 1024 cylinder boundary.  The /boot file is totally
contained within the 1024 cylinder boundary.  It still won't boot.
It won't boot on its own, nor will it boot from the Windows 2000
NTLDR bootloader.

Also note that while my fdisk and disklabel indicates Linux
partitions, none of them have yet been installed.  I installed
Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
to boot, I have not yet installed Linux.

Please help if you can.

Thank you,
Kenneth J. Hendrickson

[demime 1.01d removed an attachment of type application/octet-stream which had 
a name of dmesg]

[demime 1.01d removed an attachment of type application/octet-stream which had 
a name of fdisk]

[demime 1.01d removed an attachment of type application/octet-stream which had 
a name of disklabel]

[demime 1.01d removed an attachment of type application/octet-stream which had 
a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
I should mention that booting from the CD install media
works, but booting after installing the OpenBSD 4.5 OS
fails.

Please help if you can.

Thank you,
Kenneth J. Hendrickson

PS  I need to get this box up with OpenBSD in order to
recover some data from a ccd drive on a Pentium 266 MHz
which recently failed.  It was my main file server.  I
do not want to lose my data!

PPS  If I cannot get this D201GLY motherboard up with
OpenBSD, I am willing to buy another motherboard, in
order to get my data back.  But I'd rather not have to
buy another motherboard.  The D201GLY will serve my
purposes if only I can get it to boot!!

-Original Message-
From: Hendrickson, Kenneth
Sent: Sat 7/4/2009 5:00 PM
To: misc@openbsd.org; b...@openbsd.org
Subject: Cannot Boot with Intel D201GLY Motherboard

Cannot Boot with Intel D201GLY Motherboard

Disk is 120GB PATA IDE

dmesg, fdisk output, and disklabel output are all attached
OpenBSD.PDR is also attached

I have Googled for problems/answers, and still run into a dead end.

There must be a requirement which is not stated in the documentation,
which I am not following.  Please help.

(I am an experienced OpenBSD user, having used OpenBSD continuously
since 1998, and having built my own kernels/userland, and also have
built OpenBSD for embedded systems.)

The instructions for booting from NTLDR (Windows 2000) do not work.
As soon as the messages get to the CPU, the system reboots.  Booting
never works, either from the OpenBSD partition, or from NTLDR from
Windows 2000.  I have included my OpenBSD.PDR file for examination.

Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
partition, and had both #1 and #4 set to a6 for OpenBSD.  That
didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
and #4 partition was set to da for No Filesystem.  That also
didn't work.  Please note that my entire OpenBSD / filesystem is
within the 1024 cylinder boundary.  The /boot file is totally
contained within the 1024 cylinder boundary.  It still won't boot.
It won't boot on its own, nor will it boot from the Windows 2000
NTLDR bootloader.

Also note that while my fdisk and disklabel indicates Linux
partitions, none of them have yet been installed.  I installed
Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
to boot, I have not yet installed Linux.

Please help if you can.

Thank you,
Kenneth J. Hendrickson



FW: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
I should mention that booting from the CD install media
works, but booting after installing the OpenBSD 4.5 OS
fails.

Please help if you can.

Thank you,
Kenneth J. Hendrickson

PS  I need to get this box up with OpenBSD in order to
recover some data from a ccd drive on a Pentium 266 MHz
which recently failed.  It was my main file server.  I
do not want to lose my data!

PPS  If I cannot get this D201GLY motherboard up with
OpenBSD, I am willing to buy another motherboard, in
order to get my data back.  But I'd rather not have to
buy another motherboard.  The D201GLY will serve my
purposes if only I can get it to boot!!



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Stuart Henderson
some of the Atom boards seem to need APIC; if you want to stick with
4.5 then try the GENERIC.MP kernel (bsd.mp); otherwise try a -current
snapshot (where APIC is used in GENERIC as well as GENERIC.MP).


On 2009/07/04 17:00, Hendrickson, Kenneth wrote:
 Cannot Boot with Intel D201GLY Motherboard
 
 Disk is 120GB PATA IDE
 
 dmesg, fdisk output, and disklabel output are all attached
 OpenBSD.PDR is also attached
 
 I have Googled for problems/answers, and still run into a dead end.
 
 There must be a requirement which is not stated in the documentation,
 which I am not following.  Please help.
 
 (I am an experienced OpenBSD user, having used OpenBSD continuously
 since 1998, and having built my own kernels/userland, and also have
 built OpenBSD for embedded systems.)
 
 The instructions for booting from NTLDR (Windows 2000) do not work.
 As soon as the messages get to the CPU, the system reboots.  Booting
 never works, either from the OpenBSD partition, or from NTLDR from
 Windows 2000.  I have included my OpenBSD.PDR file for examination.
 
 Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
 partition, and had both #1 and #4 set to a6 for OpenBSD.  That
 didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
 and #4 partition was set to da for No Filesystem.  That also
 didn't work.  Please note that my entire OpenBSD / filesystem is
 within the 1024 cylinder boundary.  The /boot file is totally
 contained within the 1024 cylinder boundary.  It still won't boot.
 It won't boot on its own, nor will it boot from the Windows 2000
 NTLDR bootloader.
 
 Also note that while my fdisk and disklabel indicates Linux
 partitions, none of them have yet been installed.  I installed
 Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
 to boot, I have not yet installed Linux.
 
 Please help if you can.
 
 Thank you,
 Kenneth J. Hendrickson
 
 [demime 1.01d removed an attachment of type application/octet-stream which 
 had a name of dmesg]
 
 [demime 1.01d removed an attachment of type application/octet-stream which 
 had a name of fdisk]
 
 [demime 1.01d removed an attachment of type application/octet-stream which 
 had a name of disklabel]
 
 [demime 1.01d removed an attachment of type application/octet-stream which 
 had a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
This will defeat the entire purpose.

I am trying to recover data from a ccd device on a very old OpenBSD
system.  If I have to plug in a PCI video card, then the PCI slot
will not be available for the Promise PCI hard drive controller.
(There is only 1 PCI slot on this motherboard.)

The only way I can recover my data is with the Promise card.

So this is a very disappointing result.  :-(

If anybody has any other suggestions, please let me know.

Thanks,
Kenneth J. Hendrickson




-Original Message-
From: Mike Belopuhov [mailto:mi...@lucifier.net]
Sent: Sat 7/4/2009 6:39 PM
To: Hendrickson, Kenneth
Subject: Re: Cannot Boot with Intel D201GLY Motherboard


you have to put a PCI video card in. it's SiS video that blows things up.
though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody
has figured out what's actually is a problem because of the lack of this
hardware.

On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote:
 Cannot Boot with Intel D201GLY Motherboard

 Disk is 120GB PATA IDE

 dmesg, fdisk output, and disklabel output are all attached
 OpenBSD.PDR is also attached

 I have Googled for problems/answers, and still run into a dead end.

 There must be a requirement which is not stated in the documentation,
 which I am not following.  Please help.

 (I am an experienced OpenBSD user, having used OpenBSD continuously
 since 1998, and having built my own kernels/userland, and also have
 built OpenBSD for embedded systems.)

 The instructions for booting from NTLDR (Windows 2000) do not work.
 As soon as the messages get to the CPU, the system reboots.  Booting
 never works, either from the OpenBSD partition, or from NTLDR from
 Windows 2000.  I have included my OpenBSD.PDR file for examination.

 Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
 partition, and had both #1 and #4 set to a6 for OpenBSD.  That
 didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
 and #4 partition was set to da for No Filesystem.  That also
 didn't work.  Please note that my entire OpenBSD / filesystem is
 within the 1024 cylinder boundary.  The /boot file is totally
 contained within the 1024 cylinder boundary.  It still won't boot.
 It won't boot on its own, nor will it boot from the Windows 2000
 NTLDR bootloader.

 Also note that while my fdisk and disklabel indicates Linux
 partitions, none of them have yet been installed.  I installed
 Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
 to boot, I have not yet installed Linux.

 Please help if you can.

 Thank you,
 Kenneth J. Hendrickson

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of dmesg]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of fdisk]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of disklabel]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
This is a very disappointing result!!! :-(

I am trying to recover old data from a ccd device, on a
Promise hard drive controller card.

If I cannot use the Promise HDD controller card, then I
cannot recover my data.

If I must use another PCI video card, then I will not be
able to use the Promise HDD controller card, because my
motherboard has only 1 PCI slot.

So this will defeat the entire purpose!

If anybody else has any suggestions, please let me know!

Thanks,
Kenneth J. Hendrickson



-Original Message-
From: Mike Belopuhov [mailto:mi...@lucifier.net]
Sent: Sat 7/4/2009 6:39 PM
To: Hendrickson, Kenneth
Subject: Re: Cannot Boot with Intel D201GLY Motherboard


you have to put a PCI video card in. it's SiS video that blows things up.
though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody
has figured out what's actually is a problem because of the lack of this
hardware.

On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote:
 Cannot Boot with Intel D201GLY Motherboard

 Disk is 120GB PATA IDE

 dmesg, fdisk output, and disklabel output are all attached
 OpenBSD.PDR is also attached

 I have Googled for problems/answers, and still run into a dead end.

 There must be a requirement which is not stated in the documentation,
 which I am not following.  Please help.

 (I am an experienced OpenBSD user, having used OpenBSD continuously
 since 1998, and having built my own kernels/userland, and also have
 built OpenBSD for embedded systems.)

 The instructions for booting from NTLDR (Windows 2000) do not work.
 As soon as the messages get to the CPU, the system reboots.  Booting
 never works, either from the OpenBSD partition, or from NTLDR from
 Windows 2000.  I have included my OpenBSD.PDR file for examination.

 Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
 partition, and had both #1 and #4 set to a6 for OpenBSD.  That
 didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
 and #4 partition was set to da for No Filesystem.  That also
 didn't work.  Please note that my entire OpenBSD / filesystem is
 within the 1024 cylinder boundary.  The /boot file is totally
 contained within the 1024 cylinder boundary.  It still won't boot.
 It won't boot on its own, nor will it boot from the Windows 2000
 NTLDR bootloader.

 Also note that while my fdisk and disklabel indicates Linux
 partitions, none of them have yet been installed.  I installed
 Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
 to boot, I have not yet installed Linux.

 Please help if you can.

 Thank you,
 Kenneth J. Hendrickson

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of dmesg]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of fdisk]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of disklabel]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Hendrickson, Kenneth
Disabling acpi (in OpenBSD 4.5) does not work.

Any help would be appreciated.  I do *not* want to lose my old data!

Thanks,
Ken Hendrickson




-Original Message-
From: Mike Belopuhov [mailto:mi...@lucifier.net]
Sent: Sat 7/4/2009 6:39 PM
To: Hendrickson, Kenneth
Subject: Re: Cannot Boot with Intel D201GLY Motherboard


you have to put a PCI video card in. it's SiS video that blows things up.
though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody
has figured out what's actually is a problem because of the lack of this
hardware.

On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote:
 Cannot Boot with Intel D201GLY Motherboard

 Disk is 120GB PATA IDE

 dmesg, fdisk output, and disklabel output are all attached
 OpenBSD.PDR is also attached

 I have Googled for problems/answers, and still run into a dead end.

 There must be a requirement which is not stated in the documentation,
 which I am not following.  Please help.

 (I am an experienced OpenBSD user, having used OpenBSD continuously
 since 1998, and having built my own kernels/userland, and also have
 built OpenBSD for embedded systems.)

 The instructions for booting from NTLDR (Windows 2000) do not work.
 As soon as the messages get to the CPU, the system reboots.  Booting
 never works, either from the OpenBSD partition, or from NTLDR from
 Windows 2000.  I have included my OpenBSD.PDR file for examination.

 Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
 partition, and had both #1 and #4 set to a6 for OpenBSD.  That
 didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
 and #4 partition was set to da for No Filesystem.  That also
 didn't work.  Please note that my entire OpenBSD / filesystem is
 within the 1024 cylinder boundary.  The /boot file is totally
 contained within the 1024 cylinder boundary.  It still won't boot.
 It won't boot on its own, nor will it boot from the Windows 2000
 NTLDR bootloader.

 Also note that while my fdisk and disklabel indicates Linux
 partitions, none of them have yet been installed.  I installed
 Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
 to boot, I have not yet installed Linux.

 Please help if you can.

 Thank you,
 Kenneth J. Hendrickson

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of dmesg]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of fdisk]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of disklabel]

 [demime 1.01d removed an attachment of type application/octet-stream which
had a name of OpenBSD.PDR]



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Brynet
Hi Ken,

Unfortunately I cannot see your attachments.. as the lists do not permit them.

As this is a strictly a recovery operating, ffsrv is rumoured to
work for some people on Windows.. but it probably won't help you
because of the ccd(4) setup.

I cannot explain the problem you're facing, but it is possible that
perhaps the geometry reported by the pciide(4) driver differs from the
one determined by the BIOS, confusing the boot loader.

One entirely unsupported option might be to use QEMU for Windows to
access the raw disks, i.e: if there are 3 drives in the computer.

(Examples..)
\\.\PhysicalDrive0 == Windows 2000 boot drive.
\\.\PhysicalDrive1 == OpenBSD device, start of ccd(4).
\\.\PhysicalDrive2 == OpenBSD drive, end of ccd(4).

Create an image with qemu-img(1), hdd.img for example.. enough for OpenBSD.
C:\QEMU\qemu.exe -L. -m 256 -hda hdd.img -hdb \\.\PhysicalDrive1 -hdc
\\.\PhysicalDrive2 -cdrom install45.iso -boot d

Now presumably you could install OpenBSD inside QEMU, baring any bugs
in the emulation.. wd1/wd2 should be the 2 physical devices, and the
labels you created on them should remaining, you'll simply need to
setup ccd(4) inside the environment and then backup the files to your
host system.

However, the best option would be to simply acquire an old beige box
and install OpenBSD and back up the files to another system on your
network.

http://ffsdrv.sf.net/
http://www.h7.dion.ne.jp/~qemu-win/
http://www.freecycle.org/

HTH.

-Brynet



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Brynet
Stuart Henderson wrote:
 some of the Atom boards seem to need APIC; if you want to stick with
 4.5 then try the GENERIC.MP kernel (bsd.mp); otherwise try a -current
 snapshot (where APIC is used in GENERIC as well as GENERIC.MP).

Hi sthen,

OpenBSD 4.5 shipped with APIC/IOAPIC in the SP kernel, it's not longer
needed to boot MP kernels. :-)

-Brynet.



Re: Cannot Boot with Intel D201GLY Motherboard

2009-07-04 Thread Duncan Patton a Campbell
On Sat, 4 Jul 2009 20:21:12 -0400
Hendrickson, Kenneth khend...@harris.com wrote:

 Disabling acpi (in OpenBSD 4.5) does not work.
 
 Any help would be appreciated.  I do *not* want to lose my old data!
 

Buy a new /root disk.  They are cheap.

Dhu

 Thanks,
 Ken Hendrickson
 
 
 
 
 -Original Message-
 From: Mike Belopuhov [mailto:mi...@lucifier.net]
 Sent: Sat 7/4/2009 6:39 PM
 To: Hendrickson, Kenneth
 Subject: Re: Cannot Boot with Intel D201GLY Motherboard
 
 
 you have to put a PCI video card in. it's SiS video that blows things up.
 though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody
 has figured out what's actually is a problem because of the lack of this
 hardware.
 
 On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote:
  Cannot Boot with Intel D201GLY Motherboard
 
  Disk is 120GB PATA IDE
 
  dmesg, fdisk output, and disklabel output are all attached
  OpenBSD.PDR is also attached
 
  I have Googled for problems/answers, and still run into a dead end.
 
  There must be a requirement which is not stated in the documentation,
  which I am not following.  Please help.
 
  (I am an experienced OpenBSD user, having used OpenBSD continuously
  since 1998, and having built my own kernels/userland, and also have
  built OpenBSD for embedded systems.)
 
  The instructions for booting from NTLDR (Windows 2000) do not work.
  As soon as the messages get to the CPU, the system reboots.  Booting
  never works, either from the OpenBSD partition, or from NTLDR from
  Windows 2000.  I have included my OpenBSD.PDR file for examination.
 
  Originally, my OpenBSD partition was #4 in fdisk.  I added the #1
  partition, and had both #1 and #4 set to a6 for OpenBSD.  That
  didn't work.  I then chose only #1 partition to be a6 for OpenBSD,
  and #4 partition was set to da for No Filesystem.  That also
  didn't work.  Please note that my entire OpenBSD / filesystem is
  within the 1024 cylinder boundary.  The /boot file is totally
  contained within the 1024 cylinder boundary.  It still won't boot.
  It won't boot on its own, nor will it boot from the Windows 2000
  NTLDR bootloader.
 
  Also note that while my fdisk and disklabel indicates Linux
  partitions, none of them have yet been installed.  I installed
  Windows 2000 first, then OpenBSD.  Since I could never get OpenBSD
  to boot, I have not yet installed Linux.
 
  Please help if you can.
 
  Thank you,
  Kenneth J. Hendrickson
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of dmesg]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of fdisk]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of disklabel]
 
  [demime 1.01d removed an attachment of type application/octet-stream which
 had a name of OpenBSD.PDR]