Hi,

It's in my backlog of devices to play with for F-39.

It looks like it's not finding the storage, you don't mention what sort of storage you're trying to run Fedora from, is it the SD card or do you have the firmware on SD and Fedora on something else?

Peter

On Sun, 30 Jul 2023, 13:18 Andreas Reschke, arm_ml@rirasoft.de wrote:

Hi there, I've tried to install Fedora on my Rock 5 without success.

Booting with

https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5b... on SD-Card and source from

https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything... .

Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # #

Full log file: see rock.txt

Has anybody more succcess ?

Greetings Andreas_______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Hi Andreas,

...

It's in my backlog of devices to play with for F-39.

It looks like it's not finding the storage, you don't mention what sort of storage you're trying to run Fedora from, is it the SD card or do you have the firmware on SD and Fedora on something else?

Peter

Hello Peter, UEFI is on SD-Card, Fedora iso is on USB-Stick, another empty USB-Stick and NVME disc are available for storage.

So a quick look on upstream lists it doesn't look like USB [1] or either of the PCI controllers [2][3], there's two different ones, have yet made it upstream as yet. so ATM without a custom kernel I wouldn't expect it to work for either USB or NVME storage.

The patch set for the USB support isn't upstream yet and it'll only support the upper USB3 port until they land another driver. On the plus side it looks like both the pcie patch sets are headed towards the 6.6 merge window.

Looking at upstream DTs for the Rock5B it looks like it's just the mSD/eMMC storage that's enabled as of 6.5-rc4, it doesn't look like even the ethernet works.

I think out of the box we probably won't be usable until F-40 for this device. I have seen a lot posted upstream, it seems a lot of that hasn't actually landed yet though.

Peter

[1] https://www.spinics.net/lists/linux-usb/msg244163.html [2] https://www.spinics.net/lists/linux-pci/msg141988.html [3] https://www.spinics.net/lists/linux-pci/msg141465.html

...

On Sun, 30 Jul 2023, 13:18 Andreas Reschke, arm_ml@rirasoft.de wrote:

...

Hi there, I've tried to install Fedora on my Rock 5 without success.

Booting with

https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5b...

...

on SD-Card and source from

https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything....

...

Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # #

Full log file: see rock.txt

Has anybody more succcess ?

Greetings Andreas_______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:

https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

...

Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Hello,

today I've tried once again to install Fedora on Rock 5B.

It works !! Even with GUI!

What you need: 1) https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.9.1/rock-5b... dd this Image on a SD-Card

2) https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything...

dd this Image on a USB stick

Put both in your Rock 5B and boot. I've done the Net-install installation with KDE Wayland. The SD-Card with UEFI is needed for booting. Don't know if it's possible to write it to the Firmware or somewhere else.

After a first check

not working:

- Sound

- Bluetooth

working

- Fan for CPU

- WIFI

- NVME

oot@rockpi5:~# lsblk -f NAME              FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS zram0                                                                                              [SWAP] nvme0n1 ├─nvme0n1p1       vfat        FAT32          F81B-9757                                 588M     2% /boot/efi ├─nvme0n1p2       xfs                        0fa12a00-a5e6-4063-b5d9-a6bbb8e5d324    711,5M    26% /boot └─nvme0n1p3       LVM2_member LVM2 001       6X90NM-HSY9-mFxU-AmZs-aBwa-53sW-OeWx6m  ├─fedora-root   xfs                        900a06a9-f39b-45ee-b088-439a4088693c      6,1G    59% /  └─fedora-homelv xfs                        cc8dcc56-38ac-4ac2-9c0c-332b89044974     95,4G     5% /home root@rockpi5:~# lspci 0000:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 0002:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 0004:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) root@rockpi5:~# lsmod | sort bluetooth             897024  17 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm bnep                   32768  2 btbcm                  24576  1 btusb btintel                57344  1 btusb btmtk                  16384  1 btusb btrtl                  32768  1 btusb btusb                  77824  0 cfg80211             1073152  3 rtw89_8852b,rtw89_core,mac80211 crct10dif_ce           12288  1 dm_multipath           45056  0 fat                    94208  1 vfat fuse                  180224  3 ghash_ce               20480  0 ip_set                 61440  0 joydev                 32768  0 libarc4                12288  1 mac80211 loop                   36864  0 mac80211             1282048  2 rtw89_core,rtw89_pci Module                  Size  Used by nf_conntrack          180224  2 nf_nat,nft_ct nf_defrag_ipv4         12288  1 nf_conntrack nf_defrag_ipv6         24576  1 nf_conntrack nf_nat                 57344  1 nft_chain_nat nfnetlink              20480  3 nf_tables,ip_set nf_reject_ipv4         16384  1 nft_reject_inet nf_reject_ipv6         24576  1 nft_reject_inet nf_tables             286720  391 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet nft_chain_nat          12288  3 nft_ct                 20480  7 nft_fib                12288  3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet nft_fib_inet           12288  1 nft_fib_ipv4           12288  1 nft_fib_inet nft_fib_ipv6           12288  1 nft_fib_inet nft_reject             12288  1 nft_reject_inet nft_reject_inet        12288  16 nvme                   57344  4 nvme_core             176128  5 nvme ohci_hcd               61440  1 ohci_platform ohci_platform          12288  0 polyval_ce             12288  0 polyval_generic        12288  1 polyval_ce qrtr                   45056  4 r8169                 110592  0 rfcomm                 98304  0 rfkill                 40960  8 bluetooth,cfg80211 rtw89_8852b           368640  1 rtw89_8852be rtw89_8852be           12288  0 rtw89_core            495616  2 rtw89_8852b,rtw89_pci rtw89_pci              69632  1 rtw89_8852be scsi_dh_alua           24576  0 scsi_dh_emc            12288  0 scsi_dh_rdac           16384  0 snd                   131072  5 snd_seq,snd_seq_device,snd_timer snd_hrtimer            12288  1 snd_seq               110592  7 snd_seq_dummy snd_seq_device         16384  1 snd_seq snd_seq_dummy          12288  0 snd_timer              49152  2 snd_seq,snd_hrtimer soundcore              16384  1 snd sunrpc                733184  1 uinput                 24576  0 vfat                   20480  1 xfs                  2199552  3 xhci_plat_hcd          20480  0 zram                   32768  2 root@rockpi5:~#

Don't know what driver for graphic is used. System isn't fast as the Armbian version, but hey it's working.

Andreas

Am 01.08.23 um 08:27 schrieb Andreas Reschke:

Thank you Peter,

so we have to wait. I will try it again at the end of the year.

Greetings

Andreas

Am 01.08.23 um 00:06 schrieb Peter Robinson:

...

Hi Andreas,

...

...

It's in my backlog of devices to play with for F-39.

It looks like it's not finding the storage, you don't mention what sort of storage you're trying to run Fedora from, is it the SD card or do you have the firmware on SD and Fedora on something else?

Peter

Hello Peter, UEFI is on SD-Card, Fedora iso is on USB-Stick, another empty USB-Stick and NVME disc are available for storage.

So a quick look on upstream lists it doesn't look like USB [1] or either of the PCI controllers [2][3], there's two different ones, have yet made it upstream as yet. so ATM without a custom kernel I wouldn't expect it to work for either USB or NVME storage.

The patch set for the USB support isn't upstream yet and it'll only support the upper USB3 port until they land another driver. On the plus side it looks like both the pcie patch sets are headed towards the 6.6 merge window.

Looking at upstream DTs for the Rock5B it looks like it's just the mSD/eMMC storage that's enabled as of 6.5-rc4, it doesn't look like even the ethernet works.

I think out of the box we probably won't be usable until F-40 for this device. I have seen a lot posted upstream, it seems a lot of that hasn't actually landed yet though.

Peter

[1] https://www.spinics.net/lists/linux-usb/msg244163.html [2] https://www.spinics.net/lists/linux-pci/msg141988.html [3] https://www.spinics.net/lists/linux-pci/msg141465.html

...

...

On Sun, 30 Jul 2023, 13:18 Andreas Reschke, arm_ml@rirasoft.de wrote:

...

Hi there, I've tried to install Fedora on my Rock 5 without success.

Booting with

https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5b...

...

on SD-Card and source from

https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything....

...

Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [  352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [  352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [  352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [  352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [  352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [  352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [  352.172852] dracut-initqueue[1065]: Warning: # # [  352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [  352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [  352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [  352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [  352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [  352.174156] dracut-initqueue[1065]: Warning: # # [  352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot:     #### [  352.174543] dracut-initqueue[1065]: Warning: # # [  352.174775] dracut-initqueue[1065]: Warning: Reason unknown [  352.174970] dracut-initqueue[1065]: Warning: # #

Full log file: see rock.txt

Has anybody more succcess ?

Greetings Andreas_______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:

https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

...

Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

---

arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Hello Peter,

update from my side: booting with the last version v0.9.1 from https://github.com/edk2-porting/edk2-rk3588/releases/ and actual Fedora 40 Rawhide the installation works fine.

I'm writing this mail from this SBC.

root@rockpi5:~# inxi -F System: Host:rockpi5.reschke.lan Kernel:6.8.0-0.rc4.20240214git7e90b5c295ec.37.fc41.aarch64 arch:aarch64 bits:64 Console:pty pts/1 Distro:Fedora Linux 41 (Rawhide Prerelease) Machine: Type:Embedded-pc Mobo:Radxa model:ROCK 5 Model B serial:386F0C585A66D216 UEFI:EDK II v:0.9.1 date:10/12/2023 CPU: Info:triple core model:N/A bits:64 type:MT MCP cache:L2:2.5 MiB Speed:N/A min/max:N/A cores:No per core speed data found. Graphics: Message:No PCI device data found. Display:server:X.Org v:23.2.4 with:Xwayland v:23.2.4 driver:X: loaded:modesetting dri:swrast gpu:N/A resolution:1920x1080~60Hz API:EGL v:1.5 drivers:kms_swrast,swrast platforms:gbm,x11,surfaceless,device API:OpenGL v:4.5 vendor:mesa v:24.0.0 renderer:llvmpipe (LLVM 17.0.6    128 bits) API:Vulkan v:1.3.268 drivers:llvmpipe surfaces:xcb,xlib Audio: Message:No device data found. API:ALSA v:k6.8.0-0.rc4.20240214git7e90b5c295ec.37.fc41.aarch64 status:kernel-api Network: Device-1:Realtek RTL8852BE PCIe 802.11ax Wireless Network driver:rtw89_8852be IF:wlP2p1s0 state:up mac:2c:05:47:8f:e9:e1 Device-2:Realtek RTL8125 2.5GbE driver:r8169 IF:enP4p1s0 state:up speed:1000 Mbps duplex:full mac:00:e0:4c:68:00:cd Bluetooth: Device-1:Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver:btusb type:USB Report:btmgmt ID:hci0 state:up address:00:1B:DC:0F:6E:EF bt-v:2.1 Drives: Local Storage:total:953.87 GiB used:21.93 GiB (2.3%) ID-1:/dev/nvme0n1 vendor:Samsung model:MZVKW1T0HMLH-000H1 size:953.87 GiB Partition: ID-1:/ size:14.94 GiB used:10.23 GiB (68.5%) fs:xfs dev:/dev/dm-0 ID-2:/boot size:960 MiB used:413.3 MiB (43.1%) fs:xfs dev:/dev/nvme0n1p2 ID-3:/boot/efi size:598.8 MiB used:11.7 MiB (1.9%) fs:vfat dev:/dev/nvme0n1p1 ID-4:/home size:99.94 GiB used:11.29 GiB (11.3%) fs:xfs dev:/dev/dm-1 Swap: ID-1:swap-1 type:zram size:8 GiB used:0 KiB (0.0%) dev:/dev/zram0 Sensors: Src:lm-sensors+/sys Message:No sensor data found using /sys/class/hwmon    or lm-sensors. Info: Memory:total:16 GiB note:est. available:15.3 GiB used:6.18 GiB (40.4%) Processes:272 Uptime:5h 50m Shell:Bash inxi:3.3.32 root@rockpi5:~#

What's not working at the moment: - accelerate GPU

- sound via 3,5 mm Headphone

- Bluetooth via Realtek RTL8852BE PCIe 802.11ax Wireless Network (Radxa wireless A8)

Greetings

Andreas

Am 16.02.24 um 7:12 PM schrieb Peter Robinson:

Hi Folks,

...

It's in my backlog of devices to play with for F-39.

It looks like it's not finding the storage, you don't mention what sort of storage you're trying to run Fedora from, is it the SD card or do you have the firmware on SD and Fedora on something else?

So I've finally started to look at this and yes, it looks like there's issues with the SD card in Linux although apparently it should be supported. I will be looking at that over the weekend.

I need to find a spare NVME drive to put in it.

The plan is to have some level of support in Fedora 40.

The upstream status as documented here is a pretty good overview of where we're at upstream: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-roc...

...

On Sun, 30 Jul 2023, 13:18 Andreas Reschke,arm_ml@rirasoft.de wrote:

...

Hi there, I've tried to install Fedora on my Rock 5 without success.

Booting with https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5b... on SD-Card and source from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything....

Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # #

Full log file: see rock.txt

Has anybody more succcess ?

Greetings Andreas_______________________________________________ arm mailing list --arm@lists.fedoraproject.org To unsubscribe send an email toarm-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

-- _______________________________________________ arm mailing list --arm@lists.fedoraproject.org To unsubscribe send an email toarm-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

Am 16.02.24 um 19:36 schrieb Peter Robinson:

...

What's not working at the moment:

• accelerate GPU

• sound via 3,5 mm Headphone

Both of the above are known.

...

• Bluetooth via Realtek RTL8852BE PCIe 802.11ax Wireless Network (Radxa wireless A8)

And I think that is too because the USB isn't plumbed through to the M2-E slot yet (see the link I referenced).

...

Greetings

Andreas

Hello Peter,

what does this mean ?

Issue SoC Rock Pi 5A Rock Pi 5B EVB1 Notes

Headphone Jack Playback |n/a| 6.6-rc1 6.4-rc1 6.8-rc1 DONE

Sound via 3,5 mm Headphone doesn't work. No soundcard found?

root@rockpi5:~# inxi -A Audio:Message:No device data found. API:ALSA v:k6.10.0-0.rc2.20240607git8a92980606e3.28.fc41.aarch64 status:kernel-api Server-1:PipeWire v:1.1.82 status:active root@rockpi5:~#

-- _______________________________________________ arm mailing list --arm@lists.fedoraproject.org To unsubscribe send an email toarm-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue