-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Intel Apollo Lake" #238
Comments
Is this log from upstream flashrom? Looks like Chromium/Chrome OS flashrom. |
Hello,
Short answer is (I believe) Chromium/Chrome OS from the SSH (ctrl+shift+t)
terminal in developer mode.
Should there be anything else I can do from my end to provide additional
information just let me know.
I had been playing with both the Linux and SSH (ctrl+shift+t) terminals
looking to increase functionality while exploring what might be the most
intuitive build environment for me.
I'd meant to add more to the issue however as I was also messing with
Chrome flags I crashed the system.
Honestly, part time I've been learning (teaching myself) to code and use
commands in an effort to better move forward the shared vision of Sovereign
Wealth US. It's simply not within my means to continue paying for further
development or a webmaster.
Kind regards,
Lee
…On Sat, Jan 22, 2022, 12:51 PM Angel Pons ***@***.***> wrote:
Is this log from upstream flashrom? Looks like Chromium/Chrome OS flashrom.
—
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMVKMGDDRIKTAHSZT6MPK63UXLVAXANCNFSM5MQA5PWA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Right, so it's most likely Chrome OS flashrom. Upstream flashrom doesn't have this problem. Just to be sure, it would be nice if you could provide a full log. |
Thanks for getting back to me Angel,
Honestly beyond trying to scroll through the command history and rerunning
the code to recreate the full log... Save for one providing some other
snipit of code. Not sure how else one may retrieve the log.
That being said, I haven't the device on me just now.
…On Mon, Jan 24, 2022, 7:46 AM Angel Pons ***@***.***> wrote:
Right, so it's most likely Chrome OS flashrom. Upstream flashrom doesn't
have this problem. Just to be sure, it would be nice if you could provide a
full log.
—
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMVKMGCXBSR4QCBNTC6SKB3UXVC4BANCNFSM5MQA5PWA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Warning: unexpected second chipset match: "Intel Apollo Lake"
ignoring, please report lspci and board URL to flashrom@flashrom.org
with 'CHIPSET: your board name' in the subject line.
Found Winbond flash chip "W25Q128.JW.DTR" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
Block protection could not be disabled!
Reading flash... done.
SUCCESS
FMAP REGION: RW_LEGACY
Name Offset Type Size Comp
payload 0x0 simple elf 53662 none
seavgabios.rom 0xd200 optionrom 28672 none
links 0x14240 raw 796 none
bootorder 0x145c0 raw 465 none
etc/boot-menu-key 0x14800 raw 8 none
etc/boot-menu-message 0x14880 raw 28 none
etc/boot-menu-wait 0x14900 raw 8 none
(empty) 0x14980 null 2012696 none
The text was updated successfully, but these errors were encountered: