home.social

#unified-extensible-firmware-interface — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #unified-extensible-firmware-interface, aggregated by home.social.

fetched live
  1. I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

    Here is the message (reformatted to hopefully suit mastodon's boxes):
    [ 0.205100] apple-properties: device path parse error -19 at 0x14:
    00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
    00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
    00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
    00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
    00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
    00000050: 12 04 ..

    "-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

    I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

    It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

    #linux #UnifiedExtensibleFirmwareInterface

  2. I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

    Here is the message (reformatted to hopefully suit mastodon's boxes):
    [ 0.205100] apple-properties: device path parse error -19 at 0x14:
    00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
    00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
    00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
    00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
    00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
    00000050: 12 04 ..

    "-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

    I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

    It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

    #linux #UnifiedExtensibleFirmwareInterface

  3. I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

    Here is the message (reformatted to hopefully suit mastodon's boxes):
    [ 0.205100] apple-properties: device path parse error -19 at 0x14:
    00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
    00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
    00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
    00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
    00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
    00000050: 12 04 ..

    "-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

    I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

    It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

    #linux #UnifiedExtensibleFirmwareInterface

  4. Secure Boot is completely broken on 200+ models from 5 big device makers - Enlarge (credit: sasha85ru | Getty Imates)

    In 2012, an industr... - arstechnica.com/?p=2039140 #unifiedextensiblefirmwareinterface #keycompromise #cryptography #supplychain #secureboot #features #security #rootkits #biz#uefi

  5. Secure Boot is completely broken on 200+ models from 5 big device makers - Enlarge (credit: sasha85ru | Getty Imates)

    In 2012, an industr... - arstechnica.com/?p=2039140 #unifiedextensiblefirmwareinterface #keycompromise #cryptography #supplychain #secureboot #features #security #rootkits #biz#uefi

  6. Secure Boot is completely broken on 200+ models from 5 big device makers - Enlarge (credit: sasha85ru | Getty Imates)

    In 2012, an industr... - arstechnica.com/?p=2039140 #unifiedextensiblefirmwareinterface #keycompromise #cryptography #supplychain #secureboot #features #security #rootkits #biz#uefi

  7. One of the Internet’s most aggressive threats could take UEFI malware mainstream - Enlarge (credit: Getty Images)
    One of the Internet’s most aggressive threats has just gotten mean... - arstechnica.com/?p=1727276 #unifiedextensiblefirmwareinterface #bootkits #trickbot #malware #biz&it #tech #uefi

  8. New flaw neuters Secure Boot, but there’s no reason to panic. Here’s why - Enlarge (credit: Aurich Lawson / Getty Images)
    GRUB2, one of the world’s most-widely used program... more: arstechnica.com/?p=1695012 #unifiedextensiblefirmwareinterface #secureboot #boothole #bootkits #biz&it #tech #uefi