On Tue, 19 Feb 2013 15:46:08 +0100, Tuxce wrote:
On Mon, 18 Feb 2013 17:50:06 +0100
"Ralf Mardorf" wrote:
# cat /etc/adjtime
LOCAL
That's why timedatectl command fails, LOCAL must be
on the line 3 :
$ cat /etc/adjtime
0.0 0 0
0
LOCAL
Thank you :)
[root@archlinux etc]# cat adjtime
LOCAL
[
On Wed, Feb 20, 2013 at 1:31 AM, Brock.Zheng wrote:
> Hi all
>
>I found that package in community,
>The pkg has no content. The only file in it's pkg is
>a .PKGINFO file:
>
>$> tar -tf
> archlinux/community/os/x86_64/linux-tools-meta-3.8-1-x86_64.pkg.tar.xz
>.PKGINFO
>
>An
On Tue, 19 Feb 2013 17:02:54 +0100
Kwpolska wrote:
> On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf
> wrote:
> > On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen wrote:
> >>>
> >>> # timedatectl set-local-rtc 1
> >>> Failed to issue method call: Input/output error
> >>
> >>
> >> That message is
On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf
wrote:
> On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen wrote:
>>>
>>> # timedatectl set-local-rtc 1
>>> Failed to issue method call: Input/output error
>>
>>
>> That message is disconcerting (at least the error message should have
>> been clearer)
On Mon, 18 Feb 2013 17:50:06 +0100
"Ralf Mardorf" wrote:
> Hi :)
>
> after a reboot there always is an offset of -3600 sec, when running
> ntpdate.
>
> # timedatectl status | grep local
> RTC in local TZ: yes
> Warning: The RTC is configured to maintain time in the local time
> zone. Th
Hi Mike,
Lots of stuff going on, so sorry for not answering inline.
* It looks like NetworkManager and dhcpd are stepping on eachother's
toes. Maybe you want to disable dhcpd and only use NM?
* Any service that cannot deal with network devices appearing or being
rename after it is started (is b
On Tue, Feb 19, 2013 at 9:27 PM, Mike Cloaked wrote:
>
>
> So the dhcpd4 service is fast compared to the NetworkManager service.
>
> I know this discussion is now about the incorrect start of dhcpd4 - I can
move this to a new topic title if necessary.
However I looked at journalctl for the lines
On Tue, Feb 19, 2013 at 9:03 PM, Mike Cloaked wrote:
>
>> I will check which of the two is enabled - but I have since my last post
> now switched on dhcpd (server) and named services - after boot the dhcpd
> service had entered a failed state and I am now wondering if I need to add
> the systemd-
On Tue, Feb 19, 2013 at 4:33 PM, Tom Gundersen wrote:
Just to be clear: the problem is still occurring (I am confused by
> "until recently")? Was it brought on by the recent udev naming change,
> or is it a long-standing problem?
>
This is a new system that was installed very recently using the
I've been trying again with the latest kernel, 3.7.9-1-i686. My logs are
now showing what looks like a possible clue; here's what I think is the
interesting part of /var/log/Xorg.0.log.old for my last attempt to boot
using that kernel:
[ 1426.786] (II) NOUVEAU(0): NVLeaveVT is called.
[ 1426.78
Hi Mike,
On Tue, Feb 19, 2013 at 3:32 PM, Mike Cloaked wrote:
> I have a system with two ethernet sockets on the motherboard, and I have
> until very recently been finding that my network at random failed to come
> up during the boot process.
Just to be clear: the problem is still occurring (I a
I have a system with two ethernet sockets on the motherboard, and I have
until very recently been finding that my network at random failed to come
up during the boot process.
I have the ethernet cable plugged into only one of the two sockets, and
assign the names to the interfaces as eno1 and eno2
On Tue, 2013-02-19 at 09:41 +0100, Sergi Pons Freixes wrote:
> Hi All,
>
> I have the vanilla and the PAE kernels installed, and I use latter as my
> default for booting. I installed tp_smapi, and the modules are placed on
> /usr/lib/modules/extramodules-3.7-ARCH/ instead of
> /usr/lib/modules/ext
13 matches
Mail list logo
