cvs was down for awhile because a gateway machine crashed. service should now be restored.
new dapper non RT VM begins downloading 214 updates....
did you ever get the extra RAM working?
for some value of working
(a value around 3.2G)
server kernel will recognize all 4G, but there is no nvidia driver for that kernel
nv driver has suck
vesa driver is usable, but only has 16 bit memory depth if I want full resolution
you could use Ubuntu 64-bit
(and of course is software GLX, but that seems acceptable for the kind of stuff I do - AXIS and vismach
I have no desire to explore 64bit at the moment
at least with 8.04, even Wine seems to work pretty well on 64-bit
I'm still running 6.06 on this machine
yep, so an upgrade would be a hassle
I'm seriously tempted to jump to 8.04 - the 8.04 server kernal has a linux-restricted-modules package, which should have the nvidia driver
I'm pretty sure the only problems I've had on 64-bit (that I wouldn't have had on 32-bit also) are related to compiling ATI proprietary drivers
hmm, the first time I thought it was a coincidence, but something weird is happening
I have a MyBook USB external hard drive
it is umount'ed, and spun down
when I go into vmware console and create a new vm (click on new, haven't filled in any of the dialogs yet), the drive spins up
doesn't mount, just spins up, later times out and spins down again
it could be doing a partition check
that makes sense (I think)
hmm, I bet dapper doens't actually need 512M of memory once installed
aren't sliders nice? :)
the breezy vm's have 128M, the win95 one has 64M
I just dropped the non-rt dapper (new vm) to 256, I bet I can do the same with the RT one once installed
you can set the VMs to boot into console mode instead of desktop too
I dunno why I thought that I had all the vm's at 512M
neato - the 'at speed' stuff works great
if facing in CSS on the lathe, when it rapids back out to the large radius, it waits for the slowdown before making the next pass
it will also be useful on mills...
so if I hook up a 'timedelay' component on my mill and set the timeout right, I'll get something useful?
to wait for spin-up at spindle on?
yes that would work since it's single-speed and presumably always takes about the same amount of time.
then it will be able to rapid while spinning up, but it won't feed until the delay has passed
I noticed my actual-spindle-speed display flashes negative agazillion on each threading pass
not a surprised, I suppose - and it must not hurt anything
but a good velocity output from mesa would be nice.
I suppose that makes sense -- it's ddt, not from the driver, right?
if it's from the driver it should be possible to do better
does the m5i20 firmware have the timestamp register?
* SWPadnos doesn't think so
I don't think hm4 does
I bet hm2 does
right, unless you guys added it
HM2 has it, but I guess it's not used yet
from PeteW's comments
I cut a whole mess of cast iron on it tonight - was fun
I was talking specifically about velocity estimate over an index reset
I understand - two different concerns
right, I don't think there's any support in the HM4 firmware to make the 5i20 driver any better than ddt
hm2 has two registers for reading the encoder: one is status bits + counter bits, and one is latched counter bits + counter bits. the first one is what is currently being read, I think.
there is in the hostmot2 firmware, but it's unused in the driver so far
I put a dumb velocity output in the driver - it was useless since the spindle encoder is low counts
I run the ddt very slow and it works ok
or maybe there are three, because I just named two and not the one for high-quality velocity estimation
I think it also has a timestamp register so the driver could get accurate counts and time intervals
index will screw things up at the moment, but it may be possible to just latch the count instead of resetting it
(I think Pete said that was possible with the current firmware, but it's not what the driver does)
on the cycle when it resets, just output the previous velocity?
seems like it would be fine
see you jepler
that would probably work OK for spindles up to 60000 RPM anyway :)
is the firmware packaging i checked in about what you were thinking of?
I didn't look closely, but there is one problem I anticipate: on -sim systems the package probably shouldn't be built or recommended
I think it needs some work in debian/configure to make this possible
right, i see
is there currently a -sim package? i didnt see one
you build the sim package by: debian/configure sim; dpkg-buildpackage -rfakeroot
that debian/configure script confuses me a bit, i'm not used to there being one there
no, it's probably undebianish to do it that way
but unfortunately we don't have debian experts, only me
it seems to be getting the job done, which is not nothing ;-)
i'm no debian expert but i'll take a look at it
would it make sense to compile both emc2 and emc2-sim packages, using different build dirs maybe?
seb_kuzminsky: that's only half of the story
well, it's a bit of a mess...
we also use configure to get the right kernel for building against the headers
for example I have 3-4 rtai kernels installed on my box
in case users have multiple rtai kernels installed, for different sandbox RIPs
and use debian/configure to point to the right one
RP isn't sim
and consider 8.10: there's no realtime kernel, but you can almost certainly build sim
another thing I'm not sure about.. how do packages handle multiple distro's?
for example building debian (etch or whatever) and ubuntu packages..
are there packages out there that do that? or are there branches/forks that do that..
in some cases you can use alternatives in Depends and Build-Depends (the "|") character
alex_joni: i'm not sure how that's done, i think by forking the debian/ dir
Build-Depends: ubuntu-package-name | debian-package-name
you guys have the debian build system fixed by the time I get back, ok?
yeah, but you saw that Build-Depends doesn't work with |
only in Depends it works..
(remember the lyx stuff we had to move to debian/configure)
lyx-qt | lyx
jepler: Yes Sir! ;-)
jepler: and rpm's if you have a long lunch
and windows .nsi installers ;-)
it's actually .msi afaik
"..structured as OLE Structured Storage Files and commonly known as "MSI files", from their default file extension"
ok i'll do .deb, you do .msi
back to the dayjob for me
I've been looking at the document generation using asciidoc to create the xml files and xsltproc to create the xml.fo files then fop to create the html and pdf files
it there anything I need to look out for?
tables and pictures mostly
text will surely work/look right :)
ok, I'm working on a sample to check the layout and look of both
might take a while :)
one thing we could care about is resolution for print/web
maybe it works to have 2 different resolutions for the pictures, or the translate process can do that..
yea the stylesheet can take care of different things for html and pdf
I'm about to get a grasp of the whole document chain :O
sounds like we have a volunteer to push this :D
* BigJohnT says "who me?"
kinda fun really
well I got a fo with only one error :)
fo = following error?
fo formatted output file :)
isn't one error usually enough?
it's better than having many!
[Global Notice] Hi all, In about five (5) minutes two of our client servers will be going down for maintenance, the downtime window is set to one hour, but in reality it should be significantly less. Affected users ~1200. Thank you for using freenode and have a great day!
[Global Notice] Hi all, the upgrades went fine, both servers are now back in rotation -- it went a lot quicker than expected, you'd never guess we run gentoo! Apologies for the inconvenience caused and have a nice day!