On Thu, 10 Feb 2011 09:26:09 +0200, Alex Joni wrote:
> Can you check the md5sum for the downloaded/burned CD?
> The only explanation I can figure is a mixup in the downloading 
> process..
> the 10.04+emc2 live CD has been used by loads of people (and RT 
> worked for
> most of them).

 CD Title: emc2buntu10.04
   /dev/hda   691916  691916  0 100% /mnt/dvd

 c2 ~ > md5sum /dev/hda
   5283b33b7e23e79da1ee561ad476b05f  /dev/hda

 Which matches the documented checksum on 
 <http://www.linuxcnc.org/content/view/21/4/lang,english/>

 On Wed, 9 Feb 2011 23:17:18 -0600, Chris Radek wrote:
> What exactly were the symptoms?  What did you see?  What was reported
> in dmesg?  What kind of hardware was it?

 I'm in the middle of rebuilding from source so it will take awhile 
 before I fully replicate the issues, but here are some more details.  I 
 did not delve much more deeply once I learned that the kernel modules 
 were not where they were being looked for </lib/modules/*>.  It is 
 possible that I misread the message, so when the recompilation of the 
 kernel is done I will reboot the CD and document the details.

 For now, the machine is a HP ze1115 laptop with 256MB Ram running on a 
 1.1GHz AMD Duron CPU.  Before people start going off about laptops 
 having timing issues, what I wanted to do is to test it to see if it 
 would be good enough to control a SLOW cnc machine.  Also, I had RTAI 
 running on this laptop before, so I know that it will run...


   EBo --


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to