His Chromebook isn't a Chromebook, it's a Thinkpad x230, but it's a similar principle.
I'm okay without kudos or karma or any of those things. :) On 04/07/17 20:29, Zoran Stojsavljevic wrote: > Yup. John was right. The date on your Chromebook is Sun Aug 16 > 11:22:22 CEST 2161 > > Looking to your log, I found the first problem (I read thread after I > found auditd log portion and decipher the time): > > [ 2.489343] audit: type=1400 audit(6047083342.480:2): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/sbin/dhclient" pid=489 comm="apparmor_parser" > [ 2.489350] audit: type=1400 audit(6047083342.480:3): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=489 > comm="apparmor_parser" > [ 2.489355] audit: type=1400 audit(6047083342.480:4): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=489 > comm="apparmor_parser" > [ 2.489358] audit: type=1400 audit(6047083342.480:5): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/connman/scripts/dhclient-script" pid=489 > comm="apparmor_parser" > [ 2.492907] audit: type=1400 audit(6047083342.484:6): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/lightdm/lightdm-guest-session" pid=488 > comm="apparmor_parser" > [ 2.492914] audit: type=1400 audit(6047083342.484:7): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=488 > comm="apparmor_parser" > [ 2.493976] audit: type=1400 audit(6047083342.484:8): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/snapd/snap-confine" pid=501 comm="apparmor_parser" > [ 2.493985] audit: type=1400 audit(6047083342.484:9): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" > pid=501 comm="apparmor_parser" > [ 2.497248] audit: type=1400 audit(6047083342.488:10): > apparmor="STATUS" operation="profile_load" profile="unconfined" > name="/usr/sbin/cups-browsed" pid=503 comm="apparmor_parser" > > Just do the CLI command: date -d @6047083342.488 and you'll see. > > By that time (Y2161) I'll look something like this (200Y old > man): > https://s-media-cache-ak0.pinimg.com/originals/b1/c9/8f/b1c98fb01833bdbd06513a3ffc8f6590.jpg > > There are other problems (as well) in your dmesg log. But not to spoil > the situation (KUDOS to John). If you find anything else wrong, just > scream! ;-) > > Zoran > > On Tue, Jul 4, 2017 at 7:08 PM, John Lewis <[email protected] > <mailto:[email protected]>> wrote: > > \o/ ;) > > > On 04/07/17 17:36, Marcel Maci wrote: > > Hi, this is really too silly - it was the system date and time!!! > > And what confused me additionally was that I used > > > > date -s ".." > > > > instead of: > > > > sudo date -s ".." > > > > (And at the beginning I didn't realize that the system date hadn't > > changed ...) > > > > So, no need to investigate more about this case: it works! > > > > > > --- > > Am Tue, 4 Jul 2017 13:35:12 +0100 > > schrieb John Lewis <[email protected] > <mailto:[email protected]>>: > > > >> Hi Guys, > >> > >> On Chromebooks, it's quite easy for the time to go completely wrong > >> because of no CMOS battery (so you lose the time and get something > >> stupid if the battery completely drains or is disconnected), which > >> then stops Network Manager from being able to connect (at least > with > >> wifi), for reasons best known to devs ... > >> > >> In systemd based distros you need to use timedatectl to correct > such a > >> situation. If it's not that then please ignore me. > >> > >> Regards, > >> > >> John. > >> > >> > >> On 04/07/17 13:27, Zoran Stojsavljevic wrote: > >>> Hello Marcel, > >>> > >>> Which OS you are using on the top of Coreboot/SeaBIOS? I assume > >>> Linux. If Linux, could you, please, post your complete dmesg > log of > >>> the current session after you are fully up and running user space? > >>> > >>> Thank you, > >>> Zoran > >>> > >>> On Mon, Jul 3, 2017 at 5:23 PM, Marcel Maci <[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] <mailto:[email protected]>>> wrote: > >>> > >>> > >>> Hi, I've flashed coreboot with seaBIOS and me_cleaner to my > >>> Thinkpad x230 and everything works fine except the network. > Neither > >>> wifi nor ethernet works. Could this be a problem with the gbe.bin > >>> I've used (I extracted it with ifdtool -x from the factory > bios and > >>> the first time I did this on another Thinkpad x230 it worked > >>> perfectly)? > >>> > >>> -- > >>> coreboot mailing list: [email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] <mailto:[email protected]>> > >>> https://mail.coreboot.org/mailman/listinfo/coreboot > <https://mail.coreboot.org/mailman/listinfo/coreboot> > >>> <https://mail.coreboot.org/mailman/listinfo/coreboot > <https://mail.coreboot.org/mailman/listinfo/coreboot>> > >>> > >>> > >>> > >>> > >
-- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
