Re: Does the OpenBSD support well AMD's APU hardware?
On Sun, Jun 29, 2014 at 3:36 PM, lm wrote: > Hello, > I haven't follow your issue, but it looks to me > like your fans are not spinning under OpenBSD. > Did you check that? > > lm Good idea to check, for sure. Fans are good, though. The only thing noisier in my house would be the refrigerator when the compressor kicks on. (Yes, the silence is "deafening" in my home -- my thoughts are allowed free rein without the competing noise of the outside world.) I can hear increase in speed even with a single core as processing becomes more intensive. As I mentioned earlier, I don't consider any of this an issue. The additional cores do not add anything to enhance my OpenBSD experience :) I did think of a more elegant way to handle my box, though. I can leave the cores enabled along with HyperThreading and simply omit the bsd.mp package when installing/upgrading. Without bsd.mp, the other cores have no choice but to stare at cpu0 wistfully. Gilbert
Re: Does the OpenBSD support well AMD's APU hardware?
>> I wonder what temp Windows and Liunx run at with all the cores enabled. > Output from Linuxmint regarding temps (uptime 20:00 min) $ acpi -V Battery 0: Charging, 42%, 00:43:40 until charged Battery 0: design capacity 5600 mAh, last full capacity 3275 mAh = 58% Adapter 0: on-line Thermal 0: ok, 25.0 degrees C Thermal 0: trip point 0 switches to mode critical at temperature 107.0 degrees C Cooling 0: intel_powerclamp no state information available Cooling 1: pkg-temp-0 no state information available Cooling 2: LCD 8 of 15 Cooling 3: LCD 8 of 15 Cooling 4: Processor 0 of 10 Cooling 5: Processor 0 of 10 Cooling 6: Processor 0 of 10 Cooling 7: Processor 0 of 10 Cooling 8: Processor 0 of 10 Cooling 9: Processor 0 of 10 Cooling 10: Processor 0 of 10 Cooling 11: Processor 0 of 10 Output from Windows 8.1 Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>wmic wmic:root\cli>/namespace:\\root\wmi PATH MSAcpi_ThermalZoneTemperature \ get CurrentTemperature CurrentTemperature 2982 wmic:root\cli> Gilbert
Re: Does the OpenBSD support well AMD's APU hardware?
On Sun, Jun 29, 2014 at 2:52 PM, Chris Cappuccio wrote: > Gilbert Sanford [gilbertz@gmail.com] wrote: >> >> You may have noticed "acpitz0 at acpi0: critical temperature is 107 degC" in >> my >> dmesg . . . it always says that, and that's probably where it was before I >> disabled processor cores. I don't think the GPU is doing anything, but the >> processor was definitely cooking. My unit is very comfortable now, and >> OpenBSD simply flies. This is a very fast box compared to what I've had in >> the past. Perhaps the poster from Poland can acquire the right kind >> of hardware. > > I wonder what temp Windows and Liunx run at with all the cores enabled. Is there any specific output you'd like to have? I've already enabled the cores, and in 5 minutes after booting OpenBSD (today's snapshot) with bsd.mp, the left side of the laptop was hot enough to put water on a slow boil. I've been up with Linuxmint 17 for almost 20 minutes with all cores enabled, and my laptop has cooled down to the point where it feels like I'm running OpenBSD with a single processor. I never complained, because performance didn't suffer. Even if it were otherwise, I still wouldn't complain, because you guys deal with more than I would be willing to entertain from userland. I would have simply purchased the right hardware and quietly got about my work. If you want anything, just let me know, even if it's just to satisfy your curiosity. Gilbert
Re: Does the OpenBSD support well AMD's APU hardware?
On Sun, Jun 29, 2014 at 1:08 PM, Chris Cappuccio wrote: > Gilbert Sanford [gilbertz@gmail.com] wrote: >> Though the following has nothing to do with AMD GPU's, it may be of interest. >> I will share my config with you with one caveat: I'm from Alabama, and we all >> know what that means ... >> http://marc.info/?l=openbsd-misc&m=139656417532670&w=2 > > If you're lucky someone will have Nouveau ported before too long. > > I've noticed that Nvidia laptops tend to get really damn hot. I stick > with integrated video because it is always cooler than a discrete video > chip. > > I wonder, why not just buy something with integrated, supported Intel or ATI > video to begin with? (And that's exactly what this guy wants, as well.) > > -- > "If you see fraud and don't shout fraud, you are a fraud" -- Nassim Taleb Chris, you're absolutely right. I now know more than I did a year ago, and my next purchase, when this one dies, will be a box with integrated Intel only. Intel with integrated video is the only way to fly for those of us who just live in a tmux'ed xterm with Firefox or Chrome on the side (genuine, one-man, in-house web devel from Alabama -- man, that's funny!! You guys think OpenSSL is horrifying . . . pray that you never have to look at the 9500 lines I wrote for our multiple warehouse inventory system for the Parts Department, hahaha :) it's worked for over 2 years!) Occasionally, I break out the GIMP, but, again, integrated Intel is more than up to the task. No doubt, I got lucky with what I'm doing, to the point that Nouveau isn't necessary, nor do I care to run anything else to get it. (I keep "Winders" and Linuxmint on the box to ensure I can handle whatever comes my way in the business world.) You may have noticed "acpitz0 at acpi0: critical temperature is 107 degC" in my dmesg . . . it always says that, and that's probably where it was before I disabled processor cores. I don't think the GPU is doing anything, but the processor was definitely cooking. My unit is very comfortable now, and OpenBSD simply flies. This is a very fast box compared to what I've had in the past. Perhaps the poster from Poland can acquire the right kind of hardware. Sorry I top-posted earlier. All you guys are great!! Pure genius hard at work. Gilbert
Re: Does the OpenBSD support well AMD's APU hardware?
Though the following has nothing to do with AMD GPU's, it may be of interest. I will share my config with you with one caveat: I'm from Alabama, and we all know what that means ... http://marc.info/?l=openbsd-misc&m=139656417532670&w=2 (I still laugh about that one every time I read it -- it's a looonnn shot indeed!!!) If the following does you no good, I apologize for wasting your time. I run OpenBSD current, Windows 8.1, and Linuxmint 17 on my Dell E6520 notebook. (I am the General Manager of a Commercial Food Equipment company, and I bought it through the company for work, development, and OpenBSD learning and fun!!) It has the Nvidia Quadro NVS4200M (Optimus) on board -- see dmesg below. I had heat issues as well. My fix is simple: In the BIOS (version A19,) under Performance, I set Multi Core Support to 1 processor, and I disabled HyperThread control. SpeedStep and TurboBoost are still enabled. My box still runs like a scalded dog (did all y'all get that? if not, it means I discern no change in performance.) I have zero issues with heat. For what it's worth, I detect no drop in performance with either Windows 8.1 or Linuxmint 17, although I do not boot either one very often. Both of those systems performed without any problems before I tweaked my BIOS (no heat, Windows used Nvidia driver, Linuxmint used Nouveau driver,) but they both run fine with the tweaked BIOS, so I leave my system "optimized" for OpenBSD. Mind you now, I rely on a very subjective method of using my patience level to measure performance; if I have to wait on anything from a computer of any sort, I'm not going to tolerate it for long. I just don't have time. A couple more things to mention. No, I can't run Gnome. No, the Broadcom wire- less card is dead weight. Ask me if I care. Nope, sure don't. Love cwm, and I'm either connected to the net via ethernet or tethered to my smartphone. Remember I'm from Alabama, so I don't have a problem doing more with less. (Hmmm . . . maybe if I were not so slow, being from Alabama and everything, I might have time to do more with less . . .) I also understand the financial restraints in obtaining hardware. (I purchased my notebook as a refurbished unit with tax and shipping for around $320 US about a year ago.) And yes, I run full HD, 1920x1080 without a hiccup. After all, OpenBSD "Just Works!" The xrandr output below is due to the Intel HD 3000 graphics, of course. $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767 LVDS1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.01*+ 40.01 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.3256.25 640x480 59.94 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) So, if this helps you, great. I finally figured out that single processor performance still rules in my world -- the other seven cores on that smokin' Intel 2720QM can just "stay on the porch with the rest of the dawgs." Sincerely, Gilbert OpenBSD 5.5-current (GENERIC) #218: Fri Jun 27 12:27:41 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC RTC BIOS diagnostic error 3f real mem = 8448847872 (8057MB) avail mem = 8215207936 (7834MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf2090 (106 entries) bios0: vendor Dell Inc. version "A19" date 11/14/2013 bios0: Dell Inc. Latitude E6520 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC TCPA SSDT MCFG HPET BOOT SSDT SSDT SSDT DMAR SLIC SSDT acpi0: wakeup devices UAR1(S3) HDEF(S4) GLAN(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(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) i7-2720QM CPU @ 2.20GHz, 2195.32 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 3 (RP02) acpiprt4 at acpi0: bus 10 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus 11 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus
Re: Are xdm configs overwritten on upgrade?
Why not create a .xsession file in your home directory? Refer to Section 11.5.3 at www.openbsd.org/faq/faq11.html for more details. The last paragraph should be most helpful. Gilbert Hello, I want to prevent xconsole starting with xdm. I see it is started in /etc/X11/xdm/Xsetup_0. Is there a user or system specific file for xdm conf files as there are for /etc/rc.conf? If not, and I modify Xsetup_0 will it be overwritten on OS upgrade? Many thanks, Laurence
Re: Chromium package missing from amd64 snapshots
I grabbed it yesterday from the Erlangen Germany mirror : openbsd.cs.fau.de/pub/OpenBSD/snapshots/packages/amd64/ Gilbert
Re: Looking for good, small, canadian version laptop suggestions
I have purchased over 20 machines (about 50% laptop) from dfsdirectsales.com over the last 5 years, and most of them had next day business support still in effect from Dell. I had only one machine that needed service (a Latitude E6510,) and it was repaired at no charge within 2 days. Also, please use your favorite search engine to look for "dfs coupon codes." I have saved as much as 50% (usually 25 - 30%) using the code at checkout. "Retail me not" has legitimate codes. I copy the code I want to use and paste and apply it when I check out. The discount will show, if the code is valid. A nice customer service rep at DFS Direct Sales told me about the coupons, so it's not a scam. I have been shopping at the US site. Good luck with your purchase, Gilbert
Re: mysql.sock location
On Fri, Aug 23, 2013 at 10:06 PM, Guy Ferguson wrote: > Hmm - ok, I actually just went to that path > (/usr/local/share/doc/pkg- readmes/) and there are 4 files, one of which is a > mysql-server-5.x.xx..but it's only 1325 bytes, and certainly no > comments from users like ajacoutot@. I mean, there are maybe two or three > sugegstions about changing the login.conf and my.cnf, but it certainly > wouldn't have been any help with the issues i faced. > > Perhaps there are some other dox in another location? > > thanks, > > Guy I apologize for not READING everyone's posts more carefully. I finally remembered where I first read about placing the mysql socket in the chroot: http://www.openbsd.org/cgi-bin/cvsweb/ports/www/drupal5/core/pkg/Attic/MESSAGE?rev=1.4;content-type=text%2Fplain Thu Jul 24 09:28:40 2008 UTC I was a brand new user with OpenBSD in 2008, and I was installing drupal. The drupal-5 instructions included running mysql in chrooted httpd. As stu@ pointed out earlier, instructions were moved from the drupal pkg-readme to the mysql-server pkg-readme post 5.3. See the changes for Revision 1.4 at: http://www.openbsd.org/cgi-bin/cvsweb/ports/www/drupal6/core/pkg/README Thus, my suggestion to Mr. Ferguson to read the included pkg_readme for mysql-server must have seemed idiotic at best. All of you have shown exemplary conduct in tolerating my beginner's attempts to help a new user. I knew what to do, but I wasn't clear and precise with my instructions. Sigh, I still have so much to learn, but, I won't give up. I'll learn from this, too, and do a much better job next time. Thank you all for being patient with me. Gilbert
Re: mysql.sock location
You are spot on in your observation that MySQL is not OpenBSD. I used the lesson I learned in that succinct assertion to realize the distinction between a pkg-readme and a manual page, i.e., a pkg-readme is not a manual page, even if an OpenBSD developer wrote the pkg-readme! Please pardon me for misappropriating words that pertain to manual pages from the "Welcome to OpenBSD x.x!" new install mail message to misapply them to a pkg-readme. To ensure that I don't mislead Mr. Ferguson, or any other new user of OpenBSD, I pasted below the context of the section of the "Welcome to OpenBSD x.x!" message from which I so carelessly borrowed in case anyone may have overlooked it: "Again, PLEASE READ THE MANUAL PAGES. Our developers have spent countless hours improving them so that they are clear and precise." I didn't mean to imply that perfection had been attained in the various forms of OpenBSD documentation, but, in my limited experience with OpenBSD, I have always been very impressed with the high quality of the OpenBSD documentation. OpenBSD documentation is so good, I never even thought to ask a question on @misc. Perhaps I should have, but, based on what I now know, I see that I didn't need to ask; I just had to read what was right in front of me. I believe what Mr. de Raadt expresses so sincerely in the "Welcome to OpenBSD x.x!" mail message regarding manual pages, and I think it best to follow his instructions and trust that he and the developers know what they're doing. As I learn and grow with OpenBSD, I may one day enjoy the privilege of contributing improvements to OpenBSD. I may not. It's just not easy to stand on the shoulders of giants, even if fallibly human. Certainly, room for improvement will always exist in every endeavor. I had hoped merely to assist Mr. Ferguson by instructing him to read the mysql-server-5.1.71v0 pkg-readme written by an OpenBSD developer for those who want to know precisely what to do in order to run mysql-server on their OpenBSD system as indicated by the title of the mysql-server pkg-readme. I hope also that what I've written above might encourage every new user of OpenBSD to READ the OpenBSD provided documentation regarding their specific installation before they prematurely post their questions to the list. Thank you for your kind clarification on the comments I made previously about OpenBSD documentation. Respectfully, Gilbert On Sat, Aug 24, 2013 at 5:47 PM, Chris Cappuccio wrote: > Gilbert Sanford [gilbertz@gmail.com] wrote: >> You're welcome. Since the OpenBSD documentation is clear and precise, >> any cloud of confusion must be a product of my own defective thinking. >> So I keep going back to the documentation (I stay off Google for >> OpenBSD research) to push it in and push out the misunderstanding. > > MySQL is not OpenBSD. And while the various forms of OpenBSD documentaton may > attempt to be clear and precise, they aren't complete. There are always > improvements. > > -- > Semicolons; use them
Re: mysql.sock location
You're welcome. Since the OpenBSD documentation is clear and precise, any cloud of confusion must be a product of my own defective thinking. So I keep going back to the documentation (I stay off Google for OpenBSD research) to push it in and push out the misunderstanding. I always figured @misc would not be interested in hearing about my struggles. As far as learning is concerned, I'm just hard-headed enough (or stubborn or persistent or tenacious or dense . . . pick one) to keep after something until I get it. After 5 years, I'm just now beginning to appreciate and understand enough to recognize the genius behind OpenBSD . . . Gilbert On Fri, Aug 23, 2013 at 11:53 PM, Guy Ferguson wrote: > Gilbert, > > Thanks very much for supplying the text of your readme. > > In mine, v5.1.68, which I am pretty sure was the latest version on i386 > about tow weeks ago, all the text beginning with the heading > > > chrooted daemons and MySQL socket > = > > ...does not exist. > > SO thanks for that. And I agree with your point about multiple readings. I > guess I've learnt bad habits of googling and skimming for quick tuutes on > how to do things, with OpenBSD I need to spend the time to learn how it > works, > > Guy > > > On 24/08/2013 14:46, Gilbert Sanford wrote: >> >> chrooted daemons and MySQL socket
Re: mysql.sock location
Since you said you were new to OpenBSD, I trust the length of this post is justified, and I'm not offending others on this list. I've been using OpenBSD around 5 years now, but I had not subscribed or ever posted anything to @misc until your post. Actually, I've never participated in any mailing list until now, so I hope my humble attempt is helpful in some small way. Please understand that I trust the documentation over which the developers have spent countless hours to make clear and precise, so I will only offer what much wiser and knowledgeable persons (the OpenBSD developers) have written. Speaking again only for myself, I have learned that in order to understand what the OpenBSD developers have so clearly and precisely written, I must read it multiple times before I grasp the concept well enough to achieve my objectives. In other words, pay very close attention to everything in the OpenBSD documentation. Also read references to man pages if mentioned for additional insight. I'm running -current with mysql-server-5.1.71v0 on amd64, and I am including the README for mysql-server on MY box below. The README file on YOUR box may be different. Please pay very careful attention to the section entitled "chrooted daemons and MySQL socket" and note that there are two things to do in order to place the MySQL socket in the chroot: 1) Create a directory for the MySQL socket, and 2) Adjust /etc/my.cnf to put and connect to the MySQL socket within the chroot. See below for full context and note the author :) $OpenBSD: README-server,v 1.7 2013/03/17 07:22:23 ajacoutot Exp $ +--- | Running mysql-server-5.1.71v0 on OpenBSD +--- Initial setup = If you are installing MySQL for the first time, you have to create a default database first. In order to create the database, please run /usr/local/bin/mysql_install_db You will need to tune the values in the my.cnf file (examples available in /usr/local/share/mysql). By default, the _mysql user, and so the MySQL processes run in the login(1) class of "daemon". On a busy server, it may be advisable to put the _mysql user and processes in their own login(1) class with tuned resources, such as more open file descriptors etc. For example, add this to the login.conf(5) file: mysqld:\ :openfiles-cur=1024:\ :openfiles-max=2048:\ :tc=daemon: Rebuild the login.conf.db file if necessary: # [ -f /etc/login.conf.db ] && cap_mkdb /etc/login.conf For larger servers and dedicated database servers, these numbers and memory limits (e.g. datasize and stacksize) may also need to be increased. Please report any changes and experiences to the package maintainers so that we can update this file for future versions. chrooted daemons and MySQL socket = For external program running under a chroot(8) to be able to access the MySQL server without using a network connection, the socket must be placed inside the chroot. e.g. httpd(8) or nginx(8): connecting to MySQL from PHP --- Create a directory for the MySQL socket: # install -d -m 0711 -o _mysql -g _mysql /var/www/var/run/mysql Adjust /etc/my.cnf to put and connect to the MySQL socket within the chroot: [client] socket = /var/www/var/run/mysql/mysql.sock [mysqld] socket = /var/www/var/run/mysql/mysql.sock I follow the directions above whenever I set up a new box, and I check that mysql-server is running in the chroot after I reboot the box. Output from my box is below: $ /usr/bin/sudo ls -l /var/www/var/run/mysql/ total 0 srwxrwxrwx 1 _mysql _mysql 0 Aug 23 22:10 mysql.sock Then I load up mysql-server. Now that I've done this a few thousand times, it's easy . . . Gilbert On Fri, Aug 23, 2013 at 10:06 PM, Guy Ferguson wrote: > Hmm - ok, I actually just went to that path > (/usr/local/share/doc/pkg-readmes/) and there are 4 files, one of which is a > mysql-server-5.x.xx..but it's only 1325 bytes, and certainly no > comments from users like ajacoutot@. I mean, there are maybe two or three > sugegstions about changing the login.conf and my.cnf, but it certainly > wouldn't have been any help with the issues i faced. > > Perhaps there are some other dox in another location? > > thanks, > > Guy > > On 23/08/2013 22:16, Gilbert Sanford wrote: >> >> The instructions in /usr/local/share/doc/pkg-readmes/mysql-server-5.1.xx >> have always worked for me . . . very handy reference with specific >> instructions from ajacoutot@ on "Running mysql-server-5.1.xx on >> OpenBSD." >> >> Gilbert
Re: mysql.sock location
The instructions in /usr/local/share/doc/pkg-readmes/mysql-server-5.1.xx have always worked for me . . . very handy reference with specific instructions from ajacoutot@ on "Running mysql-server-5.1.xx on OpenBSD." Gilbert On Fri, Aug 23, 2013 at 4:34 AM, Guy Ferguson wrote: > liviu, > At last, I get your name right, if a little under-capitalised. Your help > was the first step in maybe a dozen or so that got the site back up. So > thank you kindly for that. Just some minor linking to outside the chroot > and it'll be perfect. > > But thanks for the help. > guy > > On 19/08/2013 02:54, Liviu Daia wrote: >> >> On 18 August 2013, Guy Ferguson wrote: >>> >>> Livia, >> >> If you want to address me by name, s/Livia/Liviu/ please. It might >> not be much, but it's my name, and I kind of became attached to it over >> the years. :) >> >>> Thanks for your help. >>> >>> I modded the /etc/my.cnf to add in the extra "/run" directory. >>> >>> A few other tweaks here and there and i can now get a test.php to >>> connect to the >>> default host mysql ($conn=mysql_connect...) >>> >>> So now i'm confident that mysql is working and connectable...I just >>> ahve to sort out why drupal is >>> unhappy, which no doubt is a chroot issue. >> >> [...] >> >> Like I said, the easy solution to that is to use TCP connections. >> As others have pointed out, just set hostname to 127.0.0.1 in your >> Drupal config, and you should be fine. >> >> If you insist on using UNIX sockets, you probably want to set >> >> socket = /var/www/run/mysql.sock >> >> in the /etc/my.cnf, then copy /etc/my.cnf to /var/www/etc/my.cnf, and >> set >> >> socket = /run/mysql.sock >> >> in the client section in /var/www/etc/my.cnf. There is no advantage in >> doing things like this though, you'd be just looking for future trouble. >> >> Regards, >> >> Liviu Daia >> >> >> >> - >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2013.0.3392 / Virus Database: 3211/6584 - Release Date: 08/16/13