>> If you could please provide a patch detailing exactly what you would
>> like changed, that would be appreciated.
It look like the latest u-boot-tools has exactly what I would have said. Very
sorry for taking so long to get back.
I think this bug can be closed now.
Thanks!
Rick
On Jul 21, 2015, at 12:11 PM, Bastian Blank wrote:
> However I'm still unable to reproduce the problem
> without a sledgehammer.
I reproduced the problem in a tiny test system as follows:
I created a virtual machine with VMWare running on my Mac. It has a virtual
DVD-drive (loaded with the
On Jul 25, 2015, at 3:21 PM, Bastian Blank wrote:
> On Tue, Jul 21, 2015 at 07:05:42PM -0700, Rick Thomas wrote:
>> I created a virtual machine with VMWare running on my Mac. It has a virtual
>> DVD-drive (loaded with the Jessie 8.1.0 amd64 install image) and three
>>
I haven’t seen this in ages. You can close it, I think.
Rick
On Jul 18, 2014, at 7:30 AM, Pedro Beja wrote:
> Hey Rick,
>
> this is an old bug.
>
> Could you please still reproduce this issue with newer nautilus version like
> 3.4.2-1+build1 or 3.8.2-3 ?
>
> thanks
> regards
> Pedro
--
Package: u-boot-tools
Version: 2014.10+dfsg1-5
Severity: normal
When I try fw_printenv on my cubox i4Pro, it complains
Cannot parse config file: No such file or directory
Looking in
/usr/share/doc/u-boot-tools/examples/
there are several example .config files, but none for the cubox ma
Package: u-boot-tools
Version: 2015.04+dfsg1-2
Severity: wishlist
If I wish to boot into, e.g. single user mode on my arm device, I find that
there is no way to set the kernel command parameter "single" other than
by mucking with bootargs_console in ways its creator did not intend.
The problem is
On May 26, 2015, at 10:32 AM, Vagrant Cascadian wrote:
> Control: tags -1 +pending
>
> On 2015-05-26, Rick Thomas wrote:
>> When I try fw_printenv on my cubox i4Pro, it complains
>>Cannot parse config file: No such file or directory
>>
>> Looking in
On May 26, 2015, at 12:44 PM, Rick Thomas wrote:
>
> On May 26, 2015, at 10:32 AM, Vagrant Cascadian wrote:
>
>> Control: tags -1 +pending
>>
>> On 2015-05-26, Rick Thomas wrote:
>>> When I try fw_printenv on my cubox i4Pro, it complains
>>>
On May 26, 2015, at 9:30 AM, Vagrant Cascadian wrote:
> Control: title -1 way to set kernel command line parameters in u-boot
>
> On 2015-05-26, Rick Thomas wrote:
>> If I wish to boot into, e.g. single user mode on my arm device, I find that
>> there is no way to s
On 05/26/15 13:35, Vagrant Cascadian wrote:
On 2015-05-26, Rick Thomas wrote:
On May 26, 2015, at 12:44 PM, Rick Thomas wrote:
On May 26, 2015, at 10:32 AM, Vagrant Cascadian wrote:
On 2015-05-26, Rick Thomas wrote:
The entry committed may not work with older versions of u-boot, as some
of
On May 28, 2015, at 9:56 AM, Vagrant Cascadian wrote:
… lots of useful explanation … Thank you very much! Useful stuff!
>
> I suppose I should document this in README.Debian...
That would be great! Thank you!
Rick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wi
In case it helps, here’s systemctl status as logged during emergency shell.
Rick
Jul 19 22:43:49 stretch fixup[687]: + systemctl status
Jul 19 22:43:49 stretch fixup[687]: * stretch
Jul 19 22:43:49 stretch fixup[687]: State: maintenance
Jul 19 22:43:49 stretch fixup[687]: Jobs: 0 queued
On a hunch, I made the following change
> # diff /SAVE/etc/lvm/lvm.conf /etc/lvm/lvm.conf
> 823c823
> < use_lvmetad = 1
> ---
> > use_lvmetad = 0
and ran
> # update-initramfs -u
Then rebooted. The problem went away…
As I understand it, this makes LVM always check the actual physical
On May 6, 2015, at 3:35 AM, Rick Thomas wrote:
>
> On May 6, 2015, at 3:27 AM, Ian Campbell wrote:
>
>> It would be preferable to test the thing in Sid before the upload to
>> jessie-proposed-updates
>
> I’ll keep an eye out for it.
>
> But I don’t have on
On May 12, 2015, at 2:11 AM, Ian Campbell wrote:
> On Tue, 2015-05-12 at 01:33 -0700, Rick Thomas wrote:
>> On May 6, 2015, at 3:35 AM, Rick Thomas wrote:
>>
>>>
>>> On May 6, 2015, at 3:27 AM, Ian Campbell wrote:
>>>
>>>> It would be pr
Package: src:linux
Version: 4.0.2-1
Severity: normal
Tags: upstream
My cubox-i4pro armhf device has two real-time-clocks. One, snvs, is not
battery backed,
hence is not useful for setting the system clock on boot after a power failure.
The other, pcf8523, does have battery backup.
Unfortunatel
On May 16, 2015, at 3:13 AM, Ian Campbell wrote:
> On Fri, 2015-05-15 at 17:55 -0700, Rick Thomas wrote:
> [...]
>> There does not seem to be any way to over-ride this. There's code in
>> /etc/default/hwclock
>> that would do part of the work in a sysvi
On May 16, 2015, at 6:02 AM, Ben Hutchings wrote:
>> If that’s correct, I’m not sure if even sysvinit
>> with /etc/default/hwclock could have done the right thing in my case.
>
> This is not implemented directly by the init system. util-linux
> installs the script /lib/udev/hwclock-set and a u
On May 16, 2015, at 6:02 AM, Ben Hutchings wrote:
> This is not implemented directly by the init system. util-linux
> installs the script/lib/udev/hwclock-set and a udev rule that runs it
> for each RTC device. However, the hwclock-set script does nothing if
> systemd is running.
curiouser an
On May 16, 2015, at 12:58 PM, Rick Thomas wrote:
>
> On May 16, 2015, at 6:02 AM, Ben Hutchings wrote:
>
>> This is not implemented directly by the init system. util-linux
>> installs the script/lib/udev/hwclock-set and a udev rule that runs it
>> for each RTC de
Try adding
append=“ nomodeset"
to the end of the main stanza in /etc/yaboot.conf. Then (as root) execute
“ybin” to propagate the change to the bootstrap routines.
This will set the kernel command line to inhibit the kernel from trying to use
hardware acceleration for your video.
The resul
On Apr 28, 2015, at 8:02 PM, Fabio Estevam wrote:
> On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings wrote:
>
>>> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the
>>> hardware real-time-clock gets
>>> reset to midnight UTC, Dec 31, 1970.
>>> Even though the SolidRun literatu
On Apr 28, 2015, at 8:02 PM, Fabio Estevam wrote:
> On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings wrote:
>
>>> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the
>>> hardware real-time-clock gets
>>> reset to midnight UTC, Dec 31, 1970.
>>> Even though the SolidRun literatu
OK, How will I identify the upload when I see it? The box is running
Debian/Sid and I do regular updates. So presumably, I’ll see a
“linux-image-3.16.0-4-armmp” package go by sometime soon? And I’ll know I’ve
got it when I see two /dev/rtc* devices?
As for “rbtho...@cube.rcthomas.org” — I’m
On May 6, 2015, at 3:27 AM, Ian Campbell wrote:
> It would be preferable to test the thing in Sid before the upload to
> jessie-proposed-updates
I’ll keep an eye out for it.
But I don’t have one of the cubox models without the battery-backed RTC, so I
won’t be able to test that case. Is the
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: wishlist
Tags: newcomer
Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware
real-time-clock gets
reset to midnight UTC, Dec 31, 1970.
Even though the SolidRun literature says that the i4Pro has a battery backed
RTC.
A
Ben Hutchings indicates that his preference would be to disable the
non-battery-backed RTC and enable the battery-backed RTC in the kernel for the
Cubox-i4pro.
I’m not a kernel hacker, so what I’m about to say may be off the mark, but:
If I’m not mistaken, this kernel is intended to be used on
On Apr 12, 2015, at 6:10 AM, Ben Hutchings wrote:
> On Sun, 2015-04-12 at 01:37 -0700, Rick Thomas wrote:
>> Ben Hutchings indicates that his preference would be to disable the
>> non-battery-backed RTC and enable the battery-backed RTC in the kernel
>> for the Cubox-i4
Hi!
Thanks for the clarification. I see your point.
Rick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I’ve seen this bug today.
System drops into emergency mode for reasons that have nothing to do with this
bug. Network is active when in emergency shell. I type root password then
immediately exit, system continues to boot. When boot is finished, network is
not active.
system journal of ful
interfaces
Description: Binary data
This is “fresh out of the box” as it comes from the debian installer process.
I have made no changes.
Rick
On Apr 17, 2015, at 2:57 PM, Michael Biebl wrote:
> Am 17.04.2015 um 22:49 schrieb Rick Thomas:
>>
>> I’ve seen this bug today
On Apr 17, 2015, at 3:17 PM, Michael Biebl wrote:
> Am 17.04.2015 um 23:43 schrieb Rick Thomas:
>> Package: systemd
>> Version: 215-16
>> Severity: important
>>
>> When /etc/fstab has an ext4 filesystem on a logical volume which is itself
>> on a software
On Apr 17, 2015, at 3:44 PM, Michael Biebl wrote:
>
> Thanks for the data.
> Looks like an lvm issue to me:
>
> root@cube:~# lvscan
> inactive '/dev/vg1/backup' [87.29 GiB] inherit
>
> and as a result, /dev/disk/by-label/BACKUP is missing.
Yes, that’s true, of course. But the quest
Hi Michael,
Thanks very much for helping me with this. (continued following quoted material)
On Apr 21, 2015, at 11:17 AM, Michael Biebl wrote:
> control: tags -1 moreinfo unreproducible
>
> Am 18.04.2015 um 02:02 schrieb Rick Thomas:
>>
>> On Apr 17, 2015, at 3:44 PM,
On Apr 22, 2015, at 8:17 AM, Michael Biebl wrote:
> Could you copy /lib/systemd/system/lvm2-activation.service to
> /etc/systemd/system and add a line
> After=mdadm-raid.service
> to the [Unit] section.
Will do. Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Apr 22, 2015, at 8:17 AM, Michael Biebl wrote:
> Am 22.04.2015 um 12:10 schrieb Rick Thomas:
>> This works. Interestingly, without the sleep loop the vgchange
>> fails.
>>
>> Now, you say that a VM with two virtual disks configured as RAID1
>> with a logi
On Apr 21, 2015, at 11:17 AM, Michael Biebl wrote:
> If you have the sysvinit package installed,
> you can try booting with sysvinit temporarily via
> init=/lib/sysvinit/init on the kernel command line.
>
> Does that work?
I had to install sysvinit. And I had to make up a suitable /etc/initta
On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote:
> Can you boot with systemd.log_level=debug on the kernel command line and
> attach the journal output of this boot, so we have more information out
> the timing, i.e. when certain services are started
>
> There might be a race somewhere, i.e. l
On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote:
> There might be a race somewhere, i.e. lvm2-activation(-early).service
> being run *before* mdadm has assembled the RAID.
>
> You could test this theory, be artifically delaying those two services.
> Copy them to /etc/systemd/system, and add a
On Apr 23, 2015, at 2:31 PM, Michael Biebl wrote:
> Am 23.04.2015 um 21:47 schrieb Rick Thomas:
>>
>> On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote:
>>
>>> There might be a race somewhere, i.e. lvm2-activation(-early).service
>>> being ru
Package: mdadm
Version: 3.3.4-1
Severity: important
Cubox-i system has a RAID6 array of usb-keys (it's just an experiment -- I'd
never use it in a production system)
Runs Debian Sid. I recently did an upgrade that replaced
mdadm_3.3.4-1_armhf.deb with mdadm_3.3.4-1.1_armhf.deb.
Reboot following
Package: cryptsetup
Version: 2:1.6.6-5
Severity: important
Under Wheezy, I was able to put "keyscript=/lib/cryptsetup/scripts/passdev"
in /etc/crypttab to make it use a key file on a USB stick
Now with jessie, this doesn''t work.
The relevant lines from /etc/crypttab look like this:
aux
/d
I tested Marcello’s workaround. It works! That’s wonderful! Thank you so
much, Marcello!
Now some further thoughts on the subject…
It’s a workaround for this bug, but, unfortunately it’s just a workaround not a
real fix. In particular, using a “luks=no” kernel command line option disables
On Oct 16, 2015, at 3:02 AM, Marcello Barnaba wrote:
>> On Sat, 19 Mar 2011 03:40:25 +0100 Mourad De Clerck wrote:
>> my root and swap partition are encrypted with cryptsetup; root uses a custom
>> keyscript and swap uses the cryptsetup-provided "decrypt_derived" keyscript.
>> systemd seems to b
On Oct 16, 2015, at 9:20 AM, Marcello Barnaba wrote:
>
>>> Workaround: add "luks=no" to the kernel command line to disable systemd's
>>> generator:
>>> http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator.html
>
>> Does this work for encrypted root as well? Or is it
Package: inetutils-inetd
Version: 2:1.9.2.39.3a460-3
Severity: wishlist
Dear Maintainer,
inetd does not listen on IPv6 ports, only IPv4.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500,
'stable'),
Christoph provided a patch with the initial bug report in April 2013. Can we
get this fix into the Jessie release? Please! Hasn’t it been long enough?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
On Jan 25, 2016, at 8:07 AM, Kilian Krause wrote:
> Package: u-boot
> Severity: wishlist
> Tags: d-i
>
> Hi Vagrant,
>
> as just discussed the d-i mimic of installing u-boot should also be
> available when updating u-boot packages in an installed system.
>
> There may be cases, where automati
On Jan 31, 2016, at 11:37 AM, Kilian Krause wrote:
> If you have the impression that "most" of the
> ARM systems out there are only equipped with a single boot device that's not
> removable, please do give a list. Otherwise, unbricking a vfat or ext4
> partition on a PC should be piece of cake.
On Jan 31, 2016, at 2:42 PM, Rick Thomas wrote:
> boot from internal MMC flash that is soldered to the mainboard.
Sorry, *not* "MMC flash". That *should* be "MTD flash".
see:
http://www.linux-mtd.infradead.org/faq/general.html
for an explanation of the difference.
Enjoy!
Rick
Package: installation-reports
Severity: normal
Dear Maintainer,
First, I upgraded U-boot on the machine to version "2014.10+dfsg1-5"
Second, I downloaded uImage and uInitrd from
https://d-i.debian.org/daily-images/armel/daily/kirkwood/netboot/marvell/sheevaplug/
and put them on a USB stick (
On Jan 6, 2016, at 9:10 AM, Vagrant Cascadian wrote:
>> So I guess it’s all explained by https://bugs.debian.org/781874 .
>
> I really don't understand the logic outlined in that bug report, and
> your results don't exactly come to the same conclusion, which is why
> I've never "fixed" it.
Wel
On Jan 6, 2016, at 12:59 PM, Rick Thomas wrote:
> At a minimum, the patch in bug#781874 needs to be applied in order to be
> compatible with modern version of u-boot.
Oooops! Sorry! Brain-fart… The patch doesn’t do what I thought it did.
What I should have said is:
At a minimum, th
On Jan 7, 2016, at 7:25 PM, Martin Michlmayr wrote:
> So it sounds like you had:
> - standard
> - SSH server
> - print server
>
>> tmpfs tmpfs 102788 348102440 1% /run
>> /dev/sda2 ext4 2065152 1878636 61896 97% /
>
> I'm surprised it took 1.8 GB.
>
>
On Jan 7, 2016, at 9:07 PM, Martin Michlmayr wrote:
> * Patryk Hanckowiak [2015-07-24 00:58]:
>> The guided LVM encrypted partitioning layout does not create a separate /usr
>> partition and creates a 8-10 GB / (root) partition. This happens in both
>> separate /var, /tmp, /home installer optio
Package: u-boot
Version: 2014.10+dfsg1-5
Severity: wishlist
Dear Maintainer,
I have two OpenRD machines, a "Client" and an "Ultimate" that I'm willing to
use for testing new releases.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates')
Package: apticron
Version: 1.1.58
Followup-For: Bug #812719
Dear Maintainer,
I see the same problem. Stock, out of the box, stretch installation.
I have tested the fix in the original bugreport. It works.
Thanks!
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT
Package: python-gnuplot
Version: 1.8-6
Severity: normal
Dear Maintainer,
* What led up to the situation?
Installed python-gnuplot then unpacked and ran the demo.py from
/usr/share/doc/python-gnuplot/examples
* What was the outcome of this action?
error/warning messages were not expected, th
On Wed, 24 Feb 2016 15:06:27 -0800 Vagrant Cascadian wrote:
> On 2016-02-24, Vagrant Cascadian wrote:
> > On 2016-02-04, Ben Hutchings wrote:
> >> Oh, so the MODULES=most case is bust and we need to list more host
> >> controller drivers (or include all modules under drivers/usb/host/).
> >> How a
Package: s-nail
Version: 14.8.5-4
Followup-For: Bug #806858
Dear Maintainer,
So what, exactly, are the correct permissions for s-nail-privsep?
Should it be:
-rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep
or:
-rwsr-xr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-n
This problem persists in mdadm_3.3.4-1.1+b1_armhf.
Attached is the output of dmesg after booting, dropping into emergency mode,
running “systemctl restart mdadm-raid” and typing “exit” resulting in boot
completion.
dmesg-mdadm_3.3.4-1.1+b.out
Description: Binary data
Rick
Package: src:linux
Version: 4.3.3-5~bpo8+1
Severity: normal
Dear Maintainer,
The 4.3.0.0 kernel on an "OpenRD Client" fails to recognize the SD card --
there is no mmc device shown by lsblk.
This is fixed by using a modified DTB file provided by Aaro Koskinen.
Fix tested by Rick Thom
Hi Aaro,
Andrew wrote
> On Sun, Jan 17, 2016 at 11:55:19PM -0800, Rick Thomas wrote:
>>
>> On Jan 17, 2016, at 2:42 PM, Martin Michlmayr wrote:
>>> * Andrew Lunn [2016-01-10 16:38]:
>>>> Please can you try the following patch. If this works, i can add it
> On Jan 20, 2016, at 2:54 PM, Aaro Koskinen wrote:
>
> I can add more verbose comments to mainline kernel .dts on how to
> enable serial port, and how to select between rs232/485. Andrew, do
> you want me to resend the current patches, or can it be done with an
> incremental patch?
>
> However
Package: u-boot-tools
Version: 2016.01+dfsg1-1
Severity: wishlist
I believe the following to be true based on experiments with my two
sheevaplugs:
If your Sheevaplug has a u-boot version prior to 2014.10+dfsg1-5,
including any of the original "Marvell" versions, the environment is
located at 0x6
Package: ntp
Version: 1:4.2.6.p5+dfsg-2+deb7u1
Severity: wishlist
Dear Maintainer,
NTP version 4.2.8 includes over 1000 bug fixes and new features,
including final replacement and deprecation of the ntpdc command.
We should consider upgrading.
Anything I can do to help, let me know...
-- Syste
Package: installation-reports
Followup-For: Bug #834974
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was attempting a test installation of the new Stretch release.
* What exactly did you do (or not do) tha
I re-installed u-boot on the uSDcard. And with that, it booted up a treat.
So somehow the u-boot binary on the uSDcard is getting clobbered in the
installation process.
Rick
On Jun 24, 2017, at 8:41 AM, Cyril Brulebois wrote:
> Hi Rick,
>
> Rick Thomas (2017-06-23):
>> I re-installed u-boot on the uSDcard. And with that, it booted up a
>> treat.
>>
>> So somehow the u-boot binary on the uSDcard is getting clobbered in
>>
Oooops!
syslog is mode 600, and I wasn’t root when I created the cpio archive.
Here is is
syslog.gz
Description: GNU Zip compressed data
Sorry!
Rick
On Jun 24, 2017, at 2:23 PM, Cyril Brulebois wrote:
> Hi again,
>
> Rick Thomas (2017-06-24):
>> I did attach all the log
On Feb 10, 2017, at 12:43 PM, Cyril Brulebois wrote:
> Hi,
>
> Karsten Merker (2017-02-10):
>> when using the "Guided - use entire disk" option, partman by
>> default clobbers the boot sector and the area after it (where
>> u-boot is located) to make sure that there are no remains of old
>> pa
Great! Is there an installer image somewhere I can test this with on my
Cubox-i4x4 ?
Thanks!
Rick
On Jul 15, 2017, at 3:21 PM, Debian Bug Tracking System
wrote:
> Your message dated Sat, 15 Jul 2017 22:17:18 +
> with message-id
> and subject line Bug#854822: fixed in partman-base 191+de
12:08 schrieb Rick Thomas:
>> Main PID: 477 (code=exited, status=228/SECCOMP)
> ...
>> Kernel: Linux 4.6.0-1-marvell
>
> That looks like you are using a custom kernel. Is the problem
> reproducible with the default Debian Linux kernel?
>
>
> --
> Why
Description: Binary data
On Jul 28, 2016, at 1:24 PM, Michael Biebl wrote:
> Am 28.07.2016 um 22:01 schrieb Rick Thomas:
>> No. This is a stock kernel. It’s available from both testing and unstable
>> repos. The machine itself is a SheevaPlug. Nothing custom about it.
>>
&g
/SECCOMP)
Any other thoughts?
Rick
On Jul 28, 2016, at 2:04 PM, Michael Biebl wrote:
> Am 28.07.2016 um 22:50 schrieb Rick Thomas:
>> In the interest of having a working system, I reverted that machine to
>> systemd version 230-7. Unsurprisingly, the problem went away.
>
Hmmm… Curiouser and curiouser!
I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The
problem is *not* present there.
The problem may be specific to arm hardware? I’ll try it on a PowerPC G4
(Apple Mac PPC) machine later today.
Rick
On Jul 28, 2016, at 5:18 PM, Rick
(including the systemd version in question) and it does *not* have
the problem. This is the same result I saw on the amd64 (virtual) machine.
So it seems to be arm specific…
Any thoughts?
On Jul 29, 2016, at 3:02 PM, Michael Biebl wrote:
> Am 29.07.2016 um 23:29 schrieb Rick Thomas:
>
Has anyone else noticed this bug?
Bug#832713: systemd: after "systemd (231-1) unstable" update
systemd-jurnald.service fails to start
I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on both.
I’ve also tried it on amd64 and powerpc hardware. The bug is not present there.
Thanks, Christian!
What is your armel box? I *do* see it on my SheevaPlug (armel), so there may
be a clue. Is your armel kernel customized in some way?
Enjoy!
Rick
> On Jul 30, 2016, at 11:33 PM, Christian Marillat wrote:
>
> On 30 juil. 2016 23:02, Rick Thomas wrote:
>
&
Can you send the output of ‘uname -a ; systemd —version’ on that box?
Thanks!
On Jul 31, 2016, at 12:22 AM, Christian Marillat wrote:
> On 31 juil. 2016 08:50, Rick Thomas wrote:
>
>> Thanks, Christian!
>>
>> What is your armel box? I *do* see it on my SheevaPlug
On Jul 31, 2016, at 2:02 AM, Christian Marillat wrote:
> On 31 juil. 2016 10:50, Rick Thomas wrote:
>
>> Can you send the output of ‘uname -a ; systemd —version’ on that box?
>
> Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4.6-1+rpi14 (2016-05-05) armv7l
> GNU/Linux
>
Thanks for you help so far, Michael!
Can I ask one last favor on this?
It seems that the bug (whatever it is) depends on things like kernel version
and machine architecture.
So, can you suggest someone who can take this further?
Thanks!
Rick
This 8 year old bug is still present in jessie and stretch — the change to
systemd did not fix it!
Please, somebody pay attention! This bug makes ntpd unreliable tending to
useless on systems that get their network config from dhcp.
Rick
Package: ntpdate
Version: 1:4.2.6.p5+dfsg-7+deb8u2
Severity: important
during system startup ntpdate starts before dhcpclient finishes. hence ntpdate
can't find its server so it dies and fails to set the clock.
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT polic
3d:bd:bc
> Aug 01 02:49:47 dillserver ifup[671]: Sending on Socket/fallback
> Aug 01 02:49:47 dillserver ifup[671]: DHCPDISCOVER on eth0 to 255.255.255.255
> port 67 interval 4
>
On Aug 1, 2016, at 2:56 AM, Kurt Roeckx wrote:
> On Mon, Aug 01, 2016 at 02:37:58AM -0700, Rick Thomas wr
8.25
> May 18 03:53:30 ultimate ntpd[399]: Soliciting pool server 129.250.35.250
> May 18 03:53:31 ultimate ntpd[399]: Soliciting pool server 50.116.55.65
The DHCPACK that assigns the IP address to the interface occurs during the
middle of ntpd’s startup, so two of three pool statements get
On Aug 1, 2016, at 2:56 AM, Kurt Roeckx wrote:
> On Mon, Aug 01, 2016 at 02:37:58AM -0700, Rick Thomas wrote:
>> This 8 year old bug is still present in jessie and stretch -- the change to
>> systemd did not fix it!
>>
>> Please, somebody pay attention! This bug ma
On Aug 1, 2016, at 6:32 AM, Kurt Roeckx wrote:
>>
>> The DHCPACK that assigns the IP address to the interface occurs during the
>> middle of ntpd's startup, so two of three pool statements get failed DNS.
>> The third one succeeds, so ntpd gets some servers, but not all the servers
>> it's
On Aug 1, 2016, at 2:40 PM, Felipe Sateler wrote:
> On 28 July 2016 at 17:04, Michael Biebl wrote:
>> Am 28.07.2016 um 22:50 schrieb Rick Thomas:
>>> In the interest of having a working system, I reverted that machine to
>>> systemd version 230-7. Unsurprisi
On Aug 2, 2016, at 11:15 PM, Michael Biebl wrote:
> Am 01.08.2016 um 23:40 schrieb Felipe Sateler:
>> So I think the kernel should enable SECCOMP.
>
> I agree, unless SECCOMP on arm has some unwanted side-effects.
> Felipe, can you file a bug report against the linux package accordingly?
It ma
On Aug 3, 2016, at 9:06 AM, Felipe Sateler wrote:
> On 1 August 2016 at 18:32, Rick Thomas wrote:
>>
>> Thanks, Filipe!
>>
>> What do we have to do at this point to test this and then translate it into
>> a patch?
>
> OK, so I have a proof-of-concept
> On Aug 3, 2016, at 3:58 PM, Felipe Sateler wrote:
>
> On 3 August 2016 at 16:44, Rick Thomas wrote:
>>
>> On Aug 3, 2016, at 9:06 AM, Felipe Sateler wrote:
>>
>>> On 1 August 2016 at 18:32, Rick Thomas wrote:
>>>>
>>>> Thank
On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian wrote:
> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian wrote:
>>> On 2016-09-17, Rick Thomas wrote:
>>>> On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian wrote:
>>>>>
On Nov 2, 2016, at 10:38 AM, Vagrant Cascadian wrote:
> I've uploaded u-boot 2016.11~rc3 to the cascadia.debian.net
> repository. I won’t hold my breath, but give it a try...
I will. No promises on the target date, but “soon”! (-;
> Another option which might help debug the issue is to build
On Nov 18, 2016, at 10:22 AM, Martin Michlmayr wrote:
> * Philipp Kern [2016-11-18 17:19]:
>>> Thanks for the CC. I just added wget-udeb and it adds 345 KB,
>>> which breaks the orion5x-qnap image. However, this image is really
>>> quite a special case and I don't want to block https support
On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian wrote:
> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that…
Will do. Sometime this weekend.
>
>> let me know if there’s anything more I can do to help…
>
> If it's not fixed in 2016.11~rc1, the only thing left to try
On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote:
> I'd be curious if you re-install and delete each partition individually
> and re-create manually vs. using one of the auto-partitioning methods.
I’ll give this a try over the weekend and report back what I find.
Is it possible that the aut
On Sep 2, 2016, at 4:40 PM, Gunnar Wolf wrote:
> Can somebody confirm whether the Jessie
> installer actually works reliably on this machine? (that is, whether
> it's always been broken or we have a regression)
I’ll give that a try as well over the weekend. Let you know what I find.
Rick
On Sep 2, 2016, at 6:30 PM, Rick Thomas wrote:
>
> On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote:
>
>> I'd be curious if you re-install and delete each partition individually
>> and re-create manually vs. using one of the auto-partitioning methods.
>
&g
> On Sep 2, 2016, at 6:33 PM, Rick Thomas wrote:
>
>
> On Sep 2, 2016, at 4:40 PM, Gunnar Wolf wrote:
>
>> Can somebody confirm whether the Jessie
>> installer actually works reliably on this machine? (that is, whether
>> it's always been broken or we ha
201 - 300 of 612 matches
Mail list logo
