Solved Librebooted macbook "--MORE--Unknown key 0xff detected"
- Login o registrati per inviare commenti
I have some good news for those of you who have a librebooted macbook 2.1 and ran into the issue of "--MORE--Unknown key 0xff detected"-spam when starting the laptop. That issue might be fixed now. For more details about the problem I refer you to:
https://trisquel.info/en/wiki/macbook
and
https://trisquel.info/en/forum/librebooted-macbook-21
I did two changes after which the problem is gone (at least hasn't appeared during the past two days).
- I compiled a recent libreboot and rom (macbook21_svenska_vesafb.rom) from source. It was at commit 7c5fc471cfcdc48086491c87773a3667ae016873 from their git repository at git://git.savannah.nongnu.org/libreboot.git
- I used the cbfstool to use my old grub.cfg in the new rom. In addition I had added the line "terminal_output --append cbmemc" into this grub.cfg. I have no idea what it does, but this was added in one of the commits since last release, which was in may this year.
So hopefully this will get rid of an extremely annoying issue for some of the more adventurous of you.
Happy new year!
This is great news! Especially since this test report listed a lot of serious issues with a recent version of libreboot on the macbook2,1. Could you please report your findings to the libreboot mailing list?
Happy GNU year!
One suitable deposit might also be h-node.
I have some good news for those of you who have a librebooted macbook 2.1 and
ran into the issue of "--MORE--Unknown key 0xff detected"-spam when starting
the laptop. That issue might be fixed now. For more details about the problem
I refer you to:
https://trisquel.info/en/wiki/macbook
and
https://trisquel.info/en/forum/librebooted-macbook-21
I did two changes after which the problem is gone (at least hasn't appeared
during the past two days).
- I compiled a recent libreboot and rom (macbook21_svenska_vesafb.rom) from
source. It was at commit 7c5fc471cfcdc48086491c87773a3667ae016873 from their
git repository at git://git.savannah.nongnu.org/libreboot.git
- I used the cbfstool to use my old grub.cfg in the new rom. In addition I
had added the line "terminal_output --append cbmemc" into this grub.cfg. I
have no idea what it does, but this was added in one of the commits since
last release, which was in may this year.
So hopefully this will get rid of an extremely annoying issue for some of the
more adventurous of you.
Happy new year!
Very good!
Eemeli,
Look at this commit just added to libreboot:
http://git.savannah.gnu.org/cgit/libreboot.git/commit/?id=0c651b42de90173206bcbfc5d5aa4e71e973177f
Can you re-compile with that latest commit, and confirm? This ought to solve that bug "--MORE--Unknown key 0xff detected" but I don't have a macbook21 to test on for confirmation.
I don't monitor this forum regularly, so it's better to confirm via IRC (ping francis7) or send an email to the libreboot mailing list. Thanks!
Using that did not change anything: removing that option from the 20150518 release did not fix the issue on my laptop. On the other hand removing it from the grub.cfg of the rom that I compiled in the first post did not make things worse. I will send a more detailed report to the mailing list soon.
This is great news! Especially since this test report listed a lot of serious
issues with a recent version of libreboot on the macbook2,1. Could you please
report your findings to the libreboot mailing list?
Happy GNU year!
One suitable deposit might also be h-node.
Very good!
Eemeli,
Look at this commit just added to libreboot:
http://git.savannah.gnu.org/cgit/libreboot.git/commit/?id=0c651b42de90173206bcbfc5d5aa4e71e973177f
Can you re-compile with that latest commit, and confirm? This ought to solve
that bug "--MORE--Unknown key 0xff detected" but I don't have a macbook21 to
test on for confirmation.
I don't monitor this forum regularly, so it's better to confirm via IRC (ping
francis7) or send an email to the libreboot mailing list. Thanks!
Using that did not change anything: removing that option from the 20150518
release did not fix the issue on my laptop. On the other hand removing it
from the grub.cfg of the rom that I compiled in the first post did not make
things worse. I will send a more detailed report to the mailing list soon.
- Login o registrati per inviare commenti