SeaBIOS

seabios@seabios.org

3783 discussions

SecureDrive
by Аладышев Константин 17 May '18

17 May '18

I'm having problems with USB boot from Transcend JetFlash 620 drive 32GB. SeaBIOS doesn't see it as boot device. I suppose the problem is in SecureDrive technology that is used on this device. I tried to remove it with "CD-ROM Remover_v1.0.0.3" tool that I've found. It removed CD partition from OS, but SeaBIOS still can't see flash drive as boot device. Does someone know how to solve this issue? Best Regards, Aladyshev Konstantin

1 0

[PATCH] Enable shell-like * globing in bootorder entries
by Ian Kelling 16 May '18

16 May '18

Signed-off-by: Ian Kelling <ian(a)iankelling.org> --- src/boot.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/boot.c b/src/boot.c index ff705fd..ca64595 100644 --- a/src/boot.c +++ b/src/boot.c @@ -91,14 +91,14 @@ glob_prefix(const char *glob, const char *str) } } -// Search the bootorder list for the given glob pattern. +// Search the bootorder glob list for the given device description static int -find_prio(const char *glob) +find_prio(const char *desc) { - dprintf(1, "Searching bootorder for: %s\n", glob); + dprintf(1, "Searching bootorder for: %s\n", desc); int i; for (i = 0; i < BootorderCount; i++) - if (glob_prefix(glob, Bootorder[i])) + if (glob_prefix(Bootorder[i], desc)) return i+1; return -1; } -- 2.7.4

3 5

Re: [SeaBIOS] Librem 15v3 hangs at Booting from Hard Disk...
by Youness Alaoui 16 May '18

16 May '18

On Wed, May 9, 2018 at 9:14 PM, Philip C. <pchampon(a)gmail.com> wrote: > Hello everyone! > > I've been having some issues with a laptop recently. My Librem 15v3 was > bouncing along, until one day I ran into an apt-get upgrade issue. I > attempted to fix the affected script by pointing it to the base directory > busybox lived. The upgrade completed without any apparent issue. This is clearly totally unrelated to SeaBIOS, and it looks like an linux/grub installation problem. > > But, now no matter what I do, unattended boots hang on > > SeaBIOS (version rel-1.11.0-0-g63451fc) > Booting from Hard Disk... > _ If you see nothing after that, then that probably means that SeaBIOS executed whatever was on the drive's boot sector and that failed to do anything, so grub crashed or there was no grub in the first place, or it was misconfigured and it stopped instead of showing some error message, etc.. whatever the issue is, it looks like it's not related to SeaBIOS. > > I have tried reinstalling the OS, using their live boot ISO. Each time, no > matter which disk I configure (/dev/sda or /dev/nvme0n1), the install fails > with the message > > Installation failed Failed to run update-initramfs on the target The exit > code was 2 What OS is that ? What's the error of update-initramfs ? Did you try to run update-initramfs manually to see what error it gives you ? I remember seeing a similar error related to a busybox depedency (this error https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864143) and I can't remember the exact fix, but it was something like : edit /etc/initramfs-tools/initramfs.conf and change the "BUSYBOX=auto" to either "y" or "n", one of them fixes it. Or maybe it was the file /usr/share/initramfs-tools/conf-hooks.d/cryptsetup, or maybe you have to add a line "BUSYBOXDIR=/bin" to the config.. Either way, you should fix whatever is causing that first. > > I have upgraded coreboot, no joy. I have also tried manually running grub, > from the installer, ie > > mkdir /mnt/root > cryptsetup luksOpen /dev/sda3 root > mount /dev/mapper/root /mnt/root > mount /dev/sda1 /mnt/root/boot > grub-install --boot-directory=/mnt/root/boot /dev/sda > update-grub2 > Yeah, upgrading coreboot won't change anything if your hard drive doesn't have a working grub installed on it. I think your issue here might be that "update-grub2" will update the grub files in /boot (from the live USB), not in /mnt/root/boot. I would suggest to simplify your life and just "mount /dev/sda1 /boot" so the update would work (even if you manually use grub-mkconfig -o /mnt/root/boot, it will still scan some things in /boot, and it might mess things up, so just mount it on top of the existing /boot and call update-grub) > The folks at purism/librem seem to be as confused as I am. Does anyone here > have any insight into how I can fix this problem? I haven't heard of this issue, usually, if it's related to coreboot, I get asked for my opinion, but I suppose I wasn't poked about it by tech support because it's a linux/install problem, and indeed, it's not related to coreboot. As for all that stuff about getting seabios debug, I don't know how much that will help you. I'm sure all you'll see is something like "jumping into boot sector" then nothing, it's not like the cbmem console log will have the grub debug output in it saying "I'm about to crash because I can't find my config" for example. Unless SeaBIOS sets up a segfault handler or something prior to jumping into boot drive and writes to the log a crash report, I have no idea if it does that. > > Thanks! > I hope that helps, good luck. And if you need more help, I suggest not to spam this mailing list with non-seabios-development related questions, you can continue emailing me directly. Youness.

1 0

bug: boot menu items 10+ cannot be selected
by Ian Kelling 16 May '18

16 May '18

The boot menu says option 10, but when you type 10, it selects #1 as soon as you press 1. I think an easy fix would be that when there are at least 10 items in the boot menu to print 01, 02, etc. and read 2 characters. I don't care about this being fixed, just figured I'd report it. -- Ian Kelling https://iankelling.org

3 2

Re: [SeaBIOS] Librem 15v3 hangs at Booting from Hard Disk...
by Paul Menzel 15 May '18

15 May '18

Dear Philip, First of all, please respect the netiquette and do not top post. It makes replying much harder. Please use the interleaved style in the future. On 05/15/18 04:09, Philip C. wrote: […] > On Wed, May 9, 2018 at 9:14 PM Philip C. <pchampon(a)gmail.com> wrote: > But, now no matter what I do, unattended boots hang on > > SeaBIOS (version rel-1.11.0-0-g63451fc) > Booting from Hard Disk... Second, I really think this not a SeaBIOS issue, but a hard drive issue. But it seems functional, as SeaBIOS is listing it in the boot menu, and you can access it from the live installation. > I managed to get some feedback from Kevin, on IRC, which was set debug to > 8... > I began the adventure, by taking advantage of a pureos script > https://code.puri.sm/kakaroto/coreboot-files/raw/master/build_coreboot.sh > > I had to make a few modifications > megadl ' > https://mega.nz/#!fA03xADA!5uqZiKwNZIP1J27xHzIKVQPQaNfqxdtzKjPRxxwZMc8' > mv Intel\ CSME\ 11.0\ Firmware\ Repository\ Pack\ r50.rar > coreboot/me_11_repository.rar > comment out lines 226 and 227 > cd coreboot/flashrom && CFLAGS="-Wno-error=deprecated-declarations" > make; cd - > update the librem15v3 coreboot config file, setting seabios debug from > -1 to 8 > comment out the attempt to check the sha256 of the coreboot (since > debug changes sha) > the script created a coreboot rom file and claimed that it flashed the > rom > > However, when I rebooted, I didn't see any extra output on the screen and > it is still hung on the Booting from Hard disk... message > > Any thoughts on how I can get the debug output? 1. You need to capture the coreboot and SeaBIOS messages. Does the device have ports which can be used for debugging? As it’s a laptop, that is probably not the case. You could see if the messages are preserved during reboot. So, plug in the device with the live distribution, try to boot from the drive, get the error, and (warm) reboot, and select the distribution. Build `cbmem`, by getting the coreboot source code [1], and then do `make -C util/cbmem`. Or start a Linux kernel with `CONFIG_GOOGLE_MEMCONSOLE_COREBOOT` and look into `/sys/firmware/log`. 2. See if the option *SPI Flash console output* (`CONFIG_CONSOLE_SPI_FLASH`) is supported on your board. The Puri.sm folks should know and help you with that. > Send coreboot debug output to the SPI Flash in the FMAP CONSOLE area > > This option can cause premature wear on the SPI flash and should not > be used as a normal means of debugging. It is only to be enabled and > used when porting a new motherboard which has no other console > available (no UART, no POST, no cbmem access(non bootable)). Since > a non bootable machine will require the use of an external SPI Flash > programmer, the developer can grab the console log at the same time. > > The flash console will not be erased on reboot, so once it is full, > the flashconsole driver will stop writing to it. This is to avoid > wear on the flash, and to avoid erasing sectors (which may freeze > the SPI controller on skylake). > > The 'CONSOLE' area can be extracted from the FMAP with : > cbfstool rom.bin read -r CONSOLE -f console.log Kind regards, Paul

1 0

Re: [SeaBIOS] Librem 15v3 hangs at Booting from Hard Disk...
by Philip C. 15 May '18

15 May '18

Hello biosers, I managed to get some feedback from Kevin, on IRC, which was set debug to 8... I began the adventure, by taking advantage of a pureos script https://code.puri.sm/kakaroto/coreboot-files/raw/master/build_coreboot.sh I had to make a few modifications megadl ' https://mega.nz/#!fA03xADA!5uqZiKwNZIP1J27xHzIKVQPQaNfqxdtzKjPRxxwZMc8' mv Intel\ CSME\ 11.0\ Firmware\ Repository\ Pack\ r50.rar coreboot/me_11_repository.rar comment out lines 226 and 227 cd coreboot/flashrom && CFLAGS="-Wno-error=deprecated-declarations" make; cd - update the librem15v3 coreboot config file, setting seabios debug from -1 to 8 comment out the attempt to check the sha256 of the coreboot (since debug changes sha) the script created a coreboot rom file and claimed that it flashed the rom However, when I rebooted, I didn't see any extra output on the screen and it is still hung on the Booting from Hard disk... message Any thoughts on how I can get the debug output? Thanks On Wed, May 9, 2018 at 9:14 PM Philip C. <pchampon(a)gmail.com> wrote: > Hello everyone! > > I've been having some issues with a laptop recently. My Librem 15v3 was > bouncing along, until one day I ran into an apt-get upgrade issue. I > attempted to fix the affected script by pointing it to the base directory > busybox lived. The upgrade completed without any apparent issue. > > But, now no matter what I do, unattended boots hang on > > SeaBIOS (version rel-1.11.0-0-g63451fc) > Booting from Hard Disk... > _ > > I have tried reinstalling the OS, using their live boot ISO. Each time, no > matter which disk I configure (/dev/sda or /dev/nvme0n1), the install fails > with the message > > Installation failed Failed to run update-initramfs on the target The exit > code was 2 > > I have upgraded coreboot, no joy. I have also tried manually running grub, > from the installer, ie > > > 1. mkdir /mnt/root > 2. cryptsetup luksOpen /dev/sda3 root > 3. mount /dev/mapper/root /mnt/root > 4. mount /dev/sda1 /mnt/root/boot > 5. grub-install --boot-directory=/mnt/root/boot /dev/sda > 6. update-grub2 > > The folks at purism/librem seem to be as confused as I am. Does anyone > here have any insight into how I can fix this problem? > > Thanks! >

1 0

Librem 15v3 hangs at Booting from Hard Disk...
by Philip C. 10 May '18

10 May '18

Hello everyone! I've been having some issues with a laptop recently. My Librem 15v3 was bouncing along, until one day I ran into an apt-get upgrade issue. I attempted to fix the affected script by pointing it to the base directory busybox lived. The upgrade completed without any apparent issue. But, now no matter what I do, unattended boots hang on SeaBIOS (version rel-1.11.0-0-g63451fc) Booting from Hard Disk... _ I have tried reinstalling the OS, using their live boot ISO. Each time, no matter which disk I configure (/dev/sda or /dev/nvme0n1), the install fails with the message Installation failed Failed to run update-initramfs on the target The exit code was 2 I have upgraded coreboot, no joy. I have also tried manually running grub, from the installer, ie 1. mkdir /mnt/root 2. cryptsetup luksOpen /dev/sda3 root 3. mount /dev/mapper/root /mnt/root 4. mount /dev/sda1 /mnt/root/boot 5. grub-install --boot-directory=/mnt/root/boot /dev/sda 6. update-grub2 The folks at purism/librem seem to be as confused as I am. Does anyone here have any insight into how I can fix this problem? Thanks!

1 0

K-TEK-M275TP-FN-BL-ML USB keyboard support
by Аладышев Константин 29 Apr '18

29 Apr '18

Hello! I'm having problems with K-TEK-M275TP-FN-BL-ML keyboard (http://www.key-tek.cn/Productview.asp?id=777). It is USB device with keyboard and touchpad combined. It works in OS correctly, but doesn't work in SeaBIOS. I've tried to debug this issue and found that "usb_kbd_setup" function fails on "(epdesc->wMaxPacketSize != 8)" check, cause "epdesc->wMaxPacketSize" is actually 32. I've modified this "if" statement to pass 32 value also and now function completes successfully. But it didn't help to solve my issue. There are no interrupts from keyboard, "ehci_poll_intr" always returns -1 on check: if (token & QTD_STS_ACTIVE) { // No intrs found. return -1; } I don't know what to do now. What should I check next? Does SeaBIOS support USB keyboard+touchpad devices at all?

2 5

[PATCH] tpm: Request access to locality 0
by Stefan Berger 13 Apr '18

13 Apr '18

The CRB driver has to request access to locality 0. Our QEMU CRB model will enforce that as well. Signed-off-by: Stefan Berger <stefanb(a)linux.vnet.ibm.com> --- src/hw/tpm_drivers.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/hw/tpm_drivers.c b/src/hw/tpm_drivers.c index bd971f7..e4770b3 100644 --- a/src/hw/tpm_drivers.c +++ b/src/hw/tpm_drivers.c @@ -442,6 +442,8 @@ static u32 crb_activate(u8 locty) if (!CONFIG_TCGBIOS) return 0; + writeb(CRB_REG(locty, CRB_REG_LOC_CTRL), 1); + return 0; } -- 2.5.5

2 2

Re: [SeaBIOS] [coreboot] Upgrade the 12 years old LZMA libraries - should we do it?
by Zoran Stojsavljevic 04 Apr '18

04 Apr '18

Privet Ivan, I would say that Coreboot should go for the greatest and latest. Since everything from far back in Time is refined, mostly bug free (unless the new releases do not include some new introduced bugs, which are fixed (usually) in immediate releases). This is more matter of the right chosen strategy, which every package and/or library should follow. Zoran _______ On Tue, Apr 3, 2018 at 8:03 PM, Ivan Ivanov <qmastery16(a)gmail.com> wrote: > I have noticed that both coreboot and seabios are using the very old > versions of LZMA SDK. If we will upgrade our LZMA libraries from the > outdated-by-12-years 4.42 to the current version 18.04 , speed and > compression ratio should improve and maybe a few bugs will be fixed. > Do you think it should be done, or you are OK with using such an > outdated version? > > Best regards, > Ivan Ivanov aka qmastery > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS