Re: Booting problem of my OpenBSD 5.7 road warrior

2015-08-23 Thread Stefan Sperling
On Sun, Aug 23, 2015 at 03:06:40PM +0800, Zhi-Qiang Lei wrote:
> My road warrior has a PPPoE external connection and a tunnel connection,
> established with OpenVPN, which would encrypt the packets from some special
> devices.
> 
> It works so well so far with the help with these rules in /etc/pf.conf:
> 
> pass in quick on $int_if from $arch to ! route-to $tun_if
> pass in quick on $int_if from $raspbmc to  route-to
> $tun_if
> pass out quick on $tun_if from any to any nat-to ($tun_if)
> 
> However, every time when I reboot the machine, pf fails to load the rules
> because the tunnel is not ready. The tunnel generally would take some minutes
> to establish. Is it possible to defer the loading of pf rules until all
> interfaces are ready? I also tried to parenthesize $tun_if, but it failed due
> to syntax errors.
> 
> pass in quick on $int_if from $arch to ! route-to
> ($tun_if)
> pass in quick on $int_if from $raspbmc to  route-to
> ($tun_if)
> pass out quick on $tun_if from any to any nat-to ($tun_if)
> 
> Best regards and thanks,
> Zhi-Qiang Lei

If your local tun_if IP is static, you can set it in /etc/hostname.tun0
and then use persist-local-ip in openvpn's config file. That will allow
your pf rules to load on boot. OpenVPN will use the existing local IP.

If your local tun_if IP is dynamic, you could put an anchor in your
pf rule set:
  anchor "openvpn/*"
and then add rules to this anchor when openvpn comes up (e.g. from openvpn's
up script):
  printf 'pass in quick on $int_if from $arch to ! route-to 
$tun_if\npass in quick on $int_if from $raspbmc to  
route-to\n$tun_if\npass out quick on $tun_if from any to any nat-to 
($tun_if)\n' | pfctl -a openvpn/up -f -

Note the use of single quotes to prevent the shell from expanding $int_if etc.



Booting problem of my OpenBSD 5.7 road warrior

2015-08-23 Thread Zhi-Qiang Lei
My road warrior has a PPPoE external connection and a tunnel connection,
established with OpenVPN, which would encrypt the packets from some special
devices.

It works so well so far with the help with these rules in /etc/pf.conf:

pass in quick on $int_if from $arch to ! route-to $tun_if
pass in quick on $int_if from $raspbmc to  route-to
$tun_if
pass out quick on $tun_if from any to any nat-to ($tun_if)

However, every time when I reboot the machine, pf fails to load the rules
because the tunnel is not ready. The tunnel generally would take some minutes
to establish. Is it possible to defer the loading of pf rules until all
interfaces are ready? I also tried to parenthesize $tun_if, but it failed due
to syntax errors.

pass in quick on $int_if from $arch to ! route-to
($tun_if)
pass in quick on $int_if from $raspbmc to  route-to
($tun_if)
pass out quick on $tun_if from any to any nat-to ($tun_if)

Best regards and thanks,
Zhi-Qiang Lei



Re: Another weird notebook-booting problem.

2011-06-21 Thread Stuart Henderson
On 2011-06-21, Sean Howard  wrote:
> I am also using a ProBook 4520s
> I am however using OpenBSD-4.9 amd-64.
>
> I could try to see if I can install -current, but it would take me a few days 
> (find time, backup again, reinstall, etc), however - I have attached my amd64 
> dmesg.
>
> I had to disable ACPI to get it to work,

This is really not a good idea, especially on a particularly
temperature-sensitive system like a laptop.

> since, well, that would cause a kernel panic.

I don't see a bug report for this anywhere.

It would certainly be worth copying a -current kernel over
to see if it boots and make a bug report if the ACPI problem
persists, no need to overwrite your current kernel, just
use a different name instead of /bsd.



Re: Another weird notebook-booting problem.

2011-06-20 Thread Sean Howard
I am also using a ProBook 4520s
I am however using OpenBSD-4.9 amd-64.

I could try to see if I can install -current, but it would take me a few days 
(find time, backup again, reinstall, etc), however - I have attached my amd64 
dmesg.

I had to disable ACPI to get it to work, since, well, that would cause a kernel 
panic.

--Sean

Somebody claiming to be Dave Anderson wrote:
> I've encountered a notebook (labelled hp ProBook 4520s) which, when
> booted from the i386 snapshot dated 24 May 2011 immediately reboots --
> it very briefly shows about one line of the usual booting messages, then
> goes back to the bios boot screen.
> 
> Given the limited access I have to this store demo system, how can I
> gather enough information so that someone can look into this?
> 
>   Dave
> 
> -- 
> Dave Anderson
> 
OpenBSD 4.9 (GENERIC.MP) #819: Wed Mar  2 06:57:49 MST 2011
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error a5
real mem = 1995239424 (1902MB)
avail mem = 1928101888 (1838MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x77348000 (24 entries)
bios0: vendor Hewlett-Packard version "68AZZ Ver. F.07" date 06/08/2010
bios0: Hewlett-Packard HP ProBook 4520s
acpi at bios0 not configured
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Core(TM) i3 CPU M 350 @ 2.27GHz, 2261.39 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG
cpu0: 256KB 64b/line 8-way L2 cache
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core Host" rev 0x12
vga1 at pci0 dev 2 function 0 "Intel Mobile HD graphics" rev 0x12
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0x8000, size 0x1000
inteldrm0 at vga1: irq 10
drm0 at inteldrm0
"Intel 3400 MEI" rev 0x06 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 "Intel 3400 USB" rev 0x06: irq 10
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 3400 HD Audio" rev 0x06: irq 5
azalia0: codecs: IDT 92HD81B1X, Intel/0x2804, using IDT 92HD81B1X
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 3400 PCIE" rev 0x06: irq 5
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 "Intel 3400 PCIE" rev 0x06: irq 10
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 3 "Intel 3400 PCIE" rev 0x06: irq 10
pci3 at ppb2 bus 67
athn0 at pci3 dev 0 function 0 "Atheros AR9285" rev 0x01: irq 10
athn0: AR9285 rev 2 (1T1R), ROM rev 14, address 70:f1:a1:a8:24:14
ppb3 at pci0 dev 28 function 5 "Intel 3400 PCIE" rev 0x06: irq 10
pci4 at ppb3 bus 68
re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x03: RTL8168D/8111D (0x2800), 
irq 5, address 78:e7:d1:dc:f2:c2
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
ehci1 at pci0 dev 29 function 0 "Intel 3400 USB" rev 0x06: irq 10
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xa6
pci5 at ppb4 bus 69
pcib0 at pci0 dev 31 function 0 "Intel HM57 LPC" rev 0x06
ahci0 at pci0 dev 31 function 2 "Intel 3400 AHCI" rev 0x06: irq 11, AHCI 1.3
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 238475MB, 512 bytes/sec, 488397168 sec total
cd0 at scsibus0 targ 1 lun 0:  ATAPI 5/cdrom 
removable
itherm0 at pci0 dev 31 function 6 "Intel 3400 Thermal" rev 0x06
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
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
mtrr: Pentium Pro MTRR support
uhub2 at uhub0 port 1 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
ugen0 at uhub2 port 3 "vendor 0x138a product 0x0007" rev 1.10/0.72 addr 3
uvideo0 at uhub2 port 5 configuration 1 interface 0 "Primax Electronics Ltd. 
Villem" rev 2.00/0.04 addr 4
video0 at uvideo0
uhub3 at uhub1 port 1 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
root on sd0a swap on sd0b dump on sd0b



Another weird notebook-booting problem.

2011-06-20 Thread Dave Anderson
I've encountered a notebook (labelled hp ProBook 4520s) which, when
booted from the i386 snapshot dated 24 May 2011 immediately reboots --
it very briefly shows about one line of the usual booting messages, then
goes back to the bios boot screen.

Given the limited access I have to this store demo system, how can I
gather enough information so that someone can look into this?

Dave

-- 
Dave Anderson




Re: Booting problem

2009-10-18 Thread Anatoly V. Beregovoy
On 21:53 Fri 25 Sep , Stuart Henderson wrote:
> On 2009-09-25, Anatoly V. Beregovoy  wrote:
> >>
> >> Do not treat me as an expert but I suggest you to try to enable ACPI in
> >> UKC ("boot -c").
> >>
> > Thak you for advice. I played with disable / enable command. I tried to
> > diable /enable ACPI, vga0, vga1, and some other devices, but nothing
> > helped. BTW, ACPI is enabled automatically.
> 
> ACPI is enabled by default, but under some conditions (certain
> SMBIOS versions with single cpu) APM takes priority and knocks it
> out. You can try "disable apm" to force acpi to be used, I don't
> know if it's likely to help though.
> 

I solved my problem. It was simple. I have Bus Clock frequency jumpers
on momboard wrong configured. Sorry for disturbing.



Re: Booting problem

2009-09-26 Thread Anatoly V. Beregovoy
On 21:53 Fri 25 Sep , Stuart Henderson wrote:
> On 2009-09-25, Anatoly V. Beregovoy  wrote:
> >>
> >> Do not treat me as an expert but I suggest you to try to enable ACPI in
> >> UKC ("boot -c").
> >>
> > Thak you for advice. I played with disable / enable command. I tried to
> > diable /enable ACPI, vga0, vga1, and some other devices, but nothing
> > helped. BTW, ACPI is enabled automatically.
> 
> ACPI is enabled by default, but under some conditions (certain
> SMBIOS versions with single cpu) APM takes priority and knocks it
> out. You can try "disable apm" to force acpi to be used, I don't
> know if it's likely to help though.
> 

I tried to disable apm and both apm and acpi. It didn't help.
I think my problem is because of my hardware bug :(



Re: Booting problem

2009-09-25 Thread Stuart Henderson
On 2009-09-25, Anatoly V. Beregovoy  wrote:
>>
>> Do not treat me as an expert but I suggest you to try to enable ACPI in
>> UKC ("boot -c").
>>
> Thak you for advice. I played with disable / enable command. I tried to
> diable /enable ACPI, vga0, vga1, and some other devices, but nothing
> helped. BTW, ACPI is enabled automatically.

ACPI is enabled by default, but under some conditions (certain
SMBIOS versions with single cpu) APM takes priority and knocks it
out. You can try "disable apm" to force acpi to be used, I don't
know if it's likely to help though.



Re: Booting problem

2009-09-25 Thread Anatoly V. Beregovoy
On 11:03 Fri 25 Sep , Bryan Irvine wrote:
> Out of curiosity, can you SSH into the box after waiting a few minutes?
> 
> -B
> 

Of course no. It can't even mount filesystems, and therefore can't start
/etc/netstart. I checked it. The system just freezes after showindg
"root on wd0a swap on wd0b dump on wd0b" kernel message.



Re: Booting problem

2009-09-25 Thread Bryan Irvine
Out of curiosity, can you SSH into the box after waiting a few minutes?

-B



On Fri, Sep 25, 2009 at 10:17 AM, Anatoly V. Beregovoy
 wrote:
>> > Hi all!
>> > First of all, I'm sorry about my English.
>> > I have a problem with booting OpenBSD 4.5 on my computer. It has
>> > internal and external video adapters. With only internal one the
>> > system boots without any problem. dmesg output (using only internal
>> > card) is attached to the message. When I plug an external video card
>> > OpenBSD refuses to boot. It doesn't matter what a video adapter I use
>> > (I tried with three cards). The system stops booting with the
>> > following:
>> > ...
>> > ...
>> > pckbd0 at pckbc0 (kbd slot)
>> > pckbc0: using irq 1 for kbd slot
>> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
>> > pmsi0 at pckbc0 (aux slot)
>> > pckbc0: using irq 12 for aux slot
>> > wsmouse0 at pmsi0 mux 0
>> > pcppi0 at isa0 port 0x61
>> > midi0 at pcppi0: 
>> > spkr0 at pcppi0
>> > lpt0 at isa0 port 0x378/4 irq 7
>> > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x17
>> > lm1 at wbsio0 port 0x290/8: W83627HF
>> > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
>> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
>> > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
>> > usb0 at uhci0: USB revision 1.0
>> > uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> > usb1 at uhci1: USB revision 1.0
>> > uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> > biomask ef65 netmask ef65 ttymask 
>> > mtrr: Pentium Pro MTRR support
>> > softraid0 at root
>> > root on wd0a swap on wd0b dump on wd0b
>> >
>> > Keyboard isn't working after that - the system is froze.
>> >
>> > OpenBSD is the only system on PC. Windows (r) works fine on this
>> > computer. I need to use an external adapter.
>> >
>> > What have I tried? I've tried to boot with turned on or off following
>> > options in BIOS (I tried various combinations):
>> >  - Assign IRQ to VGA;
>> >  - Video BIOS cacheable;
>> >  - Enable Internal Video;
>> >  - AGP Data Transfer Rate;
>> >  - Init Display First;
>> >  - PCI/VGA Palette Snoop.
>> > Also I tried to boot with minimal hardware (only M/B, cpu, memory,
>> > HDD, video card). I looked boot(1) but found nothing useful.
>> >
>> > My hardware:
>> > Motherboard Abit SL30 with the newest BIOS update, CPU Pentium 3 733,
>> > 128Mb RAM. I'm sure that the hardware is good. It works fine.
>> >
>> > Thank you!
>> > OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
>> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>> > cpu0: Intel Pentium III ("GenuineIntel" 686-class) 549 MHz
>> > cpu0:
>> > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3
>> >6,MMX,FXSR,SSE real mem  = 132673536 (126MB)
>> > avail mem = 119992320 (114MB)
>> > mainbus0 at root
>> > bios0 at mainbus0: AT/286+ BIOS, date 04/02/02, BIOS32 rev. 0 @
>> > 0xfb0d0, SMBIOS rev. 2.2 @ 0xf0800 (35 entries) bios0: vendor Award
>> > Software International, Inc. version "6.00 PG" date 04/02/2002 bios0:
>> > ABIT i815E-W83627HF
>> > apm0 at bios0: Power Management spec V1.2 (slowidle)
>> > apm0: AC on, battery charge unknown
>> > acpi at bios0 function 0x0 not configured
>>
>> Do not treat me as an expert but I suggest you to try to enable ACPI in
>> UKC ("boot -c").
>>
>> --
>>   Best wishes,
>> Vadim Zhukov
>>
> Thak you for advice. I played with disable / enable command. I tried to
> diable /enable ACPI, vga0, vga1, and some other devices, but nothing
> helped. BTW, ACPI is enabled automatically.



Re: Booting problem

2009-09-25 Thread Anatoly V. Beregovoy
> > Hi all!
> > First of all, I'm sorry about my English.
> > I have a problem with booting OpenBSD 4.5 on my computer. It has
> > internal and external video adapters. With only internal one the
> > system boots without any problem. dmesg output (using only internal
> > card) is attached to the message. When I plug an external video card
> > OpenBSD refuses to boot. It doesn't matter what a video adapter I use
> > (I tried with three cards). The system stops booting with the
> > following:
> > ...
> > ...
> > pckbd0 at pckbc0 (kbd slot)
> > pckbc0: using irq 1 for kbd slot
> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
> > pmsi0 at pckbc0 (aux slot)
> > pckbc0: using irq 12 for aux slot
> > wsmouse0 at pmsi0 mux 0
> > pcppi0 at isa0 port 0x61
> > midi0 at pcppi0: 
> > spkr0 at pcppi0
> > lpt0 at isa0 port 0x378/4 irq 7
> > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x17
> > lm1 at wbsio0 port 0x290/8: W83627HF
> > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> > usb0 at uhci0: USB revision 1.0
> > uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> > usb1 at uhci1: USB revision 1.0
> > uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> > biomask ef65 netmask ef65 ttymask 
> > mtrr: Pentium Pro MTRR support
> > softraid0 at root
> > root on wd0a swap on wd0b dump on wd0b
> >
> > Keyboard isn't working after that - the system is froze.
> >
> > OpenBSD is the only system on PC. Windows (r) works fine on this
> > computer. I need to use an external adapter.
> >
> > What have I tried? I've tried to boot with turned on or off following
> > options in BIOS (I tried various combinations):
> >  - Assign IRQ to VGA;
> >  - Video BIOS cacheable;
> >  - Enable Internal Video;
> >  - AGP Data Transfer Rate;
> >  - Init Display First;
> >  - PCI/VGA Palette Snoop.
> > Also I tried to boot with minimal hardware (only M/B, cpu, memory,
> > HDD, video card). I looked boot(1) but found nothing useful.
> >
> > My hardware:
> > Motherboard Abit SL30 with the newest BIOS update, CPU Pentium 3 733,
> > 128Mb RAM. I'm sure that the hardware is good. It works fine.
> >
> > Thank you!
> > OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: Intel Pentium III ("GenuineIntel" 686-class) 549 MHz
> > cpu0:
> > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3
> >6,MMX,FXSR,SSE real mem  = 132673536 (126MB)
> > avail mem = 119992320 (114MB)
> > mainbus0 at root
> > bios0 at mainbus0: AT/286+ BIOS, date 04/02/02, BIOS32 rev. 0 @
> > 0xfb0d0, SMBIOS rev. 2.2 @ 0xf0800 (35 entries) bios0: vendor Award
> > Software International, Inc. version "6.00 PG" date 04/02/2002 bios0:
> > ABIT i815E-W83627HF
> > apm0 at bios0: Power Management spec V1.2 (slowidle)
> > apm0: AC on, battery charge unknown
> > acpi at bios0 function 0x0 not configured
> 
> Do not treat me as an expert but I suggest you to try to enable ACPI in 
> UKC ("boot -c").
> 
> -- 
>   Best wishes,
> Vadim Zhukov
> 
Thak you for advice. I played with disable / enable command. I tried to
diable /enable ACPI, vga0, vga1, and some other devices, but nothing
helped. BTW, ACPI is enabled automatically.



Re: Booting problem

2009-09-20 Thread Vadim Zhukov
On 19 September 2009 c. 18:57:26 Anatoly V. Beregovoy wrote:
> Hi all!
> First of all, I'm sorry about my English.
> I have a problem with booting OpenBSD 4.5 on my computer. It has
> internal and external video adapters. With only internal one the
> system boots without any problem. dmesg output (using only internal
> card) is attached to the message. When I plug an external video card
> OpenBSD refuses to boot. It doesn't matter what a video adapter I use
> (I tried with three cards). The system stops booting with the
> following:
> ...
> ...
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pmsi0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pmsi0 mux 0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: 
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x17
> lm1 at wbsio0 port 0x290/8: W83627HF
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb1 at uhci1: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> biomask ef65 netmask ef65 ttymask 
> mtrr: Pentium Pro MTRR support
> softraid0 at root
> root on wd0a swap on wd0b dump on wd0b
>
> Keyboard isn't working after that - the system is froze.
>
> OpenBSD is the only system on PC. Windows (r) works fine on this
> computer. I need to use an external adapter.
>
> What have I tried? I've tried to boot with turned on or off following
> options in BIOS (I tried various combinations):
>  - Assign IRQ to VGA;
>  - Video BIOS cacheable;
>  - Enable Internal Video;
>  - AGP Data Transfer Rate;
>  - Init Display First;
>  - PCI/VGA Palette Snoop.
> Also I tried to boot with minimal hardware (only M/B, cpu, memory,
> HDD, video card). I looked boot(1) but found nothing useful.
>
> My hardware:
> Motherboard Abit SL30 with the newest BIOS update, CPU Pentium 3 733,
> 128Mb RAM. I'm sure that the hardware is good. It works fine.
>
> Thank you!
> OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium III ("GenuineIntel" 686-class) 549 MHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3
>6,MMX,FXSR,SSE real mem  = 132673536 (126MB)
> avail mem = 119992320 (114MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 04/02/02, BIOS32 rev. 0 @
> 0xfb0d0, SMBIOS rev. 2.2 @ 0xf0800 (35 entries) bios0: vendor Award
> Software International, Inc. version "6.00 PG" date 04/02/2002 bios0:
> ABIT i815E-W83627HF
> apm0 at bios0: Power Management spec V1.2 (slowidle)
> apm0: AC on, battery charge unknown
> acpi at bios0 function 0x0 not configured

Do not treat me as an expert but I suggest you to try to enable ACPI in
UKC ("boot -c").

--
  Best wishes,
Vadim Zhukov

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?



Booting problem

2009-09-19 Thread Anatoly V. Beregovoy
Hi all!
First of all, I'm sorry about my English.
I have a problem with booting OpenBSD 4.5 on my computer. It has internal
and external video adapters. With only internal one the system boots
without any problem. dmesg output (using only internal card) is attached
to the message. When I plug an external video card OpenBSD refuses to
boot. It doesn't matter what a video adapter I use (I tried with three
cards). The system stops booting with the following:
...
...
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: 
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x17
lm1 at wbsio0 port 0x290/8: W83627HF
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec 
usb0 at uhci0: USB revision 1.0 
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb1 at uhci1: USB revision 1.0 
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
biomask ef65 netmask ef65 ttymask 
mtrr: Pentium Pro MTRR support
softraid0 at root
root on wd0a swap on wd0b dump on wd0b

Keyboard isn't working after that - the system is froze.

OpenBSD is the only system on PC. Windows (r) works fine on this
computer. I need to use an external adapter.

What have I tried? I've tried to boot with turned on or off following
options in BIOS (I tried various combinations):
 - Assign IRQ to VGA;
 - Video BIOS cacheable;
 - Enable Internal Video;
 - AGP Data Transfer Rate;
 - Init Display First;
 - PCI/VGA Palette Snoop.
Also I tried to boot with minimal hardware (only M/B, cpu, memory, HDD,
video card). I looked boot(1) but found nothing useful.

My hardware:
Motherboard Abit SL30 with the newest BIOS update, CPU Pentium 3 733,
128Mb RAM. I'm sure that the hardware is good. It works fine.

Thank you!
OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 549 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 132673536 (126MB)
avail mem = 119992320 (114MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 04/02/02, BIOS32 rev. 0 @ 0xfb0d0, SMBIOS 
rev. 2.2 @ 0xf0800 (35 entries)
bios0: vendor Award Software International, Inc. version "6.00 PG" date 
04/02/2002
bios0: ABIT i815E-W83627HF
apm0 at bios0: Power Management spec V1.2 (slowidle)
apm0: AC on, battery charge unknown
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdef0/128 (6 entries)
pcibios0: PCI Exclusive IRQs: 5 9 11
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371SB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xa000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82815 Host" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82815 Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, size 0x400
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x02
pci1 at ppb0 bus 1
skc0 at pci1 dev 0 function 0 "D-Link Systems DGE-530T B1" rev 0x11, Yukon Lite 
(0x9): irq 11
sk0 at skc0 port A: address 00:15:e9:41:4d:04
eephy0 at sk0 phy 0: 88E1011 Gigabit PHY, rev. 5
rl0 at pci1 dev 1 function 0 "D-Link Systems 530TX+" rev 0x10: irq 5, address 
00:50:ba:4c:82:f9
rlphy0 at rl0 phy 0: RTL internal PHY
"Philips SAA7133 TV" rev 0xd1 at pci1 dev 2 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801BA LPC" rev 0x02: 24-bit timer 
at 3579545Hz
pciide0 at pci0 dev 31 function 1 "Intel 82801BA IDE" rev 0x02: 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
wd1 at pciide0 channel 1 drive 0: 
wd1: 16-sector PIO, LBA48, 476940MB, 976773168 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 4
uhci0 at pci0 dev 31 function 2 "Intel 82801BA USB" rev 0x02: irq 11
ichiic0 at pci0 dev 31 function 3 "Intel 82801BA SMBus" rev 0x02: irq 5
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 64MB SDRAM non-parity PC100CL3
spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
uhci1 at pci0 dev 31 function 4 "Intel 82801BA USB" rev 0x02: irq 11
auich0 at pci0 dev 31 function 5 "Intel 82801BA AC97" rev 0x02: irq

Re: Soekris net5501 OpenBSD 4.5 Booting Problem

2009-07-22 Thread Theo de Raadt
> I cannot get a Soekris net5501 to boot OpenBSD 4.5 from a hard drive.
> 
> Much traffic has passed on the Soekris email list.  I've now included
> misc@OpenBSD.org, because it might be an OpenBSD problem.
> 
> I re-installed OpenBSD.  And I noticed a problem at the end of the
> install process.  I have a "broken MBR".  This is probably why my
> Soekris net5501 won't boot from hard drive.
> 
> - start of transcript -
> Installing boot block...
> 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 11048
> installboot: broken MBR
> done.
> - end of transcript -
> 
> Notice that I have a broken MBR.  This is bad.  I've never seen this
> happen before.
> 
> Here is my partitioning and slicing information:
> - start of transcript -
> # fdisk wd0
> Disk: wd0   geometry: 12161/255/63 [195371568 Sectors]
> Offset: 0   Signature: 0x0

  ^^

That is not a valid MBR.  Use fdisk to fix this.  It is now required
that the MBR has a correct signature.  If the signature is not 0xAA55,
it is not a MBR partition.



Re: [Soekris] Soekris net5501 OpenBSD 4.5 Booting Problem

2009-07-17 Thread Bill Maas
Hi Ken,

On Fri, 2009-07-17 at 09:09 -0400, Hendrickson, Kenneth wrote:
> > > *0: A6  0   1   1 -131 127  63 [  63: 2112516 ] 
> > > OpenBSD 
> > >  1: DA131 128   1 -262 254  63 [ 2112579: 2112516 ] 
> > > 
> > >  2: DA263   0   1 -   6211 254  63 [ 4225095:95570685 ] 
> > > 
> > >  3: DA   6212   0   1 -  12160 254  63 [99795780:95570685 ] 
> > > 
> > 
> > Just follow the instructions in the OpenBSD installer, offered by
> > default. When it prompts you 'Do you want to use all of wd0 for OpenBSD',
> > just say yes, it will run fdisk -i
> > 
> > It will make partition 3 the default active bootable one
> 
> But I *never* want to use the entire disk for OpenBSD.  I have a system for
> quick recovery in case of a disaster.  I only use half of the disk.  When I
> install a new version of OpenBSD, I use the other half of the disk.  That way,
> if a disaster happens, I can quickly boot, run fdisk -- changing the bootable
> partition, and then reboot into my previous system.
> 
> In the above fdisk output, partitions 0 and 2 are my current system, while
> partitions 1 and 3 are my last and next systems.  After I install a new system
> onto partitions 1 and 3, partitions 0 and 2 will become my last and next
> systems.
> 
> (Using 2 partitions like this is a holdover from the days when the bootable
> partition had to be in the first few cylinders of the drive.)

>From Absolute OpenBSD - UNIX for the practical paranoid by Michael Lucas
I've learned that:

"OpenBSD partitions need to go within a single MBR partition. Dedicate a
single MBR partition ... There can only be one OpenBSD MBR partition per
hard disk."

I can't make much sense of what you describe here, but to me it looks
like it suggests that you're using a single disklabel which spans more
than one MBR partition. Or even moving around the disklabel at will. If
so, would you be willing to publish something like a howto on this
subject?. Or else tell us where to find one? I know about multiple
OpenBSD installations inside a single set of subpartitions, but that's
still a single MBR partition. No fdisk or disklabel involved after
initial setup, but probably more vulnerable than what you describe here.

Bill 

> I'm surprised more people don't do this.  It provides for very quick and easy
> recovery in the case of a disaster.  (I've only ever had such a disaster once;
> I've been using OpenBSD since late 1996.)
> 
> The other advantage of this system is that it provides an easy means for
> seeing how I did things previously.  I can quickly run disklabel, use an
> empty slice to point to one of my old slices, and then mount it.  After I'm
> done I can run disklabel again and put it back.
> 
> So I never want to use the entire disk for OpenBSD.  Therefore, I will need
> to remember to escape to a shell and run "fdisk -u" when installing to a
> virgin disk.
> 
> It would be nice if the OpenBSD install procedure checked for the lack of
> a valid MBR, and installed one automatically (after asking); that would
> save some people from experiencing the problem I experienced.
> 
> Ken Hendrickson
> ___
> Soekris-tech mailing list
> soekris-t...@lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech



Re: Soekris net5501 OpenBSD 4.5 Booting Problem

2009-07-17 Thread Hendrickson, Kenneth
> > *0: A6  0   1   1 -131 127  63 [  63: 2112516 ]
OpenBSD
> >  1: DA131 128   1 -262 254  63 [ 2112579: 2112516 ]

> >  2: DA263   0   1 -   6211 254  63 [ 4225095:95570685 ]

> >  3: DA   6212   0   1 -  12160 254  63 [99795780:95570685 ]

>
> Just follow the instructions in the OpenBSD installer, offered by
> default. When it prompts you 'Do you want to use all of wd0 for OpenBSD',
> just say yes, it will run fdisk -i
>
> It will make partition 3 the default active bootable one

But I *never* want to use the entire disk for OpenBSD.  I have a system for
quick recovery in case of a disaster.  I only use half of the disk.  When I
install a new version of OpenBSD, I use the other half of the disk.  That
way,
if a disaster happens, I can quickly boot, run fdisk -- changing the bootable
partition, and then reboot into my previous system.

In the above fdisk output, partitions 0 and 2 are my current system, while
partitions 1 and 3 are my last and next systems.  After I install a new
system
onto partitions 1 and 3, partitions 0 and 2 will become my last and next
systems.

(Using 2 partitions like this is a holdover from the days when the bootable
partition had to be in the first few cylinders of the drive.)

I'm surprised more people don't do this.  It provides for very quick and easy
recovery in the case of a disaster.  (I've only ever had such a disaster
once;
I've been using OpenBSD since late 1996.)

The other advantage of this system is that it provides an easy means for
seeing how I did things previously.  I can quickly run disklabel, use an
empty slice to point to one of my old slices, and then mount it.  After I'm
done I can run disklabel again and put it back.

So I never want to use the entire disk for OpenBSD.  Therefore, I will need
to remember to escape to a shell and run "fdisk -u" when installing to a
virgin disk.

It would be nice if the OpenBSD install procedure checked for the lack of
a valid MBR, and installed one automatically (after asking); that would
save some people from experiencing the problem I experienced.

Ken Hendrickson



Re: SOLVED: Soekris net5501 OpenBSD 4.5 Booting Problem

2009-07-16 Thread Hendrickson, Kenneth
Problem solved!  My Soekris net5501 is now booting from hard drive.

The solution is here:
http://archives.neohapsis.com/archives/openbsd/2004-05/2036.html

Thanks for everybody's help,
Ken Hendrickson

PS  Note to OpenBSD: I've never installed to a virgin disk before.
I didn't know that I had to do fdisk -u wd0 to write a master boot
record.  I would like to suggest that the install process should
check for the lack of a MBR, and if no MBR is found, prompt the
installer to write one.  If such code existed in the install process,
I would not have had the problem I just had over the last week.



Re: Soekris net5501 OpenBSD 4.5 Booting Problem

2009-07-16 Thread Hendrickson, Kenneth
I cannot get a Soekris net5501 to boot OpenBSD 4.5 from a hard drive.

Much traffic has passed on the Soekris email list.  I've now included
misc@OpenBSD.org, because it might be an OpenBSD problem.

I re-installed OpenBSD.  And I noticed a problem at the end of the
install process.  I have a "broken MBR".  This is probably why my
Soekris net5501 won't boot from hard drive.

- start of transcript -
Installing boot block...
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 11048
installboot: broken MBR
done.
- end of transcript -

Notice that I have a broken MBR.  This is bad.  I've never seen this
happen before.

Here is my partitioning and slicing information:
- start of transcript -
# fdisk wd0
Disk: wd0   geometry: 12161/255/63 [195371568 Sectors]
Offset: 0   Signature: 0x0
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
-
--
*0: A6  0   1   1 -131 127  63 [  63: 2112516 ] OpenBSD
 1: DA131 128   1 -262 254  63 [ 2112579: 2112516 ] 
 2: DA263   0   1 -   6211 254  63 [ 4225095:95570685 ] 
 3: DA   6212   0   1 -  12160 254  63 [99795780:95570685 ] 
# disklabel wd0
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: FUJITSU MHW2100B
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 12161
total sectors: 195371568
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  a:  2112516   63  4.2BSD   2048 163841
  b:  1076355  4225095swap
  c:1953715680  unused
  d:  2112516  5301450  4.2BSD   2048 163841
  e:  4201029  7413966  4.2BSD   2048 163841
  f:  4209030 11614995  4.2BSD   2048 163841
  g:  4209030 15824025  4.2BSD   2048 163841
  h:  4209030 20033055  4.2BSD   2048 163841
  i:  2112516  2112579 unknown
  j:  2104515 28451115  4.2BSD   2048 163841
  k: 95570685 99795780 unknown
  l:  2104515 24242085  4.2BSD   2048 163841
  m:  2104515 26346600  4.2BSD   2048 163841
  n: 50347710 30555630  4.2BSD   2048 163841
  o: 16787925 80903340  4.2BSD   2048 163841
  p:  2104515 97691265  4.2BSD   2048 163841
# mount -t ffs /dev/wd0a /mnt
# cat /mnt/etc/fstab
/dev/wd0a / ffs rw 1 1
/dev/wd0d /altroot ffs rw,nodev,nosuid 1 2
/dev/wd0j /root ffs rw,nodev,nosuid 1 2
/dev/wd0e /tmp ffs rw,nodev,nosuid 1 2
/dev/wd0n /usr ffs rw,nodev 1 2
/dev/wd0p /usr/local/src ffs rw,nodev 1 2
/dev/wd0o /usr/obj ffs rw,nodev,nosuid 1 2
/dev/wd0f /var ffs rw,nodev,nosuid 1 2
/dev/wd0h /var/crash ffs rw,nodev,nosuid 1 2
/dev/wd0l /var/log ffs rw,nodev,nosuid 1 2
/dev/wd0m /var/mail ffs rw,nodev,nosuid 1 2
/dev/wd0g /var/tmp ffs rw,nodev,nosuid 1 2
# umount /mnt
- end of transcript -

What do I need to do to fix this problem?  I realize this is as much an
OpenBSD problem (or more so) as it is a Soekris net5501 problem.

Is there a problem with my disk partitioning?

Is there a problem with my OpenBSD partition disk slicing?

I can provide a full transcript of the install if it will help.

Thanks In Advance,
Ken Hendrickson



Booting problem, trace and ps output included this time

2008-06-22 Thread annne annnie
Ok, I had windows installed then I installed openbsd, leaving the windows
partition active.B  I used bootpart to add openbsd to boot.ini in windows.B  I
had never booted into openbsd until after using bootpart, but when I did it
messes up I guess.B  Alright so its running and all the hardware stuff is
going across the screen with a blue background.B  Then it says:
RUN AT LEAST trace AND ps AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!B  DO
NOT EVEN BOTHER REPORTING WITHOUT INCLUDING THIS!
so I run trace, then ps.B  Sorry I don't have actually images of the output,
but I tried writing it down and taking pictures as
 suggested.B  Here are the
 outputs.

Debugger( ) at Debugger+0x5
panic( ) at panic+0x12a
_ _assert( ) at _ _assert+0x21
ahci_port_intr( ) at ahci_port_intr+0x218
ahci_poll( ) at ahci_poll+0x4d
ahci_ata_cmd( ) at ahci_ata_cmd+0x9f
ata_exec( ) at ata_exec+0x19
scsi_execute_xs( ) at scsi_execute_xs+0x6d
scsi_scsi_cmd( ) at scsi_scsi_cmd+0xcb
scsi_test_unit_ready( ) at scsi_test_unit_ready+0x4d
scsi _probedev( ) at scsi_probedev+0x28a
scsi_probe_target( ) at scsi_probe_target+0x26
scsi_probe_bus( ) at scsi_probe_bus+0x38
config_attach( ) at config_attach+011b
atascsi_attach( ) at atascsi_attach+0xf8
ahci_pci_attach( ) at ahci_pci_attach+0x178
config_attach( ) at config_attach+0x11b
pci_probe_device( ) at pci_probe_device+0x20e
pci_enumerate_bus( ) at pci_enumerate_bus+0x104
config_attach( ) at config_attach+0x11b
mainbus_attach( ) at mainbus_attach+0x14b
config_attach( ) at config_at
 config_attach+0x11b
cpu_configure( ) at cpu_configure+0x1c
main( ) at main+0x3b2
end trace frame: 0x0, count: -24
ddb>
debugger( ) at Debugger+0x5
end trace frame: 0x80c18860, count: 0
ddb> ps
B B B B B  PIDB B B B B B  PPIDB B B B B  PGRPB B B B B B B  UIDB B B 
SB B B B B B B B B B B B B B B B  FLAGSB B  WAITB B B B B B B B B B B B B 
COMMAND
*B B B B B B B  0B B B B B B B B B B  -1B B B B B B B B B B B B B B 
0B B B B B B B B B B  0B B B 
 7B B B B B B B B B B B B B B B 
0X80200B B B B B B B B B B B B B B B B B B B B B B B B B  swapper




That's it.B  It would be an incredible pain to provide you with a dmesg (did I
word that right?) without using a serial console.B  Also, if I knew how to use
a serial console, I wouldn't know how to edit the correct files from my
position.B  It will just sit there waiting for me to type commands at ddb>
So what's wrong and what am I sitting at?B 



  __
Sent from
Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html



Re: booting problem

2007-05-14 Thread Andrey Shuvikov

On 5/12/07, alicornio <[EMAIL PROTECTED]> wrote:

Hi guys

Problems with my webmail. I'm sorry.

>> Hi all
>>
>> I can't boot my system after the instalation. My OS can't be finded.
>> I follow the faq (4.12.2 - My i386 won't boot after install) and nothing
>> change. But I can boot with CD typing "b hd0a:\bsd".
>>
>> When I tried install again I saw a warning in disklabel stage:
>>
>> WARNING: inode blocks/cyl group (155) >= data blocks (5) in last
>> cylinder group. This implies 188 sector(s) cannot be allocated.
>>
>> What's happening?
>> How I can solve this problem?
>>
>> thx all
>>
>> Thiago
>>
>>
>If you post at least output of "fdisk wd0" and "disklabel wd0" commands...

My disk: [WIN(ntfs)][DATA(ntfs)][OpenBSD]

1- Booting from frist partition (my webmail can't print
 lines with '*' in the begin)
2- I jump 1 cylinder between partition 1 and 2.

#fdisk -e wd0
Enter 'help' for information
fdisk: 1> p m
Disk: wd0 geometry: 9729/255/63 [76317 Megabytes]
Offset: 0 Signature: 0xAA55
 Starting Ending LBA Info:
 #: id C H S - C H S [ start: size ]
-
 0: 070   1   1 - 2549 254 63 [   63: 20003M]HPFS/QNX/AUX
 1: 07 2550 0 1 - 7649 254 63 [ 40965750: 40006M] HPFS/QNX/AUX
 2: A6 7651 0 1 - 9728 254 63 [ 122913315: 16300M] OpenBSD
 3: 00 0 0 0 - 0 0 0 [ 0: 0M] unused
fdisk: 1>

+++

fdisk: 1> p
Disk: wd0 geometry: 9729/255/63 [156296385 Sectors]
Offset: 0 Signature: 0xAA55
 Starting Ending LBA Info:
 #: id C H S - C H S [ start: size ]
-
 0: 070   1   1 - 2549 254 63 [ 63:   40965687] HPFS/QNX/AUX
 1: 07 2550 0 1 - 7649 254 63 [ 40965750: 81931500] HPFS/QNX/AUX
 2: A6 7651 0 1 - 9728 254 63 [ 122913315: 33383070] OpenBSD
 3: 00 0 0 0 - 0 0 0 [ 0: 0] unused
fdisk: 1>

+++

a = /, d = /tmp, e = /var, g = /usr, h = /home
i = Windows, j = data

# disklabel wd0
# Inside MBR partition 2: type A6 start 122913315 size 33383070
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: ST380817AS
falgs:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 156301488
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0

16 partitions:
# size offset fstype [fsize bsize cpg]
 a: 306621 122913315 4.2BSD 2048 16384 304 # Cyl 121937*-122241
 b: 524160 123219936 swap # Cyl 122242 -122761
 c: 156301488 0 unused 0 0 # Cyl 0 -155060
 d: 1536192 123744096 4.2BSD 2048 16384 328 # Cyl 122762 -124285
 e: 307440 125280288 4.2BSD 2048 16384 306 # Cyl 124286 -124590
 g: 14335776 125587728 4.2BSD 2048 16384 328 # Cyl 124591 -138812
 h: 16372881 139923504 4.2BSD 2048 16384 328 # Cyl 138813 -155055*
 i: 40965687 63 unknown # Cyl 0*- 40640*
 j: 81931500 40965750 unknown # Cyl 40640*-121921*
#

Need more information?
What's happening?
How I can solve this problem?

thanks

thiago




I jump 1 cylinder between partition 1 and 2.

1. What do you mean by this?

2. If your active partition is a Windows one how do you intend to boot
OpenBSD? Do you have a boot manager? Do you use ntldr and boot.ini?

3. What happens when you try to boot? Do you have any error messages?

Andrey



Re: booting problem

2007-05-11 Thread alicornio
Hi guys 

Problems with my webmail. I'm sorry. 

>> Hi all 
>> 
>> I can't boot my system after the instalation. My OS can't be finded. 
>> I follow the faq (4.12.2 - My i386 won't boot after install) and nothing 
>> change. But I can boot with CD typing "b hd0a:\bsd". 
>> 
>> When I tried install again I saw a warning in disklabel stage: 
>> 
>> WARNING: inode blocks/cyl group (155) >= data blocks (5) in last 
>> cylinder group. This implies 188 sector(s) cannot be allocated. 
>> 
>> What's happening? 
>> How I can solve this problem? 
>> 
>> thx all 
>> 
>> Thiago 
>> 
>> 
>If you post at least output of "fdisk wd0" and "disklabel wd0" commands... 

My disk: [WIN(ntfs)][DATA(ntfs)][OpenBSD] 

1- Booting from frist partition (my webmail can't print 
 lines with '*' in the begin) 
2- I jump 1 cylinder between partition 1 and 2. 

#fdisk -e wd0 
Enter 'help' for information 
fdisk: 1> p m 
Disk: wd0 geometry: 9729/255/63 [76317 Megabytes] 
Offset: 0 Signature: 0xAA55 
 Starting Ending LBA Info: 
 #: id C H S - C H S [ start: size ] 
- 
 0: 070   1   1 - 2549 254 63 [   63: 20003M]HPFS/QNX/AUX 
 1: 07 2550 0 1 - 7649 254 63 [ 40965750: 40006M] HPFS/QNX/AUX 
 2: A6 7651 0 1 - 9728 254 63 [ 122913315: 16300M] OpenBSD 
 3: 00 0 0 0 - 0 0 0 [ 0: 0M] unused 
fdisk: 1> 

+++ 

fdisk: 1> p 
Disk: wd0 geometry: 9729/255/63 [156296385 Sectors] 
Offset: 0 Signature: 0xAA55 
 Starting Ending LBA Info: 
 #: id C H S - C H S [ start: size ] 
- 
 0: 070   1   1 - 2549 254 63 [ 63:   40965687] HPFS/QNX/AUX 
 1: 07 2550 0 1 - 7649 254 63 [ 40965750: 81931500] HPFS/QNX/AUX 
 2: A6 7651 0 1 - 9728 254 63 [ 122913315: 33383070] OpenBSD 
 3: 00 0 0 0 - 0 0 0 [ 0: 0] unused 
fdisk: 1> 

+++ 

a = /, d = /tmp, e = /var, g = /usr, h = /home 
i = Windows, j = data 

# disklabel wd0 
# Inside MBR partition 2: type A6 start 122913315 size 33383070 
# /dev/rwd0c: 
type: ESDI 
disk: ESDI/IDE disk 
label: ST380817AS 
falgs: 
bytes/sector: 512 
sectors/track: 63 
tracks/cylinder: 16 
sectors/cylinder: 1008 
cylinders: 16383 
total sectors: 156301488 
rpm: 3600 
interleave: 1 
trackskew: 0 
cylinderskew: 0 
headswitch: 0 # microseconds 
track-to-track seek: 0 # microseconds 
drivedata: 0 

16 partitions: 
# size offset fstype [fsize bsize cpg] 
 a: 306621 122913315 4.2BSD 2048 16384 304 # Cyl 121937*-122241 
 b: 524160 123219936 swap # Cyl 122242 -122761 
 c: 156301488 0 unused 0 0 # Cyl 0 -155060 
 d: 1536192 123744096 4.2BSD 2048 16384 328 # Cyl 122762 -124285 
 e: 307440 125280288 4.2BSD 2048 16384 306 # Cyl 124286 -124590 
 g: 14335776 125587728 4.2BSD 2048 16384 328 # Cyl 124591 -138812 
 h: 16372881 139923504 4.2BSD 2048 16384 328 # Cyl 138813 -155055* 
 i: 40965687 63 unknown # Cyl 0*- 40640* 
 j: 81931500 40965750 unknown # Cyl 40640*-121921* 
# 

Need more information? 
What's happening? 
How I can solve this problem? 

thanks 

thiago 



Re: booting problem

2007-05-11 Thread alicornio
Hi guys 

>> Hi all 
>> 
>> I can't boot my system after the instalation. My OS can't be finded. 
>> I follow the faq (4.12.2 - My i386 won't boot after install) and nothing 
>> change. But I can boot with CD typing "b hd0a:\bsd". 
>> 
>> When I tried install again I saw a warning in disklabel stage: 
>> 
>> WARNING: inode blocks/cyl group (155) >= data blocks (5) in last 
>> cylinder group. This implies 188 sector(s) cannot be allocated. 
>> 
>> What's happening? 
>> How I can solve this problem? 
>> 
>> thx all 
>> 
>> Thiago 
>> 
>> 
>If you post at least output of "fdisk wd0" and "disklabel wd0" commands... 


My disk: [WIN(ntfs)][DATA(ntfs)][OpenBSD] 

1- I know, it's flaged to my Windows partition 

2- I jump 1 cylinder between partition 1 and 2. 

#fdisk -e wd0 
Enter 'help' for information 
fdisk: 1> p m 
Disk: wd0   geometry: 9729/255/63 [76317 Megabytes] 
Offset: 0   Signature: 0xAA55 
 StartingEnding  LBA Info: 
 #: idC   H   S -C   H  S [ start:  size ] 
- 
*0: 070   1   1 - 2549 254 63 [63: 20003M] HPFS/QNX/AUX 
 1: 07 2550   0   1 - 7649 254 63 [  40965750: 40006M] HPFS/QNX/AUX 
 2: A6 7651   0   1 - 9728 254 63 [ 122913315: 16300M] OpenBSD 
 3: 000   0   0 -0   0  0 [ 0: 0M] unused 
fdisk: 1> 

+++ 

fdisk: 1> p 
Disk: wd0   geometry: 9729/255/63 [156296385 Sectors] 
Offset: 0   Signature: 0xAA55 
 StartingEnding  LBA Info: 
 #: idC   H   S -C   H  S [ start:  size ] 
- 
*0: 070   1   1 - 2549 254 63 [63:   40965687] HPFS/QNX/AUX 
 1: 07 2550   0   1 - 7649 254 63 [  40965750:   81931500] HPFS/QNX/AUX 
 2: A6 7651   0   1 - 9728 254 63 [ 122913315:   33383070] OpenBSD 
 3: 000   0   0 -0   0  0 [ 0:  0] unused 
fdisk: 1> 

+++ 

a = /, d = /tmp, e = /var, g = /usr, h = /home 
i = Windows, j = data 

# disklabel wd0 
# Inside MBR partition 2: type A6 start 122913315 size 33383070 
# /dev/rwd0c: 
type: ESDI 
disk: ESDI/IDE disk 
label: ST380817AS 
falgs: 
bytes/sector: 512 
sectors/track: 63 
tracks/cylinder: 16 
sectors/cylinder: 1008 
cylinders: 16383 
total sectors: 156301488 
rpm: 3600 
interleave: 1 
trackskew: 0 
cylinderskew: 0 
headswitch: 0  # microseconds 
track-to-track seek: 0 # microseconds 
drivedata: 0 

16 partitions: 
# size offset   fstype  [fsize   bsize   cpg] 
  a:306621  122913315   4.2BSD2048   16384   304 # Cyl 
121937*-122241 
  b:524160  123219936 swap   # Cyl 122242 
-122761 
  c: 156301488  0   unused   0   0   # Cyl 0 -155060 
  d:   1536192  123744096   4.2BSD2048   16384   328 # Cyl 122762 
-124285 
  e:307440  125280288   4.2BSD2048   16384   306 # Cyl 124286 
-124590 
  g:  14335776  125587728   4.2BSD2048   16384   328 # Cyl 124591 
-138812 
  h:  16372881  139923504   4.2BSD2048   16384   328 # Cyl 138813 
-155055* 
  i:  40965687 63  unknown   # Cyl 0*- 
40640* 
  j:  81931500   40965750  unknown   # Cyl 
40640*-121921* 
# 

Need more information? 
What's happening? 
How I can solve this problem? 

thanks 

thiago 



Re: booting problem

2007-05-11 Thread Andrey Shuvikov

On 5/11/07, alicornio <[EMAIL PROTECTED]> wrote:

Hi all

I can't boot my system after the instalation. My OS can't be finded.
I follow the faq (4.12.2 - My i386 won't boot after install) and nothing
change. But I can boot with CD typing "b hd0a:\bsd".

When I tried install again I saw a warning in disklabel stage:

WARNING: inode blocks/cyl group (155) >= data blocks (5) in last
cylinder group. This implies 188 sector(s) cannot be allocated.

What's happening?
How I can solve this problem?

thx all

Thiago



If you post at least output of "fdisk wd0" and "disklabel wd0" commands...



Re: booting problem

2007-05-10 Thread Otto Moerbeek
On Fri, 11 May 2007, alicornio wrote:

> Hi all 
> 
> I can't boot my system after the instalation. My OS can't be finded. 
> I follow the faq (4.12.2 - My i386 won't boot after install) and nothing 
> change. But I can boot with CD typing "b hd0a:\bsd". 
> 
> When I tried install again I saw a warning in disklabel stage: 
> 
> WARNING: inode blocks/cyl group (155) >= data blocks (5) in last 
> cylinder group. This implies 188 sector(s) cannot be allocated. 

This is not a problem. It's just that a very small part o f your disk
is not being used.

> 
> What's happening? 
> How I can solve this problem? 

Since you left out any details about your setup, we cannot help you with
the booting problem.

-Otto



Re: booting problem

2007-05-10 Thread Nick Guenther

On 5/11/07, alicornio <[EMAIL PROTECTED]> wrote:

Hi all

I can't boot my system after the instalation. My OS can't be finded.
I follow the faq (4.12.2 - My i386 won't boot after install) and nothing
change. But I can boot with CD typing "b hd0a:\bsd".

When I tried install again I saw a warning in disklabel stage:

WARNING: inode blocks/cyl group (155) >= data blocks (5) in last
cylinder group. This implies 188 sector(s) cannot be allocated.

What's happening?
How I can solve this problem?


Did you leave 63 sectors free at the start of the disk? This seems
like something is getting overwritten poorly.

-Nick



booting problem

2007-05-10 Thread alicornio
Hi all 

I can't boot my system after the instalation. My OS can't be finded. 
I follow the faq (4.12.2 - My i386 won't boot after install) and nothing 
change. But I can boot with CD typing "b hd0a:\bsd". 

When I tried install again I saw a warning in disklabel stage: 

WARNING: inode blocks/cyl group (155) >= data blocks (5) in last 
cylinder group. This implies 188 sector(s) cannot be allocated. 

What's happening? 
How I can solve this problem? 

thx all 

Thiago