faq4.html multibooting grub
I believe the FAQ4 section on multibooting is placing all Grub2 based distributions into the same bucket incorrectly. Debian and its derivatives utilize a different path to BOOTX64.EFI and are amendable to multibooting with OpenBSD. See attached patch for details. -- J. Scott Heppler --- faq4.html Wed Jan 26 10:17:32 2022 +++ faq4_new.html Wed Jan 26 10:42:04 2022 @@ -572,8 +572,15 @@ https://www.rodsbooks.com/refind/;>rEFInd is reported to usually work. -https://www.gnu.org/software/grub/;>GRUB is reported to usually -fail. +https://www.gnu.org/software/grub/;>GRUB has issues when +multibooting Fedora, Redhat, and their derivatives. +OpenBSD uses the same /boot/efi/BOOT/EFI/BOOTX64.EFI location as the previosly +listed Linux distributions and will overwrite it on installation. It is +possible to move BOOTX64.EFI to another location but this causes OpenBSD's +kernel relinking to fail. +Debian, and derivatives, utilize /boot/efi/EFI/debian/grubx64.efi which avoids +the conflict. + In either case, you are completely on your own. Windows
Re: flashrom fails w/ LIBUSB_ERROR_TIMEOUT
On 2022/01/26 20:19, rgc wrote:
> On Tue, Jan 25, 2022 at 09:49:05PM +0900, rgc wrote:
> > misc@
> >
> > got a CH341A SPI programmer.
> > works on Linux.
> > anybody got it to work with 70-current? or previous?
> >
> >
> > caveat from /usr/local/share/doc/pkg-readmes/flashrom:
> > -
> > flashrom also supports some external programming devices via USB; in
> > those cases it can be run from a normal boot.
> >
> > so flashrom should just work (tm) right!?
>
> i just found the time to try flashrom in single user mode ("boot -s") and
> i get the same error ... still timeout.
Single user mode for flashrom is to provide raw system access for direct
programming of the motherboard that you are running on, it won't help
USB.
> > glitch# flashrom -p ch341a_spi -r top.rom
> > flashrom v1.2 on OpenBSD 7.0 (amd64)
> > flashrom is free software, get the source code at https://flashrom.org
> >
> > Using clock_gettime for delay loops (clk_id: 3, resolution: 1ns).
> > Found Winbond flash chip "W25Q32.V" (4096 kB, SPI) on ch341a_spi.
> > Reading flash... ch341a_spi_spi_send_command: failed to submit OUT
> > transfer: LIBUSB_ERROR_TIMEOUT
> > ch341a_spi_spi_send_command: Failed to write 4265 bytes
> > Read operation failed!
> > FAILED.
Looking at the ch341a_spi code in flashrom, it looks like it uses bulk
async transfers; these are known *not* to work on OpenBSD with libusb.
(In general USB support, especially to programs running in userland, is
not brilliant on OpenBSD; you're probably better off with a little Linux
box for those.)
Re: flashrom fails w/ LIBUSB_ERROR_TIMEOUT
On Tue, Jan 25, 2022 at 09:49:05PM +0900, rgc wrote: > misc@ > > got a CH341A SPI programmer. > works on Linux. > anybody got it to work with 70-current? or previous? > i am not in a position to REALLY help you, but i (and others) can attest to the fact that the flashrom program works to some extent... ie: we have used it to dump/read and even write firmware onto pc-engines APU boards... since i used-it recently i can confirm that it works in current-obsd-70... you did not provide a DMESG for the complete system and in particular you did not exactly describe your situation well... are you trying to read from a chip plugged into the actual dip-holder ? or from the clip-extension ? here are two links which might be helpful: 1 - this link warns that you might have a voltage-issue with your system... https://www.blackhillsinfosec.com/dumping-firmware-with-the-ch341a-programmer/ 2 - this link cautions that you might have trouble with the clip-extension positioning... https://www.win-raid.com/t4287f16-GUIDE-The-Beginners-Guide-to-Using-a-CH-A-SPI-Programmer-Flasher-With-Pictures.html presumably, if the system worked in linux - you have solved both of those issues... can you confirm that the setup that YOU are using has worked for YOU in linux ? and, like anything else - the source-code is available if you really want to sort it out... just fyi - i will enclose my most recent log of a successful read (sans dmesg)... hth... $ cat backuplog01.1 flashrom v1.2 on OpenBSD 7.0 (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 3, resolution: 1ns). coreboot table found at 0xcfeba000. Found chipset "AMD FCH". Enabling flash write... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0xff80. Reading flash... done.
