Open taleteller opened 8 months ago
The issue template outlines how to provide the support file - https://wiki.batocera.org/troubleshooting#create_a_batocera_support_file
Sure, if it helps: batocera-support-20240312144831.tar.gz
This is from a USB booted V39, it should contain an internal SATA device, like /dev/sdb
but nope. Smells like missing kernel flags to me. Do you want a V38 as well?
the kernel module configuration for sata hasn't changed. you may have stumbled upon a kernel regression for your controller. we have move to 6.8 now, did you want to try an early v40 image?
@taleteller v40 early tests which has the updated kernel - https://drive.google.com/drive/folders/1_bqmR7CoZ78i7DolYt5b-RRqB5c-LPyN?usp=drive_link
Sadly still no internal devices, support file from this image attached batocera-support-20240315110619.tar.gz
@taleteller create a manjaro USB & boot off that. set the kernel to 6.7 or 6.8 then reboot. ensure you're on that kernel version (uname -r
via the terminal will confirm) & then verify you can access your sata device. that's a good way to confirm the suspected kernel regression.
This might take a little, because the latest manjora iso comes with 6.6 (internal drive working) and to get a reliable result I need to install it. The only drive spares I got around are hdds.
only you can verify it unfortunately. other systems are fine. the alternative is to move away from sata for that board but if it's a regression, the kernel devs needs to know pronto.
Yap, this is a kernel thing. Manjaro with 6.6.19-1 boots fine, booting with 6.7.7-1 and 6.8.0rc6-1 fail and drop me on an emergency shell without sda present in the dev tree.
By coincidence I found a similar unsolved case in the Manjaro Forums with also similar hardware: https://forum.manjaro.org/t/stuck-on-emergency-shell-with-kernel-6-7/157796
ok good, thought as much. you will need to raise an issue with the linux kernel - https://www.kernel.org/doc/html/v4.19/admin-guide/reporting-bugs.html#:~:text=lists%20like%20LKML.-,Identify%20who%20to%20notify,via%20the%20subsystem%20mailing%20list.
Well the kernel dev list is not really my waters. I can verify the problem for one Mainboard of one Vendor and would need to check mainline built kernels and I am not exactly the gentoo guy. Doubtful such an issue will get attention anytime soon. Meanwhile I verified that NVMe devices are working and therefore I will migrate to it.
FYI, there is a bug report on that issue
Batocera build version
39
Your architecture
X86
Your Graphic Processor Unit(s) (GPU)
Nvidia, does not matter
Issue description
Today I attempted an Upgrade to check if the full broken status of DBus/Steam has been addressed (Spoiler: nope) and ended up with a broken system. After the Upgrade V38->V39 the system would not boot anymore stuck with a black screen.
Detailed reproduction steps
I use an B660 mainboard together with an 12th gen CPU and a SATA SSD. Just upgrading to V39 was enough to have a lot of "fun" for the whole day.
Details of any attempts to fix this yourself
My first assumption was that something in the upgrade processes went wrong, or it being some secure boot issue. Neither is true. After getting into the verbose boot start i got these lines repeating on the consoles
Therefore early boot was working but after that the device went missing. I attempted a reinstallation from a stick but oddly the SSD would not show up. Clearing it was of no use. Therefore I wrote the image file directly to the SSD by adapter. Then I got the exact same problem as above. More crosschecking revealed, the system no longer recognizes any internal SATA devices. (NVMe I have not checked). On V38 it works fine, V39 no longer. Booting V39 via USB works fine, but thats no solution.
I ended up downgrading to V38
Details of any modifications you have made to Batocera.
N/A
Logs and data
Oddly enough lspci and dmsg came up IDENTICAL on v38 and v39. However on V39 no internal SATA device appears in /dev or anywhere else.