Processed: Re: Bug#721578: debian-installer: LVM + ZFS fails to work
Processing commands for cont...@bugs.debian.org: reassign 721578 partman-zfs Bug #721578 [debian-installer] debian-installer: LVM + ZFS fails to work Bug reassigned from package 'debian-installer' to 'partman-zfs'. Ignoring request to alter found versions of bug #721578 to the same values previously set Ignoring request to alter fixed versions of bug #721578 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 721578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137810437812184.transcr...@bugs.debian.org
Bug#721578: debian-installer: LVM + ZFS fails to work
reassign 721578 partman-zfs thanks Quoting Dan Greene (dan-gre...@wi.rr.com): At this point, there was an error message, but there didn't seem to be anything related to ZFS in /var/log/messages. I chose to contiune the installation, and the partitioning screen recognized those partitions as ZFS. However, those partitions weren't mounted at the next stage, and the installation failed when trying to install the kernel due to lack of space. Hello, ZFS on Linux is still work in progress. Recent changes were committed and uploaded but I'm unsure whether everything in Debian is ready for ZFS support, which includes the installer. CC'ing Aron Xu who is, if I'm correct, working on this. signature.asc Description: Digital signature
Bug#721578: debian-installer: LVM + ZFS fails to work
Hi, On 02/09/13 02:38, Dan Greene wrote: In the installer: Did guided partitioning using LVM, with seperate /usr, /home, /tmp, and /var. Choose Configure ZFS, configuring /usr, /hone, and /var to use zfs. That's not a sensible setup, by the way. Only a single partition is needed to form a ZFS 'pool', and then ZFS allocates its own 'logical volumes' (usr, home, var...) out of that. So, ZFS more or less replaces LVM functionality. Maybe there ought to be a 'Guided partitioning using ZFS' option... That's not to say it absolutely cannot work. I'm not sure. There could be a valid use case if someone merely wants to try ZFS and dual-boot it, if their entire disk is already LVM. What does work well is using LVM logical volumes as virtual hard disks for a Xen or KVM guest for example. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52247851.1060...@pyro.eu.org
RE: Tajik Language - Adding support for a new language
Hello everyone! Just would like to inform that Tajik translation for Debian installer is now 100%! Hope to see full Tajik version for the Debian installer soon, including OSs like Ubuntu and others. However, these 100% is still a subject to improve and change the existing translations during the tests. Thanks to everyone who helped to add Tajik Victor --- Victor Ibragimov victor.ibragi...@gmail.com -Original Message- From: Christian PERRIER [mailto:bubu...@debian.org] Sent: 19 август 2013 с. 01:19 To: debian-boot@lists.debian.org; debian-i...@lists.debian.org; 'ubuntu-translators' Subject: Re: Tajik Language - Adding support for a new language Quoting Victor Ibragimov (victor.ibragi...@gmail.com): Dear Christian, Could you please, check which installer is used by Kazakh language: text-based or graphical? text-based I am just interested if they also use gtk (graphical) since we have similar special characters. From what the translator told me, Kazakh is possible to render at the console. It's indeed maybe possible that Tajik can, also. Jere is the list of characters used by Kazakh, as it was sent by the translator: аәбвгғдеёжзийкқлмнңоөпрстуұүхфһцчшщъыіьэюяАӘБВГҒДЕЁЖЗИЙКҚЛМНҢОӨПРСТУҰҮФХҺЦЧШЩЪİЬЭЮЯ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5224788d.a89b700a.0d1f.c...@mx.google.com
Bug#721578: debian-installer: LVM + ZFS fails to work
Steven Chamberlain: So, ZFS more or less replaces LVM functionality. Maybe there ought to be a 'Guided partitioning using ZFS' option... Yes, of course. Adding this to partman-zfs is not trivial though (most of partman-zfs mimics partman-lvm, but this part required extra work and I didn't have time when I did the initial port). That's not to say it absolutely cannot work. I'm not sure. There could be a valid use case if someone merely wants to try ZFS and dual-boot it, if their entire disk is already LVM. What does work well is using LVM logical volumes as virtual hard disks for a Xen or KVM guest for example. Note that LVM support (with readonly metadata) in kFreeBSD D-I is still incomplete. Most of the pieces are there though, I think you just need to manually load the geom_lvm kernel modules. -- Robert Millan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52247c37.10...@debian.org
Bug#645210: marked as done (debian-installer: grub2 setup for a new drive misses a Windows boot choice from the original drive)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #645210, regarding debian-installer: grub2 setup for a new drive misses a Windows boot choice from the original drive 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.) -- 645210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Version: i386 netinst as of October 5, 2011 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? I decided to install Debian on a new disk drive and preserve the Windows installation on the original drive. I downloaded the latest i386 netinst ISO image of Debian Installer, burned it on a DVD and booted off it. * What exactly did you do (or not do) that was effective (or ineffective)? I chose the new drive for simple partitioning. I chose to install Grub2 in MBR of the original drive. * What was the outcome of this action? I did not see Windows as a boot option. (This took a worse turn when the udev in the initial RAM disk image loaded a kernel module radeon for my video card ATI Radeon HD 3600, apparently in an attempt to provide a frame buffer for the text mode, and the video card showed garbage. It took a while to add an option blacklist=radeon to the kernel command line at boot time and add a line blacklist radeon to a file in /etc/modprobe.d). * What outcome did you expect instead? I expected to see a boot option to start from a partition in the original disk drive. Here is how I worked around the issue. I booted off the netinst DVD into a rescue mode. Ran update-grub and it did not show the Windows partition of the original drive. Inspected the output of os-prober. I believe it did not show Windows either. I then ran fdisk -l and I think I saw my original disk drive with its Windows partition. After inspecting os-prober I figured it depended on the list of mounted partitions. I added the Windows partition to /etc/fstab, /dev/sda1 /c ntfsauto0 0 Unfortunately, mount /c failed because the target root partition where I chrooted did not have modules of the rescue kernel. I cannot remember how I succeeded in mounting the partition before re-running update-grub. Perhaps, I returned or rebooted to the dialogs of the rescue mode of Debian Installer and chose to re-configure Grub2 in the dialogs. I could see my Windows partition of the original drive in the bootloader's list at boot time. I could successfully start Windows. Here is my opinion on a possible root cause. It seems that Debian Installer does not attempt to mount partitions on drives other than the one selected for partitioning. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- reassign 619236 debian-installer severity 619236 normal reassign 705484 debian-installer thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, Holger signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#623735: marked as done (installation-reports: Installer MOVES extended partition when using manual partitioning method)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #623735, regarding installation-reports: Installer MOVES extended partition when using manual partitioning method 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.) -- 623735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Tags: d-i This is a Debian 6 (squeeze) installation using the 6.0.1a i386 net install CD. After selecting manual partitioning, existing primary partition /dev/sda1 was chosen as the root partition, and an existing logical partition /dev/sda5 was selected for swap, with both to be formatted. The root partition as ext4, the swap partition as swap. After the installation completed, the extended partition had been moved by 61 sectors further into the disk. This problem is VERY repeatable, and has also been noted on the current Ubuntu installer (Ubuntu 10.10). Existing partitions should absolutely not be moved unless the user says so. The following are 3 listings of the partition table before and after the installation, where it can be seen that the extended partition starts 61 sectors further into the disk after the installation completes: BEFORE: (fdisk -l fdisk -lu cfdisk) ~~~ Disk /dev/sda: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 650 5221093+ 83 Linux /dev/sda2 651208811550735 f Win95 Ext'd (LBA) /dev/sda5 651 800 1204843+ 82 Linux swap /dev/sda6 801208810345828+ b Win95 FAT32 Disk /dev/sda: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders, total 33554432 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sda1 6310442249 5221093+ 83 Linux /dev/sda2104422503354371911550735 f Win95 Ext'd (LBA) /dev/sda51044231312851999 1204843+ 82 Linux swap /dev/sda6128520633354371910345828+ b Win95 FAT32 Partition Table for /dev/sda ---Starting--- EndingStart Number of # Flags Head Sect Cyl ID Head Sect Cyl SectorSectors -- - --- --- 1 0x00110 0x83 254 63 649 6310442187 2 0x0001 650 0x0F 254 63 10231044225023101470 3 0x00000 0x00000 0 0 4 0x00000 0x00000 0 0 5 0x0011 650 0x82 254 63 799 63 2409687 6 0x0011 800 0x0B 254 63 1023 6320691657 AFTER: (fdisk -l fdisk -lu cfdisk) ~~ Disk /dev/sda: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 650 5221093+ 83 Linux /dev/sda2 651208811550704+ f Win95 Ext'd (LBA) /dev/sda5 651 800 1204843+ 82 Linux swap /dev/sda6 801208810345828+ b Win95 FAT32 Disk /dev/sda: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders, total 33554432 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sda1 6310442249 5221093+ 83 Linux /dev/sda2104423113354371911550704+ f Win95 Ext'd (LBA) /dev/sda51044231312851999 1204843+ 82 Linux swap /dev/sda6128520633354371910345828+ b Win95 FAT32 Partition Table for /dev/sda ---Starting--- EndingStart Number of # Flags Head Sect Cyl ID Head Sect Cyl SectorSectors -- - --- --- 1 0x00110 0x83 254 63 649 6310442187 2 0x000 62 650 0x0F 254 63 10231044231123101409 3 0x00000 0x00000 0 0 4 0x00000 0x00000 0 0 5 0x001
Bug#702434: marked as done (installation-reports: isolinux.bin is missing or corrupted)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #702434, regarding installation-reports: isolinux.bin is missing or corrupted 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.) -- 702434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Dear Maintainer, I downloaded the iso, and checked its md5sum. I then installed it on a u$When I booted, it said isolinux.bin is missing or corrupted. However, is$I did it also with the cd iso, with the same results. It did work using unetbootin and writing to a CD, and installed fine -- Package-specific info: Boot method: usb Image version: wheezy rc1 both netinstall and CD for amd64 http://www.de$Date: Date and time of the install -- Package-specific info: Boot method: Image version: Date: Date and time of the install Machine: Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=7.0 (wheezy) - installer build 20130211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04) lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c597] lspci -knn: 00:1f.2 SATA controller
Bug#667802: marked as done (installation-reports: SunBlade1000 Netinstall with USB drive sda with firmware /boot / on sdb Won't boot w/o USB drive.)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #667802, regarding installation-reports: SunBlade1000 Netinstall with USB drive sda with firmware /boot / on sdb Won't boot w/o USB drive. 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.) -- 667802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Tags: d-i Booting from a netinst CD with a USB drive plugged in with a non-free firmware. Installation assigns the USB as sda and the system hard drive as sdb. Booting without the USB drive drops to a very limited shell. Booting with the USB drive plugged in is normal, GUI loads etc. -- Package-specific info: Boot method: CD Image version: debian-6.0.4-sparc-netinst.iso from cdimage.debian.org Date: Date and time of the install Machine: Sun Blade 1000 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=6.0 (squeeze) - installer build 20110106+squeeze4 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 2.6.32-5-sparc64 #1 Mon Jan 16 16:15:31 UTC 2012 sparc64 GNU/Linux lspci -knn: :00:05.0 Bridge [0680]: Oracle Corporation RIO EBUS [108e:1100] (rev 01) lspci -knn: :00:05.1 Ethernet controller [0200]: Oracle Corporation RIO 10/100 Ethernet [eri] [108e:1101] (rev 01) lspci -knn: Kernel driver in use: gem lspci -knn: :00:05.2 FireWire (IEEE 1394) [0c00]: Oracle Corporation RIO 1394 [108e:1102] (rev 01) lspci -knn: :00:05.3 USB Controller [0c03]: Oracle Corporation RIO USB [108e:1103] (rev 01) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: :00:06.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c875 [1000:000f] (rev 37) lspci -knn: Kernel driver in use: sym53c8xx lspci -knn: :00:06.1 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c875 [1000:000f] (rev 37) lspci -knn: Kernel driver in use: sym53c8xx lspci -knn: 0001:00:04.0 SCSI storage controller [0100]: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter [1077:2200] (rev 05) lspci -knn: Kernel driver in use: qla2xxx usb-list: usb-list: Bus 01 Device 01: OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.32-5-sparc64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB Receiver [046d:c501] usb-list:Level 01 Parent 01 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: Logitech usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 02 Driver usbhid usb-list: usb-list: Bus 01 Device 03: HP Basic USB Keyboard [03f0:0024] usb-list:Level 01 Parent 01 Port 01 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: CHICONY usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 01 Driver usbhid usb-list: usb-list: Bus 01 Device 04: DataTraveler 2.0 [08ec:2038] usb-list:Level 01 Parent 01 Port 02 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: Kingston usb-list:Interface 00: Class 08(mstor) Subclass 06 Protocol 50 Driver usb-storage prtconf: System Configuration: Sun
Bug#688064: marked as done (installation-reports: Successful classical install but wrong keyboard layout in GRUB)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #688064, regarding installation-reports: Successful classical install but wrong keyboard layout in GRUB 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.) -- 688064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal Tags: d-i Boot method: USB stick + netinst Image version: http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz + http://cdimage.debian.org/cdimage/wheezy_di_beta2/amd64/iso-cd/debian-wheezy-DI-b2-amd64-netinst.iso Date: 2012-09-18 Machine: Classical desktop computer Partitions: # df -Tl Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 239777836 7642036 220132012 4% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 202568 632201936 1% /run /dev/disk/by-uuid/add3ca6c-fc4f-439b-84a0-397a5bf6c663 ext4 239777836 7642036 220132012 4% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 1229240 232 1229008 1% /run/shm # lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) 00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01) 00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01) 00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01) 00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01) 00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] (rev 01) 01:01.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) # lspci -n 00:00.0 0600: 8086:2e30 (rev 03) 00:02.0 0300: 8086:2e32 (rev 03) 00:1b.0 0403: 8086:27d8 (rev 01) 00:1d.0 0c03: 8086:27c8 (rev 01) 00:1d.1 0c03: 8086:27c9 (rev 01) 00:1d.2 0c03: 8086:27ca (rev 01) 00:1d.3 0c03: 8086:27cb (rev 01) 00:1d.7 0c03: 8086:27cc (rev 01) 00:1e.0 0604: 8086:244e (rev e1) 00:1f.0 0601: 8086:27b8 (rev 01) 00:1f.1 0101: 8086:27df (rev 01) 00:1f.2 0101: 8086:27c0 (rev 01) 01:01.0 0200: 10b7:9200 (rev 78) 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:[E] Overall install:[O] Comments/Problems: I did follow the classical install path, only did I choose French as the locale. The machine rebooted fine and I'm using the installed system to write this report. I did find only I small problem: When I go in GRUB when the system boots, the keyboard is behaving QWERTY while it's an AZERTY keyboard and that it was detected as such by the Debian Installer. In Squeeze the keyboard layout was also wrongly set by the Debian Installer (QWERTY instead of AZERTY), so it's not a regression, but it's still a point that could usefully be improved. Thanks for your wonderful work. Warm regards, -- 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.
Bug#673548: marked as done (installation-reports: black screen after reboot of installation)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #673548, regarding installation-reports: black screen after reboot of 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.) -- 673548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? - normal installation of debian wheezy 14.05.2012 - hardware: lenovo T400 (two grafikcards. Mobility Radeon HD 3400 was on. intel off) - the logs shows that the radeon driver was loaded * What exactly did you do (or not do) that was effective (or ineffective)? effective: - to switch the grafikcard from ati to intel - after boot I deactivated kms with radeon.modeset=0 - rebooting with ati. It works but I seems that the hardware acceleration is still not working. Regards Daniel -- Package-specific info: Boot method: Image version: Date: Date and time of the install Machine: Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=7.0 (wheezy) - installer build 20120508 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux chaosbook 3.2.0-2-amd64 #1 SMP Sun Apr 15 16:47:38 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: Subsystem: Lenovo Device [17aa:20e0] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn: Subsystem: Lenovo Device [17aa:20e6] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ee] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20f0] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20f0] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20f0] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20f1] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20f2] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) lspci -knn: Kernel driver in
Bug#700656: marked as done (installation-reports: Corrupt screens after grub menu with UEFI)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #700656, regarding installation-reports: Corrupt screens after grub menu with UEFI 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.) -- 700656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, *** 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 lines *** -- Package-specific info: Boot method: CD Image version: wheezy-DI-b4-amd64-netinst, wheezy-DI-20130215-5-amd64-netinst Date: Fri 2013-02-15 19:00 UTC Machine: HP EliteBook 8350w Partitions: target media had no partition table prio to install Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: The boot of the install media via EFI succeeded and the grub menu(s), presented; however, when an installation method was selected the screen became unreadable and no further progress attempted. If a text installation was selected, the screen went black an pressing ESC caused it to flash (once for each keypress). If a graphical installation was selected, colorful pixel vomit is displayed. An EFI boot using Ubuntu 12.10 (amd64) live/install media works and can install a system that can boot via EFI. BIOS mode booting of the install media (b4) does work and does install a system that will boot via BIOS. Booting and installing in a VirtualBox instance works no matter what boot method was used. This report was completed in a VirtualBox instance. The hardware summary below is from a Squeeze BIOS install boot. -- 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=7.0 (wheezy) - installer build 20121114 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == /proc/cmdline: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=657a2b9d-f06f-4a8f-8771-ccd7220957e9 ro quiet lspci: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) lspci: 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) lspci: 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) lspci: 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) lspci: 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) lspci: 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) lspci: 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) lspci: 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) lspci: 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) lspci: 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) lspci: 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) lspci: 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) lspci: 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) lspci: 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family)
Bug#700976: marked as done (debian-installer: Failed to boot installed UEFI system)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #700976, regarding debian-installer: Failed to boot installed UEFI system 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.) -- 700976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Version: 2.49 Severity: critical Justification: System failed to boot Dear Maintainer, When installing Wheezy using the RC1 image and UEFI the installed system failed to boot. Image is attached with the error. It looks like it failed to install it at all. When installing I used default options on everything but using Swedish as language and entering no root password, choosing sudo instead. I also deselected the desktop and print server installation options. This test was performed in VirtualBox on Wheezy configured to use Debian x64 as OS with all other settings set to default values. This the second bug from #700974 -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso Date: 18th feb 2013 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:[E] attachment: uefi.png---End Message--- ---BeginMessage--- reassign 619236 debian-installer severity 619236 normal reassign 705484 debian-installer thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, Holger signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#704605: marked as done (installation-reports: kernel panic Wheezy)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #704605, regarding installation-reports: kernel panic Wheezy 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.) -- 704605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Kernel Panic requiring hard reset possibly having to do with lightdm-gtk-gre * What exactly did you do (or not do) that was effective (or ineffective)? On the Wheezy RC1 I installed the linux-image-486 and got a similar result (kernel panics requiring hard reset), but I was able to use the system for a few minutes as opposed to panic on startup * What was the outcome of this action? kernel panic * What outcome did you expect instead? a normally functioning system (no kernel panics that lock the system, make it unusable and require a hard reset) *** End of the template - remove these lines *** -- Package-specific info: Boot method: CD Image version: cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ from April 2, 201 2013 Date: Date and time of the install Machine: Dell Dimension 2400 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] 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: Two major problems: 1)kernel panic as described above 2)initial attempts to install failed and required a hard reset due to a cryptic error message(almost illegible): Undefined videomode number: 314. The workaround for this was to press TAB and set vga=normal instead of the default setting of 788. The only reason I was able to decipher this illegible message was to attempt to install Ubuntu 13.04 and I got the same message that was readable. The Ubuntu installation did not hang and was going to let me continue. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=7.0 (wheezy) - installer build 20130211 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux dellian 3.2.0-4-486 #1 Debian 3.2.35-2 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn:
Bug#633306: closed by Holger Levsen hol...@layer-acht.org (dealing with old installation-reports)
Hello Holger, On Mon, Sep 02, 2013 at 01:57:13PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the installation-reports package: #633306: Install troubles with GPT partions (and other issues) It has been closed by Holger Levsen hol...@layer-acht.org. The first reaction ever to this bug report. (Except for my own reply). thank you for submitting installation reports, much appreciated. No problem. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if Hopefully. A trace in the bug log would also be *much appreciated*. - they (finally) indicated success and/or n/a (though I was never asked to try something …) (Although f) was solved in a different bug report IIRC, at least no longer present) - I know from first hand experience that the functionality is working in Wheezy and/or Hopefully at least the items indicated with serious, especially the GPT ones. - they only contained very little information and/or This would be strange. At least I would've appreciated which information is missing. I try to produce bug reports with sufficient quality to debug the issues; at least as far as possible beeing a layman at the installer. - they contained user errors and/or Maybe a) (but then this could be clearer in the user guides, and it is only wishlist). I don't see this for the other items. - they were caused by broken hardware and/or The hardware is still working fine, actually I'm typing the reply now at this machine. The only issue is a spourious message about fans, but this is only happening at boot time (sometimes) and I do not boot when it is present but rather reboot. Also I would not see how this could possible influence the bug report - they have been from a development phase where things were not stable and/or This is possible. But at least a simple we know and we are working on a fix, thanks should have been possible. - they are quite old (and thus likely fixed today) and/or likly fixed today, well, I only close my bugs *iff* they are closed, not when they are likley closed. I might do this, but only if the submitter fails to react[1] (and I've not been contacted, see above). At least for my packages Debian does not hide bugs. - moreinfo was asked and not given or Nope. (The contrary, I asked if I should provide more information in #10) - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) n/a. If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. Well, given the very broad statement without any clear indication to which sub issue you are referring it is hard to see which part should be reopened / which was closed incorrectly. And I'm not going to zap the disk for a possible new bug report which might simply get closed again without comment in 2015 or so. Disappointed. Helge [1] #715529 is a possible case for this. So far, I've tagged it appropriately and downgraded it. I might eventually close it, but not without several further attempts to contact the submitter. Received: (at submit) by bugs.debian.org; 9 Jul 2011 11:49:56 + X-Spam-Checker-Version: SpamAssassin 3.3.1-bugs.debian.org_2005_01_02 (2010-03-16) on busoni.debian.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=4.0 tests=BAYES_00,FH_HELO_EQ_D_D_D_D, FOURLA,HAS_PACKAGE,HELO_DYNAMIC_IPADDR,PGPSIGNATURE autolearn=ham version=3.3.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0. Tokens: new, 15; hammy, 151; neutral, 303; spammy, 0. spammytokens: hammytokens:0.000-+--H*c:pgp-signature, 0.000-+--H*c:protocol, 0.000-+--H*c:micalg, 0.000-+--H*c:signed, 0.000-+--H*c:pgp-sha1 Return-path: deb...@helgefjell.de Received: from static.213-239-213-133.clients.your-server.de ([213.239.213.133]) by busoni.debian.org with esmtps (SSL3.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from deb...@helgefjell.de) id 1QfW2g-0008Me-Hm for sub...@bugs.debian.org; Sat, 09 Jul 2011 11:49:53 + Received: from localhost (localhost [127.0.0.1]) (uid 502) by static.213-239-213-133.clients.your-server.de with local; Sat, 09 Jul 2011 13:49:41 +0200 id 00E5801F.4E184055.0D96 Date: Sat, 9 Jul 2011 13:49:41 +0200 From: Helge Kreutzmann deb...@helgefjell.de To: sub...@bugs.debian.org Subject: Install troubles with GPT partions (and other issues) Message-ID: 20110709114941.GA3411@Debian-50-lenny-64-minimal Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature;
Processed: dealing with old installation-reports
Processing commands for cont...@bugs.debian.org: reassign 619236 debian-installer Bug #619236 [installation-reports] installation-reports: installation works fine on PS3 now, but we still can't boot after the installation Bug reassigned from package 'installation-reports' to 'debian-installer'. Ignoring request to alter found versions of bug #619236 to the same values previously set Ignoring request to alter fixed versions of bug #619236 to the same values previously set severity 619236 normal Bug #619236 [debian-installer] installation-reports: installation works fine on PS3 now, but we still can't boot after the installation Severity set to 'normal' from 'important' reassign 705484 debian-installer Bug #705484 [installation-reports] installation-reports: installer installs grub-efi-amd64-bin instead of grub-pc Bug reassigned from package 'installation-reports' to 'debian-installer'. Ignoring request to alter found versions of bug #705484 to the same values previously set Ignoring request to alter fixed versions of bug #705484 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 619236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619236 705484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137813233020428.transcr...@bugs.debian.org
Bug#706304: marked as done (installation-report: Receive error Operating System not found at first boot after install)
Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id 201309021553.23982.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #706304, regarding installation-report: Receive error Operating System not found at first boot after install 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.) -- 706304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Version: 2.49 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? EFI install using LVM appeared to go normally, but received Operating System not found on first boot. This also happened with the rc1 version. * What exactly did you do (or not do) that was effective (or ineffective)? I tried doing a grub-install to the two most likely partitions which are /dev/sda2 and /dev/sda1 * What was the outcome of this action? No change in the boot behavior * What outcome did you expect instead? -- Package-specific info: Boot method: netinst CD Image version: debian-wheezy-DI-rc2-amd64-netinst.iso 2013-04-20 17:59 Date: 27 Apr 2013 17:00 EDT Machine: Sony Viao SVS151190X Partitions: df -Tl will do; the raw partition table is preferred Filesystem Type 1K-blocksUsed Available Use% Mounted on /dev/mapper/worksys-root ext4 9611492 2891124 6232128 32% / /dev/sda2ext2 9611492 2891124 6232128 32% /boot /dev/mapper/worksys-home ext4 9611492 2891124 6232128 32% /home tmpfstmpfs6116012 0 6116012 0% /dev devpts devpts 6116012 0 6116012 0% /dev/pts none tmpfs1223204 44 1223160 1% /run Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] 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: The install appeared to be working very well throughout the process until time to boot into the new system. at that point, the screen displayed the Operating System not found message. I then rebooted from the install disk and entered Rescue Mode, and requested a shell from the worksys-root partition which is where I am submitting this installation-report from. -- 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=7.0 (wheezy) - installer build 20130415 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux worksys 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) lspci -knn: Subsystem: Sony Corporation Device [104d:909b] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) lspci -knn: Subsystem: Sony Corporation Device [104d:909c] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) lspci -knn: Subsystem: Sony Corporation Device [104d:909b] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) lspci -knn: Subsystem: Sony Corporation Device [104d:909b] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210
Bug#721627: debian-installer: cannot install bootloader when multiple disks are present
Package: debian-installer Severity: important Hello, I am installing Debian Wheezy from a mini iso on an USB thumb drive (sda) to internal SATA harddisk (sdd). sdb and sdc are possibly non-existent floppies or something. When I get to installing grub the installer insists on installing to sda which - is bogus because I need the bootloader on sdd which has the system on it - fails because sda does not have a PC partition table Please make Debian installeble from USB thumb drive. Thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130902143412.18695.53401.report...@optiplex960.ruk.cuni.cz
Bug#633306: closed by Holger Levsen hol...@layer-acht.org (dealing with old installation-reports)
Hi Helge, I'm sorry the text you replied you disappointed you, as it just was a template text which I've used to close quite some bugs. The parts mostly applicable to 633306 were: On Montag, 2. September 2013, Helge Kreutzmann wrote: - they have been from a development phase where things were not stable and/or and - they are quite old (and thus likely fixed today) and/or so, dear submitter: is 633306 fixed with the wheezy images? with current sid ones? As said: it's easy to reopen and I'll happily do so, If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. Well, given the very broad statement without any clear indication to which sub issue you are referring it is hard to see which part should be reopened / which was closed incorrectly. As you will know, it's possible to clone bugs. You can even do this yourself. And then use bug titles... And I'm not going to zap the disk for a possible new bug report which might simply get closed again without comment in 2015 or so. Disappointed. If you care so much about 633306, why wasnt there a reply from you to this bug since 2 years? The complete silence on this bug since it was filed _plus_ the fact that it mixes 5 issues _plus_ that it was from early wheezy development, made me conclude its best to close it. If there are still issues present today, new bug reports are best. cheers, Holger trying to make useful bugs visible: http://qa.debian.org/data/bts/graphs/multi/installation-reports,debian-installer,.png signature.asc Description: This is a digitally signed message part.
Re: Next (old)stable point releases
Jonathan Wiltshire wrote: On Fri, Aug 23, 2013 at 01:50:04PM +0200, Joerg Jaspert wrote: Am 19.08.2013 15:55, schrieb Julien Cristau: we should start thinking about dates for the 7.2 and 6.0.8 point releases. Which week-ends in the coming months would work for ftpmaster, press and cd? (We'd need one date for stable and another later for oldstable.) We COULD do both at once, at least ftpmaster. Cant say for cd/press, though cds may be hard. We're much longer overdue for oldstable (February) than we are for stable (June); if we stagger them, should we consider oldstable first? All dates are fine for press at the moment. Regards, Joey -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130902163500.gd18...@valse.home.infodrom.org
Re: Next (old)stable point releases
On Mon, 2013-09-02 at 18:35 +0200, Joey Schulze wrote: Jonathan Wiltshire wrote: [I don't appear to have Jonathan's mail - and nor do the list archives - so piggy-backing on Joey's.] We're much longer overdue for oldstable (February) than we are for stable (June); if we stagger them, should we consider oldstable first? It would quite probably be easier to do stable first, despite the above. We have a few packages in both p-u and o-p-u currently which are newer upstream versions (mostly via security), such that p-u o-p-u stable oldstable. If the oldstable point release occurs first, we either have to not include those packages until 6.0.9 or temporarily have oldstable stable, which is at best confusing. (We've been in the latter situation previously, for 5.0.9 / 6.0.3, and after some debate on the day decided to include the packages in any case; I'm not sure we should take that as precedent, however.) Regards, Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1378161699.18562.14.ca...@jacala.jungle.funky-badger.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Sep 03 00:03 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * FAILED BUILD: amd64 Sep 03 00:03 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * FAILED BUILD: amd64 Sep 03 00:03 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * FAILED BUILD: amd64 Sep 03 00:05 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Sep 03 00:05 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: amd64 Sep 03 00:05 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * FAILED BUILD: amd64 Sep 03 00:06 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * FAILED BUILD: armel Sep 02 08:29 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * FAILED BUILD: armhf Sep 02 09:49 buildd@hasse build_mx5_netboot-gtk http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot-gtk.log * FAILED BUILD: i386 Sep 03 00:03 buildd@biber build_cdrom_isolinux http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log * FAILED BUILD: i386 Sep 03 00:03 buildd@biber build_cdrom_gtk http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log * FAILED BUILD: i386 Sep 03 00:03 buildd@biber build_cdrom-xen http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log * FAILED BUILD: i386 Sep 03 00:05 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Sep 03 00:05 buildd@biber build_netboot-xen http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log * FAILED BUILD: i386 Sep 03 00:06 buildd@biber build_hd-media http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log * FAILED BUILD: i386 Sep 03 00:06 buildd@biber build_hd-media_gtk http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log * OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: amd64 Sep 02 10:53 debian-cd@pettersson 5sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/5sidkfreebsd-amd64 * FAILED BUILD: amd64 Sep 02 10:53 debian-cd@pettersson Asidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/Asidkfreebsd-amd64 * FAILED BUILD: amd64 Sep 02 10:53 debian-cd@pettersson 4sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-amd64 * FAILED BUILD: amd64 Sep 02 10:54 debian-cd@pettersson 3sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/3sidkfreebsd-amd64 * FAILED BUILD: amd64 Sep 02 10:54 debian-cd@pettersson sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/sidkfreebsd-amd64 * FAILED BUILD: amd64 Sep 02 10:57 debian-cd@pettersson Asidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/Asidkfreebsd-i386 * FAILED BUILD: amd64 Sep 02 10:57 debian-cd@pettersson 5sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/5sidkfreebsd-i386 * FAILED BUILD: amd64 Sep 02 10:57 debian-cd@pettersson 4sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-i386 * FAILED BUILD: amd64 Sep 02 10:57 debian-cd@pettersson 3sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/3sidkfreebsd-i386 * FAILED BUILD: amd64 Sep 02 10:57 debian-cd@pettersson sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/sidkfreebsd-i386 * FAILED BUILD: amd64 Sep 02 21:51 debian-cd@pettersson 2sidi386 http://cdbuilder.debian.org/cdimage-log/2sidi386 * FAILED BUILD: amd64 Sep 02 21:51 debian-cd@pettersson Csidi386 http://cdbuilder.debian.org/cdimage-log/Csidi386 * FAILED BUILD: amd64 Sep 02 21:52 debian-cd@pettersson 2sidamd64 http://cdbuilder.debian.org/cdimage-log/2sidamd64 * FAILED BUILD: amd64 Sep 02 21:52 debian-cd@pettersson Csidamd64 http://cdbuilder.debian.org/cdimage-log/Csidamd64 * FAILED BUILD: amd64 Sep 02 21:54 debian-cd@pettersson 2sidmulti-arch-1
Re: Debian installer build: failed or old builds
Quoting Daily build aggregator (debian-boot@lists.debian.org): * FAILED BUILD: amd64 Sep 03 00:05 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log Needed speakup-modules-3.10-2-amd64-di not found (looked in apt.udeb/cache/archives/, debugudebs/) Something related to recent modules reorganization in kernel packages? Still, this package seems to be provided by the linux source package. signature.asc Description: Digital signature
