VGC-LV50DB: Intel G45: Xorg does not work in native 1920x1200 mode

2015-11-18 Thread OpenBSD user
Dear misc@,

It would be really nice if someone could give me any hint(s) on how to
get a native 1920x1200 working on VGC-LV50DB. As it is, only 1600x1200
works out of the box.

Right side of the monitor results in black 320(?)x1200, not usable space.
Panning (for 1920x1200) does work, but only in the 1600x1200 area.
Custom mode setting (through cvt) does not work either.

There are no related changeable values in the BIOS.

xrandr:
Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 32767 x 32767
LVDS1 connected 1600x1200+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
   1600x1200 60.00*+
VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768  60.00*
   800x600   60.3256.25
   848x480   60.00
   640x480   59.94
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


OpenBSD 5.8-current (GENERIC.MP) #1621: Mon Nov 16 14:03:33 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4074307584 (3885MB)
avail mem = 3946672128 (3763MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xfbb10 (17 entries)
bios0: vendor American Megatrends Inc. version "R0220T3" date 08/09/2008
bios0: Sony Corporation VGC-LV50DB
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG SLIC OEMB HPET GSCI SSDT
acpi0: wakeup devices P0P2(S4) P0P3(S4) P0P1(S4) USB0(S4) USB1(S4)
USB2(S4) USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4)
P0P4(S4) P0P5(S4) P0P6(S4) P0P7(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)2 Duo CPU E7200 @ 2.53GHz, 2521.02 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,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 275MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 2621.49 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,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (P0P1)
acpiprt2 at acpi0: bus 1 (P0P4)
acpiprt3 at acpi0: bus 2 (P0P5)
acpiprt4 at acpi0: bus -1 (P0P6)
acpiprt5 at acpi0: bus -1 (P0P7)
acpiprt6 at acpi0: bus 3 (P0P8)
acpiprt7 at acpi0: bus -1 (P0P9)
acpicpu0 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
cpu0: Enhanced SpeedStep 2521 MHz: speeds: 2533, 2136, 1870, 1603 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel G45 Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel G45 Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: msi
inteldrm0: 1024x768
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel G45 Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x2e24 (class communications subclass
miscellaneous, rev 0x03) at pci0 dev 3 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel ICH10 R BM V" rev 0x00: msi,
address 00:1d:ba:22:16:f2
uhci0 at pci0 dev 26 function 0 "Intel 82801JI USB" rev 0x00: apic 2 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801JI USB" rev 0x00: apic 2 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801JI USB" rev 0x00: apic 2 int 19
ehci0 at pci0 dev 26 function 7 "Intel 82801JI USB" rev 0x00: apic 2 int 18
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801JI HD Audio" rev 0x00: msi
azalia0: codecs: Realtek/0x0889
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801JI PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
athn0 at pci1 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 int 16
athn0: AR9280 rev 2 (1T2R), ROM rev 11, address 00:1f:e1:d4:c2:93
ppb1 at pci0 dev 28 function 1 "Intel 82801JI PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
vendor "Fujitsu", unknown product 0x2030 (class multimedia subclass
miscellaneous, rev 0x01) at pci2 dev 0 function 0 not configured
ppb2 at pci0 dev 28 function 4 "Intel 82801JI PCIE" rev 0x00: msi
pci3 at ppb2 bus 3
uhci3 at pci0 dev 29 

Re: VGC-LV50DB: Intel G45: Xorg does not work in native 1920x1200 mode

2015-11-18 Thread Jonathan Gray
On Wed, Nov 18, 2015 at 03:30:57PM +, OpenBSD user wrote:
> Dear misc@,
> 
> It would be really nice if someone could give me any hint(s) on how to
> get a native 1920x1200 working on VGC-LV50DB. As it is, only 1600x1200
> works out of the box.
> 
> Right side of the monitor results in black 320(?)x1200, not usable space.
> Panning (for 1920x1200) does work, but only in the 1600x1200 area.
> Custom mode setting (through cvt) does not work either.
> 
> There are no related changeable values in the BIOS.
> 
> xrandr:
> Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 32767 x 32767
> LVDS1 connected 1600x1200+0+0 (normal left inverted right x axis y
> axis) 0mm x 0mm
>1600x1200 60.00*+
> VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 
> 0mm
>1024x768  60.00*
>800x600   60.3256.25
>848x480   60.00
>640x480   59.94
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)

So the vga output isn't actually present/connected?

A bit of a long shot but you could try the following:

Index: sys/dev/pci/drm/i915/intel_display.c
===
RCS file: /cvs/src/sys/dev/pci/drm/i915/intel_display.c,v
retrieving revision 1.56
diff -u -p -r1.56 intel_display.c
--- sys/dev/pci/drm/i915/intel_display.c25 Sep 2015 09:42:14 -  
1.56
+++ sys/dev/pci/drm/i915/intel_display.c18 Nov 2015 15:57:22 -
@@ -10850,6 +10850,9 @@ static struct intel_quirk intel_quirks[]
/* Sony Vaio Y cannot use SSC on LVDS */
{ 0x0046, 0x104d, 0x9076, quirk_ssc_force_disable },
 
+   /* Sony VGC-LV50DB cannot use SSC on LVDS */
+   { 0x2e22, 0x104d, 0x9043, quirk_ssc_force_disable },
+
/* Acer Aspire 5734Z must invert backlight brightness */
{ 0x2a42, 0x1025, 0x0459, quirk_invert_brightness },



Re: tmux's utf vs my latin2

2015-11-18 Thread Stefan Sperling
On Wed, Nov 18, 2015 at 04:44:39PM +0100, Jan Stary wrote:
> This is current/amd64.
> With the recent addition of UTF to tmux,
> I apparently need to change something to be able
> to read my latin2 email etc as I did before.

IMO, since you're running -current, switch your locale to UTF-8 and
don't override charsets in applications (e.g. don't use 'set charset'
in muttrc).
If something is still broken then, let us know, and it will likely
improve over time. Most ports applications will just do the right thing.



Re: tmux's utf vs my latin2

2015-11-18 Thread Ted Unangst
Jan Stary wrote:
> This is current/amd64.
> With the recent addition of UTF to tmux,
> I apparently need to change something to be able
> to read my latin2 email etc as I did before.
> 
> Here is mutt reading an email written in Czech,
> (a) inside an xterm (b) inside tmux inside an xterm:
> 
> http://stare.cz/~hans/.tmp/mutt-xterm.jpg
> http://stare.cz/~hans/.tmp/mutt-tmux.jpg
> 
> Same thing happens with e.g. typing in vim:
> OK in a vim inside an xterm, not OK in vim inside tmux inside an xterm.
> 
> I set my XTerm*locale to ISO8859-2 (~/.Xrescources below),
> but apparently I need to tell that to the utf tmux.
> Am I missing something obvious?
> 
> Note that luti(1) is also involved in making
> ISO8859-2 available to my xterm.
> 
>  |   \-+- 18323 hans xinit /home/hans/.xinitrc -- /home/hans/.xserverrc :0 
> -auth /home/hans/.serverauth.qtZtR6DhMt
>  | |-+= 22909 hans Xorg -nolisten tcp
>  | | \--- 32623 root Xorg: [priv] (Xorg)
>  | \-+= 21393 hans sh /home/hans/.xinitrc
>  |   \-+- 08706 hans cwm
>  | |-+= 26831 hans xterm
>  | | \-+= 29949 hans /usr/X11R6/bin/luit -encoding ISO8859-2 -argv0 
> -ksh
>  | |   \-+= 23983 hans -ksh (ksh)
>  | | \--= 23111 root -ksh (ksh)

I was going to tell you about luit, though you've already seen it. xterm uses
it internally, but tmux doesn't. You can run it by hand too. "luit mutt"



tmux's utf vs my latin2

2015-11-18 Thread Jan Stary
This is current/amd64.
With the recent addition of UTF to tmux,
I apparently need to change something to be able
to read my latin2 email etc as I did before.

Here is mutt reading an email written in Czech,
(a) inside an xterm (b) inside tmux inside an xterm:

http://stare.cz/~hans/.tmp/mutt-xterm.jpg
http://stare.cz/~hans/.tmp/mutt-tmux.jpg

Same thing happens with e.g. typing in vim:
OK in a vim inside an xterm, not OK in vim inside tmux inside an xterm.

I set my XTerm*locale to ISO8859-2 (~/.Xrescources below),
but apparently I need to tell that to the utf tmux.
Am I missing something obvious?

Note that luti(1) is also involved in making
ISO8859-2 available to my xterm.

 |   \-+- 18323 hans xinit /home/hans/.xinitrc -- /home/hans/.xserverrc :0 
-auth /home/hans/.serverauth.qtZtR6DhMt
 | |-+= 22909 hans Xorg -nolisten tcp
 | | \--- 32623 root Xorg: [priv] (Xorg)
 | \-+= 21393 hans sh /home/hans/.xinitrc
 |   \-+- 08706 hans cwm
 | |-+= 26831 hans xterm
 | | \-+= 29949 hans /usr/X11R6/bin/luit -encoding ISO8859-2 -argv0 -ksh
 | |   \-+= 23983 hans -ksh (ksh)
 | | \--= 23111 root -ksh (ksh)


Jan



XTerm*termName: xterm-color
XTerm*message:  true
XTerm*cutNewline:   true
XTerm*cutToBeginningOfLine: true
! these should not break a "word"
XTerm*charClass:37:48,45-47:48,58:48,64:48,126:48
XTerm*toolBar:  false
!XTerm.keyboardType:vt220
XTerm*backarrowKeyIsErase:  false
!XTer*deleteIsDEL:  true
!XTerm.ptyInitialErase: true
!XTerm.ttyModes: TODO
XTerm*background:   black
XTerm*foreground:   white
XTerm*activeIcon:   false
XTerm*autowrap: true
XTerm*colorMode:true
XTerm*cursorBlink:  true
XTerm*backarrowKey: true
XTerm*dynamicColors:false
XTerm*loginShell:   true
XTerm*reverseWrap:  true
XTerm*scrollBar:false
!XTerm*scrollKey:   true
!XTerm*scrollLines: 1024
!XTerm*scrollTtyOutput: false
XTerm*saveLines:1024
XTerm*selectToClipboard:true
!XTerm*translations:TODO
XTerm*visualBell:   true
XTerm*pointerMode:  1

XTerm*eightBitInput:true
XTerm*eightBitOutput:   true
!XTerm*allowC1Printable:true
XTerm*locale:   ISO8859-2
!XTerm*font:  -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-2



KNFectomy

2015-11-18 Thread Adam Wolk
During the LibreSSL early days there were frequent KNFectomy procedures
executed by jsing@. Is the KNFectomy utensil script available
publicly? ;) man -k knf yields only style(9).

Regards,
Adam



Re: KNFectomy

2015-11-18 Thread Theo de Raadt
>Adam Wolk wrote:
>> During the LibreSSL early days there were frequent KNFectomy procedures
>> executed by jsing@. Is the KNFectomy utensil script available
>> publicly? ;) man -k knf yields only style(9).
>
>indent -ci4 -di1 -nlp $1
>
>That's not what joel used, but it's what i have in ~/bin/knf. It usually gets
>things close enough for some further refinement.

Until indent -- having come out of the back of a cow -- subtly screws
your source code and makes a mistake.

Be careful.



Re: KNFectomy

2015-11-18 Thread Theo de Raadt
>During the LibreSSL early days there were frequent KNFectomy procedures
>executed by jsing@. Is the KNFectomy utensil script available
>publicly? ;) man -k knf yields only style(9).

Most of those tools are kind of busy here and there hand-editing
files, compiling them, testing them.. and then commiting them..



Re: KNFectomy

2015-11-18 Thread Ted Unangst
Adam Wolk wrote:
> During the LibreSSL early days there were frequent KNFectomy procedures
> executed by jsing@. Is the KNFectomy utensil script available
> publicly? ;) man -k knf yields only style(9).

indent -ci4 -di1 -nlp $1

That's not what joel used, but it's what i have in ~/bin/knf. It usually gets
things close enough for some further refinement.



Re: VGC-LV50DB: Intel G45: Xorg does not work in native 1920x1200 mode

2015-11-18 Thread Lars

Hi,

On 18.11.2015 16:30, OpenBSD user wrote:

Dear misc@,

It would be really nice if someone could give me any hint(s) on how to
get a native 1920x1200 working on VGC-LV50DB. As it is, only 1600x1200
works out of the box.

Right side of the monitor results in black 320(?)x1200, not usable 
space.

Panning (for 1920x1200) does work, but only in the 1600x1200 area.
Custom mode setting (through cvt) does not work either.

There are no related changeable values in the BIOS.

xrandr:
Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 32767 x 32767
LVDS1 connected 1600x1200+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
   1600x1200 60.00*+
VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1024x768  60.00*
   800x600   60.3256.25
   848x480   60.00
   640x480   59.94
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


I have a related problem and solved it partly by some BIOS settings and 
xrandr.


My Asus Board has a buggy BIOS that screws with the screens attached to 
the system. In my BIOS the LVDS connector can be turned off but all that 
is happening is that the connector is still active with a default 
resolution of 1024*768. Whenever I boot an OS (Windows, OpenBSD, 
FreeBSD, Linux) I get 2 screens that are shown as connected - LVDS with 
1024*768 and HDMI with my actual screen attached. My BIOS also allows me 
to use a predefined resolution for the LVDS which might help in your 
case as well. It is possible that your BIOS has a predefined setting of 
1600x1200 set as active. In that case xorg is not able to use anything 
else as this is the native resolution.


So try to find something that allows you to influence the LVDS settings 
in your BIOS.


To disable the unused outputs you can use xrandr by putting something 
like the following into your .xinitrc:


xrandr --output VGA1 --off

You can also try to create a new mode with xrandr to teach xorg that 
LVDS has alternative resolutions. I did something like this for my 
screen that is attached to HDMI. Please note that you cannot copy the 
lines from me because the values for this are generated according to 
your screen. Please look around on the net (Archlinux wiki) to find more 
articles how to find those values:


xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 
1443 1448 1493 -hsync +vsync

xrandr --addmode HDMI1 2560x1440_60.00
xrandr --output HDMI1 --mode 2560x1440_60.00

In my case the side effect of having the pseudo screen on LVDS causes my 
ttys to be stuck at 1024*768 as OpenBSD finds the LVDS connector first 
and ignores the HDMI connector with the correct screen resolution. 
Interestingly the only OS that immediately finds the correct screen and 
switches to the correct resolution is NetBSD. I don't know what they do 
differently in this regard but they get it right from the start and I 
have my native 2560*1440 also on tty.


Sorry, no dmesg this time as the system is currently running Linux. If 
there is interest in a Linux dmesg I can provide it.


regards
Lars



Re: EFI: Booting from other (not the first) GPT partition possible? How? It's an Apple :-O

2015-11-18 Thread Gonzalo L. Rodriguez
Hello,

I'm kinda at the same step, but in a macbookpro12,1

I resize my OSX partition, burn a install58.fs on a usb stick, boot 
holding ALT, install OpenBSD on the part of resize partition, and then 
follow jcs@ tutorial:

https://gist.github.com/jcs/5573685

Now, "El Capitan" have like a 'Secure Level' thing that you can do the 
step Mac OS X Encryption -> 3-6. So, you need to boot on Rescue Mode and 
disable this new protection from the console on rescue mode:

# csrutil disable

Then reboot, and try the "Mac OS X Encryption" step. Install refind and 
cross your fingers :)


On 16/11, Marcel Timm wrote:
; Hi there,
; 
; one thing I would like to try is to boot from created OpenBSD EFI USB stick
; with
; 
; boot -a
; 
; and enter the OpenBSD's root partition on the HD.
; 
; Unfortunately neither the MacBook Pro 8,2 's integrated
; nor an external USB keyboard work at the prompt where to enter the
; root device's location. :(
; 
; Is there another way of telling the kernel which root device to use
; (maybe at boot's prompt - although I haven't found anything in man page..)?
; 
; If this seems to be a XY question to you, I am happy about other proposals.
; 
; Greetings
; Marcel
; 
; On 11.11.2015 16:01, Marcel Timm wrote:
; >Hello!
; >
; >My computer is a MacBook Pro 8,2.
; >
; >There is a GPT on the HD (big surprise!) with four partitions,
; >the last one being of type OpenBSD.
; >
; >I managed to put a recent OpenBSD 5.8 snapshot there
; >by booting and installing from an USB stick via EFI created like that (in
; >OSX):
; >
; >dd if=~/install58.fs of=/dev/rdisk2 bs=1m
; >
; >After installing rEFInd 0.9.2 and putting OpenBSD 5.8 snapshot's
; >BOOTX64.EFI file
; >to the MacBook's EFI partition the rEFInd boot manager shows the OpenBSD
; >EFI option.
; >
; >Selecting that OpenBSD entry starts the boot programm showing hd0 hd1 hd2
; >and hd3.
; >
; >Is it possible to boot my "EFI OpenBSD installation" from here?
; >If so, how to proceed?
; >
; >I already played with
; >
; >set device hd0d
; >
; >etc. - but it did not work.
; >
; >I will gladly share more details, if of any help.
; >
; >Thanks in advance!
; >
; >Marcel
; 

-- 
Sending from my toaster.



Re: Azalia Volume Too Quiet

2015-11-18 Thread Raf Czlonka
On Wed, Nov 18, 2015 at 02:27:21PM GMT, Stefan Wollny wrote:
> Am 11/18/15 um 01:43 schrieb Daniel Wilkins:
> >When I try to play sounds on my Thinkpad T430 I find that the audio's rather
> >quiet, I've experimented a bit and found that at about 170 (mixerctl
> >outputs.master=170) the volume stops increasing. It just stays constant from
> >170 to 255, or at least the change is so quiet that I can't hear it. I've 
> >looked
> >around in the driver a little bit, but I'm no kernel hacker, the only thing I
> >noticed that might help is that for a few widgets outamp (I'm assuming output
> >amplify?) is muted.
> >
> 
> Check the following:
> $ mixerctl outputs.master
> 
> Most likely it is s.th. like "120,120". Try setting it to "245,245" (either
> with doas/sudo or su to root).
> 
> If it fits your needs, cp mixerctl.conf from /etc/examples to /etc and set
> the variable accordingly to make this setting permanent.

Stefan, the OP already mentioned (see above) that he had already tried
that and it stays constant.

On my machine, increasing the volume on 'outputs.mixY', where 'Y' is
'2', did the trick.

Setting 'outputs.hp_boost=on' (for headphones) may increase the volume
further.

Regards,

Raf



FOSDEM 2016 CFP

2015-11-18 Thread Sergey Bronnikov
Hi, everyone.

FOSDEM 2016 (the free and open source developer's meeting in Brussels, Europe)
will feature a new track on Containers and Process isolation [1]. Therefore, we
invite developers and users from the containers community to join us for this
track and present your talks or demos [2].

[1] https://openvz.org/FOSDEM2016
[2] https://lists.openvz.org/pipermail/users/2015-November/006601.html

Sergey



Re: OpenSMTPD problem with filter-dnsbl

2015-11-18 Thread Gregory Edigarov

On 11/17/2015 09:03 PM, Gianluca D.Muscelli wrote:

Hi, I'v problem with filters in OpenSMTPD.
I would try to implement the filter-dnsbl,
I also installed the extras opensmtpd but I can't find it!
Any suggestions??
Thank you!

The filters are not available in stock version of smtpd, you should 
install recent version from git for this.

But be aware of some trade offs here.



Re: Azalia Volume Too Quiet

2015-11-18 Thread Stefan Wollny

Am 11/18/15 um 01:43 schrieb Daniel Wilkins:

When I try to play sounds on my Thinkpad T430 I find that the audio's rather
quiet, I've experimented a bit and found that at about 170 (mixerctl
outputs.master=170) the volume stops increasing. It just stays constant from
170 to 255, or at least the change is so quiet that I can't hear it. I've looked
around in the driver a little bit, but I'm no kernel hacker, the only thing I
noticed that might help is that for a few widgets outamp (I'm assuming output
amplify?) is muted.



Check the following:
$ mixerctl outputs.master

Most likely it is s.th. like "120,120". Try setting it to "245,245" 
(either with doas/sudo or su to root).


If it fits your needs, cp mixerctl.conf from /etc/examples to /etc and 
set the variable accordingly to make this setting permanent.


Best,
STEFAN



Re: KNFectomy

2015-11-18 Thread Marios Makassikis
On 18 November 2015 at 22:45, Adam Wolk  wrote:
> On Wed, 18 Nov 2015 11:38:55 -0700 (MST)
> Theo de Raadt  wrote:
>
>> >Adam Wolk wrote:
>> >> During the LibreSSL early days there were frequent KNFectomy
>> >> procedures executed by jsing@. Is the KNFectomy utensil script
>> >> available publicly? ;) man -k knf yields only style(9).
>> >
>> >indent -ci4 -di1 -nlp $1
>> >
>> >That's not what joel used, but it's what i have in ~/bin/knf. It
>> >usually gets things close enough for some further refinement.
>
> I'm afraid of tools that redirect me to rcs(1) KEYWORD SUBSTITUTION
> documentation in order to be able to decipher their flags :P Though I
> do appreciate the info, might be desperate enough on some occasions to
> try it out - who am I kidding, I will try it :)
>
>>
>> Until indent -- having come out of the back of a cow -- subtly screws
>> your source code and makes a mistake.
>>
>> Be careful.
>>
>
> Thanks for the heads up. I just had a few occasions lately that I had
> to incorporate some broken formatted C code into a project and was
> searching for a 'general pass make my eyes not bleed' like tool.
>
> Regards,
> Adam
>

Hello,

You may have better luck with clang-format :

http://clang.llvm.org/docs/ClangFormat.html

The Linux Kernel Style looks fairly close to KNF, so it can serve as
a base configuration (it's all the way down in the examples section) :

http://clang.llvm.org/docs/ClangFormatStyleOptions.html

Marios



Re: Azalia Volume Too Quiet

2015-11-18 Thread Daniel Wilkins
Oh, a quick self reply:
I've noticed that when I look in audioctl, if I have
just oss then lowat = hiwat = 25, with sndio running
lowat = hiwat = 8. Not sure if this is helpful information.



Re: Azalia Volume Too Quiet

2015-11-18 Thread Daniel Wilkins
On Wed, Nov 18, 2015 at 08:15:08PM +, Raf Czlonka wrote:
> Stefan, the OP already mentioned (see above) that he had already tried
> that and it stays constant.
> 
> On my machine, increasing the volume on 'outputs.mixY', where 'Y' is
> '2', did the trick.
> 
> Setting 'outputs.hp_boost=on' (for headphones) may increase the volume
> further.
> 
> Regards,
> 
> Raf
> 

I haven't got an outputs.mixY on my box, I'm afraid. There are references in 
other
values to a mix2 though, like outputs.spkr2_source=mix2. There *is* an 
inputs.mix_spkr{2,3}.
Changing them gives me an extra 10 units of volume (170 is distinguishable from 
255, 180 is not).
mixerctl output:

inputs.dac-0:1=150,150
inputs.dac-2:3=150,150
record.adc-2:3_mute=off
record.adc-2:3=124,124
record.adc-0:1_mute=off
record.adc-0:1=124,124
inputs.mix_source=mic2,spkr2,spkr3,beep
inputs.mix_mic2=120,120
inputs.mix_spkr2=248,248
inputs.mix_spkr3=248,248
inputs.mix_beep=120,120
inputs.mix2_source=dac-0:1,mix
inputs.mix3_source=dac-2:3,mix
inputs.mic=85,85
outputs.spkr_source=mix3
outputs.spkr_mute=off
outputs.spkr_eapd=on
outputs.hp_source=mix2
outputs.hp_mute=off
outputs.hp_boost=off
outputs.hp_eapd=on
outputs.mic2_source=mix2
outputs.mic2_mute=off
inputs.mic2=85,85
outputs.mic2_dir=input-vr80
outputs.spkr2_source=mix2
outputs.spkr2_mute=off
inputs.spkr2=255,255
outputs.spkr2_dir=output
outputs.spkr3_source=mix2
outputs.spkr3_mute=off
inputs.spkr3=255,255
outputs.spkr3_dir=output
record.adc-0:1_source=mic2,spkr2,spkr3,beep,mix,mic
record.adc-2:3_source=mic2,spkr2,spkr3,beep,mix
outputs.hp_sense=unplugged
outputs.mic2_sense=unplugged
outputs.spkr_muters=hp,mic2
outputs.master=151,151
outputs.master.mute=off
outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp,spkr2,spkr3
record.volume=124,124
record.volume.mute=off
record.volume.slaves=adc-2:3,adc-0:1



Re: KNFectomy

2015-11-18 Thread Adam Wolk
On Wed, 18 Nov 2015 11:38:55 -0700 (MST)
Theo de Raadt  wrote:

> >Adam Wolk wrote:
> >> During the LibreSSL early days there were frequent KNFectomy
> >> procedures executed by jsing@. Is the KNFectomy utensil script
> >> available publicly? ;) man -k knf yields only style(9).
> >
> >indent -ci4 -di1 -nlp $1
> >
> >That's not what joel used, but it's what i have in ~/bin/knf. It
> >usually gets things close enough for some further refinement.

I'm afraid of tools that redirect me to rcs(1) KEYWORD SUBSTITUTION
documentation in order to be able to decipher their flags :P Though I
do appreciate the info, might be desperate enough on some occasions to
try it out - who am I kidding, I will try it :)

> 
> Until indent -- having come out of the back of a cow -- subtly screws
> your source code and makes a mistake.
> 
> Be careful.
> 

Thanks for the heads up. I just had a few occasions lately that I had
to incorporate some broken formatted C code into a project and was
searching for a 'general pass make my eyes not bleed' like tool.

Regards,
Adam