d-i daily 2/18 is missing for armel only
Dear D-I Maintainer, I cannot find today(2/18)'s armel d-i daily image [0], while other arch is correctly downloadable [1][2]. If there's build error, there should be build log to check, but unfortunately there's no 2/18's folder. So I'm asking what happened. [0] https://d-i.debian.org/daily-images/armel/ [1] https://d-i.debian.org/daily-images/amd64/ [2] https://d-i.debian.org/daily-images/arm64/ Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Bug#707844: di-utils: No error message in case of wrong architecture
> Can someone confirm? I just tried. It now gives a good error message. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/
Re: d-i daily 2/18 is missing for armel only
Hi Roger, Roger Shimizu (2016-02-18): > I cannot find today(2/18)'s armel d-i daily image [0], while other > arch is correctly downloadable [1][2]. > If there's build error, there should be build log to check, but > unfortunately there's no 2/18's folder. So I'm asking what happened. Looking at /home/d-i/di/logs/di-autobuild_daily-armel-20160218- on abel (the porterbox currently used for armel d-i daily builds), it seems due to a transient network error at the beginning of the build, hich triggered an early abort (and no logs are uploaded in that case). I've just started an out-of-cron run. If successful, it should appear within a few hours (until dillon.debian.org gets files, and publishes them through a mirror network for d-i.debian.org). Mraw, KiBi. signature.asc Description: Digital signature
Bug report - ext4: Unknown symbol __getblk_gfp (err 0)
Dear Debian team,
I have problem with debian Jessie PXE installation with preseed. I'm
trying to install Debian Jessie on amd64 server. The installation goes
fine until partitionning and fails right after when trying to mount the
newly created partitions with ext4 filesystem. Dmesg give us an idea
about the error that seems related to filesystem module:
ext4: Unknown symbol __bread_gfp (err 0)
ext4: Unknown symbol __getblk_gfp (err 0)
uname -a:
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
GNU/Linux
modinfo ext4:
filename: /lib/modules/3.16.0-4-amd64/kernel/fs/ext4/ext4.ko
license:GPL
description:Fourth Extended Filesystem
author: Remy Card, Stephen Tweedie, Andrew Morton, Andreas
Dilger, Theodore Ts'o and others
alias: fs-ext4
alias: ext3
alias: fs-ext3
alias: ext2
alias: fs-ext2
depends:mbcache,jbd2,crc16
intree: Y
vermagic: 3.16.0-4-amd64 SMP mod_unload modversions
Preseed:
# Localization
d-i debian-installer/locale string en_US
d-i console-keymaps-at/keymap select us
d-i console-setup/ask_detect boolean false
d-i console-setup/layoutcode string us
# Network configuration
d-i netcfg/choose_interface select auto
d-i netcfg/get_hostname string netinstall
d-i netcfg/get_domain string
### Mirror settings
d-i mirror/country string manual
d-i mirror/http/hostname string debian.ignum.cz
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string
# Suite to install.
d-i mirror/suite string jessie
### Account setup
d-i passwd/root-login boolean true
d-i passwd/make-user boolean false
### our default password`
d-i passwd/root-password-crypted password "somepassword"
### Clock and time zone setup
d-i clock-setup/utc boolean true
d-i time/zone string Europe/Prague
d-i clock-setup/ntp boolean true
d-i clock-setup/ntp-server string ntp.ignum.cz
### Base system installation
tasksel tasksel/first multiselect standard
d-i pkgsel/include string openssh-server
d-i pkgsel/upgrade select full-upgrade
popularity-contest popularity-contest/participate boolean false
d-i pkgsel/update-policy select none
# Individual additional packages to install
d-i grub-installer/only_debian boolean true
### Allow non-free firmware
d-i hw-detect/load_firmware boolean true
### Finishing up the installation
d-i finish-install/reboot_in_progress note
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-auto/choose_recipe select boot-root
d-i mdadm/boot_degraded boolean false
d-i partman-md/confirm boolean true
d-i partman-md/confirm_nooverwrite boolean true
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
d-i partman/choose_partition select Finish partitioning and write
changes to disk
d-i partman-auto/disk string /dev/sda /dev/sdb
d-i partman-auto/method string raid
d-i partman-auto-lvm/no_boot boolean true
d-i partman-auto-lvm/new_vg_name string vg0
d-i partman-lvm/confirm boolean true
d-i partman-auto/expert_recipe string\
boot-root :: \
1000 35 1 raid \
$lvmignore{ }\
$primary{ } method{ raid } \
. \
2048 50 2048 ext4 \
$defaultignore{ }\
$lvmok{ }\
lv_name{ root } \
method{ format } \
format{ }\
use_filesystem{ }\
filesystem{ ext4 } \
mountpoint{ / } \
. \
1024 51 1024 ext4 \
$defaultignore{ }\
$lvmok{ }\
lv_name{ tmp } \
method{ format } \
format{ }\
use_filesystem{ }\
filesystem{ ext4 } \
mountpoint{ /tmp } \
. \
10240 52 10240 ext4 \
$defaultignore{ }\
$lvmok{ }\
lv_name{ var } \
method{ format } \
format{ }\
use_filesystem{ }\
filesystem{ ext4 } \
mountpoint{ /var } \
.
Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)
On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote: > Dear Debian team, > > I have problem with debian Jessie PXE installation with preseed. I'm > trying to install Debian Jessie on amd64 server. The installation goes > fine until partitionning and fails right after when trying to mount the > newly created partitions with ext4 filesystem. Dmesg give us an idea > about the error that seems related to filesystem module: > > ext4: Unknown symbol __bread_gfp (err 0) > ext4: Unknown symbol __getblk_gfp (err 0) > > uname -a: > Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 > GNU/Linux [...] This is the original kernel image for jessie (from 8.0). Not all the kernel modules from current jessie (8.3) will work with it. You must update your netboot images after each point release. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)
On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote: > [...] > Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux > > [...] > Any idea what is the problem? Your local vmlinux and initrd binaries are out of sync with the kernel modules in the mirror network, due to the kernel update in the latest point release. i.e. you need to update the binaries on your PXE server to deb8u2. The current Jessie kernel is now 3.16.7-ckt20-1+deb8u2. Ian.
Re: d-i daily 2/18 is missing for armel only
On Thu, Feb 18, 2016 at 6:44 PM, Roger Shimizu wrote: > Dear D-I Maintainer, > > I cannot find today(2/18)'s armel d-i daily image [0], while other > arch is correctly downloadable [1][2]. > If there's build error, there should be build log to check, but > unfortunately there's no 2/18's folder. So I'm asking what happened. > > [0] https://d-i.debian.org/daily-images/armel/ > [1] https://d-i.debian.org/daily-images/amd64/ > [2] https://d-i.debian.org/daily-images/arm64/ Check again then found now 2/18 folder for armel is created. Usually it's run after GMT 0:00, so I guess it's build manually. So problem seems get solved. Just curious what went wrong... -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Re: d-i daily 2/18 is missing for armel only
Dear Cyril, Sorry, just found your email in my gmail's spam folder. So I replied previous email before seeing your email. On Thu, Feb 18, 2016 at 9:05 PM, Cyril Brulebois wrote: > Hi Roger, > > Roger Shimizu (2016-02-18): >> I cannot find today(2/18)'s armel d-i daily image [0], while other >> arch is correctly downloadable [1][2]. >> If there's build error, there should be build log to check, but >> unfortunately there's no 2/18's folder. So I'm asking what happened. > > Looking at /home/d-i/di/logs/di-autobuild_daily-armel-20160218- on > abel (the porterbox currently used for armel d-i daily builds), it > seems due to a transient network error at the beginning of the build, > hich triggered an early abort (and no logs are uploaded in that case). > > I've just started an out-of-cron run. If successful, it should appear > within a few hours (until dillon.debian.org gets files, and publishes > them through a mirror network for d-i.debian.org). Glad to know the reason. Yes, now the armel daily is there. Thank you! -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Bug#760993: console-setup: CHARMAP no longer set properly
On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > Package: console-setup > Version: 1.111 > Severity: important > > In /etc/default/console-setup I have: > CHARMAP="ISO-8859-1" > > However, my console acts like it's in UTF-8 mode. > > If I restart the console-setup service it does get properly set, > so I'm guessing something else is overriding it. Hello! Do you remember if this system used systemd? Did you use the standard the QWERTY layout? I mean is it possible that the console was leaved unconfigured (not only the charmap, but also the keyboard) and the only reason you didn't notice this was that you used QWERTY layout? Anton Zinoviev
Bug#707844: marked as done (di-utils: No error message in case of wrong architecture)
Your message dated Thu, 18 Feb 2016 09:32:22 -0800 with message-id <20160218173222.ga23...@jirafa.cyrius.com> and subject line Re: Bug#707844: di-utils: No error message in case of wrong architecture has caused the Debian Bug report #707844, regarding di-utils: No error message in case of wrong architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: di-utils Version: 1.92+deb7u1 Severity: minor Dear Maintainer, I've downloaded Debian 7.0 to use in a virtual machine. I downloaded an amd64 image, and by mistake used qemu for i386. I had the normal grub and then when selecting whether I wanted graphical or normal installation, it would just hang and do nothing. When trying to do an "expert install" it finally showed me what was going on, and I could start qemu with the appropriate command line. Could you make it print an error message in these cases, for any kind of chosen kind of installation? If a CD doesn't do anything but just hangs I could assume there is something wrong with it, or the problem lies somewhere else. Bye -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.8a (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- * Salvo Tomaselli [2016-02-18 12:08]: > > Can someone confirm? > > I just tried. It now gives a good error message. Excellent! Closing bug as fixed in: debian-installer (20150828) unstable; urgency=medium [ Didier Raboud ] * In the syslinux menu tree: - Add syslinux machinery to use ifcpu64.c32 on multi-arch CDs, for CPU 64-bit capability detection -- Martin Michlmayr http://www.cyrius.com/--- End Message ---
Bug#673644: Message at end of successful install talks about floppies (should be updated)
On Sun, Mar 02, 2014 at 04:26:29PM +0100, Christian PERRIER wrote: >Quoting Cyril Brulebois (k...@debian.org): > >> debian-cd@/Steve, any opinion on this? I don't think we're going to drop >> support for CD, DVD, or USB flash disk any time soon. Not spending our >> time trying to make stuff fit on CD#1 is OK, but there's still some >> real needs for CD images last I heard… > >If you prefer sticking on the more detailed wording, then your wording >is fine and, yes, all you have to do is to change the template in the >package's git tree, then l10n-sync will do its magic the night after >and translators who have chosen to be notified will be notified. I've just pushed a change to remove all the mentions of specific media types - I think it's cleaner and easier in the longer term. Apologies for not responding on this ~2 years ago! -- Steve McIntyre, Cambridge, UK.st...@einval.com "Yes, of course duct tape works in a near-vacuum. Duct tape works anywhere. Duct tape is magic and should be worshipped." -― Andy Weir, "The Martian"
Bug#760993: console-setup: CHARMAP no longer set properly
On Thu, Feb 18, 2016 at 06:16:26PM +0200, Anton Zinoviev wrote: > On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > > Package: console-setup > > Version: 1.111 > > Severity: important > > > > In /etc/default/console-setup I have: > > CHARMAP="ISO-8859-1" > > > > However, my console acts like it's in UTF-8 mode. > > > > If I restart the console-setup service it does get properly set, > > so I'm guessing something else is overriding it. > > Hello! > > Do you remember if this system used systemd? > > Did you use the standard the QWERTY layout? I mean is it possible that > the console was leaved unconfigured (not only the charmap, but also the > keyboard) and the only reason you didn't notice this was that you used > QWERTY layout? I have no idea on which system this was. At least on this one I don't have console-setup installed, and I think it's currently the only one without systemd. I'm going to guess it was on this one anyway. All my systems are using qwerty. I might also have configured it to not touch the font. Kurt
Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report
Uwe, does that look ok? diff --git a/README b/README index 1774af6..d354c87 100644 --- a/README +++ b/README @@ -46,6 +46,8 @@ The following systems are supported: - Marvell OpenRD-Client - Marvell OpenRD-Ultimate - Neo FreeRunner (GTA02) + - NETGEAR ReadyNAS 102 + - NETGEAR ReadyNAS 104 - PlatHome OpenBlocks AX3-4 board - Plat'Home OpenBlocks A6 - QNAP TS-109 diff --git a/db/all.db b/db/all.db index 38241ce..057031f 100644 --- a/db/all.db +++ b/db/all.db @@ -820,6 +820,26 @@ DTB-Id: sun6i-a31s-primo81.dtb U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: NETGEAR ReadyNAS 102 +Kernel-Flavors: armmp armmp-lpae +DTB-Id: armada-370-netgear-rn102.dtb +DTB-Append: yes +Mtd-Kernel: uImage +Mtd-Initrd: minirootfs +U-Boot-Kernel-Address: 0x0400 +U-Boot-Initrd-Address: 0x0500 +Required-Packages: u-boot-tools + +Machine: NETGEAR ReadyNAS 104 +Kernel-Flavors: armmp armmp-lpae +DTB-Id: armada-370-netgear-rn104.dtb +DTB-Append: yes +Mtd-Kernel: uImage +Mtd-Initrd: minirootfs +U-Boot-Kernel-Address: 0x0400 +U-Boot-Initrd-Address: 0x0500 +Required-Packages: u-boot-tools + Machine: NVIDIA Tegra124 Jetson TK1 Kernel-Flavors: armmp armmp-lpae DTB-Id: tegra124-jetson-tk1.dtb -- Martin Michlmayr http://www.cyrius.com/
Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report
Hi Martin, On 02/18/2016 08:36 PM, Martin Michlmayr wrote: > Uwe, does that look ok? Yes, the rn104 entry is what I'm using, I'm just missing the Kernel-Flavors line, which looks ok, too. Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot env to pass the right root= and rootflags= parameter. Gijs uses U-Boot-Initrd-Address: 0x0 on a rn102, but I think this is not optimal. Best regards Uwe
Bug#704162: Wrong sum for GTK installer initrd.gz inside netboot.tar.gz
* Cyril Brulebois [2014-03-03 01:40]: > > There must be a small packaging bug somewhere… > > The timestamp issue was indeed a nice clue. gzip has -n to avoid storing > such information, improving build reproducibility: > I shall note pigz needs has -n and -T: ... > Tagging with patch as the solution has been identified; I haven't > committed a proper patch yet though. Sounds like this bug should be closed: commit c86563eeeb78b4d6b5841a012b21abac55aec56d Author: Cyril Brulebois Date: Thu Nov 26 01:57:36 2015 +0100 build/config/x86.cfg: Also pass -n to gzip. commit d7a975094883477cc708f382e430a280fc8c7488 Author: Cyril Brulebois Date: Thu Nov 26 01:46:33 2015 +0100 Rename GZIP into gzip, and pass an extra -T to pigz. It needs both -n and -T to behave as gzip's -n. -- Martin Michlmayr http://www.cyrius.com/
Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report
* Uwe Kleine-König [2016-02-18 20:47]: > Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot > env to pass the right root= and rootflags= parameter. Right, that's requrired, too. > Gijs uses > > U-Boot-Initrd-Address: 0x0 > > on a rn102, but I think this is not optimal. I cannot remember for sure but I thought there was an issue with the numbers you picked. I'd have to check my mails with Gijs if you cannot remember. -- Martin Michlmayr http://www.cyrius.com/
Processed: unblock 814341 with 806926, unblock 806926 with 814341
Processing commands for cont...@bugs.debian.org: > unblock 814341 with 806926 Bug #814341 [mtd-utils] let flashcp fail on nand and document it's only suitable for nor 814341 was blocked by: 806926 814341 was blocking: 806926 Removed blocking bug(s) of 814341: 806926 > unblock 806926 with 814341 Bug #806926 [flash-kernel] Please add support for Netgear Ready NAS102 and NAS104 806926 was blocked by: 813995 806926 was not blocking any bugs. Removed blocking bug(s) of 806926: 814341 > thanks Stopping processing here. Please contact me if you need assistance. -- 806926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806926 814341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of base-installer_1.162_i386.changes
base-installer_1.162_i386.changes uploaded successfully to ftp-master.debian.org along with the files: base-installer_1.162.dsc base-installer_1.162.tar.xz base-installer_1.162_all.udeb bootstrap-base_1.162_i386.udeb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Processing of base-installer_1.162_i386.changes
base-installer_1.162_i386.changes uploaded successfully to localhost along with the files: base-installer_1.162.dsc base-installer_1.162.tar.xz base-installer_1.162_all.udeb bootstrap-base_1.162_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org)
base-installer_1.162_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 19 Feb 2016 07:01:14 +0100 Source: base-installer Binary: base-installer bootstrap-base Architecture: source all i386 Version: 1.162 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: base-installer - base system installation framework (udeb) bootstrap-base - Install the base system (udeb) Changes: base-installer (1.162) unstable; urgency=medium . [ Martin Michlmayr ] * Remove armeb. * Remove armel/iop32x and armel/ads. * Add marvell flavour to armel kernel selection. Checksums-Sha1: 9d4a8ae18726f616290a4a394e96a5c38629ab7c 1899 base-installer_1.162.dsc c8547521d8bb69dadee6de164ddd24a80ce30a74 254344 base-installer_1.162.tar.xz 5e55cc57472a06a3dc44f9005177c2d894aa4c50 47544 base-installer_1.162_all.udeb fcbc79ce76ad2d1de7fae2b37eff15290df6a172 195330 bootstrap-base_1.162_i386.udeb Checksums-Sha256: 952cb0794204323b4150d42bd3cab0705abf7bdf5069491c9c7e0347ac70319d 1899 base-installer_1.162.dsc fa5d631338c3d8bbf0a42aec0e376cf5fba217d3c4f07f966b81e8579dc5dd76 254344 base-installer_1.162.tar.xz ceef9f3374d31394ce2267b99ea1067f0312c70f40a57f05f6baf9bbc44f3690 47544 base-installer_1.162_all.udeb 36d591ff7a811b0a9709d93aa1e2876d5f606db16fdbf772910099f07ccc46ce 195330 bootstrap-base_1.162_i386.udeb Files: 0ac6de90d670d733f824674dcd0010af 1899 debian-installer required base-installer_1.162.dsc b5428417782ddfa8012d80f52dcb31ee 254344 debian-installer required base-installer_1.162.tar.xz 06ae17fb0ed3aa6931168a8c54d11251 47544 debian-installer required base-installer_1.162_all.udeb 21a72885002ab5b58fcbb73697f6f7b7 195330 debian-installer required bootstrap-base_1.162_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWxrTFAAoJEIcvcCxNbiWooVQP/3LB+P/97dBYx0E6j9ZVXRX5 GyrKsNZpS3V4Eu7uUlld9KgnkdVYv40LPynrY+5MzshOnVFzvSdQuF9uPwjoqkrp 9Y6UCsbDHmWftJQ+9sDPx8iHf8kVwRPPxXZoQ/66zlmkRDKwH047x7XUQcpodZ2b C9/9ZFGnshakgMrKRnSfiu3z4FcWxv6MioLpFjLYKGXtr0jH6tcNV+x06fy3ZjoT yV6ZkTaUYYe5rGlKMuxtBixA2HubIHuPo8itHN3aqFMa8S6fqnDbSe//klT9uV6u Vc/ReFlPWprrh+9wUek0M1DBJrL4PNFP+lo9144wcosohOuFCHE18paOqO8TssPZ AgeN4v3AxG7mGkOqjb9trcIOBcLRBZaY+NuoKpg1b5RPNKeM0QZn7mHrxQc1sbVo CEugQlZ/tOub4ZWKwapBk1f5rZXPAyVd/VDFSKX+on4MXgdI1DGvZZSk3I1zoBwg 7tuLvjL+qMnJATvG2DSrne3VHdpkWavqcRoKWoUSyIftMOU3Wj3LDGKXQ/QBQco2 t/vnX1BJp5xULTfUvruJshOfZq81eEMBHfWhRVVQx8JveCzUR+V5eZFf8Rvk0Iv7 NSJWHOq4acHWQjn6DO/rHz8N21+Q/f0YBJLOAPYjT4kMxeGR1mZ5loP6NFQoFx8a 9iY2/IEQONPg7BnXeXV/ =fg6H -END PGP SIGNATURE- Thank you for your contribution to Debian.
