SeaBIOS

seabios@seabios.org

3783 discussions

1TB Guest changes to receive phys bits >=40
by Christian Ehrhardt 11 Jun '18

11 Jun '18

Hi, I was asked about x86 Guests of >1TB in size. And while some discussions where around qemu/libvirt and host-phys-bits [1] I realized that in Seabios I need exactly what is already in CentOS/RHEL [2] to get the phys-bits passed on. The change [2] itself is rather old, so I wondered if I'm missing that this was implemented in a totally different way. Do I have to switch/set options these days instead of using that patch? But I saw that it is still applied even to rather recent versions. So the question become why the change is not upstream yet? Was it maybe discussed in the past and Nack'ed for some reason? I didn't find the discussion if that is the case and would appreciate the pointer. We are closing in to make 1TB more common rather quickly, so I wonder if really nothing would speak against it - would it be reasonable to consider committing that upstream to Seabios these days? [1]: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1769053 [2]: https://git.centos.org/blob/rpms!seabios.git/14f0fd75785bc5f1468fa84fbd3a16… P.S. Subscribing people acking the original patch as they might have old context to provide on this. -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd

1 0

Re: [SeaBIOS] CHS translation (BIOS incompatibility)
by Kevin O'Connor 06 Jun '18

06 Jun '18

On Tue, Jun 05, 2018 at 06:09:54PM +0300, Nikolay Ivanets wrote: > > As far as I know, QEMU should be able to tell SeaBIOS the exact > > geometry to use (eg, via qemu -hdachs c,h,s[,t] option). If you're > > not getting the expected behavior, be sure to include the seabios log > > file - see: https://www.seabios.org/Debugging > > > > Here is geometry when I have with patched bios (Windows boot): > drive 0x000f57f0: PCHS=16383/16/63 translation=lba > LCHS=1024/255/32 s=143305920 > > Here is geometry I have with original Seabios (boot fails): > drive 0x000f0bd0: PCHS=16383/16/63 translation=lba > LCHS=1024/255/63 s=143305920 > > Qemu limits what we can specify in CHS to 16383, 16 and 63 > respectively and I don't see any combinations which will perform > necessary translation from PCHS=16383/16/63 to LCHS=1024/255/32. If I understand it correctly, you're looking for LCHS=1024/255/32. I don't know why QEMU wont let you specify heads=255, but short of doing that, I don't see a way for SeaBIOS to obtain that logical mapping. The disk geometry translation stuff is arcane - the SeaBIOS code is translated from the original Bochs bios code. If it needs to be enhanced, it would require both a qemu patch (to specify the desired translation/geometry) and a seabios patch (to implement it). -Kevin

2 1

Re: [SeaBIOS] CHS translation (BIOS incompatibility)
by Kevin O'Connor 06 Jun '18

06 Jun '18

On Tue, Jun 05, 2018 at 12:51:54PM +0300, Nikolay Ivanets wrote: > 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? As far as I know, QEMU should be able to tell SeaBIOS the exact geometry to use (eg, via qemu -hdachs c,h,s[,t] option). If you're not getting the expected behavior, be sure to include the seabios log file - see: https://www.seabios.org/Debugging -Kevin

2 1

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS