Jump to content

Recommended Posts

Posted

Hi all, i've installed Postgresql on my Nanopi M4 V2 board which is running Buster  Armbian Linux 4.4.192-rk3399 and it appears to have installed ok but it won't start - there's nothing in the logs and running pg_isready returns no response - any ideas guys

Posted

I've no specific postgresql experience but I have found that the way Armbian handles logging to zram can mean that the log files either don't exist or can't be written.

Generally the answer to situations like this is to try running the binary from a command prompt with the 'verbose' switch set, if it then runs OK, try to modify the sysctl files to enable logging.

 

 

Posted
1 hour ago, GeorgeP said:

I've no specific postgresql experience but I have found that the way Armbian handles logging to zram can mean that the log files either don't exist or can't be written.

Generally the answer to situations like this is to try running the binary from a command prompt with the 'verbose' switch set, if it then runs OK, try to modify the sysctl files to enable logging.

 

 

Thanks I'll give it a shot

Posted
4 hours ago, pkfox said:

Thanks I'll give it a shot

I can't even find the binary - also the install usually creates a /etc/postgresql folder which isn't happening - I've tried removing the install and reinstalling but I receive the message that it's already installed ? WTF ?

 

Posted

It looks like there is some problem but it installs perfectly on a clean Armbian Buster armhf / Cubietruck http://ix.io/24wp

 

Spoiler

apt install postgresql-11 postgresql-client-11
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libllvm7 libpq5 libxslt1.1 postgresql-client-common postgresql-common ssl-cert
Suggested packages:
  postgresql-doc-11 libjson-perl openssl-blacklist
The following NEW packages will be installed:
  libllvm7 libpq5 libxslt1.1 postgresql-11 postgresql-client-11 postgresql-client-common postgresql-common ssl-cert
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 26.8 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://security.debian.org buster/updates/main armhf postgresql-client-common all 200+deb10u3 [84.9 kB]
Get:2 http://security.debian.org buster/updates/main armhf postgresql-common all 200+deb10u3 [225 kB] 
Get:3 http://cdn-fastly.deb.debian.org/debian buster/main armhf libllvm7 armhf 1:7.0.1-8 [11.3 MB]
Get:4 http://cdn-fastly.deb.debian.org/debian buster/main armhf libpq5 armhf 11.5-1+deb10u1 [152 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian buster/main armhf libxslt1.1 armhf 1.1.32-2.2~deb10u1 [217 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian buster/main armhf postgresql-client-11 armhf 11.5-1+deb10u1 [1,328 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian buster/main armhf ssl-cert all 1.0.39 [20.8 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian buster/main armhf postgresql-11 armhf 11.5-1+deb10u1 [13.5 MB]
Fetched 26.8 MB in 5s (5,713 kB/s)        
Preconfiguring packages ...
Selecting previously unselected package libllvm7:armhf.
(Reading database ... 33631 files and directories currently installed.)
Preparing to unpack .../0-libllvm7_1%3a7.0.1-8_armhf.deb ...
Unpacking libllvm7:armhf (1:7.0.1-8) ...
Selecting previously unselected package libpq5:armhf.
Preparing to unpack .../1-libpq5_11.5-1+deb10u1_armhf.deb ...
Unpacking libpq5:armhf (11.5-1+deb10u1) ...
Selecting previously unselected package libxslt1.1:armhf.
Preparing to unpack .../2-libxslt1.1_1.1.32-2.2~deb10u1_armhf.deb ...
Unpacking libxslt1.1:armhf (1.1.32-2.2~deb10u1) ...
Selecting previously unselected package postgresql-client-common.
Preparing to unpack .../3-postgresql-client-common_200+deb10u3_all.deb ...
Unpacking postgresql-client-common (200+deb10u3) ...
Selecting previously unselected package postgresql-client-11.
Preparing to unpack .../4-postgresql-client-11_11.5-1+deb10u1_armhf.deb ...
Unpacking postgresql-client-11 (11.5-1+deb10u1) ...
Selecting previously unselected package ssl-cert.
Preparing to unpack .../5-ssl-cert_1.0.39_all.deb ...
Unpacking ssl-cert (1.0.39) ...
Selecting previously unselected package postgresql-common.
Preparing to unpack .../6-postgresql-common_200+deb10u3_all.deb ...
Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common'
Unpacking postgresql-common (200+deb10u3) ...
Selecting previously unselected package postgresql-11.
Preparing to unpack .../7-postgresql-11_11.5-1+deb10u1_armhf.deb ...
Unpacking postgresql-11 (11.5-1+deb10u1) ...
Setting up postgresql-client-common (200+deb10u3) ...
Setting up libpq5:armhf (11.5-1+deb10u1) ...
Setting up ssl-cert (1.0.39) ...
Setting up postgresql-client-11 (11.5-1+deb10u1) ...
update-alternatives: using /usr/share/postgresql/11/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode
Setting up postgresql-common (200+deb10u3) ...
Adding user postgres to group ssl-cert

Creating config file /etc/postgresql-common/createcluster.conf with new version
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service → /lib/systemd/system/postgresql.service.
Setting up libxslt1.1:armhf (1.1.32-2.2~deb10u1) ...
Setting up libllvm7:armhf (1:7.0.1-8) ...
Setting up postgresql-11 (11.5-1+deb10u1) ...
Creating new PostgreSQL cluster 11/main ...
/usr/lib/postgresql/11/bin/initdb -D /var/lib/postgresql/11/main --auth-local peer --auth-host md5
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/11/main ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctlcluster 11 main start

Ver Cluster Port Status Owner    Data directory              Log file
11  main    5432 down   postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log
update-alternatives: using /usr/share/postgresql/11/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Processing triggers for systemd (241-7~deb10u2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
root@cubietruck:~# pg_isready
/var/run/postgresql:5432 - accepting connections
root@cubietruck:~# systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2019-12-15 17:37:47 UTC; 55s ago
 Main PID: 8447 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4560)
   Memory: 0B
   CGroup: /system.slice/postgresql.service

Dec 15 17:37:47 cubietruck systemd[1]: Starting PostgreSQL RDBMS...
Dec 15 17:37:47 cubietruck systemd[1]: Started PostgreSQL RDBMS.
root@cubietruck:~# su - postgres

postgres@cubietruck:~$ psql
psql (11.5 (Debian 11.5-1+deb10u1))
Type "help" for help.

postgres=# 

 

 

Posted
3 hours ago, Igor said:

It looks like there is some problem but it installs perfectly on a clean Armbian Buster armhf / Cubietruck http://ix.io/24wp

 

  Reveal hidden contents


apt install postgresql-11 postgresql-client-11
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libllvm7 libpq5 libxslt1.1 postgresql-client-common postgresql-common ssl-cert
Suggested packages:
  postgresql-doc-11 libjson-perl openssl-blacklist
The following NEW packages will be installed:
  libllvm7 libpq5 libxslt1.1 postgresql-11 postgresql-client-11 postgresql-client-common postgresql-common ssl-cert
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 26.8 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://security.debian.org buster/updates/main armhf postgresql-client-common all 200+deb10u3 [84.9 kB]
Get:2 http://security.debian.org buster/updates/main armhf postgresql-common all 200+deb10u3 [225 kB] 
Get:3 http://cdn-fastly.deb.debian.org/debian buster/main armhf libllvm7 armhf 1:7.0.1-8 [11.3 MB]
Get:4 http://cdn-fastly.deb.debian.org/debian buster/main armhf libpq5 armhf 11.5-1+deb10u1 [152 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian buster/main armhf libxslt1.1 armhf 1.1.32-2.2~deb10u1 [217 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian buster/main armhf postgresql-client-11 armhf 11.5-1+deb10u1 [1,328 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian buster/main armhf ssl-cert all 1.0.39 [20.8 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian buster/main armhf postgresql-11 armhf 11.5-1+deb10u1 [13.5 MB]
Fetched 26.8 MB in 5s (5,713 kB/s)        
Preconfiguring packages ...
Selecting previously unselected package libllvm7:armhf.
(Reading database ... 33631 files and directories currently installed.)
Preparing to unpack .../0-libllvm7_1%3a7.0.1-8_armhf.deb ...
Unpacking libllvm7:armhf (1:7.0.1-8) ...
Selecting previously unselected package libpq5:armhf.
Preparing to unpack .../1-libpq5_11.5-1+deb10u1_armhf.deb ...
Unpacking libpq5:armhf (11.5-1+deb10u1) ...
Selecting previously unselected package libxslt1.1:armhf.
Preparing to unpack .../2-libxslt1.1_1.1.32-2.2~deb10u1_armhf.deb ...
Unpacking libxslt1.1:armhf (1.1.32-2.2~deb10u1) ...
Selecting previously unselected package postgresql-client-common.
Preparing to unpack .../3-postgresql-client-common_200+deb10u3_all.deb ...
Unpacking postgresql-client-common (200+deb10u3) ...
Selecting previously unselected package postgresql-client-11.
Preparing to unpack .../4-postgresql-client-11_11.5-1+deb10u1_armhf.deb ...
Unpacking postgresql-client-11 (11.5-1+deb10u1) ...
Selecting previously unselected package ssl-cert.
Preparing to unpack .../5-ssl-cert_1.0.39_all.deb ...
Unpacking ssl-cert (1.0.39) ...
Selecting previously unselected package postgresql-common.
Preparing to unpack .../6-postgresql-common_200+deb10u3_all.deb ...
Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common'
Unpacking postgresql-common (200+deb10u3) ...
Selecting previously unselected package postgresql-11.
Preparing to unpack .../7-postgresql-11_11.5-1+deb10u1_armhf.deb ...
Unpacking postgresql-11 (11.5-1+deb10u1) ...
Setting up postgresql-client-common (200+deb10u3) ...
Setting up libpq5:armhf (11.5-1+deb10u1) ...
Setting up ssl-cert (1.0.39) ...
Setting up postgresql-client-11 (11.5-1+deb10u1) ...
update-alternatives: using /usr/share/postgresql/11/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode
Setting up postgresql-common (200+deb10u3) ...
Adding user postgres to group ssl-cert

Creating config file /etc/postgresql-common/createcluster.conf with new version
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service → /lib/systemd/system/postgresql.service.
Setting up libxslt1.1:armhf (1.1.32-2.2~deb10u1) ...
Setting up libllvm7:armhf (1:7.0.1-8) ...
Setting up postgresql-11 (11.5-1+deb10u1) ...
Creating new PostgreSQL cluster 11/main ...
/usr/lib/postgresql/11/bin/initdb -D /var/lib/postgresql/11/main --auth-local peer --auth-host md5
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/11/main ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctlcluster 11 main start

Ver Cluster Port Status Owner    Data directory              Log file
11  main    5432 down   postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log
update-alternatives: using /usr/share/postgresql/11/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Processing triggers for systemd (241-7~deb10u2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
root@cubietruck:~# pg_isready
/var/run/postgresql:5432 - accepting connections
root@cubietruck:~# systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2019-12-15 17:37:47 UTC; 55s ago
 Main PID: 8447 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4560)
   Memory: 0B
   CGroup: /system.slice/postgresql.service

Dec 15 17:37:47 cubietruck systemd[1]: Starting PostgreSQL RDBMS...
Dec 15 17:37:47 cubietruck systemd[1]: Started PostgreSQL RDBMS.
root@cubietruck:~# su - postgres

postgres@cubietruck:~$ psql
psql (11.5 (Debian 11.5-1+deb10u1))
Type "help" for help.

postgres=# 

 

OK Igor v weird though ? I have it running perfectly on the M4 V1

 

Posted
8 hours ago, pkfox said:

OK Igor v weird though ? I have it running perfectly on the M4 V1


Need to do more tests to find out where is the source of this trouble. M4 V2 image is still labelled as "testing" - it is expected that you will not use it for real yet - which means this is not a big problem yet. But yes, we have to fix it.

Posted
1 hour ago, Igor said:


Need to do more tests to find out where is the source of this trouble. M4 V2 image is still labelled as "testing" - it is expected that you will not use it for real yet - which means this is not a big problem yet. But yes, we have to fix it.

Oh I'm not using it for real just trying to do something useful with it as I am with the M4 V1 , I only bought the V2 because they seem to have discontinued the V1 4gb model which is a pity as Armbian is rock solid on those.

 

Posted
51 minutes ago, pkfox said:

I only bought the V2 because they seem to have discontinued the V1 4gb model which is a pity as Armbian is rock solid on those.


Understand, but there is little we can do about. We need to adjust software. Perhaps help develop support? Its heavily sponsored from our private time which is currently covered less than 0.5%. We - people that move things forward - are 10 - 50 x too small to fix thing with the speed average user expects ;) You are frustrated since things are not working, we as well since we can't do much about ...

Posted
15 hours ago, Igor said:


Understand, but there is little we can do about. We need to adjust software. Perhaps help develop support? Its heavily sponsored from our private time which is currently covered less than 0.5%. We - people that move things forward - are 10 - 50 x too small to fix thing with the speed average user expects ;) You are frustrated since things are not working, we as well since we can't do much about

I do appreciate what you people do and if I was more knowledgeable I would contribute but I'm quite limited in my knowledge of Linux

 

Posted
5 hours ago, pkfox said:

but I'm quite limited in my knowledge of Linux


That is great. :P You have a lot of opportunities to learn ... and help. When I started with this project, most of activities were either a blur from the past or something totally new. Persistence is the key.

 

There are lots of tasks, where no Linux know-how is needed, but has to be done. Since most people don't even notice, nobody likes to do them ... I have to do it.
 

Posted
9 hours ago, Igor said:


That is great. :P You have a lot of opportunities to learn ... and help. When I started with this project, most of activities were either a blur from the past or something totally new. Persistence is the key.

 

There are lots of tasks, where no Linux know-how is needed, but has to be done. Since most people don't even notice, nobody likes to do them ... I have to do it.
 

Hi Igor, I though I'd start from scratch, so , I flashed the image supplied by @pask , used the wi-fi drivers specified by @martinayotte, and applied the boot loader patch supplied by @pask. All booted fine with wi-fi working , so I attempted to install postgresql. And it worked perfectly, don't know why but I must have screwed something up before - good news is it works, bad news is I don't know why - thanks for your help.

Posted
4 hours ago, pkfox said:

Hi Igor, I though I'd start from scratch, so , I flashed the image supplied by @pask , used the wi-fi drivers specified by @martinayotte, and applied the boot loader patch supplied by @pask. All booted fine with wi-fi working , so I attempted to install postgresql. And it worked perfectly, don't know why but I must have screwed something up before - good news is it works, bad news is I don't know why - thanks for your help.

@pkfox It's time to use WIP images for this board https://www.armbian.com/nanopi-m4-v2/

No need anymore for patchs or other magics.

 

Anyway, my experience is that the 4.4.y images still don't work for me. While the ones with buster 5.4 kernel work, but I'm still struggling to get anything really useful done as I'm still experiencing some unreliable behavior, like sudden freezes when connecting be means of tigervnc.  Perhaps my board is an unlucky sample.

 

Let us know if you experience goes better.

Posted
59 minutes ago, pask said:

@pkfox It's time to use WIP images for this board https://www.armbian.com/nanopi-m4-v2/

No need anymore for patchs or other magics.

 

Anyway, my experience is that the 4.4.y images still don't work for me. While the ones with buster 5.4 kernel work, but I'm still struggling to get anything really useful done as I'm still experiencing some unreliable behavior, like sudden freezes when connecting be means of tigervnc.  Perhaps my board is an unlucky sample.

 

Let us know if you experience goes better.

Hi @pask are you saying I can flash the image you gave a link to and it will boot and wifi will work ? your original images were about 1gb and these are only 300mb ish is this correct ?

 

Posted
20 minutes ago, pkfox said:

Hi @pask are you saying I can flash the image you gave a link to and it will boot and wifi will work ? your original images were about 1gb and these are only 300mb ish is this correct ?

 

I you scroll down the page https://www.armbian.com/nanopi-m4-v2/

you'll find the fat desktop images too.

 

Posted
1 hour ago, pask said:

my experience is that the 4.4.y images still don't work for me

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

I was able to fix wireless with the following addition to the NetworkManager's config file.

 

/etc/NetworkManager/NetworkManager.conf

[device]
wifi.scan-rand-mac-address=no

Wired connection is another beast. As soon as it connects and receives IP address it becomes totally slow, unreliable and starts dropping packets.

I tried to make the Frankenstein image your way (M4 image + rockpi's u-boot) and it behaves the same.

OTOH FriendlyARM's image has stable wired connection and I cannot find the reason why, yet :(

Posted
47 minutes ago, pask said:

I you scroll down the page https://www.armbian.com/nanopi-m4-v2/

you'll find the fat desktop images too.

 

Hey good work @pask - flashed it straight to eMMC and it booted - no WiFi though :-( - I tried copying the broadcom drivers I've been using with your original image but no joy - using armbian-config my network is shown but won't connect ( fails with no reason given ) tried it from cli nmcli but same error message

Posted
48 minutes ago, piter75 said:

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

I was able to fix wireless with the following addition to the NetworkManager's config file.

 

/etc/NetworkManager/NetworkManager.conf


[device]
wifi.scan-rand-mac-address=no

Wired connection is another beast. As soon as it connects and receives IP address it becomes totally slow, unreliable and starts dropping packets.

I tried to make the Frankenstein image your way (M4 image + rockpi's u-boot) and it behaves the same.

OTOH FriendlyARM's image has stable wired connection and I cannot find the reason why, yet :(

Good man WiFi now works - thanks very much - maybe @pask can add those lines to his build - did I need to use the drivers from @pask original build ? or will the ones in the new build work ok

Posted
9 hours ago, piter75 said:

Is it still the issue that as soon as you connect UART it stops working?

 

The other thing that does not work in 4.4.x right now is networking :(

 

 

Hello @piter75

Thank you! Now I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network. 

 

BTW I've not anymore connected my serial dongle to the m4v2, as I've moved the board from my desktop to an "intended production" position, and I'm using it headless and wired connected.

 

The 5.4.2 buster image works quite well in server mode (wired network, usb, and so on). Still troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes of the xfce desktop environment. But the board itself doesn't freeze: indeed, if I close the tigervnc client window once frozen,  when I reconnect to the tigervnc server, I can continue using the desktop, at least until the next freeze.

I suspect It's not a tigervnc specific issue, as I've also tried x2go and experienced a similar behavior.

 

8 hours ago, pkfox said:

Good man WiFi now works - thanks very much - maybe @pask can add those lines to his build - did I need to use the drivers from @pask original build ? or will the ones in the new build work ok

 

 Thank you too @pkfox

Actually who deserves our kudos are the great armbian developers, and among them I can cite @piter75, who has made possible to us the use of the great armbian OS on this board.

 

Posted
2 hours ago, pask said:

 

Hello @piter75

Thank you! Now I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network. 

 

BTW I've not anymore connected my serial dongle to the m4v2, as I've moved the board from my desktop to an "intended production" position, and I'm using it headless and wired connected.

 

The 5.4.2 buster image works quite well in server mode (wired network, usb, and so on). Still troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes of the xfce desktop environment. But the board itself doesn't freeze: indeed, if I close the tigervnc client window once frozen,  when I reconnect to the tigervnc server, I can continue using the desktop, at least until the next freeze.

I suspect It's not a tigervnc specific issue, as I've also tried x2go and experienced a similar behavior.

 

 

 Thank you too @pkfox

Actually who deserves our kudos are the great armbian developers, and among them I can cite @piter75, who has made possible to us the use of the great armbian OS on this board.

 

I've now redone the whole process from scratch thus ( I did this using a Linux box and a USB TTL serial cable)

 

1) Download an image from @pask link

2) Start a terminal

3) cd to the folder containing your download

4) Unzip your download to extract the *.img file

5) Connect an sdcard or eMMC to your pc ( I used a transcend adapter )

6) Run lsblk to identify your device, in my case it returned /dev/sdc

7) Run mount to ensure it is not mounted and unmount it if necessary ( umount /dev/sdc or umount /dev/sdc1 )

8) Run dd if =NameOfYourImage.img of=/dev/sdc status=progress

9) When completed ( it takes a while ) make a directory to enable you to mount your device ( mkdir /mnt/MyDevice)

10) Run mount /dev/sdc1 /mnt/MyDevice

11) nano /mnt/MyDevice/etc/NetworkManager/NetworkManager.conf

12) Add these two lines and save the file

[device]
wifi.scan-rand-mac-address=no

 

13) Unmount the device (umount /mnt/MyDevice)

14) Put the device( sdcard or eMMC ) in the M4 - DO NOT APPLY POWER YET !

15) Connect a serial cable to the UART pins on the board and attach the other end to a USB port on your PC

16) Issue this command picocom -b 1150000 /dev/ttyUSB0 ( I'm typing this at work but I think this is correct ) this should connect you to the M4

16) Apply power to the M4 and you should see the boot output

15) Login as root with password 1234 ( you'll be prompted to change the password )

17) Run armbian-config to configure wifi

18) Ensure you have an ip address ( ip a ) and look for wlan0

19) Reboot the M4 having removed the serial cable first.

 

In my case It all worked - your case may be different.

 

 

 

 

 

 

 

Posted
On 12/18/2019 at 8:50 AM, pask said:

I understand why I'm not able to reach the nanopim4-v2 with a buster/4.4x sd image through the wired network

I hopefully managed to fix networking in legacy kernel. At least it works well on my unit now ;-)

It is merged into master and downloadable images are also recreated.

 

On 12/18/2019 at 8:50 AM, pask said:

troubles when in desktop mode as I have experienced frequent freezes that make it unusable. Even when connected via a tigervnc client to a tigervnc server there are frequent freezes

I am wondering whether it may have something to do with Panfrost gpu driver being not really stable yet.

Maybe VNC is also using gpu to accelerate desktop drawing...

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines