Hi to all!
I'm trying to install siduction 2023.1.0 on an Hyper-v v2 created VM
The iso load ok but when fail to install (iso checksum is OK)
PCI: Fatal: No config space access function found
Waiting for up to 30s for devices to settle...
Failed to detect live media
Busybox v1.36.1
(initramfs)_
From what I read the first error line
"PCI Fatal error..." despite of the name fatal could be treated just as a warning
(please correct me if I'm wrong) and it's simply because Hyper-v v2 VM doesn't emulate PCI devices at all
For the "Failed to detect live media" I already tried copying the iso content to a disk
dd if=.../siduction-2023.1.1.iso of=/dev/sdb
but the results are the same: live Siduction menu start but refuse to install with same error
Could you help me to find a workaround?
Thank you in advance :)
I don't know about Hyper-V VMs, so this is just a guess without knowledge: could it be Hyper-V is configured with Secure Boot on, which won't work with Siduction Iso? Are there any settings in the VM configuration where you could switch off Secure Boot?
yes, on a Hyper-v V2 the secure boot is to be disabled when running a linux-os
Also not being familiar with Hyper-V I did a quick search and got this at the top.
https://bobcares.com/blog/hyper-v-secure-boot-disable/
Thank you but not work
I've already disabled Secure boot (indeed if activated i can't even reach the live cd menu) so it's something that happen after boot
Just as test I successfully installed on a same type VM last Debian and Kubuntu (that also use Calamares) without issues
I tried more and more things without good results
I'm about to lose my hope and move to vanilla Debian
I tested load and install of many other distribution but not Siduction do you think could I open a bug report?
what iso and which DE did you take ?
best choice should be Siduction Test Builds
Tried with both official release 2023.1.1 iso and lastest test iso 202410211701: no luck
KDE Xorg and Xcfe all lead to same result
I suppose is a problem with the loader of the iso before the specific flavors of the ISOs
The images are fine, just booted the Plasma image last night after I built it. Never used Hyper-V myself, so no idea.
I don't think, our iso will work in hyperv, if hyper-v because
a) our kernel is not configured for hyper-v guest and
b) fll-initramfs has to include another type of detection the live media
And for me, i will not change that, since i have no interest running siduction in hyper-v.
siduction is mainly for real hardware, that's it.
If it works in some kind of virtualisation, good, if not, it does not matter. (It works in qemu and vbox, so it's fine for me).
Quite a pity, I really love to move some of my VMs to Siduction and for my situation HyperV is the best viable option.
Please, I wouldn't call myself a Linux expert but I love to learn on the way, so with some hints from you about where to start I would love to dedicate some efforts trying to solve and perhpas help other people with similar needs.
I think that because it is already working in other distributions like (K)Ubuntu and the Debian Sid itself it couldn't be a too hard task, probably just starting comparing how it works in the other distributions could be a start.
I also understand it's not a priority for the project but a bonus point is that as the Hyper-V emulated VM hardware is stable across versions a fix can potentially last years even without be actively maintained.
QuotePlease, I wouldn't call myself a Linux expert but I love to learn on the way, so with some hints from you about where to start I would love to dedicate some efforts trying to solve and perhpas help other people with similar needs.
Quote
I think that because it is already working in other distributions like (K)Ubuntu and the Debian Sid itself it couldn't be a too hard task, probably just starting comparing how it works in the other distributions could be a start.
Since i have not time for that, you can try to fix it for us:
https://github.com/siduction/fll-live-initramfs
Maybe you can add the needed code.
Thank you!
I hope I can help, I already started to have a look at it
But maybe your real problem is, our kernel is not configured for hyperv support.
Ok, but one thing a time ;)