<![CDATA[PINE64 - Debian]]>

<![CDATA[PINE64 - Debian]]> https://forum.pine64.org/ Sun, 17 May 2026 21:49:42 +0000 MyBB <![CDATA[lost eth0 on my pine64]]> https://forum.pine64.org/showthread.php?tid=13138 Tue, 16 Feb 2021 17:22:53 +0000 psarazin]]> https://forum.pine64.org/showthread.php?tid=13138 newbies on Pine64 and armbian I cannot connect network using ethernet connector
just installed armbian today and the wlan is working fine but system looks cannot fine eth0

the debian version used is

cat debian_version
10.7i

now I used armbian-config to setup the Wifi but here eth0 is no more present....

I don't know where I can go to enforce driver or something like that ... I more Windows users ;-)

Thanks in advance for your support ...

Furthemore my english is not perfect I'm French

Pierre.]]> newbies on Pine64 and armbian I cannot connect network using ethernet connector
just installed armbian today and the wlan is working fine but system looks cannot fine eth0

the debian version used is

cat debian_version
10.7i

now I used armbian-config to setup the Wifi but here eth0 is no more present....

I don't know where I can go to enforce driver or something like that ... I more Windows users ;-)

Thanks in advance for your support ...

Furthemore my english is not perfect I'm French

Pierre.]]> <![CDATA[Debian installer on Pine A64+ but no hdmi]]> https://forum.pine64.org/showthread.php?tid=9943 Mon, 25 May 2020 17:24:39 +0000 mrwick]]> https://forum.pine64.org/showthread.php?tid=9943
After following the steps on the debian wiki and running into no kernel modules found issues, I ended up downloading directly from:

http://ftp.debian.org/debian/dists/stabl...rd-images/

doing the zcat > to the card and was able to do a fairly regular debian install process.

Strange thing is, it is always over the console with the olimex USB-Serial cable:

https://www.olimex.com/Products/Componen...l-Cable-F/

OK, no problem for an install, but then going to testing, kernel 5.6.0-1-arm64 and still no HDMI, even console. Serial is nice, and ssh is most likely the main way I will be interfacing with the computer, but I am curious as to how to troubleshoot the HDMI output.

Still searching but maybe someone here can already point me in the right direction]]>
After following the steps on the debian wiki and running into no kernel modules found issues, I ended up downloading directly from:

http://ftp.debian.org/debian/dists/stabl...rd-images/

doing the zcat > to the card and was able to do a fairly regular debian install process.

Strange thing is, it is always over the console with the olimex USB-Serial cable:

https://www.olimex.com/Products/Componen...l-Cable-F/

OK, no problem for an install, but then going to testing, kernel 5.6.0-1-arm64 and still no HDMI, even console. Serial is nice, and ssh is most likely the main way I will be interfacing with the computer, but I am curious as to how to troubleshoot the HDMI output.

Still searching but maybe someone here can already point me in the right direction]]> <![CDATA[Captive portal at school not working on the Pinebook pro]]> https://forum.pine64.org/showthread.php?tid=8771 Tue, 14 Jan 2020 13:00:22 +0000 WilliamZieg]]> https://forum.pine64.org/showthread.php?tid=8771 <![CDATA[OMV/debian/systemd: how to start the network]]> https://forum.pine64.org/showthread.php?tid=8535 Tue, 10 Dec 2019 23:29:50 +0000 kittyland]]> https://forum.pine64.org/showthread.php?tid=8535
I've been using ayufan's OMV for some time. Lately, after some updates, and a reboot, it would not boot properly, and after anpther reboot, it would not boot at all and leave no human readable traces on the SD card.

With some serial connection, it turns out that it boots after all, it just stays invisible.

One of the USB disks has acquired USB connection troubles (btw is there any way to get any USB hard disk working with any SBC? These are extremely rare). Which turns out to be the only backdoor into the system.

Without the broken USB disk, systemd starts some things (notably excluding the network, preventing any troubleshooting), then it complains about the missing disks, it also once ran a (preparation? prerequisite? I cannot remember) job for OMV, with no time limit, and yes it actually never finishes. There is no way to get in and debug or fix anything, all I can do is ... well ... "watch s..omething scroll by".

With the broken USB disk, it goes into maintenance mode, and can demonstrate that indeed the network can be started, there is no reason to hold back.

How can I change the systemd configuration to just start the network? And ssh, rsyslog, ntp at the very least?

thanks a lot]]>
I've been using ayufan's OMV for some time. Lately, after some updates, and a reboot, it would not boot properly, and after anpther reboot, it would not boot at all and leave no human readable traces on the SD card.

With some serial connection, it turns out that it boots after all, it just stays invisible.

One of the USB disks has acquired USB connection troubles (btw is there any way to get any USB hard disk working with any SBC? These are extremely rare). Which turns out to be the only backdoor into the system.

Without the broken USB disk, systemd starts some things (notably excluding the network, preventing any troubleshooting), then it complains about the missing disks, it also once ran a (preparation? prerequisite? I cannot remember) job for OMV, with no time limit, and yes it actually never finishes. There is no way to get in and debug or fix anything, all I can do is ... well ... "watch s..omething scroll by".

With the broken USB disk, it goes into maintenance mode, and can demonstrate that indeed the network can be started, there is no reason to hold back.

How can I change the systemd configuration to just start the network? And ssh, rsyslog, ntp at the very least?

thanks a lot]]> <![CDATA[Switching from Mint or MX Linux to Pinebook Pro]]> https://forum.pine64.org/showthread.php?tid=7671 Sun, 07 Jul 2019 14:06:03 +0000 User 12599]]> https://forum.pine64.org/showthread.php?tid=7671

Switching from Winblows after 18 years to Linux in 2009, I've been utilizing primarily Linux Mint with the XFCE Desktop as well as MX Linux, also with the XFCE Desktop. Both of these more or less based on Debian, MX Linux moreso than Mint. I use the terminal when I have to, feel perfectly comfortable with it, but really prefer to just point 'n' click as much as possible.

Now I'm seriously considering making a switch from my current Linux over to the upcoming PINEBOOK Pro. My concern of course being whether or not such a switch is even possible since I'm a hobby photographer who uses Gimp almost daily (with reduced image sizes below 2000 px width per image), as well as LibreOffice / OpenOffice (since 2003), Komodo Edit (not IDE) for Webpage stuff, and Thunderbird for all of my email accounts (for the past 15 years or so). There's a ton of other software that I utilize as well, but nothing that I couldn't easily switch away from. The ones that I just listed are really important to me. I'm not a gamer, could care less about all of the gaming junk, but I am seriously hooked on the XFCE desktop environment (Mate is alright too, but I prefer XFCE).

So if I were to get a PINEBOOK Pro, how difficult would it be for me to continue using those mentioned items that I really don't want to do without (Gimp, LibreOffice, Komodo Edit, Thunderbird, XFCE Desktop) ??? Are these already available within the ARM architecture? Is it difficult or even possible to port current Linux apps such as the ones mentioned, over to a PINEBOOK Pro Linux Laptop?
Do ARM based versions of Linux also have Software/Package managers with click to install apps?
Is it possible to utilize 2TB external drives on the PINEBOOK Pro USB ports?
I would sincerely appreciate some helpful input on these questions. Thank you, everyone.

.]]>

Switching from Winblows after 18 years to Linux in 2009, I've been utilizing primarily Linux Mint with the XFCE Desktop as well as MX Linux, also with the XFCE Desktop. Both of these more or less based on Debian, MX Linux moreso than Mint. I use the terminal when I have to, feel perfectly comfortable with it, but really prefer to just point 'n' click as much as possible.

Now I'm seriously considering making a switch from my current Linux over to the upcoming PINEBOOK Pro. My concern of course being whether or not such a switch is even possible since I'm a hobby photographer who uses Gimp almost daily (with reduced image sizes below 2000 px width per image), as well as LibreOffice / OpenOffice (since 2003), Komodo Edit (not IDE) for Webpage stuff, and Thunderbird for all of my email accounts (for the past 15 years or so). There's a ton of other software that I utilize as well, but nothing that I couldn't easily switch away from. The ones that I just listed are really important to me. I'm not a gamer, could care less about all of the gaming junk, but I am seriously hooked on the XFCE desktop environment (Mate is alright too, but I prefer XFCE).

So if I were to get a PINEBOOK Pro, how difficult would it be for me to continue using those mentioned items that I really don't want to do without (Gimp, LibreOffice, Komodo Edit, Thunderbird, XFCE Desktop) ??? Are these already available within the ARM architecture? Is it difficult or even possible to port current Linux apps such as the ones mentioned, over to a PINEBOOK Pro Linux Laptop?
Do ARM based versions of Linux also have Software/Package managers with click to install apps?
Is it possible to utilize 2TB external drives on the PINEBOOK Pro USB ports?
I would sincerely appreciate some helpful input on these questions. Thank you, everyone.

.]]> <![CDATA[Installing DietPi to EMMC on Rock64]]> https://forum.pine64.org/showthread.php?tid=7542 Thu, 30 May 2019 04:13:52 +0000 rrosenheim]]> https://forum.pine64.org/showthread.php?tid=7542
(For the record, I'm not a Linux guru so just looking for some guidance.)

Thanks.]]>
(For the record, I'm not a Linux guru so just looking for some guidance.)

Thanks.]]> <![CDATA[Installing Debian with the Debian Installer (Buster RC1)]]> https://forum.pine64.org/showthread.php?tid=7455 Sat, 04 May 2019 18:05:44 +0000 amp]]> https://forum.pine64.org/showthread.php?tid=7455
I successfully installed Debian Buster using the official Debian Installer (Buster RC 1).

See the page in the Debian wiki for a general description of the process. I can add more details if needed.

Have fun Big Grin

Big Grin

]]>
I successfully installed Debian Buster using the official Debian Installer (Buster RC 1).

See the page in the Debian wiki for a general description of the process. I can add more details if needed.

Have fun Big Grin

Big Grin

]]> <![CDATA[Debian 10 (Buster) in deep freeze - includes support for Pine64+]]> https://forum.pine64.org/showthread.php?tid=7443 Wed, 01 May 2019 08:34:59 +0000 amp]]> https://forum.pine64.org/showthread.php?tid=7443
For those not following Debian development Buster (Debian 10) is now in deep freeze and will most likely be released in the following months.

I have been running it on a Pine64+ for the past months and it's quite usable for me.

Works for me:

HDMI video output at 1920x1080 (tested console only, most likely framebuffer)
USB (both ports)
Ethernet at GBit speeds
Watchdog (i.e. the logs show it is being enabled)

Problems encountered so far:

slightly unstable, apparently more so when (lots) of USB stuff connected to it
occasional clock jumps to the future (95 years?)

As this is mostly a headless system (I'm using the HDMI output only occasionally for debugging) I did not test other features.

Have fun with Buster Big Grin

Big Grin

]]>
For those not following Debian development Buster (Debian 10) is now in deep freeze and will most likely be released in the following months.

I have been running it on a Pine64+ for the past months and it's quite usable for me.

Works for me:

HDMI video output at 1920x1080 (tested console only, most likely framebuffer)
USB (both ports)
Ethernet at GBit speeds
Watchdog (i.e. the logs show it is being enabled)

Problems encountered so far:

slightly unstable, apparently more so when (lots) of USB stuff connected to it
occasional clock jumps to the future (95 years?)

As this is mostly a headless system (I'm using the HDMI output only occasionally for debugging) I did not test other features.

Have fun with Buster Big Grin

Big Grin

]]> <![CDATA[Script to build pure Debian images for Pine64+]]> https://forum.pine64.org/showthread.php?tid=7442 Wed, 01 May 2019 08:18:57 +0000 amp]]> https://forum.pine64.org/showthread.php?tid=7442
As a Debian purist I wrote a small script to build a Debian image for my Pine64+ with absolutely minimal (and optional) customization.

https://salsa.debian.org/amp-guest/pine6...buildimage

In order to use the script you should read it first, but this is a good idea anyway with random scripts from the internet that must be run as root. In any case, if running it will join your pine64 to a botnet, destroy your data and/or hardware, set your house on fire, etc. I will not assume any responsibility. Use at your own risk!

At the moment I have no intention to publish any images as I believe one should build it's own (hence the motivation to write this script).

It's been a while since I used the script, but I think I was able to use a Stretch image (most likely the mainline Stretch image created by CallMeFoxie https://forum.pine64.org/showthread.php?tid=4931) to build a usable pure Debian Buster image, which I have been using since.

In case you are not following Debian development, Buster is now in deep freeze, which means it's quite close to the final version that will be released sometime in the following months.

I'm sure the script can be improved in various ways, including due to my modest scripting skills. Patches or Merge Requests on Debian's Salsa are welcome, provided they preserve the spirit: pure Debian with minimal (and preferably optional) customization.

Enjoy Big Grin

Big Grin

]]>
As a Debian purist I wrote a small script to build a Debian image for my Pine64+ with absolutely minimal (and optional) customization.

https://salsa.debian.org/amp-guest/pine6...buildimage

In order to use the script you should read it first, but this is a good idea anyway with random scripts from the internet that must be run as root. In any case, if running it will join your pine64 to a botnet, destroy your data and/or hardware, set your house on fire, etc. I will not assume any responsibility. Use at your own risk!

At the moment I have no intention to publish any images as I believe one should build it's own (hence the motivation to write this script).

It's been a while since I used the script, but I think I was able to use a Stretch image (most likely the mainline Stretch image created by CallMeFoxie https://forum.pine64.org/showthread.php?tid=4931) to build a usable pure Debian Buster image, which I have been using since.

In case you are not following Debian development, Buster is now in deep freeze, which means it's quite close to the final version that will be released sometime in the following months.

I'm sure the script can be improved in various ways, including due to my modest scripting skills. Patches or Merge Requests on Debian's Salsa are welcome, provided they preserve the spirit: pure Debian with minimal (and preferably optional) customization.

Enjoy Big Grin

Big Grin

]]> <![CDATA[Debian (Stretch) for Pine64-LTS]]> https://forum.pine64.org/showthread.php?tid=7322 Fri, 29 Mar 2019 11:15:15 +0000 wgray]]> https://forum.pine64.org/showthread.php?tid=7322
When will the Debian (Stretch) release be available for the Pine64-LTS?]]>
When will the Debian (Stretch) release be available for the Pine64-LTS?]]> <![CDATA[insmod ko: Invalid module format]]> https://forum.pine64.org/showthread.php?tid=7303 Mon, 25 Mar 2019 19:00:06 +0000 zener]]> https://forum.pine64.org/showthread.php?tid=7303

Code:
/etc/debian_version 

buster/sid

root@rockpro64:/tmp# uname -a

Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

However if I insmod a kernel module which have just been compiled using /usr/src/linux-headers-4.4.132-1075-rockchip-ayufan-ga83beded8524 I get:

Code:
insmod: ERROR: could not insert module xtrx_linux_pcie_drv/xtrx.ko: Invalid module format

root@rockpro64:/tmp# dmesg | tail -1

[98715.709490] xtrx: version magic '4.4.132 SMP mod_unload aarch64' should be '4.4.132-1075-rockchip-ayufan-ga83beded8524 SMP mod_unload aarch64'

How can I resolve this inconsistency?]]>

Code:
/etc/debian_version 

buster/sid

root@rockpro64:/tmp# uname -a

Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

However if I insmod a kernel module which have just been compiled using /usr/src/linux-headers-4.4.132-1075-rockchip-ayufan-ga83beded8524 I get:

Code:
insmod: ERROR: could not insert module xtrx_linux_pcie_drv/xtrx.ko: Invalid module format

root@rockpro64:/tmp# dmesg | tail -1

[98715.709490] xtrx: version magic '4.4.132 SMP mod_unload aarch64' should be '4.4.132-1075-rockchip-ayufan-ga83beded8524 SMP mod_unload aarch64'

How can I resolve this inconsistency?]]> <![CDATA[A64+ vs. A64-LTS - Build boots?]]> https://forum.pine64.org/showthread.php?tid=6491 Sun, 02 Sep 2018 13:47:52 +0000 Baldnerd]]> https://forum.pine64.org/showthread.php?tid=6491 I accidentally booted my A64-LTS with the A64+ Debian image, and it booted fine and everything seemed to work. From reading, I had thought the SOPine build was completely different than the A64+ and would not be interchangeable, yet this doesn't appear to be the case.

Could you kindly explain to me the actual difference? Like, is there a risk involved in interchanging the SD card between A64+ and the A64-LTS?

I'm actually a bit surprised/confused as I thought it would not boot if I installed the wrong platform's OS on the wrong board.

Thanks for helping clarify my brain! Tongue

Tongue

Robbie]]> I accidentally booted my A64-LTS with the A64+ Debian image, and it booted fine and everything seemed to work. From reading, I had thought the SOPine build was completely different than the A64+ and would not be interchangeable, yet this doesn't appear to be the case.

Could you kindly explain to me the actual difference? Like, is there a risk involved in interchanging the SD card between A64+ and the A64-LTS?

I'm actually a bit surprised/confused as I thought it would not boot if I installed the wrong platform's OS on the wrong board.

Thanks for helping clarify my brain! Tongue

Tongue

Robbie]]> <![CDATA[gphoto2 error]]> https://forum.pine64.org/showthread.php?tid=6127 Fri, 01 Jun 2018 11:13:21 +0000 BostonBay]]> https://forum.pine64.org/showthread.php?tid=6127
I have Debian installed on my A64, trimmed down to be headless. It only offers SSH connections with only TTY & SSH access.

It works fine but gphoto2 throws an error when attempting to access my Canon EOS 350d.

gphoto2 --auto-detect re4cognises it:

ken@floki:~$ gphoto2 --auto-detect
Model Port
----------------------------------------------------------
Canon EOS 350D usb:002,003

gphoto2 -L or gphoto2 -l returns an error:

*** Error ***
An error occurred in the io-library ('I/O problem'): No error description available
*** Error (-7: 'I/O problem') ***

I also specified a port using --port and tried --summary. Received the same error.

Last year on a Debian build and AMD X64 machine it worked fine. My Win 10 machine sees the camera just fine. Does anyone have any guidance?

Thanks!

-Ken
KC7RAD

Quick follow-up.

I found a post somewhere that indicates in some cases, in order to run gphoto2, the user must be running with root privileges. So, I ran gphoto2 using sudo and it works mostly. When I say 'mostly', I mean that after entering SHELL mode, then exiting, I receive similar errors from my original post. Resetting the camera clears the error.

So, basically my solution to the problem I asked about is to run gphoto2 using sudo.]]>
I have Debian installed on my A64, trimmed down to be headless. It only offers SSH connections with only TTY & SSH access.

It works fine but gphoto2 throws an error when attempting to access my Canon EOS 350d.

gphoto2 --auto-detect re4cognises it:

ken@floki:~$ gphoto2 --auto-detect
Model Port
----------------------------------------------------------
Canon EOS 350D usb:002,003

gphoto2 -L or gphoto2 -l returns an error:

*** Error ***
An error occurred in the io-library ('I/O problem'): No error description available
*** Error (-7: 'I/O problem') ***

I also specified a port using --port and tried --summary. Received the same error.

Last year on a Debian build and AMD X64 machine it worked fine. My Win 10 machine sees the camera just fine. Does anyone have any guidance?

Thanks!

-Ken
KC7RAD

Quick follow-up.

I found a post somewhere that indicates in some cases, in order to run gphoto2, the user must be running with root privileges. So, I ran gphoto2 using sudo and it works mostly. When I say 'mostly', I mean that after entering SHELL mode, then exiting, I receive similar errors from my original post. Resetting the camera clears the error.

So, basically my solution to the problem I asked about is to run gphoto2 using sudo.]]> <![CDATA[how to set kernel parameter 'fsck.mode=force']]> https://forum.pine64.org/showthread.php?tid=6039 Wed, 09 May 2018 08:57:53 +0000 marcelser]]> https://forum.pine64.org/showthread.php?tid=6039
I spent now several hours trying to find out by googling and search in this forum how to set the kernel parameter "fsck.mode=force" on the Pine A64. I tried to understand the boot process from the sunxi documentation but to be honest, the boot process of the pine a64 is like rocket science to me with all this parts like u-boot, initrd, kernel, etc.

I finally tried setting it in uEnv.txt but when I look at /proc/cmdline it's not applied. The system I'm running is debian with version "stretch/sid" and kernel image is "3.10.105-0-pine64-longsleep"

Can anyone in simple words explain me how to do this. I cannot be that hard, but it seems it's very hard to find instructions for this seemingly simple task.

Thanks to anyone who could she a light on this.

PS: Why is it so complicated on the PineA64 when on Raspberry I can just modify cmdline.txt and I'm done?]]>
I spent now several hours trying to find out by googling and search in this forum how to set the kernel parameter "fsck.mode=force" on the Pine A64. I tried to understand the boot process from the sunxi documentation but to be honest, the boot process of the pine a64 is like rocket science to me with all this parts like u-boot, initrd, kernel, etc.

I finally tried setting it in uEnv.txt but when I look at /proc/cmdline it's not applied. The system I'm running is debian with version "stretch/sid" and kernel image is "3.10.105-0-pine64-longsleep"

Can anyone in simple words explain me how to do this. I cannot be that hard, but it seems it's very hard to find instructions for this seemingly simple task.

Thanks to anyone who could she a light on this.

PS: Why is it so complicated on the PineA64 when on Raspberry I can just modify cmdline.txt and I'm done?]]> <![CDATA[Is there just one fuctioning Debian Desktop image?]]> https://forum.pine64.org/showthread.php?tid=5894 Mon, 26 Mar 2018 01:16:14 +0000 KNERD]]> https://forum.pine64.org/showthread.php?tid=5894
Armbian ( https://dl.armbian.com/pine64/) : just loads up to a certain point then starts just spewing "Call trace:" Even their Ubuntu image won't boot (Kernel panic).

The Ayunfan current image ( https://github.com/ayufan-pine64/linux-b...tag/0.7.19 ) boots, but requires additional files from an repo to install a desktop which is no longer available.

Older versions seem to get that Kernel Panic also.

The only one I can get up and running, is the one listed on the Wiki, but is not stable at all.

http://wiki.pine64.org/index.php/Pine_A6...essie_Mate

Another other suggestions?]]>
Armbian ( https://dl.armbian.com/pine64/) : just loads up to a certain point then starts just spewing "Call trace:" Even their Ubuntu image won't boot (Kernel panic).

The Ayunfan current image ( https://github.com/ayufan-pine64/linux-b...tag/0.7.19 ) boots, but requires additional files from an repo to install a desktop which is no longer available.

Older versions seem to get that Kernel Panic also.

The only one I can get up and running, is the one listed on the Wiki, but is not stable at all.

http://wiki.pine64.org/index.php/Pine_A6...essie_Mate

Another other suggestions?]]>