I took delivery of a RPi4 today and now have Quirky Xerus 8.1.4 running. Too early to say if there will be problems but first impression is that everything looks OK.
I have used the same trick we used to get alpha4/zap6 to run on RPi2.
It took me three attempts before the system started correctly. I had to take the micro SD card out and do some off-line debugging before I realised which particular stupid mistake I had made this time round. So I am going to do a complete rebuild and see I can get a clean start-up at the first attempt.
Some immediate comments:
I have the 2Gb version of the RPi4 and am pleased to report that QX814 sees (and is using) all the RAM.
The built in 'hardware info' programme reports the BCM2711 processor in the RPi4 at 108 bogoMips. If I remember correctly, the figures for RPi2 and RPi3 were 57 and 76 bogoMips.
For those of you who have not yet read the specifications for the RPi4, the major changes are:
2 USB3 ports and 2 USB2 ports rather than the 4 USB2 ports in the RPi3.
3 amp power supply with USB-C connector.
Two mini-HDMI ports rather and one large HDMI port.
My initial impression (subject to revision) is that QX814 looks quite usable on RPi4 while we keep our fingers crossed for a RPi4 build of EasyOS. Posted from my RPi4.
Quirky Xerus 8.1.4 for Raspberry Pi2 and 3
RPi4
I've built a basic system on the RPi4 and not yet encountered any difficulties (still early days). There might be some glitch with wifi support, but I am currently all ethernet and no wifi so I can't test this.
For anyone who is interested, this is the sequence I followed for porting QX814 to the RPi4:
From Github, download the latest RPI firmware master and unpack it. This provided me with Linux kernel version 4.19.66. The kernel is updated as and when necessary, so the number moves on every once in a while.
Write the Quirly Xerus image on a micro-SD card as per BK's instructions.
Mount the partitions on the card you have written and make some changes.
On the first partition (75Mb) delete everything except the cmdline.txt and the config.txt. Then replace the files you have deleted with the up to date equivalents from the firmware master. Copy the overlays directory and the start-up files to the partition (you don't need the github hash).
On the second partition (6.8Gb) navigate to /boot/part1 and repeat the operation you have just performed.
Navigate to /opt, delete the vc folder and replace it with the up to date version from Github
Navigate to /lib/modules and delete the 4.4.34-v7+ folder and replace it with the 4.19.66-v7l+ folder.
Put the card in the RPi4, power-up and hope for the best.
For anyone who is interested, this is the sequence I followed for porting QX814 to the RPi4:
From Github, download the latest RPI firmware master and unpack it. This provided me with Linux kernel version 4.19.66. The kernel is updated as and when necessary, so the number moves on every once in a while.
Code: Select all
https://github.com/Hexxeh/rpi-firmware/archive/master.zipCode: Select all
http://bkhome.org/news/201612/quirky-814-for-pi2-and-pi3.htmlOn the first partition (75Mb) delete everything except the cmdline.txt and the config.txt. Then replace the files you have deleted with the up to date equivalents from the firmware master. Copy the overlays directory and the start-up files to the partition (you don't need the github hash).
On the second partition (6.8Gb) navigate to /boot/part1 and repeat the operation you have just performed.
Navigate to /opt, delete the vc folder and replace it with the up to date version from Github
Navigate to /lib/modules and delete the 4.4.34-v7+ folder and replace it with the 4.19.66-v7l+ folder.
Put the card in the RPi4, power-up and hope for the best.
I give up
@ amj
Whats the magic to getting firefox working. A year ago I had this quirky running with berryboot and had a go at firefox. I remember that I had to get this GLIBC 2.27 and a dozen of later new libs but I could not get firefox to work. Just had another go at firefox. Found a libc6 deb package and opened it up and was heading to user/lib and noticed an arm-linux-gnueabihf folder in /usr and thought to myself, I didn't put that there yet, I looked inside and it has the same files I just downloaded. I thought @ amj must have put it there so I went to ld.so.config to see it must have been @ amj that installed libc6. Then when I saw the 'couldnt load XPCOM' that where I gave up a year ago.
Whats the magic to getting firefox work.
I got vivaldi to work firstly and wondered why I only needed libnss3 to make it load. @ amj done all the heavy lifting.
Anyone wanting to use vivaldi running as spot can try this courtesy of STEP.
I wrote a small starter script some time ago, and it's been working up to this version. Save the following code to /usr/bin/s-tor-browser or another name of your liking, and make it executable. Run the script to start tor browser. For added security, it runs the browser as user spot. For convenience, I keep the tor browser folder tor-browser_en-US, in /home/spot/Downloads/.
(vivaldi is installed to opt, call the script in usr/ bin simply vivaldi )
log="/tmp/${0##*/}.log"
TBB=vivaldi
exec 2>"${log}"
cd /opt/${TBB}/ &&
chown -R spot.spot .. &&
rm -f ../torbrowser.log &&
if ! exec run-as-spot ./vivaldi -l --detach "$@"; then
[ -f ../torbrowser.log ] && cat ../torbrowser.log >> "${log}"
defaultterm -title "ERROR while starting TorBrowser" -e less "${log}" &
exit 1
fi
echo "see ${log}"
@ amj
Whats the magic to getting firefox working. A year ago I had this quirky running with berryboot and had a go at firefox. I remember that I had to get this GLIBC 2.27 and a dozen of later new libs but I could not get firefox to work. Just had another go at firefox. Found a libc6 deb package and opened it up and was heading to user/lib and noticed an arm-linux-gnueabihf folder in /usr and thought to myself, I didn't put that there yet, I looked inside and it has the same files I just downloaded. I thought @ amj must have put it there so I went to ld.so.config to see it must have been @ amj that installed libc6. Then when I saw the 'couldnt load XPCOM' that where I gave up a year ago.
Whats the magic to getting firefox work.
I got vivaldi to work firstly and wondered why I only needed libnss3 to make it load. @ amj done all the heavy lifting.
Anyone wanting to use vivaldi running as spot can try this courtesy of STEP.
I wrote a small starter script some time ago, and it's been working up to this version. Save the following code to /usr/bin/s-tor-browser or another name of your liking, and make it executable. Run the script to start tor browser. For added security, it runs the browser as user spot. For convenience, I keep the tor browser folder tor-browser_en-US, in /home/spot/Downloads/.
(vivaldi is installed to opt, call the script in usr/ bin simply vivaldi )
log="/tmp/${0##*/}.log"
TBB=vivaldi
exec 2>"${log}"
cd /opt/${TBB}/ &&
chown -R spot.spot .. &&
rm -f ../torbrowser.log &&
if ! exec run-as-spot ./vivaldi -l --detach "$@"; then
[ -f ../torbrowser.log ] && cat ../torbrowser.log >> "${log}"
defaultterm -title "ERROR while starting TorBrowser" -e less "${log}" &
exit 1
fi
echo "see ${log}"