Hallo, I have to come back to this matter, because I got my new Laptop to get a second development system for 2.7 and master. This machine is an ACER E5-771G-7169, it has an Intel I7, 8 GB Ram, and a hybrid graphic card (Intel / Nvidia M840). As standard OS it has Windows 8.1. It was not too hard to use Windows to reparation the 100 GB hard disk to get space for Debian installations. I splited it to 4 partitions (Windows 8.1 , Debian 8.2 MATE ; Debian 8.2 LXDE LinuxCNC and one for common data).
I took the first hurdle, the UEFI Bios and could install Debian 8.2 - amd64 - MATE, but the second hurdle installing LinuxCNC from the ISO could not be taken, because UEFI Bios only accept 64-bit operating systems, even with security boot disabled! Fortunately ACER has a custom mode for other operating systems, otherwise it would not have been possible to boot debian, because the uefi bootloader is not certified! Off topic : Where the hell are we going? Hardware is able to decide witch operating system is allowed. And trying to install debian on some SAMSUNG laptops can kill the laptop! OK; back to the present: - The ISO is 32 bit and does not support UEFI BIOS - Wheesy is not any more the stable version As buildbot says for 2.7-rt-preempt: Jessie (uspace: realtime with RT-Preempt, and simulation) architectures: amd64, i386 I decided to install debian 8.2 - amd64 with LXDE, what was not that complicated after getting the Laptop to boot from the USB Stick. Very strange behavior, no sound, no wlan and the touchpad not working properly, installed from USB Stick with ISO debian-8.2.0-amd64-lxde-CD1.iso, but on the other partition from debian-8.2.0-amd64-netinstall.iso everything works just like a charm. After sorting most of the stuff out, I added the linuxcnc repositories: deb http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt deb-src http://buildbot.linuxcnc.org/ jessie 2.7-rtpreempt and installed LinuxCNC. OK Latency test shows 32035966 ns, that is the highest I ever got! Even a virtual machine is better ;-) But i did no optimation till now. I decides to start LinuxCNC and the gmoccapy, my baby ;-) Error: in module player, component "playbin" not found: After installing "gstreamer0.10-plugins-base" the start went OK. Jeff could you please add that dependence? gmoccapy and gscreen depend on that. Neverthereless the code for both GUI must be adapted to avoid such an error, only for not beeing present "sound". I will fix that as soon as my new development system is running. I do connect the laptop with WLAN0 to the world and want to use eth0 to connect to a MESA 7i76E to control my testing hardware. But as far as I found out till now, that will not be possible, because ther is no realtime kernel for Jessie 64 bit and the info on buildbot is not correct. So, what to do? - Does wheesy support 64 bit completly ? - do all the optimation to the installed lenny system? - change over to mint? - Sit back and wait for others to fix my sistem ;-) For the future IMO: - We need a UEFI Booting 64-bit system, as for new hardware it will be absolutely necessary. - As discussion about the OS GUI we should put at least two of in the new ISO, I would suggest LXDE / XFCE and MATE. So lets discuss and solve! Norbert (gmoccapy) Am 22.12.2015 um 22:24 schrieb Jeff Epler: >> Date: Tue, 29 Sep 2015 15:43:16 -0500 >> From: Jeff Epler <[email protected]> >> To: [email protected] >> Subject: [Emc-developers] LinuxCNC operating system support in master branch >> / for eventual LinuxCNC 2.8 >> >> For LinuxCNC 2.7 we produce packages for >> Ubuntu 10.04 "Lucid Lynx" (rtai realtime) >> Ubuntu 12.04 "Precise Pangolin" (rtai realtime) >> Debian 7.x "Wheezy" (rtai and rt-preempt realtime) >> Debian 8.x "Jessie" (rt-preempt realtime) >> >> Canonical's extended release cycle for Ubuntu 10.04 has now ended. >> >> In addition, I have identified two benefits from dropping support for >> Ubuntu 10.04 in the master branch, meaning that the oldest OSes that >> would be supported in the 2.8 release would be Ubuntu 12.04 and Debian >> 7.x. >> >> - The LD_PRELOAD workaround for the libgl bug can be dropped >> - The minimum Python version requirement can be increased to 2.7. >> >> The second benefit is the major one -- Python 2.7.x has a lot of items >> that can ease the porting process to Python3. Because Python 2.7 has >> end-of-life in 2020, and our release cycle is frequently greater than 1 >> year, we need to start this process soon. >> >> I am happy to postpone this plan by a release cycle if a developer plans >> to maintain 10.04 compatibility during the current release cycle. If >> you plan to do that, please speak up. >> >> Jeff > http://mid.gmane.org/20150929204315.GB63865%40unpythonic.net > > (the process of python3 porting alluded to in that message has not started at > all) > > Jeff > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
