Articles Hierarchy

Articles Home » RPI » RPI4 4GB unboxing

RPI4 4GB unboxing

intro
RPI 4 setup
Raspbian Linux terminal
RPI4 USB boot
ubuntu server 64bit for RPI4
RaspiOS 64bit for RPI3 &RPI4
RASPIAN is now RaspiOS


intro


we might just come from my C tutorial ( or not )

RPI 4 setup


I GOT IT
just now i get the delivery of a RPI4 / 4GB / with PS, HDMI cable, box with fan for 2829THB / 80Euro
using internet-shopping "shopee" / shop "Terminus" / transport "Kerry" / cash on delivery /

because of the increased power needed and change of power and HDMI plugs
i for first time buy a complete set..

not bad talking, just some notes:
- - there is no info how & where to install the fan ( but lots of internet resources available )
- - after see some test info that the small tape glued aluminum coolers did not effectively change temperature of cpu.. i did not use them.
- - on one monitor i see a HDMI screen blue blinking ( like initializing ), and a "desktop not available" msg. in VNC,
but installation at a other TV worked, so i question that monitor identification?
also later when i start the RPI ( but did not start the TV HDMI port first ) i get some bad default resolution on VNC,
so like i anyhow did old times, use
sudo raspi-config
and set a default resolution.
- - when insert the uSD card but not hit the slot it falls under the board, so need reopen the box to find it again.
for removal of a correct fitted card must use a pincette.
- - the box is ?heavy steel? but WIFI seems to work, no rubber dot legs provided
with the poor FAN the housing vibrates and all is high pitch noisy,
after my wife complain i disconnect the FAN and see 70 degC so must power it up again.
- - the board power and activity LEDs are not visible


RPI setup
this might be not the most logical place, but somehow a basic Raspberry Pi setup info is needed,
why not repeat it here.

needed hardware:
-1- Raspberry Pi ( here now use newest RPI4 4GB rev 1.2 )
-2- Power Supply ( here 15W , 5.1V , 3 A with USB C connector )
-3- uSD card ( 16GB sanDisk Ultra A1 )
optional:
-4- box with fan ( but i actually use RPIs on my desk without box for many years. )
-5- HDMI cable to Monitor / TV ( here now Mini HDMI port for RPI 4 )
-6- USB keyboard & mouse

needed OS
i only use default Raspbian ( because it is best supported / but there are many reasons why you might use other systems like for media server .. )
also for this are many options:
* NOOBS or Raspbian default
* desktop full or slim // or NON desktop ( only terminal ) ( called light )
i select the desktop slim version and download as ZIP 2020-02-13-raspbian-buster.zip filesize 1.1GB release-notes
( while, if you can use torrent, it will be a much faster download)

format / test uSD card
you not need but can first check the card from win PC with
SD Formatter

burn uSD
install on win PC Etcher and burn the ( not need to UNZIP ) image to a uSD card
using a external card reader ( with USB port )

or laptop build in SD slot ( and a uSD SD Adapter )

here i recommend to unmount & plug in the card again,
until you see the cards burned first partition
on this create a file ( can be empty ) called ssh
* this will allow you after first boot to connect remotely via terminal
for this can install ssh client on win 10, and provided you are able to find the RPI network IP from router
( must use a ethernet cable ).
later, after setup might use WIFI only.

the step about using ethernet cable from router can be avoided if you add to the ssh file copy a
wpa_supplicant.conf setup file to the "boot" partition prior to first boot,
so you are WIFI online with a RPI, new uSD card setup and power-cord only.

i worked many years RPI only remote ( incl setup... )
for a beginner the original desktop usage ( TV & keyboard & mouse ) is more easy to setup.

later you can use the terminal ( via remote ssh or desktop )
to also enable remote desktop with RPI pre-installed VNC server
sudo raspi-config
and VNC client/viewer installed on win PC
instead of remote SSH terminal only.

as i for this ?tutorial? did anyway a new card setup again run into the VNC resolution problem
but some old friends at the forum solved it long ago..
RPI forum
sudo nano /boot/config.txt
change to
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
max_framebuffers=2



Raspbian Linux terminal


in linux the terminal is not so much a historic relikt like the windows cmd window
and many RPI users ( are older? ) even not use desktop at all,
for the young generation windows game specialists unthinkable.
but it should not be a "one or the other"
if you work remote or local desktop or Raspian LITE ( no desktop)
you can work from the terminal ( desktop: LXTerminal app)
use help , info or man ...
the basic command you might need to checkout / learn first:
cd
ls
df

after you learn some commands and the possible switches ( parameters )
you can fight your "alzheimer" using the alias command,
and create your own working environment.



how to make linux remember your alias settings and adapt the user pi terminal start?
make a file
nano /home/pi/.bash_aliases
like this



with all this new hardware RPI4..
i see the need to update my raspi-info
( you might be used the use the '.sh' for batch file names, can do, but not need to: )

nano raspi-info
chmod +x raspi-info
./raspi-info -v




RPI4 USB boot


i want BLOG some more tests about RPI4 here
i found a old USB3 8GB stick / needed to reformat it USB3FAT32
and wanted to play RPI USB3 port
following here
do a
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash
but it only tested my "system" uSD card ( sanDisk Ultra A1 32GB )
and i not see the USB stick tested?


now the main article
is very interesting about connecting "drives" to USB3 of RPI4

and shows a way to use a uSD installation modified to look for the USB connected drive for boot.
++ here means both contain a full system burned to both,
+ change the SSD’s PARTUUID
+ on uSD /boot/cmdline.txt change to use that new SSD’s PARTUUID to boot from
+ SSD's /etc/fstab also needs new PARTUUID
+ Resizing Filesystem /dev/sda2

( this is needed as long there is no real USB boot working for RPI4
sure with RPI3 there was a easier trick to boot from USB via minimal uSD ?one file?
but possibly that trick also not work for RPI4? )

sorry, above procedure about the change of PARTUUID of the system-partition of the USB drive looks backwards for me, and leaves still 2 partitions /boot with same PARTUUID??

esp. when you think about how to work with a newly burned stick next time... so i want experiment with that little bit, using that above old 8GB USB3 stick ( kingston datatraveler )
-a- burn 2020-02-13-raspbian-buster.zip ( with ETCHER from a win10 PC )
( usually i would now do the SSH and wpa_supplicant.conf file trick for remote operation, but here not needed )

-b- sidestep, not relevant for RPI4, test if my RPI3B+ can boot that USB drive
ok worked

-c-
++ now burn again
+++ and do the file trick too ( even that is the boot partition of the USB stick what never will be used! )
+++ format a ( very old 2GB ) uSD card as fat32
+++ copy content of boot partition from USB stick to uSD

so i got the 4 color screen and the 4 raspberries and many auto restart
until a final kernal panic "/usr/lib/raspi-config/init_resize.sh failed"


shows ? only the first step of the resize of the correct system partition worked

how i get that picture?
-a- boot a RPI from SD card
-b- put in the USB stick
-c- run the add. installed GParted and look on the stick
-d- snap screensection via windows VNC



now i burn ( again ) the USB stick and a uSD card same ( using etcher win PC )
-a- boot RPI3 with other USBstick
-b- put in new USB stick remove fat32 partition boot
-c- put in new SD card remove ext4 partition
so boot from SD points to USB stick partition later for using with RPI4?
-d- try both in new RPI4 ( with no double PARTUUID expect less problem )

that worked very well,
but the file system expansion ( at first boot (say [ok] ) ) or later try via 'sudo raspi-config' is disabled.

so for this i now follow that manual:
pi@RPI4:~ $ sudo fdisk /dev/sda

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): d
Selected partition 2
Partition 2 has been deleted.

Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-15356159, default 2048): 532480
Last sector, +/-sectors or +/-size{K,M,G,T,P} (532480-15356159, default 15356159):

Created a new partition 1 of type 'Linux' and of size 7.1 GiB.
Partition #1 contains a ext4 signature.

Do you want to remove the signature? [Y]es/[N]o: N

Command (m for help): w

The partition table has been altered.
Failed to remove partition 2 from system: Device or resource busy
Failed to add partition 1 to system: Device or resource busy

The kernel still uses the old partitions. The new table will be used at the next reboot.
Syncing disks.

pi@RPI4:~ $ sudo reboot

at boot get the 4 color squares and the 4 raspberries
that's it.
so burn the USB stick again


now i used the new burned USB stick and setup in a RPI3
( where filessytem expansion works nice.. )
and then put it in the RPI4 ( with the last used SD card ( already setup boot partition only ))
boot USB stick works nice ( even now have same boot partition on SD and USB )
BUT
WIFI not work
( a recheck with the old good SD card shows hardware ok )
comparing the working wpa_supplicant.conf file with the not working of the USB-stick
( what worked also in RPI3 )
shows no difference. ok did it all again and had the same result, so one of my setup steps works for RPI3 BUT run it later on RPI4 results in WIFI disable / not associated / and even i do all that manually again not get connection.
FOUND IT
my edit for fix IP of the
sudo nano /etc/dhcpcd.conf
causes the RPI4 to disable connection
?even in a way that it not work again when i try back in RPI3 !!!
disable that lines and all could be connected again,
try the menu way of edit wlan to fix IP resulted into the same problems...
ANYHOW now i have a USB stick what works in RPI3 AND RPI4 ( even PARTUUID ... of boot double can not be used like this)
pi@RPIusb:~ $ blkid
/dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="6341-C9E5" TYPE="vfat" PARTUUID="ea7d04d6-01"
/dev/sda1: LABEL_FATBOOT="boot" LABEL="boot" UUID="6341-C9E5" TYPE="vfat" PARTUUID="ea7d04d6-01"
/dev/sda2: LABEL="rootfs" UUID="80571af6-21c9-48a0-9df5-cffb60cf79af" TYPE="ext4" PARTUUID="ea7d04d6-02"
pi@RPIusb:~ $

so as a last test with this i deleted the /boot of the USB stick to avoid that conflict
but still have the fixIP problem ( and the resolution problem and compared to SD card system very slow... ) with this setup


well, i am not at the end of what i can try:
burn SD card again and setup RPI4
( full update and usual settings ( but not the dhcpcd.conf for fixIP ))

now use
menu / accessories / SD card copier
from SD to (cleaned) USB stick
it should be fast and do most of the manual work from the above linked instructions already
only add need to change the link from SD card /boot/cmdline.txt to new PARTUUID of USB /root

sudo cp /boot/cmdline.txt /boot/cmdline.txt.bak
sudo nano /boot/cmdline.txt

and it booted from USB stick, but again
- - mounts USB boot as boot instead SD boot
- - the HDMI is resetting / flickering even on the prior good TV ( VNC works )







also when i moved the USB stick back to a RPI3 it boots without internet WIFI connection

forget it
just see: here


ubuntu server 64bit for RPI4


see first
download the image from here
ubuntu-20.04-preinstalled-server-arm64+raspi.img.xz
burn with etcher to SD card
boot and login
ubuntu
ubuntu
( and create new password)

later on that page they talk about installing a desktop too
xubuntu (Xfce)
lubuntu (LXDE)
kubuntu (KDE)
but wouldn't i need a update first, or even a internet connection?
with ethernet connected
install MC
also try external ( mobile FING ) find IP and
login ssh ( remote from PC / Terminal and SFTP )
ubuntu newpassword



now try to install the LXDE desktop too
sudo apt-get install lubuntu-desktop
over an hour downloading...
select GDM3 ??
( some info )
root ( second partition ) used 2.4GB now 5.8GB so for my 8GB uSD < 1GB free!
ok reboot:
login window and get a very empty desktop / with app list 3 pages long... /
no, not like that look too much, also the window (x) but other size option via menu only
browser firefox work, but
NO SOUND out of my HDMI TV
but instead dig into linux/ubuntu i just install
audacity
and sound works fine now.


for the performance i feel RPI4 is slower as with the RASPBIAN ( 32bit )
( but that was just first impression / actually it was expected that 64bit linux is faster.. )
and i will not choose lubuntu again...


RaspiOS 64bit for RPI3 &RPI4



RaspiOS 64bit ( RPI3 and RPI4 only ) is in work too.
2020-05-27-raspios-buster-arm64.zip
i download this beta ( 1GB )
install ok, run with RPI4,
VNC server not connect.


RASPIAN is now RaspiOS



see blog

here we can download the new raspberry pi setup:
-1- desktop full
-2- desktop ( i call slim )
-3- lite pure linux for the terminal lovers

my working style:
-a- use a old win7 PC running vuze torrent
and download all 3 in a few minutes ( here up to 3MB/s )
-b- burn (etcher) the slim version to a 8GB USB stick ( here USB 2 with 5MB/s )
and copy ssh and wpa_supplicant.conf files to it
-c- ( USB-) boot in a Raspberry Pi 3 and setup via shh client terminal
( also do from sudo raspi-config the VNC enable )
and nano /etc/dhcpcd.conf for fix ip settings
update and add install like mc gparted gimp audacity and samba server setup
add arduino, processing and
node web server ( prepared autostart but only use manual start)
a good intro also see here
-d- keep that USB stick updated
and when we need a new setup burn it to a uSD card by
SD card copier tool
from the RPI3 desktop menu ( so no SD card reader required, use RPI3 uSD card slot )
-e- boot that SD card ( like in the RPI4 )