I try to post a pull-request to GitHib but i can't "Pull request creation failed. Validation failed: must be a collaborator"
An other possibillity is compiling new image with ahci module. How can i add "ahci module" before compiling from my wsl ubuntu ?
Hello and thank you for your feedback but do not see any offense in the term "embarrasing". However, please note that the Compute Module 4 IO Board version has a PCIe port. I try to use it to mount Sata disk.
I will follow your advice and send a pull-request to GitHub to enable this kernel config dedicated to CM4.
Ahci module kernel is not include in RPi4.arm-11.0.3 version. It's embarrassing because CM4 PCIe cannot be used can't use with Sata drives.
Do you plan to include this mode in a future Raspberry CM4 version ?
Does anyone have an idea and help me ?
Hi,
Sata controller ASMEDIA does not works on Rpi Computer Module 4.
LE:~ # lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2711 PCIe Bridge (rev 20)
01:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02)
Kodi log file :
################################################################################
# ... output of dmesg
# LibreELEC release: RPi4.arm-11.0.3
#
################################################################################
[ 2.443809] pcieport 0000:00:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
[ 2.443814] pcieport 0000:00:00.0: device [14e4:2711] error status/mask=00000080/00002000
[ 2.443821] pcieport 0000:00:00.0: [ 7] BadDLLP
[ 2.444446] pcieport 0000:00:00.0: AER: Corrected error received: 0000:00:00.0
Is Sata Ctrl supported on LE ?
How can i fix it ?
Regards,
François
I reset the Flirc receiver and my Libreelec but the results were worse. The menu scrolled without any action on the remote control.
Reading the Flirc forum, I found a similar problem. External lights and IR noise interfering with signals from my remote and flooding the flirc receiver.
My TV is plasma technology and probably generates a lot of IR noise. Anyway, to solve the problem and reduce the flow of IR, i protected Flirc with a light paper mask.
Now the remote and Flirc work properly without ghost or missing event.
Thank you for this meticulous investigation.
The problem disappears when I connect a monitor in the same context with the same and others actives ir devices.
I will do the test by isolating the LE and test the remote control without external ir pollution
From "Settings > LE Settings Addon > System > Paste system logs" i got error : "failed to paste log files, try again" !
From "pastekodi" command line via ssh, no url returned !
from Kodi log uploader add-on an other error message "file is to large > 1MB" !
I build a new fresh LE install with the same problem.
Fortunualy , pastebin works fine.
URL link is http://ix.io/4hkp
Note that only TV the is connected to LE with this logfile. I did not connect an other monitor to log the proper functioning.
If necessary i can do it and paste those new logfiles.
Tank's for your help.
I don't have any CEC adapter on my LE (Settings -> System -> Input -> Peripherals) but my LE is Generic with Intel CPU and not Rpi.
So i "reset above Settings to default" and disable CEC on my TV but problem still present.
Does anybody could give me some track to explore ?
I log events before switch screens but i haven't see any suspicious events (see attach file for log output)
Any idea ?
Ok sorry for this misunderstanding. "Pb" == problem.
When LE is connected to my TV (Panasonic Viera over HDMI2) remote responds very slowly with very many misses. After several actions on the keys, remote control no longer responds at all.
if I connect LE to another monitor, then the remote works perfectly (same HDMI2 port).
No reboot necessary to see the change.
Pb desapear when use my Libreelec with an other monitor (same HDMI port) ????
Where can i log the trouble ?
I can't use flirc with my remote control (one for all URC7935). Responses times are very long and works once in 10.
I try it on fresh Libreelec install (10.0.3 - Generic / intel cpu) but result is the same.
Partition was delete and recreate with gparted.
The udev flags has been reset with news and good values :
...
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext4
....
Now automount partition works fine.
I change mount point with e2label to finish my setup.
Special thank to Chewitt bringing me on the right way.
Thread is Resolved
Good point Chewitt. It seems udev flags are persistants even after deleting partition :
# udevadm info /dev/sdd1
...
E: ID_FS_VERSION=5000
E: ID_FS_TYPE=zfs_member
....
This disk come from my NAS with zpool partition (zfs V5000 filesystem). Probably, I should destroy zpool before using the disk !
I take a look to fix it.
in addition fsck output :
# fsck.ext4 -fv /dev/sdd1
e2fsck 1.45.3 (14-Jul-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
152 inodes used (0.00%, out of 122101760)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 73/71
87005300 blocks used (17.82%, out of 488378368)
0 bad blocks
57 large files
75 regular files
68 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
143 files
Thank's Chewitt.
Please find in attachment output from command line :
# journalctl | egrep -v "ntp|kodi.sh|tun0|eth0"
It seem last line "LibreELEC systemd[1]: var-media-ST_2TB.mount: Succeeded" come from my workaround to mount /dev/sdd1 in ksh script "~/..config/autostart.sh" executed at startup.journalctl.txt
# cat autostart.sh
#!/bin/sh
mkdir -p /media/ST_2TB
mount /dev/sdd1 /var/media/ST_2TB -o nosuid,nodev,noexec,noatime
I didn't see any error about sdd.
How can i increase log level and see specific log about disk mounting processs ?
# dmesg | egrep "ata|sd"
[26144.125068] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
[26144.143480] sd 3:0:0:0: [sdd] Stopping disk
[26144.951753] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[26144.951872] sd 2:0:0:0: [sdc] Stopping disk
[26146.498437] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[26146.498515] sd 1:0:0:0: [sdb] Stopping disk
[26146.521762] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[26146.522087] sd 0:0:0:0: [sda] Stopping disk
[26150.130059] ata6: SATA link down (SStatus 0 SControl 300)
[26150.130124] ata5: SATA link down (SStatus 0 SControl 300)
[26150.189228] sd 0:0:0:0: [sda] Starting disk
[26150.189253] sd 1:0:0:0: [sdb] Starting disk
[26150.189314] sd 2:0:0:0: [sdc] Starting disk
[26150.189348] sd 3:0:0:0: [sdd] Starting disk
[26150.285794] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[26150.303256] ata2.00: configured for UDMA/133
[26156.762607] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[26156.932566] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[26156.934626] ata4.00: configured for UDMA/133
[26156.969869] ata3.00: configured for UDMA/133
[26159.755961] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[26159.788094] ata1.00: configured for UDMA/133
[31221.024496] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
[31221.056534] sd 3:0:0:0: [sdd] Stopping disk
[31221.857847] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[31221.857998] sd 2:0:0:0: [sdc] Stopping disk
[31222.277858] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[31222.277933] sd 1:0:0:0: [sdb] Stopping disk
[31222.297854] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[31222.298365] sd 0:0:0:0: [sda] Stopping disk
[31225.699602] ata5: SATA link down (SStatus 0 SControl 300)
[31225.699665] ata6: SATA link down (SStatus 0 SControl 300)
[31225.755499] sd 0:0:0:0: [sda] Starting disk
[31225.755507] sd 1:0:0:0: [sdb] Starting disk
[31225.755585] sd 2:0:0:0: [sdc] Starting disk
[31225.755615] sd 3:0:0:0: [sdd] Starting disk
[31225.855407] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[31225.872881] ata2.00: configured for UDMA/133
[31232.342208] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[31232.553128] ata3.00: configured for UDMA/133
[31232.592219] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[31232.594011] ata4.00: configured for UDMA/133
[31235.535576] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[31235.566798] ata1.00: configured for UDMA/133
