[coreboot] Re: mailing list changes
Great work, Patrick. And thank you for spending your holidays on this special gift for all of us in the coreboot community!StefanOn Dec 25, 2018 07:40, Patrick Georgi via coreboot wrote:Hi everybody,I took the opportunity of the slow season to make some changes to the mail server configuration: it's moved to another server and the mailing lists are now driven by mailman3 (before: mailman2) with hyperkitty as mailing list archive system (before: pipermail).I'm still importing and otherwise handling the archives, but the mailing list should work now. For you, I hope that the only impact will be that mailman3 has a new user management concept that manages users on a per-server basis and not per mailing list like mailman2 did. This means that your mailman credentials are void and you'll have to request new ones.If you notice anything odd with the mailing list, I'd appreciate a heads-up.Thanks,Patrick-- Google Germany GmbH, ABC-Str. 19, 20354 HamburgRegistergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: HamburgGeschäftsführer: Paul Manicle, Halimah DeLaine Prado ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Status on Dell OptiPlex 7010 support
在 2018/12/25 上午3:05, Kumonie Williams 写道: > Hello there, I have a question regarding coreboot. > > I was wondering if work was still being done to port coreboot to the > Dell OptiPlex 7010. I was looking at commit > 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board > didn’t boot at that stage in time. I have also not found much > information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, > so I was wondering if work was still being The upstream coreboot repository doesn't have these two commits. What source tree are you using? OptiPlex 7010 is still on gerrit https://review.coreboot.org/c/coreboot/+/25095. > done to port coreboot to the OptiPlex 7010, given its stock firmware > doesn’t really work that great (I'd be happy to elaborate), even at > revision A29, so I wanted to replace it with coreboot. > > Thanks. > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] mailing list changes
Hi everybody, I took the opportunity of the slow season to make some changes to the mail server configuration: it's moved to another server and the mailing lists are now driven by mailman3 (before: mailman2) with hyperkitty as mailing list archive system (before: pipermail). I'm still importing and otherwise handling the archives, but the mailing list should work now. For you, I hope that the only impact will be that mailman3 has a new user management concept that manages users on a per-server basis and not per mailing list like mailman2 did. This means that your mailman credentials are void and you'll have to request new ones. If you notice anything odd with the mailing list, I'd appreciate a heads-up. Thanks, Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Status on Dell OptiPlex 7010 support
Hello there, I have a question regarding coreboot. I was wondering if work was still being done to port coreboot to the Dell OptiPlex 7010. I was looking at commit 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board didn’t boot at that stage in time. I have also not found much information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, so I was wondering if work was still being done to port coreboot to the OptiPlex 7010, given its stock firmware doesn’t really work that great (I'd be happy to elaborate), even at revision A29, so I wanted to replace it with coreboot. Thanks. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Asus Chromebox Panther: no HW RNG?
On Sat, Dec 22, 2018 at 12:05 AM Angel Pons wrote:
>
> Hello,
>
> On Sat, Dec 22, 2018, 08:50 Grant Grundler >
>> On Wed, Nov 28, 2018 at 1:51 AM Ivan Ivanov wrote:
>> >
>> > Sorry but I think that relying on Intel RNG is a _Terrible_ idea
>> > regarding the security and not sure you should be pursuing it.
>>
>> What I'm pursueing is a reasonable initialization time so
>> wpa_supplicant can start. 555 seconds is not reasonable:
>> [ 555.496678] random: crng init done
>> [ 555.496678] random: crng init done
>> [ 555.496684] random: 7 urandom warning(s) missed due to ratelimiting
>> [ 560.265385] wlp2s0: authenticate with xx:xx:xx:xx:xx:xx
>> [ 560.279395] wlp2s0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
>> [ 560.281981] wlp2s0: authenticated
>>
>> intel-crng was proposed elsewhere as one solution to this problem but
>> it's clear to me now that this is not an option with the panther
>> chromebox.
>>
>> I don't recall seeing this with older kernels (have been running
>> debian on this HW since early 4.x releases) and will look at the
>> driver git logs.
And I found one commit which I believe is likely the issue (need to
confirm this still):
commit dc12baacb95f205948f64dc936a47d89ee110117
Author: Theodore Ts'o
Date: Wed Apr 11 14:58:27 2018 -0400
random: use a different mixing algorithm for add_device_randomness()
This change _could_ cause devices that don't have input or have
wireless networking (which doesn't get initialized until
wpa_supplicants gets a value back from /dev/random) to take a very
long time for crng_init to increment and finally determine "random:
crng init done" (in crng_reseed()).
But I need to compare v4.17 behavior (where I think this was
introduced) with v4.16 or just revert this with my own 4.18 kernel
build.
I'm using the following git commands to compare differences in releases:
git diff v4.16..v4.17 -- drivers/char/random.c
git diff v4.17..v4.18 -- drivers/char/random.c
(same parameters with "log" instead of "diff" to see the corresponding
commit messages)
...
>> I experimented with attaching just an optical mouse and that didn't
>> seem to help.
>> Attaching a keyboard and just hitting key did seem to help
>> ("crng init done" in about 10 seconds). I'm assuming the /dev/random
>> driver is not seeing enough actiivity otherwise.
>
> I have observed the same behavior on Debian Sid, I would have to smash
> my keyboard a few times to generate enough entropy. I don't see anything
> similar with Arch Linux. Maybe it has to do with distro-specific packaging?
> I haven't checked.
Does Arch-Linux kernel include the CL above?
ie Is Arch linux offering a 4.17 (or later) kernel?
cheers,
grant
ps. I realize this is the wrong forum to discuss a fix ... just want
to wrap up the conversation here to confirm my theory that this might
be a coreboot issue is wrong.
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
