Re: android sdk on openbsd
That worth publishing at undeadly.org, I think
16.02.2012 4:57 POLXZOWATELX frantisek holop min...@obiit.org NAPISAL:
hi there,
i wanted to try at least a hello world on android.
so i installed some linux on a usb stick to use as a
mobile development environment. it went rather well,
using the official hello world tutorial, eclipse and ADT.
but eclipse is not my thing really and as many components
needed for android development run on openbsd, and there
is linux emulation (must be on for this) i started
wondering how far could i get on openbsd before using
linux as a crutch.
turns out, looong way.
the development flow is basically: write code, make apk,
install apk on phone/emulator, run apk, (get rich).
first things first, had to cheat to get the SDK. the
initial download android-sdk_r16-linux.tgz contains
only scaffolding to get the real thing. it is in java,
but unfortunately swt (part of eclipse) from ports is
too old and i couldnt use the GUI or install ADT (Android
Development Tools).
TODO: try to update the eclipse port.
but as i already had all of it on the linux stick,
i simply rsync-ed it over under ~/adroid-sdk
$ ls -1 android-sdk
SDK Readme.txt
add-ons/
docs/
platform-tools/
platforms/
samples/
sources/
system-images/
temp/
tools/
$ sudo pkg_add jdk apache-ant
$ export
PATH=$PATH:/usr/local/jdk-1.7.0/bin:$HOME/android-sdk/tools:$HOME/adroid-sdk/
platform-tools
$ java -version
openjdk version 1.7.0
OpenJDK Runtime Environment (build 1.7.0-b00)
OpenJDK Server VM (build 21.0-b17, mixed mode)
apply the attached patch to dx.
these are the API's i have installed using linux:
$ android list target | grep ^id
id: 1 or android-3
id: 2 or Google Inc.:Google APIs:3
id: 3 or android-7
id: 4 or Google Inc.:Google APIs:7
id: 5 or android-15
id: 6 or Google Inc.:Google APIs:15
i will use id 3 (Android 2.1.x Eclair)
HelloAndroid.java is also attached
$ cd src/android/hello
~/src/android/hello$ android create project -t 3 -n HelloPuffy -p . -k
com.puffy.hello -a HelloPuffy
~/src/android/hello$ cp ~/HelloAndroid.java src/com/puffy/hello/
~/src/android/hello$ ant debug
if i did not leave out something, the output should finish with:
BUILD SUCCESSFUL
Total time: 7 seconds
for now i upload the apk files using ftp (swiftp on android).
http://obiit.org/f/hello.png
obviously, this is a suboptimal solution, and there is the emulator...
let's see how far that goes.
~/src/android/hello$ android create avd -n puffy_avd -t 3
Auto-selecting single ABI armeabi
Android 2.1 is a basic Android platform.
Do you wish to create a custom hardware profile [no]
Created AVD 'puffy_avd' based on Android 2.1, ARM (armeabi) processor,
with the following hardware config:
hw.lcd.density=240
vm.heapSize=24
unfortunately 'emulator' uses /proc to determine
it's own path, so we need to trick it:
~/src/android/hello$ sudo ln -s ~/android-sdk/tools/emulator /proc/self/exe
~/src/android/hello$ emulator -avd puffy_avd
emulator: ERROR: _camera_device_open: Cannot open camera device
'/dev/video0': No such device or address
emulator: warning: opening audio input failed
emulator: WARNING: Unable to create sensors port: Connection refused
masaka! stupefaction
http://obiit.org/f/android-emulator-on-openbsd.jpg
http://obiit.org/f/android-emulator-on-openbsd2.jpg
and its fast compared to the linux stick. just wow.
now the bad news. adb does not work.
i have asked about it some time ago on ports@
as having a native adb just by itself would be
great to push apk's, shell, root, etc.
http://marc.info/?l=openbsd-miscm=131809077812364w=2
some responses indicated it's already work in progress.
TODO: get adb to work
adb source: https://github.com/android/platform_system_core
so this is it, perhaps because i started out with zero
expectations, this is a massive happy end.
of course, hello world is just that. it remains
to be seen if more complicated projects can be
compiled.
-f
--
most days the only good thing on tv is the vase.
--- android-sdk/platform-tools/dx.orig Wed Feb 15 21:42:04 2012
+++ android-sdk/platform-tools/dx Tue Feb 14 21:29:26 2012
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/bin/sh
#
# Copyright (C) 2007 The Android Open Source Project
#
@@ -56,6 +56,7 @@
# By default, give dx a max heap size of 1 gig. This can be overridden
# by using a -J option (see below).
defaultMx=-Xmx1024M
+defaultMx=-Xmx512M
# The following will extract any initial parameters of the form
# -Jstuff from the command line and pass them to the Java
package com.puffy.hello;
import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;
public class HelloPuffy extends Activity
{
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
Re : Re : vpn isakmpd ipsec, one side with only one interface
Wesley, You might have misunderstood me. The ssh is going inside the ipsec vpn tunnel which is between Openbsd and RemoteFW Openbsd rl0 - IPSec - RemoteFW - LAN 2 - SomeDevice With this topology as a reminder Openbsd rl0 - LAN1 - Router - Internet - RemoteFW - LAN 2 - SomeDevice De : Wesley M. open...@e-solutions.re @ : Mik J mikyde...@yahoo.fr Cc : misc@openbsd.org Envoyi le : Vendredi 17 fivrier 2012 5h45 Objet : Re: Re : vpn isakmpd ipsec, one side with only one interface I know ssh works also very well. But the company has requierements : ipsec vpn with specific phase 1 and 2... Wesley. On Thu, 16 Feb 2012 19:18:09 + (GMT), Mik J mikyde...@yahoo.fr wrote: Hello, I have this configuration working without any bridge. Openbsd rl0 - LAN1 - Router - Internet - RemoteFW - LAN 2 - SomeDevice My PC is connected to a LAN1 switch, and it's able to ssh SomeDevice. As you can see my OpenBSD has just one interface and the VPN is mounted between OpenBSD and RemoteFW. - Mail original - De : Wesley M. open...@e-solutions.re @ : Markus Wernig liste...@wernig.net Cc : misc@openbsd.org Envoyi le : Jeudi 16 fivrier 2012 15h59 Objet : Re: vpn isakmpd ipsec, one side with only one interface I have it working ;-) What i have done : Create a vether0 with : inet 172.17.2.21 255.255.255.0 Create a bridge0, add to it vether0 and the physical card... PF : filter the bridge Create the vpn, i can reach the ftp :-) Pretty cool Thank's to vether !! Cheers, Wesley MOUEDINE ASSABY On Thu, 16 Feb 2012 14:03:54 +0100, Markus Wernig liste...@wernig.net wrote: Hi I'm not sure if this will work, but you could try creating a loopback interface (lo2) on FWC with the IP address that the FTP server should be reachable on and then set up a regular VPN between FWA and FWC just for that one IP address: ike esp from 172.17.2.21/32 to 192.168.0.0/24 peer ip_fwA ... Then tell the FTP server to listen on the IP of the lo2 interface (172.17.2.21?) /m On 02/13/12 14:43, Wesley M. wrote: o;?Hi, I was using ipsec vpn between 2 OpenBSD Gateway. It worked very well. Here : ---rl0---[fwA]---rl1(internet)-sis1---[fwB with ftpd]---sis0--- Now we remove ftp services from fwB and put it on an other machine fwC with an internet connection (only one network card). is it possible to keep a vpn online from fwA and fwC, and so computersA can reach again ftp using vpn (provided by fwC). Perhaps i need to use vether on fwC so briged pf ? Here the old ipsec.conf from fwB: ike esp from 172.17.2.0/24 to 192.168.0.0/24 peer ip_fwA main auth hmac-sha1 enc aes-256 group modp1024 quick auth hmac-sha1 enc aes-256 group modp1024 psk demopassword My idea on fwC : add verther0 with : inet 172.17.2.21 255.255.255.0
when re-install how to make leave some partitions untouched simple
http://www.openbsd.org/faq/faq4.html
says
Install: load OpenBSD onto the system, overwriting whatever may have been
there.
Note that it is possible to leave some partitions untouched in this process,
such as a /home,
but otherwise, assume everything else is overwritten.
NOTE for re-installers: The new installer will not clear your old disklabel if
you chose (C)ustom Layout,
but you will need to re-specify each mount point using the 'm' option in
disklabel(8).
when re-install OpenBSD, if we want to keep original /home's data, are
following steps the key point?
1) let the space belong to original /home partition untouched.
2) not set /home mount point, add /home to /etc/fstab after install
If I have more than one partitions to leave untouched, to save more steps
time,
I choose (E)dit auto layout rather than (C)ustom Layout#,delete some
partitions, add some partitions carefully and leave mount point untouched.
the steps are not simple and error-prone, should we improve the installer ?
before the step Use (A)uto layout, (E)dit auto layout, or create (C)ustom
layout? [a]
we add some step, for example:
Keep some partitions untouched? [yes] Enter
Partitions' mount point? ('?' for list) [/home] ## Note that multiple mount
point can be listed, separated by spaces.
...
Re: when re-install how to make leave some partitions untouched simple
On 2012-02-18, f5b f...@163.com wrote:
when re-install OpenBSD, if we want to keep original /home's data, are
following steps the key point?
1) let the space belong to original /home partition untouched.
2) not set /home mount point, add /home to /etc/fstab after install
yes.
If I have more than one partitions to leave untouched, to save more steps
time,
I choose (E)dit auto layout rather than (C)ustom Layout#,delete some
partitions, add some partitions carefully and leave mount point untouched.
the steps are not simple and error-prone, should we improve the installer ?
You are assuming that 1) the disklabel was previously done by using auto
layout and wasn't edited, and 2) the disklabel command in the new install
kernel uses the same partition sizes and layout as the command used for the
previous installation. This is not a safe assumption.
before the step Use (A)uto layout, (E)dit auto layout, or create (C)ustom
layout? [a]
we add some step, for example:
Keep some partitions untouched? [yes] Enter
Partitions' mount point? ('?' for list) [/home] ## Note that multiple mount
point can be listed, separated by spaces.
Having this in the installer would be blessing something dangerous.
IMHO: if you want to keep data do an *upgrade* not an *install*.
For anything else use dump/restore.
Re: Is fdisk partition a must for a non-system disk on i386
On Thu, 16 Feb 2012, Stuart Henderson wrote: On 2012-02-15, David Vasek va...@fido.cz wrote: In contrast, Marco, as the author of softraid(4), says the opposite about use of fdisk, even on the physical disks. And what he says is more recent than the example in the softraid(4) man page. http://marc.info/?l=openbsd-miscm=128847054226289w=2 My thought is that MBR partition (DOS partition) is only needed for compatibility with other OS's in case they come in touch with the disk. And probability of such encounter in case of softraid disks and vnd's is... quite low at best. Not certain but isn't the fdisk partition needed in order that you can boot from them? (Bootable softraid appeared after that post, of course). Don't know and can't check it currently. But wouldn't it be better if all OpenBSD platforms are consistent except the situations where a difference from the rest is enforced by the platform as such? Regards, David
Re: SSH Mastery -- New book by Michal Lucas!
On a personal level, I don't care. Just get it somehow. ;-) I said I wasn't going to follow up here, but given the flood of emails, I'd best answer this one en masse. About 100,000 rough words exist for Absolute OpenBSD 2nd Ed. I will announce on my blog when I need community reviewers. I put random details out on Twitter, with hashtags #absoluteopenbsd or #ao2e. ==ml On Sat, Feb 18, 2012 at 10:49:53AM +0800, Alan Cheng wrote: As much as I want a printed copy, I just ordered an electronic copy on smashwords.com -- the int'l shipping cost, which is usually higher than the book itself, can be put to better use, like a donation to the project. thanks ml. Alan On Sat, Feb 18, 2012 at 9:42 AM, Michael W. Lucas mwlu...@blackhelicopters.org wrote: YES! Now I can tell people where they can pre-order print. And they will stop bugging me. ;-) Seriously, I'm delighted to be able to do this. I'm giving the books to the OpenBSD project at my cost. I expect them to use the proceeds well, on barbeque and beer. Maybe even some code. You'll notice that the OpenBSD folks are charging cover price. That's because this is a fundraiser. I don't make anything on these books, but that's okay. It'll be available through all the usual online booksellers later. Amazon will have it cheaper, and I'll get profits from those sales. But I'm thinking that the people on this list will want the OpenBSD-direct version. ==ml On Fri, Feb 17, 2012 at 05:27:49PM -0700, Austin Hook wrote: Here's the entry I just finished adding to OpenBSD's books.html page clip SSH Mastery by Michael Lucas ISBN-13: 978-1470069711 ISBN-10: 1470069717 February 2012, 145 pp. A guide to what you need to know about SSH. This book will help you eliminate passwords on your network, tunnel unencrypted protocols through secure channels, build VPNs with OpenSSH, and more. Focuses on the OpenSSH server, the OpenSSH client, and the PuTTY client. Michael W Lucas is the author of Absolute OpenBSD and other BSD books. Helping support OpenBSD, Michael is contributing all his author's profits, from orders via the main OpenBSD order page, back to the project. [ Order direct from the OpenBSD website International.] /clip A book like this is great for those of us that have a lot on our plate. I can remember a long period when I kind of knew what OpenSSH could do but just didn't have the time to parse out the man page to properly to forward a browser port or a mail port, to set up a VPN, and I could have benefited a lot sooner with a bit more well explained cookbook examples at my fingertips. Then there's that pesky stuff with keep alive and so on. What does it all really mean for the context I was having trouble with? Hey, I wonder if Michael has anything to say about the safety of even using OpenSSH variants on a different operating system to access one of my OpenBSD boxen. I'm looking forward to read my own copy. Yes, this book has already been out in electronic form for a bit, but myself I spend too much time looking at screen and I still like the physical experience of handling a book. Besides, the printed version already benefits from reader corrections to the electronic edition. Michael has been very gracious with timely help to enable the main OpenBSD website to be the first to offer it, It will be available everywhere soon, but we do have a jump on it this time. It's been so long for us since we last enjoyed Michael's style that we enjoyed in Absolute OpenBSD, I am really happy to see him come back to us with this new volume. There will be a slight delay before the first copies arrive and can be shipped, but the order site is already set up. https://https.openbsd.org/cgi-bin/order?B09=1B08%2b=Add Austin -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlu...@blackhelicopters.org, Twitter @mwlauthor -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlu...@blackhelicopters.org, Twitter @mwlauthor
support needed with traffic shaping
Hello all, I've been playing around with pf's altq feature for the last two days. I want to achieve that my server ($srv) always has 50 % of the bandwidth for downloading available and can also borrow the other 50 % if they are not needed by other clients in the LAN. Currently I have the following pf.conf: http://pastie.org/3406858 From what I have read in the documentation and seen in examples this should do what I want. The problem is that I only get about 0.33 Mbps on speedtest.net in the std_in queue instead of 50% of my downstream. Also SSH connections from a LAN client to the OpenBSD gateway lag and are almost unusable. I would appreciate any advice to fix my pf.conf... Michael
Re: starting nsd via rc.d shows OK but not running
On Fri, Feb 17, 2012 at 07:47:32AM +0100, Antoine Jacoutot wrote:
On Thu, Feb 16, 2012 at 06:47:05PM -0500, Jiri B wrote:
On Sat, Feb 04, 2012 at 09:27:53PM +, Stuart Henderson wrote:
as to the rc.d thing; the daemon *does* start and is running when
rc_check examines it, but exits afterwards.
# cat -n /etc/rc.d/rc.subr | sed -n '117,129p'
117 while true; do # no real loop, only needed to break
118 if type rc_pre /dev/null; then
119 rc_do rc_pre || break
120 fi
121 # XXX only checks the status of the return
code,
122 # and _not_ that the daemon is actually
running
123 rc_do rc_start || break
124 if [ -n ${_bg} ]; then
125 sleep 1
126 rc_do rc_wait start || break
127 fi
128 rc_do rc_write_runfile
129 rc_exit ok
Not true, there's no rc_check at all. Any idea what's the logic behind?
Reporting 'ok' has no real sense. I understand that my own problem was
configuration, true, but having no check and just echoing 'ok' is strange
to me.
It is impossible to report whether start was OK in a _timely_ fashion and
without false positive.
Some daemons can run for like 20 or 30 seconds spawning stuffs, making
checks... then exiting because there is in fact a problem.
See comments line 121 and 122. ok means the daemon was started and return
code was ok.
Well, I still think it would be worth to add rc_check after rc_start, even I
understand
your argument about false positive.
jirib
Re: starting nsd via rc.d shows OK but not running
On Sat, Feb 18, 2012 at 10:53:10AM -0500, Jiri B wrote:
On Fri, Feb 17, 2012 at 07:47:32AM +0100, Antoine Jacoutot wrote:
On Thu, Feb 16, 2012 at 06:47:05PM -0500, Jiri B wrote:
On Sat, Feb 04, 2012 at 09:27:53PM +, Stuart Henderson wrote:
as to the rc.d thing; the daemon *does* start and is running when
rc_check examines it, but exits afterwards.
# cat -n /etc/rc.d/rc.subr | sed -n '117,129p'
117 while true; do # no real loop, only needed to
break
118 if type rc_pre /dev/null; then
119 rc_do rc_pre || break
120 fi
121 # XXX only checks the status of the
return code,
122 # and _not_ that the daemon is actually
running
123 rc_do rc_start || break
124 if [ -n ${_bg} ]; then
125 sleep 1
126 rc_do rc_wait start || break
127 fi
128 rc_do rc_write_runfile
129 rc_exit ok
Not true, there's no rc_check at all. Any idea what's the logic behind?
Reporting 'ok' has no real sense. I understand that my own problem was
configuration, true, but having no check and just echoing 'ok' is strange
to me.
It is impossible to report whether start was OK in a _timely_ fashion and
without false positive.
Some daemons can run for like 20 or 30 seconds spawning stuffs, making
checks... then exiting because there is in fact a problem.
See comments line 121 and 122. ok means the daemon was started and return
code was ok.
Well, I still think it would be worth to add rc_check after rc_start, even I
understand
your argument about false positive.
This has been discussed in the past already and we will not add it.
This could potentially delay the startup bu a _big_ amount of time.
--
Antoine
Re: starting nsd via rc.d shows OK but not running
On Sat, Feb 18, 2012 at 05:23:25PM +0100, Antoine Jacoutot wrote:
On Sat, Feb 18, 2012 at 10:53:10AM -0500, Jiri B wrote:
On Fri, Feb 17, 2012 at 07:47:32AM +0100, Antoine Jacoutot wrote:
On Thu, Feb 16, 2012 at 06:47:05PM -0500, Jiri B wrote:
On Sat, Feb 04, 2012 at 09:27:53PM +, Stuart Henderson wrote:
as to the rc.d thing; the daemon *does* start and is running when
rc_check examines it, but exits afterwards.
# cat -n /etc/rc.d/rc.subr | sed -n '117,129p'
117 while true; do # no real loop, only needed to
break
118 if type rc_pre /dev/null; then
119 rc_do rc_pre || break
120 fi
121 # XXX only checks the status of the
return code,
122 # and _not_ that the daemon is actually
running
123 rc_do rc_start || break
124 if [ -n ${_bg} ]; then
125 sleep 1
126 rc_do rc_wait start || break
127 fi
128 rc_do rc_write_runfile
129 rc_exit ok
Not true, there's no rc_check at all. Any idea what's the logic behind?
Reporting 'ok' has no real sense. I understand that my own problem was
configuration, true, but having no check and just echoing 'ok' is
strange
to me.
It is impossible to report whether start was OK in a _timely_ fashion and
without false positive.
Some daemons can run for like 20 or 30 seconds spawning stuffs, making
checks... then exiting because there is in fact a problem.
See comments line 121 and 122. ok means the daemon was started and
return code was ok.
Well, I still think it would be worth to add rc_check after rc_start, even
I understand
your argument about false positive.
This has been discussed in the past already and we will not add it.
This could potentially delay the startup bu a _big_ amount of time.
OK.
Another point. In OpenBSD gettys are started after end of /etc/rc, which
means after all packages daemons as well. Good things is you can break
hanging startup of a process in OpenBSD, not possible in some Linuxes :)
But on AIX gettys are started earlier, this is nice, even it messes
the console with output of the daemons or applications defined in
/etc/inittab.
jirib
Re: starting nsd via rc.d shows OK but not running
It is impossible to report whether start was OK in a _timely_ fashion and without false positive. Some daemons can run for like 20 or 30 seconds spawning stuffs, making checks... then exiting because there is in fact a problem. See comments line 121 and 122. ok means the daemon was started and return code was ok. Well, I still think it would be worth to add rc_check after rc_start, even I understand your argument about false positive. This has been discussed in the past already and we will not add it. This could potentially delay the startup bu a _big_ amount of time. OK. Thing is that rc.d(8) is meant to be as simple and generic as possible. Also don't forget both system and ports use this so each function has been carefully though. The drawback is that yes, sometimes it is a little too generic for each and every need, but on the other end, because it is so simple, it's very easy to tweak function(s) _within_ the daemon script itself if more extensive checks are needed (using rc_pre or even rc_start). So it is easily extensible on a case by case basis and we can keep the framework clean and simple. -- Antoine
Re: Cannot upgrade Sony Vaio VPCCA using the amd64 RAM kernel
List: openbsd-misc Subject:Re: Cannot upgrade Sony Vaio VPCCA using the amd64 RAM kernel From: Kenneth R Westerback kwesterback () rogers ! com Date: 2012-02-17 14:24:19 Message-ID: 20120217142418.GZ20102 () mac ! westerback ! ca [Download message RAW] On Thu, Feb 16, 2012 at 08:18:27PM -0600, eagir...@cox.net wrote: Grabbed the 15 February snapshot, but booting bsd.rd results in this: Using drive 0, partition 3 Loading... probing: pc0 mem[634K 511M 510M 2474M 12K 1M 12K 84K 4606M a20=on] disk: hd0+ OpenBSD/amd64 BOOT 3.18 boot bsd.rd booting hd0a:bsd.rd: 2986868+717388+2861496+0+504624=0xaef670 entry point at 0x1001e0 [7205c766, 3404, 24448b12, 1608a304] after which fans turn, and that's about it. Dmesg below sig. -- Ed Ahlsen-Girard Ft. Walton Beach FL OpenBSD 5.1 (GENERIC.MP) #206: Sat Feb 11 12:24:58 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Ken Thanks to Ken for pointing out that my initial message was misleading: the dmesg included is from AFTER I upgraded with the unpreferred, no ramdisk kernel method. It does describe the hardware, of course. -- Ed Ahlsen-Girard Ft. Walton Beach FL OpenBSD 5.1 (GENERIC.MP) #206: Sat Feb 11 12:24:58 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8496082944 (8102MB) avail mem = 8255754240 (7873MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb3a0 (17 entries) bios0: vendor American Megatrends Inc. version R1100V2 date 04/15/2011 bios0: Sony Corporation VPCCA25FX acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC HPET SSDT SLIC MCFG SSDT SSDT ECDT SSDT acpi0: wakeup devices B0D4(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3)\ USB5(S3) USB6(S3) USB7(S3) EHC1(S3) EHC2(S3) PXSX(S3) PXSX(S3)\ PXSX(S3) RP03(S3) PXSX(S3) RP04(S3) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2295.11 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,PCLMUL,\ MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,\ POPCNT,XSAVE,AVX,NXE,LONG,LAHF cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2294.79 MHz cpu1: 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,\ PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,\ x2APIC,POPCNT,XSAVE,AVX,NXE,LONG,LAHF cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2294.79 MHz cpu2: 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,\ PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,\ x2APIC,POPCNT,XSAVE,AVX,NXE,LONG,LAHF cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2294.79 MHz cpu3: 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,\ PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2\ ,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG,LAHF cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpicpu2 at acpi0: C1, PSS acpicpu3 at acpi0: C1, PSS acpitz0 at acpi0: critical temperature is 96 degC acpitz1 at acpi0: critical temperature is 96 degC acpibat0 at acpi0: BAT0 type LiOn oem Sony Corp. acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 cpu0: Enhanced SpeedStep 2294 MHz: speeds: 2301, 2300, 1800, \ 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel GT2 Video rev 0x09 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 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 Intel 6 Series USB rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
Re: when re-install how to make leave some partitions untouched simple
On Sat, Feb 18, 2012 at 12:54:30PM +, Stuart Henderson wrote: You are assuming that 1) the disklabel was previously done by using auto layout and wasn't edited, and 2) the disklabel command in the new install kernel uses the same partition sizes and layout as the command used for the previous installation. This is not a safe assumption. This is exactly what happened to me when doing a fresh install on an old disklabel. I carefully wrote down every number beforehand, but it wanted to use new fsize and bsize. But it all worked out in the end. If you want to preserve anything, back it up. Write down every number in disklabel, or forget getting it back. I had room for adding another partition at the end so I put a copy of everything there also. Chris Bennett
Re: alix2d2 LM86, no hw.sensors
On Sat, Feb 18, 2012 at 03:09 +1100, Jonathan Gray wrote:
On Fri, Feb 17, 2012 at 04:20:25PM +0100, Michal Mazurek wrote:
I have an alix2d2 running OpenBSD 5.0. There are no hw.sensors.
The producer says there is an LM86 on board, which is supported by the
maxtmp driver. It appears the driver is present in generic. I tried starting
sensorsd but got:
daemon:Feb 17 13:12:04 T1 sensorsd[10445]: startup, system has 0 sensors
How can I read the temperature of my alix2d2 running OpenBSD 5.0?
There is no driver for the CS5535/CS5536 I2C controller the chip is connected
to,
it won't work till that is written.
[un]surprisingly it's actually the same as gscsio(4). here's a port
of that code to glxpcib(4). i don't have the hardware at hand, but
i encourage you to test (:
cheers
Index: dev/pci/files.pci
===
RCS file: /cvs/src/sys/dev/pci/files.pci,v
retrieving revision 1.281
diff -u -p -r1.281 files.pci
--- dev/pci/files.pci 15 Nov 2011 22:27:53 - 1.281
+++ dev/pci/files.pci 18 Feb 2012 23:03:52 -
@@ -807,6 +807,6 @@ attach itherm at pci
file dev/pci/itherm.citherm
# AMD Geode CS5536 PCI-ISA bridge
-device glxpcib: isabus, gpiobus
+device glxpcib: isabus, gpiobus, i2cbus
attach glxpcib at pci
file dev/pci/glxpcib.c glxpcib
Index: dev/pci/glxpcib.c
===
RCS file: /cvs/src/sys/dev/pci/glxpcib.c,v
retrieving revision 1.3
diff -u -p -r1.3 glxpcib.c
--- dev/pci/glxpcib.c 23 Oct 2010 17:42:57 - 1.3
+++ dev/pci/glxpcib.c 18 Feb 2012 23:03:52 -
@@ -28,6 +28,7 @@
#include sys/device.h
#include sys/gpio.h
#include sys/timetc.h
+#include sys/rwlock.h
#include machine/bus.h
#ifdef __i386__
@@ -35,6 +36,8 @@
#endif
#include dev/gpio/gpiovar.h
+#include dev/i2c/i2cvar.h
+
#include dev/pci/pcireg.h
#include dev/pci/pcivar.h
#include dev/pci/pcidevs.h
@@ -133,6 +136,34 @@
#define AMD5536_GPIO_IN_INVRT_EN 0x24 /* invert input */
#defineAMD5536_GPIO_READ_BACK 0x30/* read back value */
+/* SMB */
+#define MSR_LBAR_SMB DIVIL_LBAR_SMB
+#define MSR_SMB_SIZE 0x07
+#define MSR_SMB_ADDR_MASK 0xfff8
+#define AMD5536_SMB_SDA0x00 /* serial data */
+#define AMD5536_SMB_STS0x01 /* status */
+#define AMD5536_SMB_STS_SLVSTOP0x80 /* slave stop */
+#define AMD5536_SMB_STS_SDAST 0x40 /* smb data status */
+#define AMD5536_SMB_STS_BER0x20 /* bus error */
+#define AMD5536_SMB_STS_NEGACK 0x10 /* negative acknowledge */
+#define AMD5536_SMB_STS_MASTER 0x02 /* master */
+#define AMD5536_SMB_STS_XMIT 0x01 /* transmit or receive */
+#define AMD5536_SMB_CST0x02 /* control status */
+#define AMD5536_SMB_CST_MATCH 0x04 /* address match */
+#define AMD5536_SMB_CST_BB 0x02 /* bus busy */
+#define AMD5536_SMB_CST_BUSY 0x01 /* busy */
+#define AMD5536_SMB_CTL1 0x03 /* control 1 */
+#define AMD5536_SMB_CTL1_ACK 0x10 /* receive acknowledge */
+#define AMD5536_SMB_CTL1_INTEN 0x04 /* interrupt enable */
+#define AMD5536_SMB_CTL1_STOP 0x02 /* stop */
+#define AMD5536_SMB_CTL1_START 0x01 /* start */
+#define AMD5536_SMB_ADDR 0x04 /* serial address */
+#define AMD5536_SMB_ADDR_SAEN 0x80 /* slave enable */
+#define AMD5536_SMB_CTL2 0x05 /* control 2 */
+#define AMD5536_SMB_CTL2_EN0x01 /* enable clock */
+#define AMD5536_SMB_CTL2_FREQ 0x78 /* 100 kHz */
+#define AMD5536_SMB_CTL3 0x06 /* control 3 */
+
/*
* MSR registers we want to preserve accross suspend/resume
*/
@@ -151,12 +182,21 @@ struct glxpcib_softc {
uint64_tsc_msrsave[nitems(glxpcib_msrlist)];
-#if !defined(SMALL_KERNEL) NGPIO 0
+#ifndef SMALL_KERNEL
+#if NGPIO 0
/* GPIO interface */
bus_space_tag_t sc_gpio_iot;
bus_space_handle_t sc_gpio_ioh;
struct gpio_chipset_tag sc_gpio_gc;
gpio_pin_t sc_gpio_pins[AMD5536_GPIO_NPINS];
+#endif
+ /* I2C interface */
+ bus_space_tag_t sc_smb_iot;
+ bus_space_handle_t sc_smb_ioh;
+ struct i2c_controller sc_smb_ic;
+ struct rwlock sc_smb_lck;
+
+ /* Watchdog */
int sc_wdog;
int sc_wdog_period;
#endif
@@ -180,11 +220,23 @@ void pcibattach(struct device *parent, s
u_int glxpcib_get_timecount(struct timecounter *tc);
-#if !defined(SMALL_KERNEL) NGPIO 0
+#ifndef SMALL_KERNEL
+int glxpcib_wdogctl_cb(void *, int);
+#if NGPIO 0
void glxpcib_gpio_pin_ctl(void *, int, int);
intglxpcib_gpio_pin_read(void *, int);
void glxpcib_gpio_pin_write(void *, int, int);
-int glxpcib_wdogctl_cb(void *, int);
+#endif
+intglxpcib_smb_acquire_bus(void *, int);
+void glxpcib_smb_release_bus(void *, int);
+intglxpcib_smb_send_start(void *, int);
+int
smartphones and managing openbsd servers
Hello list, This might not be OpenBSD specific, but maybe users can share their experiences with smartphones an managing OpenBSD servers. So far, my smartphone has been a very usefull tool to manage my OpenBSD servers. Currently i am using a Palm Treo 680 with some lousy ssh application to access my servers, it is usefull, but this is getting pretty ancient, doesn't have wifi for exaple, and i would like that feature on a smartphone. I also love the touch screen. What newer smartphones do you recommend for using also as a tool for managing OpenBSD servers (maybe windogs too) ? What experiences had you had with smartphones and OpenBSD managing? Best regards, Marcos
record off of uaudio device (help?)
Can someone point me to some docs explaining how I can record off of a uaudio device I plugged in? [after plugging in uaudio device] uaudio0 at uhub0 port 3 configuration 1 interface 0 E-MU Systems, Inc. E-MU 0202 | USB rev 2.00/1.00 addr 3 uaudio0: audio rev 1.00, 3 mixer controls audio1 at uaudio0 now what? $ audioctl -f /dev/audioctl1 name=USB audio version= config=uaudio encodings=slinear_le:24:3:1 properties=full_duplex full_duplex=0 fullduplex=0 blocksize=13216 hiwat=4 lowat=1 output_muted=0 monitor_gain=0 mode= play.rate=44100 play.sample_rate=44100 play.channels=2 play.precision=24 play.bps=3 play.msb=1 play.encoding=slinear_le play.gain=255 play.balance=32 play.port=0x0 play.avail_ports=0x0 play.seek=0 play.samples=0 play.eof=0 play.pause=0 play.error=0 play.waiting=0 play.open=0 play.active=0 play.buffer_size=65536 play.block_size=13216 play.errors=0 record.rate=44100 record.sample_rate=44100 record.channels=2 record.precision=24 record.bps=3 record.msb=1 record.encoding=slinear_le record.gain=127 record.balance=32 record.port=0x0 record.avail_ports=0x0 record.seek=0 record.samples=0 record.eof=0 record.pause=1 record.error=0 record.waiting=0 record.open=0 record.active=0 record.buffer_size=65536 record.block_size=17632 record.errors=0 $ mixerctl -v -f /dev/mixer1 inputs.dac.mute=off [ off on ] inputs.dac=255,255 volume outputs.ext12-enable=off [ off on ] $ sysctl kern.version kern.version=OpenBSD 5.0-current (GENERIC) #121: Mon Nov 28 16:00:51 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Re: record off of uaudio device (help?)
On Sun, Feb 19, 2012 at 1:59 AM, patrick keshishian pkesh...@gmail.com wrote: Can someone point me to some docs explaining how I can record off of a uaudio device I plugged in? [after plugging in uaudio device] uaudio0 at uhub0 port 3 configuration 1 interface 0 E-MU Systems, Inc. E-MU 0202 | USB rev 2.00/1.00 addr 3 uaudio0: audio rev 1.00, 3 mixer controls audio1 at uaudio0 now what? http://www.openbsd.org/faq/faq13.html#recordaudio don't specify -f for your commands so we can't see what inputs/outputs are in use by system $ audioctl -f /dev/audioctl1 name=USB audio version= config=uaudio encodings=slinear_le:24:3:1 properties=full_duplex full_duplex=0 fullduplex=0 blocksize=13216 hiwat=4 lowat=1 output_muted=0 monitor_gain=0 mode= play.rate=44100 play.sample_rate=44100 play.channels=2 play.precision=24 play.bps=3 play.msb=1 play.encoding=slinear_le play.gain=255 play.balance=32 play.port=0x0 play.avail_ports=0x0 play.seek=0 play.samples=0 play.eof=0 play.pause=0 play.error=0 play.waiting=0 play.open=0 play.active=0 play.buffer_size=65536 play.block_size=13216 play.errors=0 record.rate=44100 record.sample_rate=44100 record.channels=2 record.precision=24 record.bps=3 record.msb=1 record.encoding=slinear_le record.gain=127 record.balance=32 record.port=0x0 record.avail_ports=0x0 record.seek=0 record.samples=0 record.eof=0 record.pause=1 record.error=0 record.waiting=0 record.open=0 record.active=0 record.buffer_size=65536 record.block_size=17632 record.errors=0 $ mixerctl -v -f /dev/mixer1 inputs.dac.mute=off B [ off on ] inputs.dac=255,255 volume outputs.ext12-enable=off B [ off on ] $ sysctl kern.version kern.version=OpenBSD 5.0-current (GENERIC) #121: Mon Nov 28 16:00:51 MST 2011 B B dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Is anyone able to use subtitleeditor?
When I tell it to open any video I get this: Media file could not be played. Failed to create a GStreamer textoverlay (textoverlay). Please check your GStreamer installation. $ pkg_info -S subtitleeditor Information for inst:subtitleeditor-0.37.1p2 Signature: subtitleeditor-0.37.1p2,GL.12.0,X11.15.0,Xau.9.0,Xcomposite.3.0,Xcursor.4.0,X damage.3.1,Xdmcp.10.0,Xext.12.0,Xfixes.5.1,Xi.11.0,Xinerama.5.0,Xrandr.6.1,Xr ender.5.0,Xxf86vm.5.0,atk-1.0.2801.0,atkmm-1.6.10.0,c.62.0,cairo.11.1,cairomm -1.0.5.0,desktop-file-utils-0.19,drm.2.6,enchant-1.6.0p0,enchant.6.1,expat.9. 0,fontconfig.7.0,freetype.18.1,gdk-x11-2.0.2400.0,gdk_pixbuf-2.0.2200.1,gdkmm -2.4.11.0,gettext-0.18.1p0,gio-2.0.2992.0,giomm-2.4.11.0,glib-2.0.2992.0,glib mm-2.4.11.0,gmodule-2.0.2992.0,gobject-2.0.2992.0,gstaudio-0.10.2.5,gstbase-0 .10.2.4,gstcdda-0.10.2.5,gstcontroller-0.10.3.4,gstdataprotocol-0.10.2.4,gsti nterfaces-0.10.2.5,gstnet-0.10.2.4,gstnetbuffer-0.10.2.5,gstpbutils-0.10.2.5, gstreamer-0.10.2.4,gstreamer-plugins-base-0.10.35p1,gstreamer-plugins-good-0. 10.30p2v0,gstreamermm-0.10.1.0,gstreamermm-0.10.10,gstrtp-0.10.2.5,gsttag-0.1 0.2.5,gstvideo-0.10.2.5,gthread-2.0.2992.0,gtk-update-icon-cache-2.24.8,gtk-x 11-2.0.2400.0,gtk2mm-2.24.2p0,gtkmm-2.4.11.0,iconv.6.0,intl.5.0,iso-codes-3.2 8,libiconv-1.14,m.7.0,pango-1.0.2903.0,pangocairo-1.0.2903.0,pangoft2-1.0.290 3.0,pangomm-1.4.10.0,pcre-8.21,pcre.2.5,pixman-1.22.2,png.13.0,pthread-stubs. 1.0,pthread.13.3,sigc-2.0.2.0,stdc++.54.0,xcb-render.0.0,xcb-shm.0.0,xcb.2.2, xml++-2.6.1.0,xml2.12.0,z.4.1 $ subtitleeditor (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_factory_get_element_type: assertion `GST_IS_ELEMENT_FACTORY (factory)' failed (subtitleeditor:29100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (subtitleeditor:29100): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type,
Re: record off of uaudio device (help?)
I should have been more specific with my question and subject line: I don't see where aucat's -f device values are documented. Googling finds old (google-cached) current.html pages, circa 2009, suggesting using 'aucat -f sun:1' for /dev/audio1. However, this at first failed: $ aucat -f sun:1 -m rec -o /tmp/test.wav sio(sun:1|): busy loop, disconnecting A bit more googling finds this post[1] suggesting addition of -z 256 to aucat, which seems to make things work. $ aucat -z 256 -f sun:1 -o /tmp/test.wav ^C --patrick [1] http://old.nabble.com/aucat-bug-in-4.8-beta-i386---td29333138.html On Sat, Feb 18, 2012 at 4:59 PM, patrick keshishian pkesh...@gmail.com wrote: Can someone point me to some docs explaining how I can record off of a uaudio device I plugged in? [after plugging in uaudio device] uaudio0 at uhub0 port 3 configuration 1 interface 0 E-MU Systems, Inc. E-MU 0202 | USB rev 2.00/1.00 addr 3 uaudio0: audio rev 1.00, 3 mixer controls audio1 at uaudio0 now what? $ audioctl -f /dev/audioctl1 name=USB audio version= config=uaudio encodings=slinear_le:24:3:1 properties=full_duplex full_duplex=0 fullduplex=0 blocksize=13216 hiwat=4 lowat=1 output_muted=0 monitor_gain=0 mode= play.rate=44100 play.sample_rate=44100 play.channels=2 play.precision=24 play.bps=3 play.msb=1 play.encoding=slinear_le play.gain=255 play.balance=32 play.port=0x0 play.avail_ports=0x0 play.seek=0 play.samples=0 play.eof=0 play.pause=0 play.error=0 play.waiting=0 play.open=0 play.active=0 play.buffer_size=65536 play.block_size=13216 play.errors=0 record.rate=44100 record.sample_rate=44100 record.channels=2 record.precision=24 record.bps=3 record.msb=1 record.encoding=slinear_le record.gain=127 record.balance=32 record.port=0x0 record.avail_ports=0x0 record.seek=0 record.samples=0 record.eof=0 record.pause=1 record.error=0 record.waiting=0 record.open=0 record.active=0 record.buffer_size=65536 record.block_size=17632 record.errors=0 $ mixerctl -v -f /dev/mixer1 inputs.dac.mute=off [ off on ] inputs.dac=255,255 volume outputs.ext12-enable=off [ off on ] $ sysctl kern.version kern.version=OpenBSD 5.0-current (GENERIC) #121: Mon Nov 28 16:00:51 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Re: record off of uaudio device (help?)
On Sun, Feb 19, 2012 at 7:36 AM, patrick keshishian pkesh...@gmail.com wrote: I should have been more specific with my question and subject line: I don't see where aucat's -f device values are documented. Googling finds old (google-cached) current.html pages, circa 2009, suggesting using 'aucat -f sun:1' for /dev/audio1. However, this at first failed: No. I mean post output of mixerctl -v and audioctl -v ;-) Don't use Google for something what is much more better documented inside system itself http://www.openbsd.org/cgi-bin/man.cgi?query=aucatapropos=0sektion=0manpat h=OpenBSD+5.0arch=i386format=html $ aucat -f sun:1 -m rec -o /tmp/test.wav sio(sun:1|): busy loop, disconnecting A bit more googling finds this post[1] suggesting addition of -z 256 to aucat, which seems to make things work. $ aucat -z 256 -f sun:1 -o /tmp/test.wav ^C --patrick [1] http://old.nabble.com/aucat-bug-in-4.8-beta-i386---td29333138.html On Sat, Feb 18, 2012 at 4:59 PM, patrick keshishian pkesh...@gmail.com wrote: Can someone point me to some docs explaining how I can record off of a uaudio device I plugged in? [after plugging in uaudio device] uaudio0 at uhub0 port 3 configuration 1 interface 0 E-MU Systems, Inc. E-MU 0202 | USB rev 2.00/1.00 addr 3 uaudio0: audio rev 1.00, 3 mixer controls audio1 at uaudio0 now what? $ audioctl -f /dev/audioctl1 name=USB audio version= config=uaudio encodings=slinear_le:24:3:1 properties=full_duplex full_duplex=0 fullduplex=0 blocksize=13216 hiwat=4 lowat=1 output_muted=0 monitor_gain=0 mode= play.rate=44100 play.sample_rate=44100 play.channels=2 play.precision=24 play.bps=3 play.msb=1 play.encoding=slinear_le play.gain=255 play.balance=32 play.port=0x0 play.avail_ports=0x0 play.seek=0 play.samples=0 play.eof=0 play.pause=0 play.error=0 play.waiting=0 play.open=0 play.active=0 play.buffer_size=65536 play.block_size=13216 play.errors=0 record.rate=44100 record.sample_rate=44100 record.channels=2 record.precision=24 record.bps=3 record.msb=1 record.encoding=slinear_le record.gain=127 record.balance=32 record.port=0x0 record.avail_ports=0x0 record.seek=0 record.samples=0 record.eof=0 record.pause=1 record.error=0 record.waiting=0 record.open=0 record.active=0 record.buffer_size=65536 record.block_size=17632 record.errors=0 $ mixerctl -v -f /dev/mixer1 inputs.dac.mute=off B [ off on ] inputs.dac=255,255 volume outputs.ext12-enable=off B [ off on ] $ sysctl kern.version kern.version=OpenBSD 5.0-current (GENERIC) #121: Mon Nov 28 16:00:51 MST 2011 B B dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Re: record off of uaudio device (help?)
On Sat, Feb 18, 2012 at 10:57 PM, Tomas Bodzar tomas.bod...@gmail.com wrote: On Sun, Feb 19, 2012 at 7:36 AM, patrick keshishian pkesh...@gmail.com wrote: I should have been more specific with my question and subject line: I don't see where aucat's -f device values are documented. Googling finds old (google-cached) current.html pages, circa 2009, suggesting using 'aucat -f sun:1' for /dev/audio1. However, this at first failed: No. I mean post output of mixerctl -v and audioctl -v ;-) Don't use Google for something what is much more better documented inside system itself http://www.openbsd.org/cgi-bin/man.cgi?query=aucatapropos=0sektion=0manpat h=OpenBSD+5.0arch=i386format=html are _you_ /certain/ of what you speak? --patrick $ aucat -f sun:1 -m rec -o /tmp/test.wav sio(sun:1|): busy loop, disconnecting A bit more googling finds this post[1] suggesting addition of -z 256 to aucat, which seems to make things work. $ aucat -z 256 -f sun:1 -o /tmp/test.wav ^C --patrick [1] http://old.nabble.com/aucat-bug-in-4.8-beta-i386---td29333138.html On Sat, Feb 18, 2012 at 4:59 PM, patrick keshishian pkesh...@gmail.com wrote: Can someone point me to some docs explaining how I can record off of a uaudio device I plugged in? [after plugging in uaudio device] uaudio0 at uhub0 port 3 configuration 1 interface 0 E-MU Systems, Inc. E-MU 0202 | USB rev 2.00/1.00 addr 3 uaudio0: audio rev 1.00, 3 mixer controls audio1 at uaudio0 now what? $ audioctl -f /dev/audioctl1 name=USB audio version= config=uaudio encodings=slinear_le:24:3:1 properties=full_duplex full_duplex=0 fullduplex=0 blocksize=13216 hiwat=4 lowat=1 output_muted=0 monitor_gain=0 mode= play.rate=44100 play.sample_rate=44100 play.channels=2 play.precision=24 play.bps=3 play.msb=1 play.encoding=slinear_le play.gain=255 play.balance=32 play.port=0x0 play.avail_ports=0x0 play.seek=0 play.samples=0 play.eof=0 play.pause=0 play.error=0 play.waiting=0 play.open=0 play.active=0 play.buffer_size=65536 play.block_size=13216 play.errors=0 record.rate=44100 record.sample_rate=44100 record.channels=2 record.precision=24 record.bps=3 record.msb=1 record.encoding=slinear_le record.gain=127 record.balance=32 record.port=0x0 record.avail_ports=0x0 record.seek=0 record.samples=0 record.eof=0 record.pause=1 record.error=0 record.waiting=0 record.open=0 record.active=0 record.buffer_size=65536 record.block_size=17632 record.errors=0 $ mixerctl -v -f /dev/mixer1 inputs.dac.mute=off [ off on ] inputs.dac=255,255 volume outputs.ext12-enable=off [ off on ] $ sysctl kern.version kern.version=OpenBSD 5.0-current (GENERIC) #121: Mon Nov 28 16:00:51 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
