Re: Weird problem - sound suddenly stops playing

2012-09-01 Thread Joe Gidi
On Sat, September 1, 2012 1:35 am, Tomas Bodzar wrote:
 On Sat, Sep 1, 2012 at 7:11 AM, Joe Gidi j...@entropicblur.com wrote:
 I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in
 /etc/rc.conf
 with the default 'sndiod_flags=' entry. I have working audio from mpd,
 mplayer, and assorted other applications. Everything just works.


 Did you try to run with sndiod -d if there will be something more in
 console?

Thanks for the suggestion. I ran sndiod -d then started playing a song
with mpd. Output looked like this:

snd0.default: rec=0:1 play=0:1 vol=32768 join midi/in midi/out
snd0: recording s16le,0:1,48000
snd0: playing s16le,0:1,48000
snd0: block size is 960 frames, using 9 blocks
mpd0: buffer size = 8820, play = s16le,0:1,44100
starting device

Then the music stopped playing, and I got:

sock: read 40 bytes in 22330us

At that point I tried pausing and restarting the song, which produced:

snd0: device stopped
snd0: closing device
snd0: recording s16le,0:1,48000
snd0: playing s16le,0:1,48000
snd0: block size is 960 frames, using 9 blocks
mpd0: buffer size = 8820, play = s16le,0:1,44100
starting device
snd0: device stopped
snd0: closing device

Though there was no audio actually playing.

--
Joe Gidi
j...@entropicblur.com

You cannot buy skill. -- Ross Seyfried



Re: boot panic with qemu, -current guest on a Linux host

2012-09-01 Thread LEVAI Daniel
On p, aug 31, 2012 at 14:44:32 -0700, Chris Cappuccio wrote:
 somehow, your computer thinks C3_CPUID_HAS_RNG is valid, which would
 mean you are running the via_nano_setup routine, which means your cpu
 model is VIA Nano processor, which is all just wrong. wtf?

Yes, this is definitely not a VIA cpu. Passing phenom or host to qemu's
-cpu option produces the same result (as below). Also, it doesn't matter
if I use bsd or bsd.mp.

 
 LEVAI Daniel [l...@ecentrum.hu] wrote:
[...]
  OpenBSD 5.2-current (GENERIC.MP) #6: Mon Aug 27 20:40:45 MDT 2012
  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
  cpu0: AMD Phenom(tm) II X4 B50 Processor (AuthenticAMD 686-class, 512KB 
  L2 cac
  he) 3.11 GHz
  cpu0: 
  FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
  LUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,FFXSR,3DNOW2,3DNOW,SSE3,CX16,POPCNT,LAHF,CMPLEG,
  SVM,AMCR8,ABM,SSE4A,MASSE,3DNOWP
[...]
  viac3_rnd(d0b025a0,d09e3268,d08f384b,3,4) at viac3_rnd+0x9f
  amd64_errata(d0b025a0,d0b025a0,d0f8,d078eb77,d0b025a0) at 
  amd64_errata+0xb9
  
  cpu_init(d0b025a0,0,2000,0,d0bbbc04) at cpu_init+0x19
  cpu_attach(d164bfc0,d155e400,d0bbbc4c,d03ee29b,d078de30) at cpu_attach+0x297
  config_attach(d164bfc0,d09d45c0,d0bbbc4c,d078cb20,800,0,0,d08f3129,0,1,d09f21c0
  ,100f42,78bfbff) at config_attach+0x1bb
  mpbios_cpu(f51a5a9c,d16737c0,2,1,2) at mpbios_cpu+0x85
  mpbios_scan(d16737c0,d16737c0,d0bbbd60,d03ee29b,0) at mpbios_scan+0x2dc
  config_attach(d164bf80,d09d45a0,d0bbbd60,d0789d30,b) at config_attach+0x1bb
  biosattach(d164bfc0,d164bf80,d0bbbe58,d03ee29b,0) at biosattach+0x517
  config_attach(d164bfc0,d09d4560,d0bbbe58,d05afb60,3000) at 
  config_attach+0x
  1bb
  ddb{0}
  
  
  The host has an AMD Phenom(tm) II X4 B50 Processor.
[...]

Well, running trace in ddb gives me a few more lines, but I doubt it counts:

...
biosattach(d164bfc0,d164bf80,d0bbbe58,d03ee29b,0) at biosattach+0x517
config_attach(d164bfc0,d09d4560,d0bbbe58,d05afb60,3000) at config_attach+0x
1bb
mainbus_attach(0,d164bfc0,0,d09d2020,0) at mainbus_attach+0x4e
config_attach(0,d09d2020,0,0,d0a462c0) at config_attach+0x1bb
config_rootfound(d08f25ac,0,0,d03dea51,0) at config_rootfound+0x46
cpu_configure(d0b025a0,1,1000,cff3f000,1) at cpu_configure+0x29
main(d02004cd,d02004d5,0,0,0) at main+0x3fb

Should I mess around more in ddb?


Daniel

-- 
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F



Re: Weird problem - sound suddenly stops playing

2012-09-01 Thread Alexandre Ratchov
On Sat, Sep 01, 2012 at 01:53:18AM -0400, Joe Gidi wrote:
 On Sat, September 1, 2012 1:35 am, Tomas Bodzar wrote:
  On Sat, Sep 1, 2012 at 7:11 AM, Joe Gidi j...@entropicblur.com wrote:
  I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in
  /etc/rc.conf
  with the default 'sndiod_flags=' entry. I have working audio from mpd,
  mplayer, and assorted other applications. Everything just works.
 
 
  Did you try to run with sndiod -d if there will be something more in
  console?
 
 Thanks for the suggestion. I ran sndiod -d then started playing a song
 with mpd. Output looked like this:
 
 snd0.default: rec=0:1 play=0:1 vol=32768 join midi/in midi/out
 snd0: recording s16le,0:1,48000
 snd0: playing s16le,0:1,48000
 snd0: block size is 960 frames, using 9 blocks
 mpd0: buffer size = 8820, play = s16le,0:1,44100
 starting device
 
 Then the music stopped playing, and I got:
 
 sock: read 40 bytes in 22330us
 

something has stolen the cpu for 22ms, but that's OK; but this is a
strange coincidence though

 At that point I tried pausing and restarting the song, which produced:
 
 snd0: device stopped
 snd0: closing device
 snd0: recording s16le,0:1,48000
 snd0: playing s16le,0:1,48000
 snd0: block size is 960 frames, using 9 blocks
 mpd0: buffer size = 8820, play = s16le,0:1,44100
 starting device
 snd0: device stopped
 snd0: closing device
 
 Though there was no audio actually playing.
 

Could it be a program changing the mixer in the background? Could
you check whether the mixer has changed by comparing mixerctl
output before and after the sound stops?

-- Alexandre



Some probelms configuring dhcpd with iPXE options

2012-09-01 Thread C. L. Martinez
Hi all,

 I am trying to configure dhcpd daemon in a OpenBSD 5.1 host to use
iPXE options for booting vm guests via iscsi. To do this, I have
configured dhcpd.conf with these options:

option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
option ipxe.priority code 1 = signed integer 8;
option ipxe.keep-san code 8 = unsigned integer 8;
option ipxe.skip-san-boot code 9 = unsigned integer 8;
option ipxe.syslogs code 85 = string;
option ipxe.cert code 91 = string;
option ipxe.privkey code 92 = string;
option ipxe.crosscert code 93 = string;
option ipxe.no-pxedhcp code 176 = unsigned integer 8;
option ipxe.bus-id code 177 = string;
option ipxe.bios-drive code 189 = unsigned integer 8;
option ipxe.username code 190 = string;
option ipxe.password code 191 = string;
option ipxe.reverse-username code 192 = string;
option ipxe.reverse-password code 193 = string;
option ipxe.version code 235 = string;
option iscsi-initiator-iqn code 203 = string;
option ipxe.pxeext code 16 = unsigned integer 8;
option ipxe.iscsi code 17 = unsigned integer 8;
option ipxe.aoe code 18 = unsigned integer 8;
option ipxe.http code 19 = unsigned integer 8;
option ipxe.https code 20 = unsigned integer 8;
option ipxe.tftp code 21 = unsigned integer 8;
option ipxe.ftp code 22 = unsigned integer 8;
option ipxe.dns code 23 = unsigned integer 8;
option ipxe.bzimage code 24 = unsigned integer 8;
option ipxe.multiboot code 25 = unsigned integer 8;
option ipxe.slam code 26 = unsigned integer 8;
option ipxe.srp code 27 = unsigned integer 8;
option ipxe.nbi code 32 = unsigned integer 8;
option ipxe.pxe code 33 = unsigned integer 8;
option ipxe.elf code 34 = unsigned integer 8;
option ipxe.comboot code 35 = unsigned integer 8;
option ipxe.efi code 36 = unsigned integer 8;
option ipxe.fcoe code 37 = unsigned integer 8;

 .. but when I launch /etc/rc.d/dhcpd start, a lot of errors appears
(one for every option configured in dhcpd.conf):

dhcpd[11205]: /etc/dhcpd.conf line 26: no option named space
dhcpd[11205]: option space ipxe;
dhcpd[11205]:^
dhcpd[11205]: /etc/dhcpd.conf line 27: no option named ipxe-encap-opts
dhcpd[11205]: option ipxe-encap-opts code
dhcpd[11205]:^
dhcpd[11205]: /etc/dhcpd.conf line 28: no vendor named ipxe.
dhcpd[11205]: option ipxe.priority
dhcpd[11205]: ^
dhcpd[11205]: /etc/dhcpd.conf line 29: no vendor named ipxe.
dhcpd[11205]: option ipxe.keep-san
dhcpd[11205]: ^

..

Same configuration works for RHEL/CentOS 6.x dhcpd hosts ... What am I
doing wrong??

Thanks.



Reminder: friends invited you to join Select2gether.

2012-09-01 Thread anna_honn
Dear Misc,

 

anna_honn sent a request to add you as a contact on Select2gether.
 

Just a friendly reminder to join anna_honn's network, follow the link below:

Join anna_honn's Network

 

Thanks,
anna_honn

You can remove yourself from anna_honn's network at any time.
If you do not wish to receive this type of email from Select2gether in the
future, please click here to unsubscribe.
Select2gether, 555 Bryant st #444, Palo Alto, CA, 94301

[demime 1.01d removed an attachment of type image/png which had a name of 
logo-s2g.png]

[demime 1.01d removed an attachment of type image/jpeg which had a name of 
avatar_32c6d5aa73efa9095d584973683c086e.jpg]



Re: My first macppc install not going well.

2012-09-01 Thread Kenneth R Westerback
When you try the install, choose (S)hell. At the prompt try

dd if=/dev/zero of=/dev/rwd0c bs=1m count=1

You may have some old HFS partition table fragments lying around.

 Ken

On Sat, Sep 01, 2012 at 01:51:43PM +0930, David Walker wrote:
 Hi.
 
 I got an iBook G4 and I'm having issues.
 
 I'm going for an MBR scheme using the whole disk but I'm not sure
 fdisk is working according to the installation instructions but I
 might have a borked disk ...
 Here's what I see:
 
   Available disks are: wd0.
   Which one is the root disk? (or 'done') [wd0] Enter
   Use DUIDs rather than device names in fstab? [yes] n
   Use HFS or MBR partition table? [HFS] MBR
 
 Here I get read failed repeated 8 times, 3 not HFS, a print out of
 the HFS style partitions.
 The read failed are obviously cause for concern but I don't know if
 that's from trying to read some previous Apple stuff, something
 in-correct that's correctable by proceeding with a write, something
 that's stopping the rest of the install or whatever.
 
   Are you *sure* you want an MBR partition table on wd0? [no] y
   Disk: wd0   geometry: 116280/16/63 [117210240 Sectors]
   Offset: 0   Signature: 0xAA55
   Starting Ending LBA Info:
#: id  C   H   S -  C   H   S [   start:size ]
   
 ---
   *0: 06 0   0   2 -2   0  33 [  1:2048 ] DOS  32MB
1: 00 0   0   0 -0   00 [  0: 0 ] unused
2: 00 0   0   0 -0   00 [  0: 0 ] unused
3: A6 4   1  2 - 116279 15 63 [ 4096:  117206144 ] OpenBSD
   Use (W)hole disk, use the (O)penBSD area, or (E)dit the MBR? [OpenBSD] w
 
 I guess the reason for the DOS and OpenBSD partitions is that I've
 been through this a few times.
 I've tried using the whole disk or the OpenBSD area with as far as I
 can see the same result except using the whole disk re-creates the DOS
 partition.
 
   Creating a 1MB DOS partition and an OpenBSD partition for the rest
 of wd0...done.
   /dev/rwd0i: 116720008 sectors in 15490001 FAT32 clusters (4096 
 bytes/cluster)
   bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=63 hds=16 hid=262208
 bsec=116948016 bspf=113985 rdcl=2 infs=1 bkbs=2
   The auto-allocated layout for wd0 is:
   #size   offset  fstype [fsize bsize  cpg]
 a:  128.0M  64  4.2BSD   2048 163841 # /
 c: 57231.6M 0  unused
 i:  57103.5M 262208  HFS
   Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] c
 
 Here I've tried A and C but I only seem to be able to use 128MB of disk space.
 For instance using A ...
   /dev/rwd0a: 128.0MB in 262144 sectors of 512 bytes
   4 cylinder groups of 32.00MB, 2048 blocks, 4096 inodes each
   /dev/wd0a on /mnt type ffs (rw, asynchronous, local)
 
 I've tried deleting i and adding b and so on but the a is using the
 entire 128MB ...
 If I delete a which as far as I can tell is not what I should be
 doing, I can add 128MB at most ...
 
 There's not enough room to install bsd and etc so I've tried
 installing bsd.rd only but when I try ...
 boot hd:,ofwboot /bsd.rd
 ... at the OF prompt I get:
 Warning: sector size mismatch! can't OPEN: hd:,ofwboot
 Cant open device or file
 
 Any advice appreciated.
 
 Best wishes.



Re: Some probelms configuring dhcpd with iPXE options

2012-09-01 Thread Stefan Sperling
On Sat, Sep 01, 2012 at 12:22:17PM +0200, C. L. Martinez wrote:
  .. but when I launch /etc/rc.d/dhcpd start, a lot of errors appears
 (one for every option configured in dhcpd.conf):
 
 dhcpd[11205]: /etc/dhcpd.conf line 26: no option named space
 dhcpd[11205]: option space ipxe;
 dhcpd[11205]:^
 dhcpd[11205]: /etc/dhcpd.conf line 27: no option named ipxe-encap-opts
 dhcpd[11205]: option ipxe-encap-opts code
 dhcpd[11205]:^
 dhcpd[11205]: /etc/dhcpd.conf line 28: no vendor named ipxe.
 dhcpd[11205]: option ipxe.priority
 dhcpd[11205]: ^
 dhcpd[11205]: /etc/dhcpd.conf line 29: no vendor named ipxe.
 dhcpd[11205]: option ipxe.keep-san
 dhcpd[11205]: ^
 
 ..
 
 Same configuration works for RHEL/CentOS 6.x dhcpd hosts ... What am I
 doing wrong??

You probably need to use the isc-dhcp-server package for this,
not dhcpd from the base system. See /usr/ports/net/isc-dhcp

Searching the archives you can find posts like this one:
http://marc.info/?l=openbsd-miscm=134082556722850w=2



Re: Some probelms configuring dhcpd with iPXE options

2012-09-01 Thread Kenneth R Westerback
On Sat, Sep 01, 2012 at 12:22:17PM +0200, C. L. Martinez wrote:
 Hi all,
 
  I am trying to configure dhcpd daemon in a OpenBSD 5.1 host to use
 iPXE options for booting vm guests via iscsi. To do this, I have
 configured dhcpd.conf with these options:
 
 option space ipxe;
 option ipxe-encap-opts code 175 = encapsulate ipxe;
 option ipxe.priority code 1 = signed integer 8;
 option ipxe.keep-san code 8 = unsigned integer 8;
 option ipxe.skip-san-boot code 9 = unsigned integer 8;
 option ipxe.syslogs code 85 = string;
 option ipxe.cert code 91 = string;
 option ipxe.privkey code 92 = string;
 option ipxe.crosscert code 93 = string;
 option ipxe.no-pxedhcp code 176 = unsigned integer 8;
 option ipxe.bus-id code 177 = string;
 option ipxe.bios-drive code 189 = unsigned integer 8;
 option ipxe.username code 190 = string;
 option ipxe.password code 191 = string;
 option ipxe.reverse-username code 192 = string;
 option ipxe.reverse-password code 193 = string;
 option ipxe.version code 235 = string;
 option iscsi-initiator-iqn code 203 = string;
 option ipxe.pxeext code 16 = unsigned integer 8;
 option ipxe.iscsi code 17 = unsigned integer 8;
 option ipxe.aoe code 18 = unsigned integer 8;
 option ipxe.http code 19 = unsigned integer 8;
 option ipxe.https code 20 = unsigned integer 8;
 option ipxe.tftp code 21 = unsigned integer 8;
 option ipxe.ftp code 22 = unsigned integer 8;
 option ipxe.dns code 23 = unsigned integer 8;
 option ipxe.bzimage code 24 = unsigned integer 8;
 option ipxe.multiboot code 25 = unsigned integer 8;
 option ipxe.slam code 26 = unsigned integer 8;
 option ipxe.srp code 27 = unsigned integer 8;
 option ipxe.nbi code 32 = unsigned integer 8;
 option ipxe.pxe code 33 = unsigned integer 8;
 option ipxe.elf code 34 = unsigned integer 8;
 option ipxe.comboot code 35 = unsigned integer 8;
 option ipxe.efi code 36 = unsigned integer 8;
 option ipxe.fcoe code 37 = unsigned integer 8;
 
  .. but when I launch /etc/rc.d/dhcpd start, a lot of errors appears
 (one for every option configured in dhcpd.conf):
 
 dhcpd[11205]: /etc/dhcpd.conf line 26: no option named space
 dhcpd[11205]: option space ipxe;
 dhcpd[11205]:^
 dhcpd[11205]: /etc/dhcpd.conf line 27: no option named ipxe-encap-opts
 dhcpd[11205]: option ipxe-encap-opts code
 dhcpd[11205]:^
 dhcpd[11205]: /etc/dhcpd.conf line 28: no vendor named ipxe.
 dhcpd[11205]: option ipxe.priority
 dhcpd[11205]: ^
 dhcpd[11205]: /etc/dhcpd.conf line 29: no vendor named ipxe.
 dhcpd[11205]: option ipxe.keep-san
 dhcpd[11205]: ^
 
 ..
 
 Same configuration works for RHEL/CentOS 6.x dhcpd hosts ... What am I
 doing wrong??
 
 Thanks.
 

The dhcpd in base knows nothing about ipxe. Or 'space'. It is nowhere near
in sync with ISC. You might want to use the ISC dhcpd in ports, net/isc-dhcp,
or the package for your arch.

 Ken



Re: My first macppc install not going well.

2012-09-01 Thread David Walker
Now I get ...
MBR has invalid signature; not showing it.
... followed by everything working.
I've installed and successfully booted from HDD ...

Ken, you rock.

On 01/09/2012, Kenneth R Westerback kwesterb...@rogers.com wrote:
 When you try the install, choose (S)hell. At the prompt try

 dd if=/dev/zero of=/dev/rwd0c bs=1m count=1

 You may have some old HFS partition table fragments lying around.

  Ken

 On Sat, Sep 01, 2012 at 01:51:43PM +0930, David Walker wrote:
 Hi.

 I got an iBook G4 and I'm having issues.

 I'm going for an MBR scheme using the whole disk but I'm not sure
 fdisk is working according to the installation instructions but I
 might have a borked disk ...
 Here's what I see:

   Available disks are: wd0.
   Which one is the root disk? (or 'done') [wd0] Enter
   Use DUIDs rather than device names in fstab? [yes] n
   Use HFS or MBR partition table? [HFS] MBR

 Here I get read failed repeated 8 times, 3 not HFS, a print out of
 the HFS style partitions.
 The read failed are obviously cause for concern but I don't know if
 that's from trying to read some previous Apple stuff, something
 in-correct that's correctable by proceeding with a write, something
 that's stopping the rest of the install or whatever.

   Are you *sure* you want an MBR partition table on wd0? [no] y
   Disk: wd0   geometry: 116280/16/63 [117210240 Sectors]
   Offset: 0   Signature: 0xAA55
   Starting Ending LBA Info:
#: id  C   H   S -  C   H   S [   start:size ]

 ---
   *0: 06 0   0   2 -2   0  33 [  1:2048 ] DOS 
 32MB
1: 00 0   0   0 -0   00 [  0: 0 ]
 unused
2: 00 0   0   0 -0   00 [  0: 0 ]
 unused
3: A6 4   1  2 - 116279 15 63 [ 4096:  117206144 ] OpenBSD
   Use (W)hole disk, use the (O)penBSD area, or (E)dit the MBR? [OpenBSD]
 w

 I guess the reason for the DOS and OpenBSD partitions is that I've
 been through this a few times.
 I've tried using the whole disk or the OpenBSD area with as far as I
 can see the same result except using the whole disk re-creates the DOS
 partition.

   Creating a 1MB DOS partition and an OpenBSD partition for the rest
 of wd0...done.
   /dev/rwd0i: 116720008 sectors in 15490001 FAT32 clusters (4096
 bytes/cluster)
   bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=63 hds=16 hid=262208
 bsec=116948016 bspf=113985 rdcl=2 infs=1 bkbs=2
   The auto-allocated layout for wd0 is:
   #size   offset  fstype [fsize bsize  cpg]
 a:  128.0M  64  4.2BSD   2048 163841 # /
 c: 57231.6M 0  unused
 i:  57103.5M 262208  HFS
   Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] c

 Here I've tried A and C but I only seem to be able to use 128MB of disk
 space.
 For instance using A ...
   /dev/rwd0a: 128.0MB in 262144 sectors of 512 bytes
   4 cylinder groups of 32.00MB, 2048 blocks, 4096 inodes each
   /dev/wd0a on /mnt type ffs (rw, asynchronous, local)

 I've tried deleting i and adding b and so on but the a is using the
 entire 128MB ...
 If I delete a which as far as I can tell is not what I should be
 doing, I can add 128MB at most ...

 There's not enough room to install bsd and etc so I've tried
 installing bsd.rd only but when I try ...
 boot hd:,ofwboot /bsd.rd
 ... at the OF prompt I get:
 Warning: sector size mismatch! can't OPEN: hd:,ofwboot
 Cant open device or file

 Any advice appreciated.

 Best wishes.



Not receiving messages from the list

2012-09-01 Thread llemike...@aol.com

Would anybody be able to explain why
I am not regularly receiving messages
from misc?
I haven't received anything since
22 August 2012.
Comments much appreciated.
Mike



: Hotel Tanti Spa Resort : Promo Primavera 3 Noches - Fin de semana largo : Disfrute de las sierras de Córdoba :

2012-09-01 Thread Marketing
No puedes visualizar las imágenes? Versión online.

Hotel Tanti - Spa  Resort Promoción 2, 4 y 6 Noches - Septiembre
Aboná en 3 cuotas sin interés con tarjetas de crédito
Disfrute de las Sierras de Córdoba
Un cálido Hotel Resort con 24 comfortables habitaciones y SPA

¡Aviso muy importante!
Si viaja en auto, no olvide que las rutas y autopistas tienen radares.
Encienda las luces bajas y utilice cinturones delanteros y traseros.

En caso de no querer recibir más estas comunicaciones, responda este
correo con asunto REMOVER.



Re: Weird problem - sound suddenly stops playing

2012-09-01 Thread Joe Gidi
On Sat, September 1, 2012 4:59 am, Alexandre Ratchov wrote:
 On Sat, Sep 01, 2012 at 01:53:18AM -0400, Joe Gidi wrote:
 On Sat, September 1, 2012 1:35 am, Tomas Bodzar wrote:
  On Sat, Sep 1, 2012 at 7:11 AM, Joe Gidi j...@entropicblur.com wrote:
  I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in
  /etc/rc.conf
  with the default 'sndiod_flags=' entry. I have working audio from
 mpd,
  mplayer, and assorted other applications. Everything just works.
 
 
  Did you try to run with sndiod -d if there will be something more in
  console?

 Thanks for the suggestion. I ran sndiod -d then started playing a song
 with mpd. Output looked like this:

 snd0.default: rec=0:1 play=0:1 vol=32768 join midi/in midi/out
 snd0: recording s16le,0:1,48000
 snd0: playing s16le,0:1,48000
 snd0: block size is 960 frames, using 9 blocks
 mpd0: buffer size = 8820, play = s16le,0:1,44100
 starting device

 Then the music stopped playing, and I got:

 sock: read 40 bytes in 22330us


 something has stolen the cpu for 22ms, but that's OK; but this is a
 strange coincidence though

 At that point I tried pausing and restarting the song, which produced:

 snd0: device stopped
 snd0: closing device
 snd0: recording s16le,0:1,48000
 snd0: playing s16le,0:1,48000
 snd0: block size is 960 frames, using 9 blocks
 mpd0: buffer size = 8820, play = s16le,0:1,44100
 starting device
 snd0: device stopped
 snd0: closing device

 Though there was no audio actually playing.


 Could it be a program changing the mixer in the background? Could
 you check whether the mixer has changed by comparing mixerctl
 output before and after the sound stops?

 -- Alexandre

I just tried this, the mixerctl output is unchanged.

Thanks,

--
Joe Gidi
j...@entropicblur.com

You cannot buy skill. -- Ross Seyfried



Bad malloc (?)

2012-09-01 Thread rustyBSD
Hi,
in /usr/src/sbin/scsi/scsi.c line 225, why
is the malloc not checked ? ... If it fails,
it overflows, no ?



HDMI and radeon

2012-09-01 Thread Christiano F. Haesbaert
Is anyone using HDMI with a radeon card ? Does it work ? Not sure if
this is transparent to software ?

I got a new monitor and not should if I should buy a HDMI or DVI cable.



Re: Bad malloc (?)

2012-09-01 Thread Kenneth R Westerback
On Sat, Sep 01, 2012 at 07:19:25PM +0200, rustyBSD wrote:
 Hi,
 in /usr/src/sbin/scsi/scsi.c line 225, why
 is the malloc not checked ? ... If it fails,
 it overflows, no ?
 

Crufty old code. Feel free to submit an actual diff! Note there seem to
be 2 non-checked malloc returns.

 Ken



Re: problem setting inet6 route

2012-09-01 Thread Remi Locherer
On Fri, Aug 31, 2012 at 09:01:44PM +0200, Joakim Aronius wrote:
 * Remi Locherer (remi.loche...@relo.ch) wrote:
  Hi
  
  I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also
  provides IPv6 but somehow with a strange setup. I got something like the 
  following from them:
  
  Gateway Address: 2001:db8:1:1110::1/64
  Subnet I can use: 2001:db8:1:/64
 
 You could begin with actually getting real IPv6 addresses. 2001:DB8::/32 is a 
 reserved prefix for use in documentation. http://tools.ietf.org/html/rfc3849
 

Do you really think that these addresses are the ones I got from the
provider?



Re: HDMI and radeon

2012-09-01 Thread Stefan Sperling
On Sat, Sep 01, 2012 at 07:57:29PM +0200, Christiano F. Haesbaert wrote:
 Is anyone using HDMI with a radeon card ? Does it work ? Not sure if
 this is transparent to software ?
 
 I got a new monitor and not should if I should buy a HDMI or DVI cable.

I've got a DVI monitor hooked up via an HDMI cable + adapter
and it works well.

vga1 at pci1 dev 5 function 0 ATI Radeon HD 4200 rev 0x00

$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
VGA-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
   1280x1024  60.0*+   75.0  
   1024x768   75.0 60.0  
   800x60075.0 60.3  
   640x48075.0 59.9  
   720x40070.1  



Re: HDMI and radeon

2012-09-01 Thread Robert
On Sat, 1 Sep 2012 19:57:29 +0200
Christiano F. Haesbaert haesba...@haesbaert.org wrote:

 Is anyone using HDMI with a radeon card ? Does it work ? Not sure if
 this is transparent to software ?
 
 I got a new monitor and not should if I should buy a HDMI or DVI cable.
 

Hi,

I've got a dual screen setup, one via VGA and the other via HDMI (both
1920x0180). Works nicely.

Keep this in mind if you want DRI etc...
http://marc.info/?l=openbsd-miscm=125007312810120

kind regards,
Robert


dmesg:
vga1 at pci1 dev 0 function 0 ATI Radeon HD 3650 rev 0x00

xrandr:
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 3840 x 1080
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 connected 1920x1080+1920+0 (normal left inverted right x axis y
axis) 521mm x 293mm
   m1920x1080 60.0 +
   1920x1080  60.0*+   60.0  
   1680x1050  60.0  
   1600x900   60.0  
   1280x1024  75.0 60.0  
   1280x960   60.0  
   1152x864   75.0  
   1280x720   60.0  
   1152x720   60.0  
   1024x768   75.0 60.0  
   832x62474.6  
   800x60075.0 60.3  
   640x48075.0 59.9  
   720x40070.1  
DVI-0 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 521mm x 293mm 
   m1920x1080 60.0 +
   1920x1080  60.0*+   60.0  
   1680x1050  59.9  
   1600x900   60.0  
   1280x1024  75.0 60.0  
   1280x960   60.0  
   1152x864   75.0  
   1280x720   60.0  
   1152x720   60.0  
   1024x768   75.0 60.0  
   832x62474.6  
   800x60075.0 60.3  
   640x48075.0 59.9  
   720x40070.1  



Re: problem setting inet6 route

2012-09-01 Thread Joakim Aronius
* Remi Locherer (remi.loche...@relo.ch) wrote:
 On Fri, Aug 31, 2012 at 09:01:44PM +0200, Joakim Aronius wrote:
  * Remi Locherer (remi.loche...@relo.ch) wrote:
   Hi
   
   I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also
   provides IPv6 but somehow with a strange setup. I got something like the 
   following from them:
   
   Gateway Address: 2001:db8:1:1110::1/64
   Subnet I can use: 2001:db8:1:/64
  
  You could begin with actually getting real IPv6 addresses. 2001:DB8::/32 is 
  a reserved prefix for use in documentation. 
  http://tools.ietf.org/html/rfc3849
  
 
 Do you really think that these addresses are the ones I got from the
 provider?

Well, with that kind of question and miss-typed address i figured you did not 
have a clue, maybe I was wrong, my bad. 
But I do not believe in keeping IP addresses secret, it doesn't help. 
Good luck with IPv6!
/J



Re: problem setting inet6 route

2012-09-01 Thread Philip Guenther
On Fri, Aug 31, 2012 at 7:52 AM, Remi Locherer remi.loche...@relo.ch wrote:
 On Fri, Aug 31, 2012 at 09:47:39AM -0400, Simon Perreault wrote:
 Le 2012-08-31 03:19, Remi Locherer a ?crit :
 I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also
 provides IPv6 but somehow with a strange setup. I got something like the
 following from them:
 
 Gateway Address: 2001:db8:1:1110::1/64
 Subnet I can use: 2001:db8:1:/64


 This works. But I have to figure out (ask Hetzner) if I'm the only
 customer they use 2001:db8:1:1110::/64 (I think so).

I think the question I would have asked them is
What does your box (2001:db8:1:1110::1) need in order for it to
figure out how to send packets for my network (2001:db8:1:::/64)
to my box?  Does my box need to have a specific address or send
out router advertisements?

I.e., how is is their box going to know get the ethernet address of
your box so that it can send the packets to it?


Philip Guenther



Re: HDMI and radeon

2012-09-01 Thread Christiano F. Haesbaert
Thank you all, that should be enough :-)



Re: Notebook dmesg gathering. Developers, what info do you want?

2012-09-01 Thread Dave Anderson
On Sat, 25 Aug 2012, Dave Anderson wrote:

If there's no interest in this info, I won't burn an afternoon
collecting it.  If there is interest, answers to my questions would be
useful.

Dave

A year or so ago, as part of selecting a notebook to buy, I gathered
dmesg info from all of the notebooks I could find in local stores
(booting from and saving data to a USB stick) and sent it to
dm...@openbsd.org as well as using it myself.  Since I expect that it
would be useful to the developers to have this info for the current crop
of notebooks, I plan to do another data-gathering session sometime in
the next few weeks.  I'll be using an amd64 snapshot and, as FAQ 4.10
requests, will gather both 'dmesg' and 'sysctl hw.sensors' output using
both the sp and mp kernels for each system.

Since the data collection will be scripted it will be easy to also
gather other information; pcidump, usbdevs and acpidump come to mind.
What would be useful for the developers?  I've got a store which has
several dozen demo notebooks and will let me gather data from them, but
there won't be an opportunity to go back -- I need to get all of the
useful info at once.

So, my questions to the developers:

1) Does it matter which amd64 snapshot I use?  Are there any recent or
forthcoming ones which are especially good or bad for this purpose?

2) What additional information should I collect?  Exact commands and
options, please.  I don't mind installing tools which aren't in base,
but the output needs to go to, or be able to be redirected to, a file.

3) Other than the dmesg/sensor info which will go to dm...@openbsd.org,
where should I send the additional info?  If there's no suitable place,
I can just keep it around and let anyone who needs it ask me for it.

   Dave

-- 
Dave Anderson
d...@daveanderson.com



Re: Notebook dmesg gathering. Developers, what info do you want?

2012-09-01 Thread Ted Unangst
On Sat, Sep 01, 2012 at 17:46, Dave Anderson wrote:
 On Sat, 25 Aug 2012, Dave Anderson wrote:
 
 If there's no interest in this info, I won't burn an afternoon
 collecting it.  If there is interest, answers to my questions would be
 useful.

It's probably not that useful.  In the event the hardware doesn't
work, you're not in a position to test fixes.  Unless you were
planning on buying a sample for a developer. :)

The dmesg collection is interesting because it reveals what hardware
people are using.  Filling it up with examples of hardware that people
are not using is less interesting.

Perhaps just run the tests, see which machines fail to boot or don't
have any disks or network detected, and write an email to misc so
people know not to buy that hardware.