It was the F25 1-3 workstation image. It never did finish. The network
interface changed IPs so possibly sshd didn't actually crash. I assume it was
dropping packets or something. Now I can't finish the update. I am getting
"Error: Failed to synchronize cache for repo 'updates'"
which sounds
Hi Everyone,
I've been running a raspberry pi 3 with Fedora release 25 (Twenty
Five) using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the
last 2 weeks that my Pi locks up. I tried hooking it up to an HDMI monitor,
and USB keyboard to see if the system generates any message,
On Thu, Jan 12, 2017 at 2:01 AM, Richard Ryniker wrote:
> 4.9.2 does not appear to do much good. The blank screen problem
> https://bugzilla.redhat.com/show_bug.cgi?id=1387733
> continues, and the
> kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
> message
On Sat, Jan 28, 2017 at 10:21 PM, solarflow99 wrote:
> ha! I got it to work. Had to be done manually, I have no idea why the
> ifcfg- scripts just won't take it, all it ever accepted was eth0:0 as a
> regular subinterface and thats it.
>
>
> ip link add link eth0 name
A RTC is a hardware clock. "RTC in local TZ: yes" only indicates, that
the RTC would have been in local TZ. The alternative is UTC. Please
check the warning for more information.
If you want a bit of time improvement without buying a RTC (and
configuring it...), you can use systemd-timesyncd. It
Then why do I get the warning ? Why does it say RTC in local TZ ?
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Am 31. Januar 2017 21:06:09 MEZ schrieb linux guy :
># timedatectl
> Local time: Tue 2017-01-31 12:49:07 MST
> Universal time: Tue 2017-01-31 19:49:07 UTC
>RTC time: n/a
> Time zone: America/Edmonton (MST, -0700)
> Network time on: yes
>NTP
And the documentation is very good too. That definitely helps.
https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
# timedatectl
Local time: Tue 2017-01-31 12:49:07 MST
Universal time: Tue 2017-01-31 19:49:07 UTC
RTC time: n/a
Time zone: America/Edmonton (MST, -0700)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: yes
Warning: The system is configured to read the RTC time
Which image did you install ?
On Mon, Jan 30, 2017 at 9:34 PM, Sean Omalley
wrote:
> It is acting super slow for me too. I don't know how fast my media is, but
> the update is stlll going (319/999) and it has been around 5 hours so far.
> I don't see any zombies but
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 16:00:22 UTC. The full logs are available
at
On Fri, Dec 16, 2016 at 11:02 AM, wrote:
> Hi,
>
> As I've finally managed to get Fedora 25 booting from a USB attached HDD on a
> Raspberry Pi (2B) and I wasn't really able to it documented anywhere I'd like
> to document some of the things I found before I forget.
>
> As
> Am 31. Januar 2017 00:19:01 MEZ schrieb Peter Robinson
> :
>>On Mon, Jan 30, 2017 at 9:03 PM, Alexander Petrenz
>> wrote:
>>> Hi all,
>>>
>>> since I wasn´t able to find out what´s causing those crashes I moved
>>to
>>> raspian and since then the Pi (it
13 matches
Mail list logo