FlyGoat
Unable to boot from USB
I'm unable to preform USB boot, I modified the source code to prioritize USB Boot, however, USB devices appear to get disabled on boot. Additionally, I cannot boot from eMMC, it should time out after 30 seconds, but it simply doesnt. I2C keyboards (like those connected in laptops) also seem to just not work. Also, USB keyboards dont work at all.
At least give some information about your hardware ?
Don't think the I2C keyboard thing can be fixed easily it will need a whole new driver in SeaBIOS.
I figured out the USB problem is a bug with 1.2.3, but 1.2.1 doesnt work on my hardware at all. I believe we should keep this open till the USB bug is universally fixed
@generalchuckles-cm
I figured out the USB problem is a bug with 1.2.3, but 1.2.1 doesnt work on my hardware at all. I believe we should keep this open till the USB bug is universally fixed
If 1.2.1 isn't enough but 1.2.3 is too much, you can try one of the halfway builds published in #87
I did try 1.2.2 when it came out, but if theres an inbetween beta build, ill try it, I'll check. The problem is, in 1.2.2 and below, Jasper Lake's PAM Register couldn't be unlocked. Anywaays the I2C bug is a SeaBIOS problem, and I don't blame them. Most BIOSes come from AMI (like Gateway and Acer), and InsydeH20 (like HP), which have this. I very might be able to mix the I2C in the MrChromebox firmware to have that, but it would take me some serious time. Still, since my device is a modified Chromebook, I'm pretty sure an I2C merge is possible since MrChromebox Coreboot, is based on SeaBIOS (and coreboot payload)
I did try 1.2.2 when it came out, but if theres an inbetween beta build, ill try it, I'll check.
There are more than one.
Anywaays the I2C bug is a SeaBIOS problem, and I don't blame them. Most BIOSes come from AMI (like Gateway and Acer), and InsydeH20 (like HP), which have this. I very might be able to mix the I2C in the MrChromebox firmware to have that, but it would take me some serious time. Still, since my device is a modified Chromebook, I'm pretty sure an I2C merge is possible since MrChromebox Coreboot, is based on SeaBIOS (and coreboot payload)
For now is more matter than luck, than anything else, see my bug about the usbkeyboard I use.
On the N100 I tested quickly, the thing doesn't work because the above 4G remapping, albeit the bios has the needed option checked, and so on.
It's the kind of things that hardly can be addressed by a single or a couple of developers, especially in this case that a good share of code comes from another project.
I hope that more devs and more testers will be involved in the next months, because the project is very interesting and useful, but the chances that something doesn't work on a specific scenario are still too high.
I'm going to for now, try to merge the I2C driver into SeaBIOS and then CSMWrap and see if I can come up with something, and hopefully contribute
To clarify: Contribute to seaBIOS, NOT here unless seaBIOS people dont accept it, I dont want to have to redo all this, nor do I want you guys to, when a new SeaBIOS is used
The artifact right after 1.2.2, Prefering SMBIOS2, both works with USB and works on my jasper lake PC!
It turns out it doesnt recognize USB drives at all. I can't at all tell if its because im using a USB hub yet. I'm gonna keep wworking on this tomorrow, its 10:46PM at the time of my posting this comment
@generalchuckles-cm Thanks for all troubleshooting.
However, my time is really limited for next 1-2 months so I won't be able to look into those platform issues. Contributions are always welcomed, tho.
Re SeaBIOS, my plan was to upstream all of our CSMWrap downstream changes so eventually we can build from upstream source.
Thanks
I'll manually troubleshoot. I have the source off of the change of preferring SMBIOS2 over 3 which fixed the PAM issue on my system. I understand the limited time, and if I cannot figure it out, I hope you do!
Wait, seabios is not even parsing SMBIOS, so I have no idea how can it influence USB stuff..
Not what I meant in this case. I just chose a random build between 1.2.2 and 1.2.3
I've also noted it starts in graphics mode which is a problem when starting installers and games in MS-DOS
I've also noted it starts in graphics mode which is a problem when starting installers and games in MS-DOS
@generalchuckles-cm isn't that the usual SeaBIOS VGA ROM issue that others have ? You can solve it by extracting the legacy video ROM from your BIOS and using that if it's old enough to support it.
Wouldnt work. iGPUs have no vBIOS generally, and my systen is UEFI Class 3, i dont think it has a legacy video rom
We do use seabios coreboot leagcy rom. Other rom types won't work as they are all hardware specific.
I'm gonna force seaBIOS to compile its legacy video rom
@generalchuckles-cm What is the iGPU ?
Sometimes you might be able to find legacy ROM for it on another system (it's stored in the UEFI), though swapping the VBT table in it is necessary and might be tricky.
im on a modded chromebook, mrchromebox coreboot BIOS, UEFI only tho
SeaBIOS wouldnt compile when i told it to use its own legacy rom
Might be able to find a legacy ROM in some miniPC or laptop BIOS.
https://www.oemproduction.com/nano-n6000d mentions legacy BIOS support so Intel did make it for Jasper Lake.
Personally, I wonder if theres a config edit I can make to make it boot first in text mode
Also suggestion: CSMWrap Discord Server, would be useful so I dont have to constantly refresh github waiting on response.