[12:34:44] -!- logger[psha] [logger[psha]!~email@example.com] has joined #linuxcnc-devel
[freenode-info] help freenode weed out clonebots -- please register your IRC nick and auto-identify: http://freenode.net/faq.shtml#nicksetup
[12:36:09] -!- Wildhoney has quit [Ping timeout: 264 seconds]
[12:38:25] -!- b_b has quit [Changing host]
[12:46:53] -!- sirdancealo2 has quit [Ping timeout: 240 seconds]
[12:47:03] krusty_ar_ is now known as krusty_ar
[12:57:53] -!- sirdancealot has quit [Ping timeout: 240 seconds]
[12:59:30] -!- skorasaurus has quit [Quit: WeeChat 0.3.7]
[13:13:57] -!- Kup has quit [Ping timeout: 264 seconds]
[13:17:11] -!- kwallace [firstname.lastname@example.org] has joined #linuxcnc-devel
[13:17:51] -!- KekS- has quit [Quit: Page closed]
[13:17:51] -!- Spida has quit [Ping timeout: 240 seconds]
[13:20:53] -!- odogono has quit [Ping timeout: 240 seconds]
[13:29:09] -!- md-2 has quit [Ping timeout: 248 seconds]
[13:35:54] -!- theorbtwo has quit [Remote host closed the connection]
[13:49:20] md2 is now known as Guest26486
[13:52:09] -!- maximilian_h [email@example.com] has joined #linuxcnc-devel
[13:52:58] -!- md-2 has quit [Ping timeout: 276 seconds]
[13:57:31] -!- riz_ [riz_!62dd7d6e@gateway/web/freenode/ip.184.108.40.206] has joined #linuxcnc-devel
[13:59:11] -!- rob__H [rob__Hfirstname.lastname@example.org] has joined #linuxcnc-devel
When it comes to mdi commands. I see that halui takes in mdi_commands[n]. Is this an array of commands whereby multiple commands can be executed at once iwth mdi, or is this just an array to hold a single command?
[14:02:48] -!- rob_h has quit [Ping timeout: 256 seconds]
what are you trying to do?
I'm trying to run multi-line mdi commands
rather than a single command at a time
ah, make a sub, and use halui to issue O<sub> call
[14:06:58] -!- theorbtwo has quit [Remote host closed the connection]
I do this in one of my fanuc systems now
So mdi_commands[n] just refers to a single line string of length [n]?
in the ini file, you specify one line per halui-mdi input pin
I don't remember how it's stored in the C and it doesn't matter
mdi commands are one line at a time, whether you type them or they come from the ini file via halui
but that one line can be O-call
and this is the answer to your problem
OK, I see
Thanks. Will try it out
[14:10:47] <cradek> http://www.linuxcnc.org/docs/html/man/man1/halui.1.html
see the mdi section here in the halui docs
OK. I'll check it out
[14:34:23] -!- knownasilya has quit [Ping timeout: 240 seconds]
[14:36:08] -!- Kup has quit [Read error: Connection reset by peer]
[14:40:24] -!- ktchk has quit [Ping timeout: 268 seconds]
[14:41:50] -!- psha[work] has quit [Quit: Lost terminal]
[14:42:36] -!- ktchk [email@example.com] has joined #linuxcnc-devel
Hello ubuntu precise rtai linuxcnc 2.5 is there any success road map?
ktchk: this RTAI tree is reported to work with 3.x kernels and run linuxcnc: https://github.com/ShabbyX/RTAI
ktchk: I have not tried it. if you try it, please report your results here!
cradek: how about linuxcnc 2.5 can it be complile under rtai3.x?
I think if you can get that rtai built, linuxcnc 2.5 will run under it, but I have not tried it.
Ok I have a ssd can test on. will come back later.
seb_kuzminsky: hmm, I thought we decided 4th saturday, not last saturday, but I see that's not in the first meeting's minutes
[14:57:17] -!- gimps_ has quit [Client Quit]
[14:57:22] -!- kwallace2 [firstname.lastname@example.org] has joined #linuxcnc-devel
[14:57:39] -!- gimps has quit [Disconnected by services]
ok I'm not imagining that there was some support for that: http://meetlog.archivist.info/meeting.php?id=201306
there was no firm decision
[14:58:54] -!- kwallace has quit [Ping timeout: 268 seconds]
[14:59:42] -!- f1oat [f1oat!~f1oat@AMontsouris-553-1-69-16.w92-151.abo.wanadoo.fr] has joined #linuxcnc-devel
seb_kuzminsky: the irc channel topic and http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Meeting201308
don't agree so we need to figure this out asap
[15:04:28] -!- riz_ has quit [Quit: Page closed]
[15:08:29] -!- JT-Shop has quit [Read error: Connection reset by peer]
[15:08:29] -!- jthornton_ has quit [Read error: Connection reset by peer]
[15:08:58] -!- jthornton_ [email@example.com] has joined #linuxcnc-devel
[15:08:58] -!- JT-Shop [JT-Shop!~John@220.127.116.11] has joined #linuxcnc-devel
[15:12:35] -!- syyl_ws has quit [Quit: Verlassend]
[15:14:37] -!- ve7it [ve7it!~LawrenceG@S01060014d19d0b68.pk.shawcable.net] has joined #linuxcnc-devel
cradek: darn, i messed it up :-(
ok it seems like the 4th saturday had more support than the last saturday
[15:22:48] -!- maximilian_h has quit [Quit: Leaving.]
i updated the wiki, i'll mail out a correction to my earlier announcement
and i updated my proposal on the 2013 August agenda to say "4th Saturday" instead of "last Saturday"
[15:41:14] -!- mhaberler has quit [Quit: mhaberler]
[15:42:45] -!- AR__ has quit [Ping timeout: 264 seconds]
I didn't know if you had reasons to prefer last over 4th
my only reason is that it makes it 0.1% faster to identify the square to click in in the calendar
I didn't remember that we decided not to decide yet, haha
it's the first one fom the end, not the 4th one from the beginning
i guess the civic thing for me to do last month would have been to send out a broadcast email trying to build consensus for one or the other
i dont actually care which it is, i just want us to pick one so i dont have to think about it any more
oh btw, i built linux 3.4.53 with the shabby/memleak rtai, gonna try booting it on real hardware one of the next couple of nights
jepler said 4th was easier than last for putting in software calendar things - if this is true it's a strong reason I think (I don't use any calendaring stuff)
also I object on principle to calendar being a verb
[15:48:53] -!- sirdancealot has quit [Ping timeout: 240 seconds]
all the calendars i've used support both "Nth from the beginning" and "Nth from the end", i think
but like i said, i really dont care
and if i'd known people would have a preference for the other way of identifying a saturday i would have chosen it from the start
[15:49:47] -!- ktchk has quit [Ping timeout: 260 seconds]
it's as if you're totally reasonable
only on things that don't matter ;-)
might that be useful for precise? I think precise uses an offspring of 3.2.0
yes i think it will be useful for precise
I am nervous about abandoning the distro's kernel - that's sure led to misery in the past
i've been doing all my rtai testing so far on paolo's 3.5.7 kernel on precise, and haven't run into any kernel/usr problems
skunkworks had network card problems
ah yes, i remember that
and I bet neither of you depend on terrible firmware blobs
stuff like that is where the misery is usually found
i guess we could ask memleak to port his kernel patch to 3.2
but my mind's open about this - I'm not saying it's a dead end or anything
he seems to enjoy that kind of work, and helpful
heck maybe it'd just work? I have no idea how different they are
i think it's worth trying 3.4 on precise
yeah he's awesome
sure, why not
3.4 is a long-term kernel maintained by greg k-h, unlike 3.2 which is eol-ed and only sporadically maintained by canonical now
I need to find me some newer hardware that can run precise+rtai
oh, it sure makes sense to move to 3.4 if possible then
i'm sad it doesnt run well on your old hardware, and confused, because it runs well on my old hardware
maybe your old hardware is older than my old hardware
yeah I couldn't get it installed on my P4 at all
i ran it on my P4
the one that runs my bridgeport
I also tried an old server class xeon box with no luck
I didn't even bother to try my dual P3
[15:57:05] -!- capricorn_1 has quit [Quit: Konversation terminated!]
i've also run precise (not rtai) on an old pre-p4 laptop that i gave to my nephew
what happens when these machines don't work for you?
various wrong things I didn't record carefully :-/
oh, that! i think i heard another bug report like that!
I think one made it to the desktop, but it was weirdly broken somehow
the other would just do stupid grub tricks like freezing with the rectangle in the corner of the screen
[15:58:44] -!- b_b has quit [Excess Flood]
[15:59:02] -!- b_b has quit [Excess Flood]
did you install from usb or optical?
[15:59:13] -!- b_b has quit [Excess Flood]
[15:59:22] -!- b_b has quit [Changing host]
[15:59:24] -!- b_b has quit [Excess Flood]
usb, musta been
my usb installer was fine - I booted my (newish) desktop from it - but maybe usb+old hardware = doom
[15:59:37] -!- b_b has quit [Remote host closed the connection]
ah, that could be
we should find one of those floppy disks or dvds or whatever they were called
I remember trying seb_kuzminsky rtai build recently.. I don't remember if it had the same network card issue... (as xenomai)
[16:00:10] -!- b_b has quit [Changing host]
i remember you tried it skunkworks
you have that fateful nic, rtl 86 something something
you mean the first-known fateful nic
e1000s for everyone!
that sounds right
soemthing like that
I love motherboards with slots - driver is weird? get different card from pile, throw troublesome card in pile (do this in order)
i hereby nickname that nic "cancer"
the 8168 driver running the 8168 nic
the 8169 driver running the 8168 nic
nic cancer.. Sounds like a super hero..
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
funny, that's what's in my (mostly slotless) newish desktop
works fine in lucid and precise
yeah i guess it's the cheapest thing available, so all mb manufacturers use it
cradek, sure - just don't add realtime..
well, i think it's "just dont switch away from linux 3.2"
[16:04:53] -!- sirdancealot has quit [Ping timeout: 240 seconds]
yeah it's not a question of realtime
this is zultrons quote..
The r8169 driver is finicky when driving an r8168 NIC, and won't drive it at 1Gb in any case. The Xenomai patches break it entirely.
someone has slogged through the mud and made it work in lucid and precise, and we don't benefit from that work when we use a different kernel
oh xenomai is actually what breaks it? I didn't expect that.
shows what I know
if so, rtai breaks it too
I'm sad. it's been so long since linux + wired ethernet was hard to get working
i think the driver worked in older kernels, then someone hacked on it and broke this particular very common hardware, and that went into the newer kernel that both rtai and xenomai are based on
If you have an r8168 and networking problems (or want full 1Gb speed), install the correct r8168 driver. The r8169 may be loaded in the initrd, in which case the r8168 cannot be automatically loaded, because the two drivers conflict. To fix this problem, the initrd must be rebuilt to include the r8168.
[16:09:51] -!- dway has quit [Quit: NOOOOOOooooooooo……]
$ lsmod|grep r8
r8169 62154 0
my precise machine is using r8169 and gigabit works
I didn't do anything special
oh but it's 3.2 which is before the breakage?
sorry - I have nothing more to copy and paste..
[16:14:17] -!- abetusk has quit [Remote host closed the connection]
Zultron gave me specific instructions that fixed the 8168 issue on my (D525) test system
so he may be the one to ask about 8169/8168 issues
it is on the wiki
(8168 is newer BTW)
wait - I do have one more thing to copy and paste..
[16:17:27] <skunkworks> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?XenomaiKernelPackages
the r8169 driver driving the 8168 doesn't work well, only driving it at 100Mb if it works at all.
Wonder if the problem is that the 8169 driver thinks its OK with a 8168 (when it clearly is not)
Lots of kernel patches mess it up, even though they don't touch it directly at all.
Xen and xenomai are two examples.
I'd put money on RTAI messing it up, too.
yay for equality
zultron: do you know: did this become the case after kernel 3.2.0? I ask because mine works with the precise kernel.
I don't really know, but I do know that the Xen kernel breaks it for 2.6.something.
I am a heavy gigabit user (my home directory and other important things are on nfs) and it's using the 8169 driver
interesting, really old problem then
Yeah. A quick google search turns up LOTS of hits.
It's RealTek's fault. :P
More annoying is you can't put an 8168 and 8169 NIC in the same host at the same time.
I snap up e1000 cards whenever I see them at goodwill...
That's exactly what I did after figuring out this mess a year ago.
[16:31:35] -!- psha [firstname.lastname@example.org] has joined #linuxcnc-devel
[16:31:52] -!- AR_ has quit [Ping timeout: 246 seconds]
[16:33:19] -!- mhaberler has quit [Quit: mhaberler]
[16:33:26] -!- `Nerobro has quit [Ping timeout: 240 seconds]
Maybe the 8169 driver should not indicate it works with 8168s...
this is an issue with the RTNet driver as well
Yeah, it's hard to believe that with the proliferation of these chipsets that nobody's gotten around to fixing the problem.
the 8168 has got to be one of the most common GigE chips on low cost MBs
sort of like the next gen RTK8139 (sort of sad that buggy RTK crap pushes out decent chips however)
[16:45:06] -!- Guest26486 has quit [Remote host closed the connection]
it works fine with winders and it's the cheapest, pretty much all the mainboard MBA's care about
we tried using some RTK chips in PC/104 Ethernet cards a while ago
reliably failed temperature tests
They probably fix the bugs in their windows drivers since thats their bread&butter
[16:49:04] -!- odogono_ has quit [Quit: odogono_]
[16:52:13] -!- jfire has quit [Quit: Leaving.]
[16:52:45] -!- motioncontrol has quit [Quit: Sto andando via]
[16:54:58] -!- R2E4_ has quit [Ping timeout: 276 seconds]
the latest R8168 driver is from last month
[17:00:23] -!- nspiel has quit [Ping timeout: 250 seconds]
[17:04:53] -!- sirdancealot has quit [Ping timeout: 240 seconds]
been running RTAI and 2.4 kernel all week on this with no issues yet http://www.gigabyte.us/products/product-page.aspx?pid=3447#sp
uses RT 8111C
do you mean 3.4?
ShabbyX git rtai? have you run linuxcnc 2.5 on it?
pretty sure memleak has, he'll be back later
it's his system here
cool, ktchk was asking this question earlier, I'd like to hear too
in fact he developed it all using that board
latency is still poor on the new AMD Socket FM2 Athlon™/A- Series Processors
not sure why yet
I think he's going to get 64 bit working and then work with Lars on the solving the latency issues
well this is appropos: https://lwn.net/Articles/561327/
I have access to the AMD emulator for all the cpu's and chipsets, it would be interesting if we find anything in the hardware design that we can recommend to AMD to change to get latency below 1uS or better
[17:14:13] -!- Wildhoney has quit [Ping timeout: 248 seconds]
I would guess that unless all bus master transfers are are disabled/made synchronous with the RT threads I doubt if 1 usec is possible
[17:20:58] -!- erictheise has quit [Ping timeout: 276 seconds]
[17:20:58] erictheise_ is now known as erictheise
Though a early thread invocation, spin till timer match should get better than
1 usec on most hardware at the expense of 100*maxlatency/threadperiod % CPU wastage
there was an Atom board that was under 1uS a few years ago
1 usec if no I/O was done...
~50 usec if done
Padnos used it for something
speaking of him, what has become of him?
Yeah no video
I never tried the board, only heard about his experience
[17:33:45] -!- javisantana has quit [Ping timeout: 264 seconds]
[17:37:11] -!- andypugh [email@example.com] has joined #linuxcnc-devel
[17:37:40] -!- jfire has quit [Ping timeout: 264 seconds]
[17:41:37] -!- `Nerobro_ has quit [Read error: Connection reset by peer]
[17:42:49] -!- fragalot has quit [Read error: Connection reset by peer]
[17:43:52] -!- IchGuckLive has quit [Quit: ChatZilla 0.9.87 [Firefox 20.0/20130329043827]]
[17:52:21] mrsun is now known as MrSunshine
[18:02:27] -!- zzolo has quit [Quit: zzolo]
[18:36:03] -!- ve7it has quit [Remote host closed the connection]
[18:47:34] Amir_ is now known as Guest50868
[18:50:16] -!- Guest50868 has quit [Client Quit]
[18:51:10] -!- javisantana has quit [Remote host closed the connection]
[18:53:57] -!- ktchk [firstname.lastname@example.org] has joined #linuxcnc-devel
[18:55:35] -!- nikola has quit [Quit: Page closed]
[18:55:59] -!- tom_o_t has quit [Quit: Leaving]
[18:57:09] -!- franco_64 has quit [Quit: Page closed]