Framework 13 pro cannot see 1TB Gen2 expansion card in bios boot list

Community Support
,
1

I have just received my framework 13 pro and am very pleased with it. I want to move over to linux so have ubuntu installed on the internal drive. However I still need to access one or two windows programs from time to time so have installed windows to go using rufus on the expansion card (1TB gen2). No matter what I do it is not recognised in the BIOS boot menu until I pull the expansion card out and then re-insert while in the BIOS menu. After it is re-inserted it appears in the list and then I can boot into windows without a problem. Things I have tried without success:

  1. Turned off secure boot
  2. Added the windows EFI hashes to the BIOS database
  3. Tried in every port

Am I doing something wrong? I really want to keep the expansion card in the computer and then just boot from BIOS when needed but having to take it out and re-insert is a pain. Is there any way I can fix this (maybe a shortcut key to refresh the usb list or something).

2

What’s the make and model of the expansion card that you’re plugging in?

When you say tried in every port:

Are you plugging it in to a USB C port or USB A port?

And you’ve used this USB A/C port in every location on the laptop?

Here’s part of what good ole google AI Overview said try (only do one at a time).

Screenshot_20260830_112042_Chrome
Screenshot_20260830_112042_Chrome1080×3118 352 KB

3

Its a framework 1TB gen 2 expansion card.
I have tried turning off quick boot in the BIOS but still does not work
The framework 13 pro only has the four usb-c/thunderbolt ports
As far as I know the BIOS does not have any legacy USB support but booting from USB is enabled.
No idea what XHCI support is - Can’t find anything about that in the BIOS

4

If it works after replugging, maybe it’s just not registering quick enough when the devices were enumerated. Did you try setting a “Timeout” (in the configuration utility under “Boot”) of maybe 2 seconds? I tried booting my 13 Pro with a usb key attached and it shows it when it was plugged in before turning on, an expansion card should work the same way. Is it also missing from the “Boot from file” menu? Just to rule out it’s not detecting the bootability of the expasion card.

5

Used a 2 second timeout but no difference.

It is missing from the “Boot from file” menu until I unplug and re-insert.

I also believe it’s not registered when BIOS does it’s enumeration. That why I was wondering if there is any keyboard shortcut that I can press to do the usb enumeration

6

Are you using the Intel or amd model of the 13 Pro?

What else do you have plugged in to the other expansion card slots? I.e. what expansion cards and what (if anything) do you have plugged into them?

As a test:

Power down. Unplug from Power Supply if connected.

Remove all connected devices.

Remove all expansion cards.

Only plug in the storage expansion card to the top left (the one nearest the hinge wirh the laptop facing you).

Leave all the other 3 expansion slots empty with no expansion card or devices plugged in.

Now boot to bios and check if it shows.

7

I’m having the exact same issue. Boots fine if you unplug and plug it back in. Warm boot and cold boot have the same result. Regular USB drives work fine (3.2 and 4).

I think there’s something off about the 1tb 2nd gen expansion drive firmware.

InteL X9 388H

8

Intel X7 358H

No difference - not seen until I unplug/re-plug

9

That’s interesting. It’s good to know I’m not alone :slightly_smiling_face:

10

Thinking that a support ticket will need to be lodged with Framework: https://frame.work/au/en/support

@Framework

11

Its already done :slightly_smiling_face:

I’ll update when I learn anything new

12

Support didn’t have much to say other than “maybe wait for new firmware” on my end. I personally don’t think the hardware is faulty. I think something in the way the USB firmware presents itself causes it not to initialize during preboot.

I have a framework desktop I will plug this into this weekend and see if the behavior changes.

13

It could be something with how it enumerates itself to the BIOS that is causing it not to show up correctly. One of the devs with experience in low level work can probably explain this better.

They are probably right in that it is going to take a firmware update to resolve the issue.

14

I’ve tested the expansion card on my 13th gen framework 13 and it works.

15

Well that’s interesting.

It certainly points to the issue being with the Framework 13 Pro bios. A conflict or something.

I’m assuming you’ve let framework know this?

16

I have a support ticket with them at the moment.

I have also created a rufus boot disk on one of my old USB-A sticks and that works correctly in the Pro so it must simply be some conflict between the Pro’s BIOS and the expansion card