On Sun, 2013-01-06 at 07:48 +0100, Hanno Hecker wrote:
* why does this only happen while I use the wheezy2 package? I've
rebuilt the initramfs now ~10 times with this, with the wheezy1 and
the sid version this never happened (and those were always
generated,
I've used the deb
On Sun, 2013-01-06 at 07:48 +0100, Hanno Hecker wrote:
... full boot log is attached, there you can see it stops while / after
installing knfsd.
My kernel log stops then as well. I think it is just because all further
output is from the proper userspace and isn't going to the kernel logs.
On Sun, 06 Jan 2013 09:37:25 +
Ian Campbell i...@hellion.org.uk wrote:
On Sun, 2013-01-06 at 07:48 +0100, Hanno Hecker wrote:
* why does this only happen while I use the wheezy2 package? I've
rebuilt the initramfs now ~10 times with this, with the wheezy1 and
the sid version this
On Sun, 2013-01-06 at 16:23 +0100, Hanno Hecker wrote:
* should udev start before qcontrol and should evdev.ko be in the
modules list? or does qcontrol switch the watchdog off w/o it?
it
seems like it works without it...
evdev.ko is only needed to handle button presses, the
On Thu, 2013-01-03 at 10:17 +, Martin Michlmayr wrote:
The device booted fine but I saw the following error:
| Error opening /dev/input/by-path/platform-gpio-keys-event: No such file or
directory
which makes me wonder whether qcontrol was really executed properly.
I finally found an old
On Sat, 05 Jan 2013 20:04:14 +
Ian Campbell i...@hellion.org.uk wrote:
Hanno, I'm afraid don't know what is causing your boot failures but I
don't think it is related to the new qcontrol package :-(
No, it's not related to qcontrol:
A few things I tried while diagnosing this today:
* Hanno Hecker hah+deb...@uu-x.de [2013-01-01 10:37]:
Martin: This is a new TS-419P II, the filename in the DHCP config
must begin with F_TS-419P2+. strings mtd4 file did not show
anything useful, but this name was requested via DHCP, visible in
tcpdump -vv.
Fixed, thanks!
--
Martin
I just installed the test package on my TS-219 (which doesn't have the
watchdog problem).
The device booted fine but I saw the following error:
| Error opening /dev/input/by-path/platform-gpio-keys-event: No such file or
directory
which makes me wonder whether qcontrol was really executed
On Thu, 2013-01-03 at 10:17 +, Martin Michlmayr wrote:
I just installed the test package on my TS-219 (which doesn't have the
watchdog problem).
The device booted fine but I saw the following error:
| Error opening /dev/input/by-path/platform-gpio-keys-event: No such file or
directory
On Tue, 2013-01-01 at 13:18 +0100, Hanno Hecker wrote:
On Tue, 1 Jan 2013 10:37:17 +0100
Hanno Hecker hah+deb...@uu-x.de wrote:
I'm not sure what happened, but I had to use the recovery boot to get a
running system again. The watchdog did not trigger, so it stayed up,
but it did not boot
On Mon, 31 Dec 2012 08:12:33 +
Ian Campbell i...@hellion.org.uk wrote:
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote:
Might be better to backport --direct instead.
This turned out to be relatively simple, thanks for the hint.
Hanno,
Could you try the packages at
On Tue, 1 Jan 2013 10:37:17 +0100
Hanno Hecker hah+deb...@uu-x.de wrote:
I'm not sure what happened, but I had to use the recovery boot to get a
running system again. The watchdog did not trigger, so it stayed up,
but it did not boot full, IIRC the only open port was 111/tcp
(portmapper). No
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote:
* Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]:
qcommand is probably right thing to use even in the Sid version,
I believe qcommand only exists in the udeb, so this won't work.
Might be better to backport --direct instead.
Package: qcontrol
Followup-For: Bug #693263
Dear Maintainer,
the qcontrol initramfs script
/usr/share/initramfs-tools/scripts/init-bottom/qcontrol tries to execute
/sbin/qcontrol --direct watchdog off
but the wheezy version (0.4.2-7+wheezy1) does not know about the --direct
switch, so the
On Sat, 2012-12-29 at 14:36 +0100, Hanno Hecker wrote:
the qcontrol initramfs script
/usr/share/initramfs-tools/scripts/init-bottom/qcontrol tries to execute
/sbin/qcontrol --direct watchdog off
but the wheezy version (0.4.2-7+wheezy1) does not know about the --direct
switch, so the script
* Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]:
qcommand is probably right thing to use even in the Sid version,
I believe qcommand only exists in the udeb, so this won't work.
Might be better to backport --direct instead.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE,
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote:
* Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]:
qcommand is probably right thing to use even in the Sid version,
I believe qcommand only exists in the udeb, so this won't work.
Might be better to backport --direct instead.
On Sat, 2012-12-29 at 14:48 +, Martin Michlmayr wrote:
* Ian Campbell i...@hellion.org.uk [2012-12-29 14:20]:
qcommand is probably right thing to use even in the Sid version,
I believe qcommand only exists in the udeb, so this won't work.
Might be better to backport --direct instead.
18 matches
Mail list logo