On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote:
On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote:
Here's an idea. First extract the real initrd from the back half of the
initrd:
ijc@dagon:tmp$ cat /boot/initrd.img | ( cpio -t 2 ; cat )
initrd.real
On Sun, 2015-05-10 at 13:45 +0100, Ian Campbell wrote:
I'm thinking that the best way to approach this would be to upload the
workaround to Sid and wait for it to propagate to Stretch, so it gets some
degree of real world testing and then upload the workaround upload to
Jessie-pu
and carry
On Tue, 2015-05-19 at 12:52 +0100, Steve McIntyre wrote:
+CONFIG_USB_XHCI_PLATFORM=y
This guy seems to match on:
static const struct of_device_id usb_xhci_of_match[] = {
{ .compatible = generic-xhci },
{ .compatible = xhci-platform },
{ .compatible =
On Tue, 2015-05-19 at 20:02 +0100, Ian Campbell wrote:
On Tue, 2015-05-19 at 12:52 +0100, Steve McIntyre wrote:
+CONFIG_USB_XHCI_PLATFORM=y
This guy seems to match on:
static const struct of_device_id usb_xhci_of_match[] = {
{ .compatible = generic-xhci },
{ .compatible
On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
Note that despite the memory setting above, the dom0 has not been allocated
exactly the amount asked for:
# xl list 0
NameID Mem VCPUsState Time(s)
Domain-0
On Sun, 2015-05-03 at 15:21 +0100, Ben Hutchings wrote:
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal
Tags: upstream
On the OpenBlocks AX3-4, the kernel logs these messages at every boot:
[1.853325] rtc-mv d0010300.rtc: internal RTC not ticking
[1.863449]
On Sun, 2015-05-17 at 15:14 +0100, Ian Campbell wrote:
On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
Note that despite the memory setting above, the dom0 has not been allocated
exactly the amount asked for:
# xl list 0
NameID Mem
On Mon, 2015-04-06 at 12:08 +0200, Sjoerd Simons wrote:
For reference when using linux-image-3.19.0-trunk-armmp this would add ~8
mbyte
of dtb files to /boot, current linux-next's multi_v7 configuration generates
around ~11 mbyte of dtb files.
That's a gain of a couple of M in the space of a
On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
Bug #776448 claims to have fixed this problem, however it seems that the
fix is incomplete?
Yes, it was. It looks like I was even told and didn't notice:
http://article.gmane.org/gmane.comp.emulators.xen.devel/230401 :-/
I'll queue
On Sun, 2015-05-17 at 14:51 +0100, Ian Campbell wrote:
On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
Bug #776448 claims to have fixed this problem, however it seems that the
fix is incomplete?
Yes, it was. It looks like I was even told and didn't notice:
http://article.gmane.org
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 sysvinit setup, but it seems to be
ignored under systemd.
[...]
Presumably, there is systemd magic that
On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote:
On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote:
according to the documentation the option ucode=scan should tell XEN to
look for a microcode update in an uncompressed initrd.
While I don’t use the Debian
Thanks Atom2, thanks for the refs, I've added the Debian bug and the
submitter back to the CC.
On Wed, 2015-05-13 at 22:11 +0200, Atom2 wrote:
Am 13.05.15 um 15:41 schrieb Ian Campbell:
I think I remember some discussion of something in this area not too
long ago on xen-devel. CC-s added.
I
I think I remember some discussion of something in this area not too
long ago on xen-devel. CC-s added.
Konrad, do you know of any issues with ucode=scan in 4.4?
On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote:
Package: xen-hypervisor-4.5-amd64
Version: 4.5.0-1
Severity: normal
On Wed, 2015-05-13 at 11:57 -0400, Konrad Rzeszutek Wilk wrote:
according to the documentation the option ucode=scan should tell XEN to
look for a microcode update in an uncompressed initrd.
While I don’t use the Debian kernel the tools to generate the initrd are
part of Debian.
On Tue, 2015-05-12 at 17:28 +0200, zer0 divide wrote:
Package: xen-hypervisor-4.5-amd64_4.5.0-1_amd64.deb
Version: 4.5.0-1
Hi,
I use xen with sdl, not with vnc. When I boot on
xen-hypervisor-4.4-amd64, everything is fine. With Debian or Windows
8.1 I have a good display,
But when I
Control: tag -1 +upstream +forwarded
On Sun, 2015-05-10 at 12:33 +1000, Russell Coker wrote:
Package: xen-utils-4.4
Version: 4.4.1-9
Severity: normal
# /usr/lib/xen-4.4/bin/xl create -c /etc/xen/katana
Parsing config from /etc/xen/katana
libxl: error: libxl_utils.c:217:logrename: failed
On Tue, 2015-05-12 at 01:33 -0700, Rick Thomas wrote:
On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote:
On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote:
It would be preferable to test the thing in Sid before the upload to
jessie-proposed-updates
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
qcontrol (0.5.4-2) UNRELEASED; urgency=medium
* Update Vcs-* to point to anonscm.
+ * Install and enable systemd unit files and corresponding udev rule.
+(Closes: #781886)
-- Ian Campbell i...@debian.org Sun, 14 Sep 2014
On Sat, 2015-05-09 at 03:41 +0200, Romain Mourier wrote:
[...]
xen-create-image --hostname=test0 --lvm=raid10 --fs=ext4
--bridge=br-lan --dhcp --dist=jessie
[...]
root@hv0:~# xl create /etc/xen/test0.cfg xl console test0
What does /etc/xen/test0.cfg contain? I suspect it is reusing the
On Sat, 2015-05-09 at 14:07 +0200, Romain Mourier wrote:
On 09/05/2015 13:25, Ian Campbell wrote:
On Sat, 2015-05-09 at 03:41 +0200, Romain Mourier wrote:
[...]
xen-create-image --hostname=test0 --lvm=raid10 --fs=ext4
--bridge=br-lan --dhcp --dist=jessie
[...]
root@hv0:~# xl
Control: reassign -1 xen-tools 4.5-1
Reassigning to xen-tools as discussed, full BR quoted below.
@xen-tools: I think this is because xen-tools has used the host
initramfs and hence has inherited some sort of hook script which insists
on the RAID stuff being present, which there isn't in the
Thanks, I'll take a look when I finally get a spare moment!
On Sun, 2015-05-03 at 13:24 -0500, David Lechner wrote:
Yes, you guessed correctly. The v2 patch is the good one.
On 05/03/2015 03:19 AM, Ian Campbell wrote:
Hi David,
On Fri, 2015-04-24 at 21:25 -0500, David Lechner wrote
Resending with a more obvious subject.
The workaround I describe in the final paragraph does seem to work, but
I'm not sure that's the best way to go.
On Mon, 2015-05-04 at 15:31 +0100, Ian Campbell wrote:
(CC initramfs-tools@packages, context is flash-kernel invocation not
being deferred via
Control: submitter -1 Rick Thomas rbtho...@pobox.com
On Wed, 2015-05-06 at 03:00 -0700, Rick Thomas wrote:
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
Package: dnsmasq
Followup-For: Bug #783459
Dear Maintainer,
After upgrading to 2.62-3+deb7u2 on Wheezy/armel dnsmasq now fails to start
with:
root@yog-sothoth:~# dpkg -i dnsmasq*2.62-3+deb7u2*.deb
(Reading database ... 25941 files and directories currently installed.)
Preparing to
On Sat, 2015-05-02 at 17:21 +0100, Ian Campbell wrote:
We typically build RTCs statically (for this sort of reason) so it seems
like the right thing for us to do here is to build both in.
Which I've now done in SVN. Rick, please test the next upload.
Also, Rick, I'm getting messages from my
On Wed, 2015-05-06 at 11:34 +0200, Salvatore Bonaccorso wrote:
I just tried to replicate that configuration and set up a wheezy VM up with
two
interfaces eth0, eth1, and set the following modifications:
interface=eth1
bind-interfaces
domain=example.com
Maintainer: Ian Campbell i...@debian.org
Changed-By: Ian Campbell i...@debian.org
Description:
dnsmasq- Small caching DNS proxy and DHCP/TFTP server
dnsmasq-base - Small caching DNS proxy and DHCP/TFTP server
dnsmasq-utils - Utilities for manipulating DHCP leases
Changes:
dnsmasq (2.62-3
On Wed, 2015-05-06 at 16:16 +0200, Salvatore Bonaccorso wrote:
Could either of you try to rebuild dnsmasq in a clean chroot and see
if the problem resolves?
Just kicked off sbuild --dist wheezy --arch armel --binNMU=1
dnsmasq_2.62-3+deb7u2.dsc on a local machine whose chroot _should_ be
clean
(CC initramfs-tools@packages, context is flash-kernel invocation not
being deferred via triggers during upgrade and ultimately running
several times in a dist-upgrade)
On Sat, 2015-04-04 at 10:49 +0100, Ian Campbell wrote:
At first glance it seems like invocations via the initramfs-tools hooks
On Sun, 2015-05-03 at 00:40 +0100, Ben Hutchings wrote:
On Sat, 2015-05-02 at 20:09 +0100, Ben Hutchings wrote:
On Sat, 2015-05-02 at 16:35 +0100, Ian Campbell wrote:
[...]
Essentially if Boot-Device is set then Boot-*-Path should be relative to
that device, if Boot-Device is not set
On Sat, 2015-05-02 at 20:09 +0100, Ben Hutchings wrote:
It seems that the code which handles the Boot-Device case is buggy in
the face of a firmware partition which has some hierarchy to it.
If the boot images need to be in a specific subdirectory then it's not
so unreasonable to expect
Hi David,
On Fri, 2015-04-24 at 21:25 -0500, David Lechner wrote:
Tags: patch
I botched the first patch. This one fixes it correctly.
Thanks for the patch(es). The buglog at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783278 has somehow
ended up with the message ordering confused.
I'm
On Tue, 2015-04-21 at 09:12 -0700, Vagrant Cascadian wrote:
Package: flash-kernel
Version: 3.35
Severity: wishlist
Tags: patch
This patch adds a few improvements to the uboot-generic bootscript:
* Use kernel version in versioned files
* Include kernel version, device and partition in
On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote:
load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} \
- load ${device} ${partition} ${fdtaddr} ${pathprefix}dtb-${kvers} \
+ load ${device} ${partition} ${fdtaddr}
${pathprefix}dtbs-${kvers}/${fdtfile} \
+
On Sun, 2015-05-03 at 13:10 +0100, Ben Hutchings wrote:
On Sun, 2015-05-03 at 08:35 +0100, Ian Campbell wrote:
On Sun, 2015-05-03 at 00:40 +0100, Ben Hutchings wrote:
On Sat, 2015-05-02 at 20:09 +0100, Ben Hutchings wrote:
On Sat, 2015-05-02 at 16:35 +0100, Ian Campbell wrote
Control: forwarded -1
https://mail.gna.org/public/cryptodev-linux-devel/2015-04/msg00011.html
On Wed, 2015-04-29 at 15:06 +0200, JM wrote:
Following the update from Wheezy to Jessie, mv_cesa crypto module
fails two kernel self-checks:
Hi JM,
Looks like you've already took this to upstream,
On Wed, 2015-04-29 at 09:57 +0100, Russell King - ARM Linux wrote:
On Sat, Apr 11, 2015 at 01:08:50AM +0100, Ben Hutchings wrote:
If this RTC is not battery backed, it seems like it ought to be disabled
in this board's device tree.
It's not that simple.
On the lower-end models, the
On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote:
Package: flash-kernel
Version: 3.35
Severity: wishlist
Tags: patch
Hi Vagrant,
The following patch prefers the use of the dtb file identified by the
u-boot variable ${fdtfile}, which makes it easier to support installs
where a
On Sun, 2015-04-26 at 00:39 +0100, Ben Hutchings wrote:
On Sat, 25 Apr 2015 23:39:44 +0100 Ben Hutchings b...@decadent.org.uk wrote:
Secondly, if the installation uses LVM, /dev/sda1 is the /boot
partition, not the root partition. After fixing the first problem,
flash-kernel fails like
On Sat, 2015-04-04 at 14:13 +0200,
debbug.jessie.upgradereport.nospam@sub.noloop.net wrote:
On Sat, Apr 04, 2015 at 10:52:35 +0100, Ian Campbell wrote:
On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote:
** error: apt-get dist-upgrade broke during a flash-kernel
This happened
(CCing Nobuhiro who contributed the flash-kernel db entry for this
device)
On Sat, 2015-05-02 at 15:40 +0100, Ian Campbell wrote:
On Sun, 2015-04-26 at 00:39 +0100, Ben Hutchings wrote:
On Sat, 25 Apr 2015 23:39:44 +0100 Ben Hutchings b...@decadent.org.uk
wrote:
Secondly
On Wed, 2015-04-08 at 18:16 +0200, Andreas Beckmann wrote:
[...]
This seems to be the only grub-* package leaving (lots of) stuff
around after purge.
Looking at the postinst/postrm code it seems that actually the inverse
is true, only grub-pc is cleaning up after itself (and then only
On Wed, 2015-04-29 at 15:33 -0700, Rick Thomas wrote:
On Apr 29, 2015, at 12:35 PM, Karsten Merker wrote:
On Tue, Apr 28, 2015 at 04:55:40AM -0700, Rick Thomas wrote:
On Apr 10, 2015, at 4:20 AM, Karsten Merker mer...@debian.org wrote:
On Fri, Apr 10, 2015 at 03:07:31AM -0700, Rick Thomas
Source: linux
Version: 3.16.7-ckt9-2
X-Debbugs-Cc: leif.lindh...@linaro.org, woo...@wookware.org, st...@einval.com
Control: notfound -1 3.17-1~exp1
Control: submitter -1 Mark Rutland mark.rutl...@arm.com
On Thu, 2015-04-30 at 17:01 +0100, Mark Rutland wrote:
Hi Ian,
Hi Mark,
Such things are
Control: reassign -1 flash-kernel flash-kernel/3.34
Third time's the charm!
On Mon, 2015-04-20 at 15:47 -0400, Samuel Bronson wrote:
Control: reasssign -1 flash-kernel flash-kernel/3.34
On Sat, 04 Apr 2015 10:49:14 +0100 Ian Campbell i...@debian.org wrote:
Control: clone -1 -2
Control
On Sat, 2015-05-02 at 17:12 +0100, Russell King - ARM Linux wrote:
On Sat, May 02, 2015 at 05:01:04PM +0100, Ian Campbell wrote:
So is your advice for a multi platform kernel supporting all Cubox
devices to just enable both and to sort out any syncing/naming etc in
userspace?
I don't see
On Tue, 2015-04-21 at 14:07 +0100, Ian Campbell wrote:
On Tue, 2015-04-21 at 13:31 +0200, Wolodja Wentland wrote:
Package: src:linux
Version: 3.16.7-ckt4-3~bpo70+1
Severity: important
Hello,
ever since upgrading some of our Xen dom0s to the kernel in backports at
that time
--- oldsys-preseed-3.15/debian/changelog2015-02-26 03:55:12.0
+
+++ oldsys-preseed-3.16/debian/changelog2015-04-21 06:07:22.0
+0100
@@ -1,3 +1,11 @@
+oldsys-preseed (3.16) unstable; urgency=medium
+
+ [ Ian Campbell ]
+ * Avoid exiting prematurely on arm*/orion5x
On Tue, 2015-04-21 at 13:31 +0200, Wolodja Wentland wrote:
Package: src:linux
Version: 3.16.7-ckt4-3~bpo70+1
Severity: important
Hello,
ever since upgrading some of our Xen dom0s to the kernel in backports at
that time (3.16.7-ckt4-3~bpo70+1) we are seeing domU freezes with output such
Package: oldsys-preseed
Version: 3.15
Severity: grave
Tags: patch
Doing a test install of jessie on my TS-419 I get asked (via the serial)
for a serial port and a ssh password. I happen to have a serial port but
these devices mostly do not and are supposed to be headless.
I'm using the images
On Mon, 2015-04-20 at 19:11 +0100, Ian Campbell wrote:
By commenting out that one line things seem to progress in a way which
looks promising (i.e. much more spew than above). I think the most
plausible solution would be:
diff --git a/oldsys-preseed b/oldsys-preseed
index f60196f..4cd7138
On Wed, 2015-04-15 at 23:39 +0200, Cyril Brulebois wrote:
Karsten Merker mer...@debian.org (2015-04-15):
On Tue, Apr 14, 2015 at 06:42:57PM -0700, Vagrant Cascadian wrote:
Did some troubleshooting (far more than I expected, now I remember
why I hadn't already done this for BBB), and came
On Thu, 2015-04-16 at 09:53 +0200, Michael Stapelberg wrote:
I can’t recall seeing this (qcontrol works fine on my qnaps) and I
don’t have time to debug this, sorry.
No problem, I'll keep digging and hit up pkg-systemd lists for help.
Ian.
--
To UNSUBSCRIBE, email to
On Thu, 2015-04-16 at 10:28 +0200, reportbug wrote:
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
@reportbug (sorry I don't seem to know your real name), could you try
adding a call to udev settle to the qcontrold initscript, in the start
case right before the daemon
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
BTW, when this fails the system still booted and you could login and fix
it, i.e. it didn't stall the boot or anything, is that right? If that is
the case a release note might
On Wed, 2015-04-15 at 17:35 +0200, Michael Biebl wrote:
[...]
pkg-systemd-maintainers, see above: is there a way to wait for udev devices
to be available? What’s the current take on udev-settle, would that be a
reasonable workaround for this situation?
Possible solutions, in order of
On Tue, 2015-04-14 at 10:02 +0200, Michael Stapelberg wrote:
Ian, it seems like you should be following
https://wiki.debian.org/systemd/Packaging#Using_debhelper_with_dh_systemd to
get the package to properly pick up the systemd service files
I tried this (in preparation for the changes I
On Wed, 2015-04-15 at 21:07 +0200, Michael Stapelberg wrote:
I’ve added the systemd service files manually on my qnaps
before I
contributed them upstream, hence I never ran into this
issue.
What did you do manually? Does it match what I
On Fri, 2015-04-10 at 06:45 +0200, Gérald wrote:
Source: u-boot
Severity: normal
Tags: d-i patch
Dear Maintainer,
Device tree support for sheevaplug was enabled in commit
9a5e0a7d5bd0e1758fcc59db524c1695d0dab7e0
The patch from commit 9a5e0a7d5bd0e1758fcc59db524c1695d0dab7e0 must be
On Tue, 2015-04-14 at 10:02 +0200, Michael Stapelberg wrote:
Apr 02 12:08:28 hostname systemd[1]: Started LSB: Start
qcontrol daemon.
This line in the logfile indicates that systemd is using the sysvinit
script (hence the “LSB: ” prefix) of qcontrold, not the native
On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote:
** error: apt-get dist-upgrade broke during a flash-kernel
This happened on the two QNAP TS-419P+ devices but not on the QNAP
TS-219P II Turbo device. The apt-get dist-upgrade stage aborted in
a flash-kernel trigger that failed, because
On Sat, 2015-04-04 at 14:48 +0200, reportbug wrote:
Package: qcontrol
Version: 0.5.4-1
Severity: normal
After a recent wheezy-jessie upgrade, I noticed that qcontrol sometimes
fails to start on boot (or qcontrold? not sure what the difference is).
qcontrold starts the qcontrol daemon at
On Fri, 2015-03-27 at 06:47 -0700, Marc MERLIN wrote:
On Fri, Mar 27, 2015 at 08:10:31AM +, Ian Campbell wrote:
Control: retitle -1 initramfs-tools: does not support CONFIG_MODULE_COMPRESS
On Fri, 2015-03-27 at 00:31 -0700, Marc MERLIN wrote:
Sure, there you go
Now I see
On Sat, 2015-03-28 at 19:04 +, Adam D. Barratt wrote:
On Fri, 2015-03-27 at 10:01 +, Ian Campbell wrote:
Please unblock package flash-kernel both deb and udeb.
flash-kernel-installer will automatically install u-boot-tools as needed, so
installation via the installer works fine
On Sat, 2015-03-28 at 08:33 +, Marc Kleine-Budde wrote:
since linux kernel version 3.16 the OpenRD boards have been converted
to device tree.
Exclusively? My understanding was that while DT support became available
earlier the board file support was not removed for most kirkwood
platforms
+
@@ -1,3 +1,11 @@
+flash-kernel (3.34) unstable; urgency=medium
+
+ * Update u-boot-tools to Recommends. In practice it is needed on most systems
+but having it installed only by flash-kernel-installer means it is missed
+in manual configurations. (Closes: #780994)
+
+ -- Ian Campbell
Control: retitle -1 initramfs-tools: does not support CONFIG_MODULE_COMPRESS
On Fri, 2015-03-27 at 00:31 -0700, Marc MERLIN wrote:
Sure, there you go
Now I see the problem. It runs
modprobe --all --set-version=3.19.2-amd64-i915-volpreempt-20141114
--ignore-install --quiet --show-depends
Control: forcemerge 781002 781205
On Mon, 2015-03-23 at 16:20 -0500, Richard Jasmin wrote:
nope. No such luck. Initrd still is missing the kernel's modules.
Could you try:
/bin/sh -x /usr/sbin/mkinitramfs -o /tmp/foo $VERSION 2/tmp/log
(for $VERSION which lacks modules) and attach the
On Tue, 2015-03-24 at 09:29 +, Steve McIntyre wrote:
On Tue, Mar 24, 2015 at 08:55:49AM +, Ian Campbell wrote:
On Thu, 1970-01-01 at 00:49 +, Martin Stigge wrote:
That's easily resolved by installing the u-boot-tools package, but I would
have expected that do be a dependency
On Thu, 1970-01-01 at 00:49 +, Martin Stigge wrote:
That's easily resolved by installing the u-boot-tools package, but I would
have expected that do be a dependency in that case. I see that it's a
Suggests, but looks rather essential to me.
u-boot-tools is not a strict requirement for
On Thu, 2015-02-05 at 20:04 -0800, Azeem Esmail wrote:
Works with 0.6.3 (v0.6.3-766_gfde0d6d)
Does not work with 0.6.3 latest code (dailies version).
What are these the versions of?
At first reboot, the screen freezes with the following message:
mount: mounting /sys on /root/sys failed:
Control: severity -1 important
Control: tags -1 +unreproducible +moreinfo
On Wed, 2015-02-25 at 12:19 +, Ian Campbell wrote:
On Sat, 2015-02-21 at 23:27 +0900, Mark Brown wrote:
On Sat, Feb 21, 2015 at 10:31:19AM +, Ian Campbell wrote:
On Sat, 2015-02-21 at 11:39 +0900, Mark Brown
On Thu, 2015-03-05 at 12:25 +0100, Cyril Brulebois wrote:
OK. Assuming amd64 is working OK, I should check the rsync has not
broken - that seems to be the most likely cause right now. Thinking:
it would also be lovely to verify the versions of vmlinuz and the
kernel udebs in debian-cd at
On Wed, 2015-03-04 at 22:44 +, B.R. Oake wrote:
On 04/03/15 22:20, maximilian attems wrote:
they are already removed in the repository for experimental,
waiting for 3.19.X for the next upload.
in any case thanks for the details.
Hi, maks; thanks, that's good to know.
For the
On Sat, 2015-02-21 at 23:27 +0900, Mark Brown wrote:
On Sat, Feb 21, 2015 at 10:31:19AM +, Ian Campbell wrote:
On Sat, 2015-02-21 at 11:39 +0900, Mark Brown wrote:
Neither of these appears to have disrupted the
boot partition though so I'm not sure what's been doing
On Sat, 2015-02-21 at 11:39 +0900, Mark Brown wrote:
On Fri, Feb 20, 2015 at 02:32:34PM +, Steve McIntyre wrote:
In fact, for EFI just grub-install -v should tell you a lot more.
...and here's the Acer.
Thanks.
Neither of these appears to have disrupted the
boot partition though so
(Steve is probably best placed to say something sensible about this, but
he's away at the moment so I'll see if I can avoid sounding too dumb...)
On Fri, 2015-02-20 at 14:21 +0900, Mark Brown wrote:
Package: grub-efi-amd64-bin
Version: 2.02~beta2-20
Severity: critical
On a couple of
On Fri, 2015-02-20 at 18:39 +0900, Mark Brown wrote:
This is a 1st gen Lenovo Yoga, the other machine that's broken with a
fresh install is an Acer Aspire E11 (with BIOS 1.13 IIRC). I can supply
more specific data on both if you tell me what you're looking for (I see
some talk of a blacklist
Package: src:grub2
Severity: wishlist
Tags: patch, l10n
Submitter: Rudolfs Mazurs rudolfs.maz...@gmail.com
---BeginMessage---
Sorry for late replay, the updated translation is in the attachment.
2014-12-11 21:59 GMT+02:00 Ian Campbell i...@debian.org:
Hi,
You are noted as the last translator
On Mon, 2015-02-09 at 07:57 +0100, Karsten Merker wrote:
On Mon, Feb 09, 2015 at 06:20:50AM +, Ian Campbell wrote:
On Sun, 2015-02-08 at 12:25 +0100, Karsten Merker wrote:
Attached is a patch against
the Debian kernel SVN to backport the devicetree from kernel
3.18.
Applied
On Sun, 2015-02-08 at 12:25 +0100, Karsten Merker wrote:
Attached is a patch against
the Debian kernel SVN to backport the devicetree from kernel
3.18.
Applied to SVN for -4, thanks. BTW, your patch seemed to have DOS line
endings, I ran dos2unix.
Ian.
--
To UNSUBSCRIBE, email to
On Tue, 2015-01-27 at 17:03 +0100, Thomas Schmitt wrote:
Thank you (again?) for all the excellent info you've provided here and
in your followups.
I did not guess too bad with my repacking experiment.
But this does not explain how the empty FAT partition
got to the end of mini.iso
I see in
On Sat, 2015-01-31 at 19:18 -0600, Brian Paterni wrote:
* Disable qemu-traditional and rombios support using new configure
option
instead of by patching. No need to build-depend on ipxe any more.
Not that this isn't when qemu-trad was disabled in the Debian packaging,
just
Control: tags -1 + upstream help
On Tue, 2015-01-27 at 23:54 -0500, Gedalya wrote:
Most probably pvgrub2 just doesn't support PVH, but it would be so nice
if this was added.
Yes, I forgot about this and it would indeed be very nice to have.
It would be best if you could take this up with the
On Wed, 2015-01-28 at 18:38 +0100, Cyril Brulebois wrote:
dann frazier da...@dannf.org (2015-01-28):
On Wed, Jan 28, 2015 at 06:10:49PM +0100, Cyril Brulebois wrote:
I was about to push it but you apparently already did; adjusting tags
accordingly.
Cool, thanks :) Do you +1 me
Control: merge 776050 776236
On Tue, 2015-01-27 at 00:10 -0500, Gedalya wrote:
On Mon, 26 Jan 2015 10:24:41 + Ian Campbell wrote:
This is actually a kernel issue I think, so reassigning accordingly.
2c3fc8d26dd0 swiotlb-xen: pass dev_addr to
swiotlb_tbl_unmap_single
On Tue, 2015-01-27 at 09:15 +0100, Cyril Brulebois wrote:
I've just grabbed mini.iso in both (respectively used for Beta 2 and RC
1), and both seem to have efi bits inside (at least according to a loop
mount).
Not speaking of bootarch.efi but -- there was no useful grub.cfg on
the x86 mini.iso
On Tue, 2015-01-27 at 15:57 +0100, Thomas Schmitt wrote:
[...]
Thanks for all the excellent information, I still have fully absorbed it
all...
Regrettably there is no file /.disk/mkisofs in the ISO which
tells the used xorriso -as mkisofs options.
I guess that /boot/grub/efi.img got marked by
Control: reassign -1 src:linux 3.16.7-ckt4-1
On Sun, 2015-01-25 at 14:24 -0600, Brian Paterni wrote:
Package: xen-hypervisor-4.4-amd64
Version: 4.4.1-6
Severity: normal
Dear Maintainer,
I'm trying to boot into xen/dom0 but so far all attempts have resulted
in a crash followed by an
Control: reassign -1 src:linux 3.16.7-ckt4-1
On Sun, 2015-01-25 at 14:24 -0600, Brian Paterni wrote:
Package: xen-hypervisor-4.4-amd64
Version: 4.4.1-6
Severity: normal
Dear Maintainer,
I'm trying to boot into xen/dom0 but so far all attempts have resulted
in a crash followed by an
)
end
else
setfan(temp, high)
end
end
confdir(/etc/qcontrol.d)
--
-- Local variables:
-- mode: lua
-- indent-level: 8
-- End:
Thanks again...
Max
On 2015-01-20 21:40, Ian Campbell wrote:
On Mon, 2015-01-19 at 11:55 +0800, Paul Wise wrote
Control: found -1 3.16.7-ckt2-1
Control: notfound -1 3.16.0-4
On Mon, 2015-01-12 at 17:30 +0100, Draghi wrote:
Source: linux
Version: 3.16.0-4
FYI, this is the ABI not the package version. The version can be seen in
uname or in your kernel log in:
Linux version 3.16.0-4-kirkwood
Control: tag -1 +moreinfo
On Mon, 2015-01-12 at 17:30 +0100, Draghi wrote:
n...@none.net bounces with an unknown account. Hopefully you see this
here some other way.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Sat, 2015-01-03 at 09:54 -0200, Rogério Brito wrote:
[...]
Thanks for the info.
Since I can't reproduce it would be useful if you could take this issue
to the upstream developers who were involved in the original bug report
and work with them directly to find a cure.
I may try, but I
Control: tag -1 -newcomer
Control: severity -1 wishlist
On Thu, 2015-01-08 at 19:58 +0100, Sten Spans wrote:
Currently there is no working debian kernel for exynos4 / odroid
platforms.
Thanks for taking the time to submit a patch. I'm afraid I've now
remembered why I didn't enable exynos4
On Wed, 2015-01-07 at 20:49 +0100, Jérémy Bobbio wrote:
+@@ -301,7 +301,9 @@ if [ ! -z ${output_file} ]; then
+ if [ -z ${cpio_file} ]; then
+ timestamp=
+ if test -n $KBUILD_BUILD_TIMESTAMP; then
+-timestamp=$(date
On Mon, 2015-01-05 at 23:34 +, Dave Williams wrote:
Hi Ben,
OK - so far I've got:
- 3.14.15-2 works (found a .deb in apt archives on another machine)
- 3.15.5 works (built this from source, but without applying debian
patches (i.e. just unpackaged linux_3.15.5.orig.tar.xz and built that
) unstable; urgency=medium
+
+ [ Ian Campbell ]
+ * Support for TI OMAP5 uEVM board (Patch from Chen Baozi, Closes: #773255)
+ * Support for alternative machine name for BeagleBone Black. The old name was
+ambiguous with the original BeagleBone (often called White), detect if
+booting
401 - 500 of 1693 matches
Mail list logo
