I renamed “Setting up Debian sid on the Framework” to “Debian unstable (sid) on the Framework Laptop” aligning other distro threads on “Linux” category. I also wanted to emphasize this thread is for unstable (sid) branch but not for testing branch for now. Though it might be this thread could include testing branch in the future.
As a reference, to know 3 kind of branches: unstable (sid), testing, stable branches, the following documents are useful.
I updated this thread’s wiki adding “See also” section to add links to Debian testing and stable branches, and Debian based Linux threads for convenience.
any ideas on how to prevent BIOS updates from screwing with EFI boot? how does ubuntu work around this?
Run sudo grub-install --removable and you should always be able to boot back up even if the EFI boot entries have been removed.
I am running a backported Debian Bullseye and checked that the fingerprint is enabled in the BIOS. However Wenn running this command I receive the following. Is this due to me runnign Bullseye rather than sid? Or even that the packages installed seem to be 1.90.9-1?
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
According to posts in other threads, libfprint v1.92.0 or greater is needed.
Bullseye has v1.90 and sid has v1.94.
Running Debian unstable with KDE Plasma 5, I tried activating hibernation as described in the this thread. Unfortunately nothing happens when I try to go into hibernation via the plasma menu. I did disable secure boot (it simply says “disabled” in the field), and have tried to figure out corresponding logs in from dmesg -H below.
I am not really big on theses topics, so I cant tell if thats something framework particular or rather a general issue I have with debian.
[May15 20:26] PM: hibernation: hibernation entry
[ +0.000329] (NULL device *): firmware: direct-loading firmware i915/tgl_dmc_ver2_12.bin
[ +0.000207] (NULL device *): firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0.pnvm
[ +0.000387] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[ +0.000011] (NULL device *): firmware: direct-loading firmware regulatory.db
[ +0.000025] (NULL device *): firmware: direct-loading firmware intel/ibt-0041-0041.ddc
[ +0.000342] (NULL device *): firmware: direct-loading firmware intel/ibt-0041-0041.sfi
[ +0.000035] (NULL device *): firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0-66.ucode
[ +0.010187] Filesystems sync: 0.010 seconds
[ +0.000004] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ +0.001937] OOM killer disabled.
[ +0.000108] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ +0.000002] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
[ +0.000002] PM: hibernation: Marking nosave pages: [mem 0x39f99000-0x3a898fff]
[ +0.000017] PM: hibernation: Marking nosave pages: [mem 0x3f93f000-0x3f941fff]
[ +0.000001] PM: hibernation: Marking nosave pages: [mem 0x3f943000-0x3f991fff]
[ +0.000001] PM: hibernation: Marking nosave pages: [mem 0x3fbaa000-0x3fbaafff]
[ +0.000001] PM: hibernation: Marking nosave pages: [mem 0x434af000-0x45bfefff]
[ +0.000072] PM: hibernation: Marking nosave pages: [mem 0x45c00000-0xffffffff]
[ +0.001070] PM: hibernation: Basic memory bitmaps created
[ +0.000842] PM: hibernation: Preallocating image memory
[ +2.395960] PM: hibernation: Allocated 1573562 pages for snapshot
[ +0.000004] PM: hibernation: Allocated 6294248 kbytes in 2.39 seconds (2633.57 MB/s)
[ +0.000002] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ +0.001792] printk: Suspending console(s) (use no_console_suspend to debug)
[ +1.052559] ACPI: EC: interrupt blocked
[ +0.006391] ACPI: PM: Preparing to enter system sleep state S4
[ +0.014682] ACPI: EC: event blocked
[ +0.000001] ACPI: EC: EC stopped
[ +0.000001] ACPI: PM: Saving platform NVS memory
[ +0.005047] Disabling non-boot CPUs ...
[ +0.001715] smpboot: CPU 1 is now offline
[ +0.002525] smpboot: CPU 2 is now offline
[ +0.002014] smpboot: CPU 3 is now offline
[ +0.002331] smpboot: CPU 4 is now offline
[ +0.002407] smpboot: CPU 5 is now offline
[ +0.001458] smpboot: CPU 6 is now offline
[ +0.001684] smpboot: CPU 7 is now offline
[ +0.005694] PM: hibernation: Creating image:
[ +0.121866] PM: hibernation: Need to copy 1567192 pages
[ +0.000003] PM: hibernation: Normal pages needed: 1567192 + 1024, available pages: 2571242
[ +1.073339] PM: hibernation: Image created (1567192 pages copied)
[ -1.194924] ACPI: PM: Restoring platform NVS memory
[ +0.001168] ACPI: EC: EC started
[ +0.001446] Enabling non-boot CPUs ...
[ +0.000041] x86: Booting SMP configuration:
[ +0.000000] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ +0.001081] CPU1 is up
[ +0.000025] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ +0.001226] CPU2 is up
[ +0.000019] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ +0.001232] CPU3 is up
[ +0.000020] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ +0.001280] CPU4 is up
[ +0.000023] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ +0.001098] CPU5 is up
[ +0.000020] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ +0.001344] CPU6 is up
[ +0.000021] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ +0.001329] CPU7 is up
[ +0.004189] ACPI: PM: Waking up from system sleep state S4
[ +0.007443] ACPI: EC: interrupt unblocked
[ +0.040500] ACPI: EC: event unblocked
[ +0.029360] nvme nvme0: 8/0/0 default/read/poll queues
[ +0.335517] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ +0.000218] PM: Cannot get swap writer
[ +0.134720] PM: hibernation: Basic memory bitmaps freed
[ +0.000004] OOM killer enabled.
[ +0.000000] Restarting tasks ... done.
[ +0.007185] thermal thermal_zone5: failed to read out thermal zone (-61)
[ +0.002829] PM: hibernation: hibernation exit
This seems like the issue, though I’ve never run into it…
From earlier lines, it looks like you have enough swap (based on the number of pages it’s trying to write and the number of pages that are available).
Question: Are you using a swap file or a swap partition?
For reference, here’s a hibernation log from my Framework:
[ +0.132402] PM: hibernation: hibernation entry
[ +0.004448] Filesystems sync: 0.004 seconds
[ +0.000006] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ +0.002113] OOM killer disabled.
[ +0.000367] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ +0.000004] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
[ +0.000004] PM: hibernation: Marking nosave pages: [mem 0x39f99000-0x3a898fff]
[ +0.000044] PM: hibernation: Marking nosave pages: [mem 0x3f90d000-0x3f95bfff]
[ +0.000003] PM: hibernation: Marking nosave pages: [mem 0x3fbaa000-0x3fbaafff]
[ +0.000001] PM: hibernation: Marking nosave pages: [mem 0x434af000-0x45bfefff]
[ +0.000184] PM: hibernation: Marking nosave pages: [mem 0x45c00000-0xffffffff]
[ +0.002700] PM: hibernation: Basic memory bitmaps created
[ +0.001522] PM: hibernation: Preallocating image memory
[ +1.006671] PM: hibernation: Allocated 1450975 pages for snapshot
[ +0.000004] PM: hibernation: Allocated 5803900 kbytes in 1.00 seconds (5803.90 MB/s)
[ +0.000003] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ +0.001798] printk: Suspending console(s) (use no_console_suspend to debug)
[ +0.000494] wlp170s0: deauthenticating from 7c:10:c9:6b:81:e8 by local choice (Reason: 3=DEAUTH_LEAVING)
[ +0.597161] ACPI: EC: interrupt blocked
[ +0.007572] ACPI: PM: Preparing to enter system sleep state S4
[ +0.018406] ACPI: EC: event blocked
[ +0.000002] ACPI: EC: EC stopped
[ +0.000001] ACPI: PM: Saving platform NVS memory
[ +0.009953] Disabling non-boot CPUs ...
[ +0.002030] smpboot: CPU 1 is now offline
[ +0.002670] smpboot: CPU 2 is now offline
[ +0.002982] smpboot: CPU 3 is now offline
[ +0.003222] smpboot: CPU 4 is now offline
[ +0.004458] smpboot: CPU 5 is now offline
[ +0.001958] smpboot: CPU 6 is now offline
[ +0.002095] smpboot: CPU 7 is now offline
[ +0.006374] PM: hibernation: Creating image:
[ +0.375224] PM: hibernation: Need to copy 1443131 pages
[ +0.000004] PM: hibernation: Normal pages needed: 1443131 + 1024, available pages: 6889360
[ -0.374999] ACPI: PM: Restoring platform NVS memory
[ +0.000891] ACPI: EC: EC started
[ +0.001449] Enabling non-boot CPUs ...
[ +0.000041] x86: Booting SMP configuration:
[ +0.000001] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ +0.001092] CPU1 is up
[ +0.000029] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ +0.001230] CPU2 is up
[ +0.000022] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ +0.001248] CPU3 is up
[ +0.000021] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ +0.001411] CPU4 is up
[ +0.000024] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ +0.001375] CPU5 is up
[ +0.000021] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ +0.001363] CPU6 is up
[ +0.000022] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ +0.001277] CPU7 is up
[ +0.006251] ACPI: PM: Waking up from system sleep state S4
[ +0.007197] ACPI: EC: interrupt unblocked
[ +0.226922] ACPI: EC: event unblocked
[ +0.000183] usb usb1: root hub lost power or was reset
[ +0.000004] usb usb2: root hub lost power or was reset
[ +0.000024] usb usb3: root hub lost power or was reset
[ +0.000002] usb usb4: root hub lost power or was reset
[ +0.410959] usb 3-10: reset full-speed USB device number 4 using xhci_hcd
[ +0.160451] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ +0.000303] PM: hibernation: Basic memory bitmaps freed
[ +0.000010] OOM killer enabled.
[ +0.000001] Restarting tasks ... done.
[ +0.002615] Bluetooth: hci0: Device revision is 0
[ +0.000008] Bluetooth: hci0: Secure boot is enabled
[ +0.000002] Bluetooth: hci0: OTP lock is enabled
[ +0.000002] Bluetooth: hci0: API lock is enabled
[ +0.000003] Bluetooth: hci0: Debug lock is disabled
[ +0.000002] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ +0.000005] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ +0.000009] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ +0.000259] Bluetooth: hci0: Boot Address: 0x100800
[ +0.000005] Bluetooth: hci0: Firmware Version: 86-28.21
[ +0.015286] PM: hibernation: hibernation exit
Well, cheers for your reply.
I dont know if this explains the issue you highlighted, but according to lsblk I did myself a favor and somehow created a swap partition with about 1Gb size, which seems quite little.
In addition, I encrypted my ssd, which might also lead to access issues.
root@ARG ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 488M 0 part /boot
└─nvme0n1p3 259:3 0 930.5G 0 part
└─nvme0n1p3_crypt 254:0 0 930.5G 0 crypt
├─ARG--vg-root 254:1 0 929.5G 0 lvm /
└─ARG--vg-swap_1 254:2 0 976M 0 lvm [SWAP]
Originally I wanted to see, whether hibernation might save myself some battery when leaving the framework on standby and unplugged for a day or two. The “enhanced” sleep option above, doesnt really provide sufficient savings. Additionally it sometimes doesnt go/stay in “sleep” at all, so I always have to double check.
So I might have to reinstall my system, if I want to check for better standby energy consumption with hibernation.
You should be able to boot to a LiveCD, shrink the root volume, and then grow the swap volume. Your setup looks extremely similar to mine:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 487M 0 part /boot/efi
├─nvme0n1p2 259:2 0 488M 0 part /boot
└─nvme0n1p3 259:3 0 231.9G 0 part
└─nvme0n1p3_crypt 254:0 0 231.9G 0 crypt
├─Crypto-Root 254:1 0 93.1G 0 lvm /
├─Crypto-Home 254:2 0 111.8G 0 lvm /home
└─Crypto-Swap 254:3 0 14.9G 0 lvm [SWAP]
Oh, also: You’re using a swap partition, which makes the process slightly easier (apparently with swap files you have to know the offset and stuff…a bit of a headache).
Ah cheers. I thought using a swap partition would be harder to increase. But in this case I will give this a go in a couple of days. Thanks again for your help.
Quick follow up @Chiraag_Nataraj:
Do you experience “random” logouts (dont know what kind of desktop env your using) when pressing fn with any function keys? E.g. I have, very randomly, noticed that when toggling between play/pause (f5), the login screen appears, after unlocking a black screen saying framework and a rotating gear below appears and every program I was working on seconds ago is closed etc.
Additionaly some functions and settings seem to be reset/not working. I.e. wallpaper and screensaver are back to default, meta-key (binding to application launcher) doesnt respond, my second screen has a weird resolution, windows cannot be resized or closed at all, the taskbar doesnt show (auto hide enabled).
I wanted to check if this might be due to the debian branch before opening another thread.
Nope, not at all. That’s probably your Desktop Environment crashing (potentially your Wayland compositor or window manager, something low-level like that) which causes a full log-out. As for why your compositor or window manager would be crashing when you press a function key? Absolutely no idea!
Oh, I meant that it’s easier to get hibernation working with a swap partition (rather than a swap file). A swap file is easier to resize than a swap partition, actually, but resizing the swap partition isn’t super hard either.
As I said, just boot this Debian ISO to a live session, start the partition manager (probably gparted) and resize your partitions. You’ll want to shrink your ARG--vg-root first before expanding your ARG-vg-swap_1. You’re actually lucky in this case that you’re moving the beginning of your swap partition rather than partitions with data (such as /), since it’s technically more dangerous than extending the end of the partition. Either way, though, you should be fine!
Good luck and remember to have a current backup before doing this (as always!) 
Thanks for this guide! I couldn’t find a link to the Debian Bookworm installer at all and just assumed that it was still under development and wasn’t released yet. Almost gave up! Already had Ubuntu 22.04 downloaded and then stumbled upon this guide to get me back on Debian Sid!
Edit1: This post probably doesnt really belong here in full length.
However in terms of the topic of this thread Id like to point out, that the installation of the build linked in the first post here for me yields missing RAID and LVM moduls while detecting the disk.
Edit2: Further details might be found on stackexchange.
Hello again. Im a bit in a pickle. My system broke down as of yesterday. (KDE had trouble staying alive, as well as firefox or plenty of other programs after login). Nothing really worked anymore, I couldnt even determine if my RAM is broken or another package update caused this, always received alerts about core dump…Anyway I always have a fresh update and decided to start with a fresh install.
But I cannot not make anything work. I tried the weekly non-free firmware build mentioned above, but before partitioning in the installer I get an error about
Software RAID not available
The current kernel doesnt seem to support software RAID(MD) devices. This should be solved by loading the necessary modules.
followed by this message
Logical Volume Manager not available
The current kernel doesnt support the logical Volume Manager. You may need to load the lvm-mod module.
Eventually I fail while partitioning. I should mention I couldnt set up network access through wifi or ethernet, because neither gets recognised.
This is weird, I guess, however I tried multiple other .iso (current deb11.5+live+nonfree, different weekly or daily builds as netinst as well as the bookworm-alpha version. Neither worked out in the end.
However, unfortunately I lost track which weekly/daily-build got stuck/caused an error where, but in general the bookworm-alpha- version worked best, but often got either stuck while installing software, failed this one or the following grub installation.
I never really go stuck on the same software installation or configuration or grub installation subprocess, but eventually it never went through.
Does anyone have an idea, why I fail with so many different builds at so many different stages?
Im sorry if that sounds confusing and is hard to follow (i tried a lot and very often and might have missed some sleep)
For now I reactivated my old XPS but I really would like to figure out why this is happening or if this might be a hardware issue.
I try to keep track of what exactly went wrong where and when if I try anything else…
this seem like a request that should be split apart in a different topic, IMHO.
I agree, this post wasnt very thought through and more out of desperation. I went ahead and created a question with more details on stackexchange.
If anyone installed debian recently successfully, I would be happy to know what build they used anyhow.
do you mind linking to it from here?
On 2022-10-18 18:42:45, Pratched via Framework Community wrote:
I agree, this post wasnt very thought through and more out of desperation. I went ahead and created a question with more details on stackexchange.
Care to link there?
If anyone installed debian recently successfully, I would be happy to know what build they used anyhow.
I used the Debian alpha installer from Debian -- Debian-Installer
you’ll probably need one of the builds with non-free firmware: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/