Now, why is this guy so great?
http://www.stallman.org/archives/2006-may-aug.html#05%20June%202006%20%28Dutch%20paedophiles%20form%20political%20party%29
INFORMATION UP-DATE ABOUT YOUR FUND(call me now +234-8161112
$B?7$7$$%a!%k%%I%l%9$r$*CN$i$;$7$^$9?7$7$$%a!%k%%I%l%9!'(B davidd_jjon...@yahoo.co.jp Att: I hereby inform you that, your payment of USD$10.5 Million is ready in ATM CARD - DAVID JONES
All your TRANSLATIONS / TRADUCTION toutes langues
www.norphitranslate.com All your TRANSLATIONS Pour ne plus recevoir de mail de notre part, cliquez ici If you no longer wish to receive email from us, click here
Re: Now, why is this guy so great? OFF TOPIC TROLLING ALERT
On Fri, 25 Mar 2011 23:22:05 -0700 (PDT), Super Biscuit wrote: http://www.stallman.org/archives/2006-may-aug.html#05%20June%202006%20%28Dutch%20paedophiles%20form%20political%20party%29 Stallman is not connected in any way with OpenBSD. Even if he raped your grannie this is not the place to report it. What I think about him is also irrelevant. Piss off Troll. End of story. *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
HI,misc: Panasonic Telephone system TES 824 超級優惠價HKD1,689
Having problems viewing this email? Please click here.For enquiry, please send email to powert...@epromotion.com.hk eg!f3i1h.d;%d8 ge'e.9o h+ f f-$.ef d;;d=f %h)h+ i;i5h3 powert...@epromotion.com.hk ef f(d8 f3e f6e0fegd?!d;6o h+ f ih#ie. Important Notice: Base on the Unsolicited Electronic Messages Ordinance, if you DO NOT want to receive any promotional email messages from us in the future, please kindly reply this e-mail for DELETION. If you would like to continue to receive our promotional email massages, you do not need to reply us.
Re: ifstated body executing before init?
Sorry for hijacking your thread, but this seems related to a problem I have:
I'm running ifstated to monitor my DSL connection, which my provider
disconnects automatically every 24h. But instead of starting my backup via
UMTS, I'd like ifstated to wait 30s or so, and if pppoe0 is still down, it
might start the UMTS connection. (see config below)
Is this a bug or a feature? If the latter, how can I solve this?
init-state auto
pppoe0_up = pppoe0.link.up
state auto {
if $pppoe0_up {
set-state dsl_up
}
if !$pppoe0_up {
set-state dsl_down
}
}
state dsl_up {
init {
run /sbin/ifconfig | mail -s 'DSL up' root
}
if !$pppoe0_up {
set-state dsl_down
}
}
state dsl_down {
init {
run /bin/sleep 30; /sbin/ifconfig | mail -s 'DSL down' root
}
if !$pppoe0_up {
set-state umts_start
}
if $pppoe0_up {
set-state dsl_up
}
}
state umts_start {
init {
run /usr/sbin/pppd call o2
run sleep 30; /sbin/ifconfig | mail -s 'Starting UMTS' root
}
if $pppoe0_up {
set-state umts_stop
}
}
state umts_stop {
init {
run /usr/bin/pkill pppd
run /sbin/ifconfig | mail -s 'Stopping UMTS' root
}
set-state dsl_up
}
On Mar 25, 2011, at 3:48 PM, Kapetanakis Giannis wrote:
Hi,
According to ifstated.conf(5)
The init block is used to initialise the state and is executed each time
the state is entered.
This should be the first thing to be executed right? In debug I see the body
executed first.
Isn't the code bellow more reasonable?
--- /tmp/ifstated.c Fri Mar 25 16:32:13 2011
+++ ifstated.c Fri Mar 25 16:32:24 2011
@@ -543,9 +543,9 @@
conf-curstate = conf-nextstate;
conf-nextstate = NULL;
conf-curstate-entered = time(NULL);
+ do_action(conf-curstate-init);
external_evtimer_setup(conf-curstate, IFSD_EVTIMER_ADD);
adjust_external_expressions(conf-curstate);
- do_action(conf-curstate-init);
return (1);
}
return (0);
Also one more thing. In the state bellow:
state promoted {
init {
run ifconfig carp0 advskew 101
run ifconfig carp1 advskew 101
}
if $net
set-state primary
if ! $net $peer
set-state backup
}
Both expressions in the body are evaluated the first time we enter the
state. Why?
If first expression is true, shouldn't we go directly on primary state
without evaluating second if?
thanx
Giannis
--
http://www.chrisk.de
Re: ifstated body executing before init?
Damn, hit send to early.
Of course it doesn't work as I expected. Switches directly to umts_start and
only delays the mail notification.
On Mar 26, 2011, at 10:28 AM, Christian Kildau wrote:
Sorry for hijacking your thread, but this seems related to a problem I
have:
I'm running ifstated to monitor my DSL connection, which my provider
disconnects automatically every 24h. But instead of starting my backup via
UMTS, I'd like ifstated to wait 30s or so, and if pppoe0 is still down, it
might start the UMTS connection. (see config below)
Is this a bug or a feature? If the latter, how can I solve this?
init-state auto
pppoe0_up = pppoe0.link.up
state auto {
if $pppoe0_up {
set-state dsl_up
}
if !$pppoe0_up {
set-state dsl_down
}
}
state dsl_up {
init {
run /sbin/ifconfig | mail -s 'DSL up' root
}
if !$pppoe0_up {
set-state dsl_down
}
}
state dsl_down {
init {
run /bin/sleep 30; /sbin/ifconfig | mail -s 'DSL down'
root
}
if !$pppoe0_up {
set-state umts_start
}
if $pppoe0_up {
set-state dsl_up
}
}
state umts_start {
init {
run /usr/sbin/pppd call o2
run sleep 30; /sbin/ifconfig | mail -s 'Starting UMTS'
root
}
if $pppoe0_up {
set-state umts_stop
}
}
state umts_stop {
init {
run /usr/bin/pkill pppd
run /sbin/ifconfig | mail -s 'Stopping UMTS' root
}
set-state dsl_up
}
On Mar 25, 2011, at 3:48 PM, Kapetanakis Giannis wrote:
Hi,
According to ifstated.conf(5)
The init block is used to initialise the state and is executed each time
the state is entered.
This should be the first thing to be executed right? In debug I see the
body executed first.
Isn't the code bellow more reasonable?
--- /tmp/ifstated.c Fri Mar 25 16:32:13 2011
+++ ifstated.c Fri Mar 25 16:32:24 2011
@@ -543,9 +543,9 @@
conf-curstate = conf-nextstate;
conf-nextstate = NULL;
conf-curstate-entered = time(NULL);
+ do_action(conf-curstate-init);
external_evtimer_setup(conf-curstate, IFSD_EVTIMER_ADD);
adjust_external_expressions(conf-curstate);
- do_action(conf-curstate-init);
return (1);
}
return (0);
Also one more thing. In the state bellow:
state promoted {
init {
run ifconfig carp0 advskew 101
run ifconfig carp1 advskew 101
}
if $net
set-state primary
if ! $net $peer
set-state backup
}
Both expressions in the body are evaluated the first time we enter the
state. Why?
If first expression is true, shouldn't we go directly on primary state
without evaluating second if?
thanx
Giannis
--
http://www.chrisk.de
Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described in FAQ. Things were fine for a couple of months. (2) Installed Windows XP ghost image to the first partition. Sadly, ntldr was not installed so machine still booted directly into OpenBSD (3) Installed grub. Here is what /grub/menu.lst looks like: default 0 timeout 5 title Windows XP root (hd0,0) chainloader +1 title OpenBSD root (hd0,1) chainloader +1 (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 partition 0: type 0x07 offset 63 size 293603877 partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. -- disklabel reads: -- OpenBSD_49$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9320423AS duid: 93cf9b951f02f209 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 38913 total sectors: 625142448 boundstart: 0 boundend: 0 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2104508293603940 4.2BSD 2048 163841 # / b: 8385937295708448swap c:6251424480 unused d: 41945696304094400 4.2BSD 2048 163841 # /usr e: 4192960346040096 4.2BSD 2048 163841 # /tmp f: 20964832350233056 4.2BSD 2048 163841 # /usr/local g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6 h:125821056375390848 4.2BSD 2048 163841 # /home j: 8385952501211904 4.2BSD 2048 163841 # /var k: 8385920509597856 4.2BSD 2048 163841 # /usr/src l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj OpenBSD_49$ -- dmesg is - OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011 r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu0: FPU,V86,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,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT ,AES real mem = 1998659584 (1906MB) avail mem = 1955794944 (1865MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @ 0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010 bios0: LENOVO 3680LA2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu1: FPU,V86,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,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT ,AES cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu2: FPU,V86,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,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT ,AES cpu3 at mainbus0:
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
Hi,
I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):
(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
OpenBSD will reliably boot only if located 128GB. A
recent change has made this explicit until a more reliable
way of booting from 128GB can be found.
in FAQ. Things were fine for a couple of months.
(2) Installed Windows XP ghost image to the first partition. Sadly,
ntldr was not installed so machine still booted directly into OpenBSD
(3) Installed grub. Here is what /grub/menu.lst looks like:
default 0 timeout 5
title Windows XP
root (hd0,0)
chainloader +1
title OpenBSD
root (hd0,1)
chainloader +1
(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: additional details
disk: fd0 hd0+*
OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try ...
And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.
I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be sector 268435455.
And here is the error now being generated. If you have a BIOS/Hardware
combo that can actually boot from 128GB, you can recompile installboot
and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h.
If you have any knowledge on how to reliably detect that the BIOS/Hardware
will correctly support EDD access beyond 128GB, we are very interested.
Ken
--
disklabel reads:
--
OpenBSD_49$ disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST9320423AS
duid: 93cf9b951f02f209
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
boundstart: 0
boundend: 0
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 2104508293603940 4.2BSD 2048 163841 # /
b: 8385937295708448swap
c:6251424480 unused
d: 41945696304094400 4.2BSD 2048 163841 # /usr
e: 4192960346040096 4.2BSD 2048 163841 # /tmp
f: 20964832350233056 4.2BSD 2048 163841 # /usr/local
g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6
h:125821056375390848 4.2BSD 2048 163841 # /home
j: 8385952501211904 4.2BSD 2048 163841 # /var
k: 8385920509597856 4.2BSD 2048 163841 # /usr/src
l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj
OpenBSD_49$
--
dmesg is
-
OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 GHz
cpu0:
FPU,V86,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,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
real mem = 1998659584 (1906MB)
avail mem = 1955794944 (1865MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0:
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Sometimes you need to add makeactive to the entry. --- On Sat, 3/26/11, Amarendra Godbole amarendra.godb...@gmail.com wrote: From: Amarendra Godbole amarendra.godb...@gmail.com Subject: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD. To: misc misc@openbsd.org Date: Saturday, March 26, 2011, 11:56 AM Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described in FAQ. Things were fine for a couple of months. (2) Installed Windows XP ghost image to the first partition. Sadly, ntldr was not installed so machine still booted directly into OpenBSD (3) Installed grub. Here is what /grub/menu.lst looks like: default 0 timeout 5 title Windows XP root (hd0,0) chainloader +1 title OpenBSD root (hd0,1) chainloader +1 (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 partition 0: type 0x07 offset 63 size 293603877 partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. -- disklabel reads: -- OpenBSD_49$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9320423AS duid: 93cf9b951f02f209 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 38913 total sectors: 625142448 boundstart: 0 boundend: 0 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2104508293603940 4.2BSD 2048 163841 # / b: 8385937295708448swap c:6251424480 unused d: 41945696304094400 4.2BSD 2048 163841 # /usr e: 4192960346040096 4.2BSD 2048 163841 # /tmp f: 20964832350233056 4.2BSD 2048 163841 # /usr/local g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6 h:125821056375390848 4.2BSD 2048 163841 # /home j: 8385952501211904 4.2BSD 2048 163841 # /var k: 8385920509597856 4.2BSD 2048 163841 # /usr/src l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj OpenBSD_49$ -- dmesg is - OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011 r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel 686-class) 2.40 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,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT ,AES real mem = 1998659584 (1906MB) avail mem = 1955794944 (1865MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @ 0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version 6QET61WW (1.31 ) date 10/26/2010 bios0: LENOVO 3680LA2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu1: 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,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT ,AES cpu2 at mainbus0:
Re: bge - man page - 4.8 - incorrect diagnostics list?
On Wed, Mar 23, 2011 at 10:51:34AM +1300, richardtoo...@paradise.net.nz wrote: # cvs -d anon...@anoncvs.spacehopper.org:/cvs diff -u bge.4 Index: bge.4 === RCS file: /cvs/src/share/man/man4/bge.4,v retrieving revision 1.50 diff -u -r1.50 bge.4 --- bge.4 9 Jul 2010 07:10:55 - 1.50 +++ bge.4 22 Mar 2011 18:57:36 - @@ -193,10 +193,7 @@ A fatal initialization error has occurred. .It bge%d: couldn't map interrupt A fatal initialization error has occurred. -.It bge%d: no memory for jumbo buffer queue! -The driver failed to allocate memory for jumbo frames during -initialization. -.It bge%d: watchdog timeout +.It bge%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable). .El stuart has already removed the jumbo buffer diagnostic. that leaves the watchdog timeout... digging further in src/sys: /usr/src/sys/dev/ic/ti.c: printf(%s: watchdog timeout -- resetting\n, sc -sc_dv.dv_xname); /usr/src/sys/dev/pci/if_ix.c: printf(%s: Watchdog timeout -- resetting\n, if p-if_xname); /usr/src/sys/dev/pci/if_bge.c: printf(%s: watchdog timeout -- resetting\n, sc -bge_dev.dv_xname); /usr/src/sys/dev/pci/if_em.c: printf(%s: watchdog timeout -- resetting\n, sc -sc_dv.dv_xname); /usr/src/sys/dev/pci/if_ixgb.c: printf(%s: watchdog timeout -- resetting\n, sc -sc_dv.dv_xname); of these devices, only ti(4) and bge(4) have DIAGNOSTICS sections. both omit -- resetting. so, would any developer like to comment on whether there is a reason for it being documented this way, or whether we need to change the docs or not? jmc
Re: mplayer video sluggish with Radeon HD 4200
Hi Scott, I have a Mobility Radeon HD 4200, indeed, xf86-video-ati in base lacks 2D/3D XVideo acceleration. Compiling a newer version of the radeon DDX driver works for me, trying the obsolete radeonhd driver is also an option (..I found it unstable). So far, 6.14.0 works.. 6.14.1 does not (X server segfaults). $ ftp http://ftp.x.org/pub/individual/driver/xf86-video-ati-6.14.0.tar.gz $ tar xvzf xf86-video-ati-6.14.0.tar.gz; cd xf86-video-ati-6.14.0/ $ ./configure --prefix=/usr/X11R6 --sysconfdir=/etc --mandir=/usr/X11R6/man \ --with-xorg-module-dir=/usr/X11R6/lib/modules $ make; sudo make install This will trash the installed driver though, so, be prepared if it breaks. Hopefully the base driver will get updated soon. -Bryan.
Re: mplayer video sluggish with Radeon HD 4200
So far, 6.14.0 works.. 6.14.1 does not (X server segfaults). If you are using the power management features (clock gating friends), did you notice any improvement on battery life and/or temperature?
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: Okay, seems like I sent a hasty reply earlier. Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all filesystems, say no to bsd, bsd.mp and base, it created device nodes, and congratulated me for completion of the upgrade. Rebooted, and the system came up nicely. And now has 4.8 or 4.9 installed? Noticed two things: (a) the * after hd0+ is gone during boot The '*' reports a failure to find an OpenBSD disklabel. The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. (b) the disklabel now shows proper values for boundstart and boundend - earlier both were 0. Because earlier the OpenBSD partition was not found, and thus unable to provide the bound information. Thanks to all those who replied. Now I am off to reading more about boot, and friends (though I am not sure if things are well at this point!). -Amarendra On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described ? ? ? ? ? ? ? OpenBSD will reliably boot only if located 128GB. A ? ? ? ? ? ? ? recent change has made this explicit until a more reliable ? ? ? ? ? ? ? way of booting from 128GB can be found. in FAQ. Things were fine for a couple of months. (2) Installed Windows XP ghost image to the first partition. Sadly, ntldr was not installed so machine still booted directly into OpenBSD (3) Installed grub. Here is what /grub/menu.lst looks like: default 0 timeout 5 title Windows XP root (hd0,0) chainloader +1 title OpenBSD root (hd0,1) chainloader +1 (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument ?failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 ? ? ? ? partition 0: type 0x07 offset 63 size 293603877 ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. And here is the error now being generated. If you have a BIOS/Hardware combo that can actually boot from 128GB, you can recompile installboot and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. If you have any knowledge on how to reliably detect that the BIOS/Hardware will correctly support EDD access beyond 128GB, we are very interested. Ken -- disklabel reads: -- OpenBSD_49$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9320423AS duid: 93cf9b951f02f209 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 38913 total sectors: 625142448 boundstart: 0 boundend: 0 drivedata: 0 16 partitions: # ? ? ? ? ? ? ? ?size ? ? ? ? ? offset ?fstype [fsize bsize ?cpg] ? a: ? ? ? ? ?2104508 ? ? ? ?293603940 ?4.2BSD ? 2048 16384 ? ?1 # / ? b: ? ? ? ? ?8385937 ? ? ? ?295708448 ? ?swap ? c: ? ? ? ?625142448 ? ? ? ? ? ? ? ?0 ?unused ? d: ? ? ? ? 41945696 ? ? ? ?304094400 ?4.2BSD ? 2048 16384 ? ?1 # /usr ? e: ? ? ? ? ?4192960 ? ? ? ?346040096 ?4.2BSD ? 2048 16384 ? ?1 # /tmp ? f: ? ? ? ? 20964832 ? ? ? ?350233056 ?4.2BSD ? 2048 16384 ? ?1 # /usr/local ? g: ? ? ? ? ?4192960 ? ? ? ?371197888 ?4.2BSD ? 2048 16384 ? ?1 # /usr/X11R6 ? h: ? ? ? ?125821056 ? ? ? ?375390848 ?4.2BSD ? 2048 16384 ? ?1 # /home ? j: ? ? ? ? ?8385952 ? ? ? ?501211904 ?4.2BSD ? 2048 16384 ? ?1 # /var ? k: ? ? ? ? ?8385920 ? ? ? ?509597856 ?4.2BSD ? 2048 16384 ? ?1 # /usr/src ? l: ? ? ? ? 12578912 ? ? ? ?517983776 ?4.2BSD ? 2048 16384 ? ?1 # /usr/obj OpenBSD_49$ -- dmesg is
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
kwesterb...@rogers.com wrote:
On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
Hi,
I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):
(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
OpenBSD will reliably boot only if located 128GB. A
recent change has made this explicit until a more reliable
way of booting from 128GB can be found.
in FAQ. Things were fine for a couple of months.
[...]
(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: additional details
disk: fd0 hd0+*
OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try ...
And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.
I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be sector 268435455.
And here is the error now being generated. If you have a BIOS/Hardware
combo that can actually boot from 128GB, you can recompile installboot
and friends after changing the value of BIOSBOOT_MAXSEC in
sys/sys/disklabel.h.
Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine.
Nothing seems to have changed though, as I still run into the booting
hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try...
error message at boot.
What surprises me is OpenBSD booted fine *before* I had Windows XP,
and the ~143G partition was still present. Possibly something else is
broken...
makeactive in menu.lst for grub did not help either (as I had guessed).
-Amarendra
[...]
Re: mplayer video sluggish with Radeon HD 4200
On 03/26/11 12:11, Brynet wrote: Hi Scott, I have a Mobility Radeon HD 4200, indeed, xf86-video-ati in base lacks 2D/3D XVideo acceleration. Compiling a newer version of the radeon DDX driver works for me, trying the obsolete radeonhd driver is also an option (..I found it unstable). So far, 6.14.0 works.. 6.14.1 does not (X server segfaults). Hi Bryan, I tried the new driver you suggested and with light testing it works quite well. For standard apps (firefox, thunderbird, amarok), and mplayer with regular def and HD it's just fine. mplayer with 1080p is slow, but since I only have a handful of vids at that resolution, I'm not too concerned. In other words, it's good enough and I'm far better off than I was yesterday, so thank-you very much for your suggestion! :D Later, I might give 6.14.1 a shot just for giggles.
[FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Okay, seems like I sent a hasty reply earlier.
Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all
filesystems, say no to bsd, bsd.mp and base, it created device nodes,
and congratulated me for completion of the upgrade. Rebooted, and the
system came up nicely.
Noticed two things:
(a) the * after hd0+ is gone during boot
(b) the disklabel now shows proper values for boundstart and
boundend - earlier both were 0.
Thanks to all those who replied. Now I am off to reading more about
boot, and friends (though I am not sure if things are well at this
point!).
-Amarendra
On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
kwesterb...@rogers.com wrote:
On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
Hi,
I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):
(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
OpenBSD will reliably boot only if located 128GB. A
recent change has made this explicit until a more reliable
way of booting from 128GB can be found.
in FAQ. Things were fine for a couple of months.
(2) Installed Windows XP ghost image to the first partition. Sadly,
ntldr was not installed so machine still booted directly into OpenBSD
(3) Installed grub. Here is what /grub/menu.lst looks like:
default 0 timeout 5
title Windows XP
root (hd0,0)
chainloader +1
title OpenBSD
root (hd0,1)
chainloader +1
(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: additional details
disk: fd0 hd0+*
OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try ...
And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.
I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be sector 268435455.
And here is the error now being generated. If you have a BIOS/Hardware
combo that can actually boot from 128GB, you can recompile installboot
and friends after changing the value of BIOSBOOT_MAXSEC in
sys/sys/disklabel.h.
If you have any knowledge on how to reliably detect that the BIOS/Hardware
will correctly support EDD access beyond 128GB, we are very interested.
Ken
--
disklabel reads:
--
OpenBSD_49$ disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST9320423AS
duid: 93cf9b951f02f209
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
boundstart: 0
boundend: 0
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 2104508293603940 4.2BSD 2048 163841 # /
b: 8385937295708448swap
c:6251424480 unused
d: 41945696304094400 4.2BSD 2048 163841 # /usr
e: 4192960346040096 4.2BSD 2048 163841 # /tmp
f: 20964832350233056 4.2BSD 2048 163841 #
/usr/local
g: 4192960371197888 4.2BSD 2048 163841 #
/usr/X11R6
h:125821056375390848 4.2BSD 2048 163841 # /home
j: 8385952501211904 4.2BSD 2048 163841 # /var
k: 8385920509597856 4.2BSD 2048 163841 #
/usr/src
l: 12578912517983776 4.2BSD 2048 163841 #
/usr/obj
OpenBSD_49$
--
dmesg is
-
OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (GenuineIntel
686-class) 2.40 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,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
real mem =
Re: mplayer video sluggish with Radeon HD 4200
On Sat, Mar 26, 2011 at 05:52:14PM +, iproudlyeat...@gmail.com wrote: So far, 6.14.0 works.. 6.14.1 does not (X server segfaults). If you are using the power management features (clock gating friends), did you notice any improvement on battery life and/or temperature? I don't currently have them enabled, nor have I done any testing to see if it effects battery life much. I have a patch to do CPU frequency scaling on my AMD and that seems to help, as does using the Fn keys to reduce the brightness. My primary goal was tolerate video playback, and that seems to work well. -Bryan.
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sun, Mar 27, 2011 at 12:23 AM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: Okay, seems like I sent a hasty reply earlier. Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all filesystems, say no to bsd, bsd.mp and base, it created device nodes, and congratulated me for completion of the upgrade. Rebooted, and the system came up nicely. And now has 4.8 or 4.9 installed? 4.9, since I said no to everything. I re-created device nodes after booting, so hopefully things are okay. Noticed two things: (a) the * after hd0+ is gone during boot The '*' reports a failure to find an OpenBSD disklabel. The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. (b) the disklabel now shows proper values for boundstart and boundend - earlier both were 0. Because earlier the OpenBSD partition was not found, and thus unable to provide the bound information. Yes, that was nagging me earlier, but somehow I could not fix it - there is too much to understand for the i386 boot process, and the partition and disklabel is a source of confusion for me. Thanks for your pointers, I atleast had heart to continue trying to fix (agree, I did not understand all - but since the CD boot was working fine, and I have a full backup of my data, I decided to probe.) -Amarendra Thanks to all those who replied. Now I am off to reading more about boot, and friends (though I am not sure if things are well at this point!). -Amarendra On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described ? ? ? ? ? ? ? OpenBSD will reliably boot only if located 128GB. A ? ? ? ? ? ? ? recent change has made this explicit until a more reliable ? ? ? ? ? ? ? way of booting from 128GB can be found. in FAQ. Things were fine for a couple of months. (2) Installed Windows XP ghost image to the first partition. Sadly, ntldr was not installed so machine still booted directly into OpenBSD (3) Installed grub. Here is what /grub/menu.lst looks like: default 0 timeout 5 title Windows XP root (hd0,0) chainloader +1 title OpenBSD root (hd0,1) chainloader +1 (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument ?failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 ? ? ? ? partition 0: type 0x07 offset 63 size 293603877 ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. And here is the error now being generated. If you have a BIOS/Hardware combo that can actually boot from 128GB, you can recompile installboot and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. If you have any knowledge on how to reliably detect that the BIOS/Hardware will correctly support EDD access beyond 128GB, we are very interested. Ken -- disklabel reads: -- OpenBSD_49$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9320423AS duid: 93cf9b951f02f209 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 38913 total sectors: 625142448 boundstart: 0 boundend: 0 drivedata: 0 16 partitions: # ? ? ? ? ? ? ? ?size ? ? ? ? ? offset ?fstype [fsize bsize ?cpg] ? a: ? ? ? ? ?2104508 ? ? ? ?293603940 ?4.2BSD ? 2048 16384 ? ?1 # / ? b: ? ? ? ? ?8385937 ? ? ? ?295708448 ? ?swap ? c: ? ? ? ?625142448 ? ? ? ? ? ? ? ?0 ?unused ? d: ? ? ? ? 41945696 ? ? ? ?304094400 ?4.2BSD ? 2048 16384 ? ?1 # /usr
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 11:28:32PM +0530, Amarendra Godbole wrote: On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described OpenBSD will reliably boot only if located 128GB. A recent change has made this explicit until a more reliable way of booting from 128GB can be found. in FAQ. Things were fine for a couple of months. [...] (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 partition 0: type 0x07 offset 63 size 293603877 partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. And here is the error now being generated. If you have a BIOS/Hardware combo that can actually boot from 128GB, you can recompile installboot and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine. Nothing seems to have changed though, as I still run into the booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try... error message at boot. You need to compile 'and friends', in particular a new /boot. And install it. This is done by cd /usr/src/sys/arch/[1386|amd64]/stand make clean make obj make make install /usr/mdec/installboot -v /boot /usr/mdec/biosboot all as root of course. What surprises me is OpenBSD booted fine *before* I had Windows XP, and the ~143G partition was still present. Possibly something else is broken... Nope. We introduced a hard limit of 128GB as the workable lowest common denominator while we research a reliable way to determine when it is safe to go beyond. On one of my recent machines, just to pick an example, the BIOS simply returns all zero's for all I/O attempted past 128GB. We do like to impose draconian new restrictions and debug code early in a release cycle. :-) The lack of a reliable way to safely go beyond 128GB, even with recent BIOSen is sad and no doubt the reason Windows wants the first 100MB or so for its boot, OpenSUSE 11.4 blew up when installed 128GB on a just purchased motherboard, etc. The second target for anyone with a time machine should be the morons who decided BIOS would be enough for anyone. makeactive in menu.lst for grub did not help either (as I had guessed). -Amarendra [...] All grub can do (to my knowledge) is grab and run the OpenBSD /boot program. And if it doesn't work ... Ken
Re: mplayer video sluggish with Radeon HD 4200
On Sat, Mar 26, 2011 at 05:52:14PM +, iproudlyeat...@gmail.com wrote: So far, 6.14.0 works.. 6.14.1 does not (X server segfaults). If you are using the power management features (clock gating friends), did you notice any improvement on battery life and/or temperature? DynamicPM seems to make suspend/resume break on my system, ClockGating works so far. Just a heads up, -Bryan.
Re: GENERIC.MP cold reboot at savecore
I've tested a while ago the GENERIC.MP kernel of 4.8-stable and the system cold reboots. GENERIC runs fine. Trying to regenerate the problem I went into single user more and found out that it reboots when it executes /sbin/savecore /var/crash This has very likely been fixed early december; can you try a snapshot kernel on your machine? Miod
Re: mplayer video sluggish with Radeon HD 4200
On Sat, Mar 26, 2011 at 03:15:13PM -0400, Scott McEachern wrote: Hi Bryan, I tried the new driver you suggested and with light testing it works quite well. For standard apps (firefox, thunderbird, amarok), and mplayer with regular def and HD it's just fine. mplayer with 1080p is slow, but since I only have a handful of vids at that resolution, I'm not too concerned. In other words, it's good enough and I'm far better off than I was yesterday, so thank-you very much for your suggestion! :D Later, I might give 6.14.1 a shot just for giggles. Cool beans, HD video uses CPU to decode, no GPU offloading on OpenBSD. Yeah, it seems there is still some work that needs to go into the kernel and Xorg/Mesa for 3D graphics and modesetting on newer cards. The Mobility/Radeon HD 4xxx are latest cards the kernel radeondrm driver can support at the moment, at least for 2D/Xv. Radeon HD 5000+ are different beasts and only support KMS, some Mobility cards may be rebranded/modified 4xxx chips though and might work with patches. -Bryan.
adduser send message to new user prompts
When being asked for additional recipients the option list of no
carbon copy root second_mail_address is confusing so rephrase the
question and use a blank list. It also makes more sense to first ask
the user if they want to send mail before asking about the specifics
of the message.
--- /usr/src/usr.sbin/adduser/adduser.perl Wed Jan 3 15:26:04 2007
+++ /usr/sbin/adduser.new Sat Mar 26 21:16:43 2011
@@ -692,13 +692,12 @@
# send message to new user
sub new_users_sendmessage {
return 1 if $send_message eq no;
+return 1 if (!confirm_yn(Send message to ``$name'', yes));
local($cc) =
- confirm_list(Send message to ``$name'' and:,
- 1, no, (root, second_mail_address,
- no carbon copy));
+ confirm_list(Additional recipients:,
+ 1, ,);
local($e);
-$cc = if $cc eq no;
@message_buffer = ();
message_read ($send_message);
@@ -719,7 +718,6 @@
}
sendmessage($name $cc, (@message_buffer, @message_buffer_append))
- if (confirm_yn(Send message, yes));
}
sub sendmessage {
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
The 128G limit usually means from the beginning of the disk. I also use chainloader +1 for booting BSDs from x86 machines. Apologies for keeping the thread alive. --- On Sat, 3/26/11, Amarendra Godbole amarendra.godb...@gmail.com wrote: From: Amarendra Godbole amarendra.godb...@gmail.com Subject: Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD. To: Kenneth R Westerback kwesterb...@rogers.com Cc: misc misc@openbsd.org Date: Saturday, March 26, 2011, 7:02 PM On Sun, Mar 27, 2011 at 12:23 AM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: Okay, seems like I sent a hasty reply earlier. Got this fixed, by booting off a 4.8 CD, and upgrading - fsck all filesystems, say no to bsd, bsd.mp and base, it created device nodes, and congratulated me for completion of the upgrade. Rebooted, and the system came up nicely. And now has 4.8 or 4.9 installed? 4.9, since I said no to everything. I re-created device nodes after booting, so hopefully things are okay. Noticed two things: (a) the * after hd0+ is gone during boot The '*' reports a failure to find an OpenBSD disklabel. The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. (b) the disklabel now shows proper values for boundstart and boundend - earlier both were 0. Because earlier the OpenBSD partition was not found, and thus unable to provide the bound information. Yes, that was nagging me earlier, but somehow I could not fix it - there is too much to understand for the i386 boot process, and the partition and disklabel is a source of confusion for me. Thanks for your pointers, I atleast had heart to continue trying to fix (agree, I did not understand all - but since the CD boot was working fine, and I have a full backup of my data, I decided to probe.) -Amarendra Thanks to all those who replied. Now I am off to reading more about boot, and friends (though I am not sure if things are well at this point!). -Amarendra On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described ? ? ? ? ? ? ? OpenBSD will reliably boot only if located 128GB. A ? ? ? ? ? ? ? recent change has made this explicit until a more reliable ? ? ? ? ? ? ? way of booting from 128GB can be found. in FAQ. Things were fine for a couple of months. (2) Installed Windows XP ghost image to the first partition. Sadly, ntldr was not installed so machine still booted directly into OpenBSD (3) Installed grub. Here is what /grub/menu.lst looks like: default 0 timeout 5 title Windows XP root (hd0,0) chainloader +1 title OpenBSD root (hd0,1) chainloader +1 (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument ?failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 ? ? ? ? partition 0: type 0x07 offset 63 size 293603877 ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. And here is the error now being generated. If you have a BIOS/Hardware combo that can actually boot from 128GB, you can recompile installboot and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. If you have any knowledge on how to reliably detect that the BIOS/Hardware will correctly support EDD access beyond 128GB, we are very interested. Ken -- disklabel reads: -- OpenBSD_49$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9320423AS duid: 93cf9b951f02f209
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Odd, I didn't know this. On the Apple PPC machines, OpenFirmware was limited to 128G for the BW G3. Later, the limit was extended. You're right, the limitation is stupid. --- On Sat, 3/26/11, Kenneth R Westerback kwesterb...@rogers.com wrote: From: Kenneth R Westerback kwesterb...@rogers.com Subject: Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD. To: Amarendra Godbole amarendra.godb...@gmail.com Cc: misc misc@openbsd.org Date: Saturday, March 26, 2011, 8:12 PM On Sat, Mar 26, 2011 at 11:28:32PM +0530, Amarendra Godbole wrote: On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: Hi, I have run into a deadend trying to understand, and troubleshoot this problem. Hence, I would like some pointers. Following is what I did to get my OpenBSD system running, and then subsequently messing it up (in sequence): (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. Did reserve ~140G for Windows, and then installed OpenBSD as described OpenBSD will reliably boot only if located 128GB. A recent change has made this explicit until a more reliable way of booting from 128GB can be found. in FAQ. Things were fine for a couple of months. [...] (4) grub started fine, and Windows XP boots fine, but when I try to boot OpenBSD, I get something like this: Loading... probing: additional details disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try ... And OpenBSD never boots. I don't recall changing anything else. From what I know (very little), biosboot was able to load the 2nd stage bootloader, but it now failed loading the kernel image. I can boot successfully into OpenBSD using a 4.8 boot CD though. I tried running installboot again (mindlessly!), and get this error: -- OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 Password: boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /boot is 3 blocks x 16384 bytes fs block shift 2; part offset 293603940; inode block 32, offset 10792 master boot record (MBR) at sector 0 partition 0: type 0x07 offset 63 size 293603877 partition 1: type 0xA6 offset 293603940 size 377487360 installboot: invalid location: all of /boot must be sector 268435455. And here is the error now being generated. If you have a BIOS/Hardware combo that can actually boot from 128GB, you can recompile installboot and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine. Nothing seems to have changed though, as I still run into the booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try... error message at boot. You need to compile 'and friends', in particular a new /boot. And install it. This is done by cd /usr/src/sys/arch/[1386|amd64]/stand make clean make obj make make install /usr/mdec/installboot -v /boot /usr/mdec/biosboot all as root of course. What surprises me is OpenBSD booted fine *before* I had Windows XP, and the ~143G partition was still present. Possibly something else is broken... Nope. We introduced a hard limit of 128GB as the workable lowest common denominator while we research a reliable way to determine when it is safe to go beyond. On one of my recent machines, just to pick an example, the BIOS simply returns all zero's for all I/O attempted past 128GB. We do like to impose draconian new restrictions and debug code early in a release cycle. :-) The lack of a reliable way to safely go beyond 128GB, even with recent BIOSen is sad and no doubt the reason Windows wants the first 100MB or so for its boot, OpenSUSE 11.4 blew up when installed 128GB on a just purchased motherboard, etc. The second target for anyone with a time machine should be the morons who decided BIOS would be enough for anyone. makeactive in menu.lst for grub did not help either (as I had guessed). -Amarendra [...] All grub can do (to my knowledge) is grab and run the OpenBSD /boot program. And if it doesn't work ... Ken
