home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   LINUX      Torvalds farts & fans know what he ate      8,232 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 7,548 of 8,232   
   Kai Richter to Gerrit Kuehn   
   uefi   
   27 May 22 13:13:52   
   
   REPLY: 2:240/12 6251c1b6   
   MSGID: 2:240/77 6290c50c   
   CHRS: LATIN-1 2   
   TID: hpt/lnx 1.4.0-sta 09-04-05   
   Hello Gerrit!   
      
   24 May 22, Gerrit Kuehn wrote to Kai Richter:   
      
    KR>> The result is that the menu to select the starting OS is moved from   
    KR>> the disk to the BIOS.   
      
    GK> I talked about cases where something is broken and your system doesn't   
    GK> boot (maybe not even the bootmanager comes up). With MBR this means   
    GK> reconfiguring BIOS boot order,   
      
   You have to enter the uefi shell by the same way: Dive into the BIOS and   
   select it. If the system doesn't boot the boot override function is essential.   
      
    GK> probably getting some USB media to boot a rescue system from it etc.   
    GK> With the built-in UEFI shell, you can already check your partitions   
    GK> and even select what to boot   
      
   I couldn't. The, no, my uefi shell is not self explaining. I failed to start a   
   running system from the uefi shell. Well, ok, my fault.   
      
    GK> without having to reconfigure anything or to provide a rescue system   
    GK> on USB. In many cases I was able to manually boot the failed system   
    GK> with this and use the system itself then to fix booting.   
      
    GK> Some manufacturers provide firmware and bios update tools on efi   
    GK> meanwhile. In that case, you can just drop the new firmware and the   
    GK> upgrade tool on a USB stick and use UEFI-shell to run it from there.   
      
   So i have to wait until my BIOS company updates it's tools and i can save them   
   within the BIOS. Back in the old days i had my OS/2 bootmanager and rescue   
   system on a small partition.   
      
    GK> In the MBR-days you would have needed to have a MSDOS-system on the   
    GK> USB stick in addition   
      
   Why DOS? We need to kickstart the boot sequence.   
   USB stick in addition? I see an EFI partition on my disk in addition.   
      
   I've done 50% reading of an efi turorial now and it does remind me to grub.   
      
    GK> (and hope that the manufacturer would still provide a DOS-based   
    GK> update tool that is able to run on your newly bought server or   
    GK> workstation).   
      
   I'v seen an EFI editor which my bios doesn't have. Now i've to check if anyone   
   provides this efi software. The default path in my uefi shell does have   
   something like fs[01234]:/efi/tools. The design concept is to add tools from a   
   maintenance/rescue partition like we did before from the usb stick or from a   
   /boot partition.   
      
   Maybe the only thing i need is to get used to it...   
      
   Regards   
      
   Kai   
      
   --- GoldED+/LNX 1.1.4.7   
    * Origin:  Monobox  (2:240/77)   
   SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/81 106/201 114/709   
   SEEN-BY: 120/340 123/131 124/5016 129/305 330 331 153/250 757 7715   
   SEEN-BY: 154/10 203/0 214/22 218/0 1 109 501 650 700 810 830 840 850   
   SEEN-BY: 218/860 870 880 220/70 221/0 6 226/17 30 227/114 229/110   
   SEEN-BY: 229/111 112 113 206 317 400 424 426 428 452 470 550 616 664   
   SEEN-BY: 229/700 240/77 420 5138 5411 5824 5832 5853 266/512 267/800   
   SEEN-BY: 280/464 5003 282/1038 292/854 8125 301/1 310/31 317/3 320/219   
   SEEN-BY: 322/757 341/234 342/200 396/45 423/120 460/58 633/280 712/848   
   SEEN-BY: 770/1 100 330 340 772/210 220 230 2432/390 2452/250 2454/119   
   SEEN-BY: 5020/545   
   PATH: 240/77 5832 280/464 770/1 218/840 700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca