<div dir="ltr">How did you set the date? There's a change in recent Fedoras where using the "date" command or ntpdate , then rebooting won't store the date in the RTC. You need to use hwclock to set the hardware RTC.<div>
<br></div><div>Gnome UI and ntpd will do the right thing. I don't like this change either, <a href="https://bugzilla.redhat.com/show_bug.cgi?id=816752" target="_blank" style="font-size:13px;font-family:arial,sans-serif">https://bugzilla.redhat.com/show_bug.cgi?id=816752</a></div>
<div><br></div><div><br></div><div><br></div><div><br></div><div>m</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 12, 2014 at 12:18 PM, Tim Moody <span dir="ltr"><<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I checked out the rtc today. I set date and rebooted. The date does not persist.<div class="im HOEnZb"><br>
<br>
Tim<br>
-----Original Message----- From: Jon Nettleton<br></div><div class="im HOEnZb">
Sent: Tuesday, February 25, 2014 4:17 PM<br></div><div class="HOEnZb"><div class="h5">
To: xsce-devel<br>
Cc: <a href="mailto:server-devel@lists.laptop.org" target="_blank">server-devel@lists.laptop.org</a><br>
Subject: Re: [XSCE] cubox wifi<br>
<br>
I am not 100% sure what is enabled and what isn't but I believe<br>
wifi/esata/bluetooth are all working.<br>
<br>
<a href="https://github.com/jmontleon/fedora-20-cubox-i4pro" target="_blank">https://github.com/jmontleon/<u></u>fedora-20-cubox-i4pro</a><br>
<a href="https://github.com/jmontleon/fedora-20-cubox-i4pro-binary" target="_blank">https://github.com/jmontleon/<u></u>fedora-20-cubox-i4pro-binary</a><br>
<br>
Should be a good start. That is a mainline kernel not my patched 3.10<br>
kernel so there are some things that aren't supported but those are<br>
mostly multimedia/graphics related.<br>
<br>
-Jon<br>
<br>
On Tue, Feb 25, 2014 at 3:46 PM, Jon Nettleton <<a href="mailto:jon.nettleton@gmail.com" target="_blank">jon.nettleton@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
George,<br>
<br>
I agree, but the device-tree cookbook description is not as simple as<br>
the legacy way of setting up a new kernel. There are lots of<br>
variables that need to be taken into account depending on the kernel<br>
version, board version, u-boot version OS etc. Writing a proper<br>
cookbook is time I just don't have. Hopefully one of the other<br>
contributors will step up and get it done.<br>
<br>
-Jon<br>
<br>
On Tue, Feb 25, 2014 at 3:43 PM, George Hunt <<a href="mailto:georgejhunt@gmail.com" target="_blank">georgejhunt@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jon,<br>
<br>
In the long run, (my opinion), a cookbook description (similar to the<br>
solidrun link) of the process would be more needed than a tarball. Your<br>
time, and our education, has real value.<br>
<br>
<br>
On Tue, Feb 25, 2014 at 12:44 AM, Jon Nettleton <<a href="mailto:jon.nettleton@gmail.com" target="_blank">jon.nettleton@gmail.com</a>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
George,<br>
<br>
Things have actually changed a bit as the new kernel is using the new<br>
device-tree based configuration. I will build you guys a testing<br>
kernel tarball and u-boot in a little bit.<br>
<br>
-Jon<br>
<br>
On Tue, Feb 25, 2014 at 12:18 AM, George Hunt <<a href="mailto:georgejhunt@gmail.com" target="_blank">georgejhunt@gmail.com</a>><br>
wrote:<br>
> Hi Jon,<br>
><br>
> Is it correct that I can follow the directions at:<br>
><br>
><br>
><br>
> <a href="http://imx.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard" target="_blank">http://imx.solid-run.com/wiki/<u></u>index.php?title=Building_the_<u></u>kernel_and_u-boot_for_the_<u></u>CuBox-i_and_the_HummingBoard</a><br>
><br>
> with a clone from the github link you provided at<br>
> <a href="https://github.com/linux4kix/linux-linaro-stable-mx6" target="_blank">https://github.com/linux4kix/<u></u>linux-linaro-stable-mx6</a>? Are there any<br>
> gotchas?<br>
> Recommendations?<br>
><br>
> I forget the details from one month/day to the next.<br>
><br>
><br>
> On Mon, Feb 24, 2014 at 9:38 AM, Jon Nettleton > <<a href="mailto:jon.nettleton@gmail.com" target="_blank">jon.nettleton@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Finally out and ready for use.<br>
>><br>
>> <a href="https://github.com/linux4kix/linux-linaro-stable-mx6" target="_blank">https://github.com/linux4kix/<u></u>linux-linaro-stable-mx6</a><br>
>><br>
>> All the hardware is functional at this point. The wifi driver is a<br>
>> bit chatty and needs a bit more love for AP mode. Everything else<br>
>> from crypto to esata should be good to go.<br>
>><br>
>> -Jon<br>
>><br>
>> On Sun, Feb 23, 2014 at 5:28 PM, Jon Nettleton<br>
>> <<a href="mailto:jon.nettleton@gmail.com" target="_blank">jon.nettleton@gmail.com</a>><br>
>> wrote:<br>
>> > It was probably a UHS capable card. We found some hardware design<br>
>> > problems that will need to be rectified to support UHS speeds for >> > the<br>
>> > sdcard. For now we will be limiting the card-slot to standard SD<br>
>> > high<br>
>> > speed modes of 50Mhz which equates to around 20MB/s<br>
>> ><br>
>> > On Sun, Feb 23, 2014 at 5:12 PM, Tim Moody <<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a>> >> > wrote:<br>
>> >> sounds great. one thing I noticed in Haiti was that I could not >> >> get<br>
>> >> a<br>
>> >> 16G<br>
>> >> sd card to be recognized. is this expected or was it my card?<br>
>> >><br>
>> >> Tim<br>
>> >> -----Original Message----- From: Jon Nettleton<br>
>> >> Sent: Sunday, February 23, 2014 11:03 AM<br>
>> >> To: xsce-devel<br>
>> >> Cc: <a href="mailto:server-devel@lists.laptop.org" target="_blank">server-devel@lists.laptop.org</a><br>
>> >> Subject: Re: [XSCE] cubox wifi<br>
>> >><br>
>> >><br>
>> >> Tim,<br>
>> >><br>
>> >> Actually the 3.10 kernel is done. The wifi driver is a little<br>
>> >> chatty<br>
>> >> and I will work on sorting that out but it is functional. I am >> >> just<br>
>> >> cleaning up the last few patches and will be pushing the kernel >> >> for<br>
>> >> initial testing in a few hours.<br>
>> >><br>
>> >> -Jon<br>
>> >><br>
>> >> On Sat, Feb 22, 2014 at 5:34 PM, Tim Moody <<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a>> >> >> wrote:<br>
>> >>><br>
>> >>> Jon,<br>
>> >>><br>
>> >>> Can you (or anyone else) tell me where to find the drivers for >> >>> the<br>
>> >>> cubox<br>
>> >>> wifi adapter you mentioned on the call on Tue.<br>
>> >>><br>
>> >>> Thanks,<br>
>> >>><br>
>> >>> Tim<br>
>> >><br>
>> >><br>
><br>
><br>
</blockquote>
<br>
<br>
</blockquote></blockquote>
<br>
______________________________<u></u>_________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org" target="_blank">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/<u></u>listinfo/server-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br> <a href="mailto:martin.langhoff@gmail.com" target="_blank">martin.langhoff@gmail.com</a><br> - ask interesting questions<br> - don't get distracted with shiny stuff - working code first<br>
~ <a href="http://docs.moodle.org/en/User:Martin_Langhoff" target="_blank">http://docs.moodle.org/en/User:Martin_Langhoff</a>
</div>