![[Home]](/chips.gif)
History of TroubleShooting
1. LinuxCNC doesn't run - wrong kernel |
3. LinuxCNC doesn't run - wrong kernel |
2. LinuxCNC doesn't run - missing lapic |
4. LinuxCNC doesn't run - missing lapic |
|
LinuxCNC uses a RealTime operating system in order to ensure precise timing of i/o signals and trajectory calculations. |
|
LinuxCNC uses a RealTime operating system in order to ensure precise timing of i/o signals and trajectory calculations. |
|
A script is provided with LinuxCNC to load and unload all the realtime modules, and is much quicker for troubleshooting than starting and stopping all of them individually. To use it, type: |
|
A script is provided with LinuxCNC to load and unload all the realtime modules, and is much quicker for troubleshooting than starting and stopping all of them individually. To use it, type: |
|
There are several device files required for Linux applications such as LinuxCNC to talk to the RealTime OS. These device files have a reputation for getting deleted by udev. Make sure that these files exist: |
|
There are several device files required for Linux applications such as LinuxCNC to talk to the RealTime OS. These device files have a reputation for getting deleted by udev. Make sure that these files exist: |
|
Starting in LinuxCNC (then EMC2) version 2.0.4, the number of CPU cycles between invocations of the real-time motion thread is tracked. If you see this message, it usually indicates that some element of your hardware is incompatible with the real-time software. See the next section for more information about possible causes and remedies. |
|
Starting in LinuxCNC (then EMC2) version 2.0.4, the number of CPU cycles between invocations of the real-time motion thread is tracked. If you see this message, it usually indicates that some element of your hardware is incompatible with the real-time software. See the next section for more information about possible causes and remedies. |
|
DO NOT TRY TO RUN LinuxCNC WHILE THE TEST IS RUNNING |
|
DO NOT TRY TO RUN LinuxCNC WHILE THE TEST IS RUNNING |
|
you may be seeing the effects of incompatibility between your display driver and LinuxCNC. |
|
you may be seeing the effects of incompatibility between your display driver and LinuxCNC. |
|
Either edit the xorg.conf file to use the generic slow but reliable Vesa driver (LinuxCNC is not graphics intensive, this won't matter), |
|
Either edit the xorg.conf file to use the generic slow but reliable Vesa driver (LinuxCNC is not graphics intensive, this won't matter), |
|
Recent versions of LinuxCNC do latency tests on the fly, which will help in finding uncooperative hardware. |
|
Recent versions of LinuxCNC do latency tests on the fly, which will help in finding uncooperative hardware. |
|
By default, the LinuxCNC/EMC2 package for Ubuntu disables the linux parport driver entirely, because the linux parport driver interferes with LinuxCNC/EMC2 hardware drivers that use the parallel port. |
|
By default, the LinuxCNC<nowiki>/EMC2 package for Ubuntu disables the linux parport driver entirely, because the linux parport driver interferes with <nowiki>LinuxCNC/EMC2 hardware drivers that use the parallel port. |
|
To reenable the linux parport driver and disable LinuxCNC/EMC2 hardware drivers that use the parallel port, |
|
To re-enable the linux parport driver and disable LinuxCNC/EMC2 hardware drivers that use the parallel port, |
|
If your system has multiple parallel ports, you can also use some for linux and the others for LinuxCNC/EMC2. |
|
If your system has multiple parallel ports, you can also use some for linux and the others for LinuxCNC/EMC2. |