flash-kernel_3.52~bpo8+1_source.changes uploaded successfully to
ftp-master.debian.org
along with the files:
flash-kernel_3.52~bpo8+1.dsc
flash-kernel_3.52~bpo8+1.tar.xz
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
flash-kernel_3.52~bpo8+1_source.changes uploaded successfully to localhost
along with the files:
flash-kernel_3.52~bpo8+1.dsc
flash-kernel_3.52~bpo8+1.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Dec 2015 08:23:49 +
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source
Version: 3.52~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Install System
* Łukasz Stelmach [2015-11-16 10:16]:
> I will try the fix suggested by Martin Michlmayr and see if it works.
Did it work?
--
Martin Michlmayr
http://www.cyrius.com/
* Łukasz Stelmach [2015-11-17 22:48]:
> That is being taken care of by Philipp Kirchhofer.
> https://github.com/pkirchhofer/nsa325-linux-upstream
Looks like kernel support was submitted by Hans Ulli Kroll today (to
kernel.org).
BTW, if you're installing via SSH, you may also want to patch
networ
Dnia 10 grudnia 2015 18:50:00 CET, Martin Michlmayr
napisał(a):
>* Łukasz Stelmach [2015-11-16 10:16]:
>> I will try the fix suggested by Martin Michlmayr and see if it works.
>
>Did it work?
Due to personal reasons I haven't had time to verify it yet.
--
Łukasz Stelmach z podróży
Dnia 10 grudnia 2015 18:52:08 CET, Martin Michlmayr
napisał(a):
>* Łukasz Stelmach [2015-11-17 22:48]:
>> That is being taken care of by Philipp Kirchhofer.
>> https://github.com/pkirchhofer/nsa325-linux-upstream
>
>Looks like kernel support was submitted by Hans Ulli Kroll today (to
>kernel.org
* Bernhard Übelacker [2015-04-21 21:00]:
> But I was not aware that the Installer would overwrite the kernel in
> the internal flash without further asking. (Most probably because
> the internal flash holds for installations without serial console
> already the kernel/initrd of the debian installe
* Uwe Kleine-Koenig [1970-01-01 01:46]:
> Image version:
> http://ftp.de.debian.org/debian/dists/wheezy/main/installer-armhf/current/images/mx5/netboot/efikamx/uI{mage,nitrd}
> Date: 2013-05-03
>
> Machine: Freescale i.MX53 LOCO
>
> Comments/Problems:
>
> * I booted the efika kernel+initrd on
Hi Tim,
I just found your installation report from 2013 regarding Buffalo
Linkstation HS-DSGL that unfortunately nobody responded to,
* Tim Clarke [2013-09-13 15:48]:
> Running config-debian prior to install produced an error: 'You have
> to create an ext2 filesystem on /dev/sda1 or /dev/mtd0' /
* Vagrant Cascadian [2014-12-14 14:12]:
> > As far as I can tell, netboot-gtk should just work (looking at e.g.
> > build/pkg-lists/netboot/gtk/i386.cfg vs.
> > build/pkg-lists/netboot/gtk/i386.cfg)
> >
> > Can you please clarify which one you tested? If that's a netboot-gtk one,
> > can
> > you
Martin Michlmayr (2015-12-10):
> * Vagrant Cascadian [2014-12-14 14:12]:
> > > As far as I can tell, netboot-gtk should just work (looking at e.g.
> > > build/pkg-lists/netboot/gtk/i386.cfg vs.
> > > build/pkg-lists/netboot/gtk/i386.cfg)
> > >
> > > Can you please clarify which one you tested? I
Processing commands for cont...@bugs.debian.org:
> reassign 779981 installation-reports
Bug #779981 [installation-report] installation-report
Bug reassigned from package 'installation-report' to 'installation-reports'.
Ignoring request to alter found versions of bug #779981 to the same values
pre
Package: installation-report
Version: 2.60
Severity: wishlist
Tags: patch
On ARM devices using Device Tree, /proc/cpuinfo doesn't list the actual
hardware device. This information can now be found in
/proc/device-tree/model. I think it makes sense to include that file
in the installation report.
Hello Martin,
thanks for your answer.
It was less of an inconvenience as a surprise. In fact, after all
went fine, I was happy not to boot via tftp anymore. :-)
So, yes, this was just a note to the few users, who have concerns
writing to the flash in fear to create an unbootable device.
(I th
* Martin Michlmayr [2015-12-10 17:12]:
> On ARM devices using Device Tree, /proc/cpuinfo doesn't list the actual
> hardware device. This information can now be found in
> /proc/device-tree/model. I think it makes sense to include that file
> in the installation report.
One problem is that /proc
Martin Michlmayr (2015-12-10):
> * Martin Michlmayr [2015-12-10 17:12]:
> > On ARM devices using Device Tree, /proc/cpuinfo doesn't list the actual
> > hardware device. This information can now be found in
> > /proc/device-tree/model. I think it makes sense to include that file
> > in the insta
* Cyril Brulebois [2015-12-11 04:44]:
> A cursory look suggests this file is made available through:
> | drivers/of/base.c: proc_symlink("device-tree", NULL,
> "/sys/firmware/devicetree/base");
Yopu're right. It's also available via
/sys/firmware/devicetree/base/model but I'm not sure
18 matches
Mail list logo
