Re: [qubes-users] HCL report on a Lenova system

[Sven Semmler]

On 2/15/22 22:25, AmiR wrote:

I am on a NitroPad X230


Thank you for the clarification. I have updated your report [1] to reflect this 
fact, which also explains the versioning difference. Excellent outcome!

/Sven

[1] 
https://www.qubes-os.org/hcl/#nitrokey_nitropad-x230-2325pb3_i7-3520m_ivy-bridge_integrated-graphics-hd-4000

--
 public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/09cacdee-a9b5-8bab-bb41-3de0148fc4a0%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] HCL report on a Lenova system

[AmiR]

No, actually I did not touch it at all. I am on a NitroPad X230 and 
recently they have provided an updated firmware for Qubes 4.1 
(https://docs.nitrokey.com/nitropad/qubes/firmware-update-1.4.html#should-i-update-my-nitropad). 
However, I did not upgrade to this new one yet. I am planing to do so 
sometime next week.


On 2/16/22 01:24, Sven Semmler wrote:
your report states a BIOS version `Heads v1.3.1`. I just pulled and 
build the current head revision of the heads project and that version 
is `heads-v0.2.0-1150`.


Did you build and flash Heads yourself? Can you shed light on the 
version number? 


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ea69d4f4-dd10-5247-15ba-bd8415b5fa78%40gmail.com.

Re: [qubes-users] HCL report on a Lenova system

[Sven Semmler]

AmiR,

your report states a BIOS version `Heads v1.3.1`. I just pulled and build the 
current head revision of the heads project and that version is 
`heads-v0.2.0-1150`.

Did you build and flash Heads yourself? Can you shed light on the version 
number?

/Sven

--
 public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d941fbda-90b6-c505-43ad-34d26a739c33%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature

Aw: [EXT] Re: [qubes-users] Cannot boot 4.1.0 medium

[Ulrich Windl]

(Sorry for top-posting, but this web-frontend cannot quote properly.)


I guess the magic number count=5199888384 is different for 4.1.0 ;-)


Despite at first sight I'd say it doesn't look corrupted:
7g4x4a:/home/windl # blkid /dev/sdf
/dev/sdf: BLOCK_SIZE="2048" UUID="2022-02-03-10-41-48-00" 
LABEL="QUBES-R4-1-0-X86-64" TYPE="iso9660" PTUUID="35a8509b" PTTYPE="dos"
i7g4x4a:/home/windl # blkid /dev/sdf1
/dev/sdf1: BLOCK_SIZE="2048" UUID="2022-02-03-10-41-48-00" 
LABEL="QUBES-R4-1-0-X86-64" TYPE="iso9660" PTUUID="35a8509b" PTTYPE="dos" 
PARTUUID="35a8509b-01"
# blkid /dev/sdf2
/dev/sdf2: SEC_TYPE="msdos" LABEL_FATBOOT="ANACONDA" LABEL="ANACONDA" 
UUID="169B-DEBF" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="35a8509b-02"
# mount -r /dev/sdf2 /mnt
# ll /mnt
insgesamt 4
drwxr-xr-x 3 root root 2048  3. Feb 10:41 EFI
drwxr-xr-x 2 root root 2048  3. Feb 10:41 System Volume Information
# ll /mnt/EFI/
insgesamt 2
drwxr-xr-x 3 root root 2048  3. Feb 10:41 BOOT
# ll /mnt/EFI/BOOT/
insgesamt 1796
-rwxr-xr-x 1 root root 1835008  3. Feb 10:41 BOOTX64.EFI
drwxr-xr-x 2 root root2048  3. Feb 10:41 fonts
-rwxr-xr-x 1 root root1533  3. Feb 10:41 grub.cfg
# umount /mnt 
# mount -r /dev/sdf1 /mnt
# ll /mnt
insgesamt 206
-rw-r--r-- 1 root root 41  3. Feb 11:31 .discinfo
drwxr-xr-x 1 root root   2048  3. Feb 11:41 EFI
drwxr-xr-x 1 root root   2048  3. Feb 11:41 extrakernels
drwxr-xr-x 1 root root   2048  3. Feb 11:41 images
drwxr-xr-x 1 root root   4096  3. Feb 11:41 isolinux
drwxr-xr-x 1 root root   2048  3. Feb 11:41 LiveOS
drwxr-xr-x 1 root root 194560  3. Feb 11:24 Packages
drwxr-xr-x 1 root root   2048  3. Feb 11:24 repodata
-rw-r--r-- 1 root root868  3. Feb 11:41 .treeinfo

I'll try to investigate and report back. Unfortunately I don't have the 
original image here right now.

Ulrich


>>> Am 13.02.2022 um 10:04, in Nachricht <73C38467.AAF : 155 : 19119>, Tobias 
>>> Killer   schrieb:
Hi,

IMHO you should first check if the image on your USB stick is broken. See

https://github.com/QubesOS/qubes-issues/issues/7030#issuecomment-956398816

Regards,
Tobias

Am 12.02.22 um 20:15 schrieb Ulrich Windl:
> Hi!
>
>
> I downloaded and checked the Qubes OS 4.1.0 image and wrote it onto an USB 
> stick.
> When inserting the stick to boot (on a different computer), I'm offered UEFI 
> boot and normal boot by BIOS.
>
>
> "Nice, UEFI" I thought, but somehow that does not work (see attachment). 
> Well, I think UEFI boot should work for Qubes OS, too as Tails has a working 
> UEFI for quite some time now, and legacy boot is increasingly rarely 
> supported on new hardware (IMHO).
>
>
> OK, trying the other (compatibility) mode, boot also failed (see other 
> attachment).
>
>
> Now I wonder: Is my stick defective, did I have a write error, or is the 
> image defective?
>
>
> Regards,
> Ulrich
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/620C22E802A100047CEF%40gwsmtp.uni-regensburg.de.