, the uneven (unrelated to the power of 2's) values
of 600 weren't really justified in the first place: 768 decimal is
0x300, while 600 is a weird 0x258.
On Sat, Apr 3, 2021 at 3:49 AM Kevin O'Connor wrote:
>
> On Thu, Apr 01, 2021 at 05:44:06PM +0300, Mike Banon wrote:
> > Good day K
Good day Kevin, please tell if there's anything I can add for us to
proceed with a review of this patch.
On Tue, Mar 9, 2021 at 12:54 PM Mike Banon wrote:
>
> According to my calculations, my proposed 768 default - which is just
> slightly larger than a previous 600 - should also all
really justified in the first place: 768 decimal is
0x300, while 600 is a weird 0x258.
On Tue, Mar 9, 2021 at 2:28 AM Kevin O'Connor wrote:
>
> On Tue, Mar 02, 2021 at 11:21:27PM +0300, Mike Banon wrote:
> > There are plenty of coreboot platforms whose MPTABLE size is just
> > sl
size, to replace the current uneven limit of
600. SMBIOS size should be bumped the similar way as well.
Signed-off-by: Mike Banon
---
diff --git a/src/config.h b/src/config.h
index 93c8dbc..71333f8 100644
--- a/src/config.h
+++ b/src/config.h
@@ -21,9 +21,9 @@
// Largest supported externaly
Thank you so much Kevin, really happy to hear about this ;) Wish you a nice day
On Mon, Dec 21, 2020 at 7:00 PM Kevin O'Connor wrote:
>
> On Sun, Dec 13, 2020 at 03:30:45PM +0300, Mike Banon wrote:
> > Each try takes about ~3300 ticks of a timer (got this info by some
> >
es where a 3rd try was needed, I put one more just in case and to
make my fix more universal.
On Wed, Dec 9, 2020 at 8:36 PM Kevin O'Connor wrote:
>
> On Thu, Dec 03, 2020 at 07:06:59AM +0300, Mike Banon wrote:
> > At least some USB drives with a write protect switch (e.g. Netac U335
successful initialization of such a "broken hardware".
Signed-off-by: Mike Banon
diff --git a/src/hw/blockcmd.c b/src/hw/blockcmd.c
index 1f15081..6b6fea9 100644
--- a/src/hw/blockcmd.c
+++ b/src/hw/blockcmd.c
@@ -144,8 +144,9 @@ scsi_is_ready(struct disk_op_s *op)
dprintf(6, "scsi_i
2020 at 2:43 AM Nico Huber wrote:
>
> Hi Mike,
>
> On 10.11.20 19:22, Mike Banon wrote:
> > Thank you very much for your advice, dear Naresh, I will try matching
> > the UEFI routing.
>
> I wouldn't expect too much. If things are configurable in the chipset
> (the
> there isn't much demand for floppies these days (even emulated floppies).
I disagree: There's a big demand for emulated floppies thanks to the
unique capabilities provided by them! For example: if KolibriOS
(http://kolibrios.org/en/) supports your Ethernet controller and you
add a KolibriOS
Hi there Paul,
Sorry for a late reply and thanks for your message, wish you a happy
time and good health.
>
>> Add support for up to 35 boot menu entries (2 pages if >18). To solve the
>> ">10" problem currently experienced by SeaBIOS users (there are no 11, 12,
>> etc.
>> keys on a keyboard -
Rafael, please could you share a working method of expanding a floppy
from 1.44MB to i.e. 2.88MB ?
I'm back to this issue and noticed that popular Linux tools (i.e.
gparted with libparted, fatresize, etc.) weirdly do not support
resizing a FAT12 filesystem which the floppies have. Manually
compiled coreboot.rom with this command:
./build/cbfstool ./build/coreboot.rom add -f ./floppy/memtestp.bin -n
floppyimg/memtestp.lzma -t raw -c lzma
If done everything correctly, it will be available at SeaBIOS boot menu as
Ramdisk [memtestp]
Best regards,
Mike Banon
On Sun, Jul 28, 2019 at
Hope you can share your source code modifications, in the case someone
else would find them useful.
On Fri, Jul 12, 2019 at 8:19 AM Konstantin Novikov
wrote:
>
> Hello again.
>
> I want to update my progress, maybe it's can be useful for someone.
> Yes, it's all about es register. Solution is to
is
enabled. Instead of stopping the initialization attempts immediately,
stop only after getting this report for 3 times, to ensure the
succesful initialization of such a "broken hardware".
Signed-off-by: Mike Banon
---
diff --git a/src/hw/blockcmd.c b/src/hw/blockcmd.c
index 1f1508
after i.e. 3rd attempt is unsuccessful --->
reducing the wasted time to a couple of milliseconds or even less.
Hopefully this patch would be more acceptable in such a version.
cheers,
Mike
On Wed, Jun 5, 2019 at 10:46 AM Gerd Hoffmann wrote:
>
> On Tue, Jun 04, 2019 at 09:07:44PM +030
At least some USB drives with a write protect switch (e.g. Netac U335)
could report "MEDIUM NOT PRESENT" for a while if a write protect is
enabled. Do not stop the initialization attempts after getting this,
and the initialization will be successful - likely on a 2nd attempt.
Signed-of
Peter, I believe we shouldn't put it like "ELF versus Floppy" because
these ways are not mutually exclusive: they could be tried in
parallel, especially since Rafael's pursuit towards a working solution
also involves waiting for helpful replies from the mailing lists ;-)
Also, regarding SeaBIOS: I
ccessful.
Best regards,
Mike Banon
On Fri, Apr 19, 2019 at 8:50 AM Rafael Send wrote:
>>
>> Could you please calculate, where's a memory area which is matching
>> these CHS values?
>
>
> Hm, I either don't follow or don't know enough about how this stuff works to
>
s fails to read at the same CHS values, so I don't know
> how to tell how "high" it really can get
>
> I can try building an 8MB image and see if that's any better I guess.
>
> Thanks for the suggestions thus far,
>
> R
>
> On Thu, Apr 18, 2019 at 9:59 PM Mike Banon w
st
leave it as 1M)
However it seems I'll have to increase the max_track value at line 69
from 79 to 799 . (also, why at line 61 there's "18" sectors and not
"36" ? (the number of sectors at the largest 2.88MB floppy)) ...
So I'm sure that a larger floppy format is doable, just ne
> However, it hangs after that and doesn't boot my kernel.
This looks like for some reason SeaBIOS might have loaded only some
beginning part of your floppy image instead of it whole. Do you use
any of my unofficial patches currently or just the SeaBIOS master? You
could insert some debug prints
oppy will fit there). This code
should be compatible with any new sizes as well, but let me know if
there are any problems. When you're running QEMU with -serial stdio ,
it should output those debug messages into your console, if the debug
level of these messages is higher than what's set at your SeaBI
regards,
Mike Banon
On Mon, Apr 15, 2019 at 6:12 PM Rafael Send wrote:
>
> I haven't gotten around to poking at SeaBIOS yet, I'm still wondering how to
> test my large floppies.
>
> Syslinux appears to install to them fine, but QEMU doesn't seem to like
> booting them with -fda.
&g
Personally I think that either this guy did something incorrectly or
there's a Windows 3.1 bug. Meanwhile, Rafael's Linux-based OS is going
to boot from this floppy like it's a ramdisk, so hopefully should be
indifferent to the custom floppy sizes and would work. I share the
same hopes for
ike taking shots in the dark, but
> I'll see what I can come up with.
>
> Cheers,
> R
>
> Mike Banon schrieb am Fr., 12. Apr. 2019, 22:52:
>>
>> Hi Rafael,
>>
>> I believe that, with a little more effort, this guy would have
>> succeeded at add
regards,
Mike Banon
On Fri, Apr 12, 2019 at 9:39 PM Rafael Send wrote:
>
> Hi,
> I'm working on stuffing a bootable Linux distro into coreboot. In QEMU I
> already succeded by using coreboot's built-in kernel loading mechanism, but
> that's without SeaBIOS.
>
> I'd love to
Good day,
> Also note that not all keyboards layouts have querty ordering. Mine
> (german) has quertz, and dvorak looks completely different.
Thank you, I forgot about this. Hope their scancodes are the same...
By the way: if we are extending the boot menu, at ./src/config.h we
need to
have any devices with TPM so it is hard for me to debug
this part. The best thing I could do is to hack into SeaBIOS tpm code
to make it show the tpm menu entries stuff which does not exist, but
at the moment I don't even know how it looks like...
Best regards,
Mike Banon
___
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-le...@seabios.org
own version (aside from the size issue) - I am open to
suggestions and could try to address them when I will have enough free
time.
Best regards,
Mike Banon
___
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-le...@seabios.org
ll be enabled: press
one or two digit keys and then ENTER to confirm your choice, or remove a digit
by pressing the '.Del' key. Also you could call TPM with '-' key at any moment,
or boot with a single key press of your fullsize keyboard.
Signed-off-by: Mike Banon
(patch body is after the testing instructi
Why BMP? It's a lossless image format which could be LZMA compressed
quite well depending on the image's variety of colours. And finally I
found out how to get a working splash screen - instructions tested on
AMD Lenovo G505S laptop with 1366x768 screen resolution :
1) Install the ImageMagick
Please tell, will the old ASCII mailing list archive continue to work
and get the new messages?
I found it as really convenient to wget and observe with lightweight
browsers or even console "links"
On Wed, Jan 9, 2019 at 5:03 PM Laszlo Ersek wrote:
>
> On 01/08/19 23:52, Kevin O'Connor wrote:
>
e floppies as a
coreboot user.
Signed-off-by: Mike Banon
---
diff --git a/src/block.h b/src/block.h
index f64e880..aaa236f 100644
--- a/src/block.h
+++ b/src/block.h
@@ -2,7 +2,7 @@
#define __BLOCK_H
#include "types.h" // u32
-
+#include "romfi
le with (0x8c/4) = 23 iterations. It works but
SeaBIOS quickly freezes after that, which probably means it is
incorrect substitution for some reason
Best regards,
Mike Banon
___
SeaBIOS mailing list
SeaBIOS@seabios.org
https://mail.coreboot.org/mailman/listinfo/seabios
st regards,
Mike Banon
On Sat, Nov 17, 2018 at 2:30 AM Mike Banon wrote:
>
> Thank you very much for clarifying, Kevin. I finally moved this ram
> allocation to do_boot function (line 800) at boot.c - after the
> printf("Booting from Floppy...\n") - but sadly it seems tha
3, 2018 at 9:06 PM Kevin O'Connor wrote:
>
> On Sun, Nov 11, 2018 at 02:12:09AM +0300, Mike Banon wrote:
> > > However I'm concerned that this would reserve memory for all
> > > of the floppy images in the e820 map (and thus the final OS
> > > would not be able to
source code - mostly placing the "floppy searching"
code inside the "for" cycle. But I could try to do something with the
allocation part if that wouldn't turn out too difficult
On Sat, Nov 10, 2018 at 9:16 PM Kevin O'Connor wrote:
>
> On Fri, Nov 02, 2018 at 01:07:
boot.rom add -f ./floppy/memtestp.bin -n
floppyimg/memtestp.lzma -t raw -c lzma
If done everything correctly, it will be available at SeaBIOS boot
menu as Ramdisk [memtestp]
Best regards,
Mike Banon
On Mon, Nov 5, 2018 at 3:51 PM Krystian Hebel wrote:
>
>
>
> On 11/05/18 13:32, Paul
there at some laptops)
Shortened patch description message:
All the available floppy images will be found and listed in a boot
menu, instead of the first found. Useful if you are participating in a
hobby OS development or would like to access multiple floppies as a
coreboot user.
Signed-off-by: Mike Banon
or (more likely) its partition table or maybe
GRUB2 is corrupted. Then you could try restoring GRUB2, by following
these instructions for example -
https://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd
If yes, it didn't help you?
Best regards,
Mike Banon
On Wed, Aug 8
Sun, Feb 25, 2018 at 5:41 PM, Kevin O'Connor <ke...@koconnor.net> wrote:
> On Sun, Feb 25, 2018 at 03:05:06AM +0300, Mike Banon wrote:
>> Friends, I need your help. While trying to improve SeaBIOS I got stuck
>> at this very strange problem - which does not appear when you do a
ngs, "emulation/qemu-i440fx" target
Best regards,
Mike
On Sun, Feb 25, 2018 at 11:55 AM, Paul Menzel <pmen...@molgen.mpg.de> wrote:
> Dear Mike,
>
>
> Am 25.02.2018 um 01:05 schrieb Mike Banon:
>>
>> Friends, I need your help. While trying to impro
void *temp =
malloc_tmphigh(size); --- but we couldn't call there our testfunc()
which calls "malloc_" without running into this problem?
Best regards,
Mike Banon
___
SeaBIOS mailing list
SeaBIOS@seabios.org
https://mail.coreboot.org/mailman/listinfo/seabios
43 matches
Mail list logo
