Re: OpenBSD 5.6/current on Soekris 6501-70
On 2014-12-08, Martin Hanson greencopperm...@yandex.com wrote: I would like to be able to run ~100-120 MB/s from one NIC to the other on this box, if possible? MB/s (megabytes): no. Mb/s (megabits): yes.
Re: OpenBSD 5.6/current on Soekris 6501-70
On Mon, Dec 08, 2014 at 12:53:32AM +0100, Martin Hanson wrote: Hi, Anyone running OpenBSD 5.6 or current on Soekris 6501-70 who wouldn't mind sharing some through-put data for gigabit performance. Regards, MH Hi, I can't tell you how much the Soekris 6501-70 does with plaintext traffic. But in an iked setup and AES encryption and no VPN card I get about 35 Mbps give or take 5 Mbps. In my setup the 6501-70 is between a Lanner 7530B firewall also with an Atom CPU (but i386)... Hope that helps, if any... Regards, -peter
OpenSMTPD: SMTP_LIMIT_MAIL and SMTP_LIMIT_RCPT
Hello @list, are there any plans for those constants to be configurable via smtpd.conf? //mxb
Re: OpenBSD 5.6/current on Soekris 6501-70
We have exactly this model. tcpbench from base gave only around 340Mbit/s on those. So CPU is probably one problem on those boards. tcpbench done against 1U machines with better CPU and doing almost line rate on 1G NIC. //mxb On 8 dec 2014, at 00:53, Martin Hanson greencopperm...@yandex.com wrote: Hi, Anyone running OpenBSD 5.6 or current on Soekris 6501-70 who wouldn't mind sharing some through-put data for gigabit performance. Regards, MH
Re: OpenSMTPD: SMTP_LIMIT_MAIL and SMTP_LIMIT_RCPT
On Mon, Dec 08, 2014 at 11:00:50AM +0100, mxb wrote: Hello @list, are there any plans for those constants to be configurable via smtpd.conf? yes, they are actually already configurable in my sandbox thanks to a diff from a user, however not committed to OpenBSD yet. out of curiosity, why are you unhappy with the defaults ? -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: OpenSMTPD: SMTP_LIMIT_MAIL and SMTP_LIMIT_RCPT
We do a lot of bulk mails and not via local smtp, eg. PHP-code talks directly to opensmtpd. opensmtpd used as internal relay/smart host. I had to higher limits for those two in order to escape 452 4.5.3 Too many recipients: Too many messages sent “ //mxb On 8 dec 2014, at 11:14, Gilles Chehade gil...@poolp.org wrote: On Mon, Dec 08, 2014 at 11:00:50AM +0100, mxb wrote: Hello @list, are there any plans for those constants to be configurable via smtpd.conf? yes, they are actually already configurable in my sandbox thanks to a diff from a user, however not committed to OpenBSD yet. out of curiosity, why are you unhappy with the defaults ? -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: OpenBSD 5.6/current on Soekris 6501-70
On 12/08/14 05:12, mxb wrote: We have exactly this model. tcpbench from base gave only around 340Mbit/s on those. So CPU is probably one problem on those boards. tcpbench done against 1U machines with better CPU and doing almost line rate on 1G NIC. I didn't want to quote any particular numbers as I do not have any benchmarks but I was thinking in the hundreds of Mb/s range but not really high. The unfortunate reality is systems of this class are fine for low end to mid range use but are CPU limited for anything further. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: OpenSMTPD: SMTP_LIMIT_MAIL and SMTP_LIMIT_RCPT
Stupid question but... why not catch the 4xx error and reestablish a new connection ? The limits are here for a purpose and bumping them to work-around a lack of check in some PHP code doesn't strike me as a good idea. No matter the value you set, value + 1 will still hit the check, while a very large value will open your servers to some attacks. On Mon, Dec 08, 2014 at 11:24:21AM +0100, mxb wrote: We do a lot of bulk mails and not via local smtp, eg. PHP-code talks directly to opensmtpd. opensmtpd used as internal relay/smart host. I had to higher limits for those two in order to escape 452 4.5.3 Too many recipients: Too many messages sent ??? //mxb On 8 dec 2014, at 11:14, Gilles Chehade gil...@poolp.org wrote: On Mon, Dec 08, 2014 at 11:00:50AM +0100, mxb wrote: Hello @list, are there any plans for those constants to be configurable via smtpd.conf? yes, they are actually already configurable in my sandbox thanks to a diff from a user, however not committed to OpenBSD yet. out of curiosity, why are you unhappy with the defaults ? -- Gilles Chehade https://www.poolp.org @poolpOrg -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: apmd.8 lacks of hibernation quirks info
Hello Mike, On Sun 07/12 10:58, Mike Larkin wrote: Which machines don't work, and how do they break? I would like to know. Please file a bug report (man sendbug). Last time I tried hibernation on my ThinkPad R61 (running current) was some months ago and, even being both sleep and resume functional, they were too slow to be practical (some minutes for sleeping, more than 20 for resuming). When I discovered a fully working hibernation/resume on a Compaq 610 laptop with a brand new 5.6, I thought to a good hardware support for that particular machine. After your message, I retried hibernation on the R61 (with the very last snapshot, by the way), and it works flawlessly there too! So I can report only excellent results! Thanks a lot for your work. Any comments on the two points that I highlighted in my OP? -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: USB printer not working with CUPS 2.0.1 (in -current)
Hello Antoine, On Sat 06/12 12:28, Antoine Jacoutot wrote: Actually, I just hooked up my HP USB printer and was able to print just fine... Oop sorry I meant to answer that in previous: just22@poseidon:[~] ll /etc/cups/printers.conf -rw--- 1 root _cups 897B Dec 3 08:58 /etc/cups/printers.conf (not readable by _cups?) That's fine. cupsd starts as root, read its config and then drops privileges to _cups. At this point, I'm completely out of ideas... Maybe a regression specific to that particular PPD? Just wait and see what happens with future updates... Just to give you a more complete picture, I tried to remove/reinstall cups and hplip, wiping out all the related directories, just in case of some strange side effects related to previous configs, without any luck. Of course, if you have anything else to suggest in order to help the debug, please let me know. All the best -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: USB printer not working with CUPS 2.0.1 (in -current)
On Mon, Dec 08, 2014 at 04:05:31PM +0100, Alessandro DE LAURENZIS wrote: Hello Antoine, On Sat 06/12 12:28, Antoine Jacoutot wrote: Actually, I just hooked up my HP USB printer and was able to print just fine... Oop sorry I meant to answer that in previous: just22@poseidon:[~] ll /etc/cups/printers.conf -rw--- 1 root _cups 897B Dec 3 08:58 /etc/cups/printers.conf (not readable by _cups?) That's fine. cupsd starts as root, read its config and then drops privileges to _cups. At this point, I'm completely out of ideas... Maybe a regression specific to that particular PPD? Just wait and see what happens with future updates... Just to give you a more complete picture, I tried to remove/reinstall cups and hplip, wiping out all the related directories, just in case of some strange side effects related to previous configs, without any luck. Of course, if you have anything else to suggest in order to help the debug, please let me know. Were is your ppd coming from? Did you generate it yourself? -- Antoine
Re: USB printer not working with CUPS 2.0.1 (in -current)
On Mon, Dec 08, 2014 at 10:05:31AM EST, Alessandro DE LAURENZIS wrote: Hi Alessandro, Of course, if you have anything else to suggest in order to help the debug, please let me know. As Antoine has pointed out: AJ The issue is not with USB printing per se but with the HPLIP AJ driver with a USB printer. I have several USB printers that AJ I use without issue. AJ There's probably a regression in HLIP after CUPS got updated AJ to version 2. I'll try and look into it but don't hold your AJ breath too soon... or maybe a future HPLIP release will fix this. That may as well be true but I wanted to double-check whether your issue is at all related to the recent USB 3.0/xhci changes in -current? The reason I mention it is the fact that several people have reported issues with USB 1.x and/or USB 2.0 devices while using USB 3.0 ports. Regards, Raf
Re: DNS: how to verify glue NS records?
Thanks to all for your replies but... I'm sorry for the misleading Subject of this thread, I meant delegation NS records (not glue records). Below is the answer from bind-us...@lists.isc.org. -- Alexei Original Message Subject: Re: DNS: how to verify glue NS records? Date: Fri, 5 Dec 2014 10:39:28 -0500 From: Casey Deccio ca...@deccio.net To: Alexei Malinin alexei.mali...@mail.ru CC: Bind Users bind-us...@lists.isc.org Hi Alexei, On Fri, Dec 5, 2014 at 10:16 AM, Alexei Malinin alexei.mali...@mail.ru wrote: I would like to resolve this problem: - I have a child DNS zone served by my ISP slave name server; - the parent zone is served by my ISP master name server; - the question is - how and with what tools (dig, host, nslookup, or maybe C or Perl libs) can I verify the NS glue records in the parent zone of my ISP (zone transfers are denied)? The delegation NS records (i.e., the NS records in the parent zone) cannot be determined using simple queries because the parent zone is also authoritative for the child zone, as you mentioned. Thus, when one of those servers (e.g., ns1.agtel.net) is queried for 0-15.66.233.212.in-addr.arpa/NS, the server will (should) always send the authoritative NS RRset in (i.e., from the child) preference to the delegation NS RRset (i.e., in the parent), and in fact the latter may be different. There are by definition no glue records for your zone. Glue A/ records are only required in the parent for NS targets that are subdomains of the delegated child zone to bootstrap resolution. For example, ns1.example.com as an NS target for example.com. That is not the case with yours (and usually isn't with in-addr.arpa zones). My child zone is 0-15.66.233.212.in-addr.arpa. I tried dig -4 +multiline +showsearch +trace 0-15.66.233.212.in-addr.arpa ns but it was not possible to make any conclusions about NS glue records from the dig output. . I found some tools in the Internet (for example http://www.intodns.com/0-15.66.233.212.in-addr.arpa, see Missing nameservers reported by parent) but these are inconvenient, I would like to use OS tools. That's unfortunately a misleading error, as this cannot be determined, as I mentioned above. Please give me some good advise. You'll need to take the word of the operator of your parent zone. Casey
Re: USB printer not working with CUPS 2.0.1 (in -current)
Hello Antoine, On Mon 08/12 16:11, Antoine Jacoutot wrote: Were is your ppd coming from? Did you generate it yourself? Not at all, it comes from hpcups: Description:HP Deskjet F4280 All-in-One Location: Driver: HP Deskjet f4200 Series, hpcups 3.14.6 (color, 2-sided printing) Connection: hp:/usb/Deskjet_F4200_series?serial=CN8C54F12J05BR Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: USB printer not working with CUPS 2.0.1 (in -current)
Hi Raf, On Mon 08/12 10:39, Raf wrote: That may as well be true but I wanted to double-check whether your issue is at all related to the recent USB 3.0/xhci changes in -current? The reason I mention it is the fact that several people have reported issues with USB 1.x and/or USB 2.0 devices while using USB 3.0 ports. Laptop's USB ports are 2.0; I do not know if there could be an impact of the xhci driver anyway, but how could I check? Any chances to switch off xhci and revert to uhci/ehci? -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: sensorsd, upd, and state changes
On Sun, Nov 30, 2014 at 10:54 AM, Marcus MERIGHI mcmer-open...@tor.at wrote: for the impatient, here are my questions: - Although I use the same (undocumented, undeadly.org) trick of low=1:high=2 for indicators everywhere, this can result in On is below On, and Off is below On - Although I use low=1:high=2, I get On for %3 (low limit) as well as for %4 (high limit) - Reading sensorsd.conf(5): If the limits are crossed or if the status provided by the driver changes, sensorsd(8)'s alert functionality is triggered and a command, if specified, is executed If limits are crossed, yes; if status changes, no, unless you use the low=1:high=2 trick. - Reading sensorsd.conf(5): Values for all other types of sensors can be specified in the same units as they appear under the sysctl(8) hw.sensors tree. No: low=Off:high=On results in (sensorsd -c 1 -d): sensorsd: incorrect value: Off: file or directory not found Now that I have a reporting upd(4) device, I've had a chance to poke at this. There is currently no code in upd(4) that sets WARN or CRITICAL. Yes, it appears that SENSOR_INDICATOR items require numeric high/low values. This is not documented in sensorsd.conf(5). It is either an oversight in documentation or parsing. I've found that it helps to think of the high/low values in sensorsd.conf(5) as the closed interval for normal operation. The example hw.sensors.lm0.volt3:low=4.8V:high=5.2V will trigger when the voltage goes below (but not at) 4.8V and above (but not at) 5.2V. sysctl(8) will display Off if the value is zero, and On for nonzero. So, using the closed interval rule above, you should use high=0 for indicators that you consider in good state when Off (i.e. ShutdownImminent), and low=1 for indicators that you consider in good state when On (i.e. ACPresent). # sensorsd.conf(5) hw.sensors.upd0.indicator0:high=0:command=/etc/sensorsd_log.sh %x Charging %2 %s hw.sensors.upd0.indicator1:high=0:command=/etc/sensorsd_log.sh %x Discharging %2 %s hw.sensors.upd0.indicator2:low=1:command=/etc/sensorsd_log.sh %x ACPresent %2 %s hw.sensors.upd0.indicator3:high=0:command=/etc/sensorsd_log.sh %x ShutdownImminent %2 %s hw.sensors.upd0.indicator4:low=1:command=/etc/sensorsd_log.sh %x BatteryPresent %2 %s hw.sensors.upd0.percent0:low=25:command=/etc/sensorsd_log.sh %x RemainingCapacity %2 %s hw.sensors.upd0.percent1:low=25:command=/etc/sensorsd_log.sh %x FullChargeCapacity %2 %s --david
Re: sensorsd, upd, and state changes
On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote: sysctl(8) will display Off if the value is zero, and On for nonzero. So, using the closed interval rule above, you should use high=0 for indicators that you consider in good state when Off (i.e. ShutdownImminent), and low=1 for indicators that you consider in good state when On (i.e. ACPresent). Isn't saying high=0 kind of the same thing as saying low=1? Why is there a high/low for binary indicators at all? If the state changes, execute the command. Let the command read the state and determine, based on which indicator it is, if that state is a good thing or a bad thing. Tim.
Re: sensorsd, upd, and state changes
On Mon, Dec 8, 2014 at 3:23 PM, trondd tro...@gmail.com wrote: On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote: sysctl(8) will display Off if the value is zero, and On for nonzero. So, using the closed interval rule above, you should use high=0 for indicators that you consider in good state when Off (i.e. ShutdownImminent), and low=1 for indicators that you consider in good state when On (i.e. ACPresent). Isn't saying high=0 kind of the same thing as saying low=1? Oh, I think I get this. Since the sensor doesn't trigger if it is on the limit, only outside the limit, you have to set up which is the OK state. Still a little confusing but I guess there is no way to automatically know if an indicator is supposed to be Off or On when it's in it's good state? Tim.
Re: sensorsd, upd, and state changes
On Mon, Dec 8, 2014 at 3:37 PM, trondd tro...@gmail.com wrote: On Mon, Dec 8, 2014 at 3:23 PM, trondd tro...@gmail.com wrote: On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote: sysctl(8) will display Off if the value is zero, and On for nonzero. So, using the closed interval rule above, you should use high=0 for indicators that you consider in good state when Off (i.e. ShutdownImminent), and low=1 for indicators that you consider in good state when On (i.e. ACPresent). Isn't saying high=0 kind of the same thing as saying low=1? Oh, I think I get this. Since the sensor doesn't trigger if it is on the limit, only outside the limit, you have to set up which is the OK state. Still a little confusing but I guess there is no way to automatically know if an indicator is supposed to be Off or On when it's in it's good state? Kind of. The high/low difference is what values you consider within normal operating parameters (and the output of %l). The upd(4) code hasn't yet been taught how to map specific indicator values to OK / WARN / CRITICAL status. Currently any value successfully read is marked OK. I'm working with tech@ and slowly writing diffs to improve these things. --david
Re: CVS: cvs.openbsd.org: ports
2014-12-08 23:33 GMT+03:00 Vadim Zhukov z...@cvs.openbsd.org:
CVSROOT:/cvs
Module name:ports
Changes by: z...@cvs.openbsd.org2014/12/08 13:33:51
Log message:
Import Qt 5.3.2.
Qt is a full development framework with tools designed to streamline
the creation of applications and user interfaces for desktop,
embedded, and mobile platforms.
This port is not enabled yet, because some ports will pick up Qt5
instead of Qt4, breaking build. Those will be fixed separately soon.
There are some non-critical things left to do:
1. Support for OpenBSD sensors framework.
2. V4L2 support.
3. -L${LOCALBASE}/* could come before -L${WRKBUILD}/* when linking is
done across Qt module boundaries. This means that builds of Qt 5.y
while having Qt 5.x installed (x y) will be busted.
Volunteers are welcome to come in and help fixing those problems.
Last note: don't even try to build debug FLAVOR unless you know
what you're doing and you have about 20GB of free space. You've
been warned.
landry@ agrees on continuing working in-tree
Status:
Vendor Tag: zhuk
Release Tags: zhuk_20141208
N ports/x11/qt5/Makefile
N ports/x11/qt5/distinfo
N ports/x11/qt5/qt5.port.mk
N ports/x11/qt5/patches/patch-qtbase_src_corelib_kernel_qcore_unix_p_h
N
ports/x11/qt5/patches/patch-qtbase_src_network_kernel_qdnslookup_unix_cpp
N
ports/x11/qt5/patches/patch-qtbase_src_network_socket_qnativesocketengine_unix_cpp
N ports/x11/qt5/patches/patch-qtbase_mkspecs_openbsd-g++_qmake_conf
N ports/x11/qt5/patches/patch-qtbase_qmake_generators_unix_unixmake2_cpp
N ports/x11/qt5/patches/patch-qtbase_qmake_generators_unix_unixmake_cpp
N ports/x11/qt5/patches/patch-qtbase_config_tests_unix_iconv_iconv_pro
N ports/x11/qt5/patches/patch-qtbase_src_corelib_io_qfilesystemwatcher_cpp
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_config_tests_gccdepends_gccdepends_pro
N
ports/x11/qt5/patches/patch-qtbase_config_tests_unix_pulseaudio_pulseaudio_pro
N ports/x11/qt5/patches/patch-qtbase_configure
N
ports/x11/qt5/patches/patch-qtbase_src_concurrent_qtconcurrentiteratekernel_cpp
N ports/x11/qt5/patches/patch-qtbase_src_gui_image_qxbmhandler_cpp
N
ports/x11/qt5/patches/patch-qtbase_src_network_kernel_qnetworkinterface_cpp
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_config_tests_libXcomposite_libXcomposite_pro
N ports/x11/qt5/patches/patch-qtwebkit_Source_WebCore_Target_pri
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_config_tests_libXrender_libXrender_pro
N ports/x11/qt5/patches/patch-qtdeclarative_src_qml_jit_qv4assembler_cpp
N
ports/x11/qt5/patches/patch-qtdeclarative_src_qml_jsruntime_qv4engine_cpp
N ports/x11/qt5/patches/patch-qtwebkit_Source_WebKit2_WebProcess_pro
N
ports/x11/qt5/patches/patch-qtscript_src_3rdparty_javascriptcore_WebKit_pri
N ports/x11/qt5/patches/patch-qtwebkit_Source_WTF_wtf_Platform_h
N ports/x11/qt5/patches/patch-qtbase_qmake_generators_makefile_cpp
N
ports/x11/qt5/patches/patch-qtsensors_src_plugins_sensors_dummy_dummy_pro
N
ports/x11/qt5/patches/patch-qtwebkit_Source_JavaScriptCore_heap_MachineStackMarker_cpp
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_mkspecs_features_default_pre_prf
N
ports/x11/qt5/patches/patch-qtwebkit_Source_WebKit2_Platform_CoreIPC_unix_ConnectionUnix_cpp
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_mkspecs_features_functions_prf
N ports/x11/qt5/patches/patch-qtbase_mkspecs_features_qt_build_paths_prf
N
ports/x11/qt5/patches/patch-qttools_src_assistant_clucene_qclucene-config_p_h
N ports/x11/qt5/patches/patch-qtbase_qmake_Makefile_unix
N
ports/x11/qt5/patches/patch-qtdeclarative_src_3rdparty_masm_wtf_Platform_h
N
ports/x11/qt5/patches/patch-qtwebkit_Tools_qmake_config_tests_glx_glx_pro
N
ports/x11/qt5/patches/patch-qtscript_src_3rdparty_javascriptcore_JavaScriptCore_JavaScriptCore_pri
N ports/x11/qt5/pkg/PLIST-examples
N ports/x11/qt5/pkg/PLIST-html
N ports/x11/qt5/pkg/PLIST-main
N ports/x11/qt5/pkg/PLIST-mysql
N ports/x11/qt5/pkg/PLIST-psql
N ports/x11/qt5/pkg/PLIST-sqlite2
N ports/x11/qt5/pkg/PLIST-tds
N ports/x11/qt5/pkg/DESCR-examples
N ports/x11/qt5/pkg/DESCR-html
N ports/x11/qt5/pkg/DESCR-main
N ports/x11/qt5/pkg/DESCR-mysql
N ports/x11/qt5/pkg/DESCR-psql
N ports/x11/qt5/pkg/DESCR-sqlite2
N ports/x11/qt5/pkg/DESCR-tds
No conflicts created by this import
Forgot to mention one of the main points here: work on this project
was promised by me to beck@ (and this was totally my own idea from the
beginning!), as to one of the OpenBSD Foundation directors, after
realizing that new shiny X240 is really coming to me. And this port
won't be possible for me to even
Re: sensorsd, upd, and state changes
On Mon, Dec 8, 2014 at 3:45 PM, David Higgs hig...@gmail.com wrote: I'm working with tech@ and slowly writing diffs to improve these things. --david I saw that. Thanks! Tim.
Re: OpenBSD 5.6/current on Soekris 6501-70
On Sun, Dec 7, 2014 at 8:48 PM, jungle Boogie jungleboog...@gmail.com wrote: Hi Gene, On 7 December 2014 at 20:39, Gene gh5...@gmail.com wrote: I mentioned it one of those threads, I have the 2550L2D-MxPC and one of the NICs died after nine months of use. I might just be unlucky, but I feel its worth mentioning. I probably glossed right over that post. Would you still recommend the 2550L2D-MxPC or move on to something more? I cannot recommend the 2550L2D-MxPC be used in any capacity, Regarding the brand 'OEM Production' that's the only unit on newegg.com with dual LAN. From a brief search the other day, this Jetaway looks appealing, too, but it is slightly more expensive and has fewer reviews: http://www.newegg.com/Product/Product.aspx?Item=N82E16856107095cm_re=mini_pc-_-56-107-095-_-Product It does have intel NICs and way more sata ports. If you're gonna go that route take a look at the ASRock AD2550R/U3S3 motherboard. -Gene -jb --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: Proposed patch to unmute Azalia sound card on Compaq 610
I'm curious why you decided to mask the subid here and not just test
subid == 0x308a103c ?
On Sun, Dec 07, 2014 at 03:46:13PM +0100, Alessandro DE LAURENZIS wrote:
Greetings,
Some days ago I installed OBSD 5.6 on my old Compaq 610 laptop (a pretty
standard CORE2 Duo 2010 machine - yes, I know that standard is a
kind of hard concept in the i386/amd64 world...), dmesg in [1].
Great hardware support, except that sound card was completely silent
(dmesg with AZALIA_DEBUG in [2], mixerctrl in [3], audioctl in [4]).
I played a bit with the parameters, trying to follow some advices
discussed on this list in the past, with no success.
Quick trials in both FreeBSD (10.1 and 11-current) and NetBSD (6.5.1)
revealed a working sound out of the box, confirming the well established
support for this model.
Long story short, I had a look at the code and ended up with the
following patch which makes my sound card working in OpenBSD too:
--- ./sys/dev/pci/azalia_codec.c Fri Dec 5 21:06:18 2014
+++ ./sys/dev/pci/azalia_codec.c.patched Fri Dec 5 21:08:02 2014
@@ -182,6 +182,10 @@
break;
case 0x111d7608:
this-name = IDT 92HD75B1/2;
+ if ((this-subid 0x) == 0x103c) { /* HP */
+ this-qrks |= AZ_QRK_GPIO_UNMUTE_0;
+ }
break;
case 0x111d7674:
this-name = IDT 92HD73D1;
Of course, I don't know if this is very machine specific or instead
it could be of general interest; I'm writing here just in case someone
had the same problem or the developers consider it useful to add
that upstream.
Hope this can help
All the best
[1]
OpenBSD 5.6-stable (GENERIC.MP) #1: Fri Dec 5 21:49:07 CET 2014
r...@icarus.atlantide.net:/builds/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3195731968 (3047MB)
avail mem = 3101937664 (2958MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf284b (25 entries)
bios0: vendor Hewlett-Packard version 68PVU Ver. F.08 date 09/24/2009
bios0: Hewlett-Packard Compaq 610
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC HPET APIC MCFG TCPA SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices C0B6(S5) C10E(S3) C115(S3) C116(S3) C117(S3) C121(S3)
C123(S3) C139(S5) C2AB(S5) C13C(S5) C2AC(S5) C13D(S5) C13F(S5) C247(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz, 2194.81 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,NXE,LONG,LAHF,PERF
cpu0: 2MB 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 199MHz
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 T5870 @ 2.00GHz, 1995.01 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,NXE,LONG,LAHF,PERF
cpu1: 2MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 2 (C0B6)
acpiprt1 at acpi0: bus 8 (C125)
acpiprt2 at acpi0: bus 16 (C139)
acpiprt3 at acpi0: bus 40 (C13C)
acpiprt4 at acpi0: bus 48 (C13D)
acpiprt5 at acpi0: bus 0 (C003)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: C27C, resource for C277
acpipwrres1 at acpi0: C289, resource for C27D
acpipwrres2 at acpi0: C2A5, resource for C2A3
acpipwrres3 at acpi0: C1CE, resource for C13E
acpipwrres4 at acpi0: C3C1, resource for C3C6
acpipwrres5 at acpi0: C3C2, resource for C3C7
acpipwrres6 at acpi0: C3C3, resource for C3C8
acpipwrres7 at acpi0: C3C4, resource for C3C9
acpipwrres8 at acpi0: C3C5, resource for C3CA
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 107 degC
acpitz2 at acpi0: critical temperature is 110 degC
acpitz3 at acpi0: critical temperature is 256 degC
acpitz4 at acpi0: critical temperature is 107 degC
acpibat0 at acpi0: C245 model Primary serial 01223 2009/10/04 type LIon oem
Hewlett-Packard
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: C2BE
acpibtn1 at acpi0: C15B
acpivideo0 at acpi0: C09E
acpivout0 at acpivideo0: C1B5
cpu0: Enhanced SpeedStep 2194 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel GME965 Host rev
Re: INVALID ROOT NODE
On Sun, Nov 30, 2014 at 2:48 AM, Max Power open...@cpnetserver.net wrote: I have a CRYPTO - RAID 1 softraid device /dev/sd4a [3TB OpenBSD 5.6/amd64] on which I have about 1,400,000 files and I've never had problems reading or writing. If, however, launch the tree command, eg. tree c *, returns me: tree: invalid root node: name_of_file. : morgaine; tree /bin/ksh: tree: not found : morgaine; So this is a program from some port? What does the documentation for program say about that error message? I tried to run a fsck and this is the result Huh, an error message from a random program makes you fsck your disks? That seems like an overreaction to me. As far as we know, you're just invoking it with the wrong arguments... Philip Guenther
Re: Proposed patch to unmute Azalia sound card on Compaq 610
Hi Jonathan, On Tue 09/12 16:03, Jonathan Gray wrote: I'm curious why you decided to mask the subid here and not just test subid == 0x308a103c ? In my understanding (I'm definitely not an expert), the last part of subid represents the vendor signature (HP in this case); the first 4 digits should be instead specific to the particular chip implementation. Here I just tried to make the patch more general (guessing that the GPIO needs to be unmuted for all IDT 92HD75B1/2-type cards sold by HP), and also to stay close to code style adopted for other (similar?) cases. If my assumption is wrong, then yes, you're right: the whole subid should be tested. Anyhow, thanks for your feedback. All the best -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
