Issue Tracker: Issueshttps://ticket.coreboot.org/https://ticket.coreboot.org/themes/PurpleMine2-2.16.2/favicon/favicon.ico?12024-02-16T16:13:32ZIssue Tracker
Redmine flashrom - Feature #526 (New): Add Support for Macronix MX29LV800CThttps://ticket.coreboot.org/issues/5262024-02-16T16:13:32ZStar Fox
<p>Hi,</p>
<p>it would be very nice if you can add support for the Macronix MX29LV800CT.</p>
<p>Datasheets here:<br>
<a href="https://www.mxic.com.tw/Lists/Datasheet/Attachments/8544/MX29LV800C%20T-B,%203V,%208Mb,%20v2.6.pdf" class="external">https://www.mxic.com.tw/Lists/Datasheet/Attachments/8544/MX29LV800C%20T-B,%203V,%208Mb,%20v2.6.pdf</a></p>
<p>Another Flashrom Version from jhcloos has this Chipset in the flashchips.h File:<br>
<a href="https://github.com/jhcloos/flashrom/blob/master/flashchips.h" class="external">https://github.com/jhcloos/flashrom/blob/master/flashchips.h</a></p>
<p>Big Thanks in advance</p>
coreboot - Bug #521 (New): gizmosphere/gizmo2 development board VGA support not workinghttps://ticket.coreboot.org/issues/5212023-12-24T18:50:04Z8oDE 03
<p>I got a gizmo2 development board. the official hardware and software support stopped a long time ago and no BIOS source code was released.<br>
I tried to compile coreboot firmware to support some new features. The latest supported coreboot version is 4.18.<br>
I flashed and booted the gizmo2 development board, there is no video output during the coreboot startup phase, but it boots the OS normally and the OS has video output, I purchased a FT232H board for printing logs, and it seems like there are a lot of problems.</p>
<pre><code>FMAP REGION: COREBOOT
Name Offset Type Size Comp
cbfs_master_header 0x0 cbfs header 32 none
config 0x80 raw 562 none
revision 0x300 raw 720 none
build_info 0x600 raw 103 none
spd.bin 0x6c0 spd 128 none
fallback/dsdt.aml 0x780 raw 6172 none
cmos_layout.bin 0x2000 cmos_layout 616 none
fallback/postcar 0x22c0 stage 22312 none
payload_config 0x7a40 raw 1621 none
payload_revision 0x80c0 raw 237 none
(empty) 0x8200 null 31652 none
apu/amdfw 0xfdc0 raw 135168 none
fallback/romstage 0x30e00 stage 387544 none
fallback/ramstage 0x8f880 stage 136240 LZMA (311716 decompressed)
pci1002,9830.rom 0xb0d40 optionrom 59392 none
fallback/payload 0xbf580 simple elf 72695 none
(empty) 0xd11c0 null 3255268 none
bootblock 0x3ebdc0 bootblock 16384 none
</code></pre> coreboot - Bug #517 (New): lenovo x230 boot stuck with connected external monitorhttps://ticket.coreboot.org/issues/5172023-12-04T13:10:34ZVasily Evseenko
<p>Coreboot releases 4.21 and 4.22.01 have a bug.<br>
If lenovo x230 laptop has connected external monitor then boot stuck on Seabios greeting.<br>
Boot without external monitor always succeeded.<br>
Last release without bug is 4.20.1<br>
Coreboot config attached.</p>
flashrom - Documentation #503 (In Progress): Feedback on "new" documentation website <www.flashr...https://ticket.coreboot.org/issues/5032023-08-07T14:45:04ZReal Onebajcsielias78@gmail.com
<p>This github issue is my personal feedback on flashrom's "new" documentation website.</p>
<p>TL;DR: The new website is horrible & lacks a lot of information and the "old" wiki is way more better.<br>
No download instructions</p>
<p>The new website doesn't have any download instructions, just building instructions. As a beginner, you can't tell where you should download the code. It just tells you how to build from the source where you are supposed to figure out how and where to download from.</p>
<p>On the other hand, the "old" wiki has a dedicated downloads page that is directly visible from the start page which tells you pretty much everything:</p>
<ul>
<li>Required dependencies;</li>
<li>How to get the source code with git;</li>
<li>Binary packages for various popular GNU/Linux distributions, BSD distributions and MS Windows;
Dedicated windows wiki page.</li>
</ul>
<p>It has a TON of missing resources that return 404</p>
<p>Trying to find a way to write a feedback to this project regarding this, I've noticed many webpages were missing, with the server returning me 404.<br>
Even harder to find what you need</p>
<p>There is no search feature, pages you'd expect to find your answer don't really work, etc.</p>
<p>For instance, I was trying to find the list of supported programmers. In return, the website hit me with this mess:</p>
<p>image</p>
<p>Like seriously, what is this mess?! Inserting man pages is not really helpful.</p>
<p>The old wiki on the other hand, has a dedicated page listing with images the supported programmers, which makes the difference.<br>
Ugly</p>
<p>I like the idea of minimalism, which is what a lot of websites should adopt, however this is way too simple and confusing.</p>
<p>The old wiki had more features like tables with images and colors indicating certain stuff, and I also really like the "Emergency help" red box (see below), which just gives the end user the idea that what they are doing could be potentially fatal and other important instructions.</p>
<p>image</p>
<p>The new website does not have these important features, which makes it hard to follow. It has this gray-on-white with few color indications (terminal output), which is very boring and makes me sleepy. Documentation shouldn't be boring, but be rather important.<br>
"Anon, you can't just leave your feedback here, this is the official flashrom github repository, not a place where you can leave your feedback"</p>
<p>I think that's true, but in the same time it was hard for me to really pick something from the Contact page.</p>
<p>First, there is no feedback section where I can really send this.</p>
<p>Second of all, I wanted to voice my oppinion to more people.</p>
<p>I could have easily just sent this to <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a>, but here are my answer scenarios:</p>
<pre><code>"We are sorry, but this is not the support channel, so if you want to send your feedback, send it to something@flashrom.org";
"Thank you for sending us your feedback. Your feedback is very important for us, and we'll keep that in mind" and then *the only person who read my feedback would forget about it, the feedback would be forever forgotten;
No answer and nothing would be achieved.
</code></pre>
<p>An apology message for being too harsh on the situation and thanking in advance</p>
<p>I don't really mean to be too harsh about the situation, but I've had really good anticipations about flashrom, praising it for a few months. Seeing how big of a downgrade got the documentation page made me really frustrated, which made me voice my criticism on the documentation website.</p>
<p>The program itself is quite good, can't complain about it. However, there were occasions where I had to troubleshoot the situation, and I would visit wiki.flashrom.org out of instinct. Today I visited it's domain - flashrom.org - just to see if something else is on this domain. I was very surpised to see how bad the documentation on that website was, and just assumed it was the old documentation, but the "Old wiki website" revealed that it is the otherwise.</p>
<p>In conclusion, I want to apologize on being too critic, I hope some people will really read this, I hope the developers will work on the documentation website, I want to apologize for any grammar & typo errors and I want to thank you in advance.</p>
<p>TheRealOne78</p>
coreboot - Bug #495 (In Progress): Stoney chromebooks not booting PSPSecureOS -- Graphics driver ...https://ticket.coreboot.org/issues/4952023-06-14T18:03:16ZCoolStar Organizationcoolstarorganization@gmail.com
<p>Windows 11 Graphics driver takes 30 minutes to start on Stoney due to missing PSPSecureOS. Windows 10 20H2 and newer hangs on boot (potentially from the same thing)</p>
flashrom - Support #434 (New): Add Winbond W25Q128FW supporthttps://ticket.coreboot.org/issues/4342022-10-24T12:10:30ZLuca Consoli
<p>Hello,<br>
is it possible to support Winbond W25Q128FW please?<br>
Datasheet is <a href="https://www.digikey.com/en/datasheets/winbond-electronics/winbond-electronicsw25q128fw20revk2005182017#pf6" class="external">here</a>.</p>
coreboot - Bug #427 (New): x200: Two battery charging issueshttps://ticket.coreboot.org/issues/4272022-10-14T02:59:16ZAkura Ryu
<p>I've flashed my ThinkPad X200 with coreboot. Currently it has trouble when charging.</p>
<a name="1-Charge-state-mismatch"></a>
<h2 >1. Charge state mismatch<a href="#1-Charge-state-mismatch" class="wiki-anchor">¶</a></h2>
<p>When I plug in my AC adapter, system always reports " <strong>Not charging</strong> ". </p>
<p>Here's the output from the <code>acpi</code> utility:</p>
<pre><code>Battery 0: Not charging, 23%
Adapter 0: on-line
</code></pre>
<p>But weirdly, battery level is still increasing as the AC adapter is on-line.</p>
<p>What's more, it still reports "Not charging" when AC adapter is detached (normally it should be "Discharging").</p>
<a name="2-Battery-threshold-doesnt-seem-to-work"></a>
<h2 >2. Battery threshold doesn't seem to work.<a href="#2-Battery-threshold-doesnt-seem-to-work" class="wiki-anchor">¶</a></h2>
<p>Since tp_smapi is unusable without stock firmware, I use <code>tpacpi-bat</code> to configure battery threshold. My KDE battery indicator can recognize these thresholds.</p>
<pre><code class="sh syntaxhl" data-language="sh"><span class="nb">sudo </span>tpacpi-bat <span class="nt">-s</span> ST 1 88 <span class="c"># Start threshold</span>
<span class="nb">sudo </span>tpacpi-bat <span class="nt">-s</span> SP 1 90 <span class="c"># Stop threshold</span>
</code></pre>
<p>But no matter how I charge, battery will always be fully charged.</p>
<a name="Revision"></a>
<h2 >Revision<a href="#Revision" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>OS</strong>: Arch Linux with KDE</li>
<li><strong>Coreboot revision</strong>: 93781523a</li>
<li><strong>Configuration</strong>: See attachment</li>
</ul>
flashrom - Feature #406 (New): Abstract i2c interface to allow other OSes to work with i2chttps://ticket.coreboot.org/issues/4062022-07-28T22:47:42ZAnastasia Klimchukflashrom - Feature #379 (New): Merging Minipro code for TL866xx programmershttps://ticket.coreboot.org/issues/3792022-05-11T11:04:29ZEloy Degen
<p>David Hendricks (<a class="user active user-mention" href="https://ticket.coreboot.org/users/13">@David Hendricks</a>) expressed interest in adding support in that particular issue.</p>
<p>I think that the programmer is quite somewhat different than most programmers supported in flashrom, since the programmer itself has a database of supported flash chips and abstracts more behind hardware. Which would mean that /include/flashchips.h isn't usable in this programmer.</p>
<p>There is a working open source implementation of flashing software named minipro[1], but sparsely packaged (Fedora and CentOS, only proposed in Debian) and only supports a single programmer, instead of flashrom which is more versatile. The code of minipro is GPLv3 and flashrom is GPLv2, which are incompatible licenses. Re-implementing the entire code would make implementing a lot more work. Any suggestions how to proceed here?</p>
<p>[1] <a href="https://gitlab.com/DavidGriffith/minipro" class="external">https://gitlab.com/DavidGriffith/minipro</a></p>
flashrom - Bug #374 (Response Needed): -x option filters only spaces when converting region names...https://ticket.coreboot.org/issues/3742022-04-28T01:27:32ZAnastasia Klimchuk
<p>Also check that manpage is updated</p>
<p>Relevant patch:<br>
<a href="https://review.coreboot.org/c/flashrom/+/52450" class="external">https://review.coreboot.org/c/flashrom/+/52450</a><br>
Manpage update here <a href="https://review.coreboot.org/c/flashrom/+/52892" class="external">https://review.coreboot.org/c/flashrom/+/52892</a></p>
coreboot - Feature #328 (New): Add RAM disk/filesystem in SPI flash for tianocorehttps://ticket.coreboot.org/issues/3282021-12-30T18:33:49Zxinhua wangxinhuawang0101@gmail.com
<p>Add RAM disk/filesystem in SPI flash for tianocore</p>
coreboot - Bug #251 (New): Add SD card detect GPIO in jslrvp devicetreehttps://ticket.coreboot.org/issues/2512020-01-09T06:05:32ZAamir Bohraaamir.bohra@intel.com
<p>The SD card detect GPIO currently needs to be added once the jsl gpio driver code is merged.<br>
This bug tracks its implementation.</p>
coreboot - Bug #221 (New): ASUS KCMA-D8 doesn't POST reliably when CMOS is completely cleared of ...https://ticket.coreboot.org/issues/2212019-07-19T11:26:28ZSean Rhoneespionage724@posteo.net
<p>I noticed that if I flash Coreboot, and wipe the CMOS out completely (remove the battery and power for a bit), sometimes my system won't POST. Might work the first time, might take a reset or two, and worst-case it took 5 resets in a row for it to POST.</p>
<p>If I boot the ASUS vendor BIOS, remove the BIOS chip, and replace it with a Coreboot chip, it seemingly POSTs fine consistently.</p>
<p>For Coreboot, I'm using the CMOS for NVRAM, and also the option that loads defaults every boot.</p>
coreboot - Bug #165 (New): [ga-g41m-es2l] [coreboot 4.7] [grub] GRUB payload (launched from seab...https://ticket.coreboot.org/issues/1652018-05-05T13:56:21ZAnonymous
<p>Hello,</p>
<p>[ga-g41m-es2l] [grub] GRUB halts when trying to load linux kernel</p>
<p>I'm trying to use GRUB2 payload launched from seabios. (To make sure it works before using it as main payload)<br>
The GRUB2 payload I included in my rom is using vesafb [1][2], it loads fine from seabios but once it tries to load the first menuentry, it halts and I'm forced to reset to boot from seabios again. The keyboard doesn't respond at all as well on GRUB (USB)<br>
So I'm trying to figure out why it isn't working.<br>
The coreboot rom I'm using is 4.7-fd470f7163709c1022ee6185134a2387812774ec with :</p>
<ul>
<li>NGI</li>
<li>Linear FB</li>
<li>Seabios 1.11.0-0-g63451fc (seabios master = same issue)</li>
</ul>
<p>Is GRUB2 payload able to be launched from seabios on this board ? Or does it have to be launched as main payload ?</p>
<p>included : </p>
<ul>
<li>cbmem log (-> after a reset to seabios when grub halts)</li>
<li>nvramtool settings</li>
<li>cbfstools "print"</li>
<li>grub.cfg (extracted from libreboot rom)</li>
</ul>
<p>[1] I extracted it from a libreboot rom I was using with success previously<br>
[2] I also compiled a fresh GRUB2 payload from 2.02 release, the issue is exactly the same.</p>
<hr>
<p>Strangely, if using the exact same grub payload with coreboot 4.6-db508565d2483394b709654c57533e55eebace51 with :</p>
<ul>
<li>NGI</li>
<li>Linear FB</li>
<li>Seabios 1.10.2-0-g5f4c7b1</li>
</ul>
<p>Then GRUB2 payload works fine ! It loads my 4.9.97 kernel without issue except this little error with my keyboard (not sure why) :</p>
<p>[ 0.508007] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br>
[ 0.508552] ehci-pci: EHCI PCI platform driver<br>
[ 0.508737] SCSI subsystem initialized<br>
[ 0.508926] ehci-pci 0000:00:1d.7: EHCI Host Controller<br>
[ 0.508938] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1<br>
[ 0.508967] ehci-pci 0000:00:1d.7: debug port 1<br>
[ 0.511097] i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?<br>
[ 0.511101] i8042: If AUX port is really absent please use the 'i8042.noaux' option<br>
[ 0.511777] mpt3sas version 13.100.00.00 loaded<br>
[ 0.513408] ehci-pci 0000:00:1d.7: can't setup: -110<br>
[ 0.513475] ehci-pci 0000:00:1d.7: USB bus 1 deregistered<br>
[ 0.513508] xhci_hcd 0000:02:00.0: xHCI Host Controller<br>
[ 0.513515] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1<br>
[ 0.513590] ehci-pci 0000:00:1d.7: init 0000:00:1d.7 fail, -110<br>
[ 0.513616] ehci-pci: probe of 0000:00:1d.7 failed with error -110</p>
<p>Thanks for your help</p>
coreboot - Feature #56 (New): 16GB DIMM support on Sandy/Ivy Bridgehttps://ticket.coreboot.org/issues/562016-05-31T10:39:03ZIru Caimytbk920423@gmail.com
<p>The first 16GB DDR3L was released last year, and for Intel platforms, only Broadwell and some Atom SoCs support it. However, in the compatibility list[2], it is said that many existing boards that supports DDR3 support 16GB DDR3L, and CPUs on X79 boards can support it with a modified MRC. So I think it's possible to be supported on a Sandy/Ivy Bridge machine.</p>
<p>The raminit logs show that coreboot does the memory init, and the code in romstage that should be run in memory works fine, but it crashes on payload stage.</p>
<p>(The following is what I wrote on the mailing list)</p>
<p>Hi,</p>
<p>I'm tesing to see if the coreboot Sandy/Ivy MRC supports 16GB DIMMs. Here's my result.</p>
<p>I'm using a MT16KTF2G64HZ-1G6A1[1]. My machine is Lenovo T420 with i7-3630QM. With this module inserted (I've tested 16G+0 and 16G+8G), the system can light up, but it'll then get crashed.</p>
<ul>
<li>with GRUB2 payload, it'll crash after the payload loads</li>
<li>with SeaBIOS payload with proprietary VGABIOS, I can see the prompt, and can boot to a GRUB or syslinux loader on my USB stick, but when I try to boot a system, it get crashed. If I boot to Memtest86+ on my USB stick, the system will crash when memtest starts to test the memory.</li>
</ul>
<p>And another thing I can see is, the first boot can boot to payload, but the second boot will fail. I think it's caused by the MRC cache.</p>
<p>I'm still wondering if Sandy/Ivy northbridge can support 16GB DIMMs. I'll give a more detailed EHCI debug output later. According to [2], I think the incompatibility is an MRC issue instead of hardware incompatibility.</p>
<p>[1] <a href="https://www.micron.com/parts/modules/ddr3-sdram/mt16ktf2g64hz-1g6?pc={E1D8F1A9-3DFC-4BD2-8A1E-C26ED261EB0A}" class="external">https://www.micron.com/parts/modules/ddr3-sdram/mt16ktf2g64hz-1g6?pc={E1D8F1A9-3DFC-4BD2-8A1E-C26ED261EB0A}</a><br>
[2] <a href="http://www.intelligentmemory.com/fileadmin/download/compatibilitylist.pdf" class="external">http://www.intelligentmemory.com/fileadmin/download/compatibilitylist.pdf</a></p>