Re: Bug#854181: RFH: busybox -- Tiny utilities for small and embedded systems
Hi Andrew, Andrew Shadura (2017-02-06): > Package: wnpp > Severity: normal > > Hi, > > We're entering the deep freeze in a few hours, and this mail should have > been sent a while ago, but let's not delay this any further: the Debian > Installer team requests assistance with maintaining the busybox package. > [ So please make sure to include debian-boot@lists.debian.org in copy > if you're replying to this message. ] > > > I think I could help. I'll have a look when I'm home from FOSDEM. Friendly reminder: busybox still needs a maintainer. ;) KiBi. signature.asc Description: Digital signature
Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)
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 > the installation process. Thanks for your follow-ups. Any chance you could attach the installer's syslog file? It should be stored under /var/log/installer. KiBi. signature.asc Description: Digital signature
Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting
Hi Didier, Amos Jeffries (2017-06-14): > On 14/06/17 03:38, Steve McIntyre wrote: > > There isn't a reboot step in the normal path of debian-installer. Oh, > > hang on, sorry - I've just seen what I missed earlier in your initial > > message: "On running the installer manually from inside the OEM > > Windows". Did you use the win32-installer option to start > > installation? > > I think so, yes. Any chance you could glance over this bug report and see whether you have some ideas about what could be happening on the win32-loader side? KiBi. signature.asc Description: Digital signature
Bug#865473: installation-reports, clean install debian-9.0.0-amd64-xfce-CD-1.iso, grub not working on /dev/sdc
Hi Rolf, Rolf Reintjes (2017-06-21): > My hard drives at installation: > /dev/sda is Windows 10 > /dev/sdb installation-USB-Stick (debian-9.0.0-amd64-xfce-CD-1.iso) > /dev/sdc HDD at USB connected, here the new debian will be installed > > The installation on /dev/sdc did run normally without problems. > I did not choose /dev/sda for installation of grub but /dev/sdc. > > The grub installation finished and I rebooted the system. > > I pressed F11 at boot an selected now the USB-HDD with debian (now /dev/sdb, > because I removed the installation-USB-stick) for boot. > > Now the problem occured: grub could not boot and gived a error message > (which I did not write down) that something was not found. grub entered > rescu mode. Here I did not go on with this grub. > > Instead I booted again with the installation-USB-stick, went into rescu mode > and did again install grub. This worked fine. > > Then I rebooted the system, pressed F11 on boot and selected again the > USB-HDD with debian (now /dev/sdb, because I removed the > installation-USB-stick) for boot. NOW grub did run correctly and I could > boot and use the new installed debian. > > The grub did not look like I was used to. Therefore in the running system I > did run > grub-install /dev/sdb > and > update-grub > Both was sucessfull. Now the grub did look like I was used to and everything > runs fine. Thanks for your report. Can you please attach the installer's syslog, which might have some clue? You'll find it under the /var/log/installer directory. KiBi. signature.asc Description: Digital signature
Bug#865562: debian-live-9.0.1-i386-mate.iso is affected too
Nrbrtx (2017-06-23): > I'm unable to install from debian-live-9.0.1-i386-mate.iso without > internet. It's 2017 year, is not it. Every Ubuntu had this functionality. It's 2017 year, and like every year, Debian is a volunteer project. So if you care about being able to *install* Debian from a *live* image, feel free to give a hand. In the meanwhile, there are installation images which allow you to do so, feel free to use them. KiBi. signature.asc Description: Digital signature
Bug#815569: partman-md: it should be able to choose metadata={0, 1, ddf, imsm} when creating the RAID
Roger Shimizu (2016-02-23): > I'm porting d-i onto a few Buffalo Linkstation NAS devices recently. > Linkstation's u-boot loader loads kernel/initrd from 1st partition of > the disks, which only recognize metadata=0 (or so-called 0.90) for > RAID-1 case. > > But as you know currently partman-md can only create metadata=1.2, so > I have to type: > mdadm --create /dev/md0 --level=1 --raid-devices=2 -e 0 /dev/sda1 /dev/sdb1 > to create the /dev/md0 manually. > BTW. partman-md can create the rest /dev/md1, /etc/md2, etc, without problem. > > So I ask you to support specify the metadata style when creating the RAID. > Thank you! I suppose this could be solved by adding questions that would only show up in expert installation mode. KiBi. signature.asc Description: Digital signature
Bug#815570: partman-md: it should be able to setup bitmap when creating the RAID
Hi Roger, Roger Shimizu (2016-02-23): > As bitmap plays an important role in RAID, I recommend partman-md to > have a menu to setup internal/external bitmap, and bitmap block size. > Thank you! This feels like questions that should only be asked during an expert installation? KiBi. signature.asc Description: Digital signature
Re: Bug#820818: partman is not able to resize nvme0n1p3 in d-i
[ Dropping #820818, which is archived. ]
Hi Ben,
Ben Hutchings (2017-02-05):
> Please don't do this. The rule for Linux partition device names is
> very simple and there is no need to match specific prefixes:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/block/partition-generic.c?h=v4.9#n35
>
> Please instead use the following patch:
>
> --- a/lib/resize.sh
> +++ b/lib/resize.sh
> @@ -18,15 +18,12 @@ get_real_device () {
> num=$(sed 's/^[^0-9]*\([0-9]*\)[^0-9].*/\1/'
> $backupdev/$oldid/view)
> bdev=$(cat $backupdev/device)
> case $bdev in
> - */disc)
> - bdev=${bdev%/disc}/part$num
> + /dev/*[0-9])
> + bdev=${bdev}p$num
> ;;
> - /dev/[hsv]d[a-z]|/dev/xvd[a-z])
> + /dev/*)
> bdev=$bdev$num
> ;;
> -
> /dev/cciss/c[0-9]d[0-9]|/dev/cciss/c[0-9]d[0-9][0-9]|/dev/ida/c[0-9]d[0-9]|/dev/ida/c[0-9]d[0-9][0-9]|/dev/mmcblk[0-9])
> - bdev=${bdev}p$num
> - ;;
> *)
> log "get_real_device: strange device name $bdev"
> return
Should I apply this patch as-is, or should anything be updated there?
KiBi.
signature.asc
Description: Digital signature
Bug#823020: Bug#823500: cannot boot from ext4
Hi Thierry, Thierry Reding (2017-02-27): > On Fri, May 06, 2016 at 02:20:45AM +0200, Cyril Brulebois wrote: > > Cyril Brulebois (2016-05-06): > > > Anyway, we could probably implement the change globally regardless, just > > > to make it possible to check the hypothesis on a wide range of devices, > > > and only figure out later how to fix this in a better way? > > > > > > Vagrant, what do you think? > > > > I've pushed a pu/disable-flex_bg branch to partman-ext3's git repository. > > Feedback/tests welcome. I can push to master and upload if that looks like > > a good idea. > > I just ran across this from Martin's instructions on how to install > Debian on a Jetson TX1 and this sounds familiar. I ran into a similar > bug not long ago that turned out to be caused by e2fsprogs 1.43 which > enables the 64bit (-O 64bit) feature by default. U-Boot (before 2016.07 > I think) can't deal with such filesystems and will read bogus data. > > Newer versions of U-Boot have support for this. Another solution was to > create filesystems with -O ^64bit to disable the offending option. > > Given that the last entry in this bug report is rather old, I'm not sure > this is still an issue, but I thought I'd bring it up in case this still > doesn't work properly. Thanks for bringing this up. u-boot maintainers: any action that should be taken on the d-i side? (Sorry for the lag, huge number of unread mails in my debian-boot@ mail box.) KiBi. signature.asc Description: Digital signature
Bug#865473: installation-reports, clean install debian-9.0.0-amd64-xfce-CD-1.iso, grub not working on /dev/sdc
Hi, Rolf Reintjes (2017-06-24): > Hello KiBi, > > On 24.06.2017 18:02, Cyril Brulebois wrote: > > Thanks for your report. > > > > Can you please attach the installer's syslog, which might have some clue? > > > > You'll find it under the /var/log/installer directory. > > Please find attached the file syslog from /var/log/installer. Thanks! This looks weird: > Jun 20 18:33:58 grub-installer: info: Installing grub on '' Are you sure you selected the /dev/sdc entry when you were prompted where to install grub, and not the default “Enter manually” which comes with an empty string by default? KiBi. signature.asc Description: Digital signature
Bug#865473: installation-reports, clean install debian-9.0.0-amd64-xfce-CD-1.iso, grub not working on /dev/sdc
Hello, On 24.06.2017 18:34, Cyril Brulebois wrote: Hi, Rolf Reintjes (2017-06-24): Hello KiBi, On 24.06.2017 18:02, Cyril Brulebois wrote: Thanks for your report. Can you please attach the installer's syslog, which might have some clue? You'll find it under the /var/log/installer directory. Please find attached the file syslog from /var/log/installer. Thanks! This looks weird: Jun 20 18:33:58 grub-installer: info: Installing grub on '' Are you sure you selected the /dev/sdc entry when you were prompted where to install grub, and not the default “Enter manually” which comes with an empty string by default? I cannot remember what I chose. But grub was installed on /dev/sdc because grub started on next boot. The problem was that it was not installed correctly. What about this?: Jun 20 18:34:13 main-menu[583]: (process:9773): Volume group "sdc" not found Jun 20 18:34:13 main-menu[583]: (process:9773): Cannot process volume group sdc I did the installation 2 times. First with normal mode and the second time with graphical mode. Both times I did get the same problem. Best regards Rolf
Bug#865425: debian-installer-9-netboot-mips64el: mips64el Malta netboot installer finds no installable kernel
On 2017-06-24 02:12, Cyril Brulebois wrote: > Control: reassign -1 libdebian-installer 0.110 > Control: affects -1 debian-installer-9-netboot-mips64el > > Bruno Bierbaumer (2017-06-21):² > > Package: debian-installer-9-netboot-mips64el > > Severity: normal > > Tags: d-i > > > > Dear Maintainer, > > > > I wanted to install Debian Stretch mips64el in QEMU. > > It seems that the netboot installer can't find any installable kernel for > > this architecture. > > There is definitely linux-images for 5kc-malta in the repo and the same > > install procedure worked for both mips and mipsel. > > > > Steps to reproduce: > > > > qemu-system-mips64el -M malta -m 256 -cpu MIPS64R2-generic \ > > -drive file=hda.qcow2,if=virtio,format=qcow2,index=0 \ > > -kernel vmlinux-4.9.0-3-5kc-malta \ > > -initrd initrd.gz \ > > -net user,hostfwd=tcp::2-:22 \ > > -net nic \ > > -nographic \ > > -append "nokaslr" > > > > The installer will show the error: No installable kernel was found in the > > defined APT sources > > Some info about this: > ~ # archdetect > mips64el/unknown > > and “unknown” is why base-installer isn't able to pick the right kernel. > > Looking at the hwmap structure in src/system/subarch-mips-linux.c (from > the libdebian-installer package), where architecture detection happens, > I initially thought we were missing some MIPS64 pattern there, but that > doesn't seem the case, as /proc/cpuinfo reports this: > | system type : MIPS Malta > … > | cpu model : MIPS GENERIC QEMU V0.0 FPU V0.0 > > (Full contents below for reference.) > > and those are the ones which are searched through the hwmap… > > I'm not sure how to fix libdebian-installer here, adding debian-mips@ > and qemu maintainers in copy. > > It might make sense to update the bug report title as well at some > point, since this is likely an issue on QEMU only? The current version of subarch-mips-linux.c tries to detect if the CPU is 32 or 64-bit using the CPU type. It's therefore not prepared for the "GENERIC QEMU" type returned in /proc/cpuinfo. The code should probably be modified to use the "isa" field as a fallback if the "cpu model" field can't be used to determine the flavour. That said, the quick workaround is to emulate a real CPU in QEMU. For example you can select the 5KEf CPU which is a MIPS64R2 CPU with FPU. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Re: Bug#820818: partman is not able to resize nvme0n1p3 in d-i
On Sat, 2017-06-24 at 18:27 +0200, Cyril Brulebois wrote:
> [ Dropping #820818, which is archived. ]
>
> Hi Ben,
>
> Ben Hutchings (2017-02-05):
> > Please don't do this. The rule for Linux partition device names is
> > very simple and there is no need to match specific prefixes:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/block/partition-generic.c?h=v4.9#n35
> >
> > Please instead use the following patch:
> >
> > --- a/lib/resize.sh
> > +++ b/lib/resize.sh
> > @@ -18,15 +18,12 @@ get_real_device () {
> > num=$(sed 's/^[^0-9]*\([0-9]*\)[^0-9].*/\1/'
> > $backupdev/$oldid/view)
> > bdev=$(cat $backupdev/device)
> > case $bdev in
> > - */disc)
> > - bdev=${bdev%/disc}/part$num
> > + /dev/*[0-9])
> > + bdev=${bdev}p$num
> > ;;
> > - /dev/[hsv]d[a-z]|/dev/xvd[a-z])
> > + /dev/*)
> > bdev=$bdev$num
> > ;;
> > -
> > /dev/cciss/c[0-9]d[0-9]|/dev/cciss/c[0-9]d[0-9][0-9]|/dev/ida/c[0-9]d[0-9]|/dev/ida/c[0-9]d[0-9][0-9]|/dev/mmcblk[0-9])
> > - bdev=${bdev}p$num
> > - ;;
> > *)
> > log "get_real_device: strange device name $bdev"
> > return
>
> Should I apply this patch as-is, or should anything be updated there?
I think this is still good.
Ben.
--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.
signature.asc
Description: This is a digitally signed message part
Bug#817023: os-prober doesn't detect EFI partition on MBR
Hi, kay (2016-03-07): > Package: os-prober > Version: 1.71 > > Also reproducible in os-prober 1.65 > > https://anonscm.debian.org/cgit/d-i/os-prober.git/tree/os-probes/mounted/x86/05efi#n42..n45 > > Disk has regular MBR table. It has Windows 7 and Ubuntu installed on > different partitions. Os-prober doesn't detect EFI partition on MBR > table because "udevadm info" returns "dos" partition scheme instead of > expected "msdos". > > $ udevadm info /dev/sda1 | grep dos > E: ID_PART_ENTRY_SCHEME=dos > E: ID_PART_TABLE_TYPE=dos > > $ fdisk -lu /dev/sda | grep -B1 -A1 ef > Device Boot Start End Blocks Id System > /dev/sda1 * 2048 616447 307200 ef EFI (FAT-12/16/32) > /dev/sda2 616448 128134439 63758996 7 HPFS/NTFS/exFAT > > Fixing conditions below resolves the issue: > > - \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o > \ > + \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \ > \( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != > c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \ > - \( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; > then > + \( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then > > Probably this bug relates to udevinfo replacement > (https://lists.debian.org/debian-user/2010/07/msg01134.html). > > P.S. Cross-posting report in ubuntu launchpad > https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1553678 So I've tracked this to udev in systemd.git calling blkid functions to get the partition type, and to libblkid/src/partitions/dos.c in util-linux.git; it doesn't seem to have been called msdos previously, so I think the proposed change looks good. This needs to be backported to jessie and stretch AFAICT. Cc-ing Steve since this involves EFI though, to have another pair of eyes go over this. KiBi. signature.asc Description: Digital signature
Re: Bug#820818: partman is not able to resize nvme0n1p3 in d-i
Ben Hutchings (2017-06-24): > On Sat, 2017-06-24 at 18:27 +0200, Cyril Brulebois wrote: > > Should I apply this patch as-is, or should anything be updated > > there? > > I think this is still good. Sorry for not fixing this sooner, but now that's committed and uploaded. Thanks for the suggestion! KiBi. signature.asc Description: Digital signature
Bug#778922: Installer hangs during disk formatting
Hi all, Thomas Neugebauer (2016-09-01): > I've had the same Problem when installing Debian a few days ago. I > used the 8.4 multi-arch dvd to reinstall > Debian. I had a "classic" setup with separate partitions for /var, /tmp, / + > /usr and /home and on a second hdd I had the mountpoint for > /var/lib/libvirt/images. > I've deleted the first partitions and made a simpler layout just containing > / and /home (and of course swap) the second hdd was just to be reformattet > and where the installer suddenly frozes at 33%. ps showed the > status "S" for every process, the status leds of the pc where inactive, > nothing happened. At the log console I've found the same as the initial > Bug-reporter: "Found a dos partition table of /dev/sdb1" > So I've downloaded the newer installer in version 8.5 and retried with the > same layout for hdd and it failed again. > I used the official installer releases. At the moment I have no Debian PC > arround here at work, if you need further information please let me know. This is likely the same problem as reported in #767682, which was fixed in stretch but not backported to jessie yet. I've added this to my to-do list for the 8.9 point release. KiBi. signature.asc Description: Digital signature
Bug#774525: installation-reports: Problem formating entire disk to ext4.
Hi, ajstad...@gridtrak.com (2016-09-10): > This might be the reason why the Debian Stretch Alpha 7/i386 installation > does not complete the Partition Formatting step. It gets stuck at about > 30%. > > I am using Windows 2012 R2 Hyper-V platform and tried both VHD and VHDX > virtual drives. > > This is not a problem with the current Debian 8.5.0 Jessie/i386 > installation. > > I am a novice, so I don't know how to troubleshoot or work around this > issue. This bug was fixed in stretch but not yet in jessie; it's on my todo list for the 8.9 point release though. KiBi. signature.asc Description: Digital signature
Bug#837060: debootstrap: Do not install packages of Priority:required for buildd variant
Julien Cristau (2016-09-12): > This is a transient situation because some Essential packages' > dependencies changed. I'd consider this a bug in the archive, not in > debootstrap. Any reasons to keep this bug report open then? Seen no objections, so I'm tempted to close it. KiBi. signature.asc Description: Digital signature
Processing of partman-partitioning_116_source.changes
partman-partitioning_116_source.changes uploaded successfully to localhost along with the files: partman-partitioning_116.dsc partman-partitioning_116.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
partman-partitioning_116_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Jun 2017 20:04:19 +0200 Source: partman-partitioning Binary: partman-partitioning Architecture: source Version: 116 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: partman-partitioning - Partitioning operations for partman (udeb) Changes: partman-partitioning (116) unstable; urgency=medium . [ Cyril Brulebois ] * Make get_real_device() both simpler and more generic by mimicking the linux kernel's disk_name function, thanks to Ben Hutchings (See: #820818). . [ Updated translations ] * Simplified Chinese (zh_CN.po) by Yangfl Checksums-Sha1: 39aa396f45f1e08cc8916adf7625f2b1b4bd2e54 1680 partman-partitioning_116.dsc bc1b6b00457ba09e34d0799fa89f7d557f6deb70 176092 partman-partitioning_116.tar.xz Checksums-Sha256: 4be2933c70b714f3d3aee6fe8be203948211c818b81962786a324c84fb24d545 1680 partman-partitioning_116.dsc aee265a1df6c40c17317de653635edf8305678ba89173c679b693af25414bea2 176092 partman-partitioning_116.tar.xz Files: 1e2130c6edb2334d04f0a9307ee6395f 1680 debian-installer optional partman-partitioning_116.dsc 9331ff5de220efa609b19c6d2960b58c 176092 debian-installer optional partman-partitioning_116.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJZTqnSAAoJEP+RSvDCs1UgO0AP/jd5cLjRTFwEFF4wAS8GNiHF GYN0+TdyR3zi17BxHvOI5NPGPuc8SWRPOtkvUea5KL4zwpQYLRwbEAq/t4ElLwzz nxY0rTajhF0DaM/c2bNyhFT7gVc7/KbZ0wuF409+R/BhXCrJwKaelcVm5DOyXp+G 4MXGf1bwMpiYAlK+5F8u2+fD0jQ4klY0vg3KzxC4XZC28mE2sJ4EPfdc9W7YC800 9wyFMEKCg5oaunjCUqtvxSJseWyysVn/NjnlSCKTh8BPfttE5GCVozMGWU7HlPB7 Nh1MeIJJjiSHaNQA9ml70gDeQS7MvAKMkj1fMsb1DNL7Ogeh0DhalmtCSnUUZEoX VLiD6EFaeNEHWz6fM3IblWd5lGns9V+u/frccBq0A65bp0ktBDiCZoW8XqPimH21 ySl6gDlMsj5nyldbzQSdCcLuMyAkFRgPiwbDxaFFNeOdosPv6SJ1t3WmTNezv48k FJYhDONYGyvSoVZgMxwAXM8jQBwwNS5gcXsh3oOmZhxMguA5Kw7wCJUVLv5GJ/3s r1Z7v/0wNi8dWGsAhiR05LWD+Kq31DrAt/3cxY003LgfkSOunWy/XVgBfS2iSyL3 iUpy/CjnxKq6JqKSkGeN4YZZjzSGNmkfSbGp8Ts3AyDaN38VRUDeAU1adfJl/BDt f27sJxYocpxedhjgTSiy =cQB8 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#837509: installation-reports: Partial success on Novena (no USB during install)
Hi, Vagrant Cascadian (2016-09-11): > Install mostly worked fine, but was unable to install to USB disk. > > -- Package-specific info: > > Boot method: network > Image version: > https://d-i.debian.org/daily-images/armhf/20160904-00:17/netboot/netboot.tar.gz > Date: Mon Sep 12 01:00:00 UTC 2016 > > Machine: Novena > > Base System Installation Checklist: > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > Initial boot: [O] > Detect network card:[O] > Configure network: [O] > Detect CD: [ ] > Load installer modules: [O] > Clock/timezone setup: [O] > User/password setup:[O] > Detect hard drives: [E] > Partition hard drives: [O] > Install base system:[O] > Install tasks: [O] > Install boot loader:[O] > Overall install:[O] > > Comments/Problems: > > Installation worked fine when installing to SATA or microSD, but USB > disks were not detected during the installation. The USB device detects > fine after installation. My guess is some necessary USB modules were not > available from within debian-installer. > > > Unrelated, the recent versions of d-i armhf images are failing to build > properly, which is why I was using an older daily image. Can you please attach lsmod's output from the installed system? KiBi. signature.asc Description: Digital signature
Bug#837555: marked as done (installation-reports: Successful Sid d-i Reiser4-enabled 4.7.0-1+reiser4.0.1-amd64 kernel onto root reiser4 fs HP dv6-6c53cl )
Your message dated Sat, 24 Jun 2017 20:37:42 +0200 with message-id <20170624183742.gd27...@mraw.org> and subject line Re: Bug#837555: installation-reports: Successful Sid d-i Reiser4-enabled 4.7.0-1+reiser4.0.1-amd64 kernel onto root reiser4 fs HP dv6-6c53cl has caused the Debian Bug report #837555, regarding installation-reports: Successful Sid d-i Reiser4-enabled 4.7.0-1+reiser4.0.1-amd64 kernel onto root reiser4 fs HP dv6-6c53cl 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.) -- 837555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: netboot/USB stick Image version: https://metztli.it/readOnlyEphemeral/Mictlanteuccitlalli.iso https://metztli.it/readOnlyEphemeral/Mictlanteuccitlalli.SHA256SUM Date: Sep 11, 2016 ~ 17:14 Machine: HP Pavilion dv6-6c53cl Partitions: jose@mictlantecuhtli:~$ df -Tl Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 81814640 8181464 0% /dev tmpfs tmpfs 1638284 1060 1637224 1% /run /dev/sda15 reiser4 92435000 7818180 84616820 9% / tmpfs tmpfs 51204 5116 1% /run/lock tmpfs tmpfs 3862920 7892 3855028 1% /run/shm /dev/sda9 ext2136269 103081 25918 80% /boot cgroup tmpfs 12012 0% /sys/fs/cgroup tmpfs tmpfs 1638280 20 1638260 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Installed in 'expert' mode, as I... Built Reiser4-enabled Unstable (svn) Debian Installer and Reiser4-patched kernel from Sid source specifically for a Debian native Reiser4 partitioning, formating, and installation on my development environment. Given its bleeding edge changing nature, Debian simply installed flawlessly its Debian Desktop environment. Only issue is that upon instantiation, d-i did not recognize my command: preseed/late_command="in-target apt-get install -y sysvinit-core" as I don't want *that* systemd thingy-magingy with my Enlightenment subsequent build. Thus, had to give the above command myself after first boot. I have noticed, since a while back, that the GDM3 behaves buggy, i.e., CTRL + Alt + fn to get a virtual terminal usually hangs the system; it could be as a result of not having systemd(?) -- notwithstanding still seems GDM3 behaves laggardly. I usually replace it with XDM -- which works beautifully to instantiate (and customize) Enlightenment. Please note below that since I build my own SSL-enabled BusyBox UDEB for d-i so that it can fetch its Reiser4 kernel &/or utilities from metztli.it, I usually customize its option for an 'OS name' as Xonecuiltzin (which is appended to uname -a output ;-) -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="9 (stretch) - installer build 20160911-15:10" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux mictlantecuhtli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 4.7.2-1+reiser4.0.1 (2016-09-11) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:01
Bug#847230: marked as done (installation-reports: Reiser4 successfull remote install on Cloud provider KVM infrastructure via netboot image)
Your message dated Sat, 24 Jun 2017 20:39:26 +0200 with message-id <20170624183926.gf27...@mraw.org> and subject line Re: Bug#847230: installation-reports: Reiser4 successfull remote install on Cloud provider KVM infrastructure via netboot image has caused the Debian Bug report #847230, regarding installation-reports: Reiser4 successfull remote install on Cloud provider KVM infrastructure via netboot image 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.) -- 847230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: netboot/virtual-disk Image version: Debian-Reiser4 Jessie https://sourceforge.net/projects/debian-reiser4/ Date: Dec 06, 2016 03:09 am, Pacific Standard Time (PST) Machine: upCloud Provider https://www.upcloud.com/ QEMU/KVM cloud Infrastructure-as-a-Service (IaaS) Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 2041004468199632 3% /run /dev/vda5 reiser4 18650464 1003996 17646468 6% / tmpfs tmpfs 510244 0510244 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 510244 0510244 0% /sys/fs/cgroup /dev/vda6 jfs 116331041944 11631160 1% /home /dev/vda1 ext2140805 34447 99088 26% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: netbooted off a 10Gb virtual-disk where Reiser4-enabled netboot installer was transfered thus: dd if=~/metztli.iso of=/dev/vdb bs=16M oflag=direct < https://www.upcloud.com/support/using-own-installation-media/ > Smooth Reiser4-enabled Jessie installer with newer relevant jessiena links to linux-image-4.7.0-1+reiser4.0.1-amd64_4.7.8-1+reiser4.0.1_amd64.deb < https://metztli.it/readOnlyEphemeral/shot-2016-12-06_02-57-27.jpg > Detected and carved from a 30 Gb existing virtual disk, partitioned, and formatted its root file system in Reiser4 (SFRN) 4.0.1. Debian-Reiser4 netboot detected remote network *beautifully* as I have no issues when submitting this report: < https://metztli.it/readOnlyEphemeral/tlaloccitlalli-2016-12-06_08-42-39.jpg > ---fragment of /var/log/syslog Dec 6 03:41:56 tlaloccitlalli rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="517" x-info="http://www.rsyslog.com";] start Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] Linux version 4.7.0-1+reiser4.0.1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.7.8-1+reiser4.0.1 (2016-10-26) Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.7.0-1+reiser4.0.1-amd64 root=/dev/vda5 ro quiet Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Using 'eager' FPU context switches. Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] e820: BIOS-provided physical RAM map: Dec 6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 0x-0x
Bug#849268: marked as done (installation-reports: Jessie-backported Reiser4-patched Linux 4.8.15-1 on UpCloud 8-core/48Gig RAM KVM Cloud infrastructure successful installation)
Your message dated Sat, 24 Jun 2017 20:40:06 +0200 with message-id <20170624184006.gg27...@mraw.org> and subject line Re: Bug#849268: installation-reports: Jessie-backported Reiser4-patched Linux 4.8.15-1 on UpCloud 8-core/48Gig RAM KVM Cloud infrastructure successful installation has caused the Debian Bug report #849268, regarding installation-reports: Jessie-backported Reiser4-patched Linux 4.8.15-1 on UpCloud 8-core/48Gig RAM KVM Cloud infrastructure successful installation 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.) -- 849268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: netboot ISO image 'dd' /dev/vdb Image version: https://sourceforge.net/projects/debian-reiser4/ built on 12-23-2016 Date: 12-24-2016 01:56 AM PST Machine: https://www.upcloud.com KVM Cloud infrastructure Partitions: udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 98931408976 9884164 1% /run /dev/vda6 reiser4 20423272 4523220 15900052 23% / tmpfs tmpfs 24732840 144 24732696 1% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 24732840 0 24732840 0% /sys/fs/cgroup /dev/vda5 jfs9725448 10252 9715196 1% /home /dev/vda1 ext2188403 22408156267 13% /boot tmpfs tmpfs 4946572 20 4946552 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Analyzing the 'various bugfixes and fixed vulnerabilities' in Sid kernel 4.8.15-1 I realized I had to do a Jessie-backports for Reiser4 (SFRN) 4.0.1 AND test neboot installation in massive KVM Cloud instance of 12-cores / 48 Gig RAM. "We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations" < https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug > Smooth installation of Reiser4-enabled kernel 4.8.15-1 & reiser4progs built/fetched for Jessie netboot installer. Only conflict is with nfs-commmon -- which hangs the newly installed Reiser4 Linux OS upon boot. Accordingly this particular Debian netboot installer will purge nfs-common at end of installation so that GNU/Linux Debian Jessie OS boots without issues from its initial ext2 boot ~150MB partition into Reiser4 root file system. https://metztli.it/readOnlyEphemeral/Cohuatlicue_UpCloud.png Notice below - netboot installer UDEB kernel only differs in name 'Cohuatlicue' from kernel 4.8.15-1 downloaded via SSL from meztli.it -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20161224-05:26" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux cohuatlicue 4.8.0-2+cohuatlicue-amd64 #1 SMP Debian 4.8.15-1+cohuatlicue (2016-12-22) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 I
Bug#856143: installation-reports: 4.9.10-2+reiser4.0.1 jessie-backport successful wireless install onto HP NoteBook PC
Metztli Information Technology (2017-02-25): > Boot method: netboot/USB > Image version: https://metztli.it/readOnlyEphemeral/ilhuicateocitlalli.iso > Feb 23, 2017, 05:54 AM > Date: Feb 24, 2017, 19:21 PST This has nothing to do in the Debian BTS, closing. KiBi. signature.asc Description: Digital signature
Bug#838345: marked as done (installation-reports: Successful Reiser4 Jessie 4.7.0-1+reiser4.0.1-amd64_4.7.4-1 kernel on VirtualBox 5.1.6)
Your message dated Sat, 24 Jun 2017 20:38:30 +0200 with message-id <20170624183830.ge27...@mraw.org> and subject line Re: Bug#838345: installation-reports: Successful Reiser4 Jessie 4.7.0-1+reiser4.0.1-amd64_4.7.4-1 kernel on VirtualBox 5.1.6 has caused the Debian Bug report #838345, regarding installation-reports: Successful Reiser4 Jessie 4.7.0-1+reiser4.0.1-amd64_4.7.4-1 kernel on VirtualBox 5.1.6 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.) -- 838345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: netboot image Image version: https://sourceforge.net/projects/debian-reiser4/ Date: September 19, 20:35:31 PDT Machine: VirtualBox 5.1.6 Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 4105045916404588 2% /run /dev/sda5 reiser49822436 3798668 6023768 39% / tmpfs tmpfs 10262601108 1025152 1% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 1026260 0 1026260 0% /sys/fs/cgroup /dev/sda1 ext2140805 55482 78053 42% /boot tmpfs tmpfs 205252 8205244 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Smooth Reiser4-enabled Jessie Debian-Installer in non-expert mode. elvis-tiny has been integrated into this d-i -- since I found nano awful; I wish I had elvis-tiny available as I was intially working on Reiser4 hack. SSL-enabled Busybox in d-i automatically downloaded Reiser4-patched Linux kernel 4.7.0-1 -- modified for Jessie's GCC 4.9 -- as well as reiser4progs 1.1.0-1.x built for Debian Jessie AMD64. d-i also fetches linux-base from backports to satisfy recent kernel requirements. Overall flawless installation for a non expert. Node: payinalcitlalli http://www.enlightenment.org/ss/e-57e0df154a3995.47690147.jpg (as usual Xonecuiltzin is d-i BusyBox environment.) -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20160919-14:55" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux payinalcitlalli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 4.7.4-1+reiser4.0.1 (2016-09-19) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:001e] lspci -knn: Kernel driver in use: e1000 lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] lspci -knn: 00
Bug#856143: marked as done (installation-reports: 4.9.10-2+reiser4.0.1 jessie-backport successful wireless install onto HP NoteBook PC)
Your message dated Sat, 24 Jun 2017 20:41:08 +0200 with message-id <20170624184108.gh27...@mraw.org> and subject line Re: Bug#856143: installation-reports: 4.9.10-2+reiser4.0.1 jessie-backport successful wireless install onto HP NoteBook PC has caused the Debian Bug report #856143, regarding installation-reports: 4.9.10-2+reiser4.0.1 jessie-backport successful wireless install onto HP NoteBook PC 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.) -- 856143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: netboot/USB Image version: https://metztli.it/readOnlyEphemeral/ilhuicateocitlalli.iso Feb 23, 2017, 05:54 AM Date: Feb 24, 2017, 19:21 PST Machine: HP Pavillion 16384 MB SDRAM Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 32765729480 3267092 1% /run /dev/sda6 reiser4 92791120 5951080 86840040 7% / tmpfs tmpfs 8191424 62972 8128452 1% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 8191424 0 8191424 0% /sys/fs/cgroup /dev/sda9 ext2136269 120348 8651 94% /boot tmpfs tmpfs 1638288 8 1638280 1% /run/user/118 tmpfs tmpfs 1638288 20 1638268 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: uname -a Linux ilhuicateocitlalli 4.9.0-2+reiser4.0.1-amd64 #1 SMP Debian 4.9.10-2+reiser4.0.1 (2017-02-18) x86_64 GNU/Linux Reiser4-enabled netboot debian-installar (debian-installer_20150422+deb8u4+b2_amd64.deb), my preliminary release. Small netboot ISO 'burned' to USB stick and began installation until prompted for additional USB media to search for firmware. Inserted additional USB stick with iwlwifi firmware at /lib/firmware/. Debian-installer detected wireless network without issues. During Expert Install, d-i downloaded and installed Jessie-backported components via SSL from metztli.it: linux-jessie-4.9.10-2+reiser4-amd64.deb jessie-reiser4progs-sfrn-4_0_1.deb nfs-common_1.3.4-2.1_amd64.deb libgssapi-krb5-2_1.15-1.1_amd64.deb libk5crypto3_1.15-1.1_amd64.deb libkrb5-3_1.15-1.1_amd64.deb libkrb5support0_1.15-1.1_amd64.deb Alternative URL: https://sourceforge.net/projects/debian-reiser4/files/ And from Debian offical jessie-backports repository, d-i automatically fetched: linux-base_4.3~bpo8+1_all.deb Yielded a smooth subsequent Reiser4-Debian Jessie boot procedure. d-i moves *all* my custom files into /var/log/. After boot, I dmesg[1] showed systemd-udev segmentation faults which manifested in latency; notwithstanding, after an apt-get -t jessie-backports update/dist-upgrade and reboot, dmesg showed no more seg faults. Upon successful Debian Jessie installation, wireless network settings persisted. -- [1] [ 37.404989] systemd-udevd[299]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 in systemd-udevd[55a7be2c7000+3f000] [ 37.405039] systemd-udevd[305]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 [ 37.405047] systemd-udevd[298]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 [ 37.405047] systemd-udevd[301]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 [ 37.405056] systemd-udevd[303]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 [ 37.405061] systemd-udevd[304]: segfault at ed0 ip 0ed0 sp 7ffe1d97c5f8 error 14 [ 37.405064] in systemd-udevd[55a7be2c7000+3f000] [ 37.405067] in systemd-udevd[55a7be2c7000+3f000] [ 37.4050
Bug#858849: marked as done (installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64)
Your message dated Sat, 24 Jun 2017 20:42:40 +0200 with message-id <20170624184240.gi27...@mraw.org> and subject line Re: Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64 has caused the Debian Bug report #858849, regarding installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64 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.) -- 858849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: CD/USB Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on Mar 25 08:35 (2017) Date: Mar 26, 2017, 01:49 Machine: HP Pavilion Notebook PC 2x8192MB RAM Partitions: udev devtmpfs 102400 10240 0% /dev tmpfs tmpfs 3276596 9488 3267108 1% /run /dev/sda6 reiser4 92791120 5182708 87608412 6% / tmpfs tmpfs 8191484 7048 8184436 1% /dev/shm tmpfs tmpfs 51204 5116 1% /run/lock tmpfs tmpfs 81914840 8191484 0% /sys/fs/cgroup /dev/sda9 ext213626980061 48938 63% /boot tmpfs tmpfs 16383008 1638292 1% /run/user/118 tmpfs tmpfs 1638300 20 1638280 1% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Netboot debian-installer was unable to load firmware from second USB for wifi connection; accordingly, in another virtual screen, I mounted the 2nd USB and manually copied the firmware directory onto the installer environment /lib. d-i then detected the wifi signal, etc. I selected a non-expert installation & d-i proceeded normally, by downloading via SSL from metztli.it jessie-packport 4.9.16-1+reiser4.0.1 (2017-03-24), reiser4progs 1.1.x, as well as bp replacements of: nfs-common_1.3.4-2.1_amd64.deb libgssapi-krb5-2_1.15-1.1_amd64.deb libk5crypto3_1.15-1.1_amd64.deb libkrb5-3_1.15-1.1_amd64.deb libkrb5support0_1.15-1.1_amd64.deb In this installer I noticed a lot of debugging verbosity (F4), but overall installation was successfull. In this Reiser4 'retrofitted' d-i, a non-expert install will leave the regular kernel in addition to the Reiser4-enabled bp kernel. < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_0.png > notwithstanding a netstat will show same services available as in a non-reiser4 install. Regular kernel may be purged by user -- who, if having selected option 'Debian Desktop Environment' will see: < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_01.png > Again, as in the last installation, dmesg shows segmentation faults as user operates her/his new jessie, as shown in snapshot: < https://metztli.it/readOnlyEphemeral/xiuhcohuatl_02.png > which introduce latency in the operation of the newly installed jessie. These issues will go away by doing: apt-get -t jessie-backports update apt-get -t jessie-backports dist-upgrade Except that non-expert install does not provide jessie-backports option or by default. The user thus has to add directive: deb http://ftp.debian.org/debian jessie-backports main (at least) to her/his /etc/apt/sources.list Finally, unlike user who reported bug 858078 with i915, < https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > this system booted normally into a GUI without modification on my part: lsmod | grep i915 i915 1241088 5 drm_kms_helper155648 1 i915 drm 360448 6 i915,drm_kms_helper i2c_algo_bit 16384 1 i915 video 40960 1 i915 button 16384 1 i915
Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU
Control: tag -1 moreinfo - d-i Control: severity -1 normal Geert Stappers (2016-09-19): > Control: -1 moreinfo > Stop > > On Mon, Sep 19, 2016 at 11:03:26PM +0300, Oksana Andrusiv wrote: > > > > The installation of the base system hangs. > > The very last message in log console is "installed discover". > > The issue was reproduced in 100% of attempts with and without network > > mirror. > > > > The debian 8 is currently in use on the same laptop thus I suppose it is a > > new > > problem. > > Good that the new problem is being reported. > > Please boot with 'priority=low' to get more messages > and report back.. > > See https://www.debian.org/releases/stretch/arm64/ch05s03.html.en for > additional > information. Hi Oksana, It's been a few months already and we didn't hear back from you. We can't do anything if we don't get any feedback… KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU
Processing control commands: > tag -1 moreinfo - d-i Bug #838320 [installation-reports] installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU Added tag(s) moreinfo. Bug #838320 [installation-reports] installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU Removed tag(s) d-i. > severity -1 normal Bug #838320 [installation-reports] installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU Severity set to 'normal' from 'critical' -- 838320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Preseeding the crypto password
Hi, Sean M (2016-09-21): > Hi all, > > I have a script that does the following: > > --- > #!/bin/sh > > set -e > > . /usr/share/debconf/confmodule > > PASS="x" > > db_set partman-crypto/passphrase $PASS > db_set partman-crypto/passphrase-again $PASS > db_go > --- > > It is called here in the preseed: > > d-i partman/early_command > > I would do it in d-i preseed/early_command, but partman-crypto/passphrase > doesn't seem to be available that early? Why go through a script when you can just set the parameters through tha command line, or through a preseed file (since version 77 in Debian)? > Unfortunately, after it runs this script (successfully) I still get > prompted to enter the encryption password. How would I get this question to > stick? Here's the relevant portion of the logs: > > Sep 20 23:01:33 log-output: + PASS=x > Sep 20 23:01:33 log-output: + db_set partman-crypto/passphrase x > Sep 20 23:01:33 log-output: + _db_cmd SET partman-crypto/passphrase x > Sep 20 23:01:33 log-output: + IFS= printf %s\n SET > partman-crypto/passphrase x > Sep 20 23:01:33 log-output: + IFS= > Sep 20 23:01:33 log-output: read -r _db_internal_line > Sep 20 23:01:33 log-output: + RET=value set > Sep 20 23:01:33 log-output: + return 0 > Sep 20 23:01:33 log-output: + db_set partman-crypto/passphrase-again x > Sep 20 23:01:33 log-output: + _db_cmd SET > partman-crypto/passphrase-again x > Sep 20 23:01:33 log-output: + IFS= printf %s\n SET > partman-crypto/passphrase-again x > > Sep 20 23:01:33 log-output: + IFS= > Sep 20 23:01:33 log-output: read -r _db_internal_line > Sep 20 23:01:33 log-output: + RET=value set > Sep 20 23:01:33 log-output: + return 0 > Sep 20 23:01:33 log-output: + db_go > Sep 20 23:01:33 log-output: + _db_cmd GO > Sep 20 23:01:33 log-output: + IFS= printf %s\n GO > Sep 20 23:01:33 log-output: + IFS= > Sep 20 23:01:33 log-output: read -r _db_internal_line > Sep 20 23:01:33 log-output: + RET=ok > Sep 20 23:01:33 log-output: + return 0 > Sep 20 23:01:33 kernel: [ 48.500059] Btrfs loaded > Sep 20 23:01:33 kernel: [ 48.515474] JFS: nTxBlock = 8192, nTxLock = 65536 > Sep 20 23:01:33 kernel: [ 48.528375] SGI XFS with ACLs, security > attributes, realtime, no debug enabled > Sep 20 23:01:33 md-devices: mdadm: No arrays found in config file or > automatically > Sep 20 23:01:33 partman: No matching physical volumes found > Sep 20 23:01:33 partman: Reading all physical volumes. This may > take a while... > Sep 20 23:01:35 anna-install: Installing cdebconf-newt-entropy > Sep 20 23:01:35 anna[11775]: DEBUG: resolver (libnewt0.52): package > doesn't exist (ignored) > Sep 20 23:01:35 anna[11775]: DEBUG: retrieving cdebconf-newt-entropy 0.33 > Sep 20 23:01:35 anna[11775]: 2016-09-20 23:01:35 > URL:http://mirrors.kernel.org/ubuntu/pool/main/c/cdebconf-entropy/cdebconf-newt-entropy_0.33_amd64.udeb > [18752/18752] -> > "/var/cache/anna/cdebconf-newt-entropy_0.33_amd64.udeb" [1] > Sep 20 23:01:35 anna[11775]: DEBUG: retrieving > libdebian-installer4-udeb 0.102ubuntu1.1 > Sep 20 23:01:35 anna[11775]: 2016-09-20 23:01:35 > URL:http://mirrors.kernel.org/ubuntu/pool/main/libd/libdebian-installer/libdebian-installer4-udeb_0.102ubuntu1.1_amd64.udeb > [18734/18734] -> > "/var/cache/anna/libdebian-installer4-udeb_0.102ubuntu1.1_amd64.udeb" > [1] > Sep 20 23:01:35 anna[11775]: DEBUG: retrieving libslang2-udeb 2.3.0-2ubuntu1 > Sep 20 23:01:35 anna[11775]: 2016-09-20 23:01:35 > URL:http://mirrors.kernel.org/ubuntu/pool/main/s/slang2/libslang2-udeb_2.3.0-2ubuntu1_amd64.udeb > [255104/255104] -> > "/var/cache/anna/libslang2-udeb_2.3.0-2ubuntu1_amd64.udeb" [1] > Sep 20 23:01:35 anna-install: Installing partman-crypto-dm > Sep 20 23:01:35 partman: mke2fs 1.42.13 (17-May-2015) > Sep 20 23:01:35 partman-crypto: kernel entropy_avail: 126 bits If you're installing Ubuntu, you should be asking on Ubuntu support channels. KiBi. signature.asc Description: Digital signature
Bug#838503: debian-installer: mdadm should not start syncing RAID1 arrays at full speed during installation
Hi Baptiste, Baptiste Jonglez (2016-09-21): > When creating a RAID1 array in the debian-installer and using it for > the installation, mdadm immediately starts syncing the disks of the > RAID array. > > This is a bad idea, because the subsequent install will be really slow > on rotational disks (linear disk access by mdadm and random disk > access by dpkg). On a fairly recent computer with 2 SATA disks, the > installation took around 20 minutes before even arriving to the > tasksel step. Well, I can understand the argument, but the user could very well expect disks to be in mirror mode as soon as possible, and not wait until a few days after the installation before the initial sync ends… > I can see two solutions: > > 1) lower the speed of the syncing operation, by setting the >"dev.raid.speed_limit_max" sysctl setting to e.g. 1000; I'm not sure it would be a good idea to stick a hardcoded value there, even if we were to lower the available bandwidth… Too many different cases, be it about actual hardware, disk sizes, etc. KiBi. signature.asc Description: Digital signature
Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)
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 >> the installation process. > > Thanks for your follow-ups. > > Any chance you could attach the installer's syslog file? It should be > stored under /var/log/installer. > > > KiBi. Hi KiBi, I did attach all the log files to one of my messages — as a gzipped cpio archive. The log files are at: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77 The message itself with the attachment is at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77 Let me know if you would like me to perform further tests. Hope that helps! Rick
Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)
Hi again, Rick Thomas (2017-06-24): > I did attach all the log files to one of my messages — as a gzipped cpio > archive. > > The log files are at: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77 > > The message itself with the attachment is at: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77 > > Let me know if you would like me to perform further tests. There's no syslog in there? $ zcat installer-logs.cpio.gz | cpio -it | sort 127 blocks . cdebconf hardware-summary lsb-release status KiBi. signature.asc Description: Digital signature
Bug#834974: Info received (installation-reports: Stretch 9.0.0 on Cubox-i4Pro fails to boot after install)
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 files to one of my messages — as a gzipped cpio >> archive. >> >> The log files are at: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=834974;filename=installer-logs.cpio.gz;msg=77 >> >> The message itself with the attachment is at: >>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834974#77 >> >> Let me know if you would like me to perform further tests. > > There's no syslog in there? > >$ zcat installer-logs.cpio.gz | cpio -it | sort >127 blocks >. >cdebconf >hardware-summary >lsb-release >status > > > KiBi.
Bug#762055: marked as done (d-i.debian.org: run calc-release-status regularly to catch missing tags)
Your message dated Sun, 25 Jun 2017 03:21:35 +0200 with message-id <20170625012135.ga...@mraw.org> and subject line Re: Bug#762055: d-i.debian.org: run calc-release-status regularly to catch missing tags has caused the Debian Bug report #762055, regarding d-i.debian.org: run calc-release-status regularly to catch missing tags 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.) -- 762055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: d-i.debian.org Severity: normal Part of a debian-installer upload is about including a file computed by calc-release-status; it's somewhat frustrating to see it fail because this or that tag wasn't pushed to a repository, meaning a failed checkout/translation lookup for said package. Then I get to chase people instead of keeping on preparing the upload. It would probably be a good idea to integrate that in a crontab to help detect such issues as soon as possible, and to get a quicker release step when everything else is ready. Mraw, KiBi. --- End Message --- --- Begin Message --- Cyril Brulebois (2014-09-18): > Part of a debian-installer upload is about including a file computed > by calc-release-status; it's somewhat frustrating to see it fail > because this or that tag wasn't pushed to a repository, meaning a > failed checkout/translation lookup for said package. Then I get to > chase people instead of keeping on preparing the upload. > > It would probably be a good idea to integrate that in a crontab to > help detect such issues as soon as possible, and to get a quicker > release step when everything else is ready. Closing as a duplicate of #763578… Oops. KiBi. signature.asc Description: Digital signature --- End Message ---
Bug#791999: marked as done (d-i.debian.org: keep artifacts for ttf-cjk-compact)
Your message dated Sun, 25 Jun 2017 03:24:31 +0200 with message-id <20170625012431.ga...@mraw.org> and subject line Re: Bug#791999: d-i.debian.org: keep artifacts for ttf-cjk-compact has caused the Debian Bug report #791999, regarding d-i.debian.org: keep artifacts for ttf-cjk-compact 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.) -- 791999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: d-i.debian.org Severity: normal Comparing fonts in ttf-cjk-compact is a bit hard, so it might be nice to store bits of the build tree, like characters/glyphs. My memory is a bit sketchy, but a rebuild should do the job, even if it isn't too practical. Various ideas: - The jenkins instance might be of some help here, if we were to store some artifacts for all builds. - Shipping the said bits in a dbg package would be an alternative way, making it possible to compare everything just with the archive (and snapshots etc.). Mraw, KiBi. --- End Message --- --- Begin Message --- Cyril Brulebois (2015-07-10): > Package: d-i.debian.org > Severity: normal > > Comparing fonts in ttf-cjk-compact is a bit hard, so it might be nice to > store bits of the build tree, like characters/glyphs. My memory is a bit > sketchy, but a rebuild should do the job, even if it isn't too practical. > > Various ideas: > - The jenkins instance might be of some help here, if we were to store >some artifacts for all builds. > - Shipping the said bits in a dbg package would be an alternative way, >making it possible to compare everything just with the archive (and >snapshots etc.). We moved away from using ttf-cjk-compact, so closing this bug report. KiBi. signature.asc Description: Digital signature --- End Message ---
Speeding up l10n/calc-release-status
Hi, It's been an annoyance during all releases: this script processes all packages in turn, and that takes quite a while. I've tried to make it run in parallel by defining a function and calling parallel on it, but it would need a few other functions and variables to be exported as well, so I've taken an easier route and split the interesting part into a calc-release-status-helper script, to be called for each and every package. Now, calc-release-status will treat packages in a parallel manner, using as many cores as available, and it now finishes in under 3 minutes on my d-i development machine, which makes me quite happy. :) Other consequence: output will no longer be sorted by package name due to parallelism. Current errors are: E: error getting madison info for partman-newworld for 'testing' E: error getting madison info for partman-zfs for 'testing' E: error getting madison info for prep-installer for 'testing' E: error getting madison info for quik-installer for 'testing' E: error getting madison info for yaboot-installer for 'testing' partman-zfs is kfreebsd-* only; others are powerpc-specific, which is no longer a release architecture. Christian, which update would be the best one to reflect those changes? Add a minus sign after those packages in packages_list? Or remove them from there entirely? Note: It's still on my todo list to make it run on dillon regularly, instead of waiting until release day to possibly notice missing git pushes (see bug report #762055). KiBi. signature.asc Description: Digital signature
Bug#841842: debian-installer: should use EXT4's native file-system-level encryption
Control: tag -1 moreinfo Hi Marcos, Marcos Mobley (2016-10-23): > it would be nice to be able to use EXT4's native file-system-level > encryption instead of LUKS. As far as I understand it, this would only protect the contents of a given directory instead of the whole filesystem, so that doesn't look like a suitable replacement for LUKS? If my quick research is correct (you didn't much information in your bug report), then I think the admin is supposed to be setting this up; and that's not really a job for the Debian Installer. KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#841842: debian-installer: should use EXT4's native file-system-level encryption
Processing control commands: > tag -1 moreinfo Bug #841842 [debian-installer] debian-installer: should use EXT4's native file-system-level encryption Added tag(s) moreinfo. -- 841842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#843943: debian-cd: please mention the dinstall serial in a trace file
Steve McIntyre (2017-04-25): > Pushed to the setup git repo, so marking this fixed. Thanks for the patch! Hm, I'm not seeing any trace file for this? KiBi. signature.asc Description: Digital signature
Bug#837060: debootstrap: Do not install packages of Priority:required for buildd variant
Hi, Quoting Cyril Brulebois (2017-06-24 20:23:25) > Julien Cristau (2016-09-12): > > This is a transient situation because some Essential packages' > > dependencies changed. I'd consider this a bug in the archive, not in > > debootstrap. > Any reasons to keep this bug report open then? Seen no objections, so I'm > tempted to close it. But... the buildd variant still explicitly (and not only implicitly through dependencies of essential:yes packages) installs Priority:required packages, no? cheers, josch signature.asc Description: signature
Bug#865473: installation-reports, clean install debian-9.0.0-amd64-xfce-CD-1.iso, grub not working on /dev/sdc
Hello, On 24.06.2017 18:34, Cyril Brulebois wrote: Hi, Rolf Reintjes (2017-06-24): Hello KiBi, On 24.06.2017 18:02, Cyril Brulebois wrote: Thanks for your report. Can you please attach the installer's syslog, which might have some clue? You'll find it under the /var/log/installer directory. Please find attached the file syslog from /var/log/installer. Thanks! This looks weird: Jun 20 18:33:58 grub-installer: info: Installing grub on '' Are you sure you selected the /dev/sdc entry when you were prompted where to install grub, and not the default “Enter manually” which comes with an empty string by default? I did the installation once again and had got the same problem. I downloaded the iso from another location: http://debian.netcologne.de/debian-cd/9.0.0/amd64/iso-cd/debian-9.0.0-amd64-xfce-CD-1.iso I took another USB-stick than before for installation. During installation this USB-stick was /dev/sdc and the debian system was /dev/sdb . I selected /dev/sdb for grub install. When rebooted grub came with this error message: "error: file '/boot/grub/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> " I solved the problem the same way as before. Best regards Rolf
