RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 3:20 am

cjan wrote:
Fri Jan 08, 2021 2:47 am
RonR wrote:
Fri Jan 08, 2021 2:18 am
Updating arm64 (both Lite and Desktop) from 5.10.4 to 5.10.5 fails to boot.

It starts, but goes into 4 long flashes followed by 4 short flashes (Unsupported board type).

Very reproducible.
same here.

The problem is in /boot. Restoring only 5.10.4 /boot files allows the Pi to boot normally

cjan
Posts: 915
Joined: Sun May 06, 2012 12:00 am

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 4:52 am

RonR wrote:
Fri Jan 08, 2021 3:20 am
cjan wrote:
Fri Jan 08, 2021 2:47 am
RonR wrote:
Fri Jan 08, 2021 2:18 am
Updating arm64 (both Lite and Desktop) from 5.10.4 to 5.10.5 fails to boot.

It starts, but goes into 4 long flashes followed by 4 short flashes (Unsupported board type).

Very reproducible.
same here.

The problem is in /boot. Restoring only 5.10.4 /boot files allows the Pi to boot normally
which file(s), mainly?

RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 5:02 am

cjan wrote:
Fri Jan 08, 2021 4:52 am
RonR wrote:
Fri Jan 08, 2021 3:20 am
cjan wrote:
Fri Jan 08, 2021 2:47 am
same here.

The problem is in /boot. Restoring only 5.10.4 /boot files allows the Pi to boot normally
which file(s), mainly?

I took the brute force approach:

1. Write 2020-08-20-raspios-buster-arm64-lite.img to a USB flash drive, boot it, and update it (apt update && apt full-upgrade) to 5.10.4.

2. Save /boot/cmdline.txt and /boot/config.txt and delete everything in /boot of 5.10.5.

3. Copy all the /boot files from the USB flash drive (10.5.4) to the empty /boot directory.

4. Copy the original /boot/cmdline.txt and /boot/config.txt back.

User avatar
rpdom
Posts: 18506
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 8:32 am

RonR wrote:
Fri Jan 08, 2021 5:02 am
I took the brute force approach:

1. Write 2020-08-20-raspios-buster-arm64-lite.img to a USB flash drive, boot it, and update it (apt update && apt full-upgrade) to 5.10.4.

2. Save /boot/cmdline.txt and /boot/config.txt and delete everything in /boot of 5.10.5.

3. Copy all the /boot files from the USB flash drive (10.5.4) to the empty /boot directory.

4. Copy the original /boot/cmdline.txt and /boot/config.txt back.
A better test would be to see if it was the kernel*.img files indicating a kernel issue, or the *.dat, *.bin and *.elf files indicating a bootloader/firmware issue that need reverting for a successful boot.

I only have a Pi 3B available for testing. My 4B has gone live with applications now.
Unreadable squiggle

User avatar
davidcoton
Posts: 6112
Joined: Mon Sep 01, 2014 2:37 pm
Location: Cambridge, UK
Contact: Website

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 11:00 am

cjan wrote:
Fri Jan 08, 2021 2:47 am
RonR wrote:
Fri Jan 08, 2021 2:18 am
Updating arm64 (both Lite and Desktop) from 5.10.4 to 5.10.5 fails to boot.

It starts, but goes into 4 long flashes followed by 4 short flashes (Unsupported board type).

Very reproducible.
same here.
Me too. Seems to put in some weird config, a re-written SDCard didn't work either -- somewhere the card got damaged?
Similar to other forum reports, only I know the card was not abused, just updated, rebooted (failed), and re-flash attempted using RPi-imager

Hand transcript:

Code: Select all

[12. ... ] sdhci-iproc fe340000.emmc2: card stuck in wrong state! card-busy_detect status: 0xfe00
>repeats three more times<
[ ... ]      mmcblk0: recory failed
[ ... ]      blk_update_request: I/O error dev mmcblk0 sector 0 op0x1(WRITE) flags 0x8000 phys_seg 1 prio class 0
[ ... ]      Buffer I/O error on devmmcblk0 logical block 0, lost async page write
Error: input/output error during write on/dev/mmcblk0
Retry/Ignore/Continue ?
Location: 345th cell on the right of the 210th row of L2 cache

RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Fri Jan 08, 2021 9:37 pm

apt update && apt full-upgrade now gets:

Code: Select all

Linux raspberrypi 5.10.5-v8+ #1391 SMP PREEMPT Thu Jan 7 17:55:54 GMT 2021 aarch64

which appears to boot and run properly.

test12395
Posts: 3
Joined: Tue Jun 16, 2020 4:24 pm

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Mon Jan 11, 2021 7:39 pm

having same issue with 4 long flashes followed by 4 short flashes

today i installed raspbian 64 on a new 4B 8GB board then done a apt-get update and apt-get upgrade
restarted and done a rpi-update and the board wouldn't boot after reboot.

RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Mon Jan 11, 2021 7:50 pm

test12395 wrote:
Mon Jan 11, 2021 7:39 pm
having same issue with 4 long flashes followed by 4 short flashes

today i installed raspbian 64 on a new 4B 8GB board then done a apt-get update and apt-get upgrade
restarted and done a rpi-update and the board wouldn't boot after reboot.

Weren't you at 5.10.5 without the rpi-update?

Now that 5.10 has arrived in the normal 64-bit repositories (via apt), I think it's time to revert to being extremely cautious about using rpi-update.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5745
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Mon Jan 11, 2021 7:51 pm

test12395 wrote:
Mon Jan 11, 2021 7:39 pm
today i installed raspbian 64 on a new 4B 8GB board then done a apt-get update and apt-get upgrade
restarted and done a rpi-update and the board wouldn't boot after reboot.
Do you see the bootloader diagnostic screen? Do you get the same flashing pattern with sdcard removed?
Can you read the sdcard FAT directory in another PC?

RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Mon Jan 11, 2021 8:06 pm

dom wrote:
Mon Jan 11, 2021 7:51 pm
Do you see the bootloader diagnostic screen? Do you get the same flashing pattern with sdcard removed?

Everything is normal except for halting with a flashing pattern (4L/4S) after start.elf loads:

Code: Select all

Read start.elf bytes  2941216 hnd 0x0005a003 sha256 a94a864fc9d9ee38
Read fixup.dat bytes     7299 hnd 0x0005fd44 sha256 bc6d187637facf3d
0x00c03111 0x00000000 0x0000003f
MEM GPU: 32 ARM: 991 TOTAL: 1023
Starting start.elf @ 0xfeb00200 partition 0
+
dom wrote:
Mon Jan 11, 2021 7:51 pm
Can you read the sdcard FAT directory in another PC?

Code: Select all

-rwxr-xr-x 1 root root   25195 Jan 11 13:56 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root   25458 Jan 11 13:56 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root   24806 Jan 11 13:56 bcm2708-rpi-b-rev1.dtb
-rwxr-xr-x 1 root root   24928 Jan 11 13:56 bcm2708-rpi-cm.dtb
-rwxr-xr-x 1 root root   24940 Jan 11 13:56 bcm2708-rpi-zero.dtb
-rwxr-xr-x 1 root root   26133 Jan 11 13:56 bcm2708-rpi-zero-w.dtb
-rwxr-xr-x 1 root root   26333 Jan 11 13:56 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root   26482 Jan 11 13:56 bcm2710-rpi-2-b.dtb
-rwxr-xr-x 1 root root   27980 Jan 11 13:56 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root   28599 Jan 11 13:56 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root   26289 Jan 11 13:56 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root   48145 Jan 11 13:56 bcm2711-rpi-400.dtb
-rwxr-xr-x 1 root root   47972 Jan 11 13:56 bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 root root   48303 Jan 11 13:56 bcm2711-rpi-cm4.dtb
-rwxr-xr-x 1 root root   52456 Jan 11 13:56 bootcode.bin
-rwxr-xr-x 1 root root     146 Jan 11 13:54 cmdline.txt
-rwxr-xr-x 1 root root    1796 Dec 29 17:19 config.txt
-rwxr-xr-x 1 root root   18693 Jan  8 15:30 COPYING.linux
-rwxr-xr-x 1 root root    3176 Jan  8 15:30 fixup4cd.dat
-rwxr-xr-x 1 root root    5427 Jan  8 15:30 fixup4.dat
-rwxr-xr-x 1 root root    8444 Jan  8 15:30 fixup4db.dat
-rwxr-xr-x 1 root root    8436 Jan  8 15:30 fixup4x.dat
-rwxr-xr-x 1 root root    3176 Jan 11 13:56 fixup_cd.dat
-rwxr-xr-x 1 root root    7299 Jan 11 13:56 fixup.dat
-rwxr-xr-x 1 root root   10286 Jan 11 13:56 fixup_db.dat
-rwxr-xr-x 1 root root   10288 Jan 11 13:56 fixup_x.dat
-rwxr-xr-x 1 root root     145 Aug 20 06:55 issue.txt
-rwxr-xr-x 1 root root 6301952 Jan 11 13:56 kernel7.img
-rwxr-xr-x 1 root root 7727183 Jan  8 15:30 kernel8.img
-rwxr-xr-x 1 root root 5965008 Jan 11 13:56 kernel.img
-rwxr-xr-x 1 root root    1594 Jan  8 15:30 LICENCE.broadcom
drwxr-xr-x 2 root root   17920 Jan 11 13:56 overlays
-rwxr-xr-x 1 root root  791324 Jan 11 13:56 start_cd.elf
-rwxr-xr-x 1 root root 4789480 Jan 11 13:56 start_db.elf
-rwxr-xr-x 1 root root 2941216 Jan 11 13:56 start.elf
-rwxr-xr-x 1 root root 3700040 Jan 11 13:56 start_x.elf

/mnt = rpi-updated (5.10.6) : /media = only apt updated (5.10.5)

Code: Select all

Only in /mnt: bcm2708-rpi-b.dtb
Only in /mnt: bcm2708-rpi-b-plus.dtb
Only in /mnt: bcm2708-rpi-b-rev1.dtb
Only in /mnt: bcm2708-rpi-cm.dtb
Only in /mnt: bcm2708-rpi-zero.dtb
Only in /mnt: bcm2708-rpi-zero-w.dtb
Only in /mnt: bcm2709-rpi-2-b.dtb
Binary files /mnt/bcm2710-rpi-2-b.dtb and /media/bcm2710-rpi-2-b.dtb differ
Binary files /mnt/bcm2710-rpi-3-b.dtb and /media/bcm2710-rpi-3-b.dtb differ
Binary files /mnt/bcm2710-rpi-3-b-plus.dtb and /media/bcm2710-rpi-3-b-plus.dtb differ
Binary files /mnt/bcm2710-rpi-cm3.dtb and /media/bcm2710-rpi-cm3.dtb differ
Binary files /mnt/bcm2711-rpi-400.dtb and /media/bcm2711-rpi-400.dtb differ
Binary files /mnt/bcm2711-rpi-4-b.dtb and /media/bcm2711-rpi-4-b.dtb differ
Binary files /mnt/bcm2711-rpi-cm4.dtb and /media/bcm2711-rpi-cm4.dtb differ
Only in /mnt: .firmware_revision
Only in /mnt: kernel7.img
Only in /mnt: kernel.img
Common subdirectories: /mnt/overlays and /media/overlays
Only in /mediat: start4cd.elf
Only in /mediat: start4db.elf
Only in /mediat: start4.elf
Only in /mediat: start4x.elf

afred
Posts: 7
Joined: Tue Jan 12, 2021 6:40 am

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 12, 2021 7:34 am

test12395 wrote:
Mon Jan 11, 2021 7:39 pm
having same issue with 4 long flashes followed by 4 short flashes

today i installed raspbian 64 on a new 4B 8GB board then done a apt-get update and apt-get upgrade
restarted and done a rpi-update and the board wouldn't boot after reboot.


Was doing testing and had the same problem after rpi-update. Since there was a big warning flashed when running the rpi-update. I just thought it was me. The install was new and I had nothing to save so I just re-imaged on the same SD (so have no logs) and all is working extremely well... better than 32bit with the old 5.4 kernel where I was getting all kinds of sound, video and driver related problems and problems from old software being served from apt to run on the old kernel.

No logs but here is how I made the brick:

New SD
1
used rpi-imager with:
https://downloads.raspberrypi.org/raspi ... 020-08-24/
reboot (all good)
sudo apt update
sudo apt full-upgrade.
reboot (all good)
rpi-update
reboot --> brick- I think the flash code 4 short and 5 long ??? It is hard to tell if the second flash was 4 or 5 as the change between short and long is not that obvious (add a few ms of delay between perhaps?))

Goto 1 skip rpi-update...

5.10.5-v8+ #1392 SMP PREEMPT Sat Jan 9 18:56:30 GMT 2021 aarch64 GNU/Linux
No real problems since. using as desktop/test bench arm64... Installed and compiled some programs from git (minetest as minecraftpi is not 64); played with backports repos, was thinking about trying out ZFS, which is what brought me here today.

Side note: For rpi engineers: A day or so earlier I tried to use the instructions at the top of this thread to go from an updated image 5.4 32bit on a noobs SD to move to arm64 5.10 kernel and that time after rpi-update it definitely bricked with the 7 short (kernel not found)... Again, thought it was me with nothing of use so nuked and paved with Majaro 64 for a bit until I came back to the raspios... Did I mention I have nuked a lot of test os's in the past week since getting my first rpi4b8gb, and so far the raspios arm64 5.10 is the best :)

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5745
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 12, 2021 12:18 pm

RonR wrote:
Fri Jan 08, 2021 3:20 am
The problem is in /boot. Restoring only 5.10.4 /boot files allows the Pi to boot normally
Could you (or anyone else with the 4/4 flashing LED issue) try to narrow it down?
It's most likely the firmware rather than the kernel.

Can you identify the exact update which caused this. See:
https://github.com/Hexxeh/rpi-firmware/commits/master

If you click on each commit the end of the url contains a git hash. Run

Code: Select all

sudo rpi-update <hash>
to revert to that version. Report the first version with this error.

You can also run:

Code: Select all

sudo SKIP_KERNEL=1 rpi-update <hash>
to just up/downgrade the firmware.

RonR
Posts: 2066
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 12, 2021 8:27 pm

dom wrote:
Tue Jan 12, 2021 12:18 pm
RonR wrote:
Fri Jan 08, 2021 3:20 am
The problem is in /boot. Restoring only 5.10.4 /boot files allows the Pi to boot normally
Could you (or anyone else with the 4/4 flashing LED issue) try to narrow it down?

dom,

The following procedure easily reproduces the problem:

1. Start with a fresh 2020-08-20-raspios-buster-arm64-lite.img image

2. Login: pi/raspberry

3. Run: sudo -i

4. Run: uname -a (observe : Linux raspberrypi 5.4.51-v8+ #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64 GNU/Linux)

5. Run: apt update

6. Run: apt full-upgrade

7. Run: reboot

8. Login: pi/raspberry

9. Run: sudo -i

10. Run: uname -a (observe : Linux raspberrypi 5.10.5-v8+ #1392 SMP PREEMPT Sat Jan 9 18:56:30 GMT 2021 aarch64 GNU/Linux)

11. Run: rpi-update (obseve the following:)

*** Updating firmware
*** Updating kernel modules
*** depmod 5.10.6-v7+
*** depmod 5.10.6+

*** Updating VideoCore libraries
*** Using SoftFP libraries
*** Updating SDK
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk

12. Run: reboot (observe flashing green led: 4L/4S, presumably because depmod 5.10.6-v8+ was not run)

Running rpi-update on a fresh image gets the expected result and the system functions properly following a reboot:

*** Updating firmware
*** Updating kernel modules
*** depmod 5.10.6-v7+
*** depmod 5.10.6+
*** depmod 5.10.6-v8+
*** depmod 5.10.6-v7l+
*** Updating VideoCore libraries
*** Using SoftFP libraries
*** Updating SDK
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk
Last edited by RonR on Wed Jan 13, 2021 6:21 am, edited 2 times in total.

afred
Posts: 7
Joined: Tue Jan 12, 2021 6:40 am

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 12, 2021 8:42 pm

dom wrote:
Tue Jan 12, 2021 12:18 pm
Could you (or anyone else with the 4/4 flashing LED issue) try to narrow it down?
It's most likely the firmware rather than the kernel.
Not sure if this is what you are asking or even if have the state because I really cannot tell the led flash number but I doubt I should be getting board not supported? I guess I could take a video and slow it down.

Here is the process I did same state. {May be me as I am not sure if this is the way to update; Or I am pretty sure it is not.}
Pi4B 8GB.

Code: Select all


#############################################################
clean 64bit image to 16gb SD from rpi-image
https://downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2020-08-24/
#############################################################


pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.4.51-v8+ #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64 GNU/Linux
pi@raspberrypi:~ $ 
pi@raspberrypi:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
E: Repository 'http://deb.debian.org/debian-security buster/updates InRelease' changed its 'Label' value from 'Debian' to 'Debian-Security'
N: Repository 'http://deb.debian.org/debian-security buster/updates InRelease' changed its 'Version' value from '10.7' to '10'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Get:5 http://deb.debian.org/debian-security buster/updates/main arm64 Packages [254 kB]
Get:6 http://deb.debian.org/debian-security buster/updates/main armhf Packages [254 kB]
Get:7 http://deb.debian.org/debian-security buster/updates/main Translation-en [142 kB]
Get:8 http://deb.debian.org/debian-security buster/updates/non-free Translation-en [344 B]
Fetched 651 kB in 5s (119 kB/s)                              
Reading package lists... Done
Building dependency tree       
Reading state information... Done
163 packages can be upgraded. Run 'apt list --upgradable' to see them.
pi@raspberrypi:~ $ sudo apt full-upgrade
---- snip ----
pi@raspberrypi:~ $ reboot
###############################################
###############################################

###############################################
###############################################
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.5-v8+ #1392 SMP PREEMPT Sat Jan 9 18:56:30 GMT 2021 aarch64 GNU/Linux
pi@raspberrypi:~ $ 
pi@raspberrypi:~ $ sudo rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** We\'re running for the first time
 *** Backing up files (this will take a few minutes)
 *** Remove old firmware backup
 *** Backing up firmware
 *** Remove old modules backup
 *** Backing up modules 5.10.5-v8+
#############################################################
WARNING: This update bumps to rpi-5.10.y linux tree
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=288234
'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.

DO NOT use 'rpi-update' as part of a regular update process.

##############################################################
Would you like to proceed? (y/N)
Would you like to proceed? (y/N)
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168  100   168    0     0   1365      0 --:--:-- --:--:-- --:--:--  1365
100  119M  100  119M    0     0  8640k      0  0:00:14  0:00:14 --:--:-- 9758k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 5.10.6-v7+
 *** depmod 5.10.6+
 *** Updating VideoCore libraries
 *** Using SoftFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to 32f9280932f948ecd43847a8d0c492a32469016a
 *** A reboot is needed to activate the new firmware
pi@raspberrypi:~ $ reboot

#############################################################
#### BOOT Error green ligth 4 long 5 (Or 4???) short.
####  SD in failed state so can get info. 
#############################################################


dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5745
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Wed Jan 13, 2021 4:24 pm

Thanks for reports. Looks like recent apt update removes kernel7l.img from /boot (as we aren't going to use this image with 32-bit kernel).
But rpi-update checks for Pi4 support by the existence of that file. I've made it also check for kernel8.img and that seems to work for me now.

busywait
Posts: 101
Joined: Sat May 09, 2020 10:48 pm
Location: Southampton, UK

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Sat Jan 16, 2021 5:24 pm

dom wrote:
Wed Jan 13, 2021 4:24 pm
I've made it also check for kernel8.img and that seems to work for me now.
Thanks - it fixed the boot hang for me....

I have RPiOS 32 and 64 side-by-side, booting with PINN. I booted in to the working 32-bit OS and did an offline update of the 64-bit OS:

Code: Select all

pi@rpi-tv:~ $ sudo mount /dev/mmcblk0p12 /pinn/boot64_p12
pi@rpi-tv:~ $ sudo mount /dev/mmcblk0p13 /pinn/root64_p13
pi@rpi-tv:~ $ sudo ROOT_PATH=/pinn/root64_p13 BOOT_PATH=/pinn/boot64_p12 rpi-update
64-bit OS is working again :)

22/7
Posts: 44
Joined: Thu Sep 26, 2019 9:07 pm

Mon Jan 18, 2021 3:56 pm

moving on
Last edited by 22/7 on Fri Feb 05, 2021 4:50 am, edited 1 time in total.

afred
Posts: 7
Joined: Tue Jan 12, 2021 6:40 am

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Thu Jan 21, 2021 1:51 am

I am not sure where to put this. Since I am using the arm64 I will put it here but I am not sure it is arm64 specific. If anyone wants to point me to the correct place to post info like this I would appreciate it.

RPI4 and Dual Display Settings with arm64.

I have and RPi4 8g A 7" RPI Touchscreen and HDMI 1920x1200.
Using fully updated arm64 build.

I am not sure when it happened (or if it was always funky... see Edit below) but the display settings went wonky:
The Primary display was changed from HDMI1 and set to the Touchscreen,
Some Programs use the Virtual "Screen 0" (see xrandr below) when setting their full screen resolution.
The Panel moved from HDMI1 to the touchscreen and using Main Menu - Preferences - Appearance Settings - Menu Bar to set the panel Display to HDMI-1 would not save between reboot.

Code: Select all

pi@rasp:~ $ xrandr 
Screen 0: minimum 320 x 200, current 2312 x 1680, maximum 7680 x 7680
DSI-1 connected 800x480+1512+1200 (normal left inverted right x axis y axis) 0mm x 0mm
   FIXED_MODE    60.05*+
HDMI-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   ---snip---
   
I still have not found how to stop "some" programs from using the virtual screen 0 when setting full screen resoution.

To resolve some of these I:
Edited /usr/share/dispsetup.sh
to set HDMI1 as primary and added a line to set
the touchscreen map-to-output calling xinput map-to-output raspberrypi-ts DSI-1 in the dispsetup

Code: Select all

 sudo nano /usr/share/dispsetup.sh
 ===========================================
#!/bin/sh
if ! grep -q 'Raspberry Pi' /proc/device-tree/model || (grep -q okay /proc/device-tree/soc/v3d@7ec00000/status 2> /dev/null || grep -q okay $
 #ORIG#### if xrandr --output HDMI-1 --mode 1920x1200 --rate 59.95 --pos 0x0 --rotate normal --output DSI-1 --primary --mode FIXED_MO $
 #ORIG#### xrandr --output HDMI-1 --mode 1920x1200 --rate 59.95 --pos 0x0 --rotate normal --output DSI-1 --primary --mode FI$
   if xrandr --output HDMI-1 --primary --mode 1920x1200 --rate 59.95 --pos 0x0 --rotate normal --output DSI-1 --mode FIXED_MODE --rate 60.05$
      xrandr --output HDMI-1 --primary --mode 1920x1200 --rate 59.95 --pos 0x0 --rotate normal --output DSI-1 --mode FIXED_MODE --rate 60.05$
   fi
   #  Added to set the touchscreen input to its display.
   xinput map-to-output raspberrypi-ts DSI-1
fi
if [ -e /usr/share/tssetup.sh ] ; then
. /usr/share/tssetup.sh
fi
exit 0
 ===========================================
After Reboot. I used a right click on the panel Panel Settings - Geometry to set the panel to display on the HDMI monitor (toggling if I already had it set via. Appearance Settings) and this seems to now save the panel location across reboot.

I am however afraid that my direct edits to config files will be squashed if the underlying program is updated. So if there is a better way please point me in that direction.

Next I need to find out how to stop "some" programs from using the virtual 0 when setting full screen.

Edit: upon reflection, I believe that the problems started after I used raspi-config 1 System Options :: S5 Boot / Auto Login to: Desktop GUI requiring user login... But this is just a guess. I stopped using the Desktop GUI requiring login (for now) because I found that it would create new mounts for USB drives and SD cards on USB readers every time a user logged out and in without restart (EG user logs in 3 times with 2 USB drives and SD on system there will be 6 mounts) and even worse: logging out and back in as another user the Drives could not be read. { I may post that as a separate issue when I find where to post those things}.

Edit 2-- some programs using screen 0 for full screen rather than a sane option like primary:
The programs using the virtual screen 0 for full screen seems to be a known issue in older SDL libraries used. I checked and they were using sdl 1.2. So not a raspberryos problem
http://forums.libsdl.org/viewtopic.php?p=31144
Last edited by afred on Tue Jan 26, 2021 4:27 pm, edited 1 time in total.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5745
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Thu Jan 21, 2021 11:54 am

afred wrote:
Thu Jan 21, 2021 1:51 am
Edit: upon reflection, I believe that the problems started after I used raspi-config 1 System Options :: S5 Boot / Auto Login to: Desktop GUI requiring user login... But this is just a guess. I stopped using the Desktop GUI requiring login (for now) because I found that it would create new mounts for USB drives and SD cards on USB readers every time a user logged out and in without restart (EG user logs in 3 times with 2 USB drives and SD on system there will be 6 mounts) and even worse: logging out and back in as another user the Drives could not be read. { I may post that as a separate issue when I find where to post those things}.
Try creating an issue here: https://github.com/RPi-Distro/raspberrypi-ui-mods with clear step of how to reproduce.

afred
Posts: 7
Joined: Tue Jan 12, 2021 6:40 am

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 26, 2021 4:40 pm

Problems with Bluetooth Audio

Code: Select all

RPI4B 8GB 

uname -a
Linux elan4 5.10.10-v8+ #1397 SMP PREEMPT Mon Jan 25 18:46:44 GMT 2021 aarch64 GNU/Linux
Is bluetooth audio working in arm64? I had it working in arm32.
Tried it today and:
the soundlink mini2 attached in the bluetooth Panel item;
soundlink speaker says it is connected;
soundlink is seen in the sound Panel (right click volume);
However, when I try to enable it (move the green check from HDMI to soundlink) it pops up a "Connecting Audio Device" dialog that says:
"Failed to connect to Bluetooth device-Device not found by PulseAudio"

Also is there an issue tracker for arm64?
Is this the kind of issue you want to see here?

fruitoftheloom
Posts: 26477
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Jan 26, 2021 4:53 pm

afred wrote:
Tue Jan 26, 2021 4:40 pm
Problems with Bluetooth Audio

Code: Select all

RPI4B 8GB 

uname -a
Linux elan4 5.10.10-v8+ #1397 SMP PREEMPT Mon Jan 25 18:46:44 GMT 2021 aarch64 GNU/Linux
Is bluetooth audio working in arm64? I had it working in arm32.
Tried it today and:
the soundlink mini2 attached in the bluetooth Panel item;
soundlink speaker says it is connected;
soundlink is seen in the sound Panel (right click volume);
However, when I try to enable it (move the green check from HDMI to soundlink) it pops up a "Connecting Audio Device" dialog that says:
"Failed to connect to Bluetooth device-Device not found by PulseAudio"

Also is there an issue tracker for arm64?
Is this the kind of issue you want to see here?

This whole post is regards running Raspberry Pi Operating System ARMHF 32bit Userland with a 64bit Kernel.


If you are asking about Raspberry Pi Operating System ARM64 Beta which is 64bit Userland and 64bit Kernel then you are in the wrong post, try here:

viewtopic.php?f=63&t=275372
The information is out there....you just have to let it in.

My other Linux machines: ChromeBox
https://www.aliexpress.com/item/32966393971.html
& Stone Desktop Intel CoreDuo circa 2010

JamesPi123
Posts: 121
Joined: Fri Sep 23, 2016 10:02 pm
Location: Inside my Pi
Contact: Website

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Tue Apr 13, 2021 10:18 pm

What is the status of FIQ at the moment? I got my CM4 today and am using the 64 bit kernel.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5745
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Wed Apr 14, 2021 10:05 am

JamesPi123 wrote:
Tue Apr 13, 2021 10:18 pm
What is the status of FIQ at the moment? I got my CM4 today and am using the 64 bit kernel.
There is no FIQ support (upstream) for arm64 kernel.
That is typically not an issue as the dwc_otg driver is not used on Pi4.
The upstream, non-FIQ dwc2 driver is available.

Return to “Advanced users”