doing crazy things with proxmox - today: try ressource constrained device :)

Hi, could someone please share the bios with uefi? Unfortunately I have an old version. Thanks
 
Azhrarn said:
Would it be possible to get the procedure as well. I already got to the virtualization done on multiple M340C using the H2ouve procedure.
BUT this Fifth one is running a really old BIOS and seems to recognize my 8GB SODIMM as 4GB...
I am guessing this is just old BIOS version related. So I need to download a newer BIOS....
Click to expand...
Hi, I can't seem to find any sensible explanation as to what changes I need to apply to get the H2OUVE method done, do you maybe have a short explanation or guide? Thanks in advance.
 
For information about a somewhat different procedure to "fix" the Bios look here :
https://web.archive.org/web/20230226162054/http://www.dbse.de/app.js/document?doc=igel_M340C_bios

Denis uses efivar for this:

Warning​

At your own risk! No waranty! You may brick your device! Animals can be harmed!

Patching the BIOS settings with linux​

  1. Install efivar and some kind of a hexeditor (recommended: hexedit). On Arch-Linux I installed:
    pacman -S efivar hexedit

    It should be possible to use the Arch-Linux install media without the need to install Arch-Linux.
    With grmli64-full 2021.07 (live media) you need internet access do this:
    apt update
    apt install efivar

  2. Boot system in UEFI-Mode to get access to UEFI vars (location: /sys/firmware/efi/efivars)
  3. Change to efivars virtual filesystem (should be mounted, if booted in UEFI mode)
    cd /sys/firmware/efi/efivars

  4. The complete BIOS-setup is stored in this blob/var Setup-a04a27f4-df00-4d42-b552-39511302113d, dump it
    cat Setup-a04a27f4-df00-4d42-b552-39511302113d > /tmp/setup_dumped.bin

  5. Watch out: the first 4 bytes dumped by this method are containing the UUID for the var. Remove this with dd:
    dd if=/tmp/setup_dumped.bin of=~/setup.bin bs=1 skip=4

    The size of the file should now 631 bytes, please check!
  6. Now the plain blob with settings are in ~/setup.bin make a copy..
    cp ~/setup.bin ~/setup_mod.bin

  7. Modify the blob with tools like hexedit (press CTRL-X to exit, confirm to save the changes)
    hexedit ~/setup_mod.bin

    These values were changed:
    • on address 00e0 from 00 into 01
    • on address 0149 from 01 into 00
    • This is a diff between the files:
    --- /mnt/igel/efivar_setup.txt 2022-06-02 12:25:04.000000000 +0000
    +++ /mnt/igel/efivar_setup_mod.txt 2022-06-02 12:25:56.000000000 +0000
    @@ -19,13 +19,13 @@
    000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000000d0 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 01 |................|
    -000000e0 00 00 00 00 00 00 00 00 00 00 00 01 01 00 00 00 |................|
    +000000e0 00 00 00 00 00 00 00 00 00 00 00 01 01 00 01 00 |................|
    000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 |................|
    00000100 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000130 00 00 00 00 00 00 00 00 00 00 01 00 00 00 01 01 |................|
    -00000140 01 01 01 00 00 00 00 00 00 01 00 02 03 02 00 02 |................|
    +00000140 01 01 01 00 00 00 00 00 00 00 00 02 03 02 00 02 |................|
    00000150 00 02 03 00 00 00 01 00 00 00 04 01 00 00 04 01 |................|
    00000160 00 00 04 00 00 00 04 00 00 00 00 00 00 00 00 00 |................|
    00000170 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 80 |................|

    After modifications in hexedit:
    modification applied
  8. Make the efivar writable
    chattr -i Setup-a04a27f4-df00-4d42-b552-39511302113d

  9. write the modified blob to the efivar with the efivar tool, remind the slighly changed name of the variable due to efivars requirements
    efivar -w -n a04a27f4-df00-4d42-b552-39511302113d-Setup -f ~/setup_mod.bin

  10. Verify the last step, only two values should be altered
    efivar -n a04a27f4-df00-4d42-b552-39511302113d-Setup

    If you messed up things here, you can write your unmodified setup.bin with the efivar-cmd:
    efivar -w -n a04a27f4-df00-4d42-b552-39511302113d-Setup -f ~/setup.bin
 
  • Like
Reactions: RolandK
Hello, i have
RolandK said:
i just managed

- to update my igel m340c bios for being capable of uefi boot (which is required to hack the bios to enable svm/vmx) via dumping and copying the bios from another m340c with more recent bios
- to install proxmox 7.2 with zfs/zstd compression onto that (4 gb msata ssd, 2 gb ram)
- to downsize proxmox memory requirements a little bit
- to install a debian 11 vm and have it up and running with ssh
- to still have free space of 1gb

think that's the most crazy thing i ever did with proxmox or some thin client so far

View attachment 42710

what no-sense/crazy things do you do with proxmox ?
Click to expand...
Hello,
RolandK said:
i just managed

- to update my igel m340c bios for being capable of uefi boot (which is required to hack the bios to enable svm/vmx) via dumping and copying the bios from another m340c with more recent bios
- to install proxmox 7.2 with zfs/zstd compression onto that (4 gb msata ssd, 2 gb ram)
- to downsize proxmox memory requirements a little bit
- to install a debian 11 vm and have it up and running with ssh
- to still have free space of 1gb

think that's the most crazy thing i ever did with proxmox or some thin client so far

View attachment 42710

what no-sense/crazy things do you do with proxmox ?
Click to expand...

Hello, i need the Bios File.....
 
Hello! Dear forum members, could you share the BIOS file for Igel M340C with hardware visualization? Thank you!
 
You must log in or register to reply here.
Top Bottom