#linuxcnc-devel | Logs for 2015-01-22

[05:38:01] <Martiini> I've decided to learn welding robot programming ..What do I need to know? how will I learn? kuka, fanuc, abb, motoman - all robots the same? All robots are programmed with cnc, no?
[10:29:47] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 d27ba5d 06linuxcnc 10src/emc/usr_intf/emcrsh.cc 10src/emc/usr_intf/schedrmt.cc Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d27ba5d
[11:15:11] <mozmck> anyone here used qemu recently? It has changed since I used it last, and I finally got it to run an iso but it is unusably slow.
[11:17:50] <seb_kuzminsky> mozmck: i use kvm a lot, it's nice & fast
[11:18:46] <skunkworks> I have used virtbox and kvm.. Both seem to be fast.
[11:19:23] <mozmck> ok, do you have a quick command line? the docs for the command line options in qemu look like a hundred pages or so :)
[11:19:31] <skunkworks> kvm doesn't seem to handle opengl as well as virtualbox
[11:19:53] <mozmck> I use virtualbox, but qemu was nice because I could quickly boot an iso image to test it.
[11:20:05] <seb_kuzminsky> i use libvirt's "virt-manager" for most of my day-to-day tasks (creating vms, starting & stopping them, accessing the console, etc)
[11:20:37] <seb_kuzminsky> (don't tell cradek i dont use the kvm/qemu command-line very much)
[11:20:45] <mozmck> can you just boot an iso without creating a vm for it? that's what I used to do with qemu
[11:21:07] <mozmck> it was quite nice for testing livecd's while building them.
[11:25:25] <cradek> sure, qemu -cdrom whatever.iso
[11:26:02] <mozmck> well, qemu doesn't exist anymore :) it's qemu-system-i386 or something like that.
[11:26:44] <cradek> mozmck: if it's really slow you might not have enough virtual ram. I've sure seen that.
[11:27:16] <cradek> sadly I can no longer manage to get qemu to have working networking under freedos
[11:27:17] <mozmck> I told it -m 2048
[11:27:29] <cradek> I think for a while the secret was -M isapc, but no longer
[11:28:41] <mozmck> oh, yeah, if I just do qemu-system-i386 -cdrom whatever.iso it says "could not open disk image whatever.iso: Could not open 'whatever.iso': No such file or directory"
[11:28:46] <mozmck> :)
[11:28:57] <mozmck> actually, I get a kernel panic.
[11:30:27] <cradek> qemu -enable-kvm -m 2048 -cdrom binary.hybrid.iso gives me a working desktop in about 25s
[11:30:53] <mozmck> hmm, I'll try -enable-kvm
[11:31:00] <cradek> that does seem to help
[11:31:04] <mozmck> Too many options!
[11:34:36] <mozmck> hmm, maybe I have a permissions issue: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
[11:35:31] <cradek> you might have to be in the kvm group
[11:35:38] <cradek> but I'm not and I don't get that error
[11:35:43] <cradek> it might silently fail
[11:35:51] <cradek> who knows, I'm only a sysadmin
[11:49:20] <mozmck> aha, looks like that's because I have virtualbox running
[11:52:51] <mozmck> yes, closed virtualbox, and -enable-kvm worked and it was *much* faster.
[11:53:31] <mozmck> graphics are messed up a bit
[12:13:50] <mozmck> Looks like I can use virtualbox and tell it not to create a virtual hard disk pretty easily
[12:50:34] <mozmck> what does this mean: halcmd: No license file found.
[12:55:37] <mozmck> I'm writing a component in C, and that's what halcmd said when I tried to run it and exited.
[12:56:31] <kwallace> I've seen this type of message when a component has an old or incorrect license tag: http://linuxcnc.org/docs/html/hal/comp.html#_license_and_authorship
[12:57:31] <mozmck> Well, this is a userspace component, and is not written using halcompile
[12:58:24] <cradek> that string is not in our source tree
[12:58:34] <mozmck> so I don't see how that would apply? how could I even specify a license for halcmd?
[12:58:55] <mozmck> oh, hum...
[12:59:17] <cradek> you're loading it with loadusr?
[12:59:58] <mozmck> Yes, let me check my code - that might actually be in mine somewhere /)
[13:00:23] <cradek> haha now you've got me curious
[13:00:32] <skunkworks> escapind
[13:00:40] <skunkworks> escapined?
[13:02:13] <cradek> ?
[13:02:25] <cradek> usually I can tell what word you're aiming for...
[13:03:27] <mozmck> Yep, it's in my code, but I don't know how it showed up in halcmd - that will take some digging.
[13:03:33] <skunkworks> That was me dropping a calculator on my laptop..
[13:03:53] <skunkworks> (and trying to catch it..)
[13:04:09] <mozmck> It didn't show on the command line, but showed after I ran my little hal file using halrun -I
[13:04:10] <cradek> cradek: haha I mistook it for your spelling. sorry :-)
[13:04:34] <cradek> mozmck: what kind of license file is this? are you guys doing something terrible?
[13:05:32] <mozmck> :) no, we have one feature that we generate a license file for
[13:05:54] <mozmck> so if it is not there then that feature won't work.
[13:06:42] <cradek> if that's part of linuxcnc, that's fine, but the user can just remove the license check from the source and rebuild
[13:07:16] <mozmck> No, it's part of our component that talks to our hardware.
[13:09:05] <cradek> oh hm, I think proprietary hal components are allowed by the hal library's license, but they make everyone sad. are you guys sure that's what you want to do? if you don't do that, you can get your hardware's support in the base distribution (look at mesa for instance)
[13:09:45] <cradek> that and also the love and support of other developers (look at mesa for instance)
[13:11:28] <mozmck> yes, I'm not too keen on the idea either, but that's the way my boss wanted it.
[13:12:21] <cradek> does he know he's shooting footward?
[13:12:47] <mozmck> But I do hope to contribute more in other ways to linuxcnc as I can.
[13:13:13] <cradek> oh I don't doubt your personal motives at all
[13:13:23] <cradek> I hope you don't think I'm saying that
[13:14:09] <mozmck> No, I understand, but I also understand his viewpoint as well.
[13:14:29] <mozmck> just not sure it is entirely valid...
[13:14:32] <skunkworks> don't you need the hardware for this to work?
[13:14:39] <cradek> I think someone else is making hostmot2-compatible hardware now, and this gets more users/testers for the code and doesn't hurt mesa one bit
[13:14:59] <mozmck> Yes, it needs our hardware.
[13:15:01] <cradek> skunkworks: it's usually the (misguided) fear that someone will make compatible hardware
[13:15:07] <skunkworks> ah
[13:15:42] <mozmck> I think mesa probably sells a lot more volume than we do, but I agree that it is probably not an issue.
[13:16:44] <cradek> sure, but they've become the biggest hardware vendor for linuxcnc users BY cooperating with everybody
[13:16:51] <cradek> not in spite of
[13:17:08] <cradek> I'm preaching to various choirs here, I'll stop
[13:17:09] <cradek> sorry
[13:17:14] <mozmck> I agree :)
[13:19:17] <mozmck> you don't bother me, and maybe I'll try again sometime on getting our component opened up.
[13:19:59] <mozmck> although my code is nothing great to look at :)
[17:25:43] <alex_jon1> mozmck: are there some details on this hardware?
[17:30:48] <mozmck> hi alex_joni, we have a thc, and some other things which communicate through an rs485 to usb hub.
[17:30:57] <mozmck> http://www.candcnc.net
[17:41:04] <alex_joni> cool, looks nice
[17:42:39] <mozmck> alex_joni: thanks!
[22:18:53] <mozmck> cradek: I think I worded that statement badly, instead of "you don't bother me, and maybe..." it should have been "you are not bothering me".