Sebastian Schwarz, Thu 2011-11-10 @ 16:36:54+0100:
> My display comes back with the minimal brightness setting. Also the
> XF86MonBrightnessUp (Fn+Up) and XF86MonBrightnessDown (Fn+Down)
> buttons stopped working. I can restore the previous brightness level
> and the buttons by running:
>
> c
On 10-11-2011 22:40, David C. Rankin wrote:
On 11/10/2011 04:16 PM, Kirill Churin wrote:
localtime is a mess, it were told here zillion times.
Maybe you'll better run Windows in virtual machine instead?
Thanks Kirill,
I have both virtualbox running in Arch, and I also have the original
drive
On 11/10/2011 04:16 PM, Kirill Churin wrote:
localtime is a mess, it were told here zillion times.
Maybe you'll better run Windows in virtual machine instead?
Thanks Kirill,
I have both virtualbox running in Arch, and I also have the original drive in
this box that boots windows. The other
On Fri, Nov 11, 2011 at 4:01 AM, David C. Rankin
wrote:
> It would seem that there are still some issues with this:
> http://blogs.msdn.com/oldnewthing/archive/2004/09/02/224672.aspx
This post is from 2004, and there are no any significant issues mentioned.
> So without an option for "localtime
On 11/10/2011 02:59 PM, C Anthony Risinger wrote:
Yeah I'm really not sure about the jump, ntp should be logging any changes
anyway (though I believe it will not change the time if greater than some
threshold)
... however, some time ago it was announced that localtime is no longer
supported for
Hi!
> -Mensaje original-
> De: arch-general-boun...@archlinux.org [mailto:arch-general-
> boun...@archlinux.org] En nombre de David C. Rankin
> Enviado el: jueves, 10 de noviembre de 2011 21:44
> Para: General Discussion about Arch Linux
> Asunto: Re: [arch-general] linux 3.1-4 - two i686
On Thu, Nov 10, 2011 at 5:08 PM, Leonid Isaev wrote:
> On (11/10/11 14:42), SanskritFritz wrote:
> -~> I saw rlocate was moved into community in 2008 and again back to aur. I
> -~> remember trying it once, but could not compile it. Now it complains
> -~> "configure: error: *** rlocate needs kerne
On 11/10/2011 02:47 PM, Leonid Isaev wrote:
OK. On top of my head I would suggest:
1. Play with clocksource (see kernel-parameters.txt).
2. Add "-ddd" to /etc/conf.d/ntpd.conf's NTPD_ARGS variable.
3. See thishttp://twiki.ntp.org/bin/view/Support/KnownHardwareIssues (might
need to disable ntpd).
On Nov 10, 2011 2:44 PM, "David C. Rankin"
wrote:
>
> On 11/10/2011 01:55 PM, Mauro Santos wrote:
>>
>> On 10-11-2011 19:16, David C. Rankin wrote:
>>>
>>>
>>> Richard, David - check your hardware clock "# hwclock -r" and compare
>>> that to the time returned by "# date". If they are hours apart,
On 10-11-2011 20:44, David C. Rankin wrote:
On 11/10/2011 01:55 PM, Mauro Santos wrote:
On 10-11-2011 19:16, David C. Rankin wrote:
Richard, David - check your hardware clock "# hwclock -r" and compare
that to the time returned by "# date". If they are hours apart, then
make sure your sysclock
On (11/10/11 14:19), David C. Rankin wrote:
-~> On 11/10/2011 01:28 PM, C Anthony Risinger wrote:
-~> >On Thu, Nov 10, 2011 at 1:16 PM, David C. Rankin
-~> > wrote:
-~> >>
-~> >> Richard, David - check your hardware clock "# hwclock -r" and compare
that
-~> >>to the time returned by "# date". If
On 11/10/2011 01:55 PM, Mauro Santos wrote:
On 10-11-2011 19:16, David C. Rankin wrote:
Richard, David - check your hardware clock "# hwclock -r" and compare
that to the time returned by "# date". If they are hours apart, then
make sure your sysclock is correct and set the hardware clock to you
On 11/10/2011 01:28 PM, C Anthony Risinger wrote:
On Thu, Nov 10, 2011 at 1:16 PM, David C. Rankin
wrote:
Richard, David - check your hardware clock "# hwclock -r" and compare that
to the time returned by "# date". If they are hours apart, then make sure
your sysclock is correct and set the
On 10-11-2011 19:16, David C. Rankin wrote:
Richard, David - check your hardware clock "# hwclock -r" and compare
that to the time returned by "# date". If they are hours apart, then
make sure your sysclock is correct and set the hardware clock to your
sysclock with "# hwclock -w". Worth checkin
On (11/09/2011 06:55 PM), Taylor Hedberg wrote:
-~> Additionally, after the first reboot following the update (which did not
-~> have the aforementioned display problems), I had issues with the display
-~> backlight after starting X.
Indeed there seems to be a problem with intel graphics. Since 3.
On Wed, Nov 09, 2011 at 07:55:22PM -0500, Taylor Hedberg wrote:
> Since updating to Linux 3.1 yesterday, I've been having strange problems
> with the display on my laptop. The first reboot after updating the
> kernel went normally, but every subsequent boot since then has had
> problems.
>
> This
Am 10.11.2011 20:16, schrieb David C. Rankin:
Richard, David - check your hardware clock "# hwclock -r" and compare
that to the time returned by "# date". If they are hours apart, then
make sure your sysclock is correct and set the hardware clock to your
sysclock with "# hwclock -w". Worth che
On (11/10/11 13:16), David C. Rankin wrote:
-~> Hmm.. Absolutely no help from the logs on the box that locked:
-~>
-~> Nov 10 03:20:04 phoenix -- MARK --
-~> Nov 10 03:25:34 phoenix dhcpd: DHCPREQUEST for 192.168.7.124 from
-~> 00:11:43:22:50:08 via eth0
-~> Nov 10 03:25:34 phoenix dhcpd: DHCPAC
On Thu, Nov 10, 2011 at 2:28 PM, C Anthony Risinger wrote:
> On Thu, Nov 10, 2011 at 1:16 PM, David C. Rankin
> wrote:
>>
>> Richard, David - check your hardware clock "# hwclock -r" and compare that
>> to the time returned by "# date". If they are hours apart, then make sure
>> your sysclock is
On 11/09/2011 06:55 PM, Taylor Hedberg wrote:
Additionally, after the first reboot following the update (which did not
have the aforementioned display problems), I had issues with the display
backlight after starting X.
Just to add to the display discussion...
On an x86_64 (with nVidia), aft
On Thu, Nov 10, 2011 at 1:16 PM, David C. Rankin
wrote:
>
> Richard, David - check your hardware clock "# hwclock -r" and compare that
> to the time returned by "# date". If they are hours apart, then make sure
> your sysclock is correct and set the hardware clock to your sysclock with "#
> hwclo
On 11/10/2011 12:56 PM, David J. Haines wrote:
On Thu, Nov 10, 2011 at 1:44 PM, Richard Schütz wrote:
Am 10.11.2011 18:47, schrieb David C. Rankin:
tpowa,
Upgraded 5 i686 boxes and 2 x86_64 boxes to linux 3.1-4 yesterday night.
This morning, one i686 server is dead, other i686 box responded
On Thu, Nov 10, 2011 at 1:44 PM, Richard Schütz wrote:
> Am 10.11.2011 18:47, schrieb David C. Rankin:
>>
>> tpowa,
>>
>> Upgraded 5 i686 boxes and 2 x86_64 boxes to linux 3.1-4 yesterday night.
>> This morning, one i686 server is dead, other i686 box responded to xterm
>> (return input) and then
Am 10.11.2011 18:47, schrieb David C. Rankin:
tpowa,
Upgraded 5 i686 boxes and 2 x86_64 boxes to linux 3.1-4 yesterday night.
This morning, one i686 server is dead, other i686 box responded to xterm
(return input) and then locked (ssh connection was left up after login
to confirm reboot). Two ot
tpowa,
Upgraded 5 i686 boxes and 2 x86_64 boxes to linux 3.1-4 yesterday night. This
morning, one i686 server is dead, other i686 box responded to xterm (return
input) and then locked (ssh connection was left up after login to confirm
reboot). Two other i686 boxes (under no load) still runni
On 11/10/2011 08:09 AM, Thomas Bächler wrote:
What you should figure out is that you don't need either of those packages.
That's all I needed to know. Thanks Thomas...
--
David C. Rankin, J.D.,P.E.
On (11/10/11 14:42), SanskritFritz wrote:
-~> I saw rlocate was moved into community in 2008 and again back to aur. I
-~> remember trying it once, but could not compile it. Now it complains
-~> "configure: error: *** rlocate needs kernel 2.6 to work".
-~> What is the status of this project now, is
Hello,
On 2011-11-09 at 19:55 -0500, Taylor Hedberg wrote:
> This is a Dell Latitude D620 laptop with the following
> graphics-related lines in the lspci output:
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
> 943/940GML Express Integrated Graphics Controller (rev 03)
Am 10.11.2011 07:21, schrieb David C. Rankin:
> Guys,
>
> I'm trying to figure out why the i686 codecs package (rm from extra
> now in aur) is so massively different from the x86_64 codecs64 package
> in aur. The i686 package seems fine, but the x86_64 package seems to be
> nothing but a shadow
On 10-11-2011 06:45, Uli Armbruster wrote:
* Taylor Hedberg [10.11.2011 01:55]:
Since updating to Linux 3.1 yesterday, I've been having strange problems
with the display on my laptop. The first reboot after updating the
kernel went normally, but every subsequent boot since then has had
problems
* Taylor Hedberg [10.11.2011 13:50]:
> Uli Armbruster, Thu 2011-11-10 @ 07:45:11+0100:
> > I can confirm this behavior, however I'm not sure if it's software
> > related. I have the impression that this happens here only if the
> > laptop is cold (e.g. because I carried it around outside in the co
I saw rlocate was moved into community in 2008 and again back to aur. I
remember trying it once, but could not compile it. Now it complains
"configure: error: *** rlocate needs kernel 2.6 to work".
What is the status of this project now, is it usable in archlinux? I find
the idea very attractive.
Uli Armbruster, Thu 2011-11-10 @ 07:45:11+0100:
> I can confirm this behavior, however I'm not sure if it's software
> related. I have the impression that this happens here only if the
> laptop is cold (e.g. because I carried it around outside in the cold
> german autumn). But Taylor's describtion
Have you tried playing with KMS, see if it changes anything enabling or
disabling it?
--
Cédric Girard
Am 10.11.2011 07:45, schrieb Uli Armbruster:
> * Taylor Hedberg [10.11.2011 01:55]:
>> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
>> 943/940GML Express Integrated Graphics Controller (rev 03)
>> 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
>> 94
35 matches
Mail list logo
