SeaBIOS

seabios@seabios.org

4 participants
3800 discussions

Re: [SeaBIOS] CHS translation (BIOS incompatibility)
by Nikolay Ivanets 05 Jun '18

05 Jun '18

Well, I've played with disk geometry and translation mode options for attached disk to Qemu but it didn't help. Maximum I could do is to make correct VBR sector to load at boot process setting secs=32,trans=large or secs=32,trans=none but then bootstrap code from VBR fails with "Disk read error". It reads next N sectors into a memory trying to find bootloader (NTLDR) and fails. I also noticed Volume Boot Record (first partition sector) contains "sectors per track" record at offset 0x18 (from beginning of partition). Finally I've replace all entries of '63' to '32' in src/block.c. Now number of sectors/track becomes 32 instead of hard-coded 63 in LBA translation mode . Compiled BIOS and supplied to Qemu. Now Windows boots successfully even without manually specifying of disk geometry. Definetely it is not a permanent fix. But might be considered as a workaround for disks with 32 sectors/track. p.s. It seems HP servers have an option 32/63 sectors per track and 32 is default choese. Did anyone face with 32/63 sectors per track problem? How did you solve it, if any? May be I miss something and Seabios developers can point me a right direction? Thanks. -- Mykola Ivanets -- +380979184774 Mykola Ivanets сб, 2 черв. 2018 о 17:49 Nikolay Ivanets <stenavin(a)gmail.com> пише: > > Hello. > > I have a bootable disk image taken from physical machine. Original BIOS is unknown. Operating system installed is Windows 2003 R2. > > I'm trying to boot it with Qemu and Seabios and get "Error loading operating system". > > After investigation I found: > - image contains MBR partition table and single NTFS partition > - partition starts at CHS (0,1,1) and absolute offset is 0x20 (32 sectors) > > Debugging MBR bootstrap code I found it makes several INT13 calls to BIOS: AH=08, AH=02 to get disk parameters and load first partition sector. > > It appeared BIOS returns CHS as (x,y,63) and thus MBR bootstrap loads 63rd sector instead 32nd and "Error loading operating system" happens. > > It seems well-known BIOS incompatibility issue. > > Is there any way to workaround this in Seabios? > I would appreciate for any tips. > > -- > Mykola Ivanets

1 0

[PATCH v2 0/6] qemu: add bochs-display support
by Gerd Hoffmann 04 Jun '18

04 Jun '18

Add support for the new bochs-display device in qemu. Gerd Hoffmann (6): optionrom: enable non-vga display devices cbvga: factor out cbvga_setup_modes() qemu: add bochs-display support cbvga_setup_modes: use real mode number instead of 0x140 cbvga_list_modes: don't list current mode twice cbvga_set_mode: disable clearmem in windows x86 emulator. Makefile | 2 +- vgasrc/vgahw.h | 28 +++++++++--------- vgasrc/vgautil.h | 4 +++ src/optionroms.c | 29 ++++++++++++++++++- vgasrc/bochsdisplay.c | 59 ++++++++++++++++++++++++++++++++++++++ vgasrc/cbvga.c | 78 +++++++++++++++++++++++++++++++++------------------ vgasrc/Kconfig | 17 +++++++++++ 7 files changed, 175 insertions(+), 42 deletions(-) create mode 100644 vgasrc/bochsdisplay.c -- 2.9.3

2 7

CHS translation (BIOS incompatibility)
by Nikolay Ivanets 02 Jun '18

02 Jun '18

Hello. I have a bootable disk image taken from physical machine. Original BIOS is unknown. Operating system installed is Windows 2003 R2. I'm trying to boot it with Qemu and Seabios and get "Error loading operating system". After investigation I found: - image contains MBR partition table and single NTFS partition - partition starts at CHS (0,1,1) and absolute offset is 0x20 (32 sectors) Debugging MBR bootstrap code I found it makes several INT13 calls to BIOS: AH=08, AH=02 to get disk parameters and load first partition sector. It appeared BIOS returns CHS as (x,y,63) and thus MBR bootstrap loads 63rd sector instead 32nd and "Error loading operating system" happens. It seems well-known BIOS incompatibility issue. Is there any way to workaround this in Seabios? I would appreciate for any tips. -- Mykola Ivanets

1 0

[PATCH 0/6] qemu: add bochs-display support
by Gerd Hoffmann 01 Jun '18

01 Jun '18

Add support for the new bochs-display device in qemu. Gerd Hoffmann (6): pci,optionrom: enable non-vga display devices cbvga: factor out cbvga_setup_modes() qemu: add bochs-display support cbvga_setup_modes: use real mode number instead of 0x140 cbvga_list_modes: don't list current mode twice [workaround] cbvga_set_mode: disable clearmem vgasrc/vgahw.h | 28 ++++++------ vgasrc/vgautil.h | 1 + src/fw/pciinit.c | 15 +++++-- src/optionroms.c | 29 ++++++++++++- vgasrc/cbvga.c | 127 +++++++++++++++++++++++++++++++++++++++++++------------ vgasrc/Kconfig | 17 ++++++++ 6 files changed, 173 insertions(+), 44 deletions(-) -- 2.9.3

2 15

Re: [SeaBIOS] [PATCH 0/6] qemu: add bochs-display support
by Patrick Rudolph 31 May '18

31 May '18

Patch 2, 4 and 5 looks good to me. Patch 6 causes artifacts on mode change, if the new mode is smaller than the previous. Would it be possible to include a 32bit memset into seavgabios ? That way there is no need to call a BIOS routine to clear the memory. Regards, Patrick On Thu, 2018-05-31 at 08:33 +0200, Gerd Hoffmann wrote: > Add support for the new bochs-display device in qemu. > > Gerd Hoffmann (6): > pci,optionrom: enable non-vga display devices > cbvga: factor out cbvga_setup_modes() > qemu: add bochs-display support > cbvga_setup_modes: use real mode number instead of 0x140 > cbvga_list_modes: don't list current mode twice > [workaround] cbvga_set_mode: disable clearmem > > vgasrc/vgahw.h | 28 ++++++------ > vgasrc/vgautil.h | 1 + > src/fw/pciinit.c | 15 +++++-- > src/optionroms.c | 29 ++++++++++++- > vgasrc/cbvga.c | 127 +++++++++++++++++++++++++++++++++++++++++++------------ > vgasrc/Kconfig | 17 ++++++++ > 6 files changed, 173 insertions(+), 44 deletions(-) >

2 1

[PATCH] gitignore: ignore config.mak
by Ciro Santilli 22 May '18

22 May '18

--- Resending because I had not subscribed previously and it bounced. .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index f9990fe..15c0b1a 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,4 @@ +config.mak out *.pyc .config -- 2.16.1

2 2

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

17 May '18

I guess it is not possible.. Found this article on vendor site https://www.transcend-info.com/Support/FAQ-409 "- Can the JetFlash be used as a bootable flash drive?" "JetFlash series aims at being a portable storage device and not as a bootable drive. No exclusive software tool is provided either." Best Regards, Aladyshev Konstantin From: Аладышев Константин [mailto:aladyshev@nicevt.ru] Sent: Thursday, May 17, 2018 2:50 PM To: 'seabios(a)seabios.org' Cc: kevin(a)koconnor.net Subject: SecureDrive 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

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 15 May '18

15 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS