Issues with gcc-arm-linux-gnueabihf package

[lkilo]

Hello Frank,

I've got some trouble installing the "gcc-arm-linux-gnueabihf" packet via apt.
I also tried manualy downloading the packet and installing it with dpkg but it says I've got the wrong architecture.
If it helps: uname -a output: "Linux server-00-bpi 4.4.70-BPI-R2-Kernel #1 SMP Tue Nov 28 10:59:01 CST 2017 armv7l armv7l armv7l GNU/Linux"

Regards

[frank-w]

You try to compile on r2 directly? Then you do not need this package...this package is called cross-compiler to build armhf-binaries on other architectures

[lkilo]

Ok. Well, I compiled the kernel on my BPI2 and received a "bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb" package. I tried to install it via dpkg --install, it succeeded, but I'm still on the old kernel after a reboot. Do I need to copy the uimage manually into the BPI-BOOT partition?

[frank-w]

Please check with "mount" if /boot is your mounted boot-partition or simply a folder. Official images do not mount /boot and uboot did not found your kernel because it lay on BPI-ROOT/boot instead of BPI-BOOT

I'm also not sure if postinst works (add your new kernel to uenv.txt). deb-package function is currently experimental...working on postinst-scripts...it seems i need a preinst too to check for mounted /boot => added to build.sh

[lkilo]

There is nothing mounted to /boot.
While compiling kernel the script said that there's a problem with /boot, after I did choose to install the kernel directly.
I'm not sure what to do now.

[frank-w]

• rename /boot to any other
• create an empty /boot
• mount /dev/mmcblk0p1 /boot
  try again install directly

[lkilo]

I just receive:
root@server-00-bpi:~# sudo dpkg --install /home/pi/bpi-r2-4.14/debian/bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb
(Reading database ... 252129 files and directories currently installed.)
Preparing to unpack .../bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb ...
Unpacking bananapi-r2-image-4.14-main (4.14.59-1) over (4.14.59-1) ...
dpkg: error processing archive /home/pi/bpi-r2-4.14/debian/bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb (--install):
error setting ownership of './boot/bananapi/bpi-r2/linux/uImage_4.14.59-main': Operation not permitted
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
/var/lib/dpkg/tmp.ci/postrm: 7: /var/lib/dpkg/tmp.ci/postrm: Syntax error: end of file unexpected (expecting ")")
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 2
Errors were encountered while processing:
/home/pi/bpi-r2-4.14/debian/bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb

[frank-w]

as i said, debian-package is experiemental...i try a bit to get the maintainer-scripts running for complete install...

previous version has only unpacked the files...in my local repo i fixed the syntax-error, but postinst-script seems not to be called

[lkilo]

Is there another way to get the 4.14 Kernel working? I did try the precompiled 4.14 kernel, but my bpi wont boot after copying the files from the archive.

[frank-w]

you can use build.sh to install directly on sd-card
if using the precompiled images you have to unpack the files to the BPI-OOT-folder to BPI-BOOT-Partition and from inside BPI-ROOT to BPI-ROOT

[lkilo]

The installation process succeeded, but now i got the same problem like with the precompiled kernel. The board isn't booting. The red lights lights for about 15 seconds and then turns off and nothing happens. Is there any way to fix that?

[frank-w]

if you have a usb2serial-cable you can connect to the board through debug-uart and look with minicom/putty what happens

https://www.fw-web.de/dokuwiki/doku.php?id=en/bpi-r2/debug-uart

fixed now the maintainers-scripts...have installed the 4.14.59 via deb in my ubuntu-image

[frank-w]

Btw if you switch from 4.4 to 4.14 you have to change network-config because of dsa-driver in 4.14.

[lkilo]

In the /etc/network/infterfaces file?

[frank-w]

Right. In my wiki you'll find an example https://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:network:start#permanent

but this should not poweroff the r2...it is simply not reachable because ip-config in 4.4 is done on ethx and in 4.14 on wan/lanx

[frank-w]

btw. Green and blue near gpio go off this is right,red should stay on...4.4 and mainline-kernel have a bug where thiis leds are stay on at boot which i have fixed