So my understanding is: - some redboot + kernel combo doesn't set RTC correctly on boot anymore; it looks like it's because the I2C chip isn't initialized properly: redboot-200918/dmesg-bad:sgtl5000-i2c 1-000a: Device initialisation failed redboot-200925/dmesg-bad:sgtl5000-i2c 1-000a: Device initialisation failed redboot-ubuntu-cold/dmesg-good:sgtl5000-i2c 1-000a: SGTL5000 revision 0 redboot-ubuntu-hot/dmesg-good:sgtl5000-i2c 1-000a: SGTL5000 revision 0 - some apps in Ubuntu can't deal with a time before epoch; we should fix the time at some point in the boot of the installer; we don't want to do this for all boots, but I think we can have a special case in the installer to set a post-epoch date to make sure Xorg apps work (I'm guessing Xorg apps use timestamps starting from epoch which can't be negative or something similar)
Could FSL folks please comment on whether the kernel or RedBoot is broken here? My testing matrix is: - Babbage 2 RedBoot + 2.6.28 Babbage 2 kernel: seems to work (no warning, didn't check the time) - Ubuntu Babbage 1 RedBoot + 2.6.28 Babbage 2 kernel: works - Ubuntu Babbage 1 RedBoot + Ubuntu Babbage 1 kernel: works - recent Babbage 1 RedBoot + 2.6.28 Babbage 2 kernel: breaks Thanks, -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
