Re: Trying to get Wacom CTL-490 to work
On Mon, Jul 18, 2016 at 8:03 AM, Frank Groeneveld wrote: > On Sun, Jul 17, 2016 at 08:53:50PM +0200, Frank Groeneveld wrote: >> [46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6 >> Operation not permitted. >> [46.602] (EE) Error opening /dev/uhid6: Operation not permitted > > Forgot to mention: I had changed the file permissions on uhid6 to be > worl readable and writable. The privilege separation code in xenocara has a compiled in list of devices that are permitted to be opened; of the uhid devices it only currently includes /dev/uhid0 through /dev/uhid3. You can either a) update the list and recompile the X server b) symlink it to a different name that's already in the allowed list but that's not used by OpenBSD (e.g., "/dev/ttyJ0") c) ??? Philip Guenther
Re: how would you troubleshoot stuttering video? (Lenovo Thinkpad)
On Mon, Jul 18, 2016 at 3:09 PM, Alexandre Ratchov wrote: > could you go in the bios setup and see if there are options to > disable audio recording? If so, could you enable recording and see > what happens? > That fixed it. Thank you! So, (for the list archives), azalia audio driver : http://man.openbsd.org/OpenBSD-current/man4/azalia.4 dmesg cliip: azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x04: msi azalia1: codecs: Realtek ALC292 audio0 at azalia1 When hardware microphone is disabled in BIOS, audio will stutter. Enabling hardware microphone again makes audio work fine. Very strange, but true. Thanks again.
Re: how would you troubleshoot stuttering video? (Lenovo Thinkpad)
On Mon, Jul 18, 2016 at 04:01:30PM +0800, Miles Keaton wrote: > On Mon, Jul 18, 2016 at 3:09 PM, Alexandre Ratchov wrote: > > When hardware microphone is disabled in BIOS, audio will stutter. Enabling > hardware microphone again makes audio work fine. > > Very strange, but true. Alarming? Okay, I'm in a somewhat lazy summer holiday mode here, and recent political events may have made me a little jumpy, but at this point I would seriously consider cutting the wires to the hardware microphone so as to see if audio will start stuttering againg.. :-D -- Erling Westenvik
Re: ratble and rdomain support on dhcpd and openvpn
Hi, OpenVPN does not support rdomains and probably never will, as it is OpenBSD-specific. I had some success by running it in the default rdomain an then dispatching the clients in different rdomains via PF. But this was for server mode. Maybe you can do something like that for the client, like running it in the default rdomain and make PF rules in your rdomain 200 to send relevant packets to the VPN. You might also use "route -T 200 exec openvpn ..." and a script, which will set the rdomain on connection. Look at the --up parameter of the OpenVPN man page. -- Cordialement, Pierre BARDOU -Message d'origine- De : Difan Zhao [mailto:difan.z...@pason.com] Envoyé : vendredi 15 juillet 2016 21:35 À : Chris Cappuccio Cc : Pierre Emeriaud ; misc@openbsd.org Objet : Re: ratble and rdomain support on dhcpd and openvpn Thank you sir! So I probably just stick with my hacking approach and wait for the 6.0. I see that will come in November so not too much waiting. So any idea how the openvpn might start to support rtable or rdomain? Thanks, Difan -Original Message- From: Chris Cappuccio [mailto:ch...@nmedia.net] Sent: Friday, July 15, 2016 11:07 AM To: Difan Zhao Cc: Pierre Emeriaud ; misc@openbsd.org Subject: Re: ratble and rdomain support on dhcpd and openvpn Difan Zhao [difan.z...@pason.com] wrote: > Hi Pierre, > > I just upgraded the soekris box to openbsd 5.9 however I am still > having the problem setting the rtable... > This requires OpenBSD 6.0 which is not yet released. You can use snapshots at http//ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ to install the beta code.
Re: Trying to get Wacom CTL-490 to work
On Mon, Jul 18, 2016 at 09:54:02AM +0200, Philip Guenther wrote: > > The privilege separation code in xenocara has a compiled in list of > devices that are permitted to be opened; of the uhid devices it only > currently includes /dev/uhid0 through /dev/uhid3. You can either > a) update the list and recompile the X server > b) symlink it to a different name that's already in the allowed list > but that's not used by OpenBSD (e.g., "/dev/ttyJ0") > c) ??? Great tip, thank you! The permission denied error is gone indeed. Unfortunately it seems the drive cannot do anythin with the raw uhid devices, it complains about missing X & Y directions. Frank
Re: ratble and rdomain support on dhcpd and openvpn
Great ideas! Thank you Pierre! -Original Message- From: BARDOU Pierre [mailto:bardo...@mipih.fr] Sent: Monday, July 18, 2016 8:51 AM To: Difan Zhao Cc: misc@openbsd.org Subject: RE: ratble and rdomain support on dhcpd and openvpn Hi, OpenVPN does not support rdomains and probably never will, as it is OpenBSD-specific. I had some success by running it in the default rdomain an then dispatching the clients in different rdomains via PF. But this was for server mode. Maybe you can do something like that for the client, like running it in the default rdomain and make PF rules in your rdomain 200 to send relevant packets to the VPN. You might also use "route -T 200 exec openvpn ..." and a script, which will set the rdomain on connection. Look at the --up parameter of the OpenVPN man page. -- Cordialement, Pierre BARDOU -Message d'origine- De : Difan Zhao [mailto:difan.z...@pason.com] Envoyé : vendredi 15 juillet 2016 21:35 À : Chris Cappuccio Cc : Pierre Emeriaud ; misc@openbsd.org Objet : Re: ratble and rdomain support on dhcpd and openvpn Thank you sir! So I probably just stick with my hacking approach and wait for the 6.0. I see that will come in November so not too much waiting. So any idea how the openvpn might start to support rtable or rdomain? Thanks, Difan -Original Message- From: Chris Cappuccio [mailto:ch...@nmedia.net] Sent: Friday, July 15, 2016 11:07 AM To: Difan Zhao Cc: Pierre Emeriaud ; misc@openbsd.org Subject: Re: ratble and rdomain support on dhcpd and openvpn Difan Zhao [difan.z...@pason.com] wrote: > Hi Pierre, > > I just upgraded the soekris box to openbsd 5.9 however I am still > having the problem setting the rtable... > This requires OpenBSD 6.0 which is not yet released. You can use snapshots at http//ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ to install the beta code.
#define vs enums?
Hi, does anyone know why #defines are used instead of enums here in src/usr.bin/mandoc/man.h? #define MAN_br 0 #define MAN_TH 1 #define MAN_SH 2 #define MAN_SS 3 #define MAN_TP 4 #define MAN_LP 5 #define MAN_PP 6 #define MAN_P7 #define MAN_IP 8 #define MAN_HP 9 #define MAN_SM 10 #define MAN_SB 11 #define MAN_BI 12 #define MAN_IB 13 #define MAN_BR 14 #define MAN_RB 15 #define MAN_R 16 #define MAN_B 17 #define MAN_I 18 #define MAN_IR 19 #define MAN_RI 20 #define MAN_sp 21 #define MAN_nf 22 #define MAN_fi 23 #define MAN_RE 24 #define MAN_RS 25 #define MAN_DT 26 #define MAN_UC 27 #define MAN_PD 28 #define MAN_AT 29 #define MAN_in 30 #define MAN_ft 31 #define MAN_OP 32 #define MAN_EX 33 #define MAN_EE 34 #define MAN_UR 35 #define MAN_UE 36 #define MAN_ll 37 #define MAN_MAX 38
Re: how would you troubleshoot stuttering video? (Lenovo Thinkpad)
On Mon, Jul 18, 2016 at 04:01:30PM +0800, Miles Keaton wrote: > On Mon, Jul 18, 2016 at 3:09 PM, Alexandre Ratchov wrote: > > > could you go in the bios setup and see if there are options to > > disable audio recording? If so, could you enable recording and see > > what happens? > > > > That fixed it. Thank you! > > So, (for the list archives), azalia audio driver : > http://man.openbsd.org/OpenBSD-current/man4/azalia.4 > > dmesg cliip: > azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x04: msi > azalia1: codecs: Realtek ALC292 > audio0 at azalia1 > > When hardware microphone is disabled in BIOS, audio will stutter. Enabling > hardware microphone again makes audio work fine. > > Very strange, but true. > When the microphone is disabled, the azalia driver gets confused on certain machines. We need to fix it (ie make the device appear play-only), but I don't have a machine that reproduces the problem. If you have some time, could you build a kernel with the AZALIA_DEBUG option, reboot using the new kernel and send me the output of dmesg once with the mic disabled in the bios and once with the mic enabled. This way we could compare them and possibly find a fix. thanks
Re: #define vs enums?
Hi, r...@firemail.cc wrote on Mon, Jul 18, 2016 at 08:25:47PM +0300: > does anyone know why #defines are used instead of enums here in > src/usr.bin/mandoc/man.h? > > #define MAN_br 0 > #define MAN_TH 1 > #define MAN_SH 2 [...] Of course, that is well-known and even explained in the commit logs: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/mandoc/man.h#rev1.51 If you have a better idea how to make these enums without having to define all the macros for both mdoc(7) and man(7) in roff.h and without having to give up the feature that the same member roff_node.tok can be used for both macrosets, that would be welcome. Yours, Ingo
Triggering automatic upgrade (not over network) not working
On my macppc, the presence of /auto_upgrade.conf doesn't actually
cause bsd.rd to pretend it's been netbooted. The file is present at
the root of my disk, under /dev/wda0. The documentation in
autoinstall(8) says that the presence of /auto_{upgrade,install}.conf
tells bsd.rd to treat it like an autoinstall. So far my macppc boots
bsd.rd, but stays at the prompt without doing a timeout of any kind or
trying /auto_upgrade.conf, even if I do select Autoinstall at the
prompt.
If I am to put /auto_upgrade.conf in the root of the file system in
bsd.rd, how could I do so? If not, how could I use the automatic
upgrade system without netbooting?
Thank you
Re: Triggering automatic upgrade (not over network) not working
On Mon, Jul 18, 2016 at 10:46:09PM -0400, Toyam Cox wrote:
> On my macppc, the presence of /auto_upgrade.conf doesn't actually
> cause bsd.rd to pretend it's been netbooted. The file is present at
> the root of my disk, under /dev/wda0. The documentation in
> autoinstall(8) says that the presence of /auto_{upgrade,install}.conf
> tells bsd.rd to treat it like an autoinstall. So far my macppc boots
> bsd.rd, but stays at the prompt without doing a timeout of any kind or
> trying /auto_upgrade.conf, even if I do select Autoinstall at the
> prompt.
>
> If I am to put /auto_upgrade.conf in the root of the file system in
> bsd.rd, how could I do so? If not, how could I use the automatic
> upgrade system without netbooting?
>
> Thank you
>
Hi,
For autoinstall, /auto_upgrade.conf is checked on the file system in
bsd.rd.
So you need to put your /auto_upgrade.conf file inside it.
There is no official method or tool for doing that, but it is possible:
see http://marc.info/?l=openbsd-misc&m=141552533922277&w=2 for a
possible way.
If I recall correctly, other examples exists in misc@.
Regards.
--
Sebastien Marie
