Hello Helge,
Cc: += linux-i2c
On Sun, Aug 07, 2016 at 08:48:29PM +0200, Helge Wiemann wrote:
> I located the battery and removed it for 60 seconds, then booted up my NAS
> and performed your commands. My syslog and tracelog are attached.
>
> I think this made no difference. The date is still
Hello Uwe,
I located the battery and removed it for 60 seconds, then booted up my
NAS and performed your commands. My syslog and tracelog are attached.
I think this made no difference. The date is still incorrect.
Any ideas?
Helge
On 08/07/2016 11:46 AM, Uwe Kleine-König wrote:
Hello
Hello Helge,
On 08/07/2016 11:37 AM, Helge Wiemann wrote:
> apt install i2c-tools
> echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind
> i2cget -y 0 0x30 0x80
>
> This is what you asked for:
>
> 1) -bash: echo: write error: No such device
> 2) no output
> 3) i2cget -y 0 0x30 0x80
> 4)
Hello Helge,
On 08/06/2016 08:55 PM, Helge Wiemann wrote:
> Ever since I applied your patch the system clock would not sync and
> point to January 1st (1970?). Is there any way I can reverse the stuff I
> did to my NAS?
What is my patch? Can you show your boot log? What is the output on
console
Hello Uwe,
It took a little longer as I was out of town for two weeks.
Ever since I applied your patch the system clock would not sync and
point to January 1st (1970?). Is there any way I can reverse the stuff I
did to my NAS?
Once I have done that I will retest again and see if I get to
Hello,
On Tue, Jul 19, 2016 at 09:47:04PM +0200, Helge Wiemann wrote:
> I do have "/sys/bus/i2c/devices/0-0030", but did not specifically follow
> your instructions you described in the bug report. If it helps you I will,
> please let me know.
>
> I am running a cron job to switch off my NAS at
Hello Uwe,
I do have "/sys/bus/i2c/devices/0-0030", but did not specifically follow
your instructions you described in the bug report. If it helps you I
will, please let me know.
I am running a cron job to switch off my NAS at 11 PM. However, my issue
(shutting down after a short boot) was
Hello Helge,
On Mon, Jul 18, 2016 at 08:24:38PM +0200, Helge Wiemann wrote:
> Issuing...
>
> echo +150 > /sys/bus/i2c/devices/0-0030/rtc/rtc*/wakealarm
>
> ...would not work as I don't have the "rtc" directory.
But you have /sys/bus/i2c/devices/0-0030? Even if you didn't unbind the
driver
Hello Helge,
On Sun, Jul 17, 2016 at 08:25:37AM +0200, Helge Wiemann wrote:
> Sorry for my late reply, but I stopped watching this thread and relied on
> the mailing system to send me a notification (which never came). I learned
> from Martin yesterday there has been a fix and he kindly forwarded
Hello Uwe,
Sorry for my late reply, but I stopped watching this thread and relied
on the mailing system to send me a notification (which never came). I
learned from Martin yesterday there has been a fix and he kindly
forwarded your solution to me.
This is what made my problems disappear
Hello Martin,
Thank you for posting this. Although the shutdown issue disappeared
after reinstalling the entire system my NAS would still occasionally
boot and immediately shutdown for no obvious reason. A second boot would
bring the system up as expected, but it was annoying nonetheless.
I
I don't think it has been mentioned here, but Uwe Kleine-König has
found and fixed this bug!
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794266#95
--
Martin Michlmayr
http://www.cyrius.com/
Hi Martin,
Thanks for your help. I followed the given procedure and I can power off
the Qnap now.
qnap:/home/jfc# echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind
qnap:/home/jfc# i2cget 0 0x30 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will read from
Hello Helge,
On 04/17/2016 04:18 PM, Helge Wiemann wrote:
> However, all is good now.
can you try if doing:
echo +2 > /sys/class/rtc/rtc0/wakealarm
triggers the problem again?
If so,
echo 0 > /sys/class/rtc/rtc0/wakealarm
might fix it again.
Do you have something about rtc
* jfc [2016-04-20 20:21]:
> I get the same issue since I upgraded my Qnap TS-119P II | Turbo to
> Jessie. I'm not able to shutdown my Qnap anymore, it always reboot
> whatever command I use (halt, shutdown, systemctl).
I just found the bug report again (not that it contains more
Hello,
I get the same issue since I upgraded my Qnap TS-119P II | Turbo to
Jessie. I'm not able to shutdown my Qnap anymore, it always reboot
whatever command I use (halt, shutdown, systemctl).
Is there a way to fix that, without going to a fresh install?
Thanks,
jfc
Le 17/04/2016 16:18,
Martin & Roger
A quick update: I had to reinstall the entire system because of a
network glitch during a kernel upgrade which resulted in a bricked
device. After resetting my NAS and installing Jessie from scratch the
reboot issue disappeared and the system has been running well since.
So
Martin & Roger,
Appreciate your responses and continuing support.
I installed the new kernel from the backports, but to no avail. A
shutdown still results in a reboot. I even removed the qcontrol package
to see what would happen, but it makes no difference.
I also suspect it has to do with
* Roger Shimizu [2016-04-14 03:12]:
> > I think the issue is known bug in the current Kirkwood kernel, hence I don't
> > want to dwell on the subject. I upgraded to Debian Jessie recently on my QNP
> > TS-112P and ever since I have been unable to shutdown my system,
On Sat, Apr 9, 2016 at 4:54 AM, Helge Wiemann wrote:
> Hello,
>
> I think the issue is known bug in the current Kirkwood kernel, hence I don't
> want to dwell on the subject. I upgraded to Debian Jessie recently on my QNP
> TS-112P and ever since I have been unable to
20 matches
Mail list logo