Re: [PATCH V2] d-i hd-media support for armhf
On 2014-10-01, Karsten Merker wrote:
> On Wed, Oct 01, 2014 at 07:01:44AM +0200, Cyril Brulebois wrote:
>> Karsten Merker (2014-10-01):
> attached is V3 of the patch. I have run a full armhf installer
> build with it without problems and I have done two test installs
> on a Cubietruck with the result (one from USB to SATA and one from
> USB to MMC). Those also have shown no problems.
I got a chance to test the d-i daily images... Thanks for your work on
it!
Overall, it appears to be working quite well. I've thought about
creating a similar bootscript for the netboot images.
> +if test -n "${console}"; then
> + setenv bootargs "${bootargs} console=${console}"
> +fi
It would seem that the console variable isn't consistant across u-boot
platforms. On some (sunxi) it sets both the device and the baudrate
(i.e. console=ttyS0,115200), but on many other platforms console only
sets the device (i.e. console=ttyS0) and linux then reverts to 9600
baud. But the u-boot baudrate is often 115200 with u-boot itself, and
set in a baudrate variable. It doesn't seem possible to set a sane
default...
So basically this "generic" boot script only works with platforms where
the baudrate is included in the "console" variable (or where the
baudrate defaults to 9600, to match linux's default, though I think most
of the armhf platforms at least default to 115200). *sigh*
Not sure if u-boot's shell has the ability to match contents of
variables, so the baudrate could be conditionally added only if not
already present. The only other thing I can think of is setting a
different default serial console baud rate in the kernel, at least for
armhf, but that may have all manner of other consequences.
live well,
vagrant
pgpiEcz8Pin1d.pgp
Description: PGP signature
Re: d-i bugs and freeze
Steven Chamberlain (2014-10-31):
> Hi KiBi,
>
> I'd like to fix d-i bugs, but I wonder how the impending freeze
> affects this:
> * may I still commit a non-RC bug fix to master
> * is it likely to be uploaded to sid
> * is it likely to get an unblock
Yes to all (but of course “likely” depends on what the actual fix is
about, how it's implemented, and how confident I feel with it).
> As a real example, right now I have a fix for an issue mentioned in
> two install reports, which I'd consider severity 'important'.
>
> https://lists.debian.org/debian-bsd/2014/09/msg00125.html
> | grub-mkdevicemap (in /target chroot) did not detect any (virtio)
> | hard disks. I had to "Enter device manually" in the dialog and
> | specify /dev/vtbd0, which worked.
>
> https://lists.debian.org/debian-bsd/2014/10/msg00445.html
> | Apart from that, the grub install step was not able to find the
> | disk/partition by default, so I had to specify it in the prompt as
> | '/dev/xbd0'.
It might be a good idea to have a bug report (pointing at these list
messages) and a bug closure in the changelog. This particular case
looks easy enough but I'd rather have that as a general guideline,
which is going to help unblock reviews.
> And the rather simple change is attached. Not sure what to do.
Fix it? :) You seem to be missing backslashes.
> device_to_disk () {
> echo "$1" | \
> - sed
> 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
> + sed
> 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da|vtbd|xbd\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
^^ ^^ ^^
Push to master once it's fixed and maybe Christian will upload it when
he notices the unreleased changes.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Processing of debootstrap_1.0.64~bpo70+1_amd64.changes
debootstrap_1.0.64~bpo70+1_amd64.changes uploaded successfully to localhost along with the files: debootstrap_1.0.64~bpo70+1.dsc debootstrap_1.0.64~bpo70+1.tar.gz debootstrap_1.0.64~bpo70+1_all.deb debootstrap-udeb_1.0.64~bpo70+1_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xkyig-0002di...@franck.debian.org
debootstrap_1.0.64~bpo70+1_amd64.changes ACCEPTED into wheezy-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Nov 2014 13:51:06 +0100 Source: debootstrap Binary: debootstrap debootstrap-udeb Architecture: source all Version: 1.0.64~bpo70+1 Distribution: wheezy-backports Urgency: medium Maintainer: Debian Install System Team Changed-By: Luca Falavigna Description: debootstrap - Bootstrap a basic Debian system debootstrap-udeb - Bootstrap the Debian system (udeb) Closes: 762713 Changes: debootstrap (1.0.64~bpo70+1) wheezy-backports; urgency=medium . * Rebuild for wheezy-backports. . debootstrap (1.0.64) unstable; urgency=medium . * Add (Ubuntu) vivid as a symlink to gutsy. . debootstrap (1.0.63) unstable; urgency=medium . [ Joey Hess ] * Move set -e out of shebang line. Closes: #762713 . debootstrap (1.0.62) unstable; urgency=medium . [ Cyril Brulebois ] * Fix reporting of package version in retrieval and validation steps to cope with epochs. . debootstrap (1.0.61) unstable; urgency=medium . * Fix "possibly the package $pkg is at fault" warnings to account for changed error output in dpkg 1.17.2. Checksums-Sha1: 22b11143158e82aedf12823626a6715e83cdda7b 1823 debootstrap_1.0.64~bpo70+1.dsc a3e60df1c717fba93683486fda42c1f2676a4822 59779 debootstrap_1.0.64~bpo70+1.tar.gz 78522e731266acec5932ce0ffd5e3f4324b4fea6 63154 debootstrap_1.0.64~bpo70+1_all.deb 9bc0df760dca2597c71302e17d3484a8ad629a7e 18220 debootstrap-udeb_1.0.64~bpo70+1_all.udeb Checksums-Sha256: e20f14a64e7399b770da2d972cb6e4f7fa514618a71e570b7ea00d065864b9cb 1823 debootstrap_1.0.64~bpo70+1.dsc 6e532bda944e253951bd4ff8f3d58a1fcd2e699006f7a74d167905376576765f 59779 debootstrap_1.0.64~bpo70+1.tar.gz 4410156f28aa1d7c1c76150f66d4771a150ffbc85da65995696e23873a7a9012 63154 debootstrap_1.0.64~bpo70+1_all.deb ed33d224359c5272bfa6aab3206b36012901f285a73f3d7a5bef6bef2425affb 18220 debootstrap-udeb_1.0.64~bpo70+1_all.udeb Files: 8145c575616bb771d3ab9f2ddab8fd5b 1823 admin extra debootstrap_1.0.64~bpo70+1.dsc 69d3094354d5b29388acfb6401716901 59779 admin extra debootstrap_1.0.64~bpo70+1.tar.gz dcf9a6a3b8453e49c6def47c3167f04a 63154 admin extra debootstrap_1.0.64~bpo70+1_all.deb 554185ccc6cb27fc15d0e9cfed260cb5 18220 debian-installer extra debootstrap-udeb_1.0.64~bpo70+1_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUVNigAAoJEEkIatPr4vMfSKEQAIDfPtT5vgKLmEoET7cl9AWz EobiJ/cB4n9ig/dr1Xdcm4uDiI8vYpjLI7OJKQmZtzem6t/MqsINlr/WhBoPXuY9 rB0SQe84XW5cq61lTmvF4JErjT1ljc6qEKRgUddbQCf9oRRmUvbCVRSCaoer0H+T JnyjCr5NHCA8HfH9K3iBG3E8rZSMdYTA/yXOZDm/KtdW1wrY9I9amuMytYfnU2M7 Nfh/XuLI8kJ6CtbHfw2UXvE99wdjjnk6Yhum90tb88H2rmEWFWG4z0XjbZirvBd0 FupWyKSm6t2QSKU6xo1FhbTUfg0KD/McPXDIzaRyoiHkzA18q+Hjitmpv17re1tu EhNJDIerCLAf+ZgwGb1+FiJfA39bWl1paS9xKslFePg0TIMT1/Tkmrn2w/3H9Oh7 IOp0xDcgnPhuZ5DxTTUqKPXbWjr7Y13csmLFZMzzcPV+S44rLBC4sxElfRgkJKXm NIrN7BKuQqhy87S9aZohzsyIcHxEeQYVLFDZNEto7kB5Hu3CkCyUw9ZJpIHDLf8S zXZ1zeLxYR2zQN6DbSOOSDD7UWsr2WRrLXf7tiy3rSza1edfIBdCuJv9Ydl+4ECF 34D1k6D9gjZaKCf5Pv+S9p1uJj8XxcZL44saF6bWAAQPPeZw93McO4R+fY+aZUZ+ xl8XatvCZC3/QpII6Zmd =Elkn -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xkyll-0002fj...@franck.debian.org
Re: default DE requalification: quality of task
Adam Borowski wrote: > However, I kind of fail to see the point of giving two whole points for > something as minor as the tasksel task. These points are not added up to get some kind of an overall score. -- see shy jo signature.asc Description: Digital signature
Re: desktop requalification: KDE seems to be portable
On 11/01/2014 05:13 AM, Adam Borowski wrote: On Sat, Nov 01, 2014 at 04:28:05AM +0100, Adam Borowski wrote: I see the field for "KDE/portability" is left as a question mark. In case you won't get answers from official porters soon, I can confirm KDE does work at least on: * real metal: an armhf laptop * qemu: powerpc Not so good on kfreebsd-amd64, though. FWIW, KDE and GNOME do work correctly on hppa (parisc). I just wanted to mention it although hppa is not a release-relevant arch... Helge -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545540c3.3010...@gmx.de
Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
Package: debian-installer Version: 7.7 Beta 2 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? Installing Debian Jessie amd64 using Debian-installer 7.7 Beta 2 amd64 netinst on a partition utilized before. The partition have had grub installed in the partition boot record (not sure if going without partition boot record makes a difference). * What exactly did you do (or not do) that was effective (or ineffective)? Using expert install, selected anual partitioning. No partition table, LVM, software raid etc. modifications were done. Only sda3 was configured as follows: * formatted using ext4 * mount as root After that I selected write changes to disk. * What was the outcome of this action? The formatting dialog hanged at 33%. * What outcome did you expect instead? To re-format /dev/sda3 creating a fresh ext4 filesystem. After examining the situation and killing the mkfs.ext4 process on a second virtual terminal, the installer gave a red screen error and returned to the partitioning menu. Invoking mkfs.ext4 manually on the sencond VT, it gave the yes-no question that follows (captured under the running Jessie install, so mke2fs version might be different). This might be the point where the installer hanged at. # mkfs.ext4 /dev/sda3 mke2fs 1.42.12 (29-Aug-2014) /dev/sda3 contains a ext4 file system last mounted on / on Sat Nov 1 20:18:44 2014 Proceed anyway? (y,n) After formatting from the second VT, installer was able to continue without re-formatting the partition. An other solution was to zero out the forst few megabytes of sda3 using dd and /dev/zero to allow formatting by the installer. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101201404.3656.11882.report...@achilles.db.bme.hu
