This is absolutely not true. Sometimes the formatting utility can mess things up.
I really don’t know, since I usually use dd to format my USB sticks and it’s never failed. Once you boot into the installer and get to the firmware step, can you change to a different TTY (e.g. type Ctrl+Alt+F2), press enter to activate the console, and run dmesg to see if there are any errors. Further, you can try dpkg -i /firmware/firmware-iwlwifi_20210818-1_all.deb to manually load it.
I want to emphasize that something is wrong here, since I absolutely did not have to do any of this and it all worked seamlessly during install. Maybe it’s Rufus. Maybe your ISO download is corrupted (you can finding the sha256 or sha512 checksums and comparing against the ones on the website).
I recommend you amend your original post to inform users that they should write the image to the USB drive in “DD Image mode.”
In Rufus, after loading up the ISO image and clicking START, one of the popups that will appear right before it begins to write data to the drive is “ISOHybrid image detected”. It allows the user to select if they want to write the image in “ISO Image (file copy) mode” (which they recommend) or in “DD Image (disk image) mode.” The ISO Image mode allows for full access to the drive after writing to it whereas the DD Image mode does not.
I honestly did not think this choice would make any difference whatsoever until you mentioned that you use something called dd to format your USB drives.
My apologies if I came across as rude. It’s been a long day.
Hmm, the only reference I found to that error is here, but it makes me wonder if you tried setting up fingerprint authentication on Windows before installing Linux?
Nope. My very first attempts with this Framework laptop were with Ubuntu. Regardless, you also own a Framework laptop, so you can verify that there is no “Predesktop Authentication” setting in BIOS.
I know, but people have reported issues with registering fingerprints under Windows and then installing Linux, hence I asked.
Further, this thread mentions that setting up the fingerprint reader in Windows (even just installing the driver) might have locked the device to Windows, and there’s a link to another post on there that explains how to fix it. Specifically, try this appimage.
In the other thread, you mentioned that you were going to setup Windows, so I’m wondering if you actually followed through on that. Regardless, something here has to do with the fact that you’ve reinstalled the OS multiple times (and maybe setup your fingerprints on a previous install).
Does the fingerprint device itself have its own, separate non-volatile memory where it stores the fingerprints that have been scanned? If so, I wonder if the times when I was able to successfully scan fingerprints (way back during my first Ubuntu installation) have taken up those spots in its memory and now I need to run the scripts or whatever in the other thread to erase them from memory and start from a blank slate.
Yes, it does. I believe that you’re on the right track regarding running the python script to clear out any existing prints, then trying again to enroll a new one. Best of luck!
By the way, I made this a wiki post so that others can edit with their experience (or clarify things). @Christopher_McGee, feel free to add parts specific to your experience if you wish
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.
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
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
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).
