On Thu, Mar 24, 2011 at 2:12 AM, Roman Mamedov wrote:
> On Mon, 21 Mar 2011 10:24:13 +0500
> Roman Mamedov wrote:
>
>> I will test the machine stability for a bit more over several days, in order
>> to not come to any more misleading conclusions.
>
> Sorry for the lack of updates -- to ensure the
On Thu, Mar 24, 2011 at 1:56 AM, Nicolás Reynolds wrote:
>
> Hi all,
>
> I've noticed my Yeeloong's fan isn't working since yesterday. Sensors
> output says the fan is 117RPM though, but that's too slow to prevent
> overheating.
Did you update your EC firmware and/or your kernel?
>
> rm (Roman,
Hello,
I don't know if this is perhaps something simple, but every time I boot my
Yeeloong, the system clock is off by about 10 hours.
I fix the date/time with ntpdate, and then the clock runs correctly, without
any speed skew or pauses. But on the next boot date/time is wrong again.
I noticed t
On Thu, Mar 24, 2011 at 9:21 PM, Roman Mamedov wrote:
> Hello,
>
> I don't know if this is perhaps something simple, but every time I boot my
> Yeeloong, the system clock is off by about 10 hours.
>
> I fix the date/time with ntpdate, and then the clock runs correctly, without
> any speed skew or
On Thu, 24 Mar 2011 21:41:31 +0800
wu zhangjin wrote:
> Did you enable the kernel support?
>
> $ cat .config | grep RTC | grep -v ^#
> CONFIG_RTC_LIB=y
> CONFIG_RTC_CLASS=y
> CONFIG_RTC_HCTOSYS=y
> CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
> CONFIG_RTC_INTF_SYSFS=y
> CONFIG_RTC_INTF_PROC=y
> CONFIG_RTC_I
El 24/03/11 09:15, wu zhangjin dijo:
> On Thu, Mar 24, 2011 at 1:56 AM, Nicolás Reynolds
> wrote:
> >
> > Hi all,
> >
> > I've noticed my Yeeloong's fan isn't working since yesterday. Sensors
> > output says the fan is 117RPM though, but that's too slow to prevent
> > overheating.
>
> Did you upd
On Thu, Mar 24, 2011 at 9:47 PM, Roman Mamedov wrote:
> In dmesg I see:
>
> # dmesg | grep rtc
> [ 10.380985] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
> [ 10.381073] rtc0: alarms up to one day, 114 bytes nvram
> [ 10.926866] rtc_cmos rtc_cmos: setting system clock to 2011-03
On Thu, Mar 24, 2011 at 9:56 PM, Nicolás Reynolds wrote:
> El 24/03/11 09:15, wu zhangjin dijo:
>> On Thu, Mar 24, 2011 at 1:56 AM, Nicolás Reynolds
>> wrote:
>> >
>> > Hi all,
>> >
>> > I've noticed my Yeeloong's fan isn't working since yesterday. Sensors
>> > output says the fan is 117RPM thoug
On Thu, 24 Mar 2011 22:26:59 +0800
wu zhangjin wrote:
> So, is your /dev/rtc0 broken? please check it or recreate one like this:
>
> $ rm /dev/rtc0
> $ mknod /dev/rtc0 c 254 0
I did not do that (but see below).
>
> And can you read the date out from /proc/driver/rtc
> or /sys/class/rtc/rtc0/t
Hello,
Homepage : http://dev.lemote.com:2001/
Docs : http://dev.lemote.com:2001/archlinux/other/docs/
--
Best regards!
Heiher
--
You received this message because you are subscribed to the Google Groups
"loongson-dev" group.
To post to this group, send email to loongson-dev@googlegroups.com.
El 24/03/11 11:37, Heiher dijo:
> Hello,
>
> Homepage : http://dev.lemote.com:2001/
> Docs : http://dev.lemote.com:2001/archlinux/other/docs/
Hi, seems we have been overlapping work!
Parabola is a GNU/Linux-Libre version of Archlinux, it's the same plus
freedom :)
We have a booting system from
Hello,
ArchLinux for Lemote is supported 'mipsel' architecture, It is for ICT
Loongson CPU machines.
On Thu, Mar 24, 2011 at 11:52 PM, Nicolás Reynolds wrote:
> El 24/03/11 11:37, Heiher dijo:
>> Hello,
>>
>> Homepage : http://dev.lemote.com:2001/
>> Docs : http://dev.lemote.com:2001/archlinux/o
Sorry, I meant we have a mips64el booting system, since we have been
working on a Lemote port ourselves (besides providing i686 and x86_64
packages).
El 25/03/11 12:08, Heiher dijo:
> Hello,
>
> ArchLinux for Lemote is supported 'mipsel' architecture, It is for ICT
> Loongson CPU machines.
>
> O
Hello,
Good job!
On Fri, Mar 25, 2011 at 12:20 AM, Nicolás Reynolds wrote:
> Sorry, I meant we have a mips64el booting system, since we have been
> working on a Lemote port ourselves (besides providing i686 and x86_64
> packages).
>
> El 25/03/11 12:08, Heiher dijo:
>> Hello,
>>
>> ArchLinux for
On Tue, 22 Mar 2011 23:50:07 +0800
wu zhangjin wrote:
> I mean, you can run dmesg before the system hang to check if there are
> some call traces related to rtl8187b?
As I expected, when it locks up with WPA2 AES, it does not print anything into
netconsole. Last lines (which also repeat often du
On Thu, 24 Mar 2011 23:00:29 +0500
Roman Mamedov wrote:
> I'll now switch it to WPA TKIP and try to hit the 'second type' of lock-up,
> the one when caps-lock flashes and at least some part of the kernel is alive.
Aaaand I got it!!! Any ideas what to try for a fix?
[ 892.926980] CPU 0 Unable t
Hello!
Some good news:
A fix has been recently committed to the mainline rtl8187 driver, which for me
makes it work without issue on rtl8187b device on the Yeeloong:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6410db593e8c1b2b79a2f18554310d6da9415584
Before, I had
17 matches
Mail list logo
