Recommended Industrial PCs?
Hello, can someone recommend me an Industrial PC (IPC) to use with OpenBSD? I would like to have a lot of hardware supported from this IPC by OpenBSD. Regards Martin
OpenBSD current crash (Thinkpad X220i)
hi, my notebook had a hiccup: it suddenly hanged and stoped working. I had firefox, cwm+X11, emacs (terminal) and a few tmux sessions open. The snapshot is from Monday, 24.08. I also checkoud out the sources and it is selfcompiled. Here is what I can see in my /var/log/messages before the hiccup: Aug 26 11:29:19 x220i dhclient[6121]: iwn0 down; exiting Aug 26 11:43:44 x220i apmd: battery status: high. external power status: not connected. estimated battery life 76% (251 minutes) Aug 26 12:00:01 x220i syslogd: restart Aug 26 12:33:14 x220i apmd: battery status: high. external power status: not connected. estimated battery life 55% (132 minutes) Aug 26 12:43:14 x220i apmd: battery status: low. external power status: not connected. estimated battery life 50% (119 minutes) Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake to ack request. Aug 26 12:43:36 x220i /bsd: error:
Re: Thinkpad spyware
Why should OpenBSD users be concerned? Doesn't this injection method only work when the running OS is Windows? Or are you thinking it would be a matter of principle? -Gene On Wed, Aug 26, 2015 at 8:59 AM, Shaun Reiger srei...@sprmail.net wrote: In light of what Lenovo has been doing to its customers by installing spyware like superfish and now installing crapware using Microsoft's Windows Platform Binary Table at the BIOS level. Do people still plan on purchasing laptops from them going forward. If so whats your reasoning behind this. Is anyone moving to other PC manufactures now. http://www.theregister.co.uk/2015/08/12/lenovo_firmware_nasty/ -- Shaun Ars longa, vita brevis, occasio praeceps, experimentum periculosum, iudicium difficile - Hippocrates (c. 400BC)
Re: Thinkpad spyware
In light of what Lenovo has been doing to its customers by installing spyware like superfish and now installing crapware using Microsoft's Windows Platform Binary Table at the BIOS level. Do people still plan on purchasing laptops from them going forward. If so whats your reasoning behind this. Is anyone moving to other PC manufactures now. http://www.theregister.co.uk/2015/08/12/lenovo_firmware_nasty/ Your subject is misleading, Think* series are not concerned (yet) with the crapware. I have a ThinkPad because it is a good machine for my usage. I might buy another one if I can't find a better deal. (and in the end, this topic has really few to do with OpenBSD)
Thinkpad spyware
In light of what Lenovo has been doing to its customers by installing spyware like superfish and now installing crapware using Microsoft's Windows Platform Binary Table at the BIOS level. Do people still plan on purchasing laptops from them going forward. If so whats your reasoning behind this. Is anyone moving to other PC manufactures now. http://www.theregister.co.uk/2015/08/12/lenovo_firmware_nasty/ -- Shaun Ars longa, vita brevis, occasio praeceps, experimentum periculosum, iudicium difficile - Hippocrates (c. 400BC)
Re: Thinkpad spyware
This is happening for a while now in industry, and even openbsd developers knowing this, they still suggest Lenovo hardware: http://marc.info/?l=openbsd-miscm=143671215412596w=2 I can't understand you guys. There projects running trying to develop Open Hardware, and I see no such support for their product (Freescale, for example). On lyrics 3.7 you say Want to help us? Avoid Intel [and] Broadcom [...] chipsets Both used in lenovo hardware. The paper /brhard2007/mgp00027 on WWW say: Help us when we attack a specific vendor... so what? Why should OpenBSD users be concerned? Doesn't this injection method only work when the running OS is Windows? This may be a concern because industry are slowly and silently trying to adopt locked secure boot options in Windows: http://tech.slashdot.org/story/15/03/20/2039251/oems-allowed-to-lock-secure-boot-in-windows-10-computers Remember me the methaphor boiling frog.
Re: iMac G5 install
On 25/08/15(Tue) 16:02, Joseph A Borg wrote: I have an old iMac G5 on which I'd like to install OpenBSD 5.5 as that's the latest system I purchased. the CD drive doesn't work so I started it up in target mode and reformatted the internal HD from another mac. The shrunk the partition to 10Gb and copied all the relevant files from the dvd set. Doing an ofwboot I get notifications of usb timing out and then wd0 timing out. The bsd.rd hangs when listing softraid, a few messages later. I tested the disk and verified it using Disk Utility from the other mac. Am I correct in stating that the drive is connected via sata? Is this supported at 5.5? Should I forfeit or am I missing something stupid? I believe your machine is only supported in -current or by the upcoming 5.8. M.
Re: cdio(1) cdrip (error correction / why WAVE).
I can also recommend abcde. I have transferred my ~800 discs to files using this tool. The newest version 2.7 (not yet in ports) can even download cover art now. I wish it had this feature back when I was in the process. I used 'exfalso' for that, which was a manual and very tedious process. http://lists.einval.com/pipermail/abcde-users/2015-June/000162.html regards Lars Thanks for your answer - sorry, for the delay to answer. I am not a coder so, I will ask at ports@ maybe someone could update the ports abcde / cdparanoia / cd-discid.
Re: iMac G5 install
Why don't you make an usb install key ? And you should use 5.7 or 5.8 (almost 5.8 by using snapshot) For an usb installation, I think this method still works : http://undeadly.org/cgi?action=articlesid=20140225072408 Maybe your disk is dying -Message d'origine- De : owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] De la part de Joseph A Borg Envoyé : mardi 25 août 2015 18:02 À : misc@openbsd.org Objet : iMac G5 install I have an old iMac G5 on which I'd like to install OpenBSD 5.5 as that's the latest system I purchased. the CD drive doesn't work so I started it up in target mode and reformatted the internal HD from another mac. The shrunk the partition to 10Gb and copied all the relevant files from the dvd set. Doing an ofwboot I get notifications of usb timing out and then wd0 timing out. The bsd.rd hangs when listing softraid, a few messages later. I tested the disk and verified it using Disk Utility from the other mac. Am I correct in stating that the drive is connected via sata? Is this supported at 5.5? Should I forfeit or am I missing something stupid? I transcribed the following, hope I got it right: wd0(pciide 0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 wd0 atpciide0 channel 0 drive 0: ST3500320AS wd0 (pciide 0:0:0): using pio mode 4, ultraDMA mode 6 pciide0: port 1:PHY offline wdc0 at kauaiata0 irq 38:DMA …
Re: [DIFF] nuke /var/tmp from FAQ 4
On 2015-08-25 Tue 18:51 PM |, Craig Skinner wrote:
Hi there,
FAQ 4's title is 4 - OpenBSD 5.7 Installation Guide
/var/tmp is listed as now a symbolic link to /tmp in the
Security improvements section of http://www.openbsd.org/57.html
Here's a first attempt at rewording, which might need improvements:
A typo was spotted (thanks) a question raised about purging /tmp,
yet still being able to recover editor files.
Due to /etc/{daily,rc} skirting around /tmp/{quota*,vi.recover} others,
simply note there are a few special exceptions to the /tmp purge:
--- faq4.html Tue Aug 25 18:16:19 2015
+++ faq4-no-var-tmp.htmlWed Aug 26 09:35:12 2015
@@ -2132,15 +2132,23 @@ Read more about this in a href=faq14.html#SwapFAQ
lib/tmp:/b
This is a world-writeable directory used for (as the name implies!)
-temporary storage.
-Most systems can get by with very modest amounts of storage here, 50M is
-usually many times what you should ever need, though there are a few
-applications which can use much, much more.
+temporary storage. For example,
+a
href=http://www.openbsd.org/cgi-bin/man.cgi?query=viamp;sektion=1;vi(1)/a
+uses this directory for temporary storage,
+so if the computer crashes or is rebooted while editing a file,
+the files here can be used to recover the editing session.
+Most systems can get by with very modest amounts of storage here,
+50M is usually many times what you should ever need,
+though there are a few applications which can use much, much more.
While this directory is world-writable, when it is a separate partition,
-OpenBSD defaults to mounting it nodev and nosuid, which minimizes how
-it can be used to abuse your system.
-Files left unattended here will be purged automatically, this is NOT for
-long term storage!
+OpenBSD defaults to mounting it nodev and nosuid,
+which minimizes how it can be used to abuse your system.
+Apart from a few special exceptions,
+files left unattended here will be purged automatically at
+a
href=http://www.openbsd.org/cgi-bin/man.cgi?query=rcamp;sektion=8;boot/a
+and
+a
href=http://www.openbsd.org/cgi-bin/man.cgi?query=dailyamp;sektion=8;daily(8)/a.
+This is NOT for long term storage!
lib/var:/b
This directory and mount point is used for a LOT of things, and depending
@@ -2151,20 +2159,12 @@ Some of the things that end up here (and potential add
litt/var/mail/tt: Incoming mail boxes.
litt/var/spool/tt: Outgoing mail (and other things)
litt/var/www/tt: OpenBSD's web server lives here.
- litt/var/tmp/tt: This is a persistent temporary file directory,
- as files placed here are NOT purged on reboot.
- For example, vi(1) uses this directory for temporary storage, so
- if your computer crashes or is rebooted while you are editing a file,
- the files here can be used to recover your editing session.
- Files left here over 24 hours though will be purged by the nightly
- cleanup scripts,
- a
href=http://www.openbsd.org/cgi-bin/man.cgi?query=dailyamp;sektion=8;daily(8)/a.
- litt/var/crash/tt: If the system panics, it will attempt to
+ litt/var/crash/tt: If the system panics, it will attempt to
save a core dump in the swap partition before rebooting.
This core dump will then be saved to tt/var/crash/tt upon
reboot, so tt/var/tt will need at least as much free space as
the system has RAM for this to work automatically.
- /ul
+/ul
lib/usr:/b
This is where most of OpenBSD resides.
@@ -2272,11 +2272,10 @@ Some additional thoughts on partitioning:
partitions.
This is another reason we suggest using
a href=faq15.html#PkgMgmtpre-compiled packages/a instead.
- liAt least some editors use tt/var/tmp/tt for scratch space, and
+ liAt least some editors use tt/tmp/tt for scratch space, and
this often needs to be as big or bigger than the largest file you edit.
- If you plan on editing 500M files, your tt/var/tt or
- tt/var/tmp/tt partition will need to be much larger than your
- might have planned on.
+ If you plan on editing 500M files, your tt/tmp/tt partition will
+ need to be much larger than you might have planned on.
/ul
Re: iMac G5 install
On 25/08/15(Tue) 20:11, Romain FABBRI wrote: Why don't you make an usb install key ? And you should use 5.7 or 5.8 (almost 5.8 by using snapshot) For an usb installation, I think this method still works : http://undeadly.org/cgi?action=articlesid=20140225072408 No it wont. For G5s you need to copy ofwboot and bsd.rd at the root of a FAT partition on your USB key, enter the OpenFirmware prompt and type: boot usb:,ofwboot bsd.rd Maybe your disk is dying I doubt so, it's just an interrupt problem the hpb(4) driver introduced recently is needed on such machines.
netstat statistics bridge interface
Hi all, i have configured bridge interface with em2 and em3. Generator is connected on em3 and receiver is connected on em2. I'm generating 1,48Mpps on em3 and getting around 400kpps on box connected to em2 and that is fine but counters in netstat seems doubled on total in packets and total out packets. When traffic is routed over em2 and em3 counters seems fine. Could someone please tell why i see lots of errors on em interface but when i do same setups over ix inteface i can't see any errors? OpenBSD is updated today from cvs. pf disabled kern.pool_debug=0 net.inet.ip.forwarding=1 net.inet.ip.ifq.maxlen=8192 net.inet.icmp.errppslimit=1000 # netstat -I bridge0 -w 1 bridg in bridg out total in total out packets errs packets errs colls packets errs packets errs colls 4487180457 0 4487181625 0 0 8974402936 28010060078 8974377616 0 0 408667 0 408667 0 0817399 1114990 817455 0 0 414841 0 414841 0 0829686 1090365 829623 0 0 410705 0 410705 0 0821415 1110769 821471 0 0 418013 0 418013 0 0835967 1088200 836027 0 0 410321 0 410321 0 0820706 1110852 820583 0 0 # netstat -I em3 -w 1 em3 inem3 out total in total out packets errs packets errs colls packets errs packets errs colls 4468797033 28013336610 24623020 0 0 8986879126 28027621153 8986853808 0 0 407393 10907801 0 0814730 1090780 814727 0 0 413971 10951471 0 0827946 1095147 827943 0 0 412976 10942261 0 0825956 1094226 825893 0 0 412837 1101 0 0825678 110 825735 0 0 411166 10912281 0 0822335 1091228 822270 0 0 # netstat -I em2 -w 1 em2 inem2 out total in total out packets errs packets errs colls packets errs packets errs colls 24623417 14284543 4473277412 0 0 8995839701 28039662049 8995814274 0 0 3 0 412959 0 0825805 1110303 825861 0 0 4 0 407495 0 0815053 1093808 814990 0 0 3 0 414865 0 0829737 1090340 829733 0 0 3 0 414132 0 0828152 1112466 828207 0 0 3 0 415979 0 0832084 1108386 832021 0 0
Re: Recommended Industrial PCs?
--On Wednesday, August 26, 2015 09:11:22 PM +0200 Martin Haufschild martin.haufsch...@uni-rostock.de wrote: can someone recommend me an Industrial PC (IPC) to use with OpenBSD? I would like to have a lot of hardware supported from this IPC by OpenBSD. Lanners are solid: http://www.lannerinc.com/ Caveat: I've not used graphics on them; only text mode. The graphics may be fine but I can't attest to it. Devin
Re: wtfs write error when running newfs
Hello Thomas, On Wed 26/08/2015 02:27, Thomas Bohl wrote: [...] Does it work when you make the partition smaller than 160086527? The behavior is the same whatever dimension I set for the partition. On top of that, I noticed that MBR init through fdisk doesn't work too: [snip] root@poseidon:[~] fdisk -i sd1 Do you wish to write new MBR and partition table? [n] y Writing MBR at offset 0. fdisk: error writing MBR: No such file or directory [snip] At this point, I suspect a compatibility issue of the (very old) IDE-to-USB case... Thanks for your feedback -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
gphoto2 (PTP mode camera) no more working in -current
Dear misc@ readers,
I have an old Canon camera (model Digital IXUS 40); it was perfectly
working in 5.7 through gphoto2 in PTP mode.
It doesn't work anymore in -current (5.8 GENERIC.MP#1267 amd64).
gphoto2 (well, I use gtkam actually) correctly detects it, but the
connection cannot be established. This is an excerpt of the debug
messages:
[snip]
ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING
LIST:
gtkam 0.2.0
gtkam has been compiled with the following options:
+ cc (C compiler used)
+ no bonobo (for FIXME)
+ no gnome (for FIXME)
+ no gimp (plugin for The Gimp)
+ exif (for displaying exif information)
libgphoto2 2.5.8
libgphoto2 has been compiled with the following options:
+ all camlibs
+ cc (C compiler used)
+ ltdl (for portable loading of camlibs)
+ EXIF (for special handling of EXIF files)
libgphoto2_port 0.12.0
libgphoto2_port has been compiled with the following options:
+ cc (C compiler used)
+ ltdl (for portable loading of camlibs)
+ USB (libusb1, for USB cameras)
+ no serial (for serial cameras)
+ no resmgr (serial port access and locking)
+ no ttylock (serial port locking)
+ no lockdev (serial port locking)
Using ltdl to load camera libraries from '/usr/local/lib/libgphoto2/2.5.8'...
Found '/usr/local/lib/libgphoto2/2.5.8/adc65'.
Found '/usr/local/lib/libgphoto2/2.5.8/agfa_cl20'.
Found '/usr/local/lib/libgphoto2/2.5.8/aox'.
Found '/usr/local/lib/libgphoto2/2.5.8/ax203'.
Found '/usr/local/lib/libgphoto2/2.5.8/barbie'.
Found '/usr/local/lib/libgphoto2/2.5.8/canon'.
Found '/usr/local/lib/libgphoto2/2.5.8/casio_qv'.
Found '/usr/local/lib/libgphoto2/2.5.8/clicksmart310'.
Found '/usr/local/lib/libgphoto2/2.5.8/digigr8'.
Found '/usr/local/lib/libgphoto2/2.5.8/digita'.
Found '/usr/local/lib/libgphoto2/2.5.8/dimagev'.
Found '/usr/local/lib/libgphoto2/2.5.8/dimera3500'.
Found '/usr/local/lib/libgphoto2/2.5.8/directory'.
Found '/usr/local/lib/libgphoto2/2.5.8/enigma13'.
Found '/usr/local/lib/libgphoto2/2.5.8/fuji'.
Found '/usr/local/lib/libgphoto2/2.5.8/gsmart300'.
Found '/usr/local/lib/libgphoto2/2.5.8/hp215'.
Found '/usr/local/lib/libgphoto2/2.5.8/iclick'.
Found '/usr/local/lib/libgphoto2/2.5.8/jamcam'.
Found '/usr/local/lib/libgphoto2/2.5.8/jd11'.
Found '/usr/local/lib/libgphoto2/2.5.8/jl2005a'.
Found '/usr/local/lib/libgphoto2/2.5.8/jl2005c'.
Found '/usr/local/lib/libgphoto2/2.5.8/kodak_dc120'.
Found '/usr/local/lib/libgphoto2/2.5.8/kodak_dc210'.
Found '/usr/local/lib/libgphoto2/2.5.8/kodak_dc240'.
Found '/usr/local/lib/libgphoto2/2.5.8/kodak_dc3200'.
Found '/usr/local/lib/libgphoto2/2.5.8/kodak_ez200'.
Found '/usr/local/lib/libgphoto2/2.5.8/konica'.
Found '/usr/local/lib/libgphoto2/2.5.8/konica_qm150'.
Found '/usr/local/lib/libgphoto2/2.5.8/largan'.
Found '/usr/local/lib/libgphoto2/2.5.8/lg_gsm'.
Found '/usr/local/lib/libgphoto2/2.5.8/mars'.
Found '/usr/local/lib/libgphoto2/2.5.8/mustek'.
Found '/usr/local/lib/libgphoto2/2.5.8/panasonic_coolshot'.
Found '/usr/local/lib/libgphoto2/2.5.8/panasonic_dc1000'.
Found '/usr/local/lib/libgphoto2/2.5.8/panasonic_dc1580'.
Found '/usr/local/lib/libgphoto2/2.5.8/panasonic_l859'.
Found '/usr/local/lib/libgphoto2/2.5.8/pccam300'.
Found '/usr/local/lib/libgphoto2/2.5.8/pccam600'.
Found '/usr/local/lib/libgphoto2/2.5.8/pentax'.
Found '/usr/local/lib/libgphoto2/2.5.8/polaroid_pdc320'.
Found '/usr/local/lib/libgphoto2/2.5.8/polaroid_pdc640'.
Found '/usr/local/lib/libgphoto2/2.5.8/polaroid_pdc700'.
Found '/usr/local/lib/libgphoto2/2.5.8/ptp2'.
Found '/usr/local/lib/libgphoto2/2.5.8/ricoh'.
Found '/usr/local/lib/libgphoto2/2.5.8/ricoh_g3'.
Found '/usr/local/lib/libgphoto2/2.5.8/samsung'.
Found '/usr/local/lib/libgphoto2/2.5.8/sierra'.
Found '/usr/local/lib/libgphoto2/2.5.8/sipix_blink2'.
Found '/usr/local/lib/libgphoto2/2.5.8/sipix_web2'.
Found '/usr/local/lib/libgphoto2/2.5.8/smal'.
Found '/usr/local/lib/libgphoto2/2.5.8/sonix'.
Found '/usr/local/lib/libgphoto2/2.5.8/sony_dscf1'.
Found '/usr/local/lib/libgphoto2/2.5.8/sony_dscf55'.
Found '/usr/local/lib/libgphoto2/2.5.8/soundvision'.
Found '/usr/local/lib/libgphoto2/2.5.8/spca50x'.
Found '/usr/local/lib/libgphoto2/2.5.8/sq905'.
Found '/usr/local/lib/libgphoto2/2.5.8/st2205'.
Found '/usr/local/lib/libgphoto2/2.5.8/stv0674'.
Found '/usr/local/lib/libgphoto2/2.5.8/stv0680'.
Found '/usr/local/lib/libgphoto2/2.5.8/sx330z'.
Found '/usr/local/lib/libgphoto2/2.5.8/topfield'.
Found '/usr/local/lib/libgphoto2/2.5.8/toshiba_pdrm11'.
Found '/usr/local/lib/libgphoto2/2.5.8/tp6801'.
Found 64 camera drivers.
Using ltdl to load io-drivers from '/usr/local/lib/libgphoto2_port/0.12.0'...
Called for filename '/usr/local/lib/libgphoto2_port/0.12.0/disk'.
Error during assembling of port list: 'Unspecified error' (-1).
Loaded '' ('^disk:') from '/usr/local/lib/libgphoto2_port/0.12.0/disk'.
Called for filename '/usr/local/lib/libgphoto2_port/0.12.0/ptpip'.
Loaded 'PTP/IP Connection' ('ptpip:') from
'/usr/local/lib/libgphoto2_port/0.12.0/ptpip'.
Loaded
Re: problems compiling latest 5.7 patches
Thanks for the tip. For now I think I'll try to remember it for the future, but for now use what seems to be the supported command so I don't confuse something further. I just let the compiles run in the background anyway so the time is not the important thing for me. Thanks again. On 08/22/15 15:16, Doug Hogan wrote: On Sat, Aug 22, 2015 at 02:21:49PM -0600, luke...@onemodel.org wrote: OK, I must have run an errant CVS command somewhere. (Sigh.) Thanks much for seeing that pointing it out. While you're at it, you should try running 'make -j num'. I noticed you're using GENERIC.MP but running 'make build'. My kernel compiles normally take 50s with make -j8. Without -j8, it takes around 150s. The best -j num depends on your hardware so try a few settings.
