Last update of LinuxCNC Raspberry Pi4 USB does not work

More
5 years 9 months ago #195676 by pauluzs

andypugh wrote:
To be generally usable, the kernel needs to work with the LinuxCNC packages from the buildbot.

The point of making kernel and application packages is so that users don't have to compile from source.


The buildbot is not setup to a create buster arm64 packages, , only ( Buster (arch: amd64) )
So using the buildbot packages is not possible

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago #195678 by andypugh

pauluzs wrote: The buildbot is not setup to a create buster arm64 packages, , only ( Buster (arch: amd64) )
So using the buildbot packages is not possible


Yes, that's my point.

The LinuxCNC-served kernel .deb needs to be compatible with the LinuxCNC-served package.

Or, alternatively, we give up.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #195815 by pauluzs

andypugh wrote:
Yes, that's my point.

The LinuxCNC-served kernel .deb needs to be compatible with the LinuxCNC-served package.

Or, alternatively, we give up.


Not sure what you mean with LinuxCNC-served kernel .deb, i'm using the standard vanilla debian buster kernel optional with linux-image-rt-arm64 Also from vanilla debian (backports)
Giving up because the buildbot doesn't build the arm64 packages is like the chicken vs egg question. i don't manage the buildbot.

That being said, explaning :

i did manage to compile linuxcnc master from source

What i did is build the userspace .deb packages for master and 2.8
This works on normal (sim), as well as the realtime kernel
Code:
linuxcnc-doc-cn_2.8.1_all.deb linuxcnc-doc-cn_2.9.0~pre0_all.deb linuxcnc-doc-en_2.8.1_all.deb linuxcnc-doc-en_2.9.0~pre0_all.deb linuxcnc-doc-es_2.8.1_all.deb linuxcnc-doc-es_2.9.0~pre0_all.deb linuxcnc-doc-fr_2.8.1_all.deb linuxcnc-doc-fr_2.9.0~pre0_all.deb linuxcnc-uspace-dbgsym_2.8.1_arm64.deb linuxcnc-uspace-dbgsym_2.9.0~pre0_arm64.deb linuxcnc-uspace-dev_2.8.1_arm64.deb linuxcnc-uspace-dev_2.9.0~pre0_arm64.deb linuxcnc-uspace_2.8.1_arm64.deb linuxcnc-uspace_2.9.0~pre0_arm64.deb

These can then be installed just like a distrubuted buildbot .deb linuxcnc package

Here is how:
Code:
#fix missing python-gtksourceview2 for buster sudo apt install wget -y wget http://ftp.debian.org/debian/pool/main/p/pygtksourceview/python-gtksourceview2_2.10.1-3_arm64.deb sudo apt install ./python-gtksourceview2_2.10.1-3_arm64.deb rm python-gtksourceview2_2.10.1-3_arm64.deb #Install devscripts, used to build .deb packages sudo apt install devscripts -y #Get linuxcnc source git clone git://github.com/linuxcnc/linuxcnc.git linuxcnc-dev #Change into linuxcnc-dev directory cd linuxcnc-dev #Select linuxcnc branch (master, 2.8) git checkout master git branch #Configure linuxcnc uspace ./debian/configure uspace #build and install the build dependencies .deb package sudo mk-build-deps -i #Build the .deb package for linuxcnc dpkg-buildpackage -b -uc #Install the created linuxcnc .deb package sudo apt install ../linuxcnc-uspace_2.9.0~pre0_arm64.deb

If there is a need for a seperate arm64 topic for this let me know
Last edit: 5 years 9 months ago by pauluzs.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #195837 by andypugh

pauluzs wrote:

andypugh wrote: Giving up because the buildbot doesn't build the arm64 packages is like the chicken vs egg question. i don't manage the buildbot.


The buildbot is fairly deeply embedded in how we test and release the packages. Unfortunately the chap who runs it is not as deeply involved in the project as he used to be.

I want to stay with the buildbot-created debs as that is how we can be sure that updates and fixes get properly distributed.

I have had some success with the LinuxCNC/raspberry-linux repository and the SD-card install instructions here:
www.raspberrypi.org/documentation/linux/kernel/building.md

I suspect that the debian packages made by that repository do not copy across all the files that the manual process does.



(This is with a brand-new 2GB Pi4. Maybe I should have got the 8GB one to be a better test, but it is just that bit too expensive a thing for me to buy without needing.)

Last edit: 5 years 9 months ago by andypugh.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #195843 by pauluzs

andypugh wrote: I suspect that the debian packages made by that repository do not copy across all the files that the manual process does.


Which one do you mean with "that repository "?

(This is with a brand-new 2GB Pi4. Maybe I should have got the 8GB one to be a better test, but it is just that bit too expensive a thing for me to buy without needing.)


True, using bone stock 5.9 arm64 realtime kernel, only thing i did is force_turbo=1 to prevent cpu-scaling.
This is 2 min run on rpi4_4GB
Last edit: 5 years 9 months ago by pauluzs.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago #195851 by andypugh
Well, I am confused now.

Intending to investigate the effect of limiting memory to 3GB I made a new standard 32-bit SD card image, booted my new 2GB Pi4 (bought specifically to debug this reported issue) and followed the instructions here in the LinuxCNC docs:
linuxcnc.org/docs/2.8/html/getting-start...lling_on_raspbian_10
Contrary to the reports in this and other threads, it all "just worked".

I moved the SD card to my Pi400, and that worked, and then to my old 4GB Pi4, and that worked.

Is there _actually_ a problem?

Please Log in or Create an account to join the conversation.

Time to create page: 0.342 seconds
Powered by Kunena Forum