No devices detected!

[iamthescatmann]

CSMWrap boots, everything is going well... no devices.

CSMWrap Version: 1.3.0

Hardware Details:
Motherboard: LNVNB121612 (Lenovo)
CPU: 12th Gen Intel(R) Core(TM) i5-1235U
GPU: Intel(R) Iris(R) Xe Graphics

UEFI Firmware Version: LENOVO JKCN50WW, 3/17/2025 (latest for my cutie laptoppy)
edit: uefi 2.70 insyde corp

CSMWrap Output:
when i press esc for boot menu there is nothing and when it tries to boot it gives could not read boot disk for floppy disk and hard drive (no cdrom because no cd disk for my laptop) and also tried waiting for 60 seconds so it retries like it says but it just reboots
native resolution and its unlocked and everything but i also need to use my devices!!! (my usb drive, my external sata to usb hdd, i dont think it detects my internal nvme ssd anyway i dont think i will be using it)

UEFI Settings: All requirements met with a little use of setup_var in a USB UEFI Shell + enabled Legacy Option ROMs. if available anyway
i tried to enable native csm but i found out the settings that are found in my .fd files' (i got from my lenovo support page) ifr data dont Apply to this laptop and setup_var couldnt find it i figured i dont have any native csm anywhere. for now

Legacy OS: Windows 7 Ultimate SP1 x64

Steps to Reproduce: same bug really i tried to use csmwrap everywhere even my efi partition same stuff. will keep using from the uefi shell because i can probably active like .efi drivers from there for csmwrap's convenience
i flashed my usb with a uefi shell iso using rufus then i put the csmwrap efi file then booted into the uefi shell then typed in the filename to boot

edit: csmwrap 1.2.3 also creates the same result

Could it be because i chose the legacy option rom setting?
edit2: changed it back and no so I am stuck here. I recorded the logs and they dont say anything either
Also wont be using UEFISeven because it just doesnt work even with the acpi.sys patching stuff

[iamthescatmann]

figured my hardware is just incompatible :( its pure uefi

[FlyGoat]

We are actually targeting pure UEFI hardware so this is not the reason :-)

Sounds like another XHCI issue.

[iamthescatmann]

We are actually targeting pure UEFI hardware so this is not the reason :-)

Sounds like another XHCI issue.

UPDATE:

disabling VT-d works for some reason????

[iamthescatmann]

We are actually targeting pure UEFI hardware so this is not the reason :-)

Sounds like another XHCI issue.

thank you for telling me before i figured it out Lol
could be also the reason why uefiseven and uefi boot didnt work?

[iamthescatmann]

We are actually targeting pure UEFI hardware so this is not the reason :-)

Sounds like another XHCI issue.

is VT-d 100% an issue? to include it as a requirement to disable

[iamthescatmann]

update: its only detecting my nvme ssd so far. ironic
im gonna try without booting uefi shell. (adding an efi partition entry with bootice)
also other devices. i want to run windows to go (7) on my external sata to usb hdd

[iamthescatmann]

update: its only detecting my nvme ssd so far. ironic im gonna try without booting uefi shell. (adding an efi partition entry with bootice) also other devices. i want to run windows to go (7) on my external sata to usb hdd

it only detects my internal hard drive (gpt) and i dont want to lose all my data. stuck here for now

[iamthescatmann]

update: its only detecting my nvme ssd so far. ironic im gonna try without booting uefi shell. (adding an efi partition entry with bootice) also other devices. i want to run windows to go (7) on my external sata to usb hdd

it only detects my internal hard drive (gpt) and i dont want to lose all my data. stuck here for now

tried every option. Nothing
i guess i can change up something about my hard drive

[FlyGoat]

It's also new to me that vt-d can be an issue....
USB (XHCI) is also a long-standing known issue for us, but we never got the chance to find the root cause.

[iamthescatmann]

It's also new to me that vt-d can be an issue.... USB (XHCI) is also a long-standing known issue for us, but we never got the chance to find the root cause.

I'm gonna format my hard drive to MBR to see what happens with nvme ssds unless you say something about it

About the xhci thing for me there is no xhci handoff option atleast for my uefi firmware and vt-d just seems like it does the opposite of a handoff but yeah I've tried everything and it can only detect my internal hard drive which is not part of xhci

[iamthescatmann]

It's also new to me that vt-d can be an issue.... USB (XHCI) is also a long-standing known issue for us, but we never got the chance to find the root cause.

I'm gonna format my hard drive to MBR to see what happens with nvme ssds unless you say something about it

About the xhci thing for me there is no xhci handoff option atleast for my uefi firmware and vt-d just seems like it does the opposite of a handoff but yeah I've tried everything and it can only detect my internal hard drive which is not part of xhci

weird when i turn vt-d on it detects nothing also it runs slower for some reason
cant i debug this?

[iamthescatmann]

if you want i can compile

[FlyGoat]

I have no idea what might be the problem :-(

[iamthescatmann]

I have no idea what might be the problem :-(

I'm gonna toy with the above 4g and resizable bar settings also I can format my hard drive now I'm comfortable with mbr

[ages2001]

It's also new to me that vt-d can be an issue.... USB (XHCI) is also a long-standing known issue for us, but we never got the chance to find the root cause.

@FlyGoat @iamthescatmann actually it is not directly about VT-d. It's about IOMMU. When you disable VT-d, it disables IOMMU.

Normal BIOSes usually have VT-d setting visible but IOMMU setting stays invisible. Only modded BIOSes (or manually changing IOMMU setting via 3rd tools) have IOMMU setting visible.

My laptop had same issue and solved it by disabling IOMMU with modded BIOS.