Le lundi 28 février 2011 à 18:50 +, Martin Michlmayr a écrit :
> Fortunately, LS
> Mini support is in the kernel in Debian, so I just gave you a kernel
> image that loads Mini support.
OK, thanks. I just checked out the mach-type setting for kernel images
here http://buffalo.nas-central.org/wi
Hi Antonios,
Le dimanche 27 février 2011 à 14:54 +, Antonios Galanopoulos a
écrit :
> The problem persists with the new 2.6.37 based installer although the
> dmesg output from Benjamin is much different from mine and the original
> bug reporter.
>
> The relevant dmesg output:
>
> [ 2
Le vendredi 25 février 2011 à 15:22 +, Martin Michlmayr a écrit :
> Can you boot the following installer image and see if it boots and
> finds your disk properly? (The installer itself won't work; I just
> want to know if it boots).
It boots and find my disks properly, thanks! I just tried to
Le vendredi 25 février 2011 à 12:35 +, Martin Michlmayr a écrit :
> LS-WSGL is the LS mini, right?
Yes. I'm using the lspro image thinking it also supports the mini. Then
I'm wondering: does it really support it?
benjamin
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
Le vendredi 25 février 2011 à 10:41 +0100, Benjamin Cama a écrit :
> The relevant logs are (same on both .32 and .37):
And the result of hw-report for my NAS:
uname -a: Linux debian 2.6.37-1-orion5x #1 Thu Feb 17 07:03:57 UTC 2011
armv5tel GNU/Linux
lsmod: Module Size Used
reopen 590105
thanks
Hi,
Contrary to what the bug title says, Sébastien didn't really want
support for LS-CHL at first, but rather fix its disks not being
recognized. As Antonios says, this disk controller problem also happen
on LS-WTGL, and I confirm it on LS-WSGL too (with the latest installer
Package: util-linux
Version: 2.16.2-0
Le mercredi 03 février 2010 à 03:49 +, Ben Hutchings a écrit :
> On Wed, 2010-02-03 at 03:42 +0100, Benjamin Cama wrote:
> > But still, it would be usefull to be able to set the RTC for those with
> > still a bit of juice in their battery.
Le mercredi 03 février 2010 à 02:02 +, Ben Hutchings a écrit :
> Error 22 is EINVAL and actually indicates an invalid time.
OK. I actually wanted to solve this bug to also help a bug somewhat
related to #535354, which prevent hwclock to write the hardware clock.
Actually, hwclock first read t
Hi,
I tested Ben Hutchings' patch and got this result (on a PowerBook6,8) :
rtc-generic rtc-generic: hctosys: unable to read the hardware clock
(-22)
Hope this can help solve this bug.
benjamin
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscri
9 matches
Mail list logo
