Your message dated Sun, 25 Aug 2013 12:42:38 +0200 with message-id <201308251243.25305.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #682753, regarding Package: installation-reports 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 owner@bugs.debian.org immediately.) -- 682753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682753 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Package: installation-reports
- From: Mark Salesman <s_mark85@ymail.com>
- Date: Wed, 25 Jul 2012 03:22:48 -0700 (PDT)
- Message-id: <1343211768.74214.YahooMailClassic@web121406.mail.ne1.yahoo.com>
Package: installation-reports Boot method: dd'ed CD .iso image onto a USB stick Image version: 6.0.5 amd64 Date: July 2012 Machine: PC Processor: Athlon 64 X2 5000+ Memory: 4 GB Partitions: 1: /boot ext2 2: swap 3: / ext3 5: LVM2 /usr and /home 6: LVM2 7: /xtra ext4 Output of lspci -knn (or lspci -nn): 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] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [O] Comments/Problems: Chose expert install. Installed to external USB drive, with the intent to later put this drive into the computer by hooking it up to SATA port. During installation: /dev/sda : USB stick (the installer media) /dev/sdb : 500 GB internal /dev/sdc : 500 GB in external caddy (target drive) GRUB step did not ask for which drive to install bootloader to, so it took sdb, had to manually fix later. But the real problem and reason for this report is that the ahci and ext4 modules are not included on the initrd (just usb-storage etc), resulting in an unbootable system and drop to busybox prompt when SATA-connected. Who does NOT need ahci these days!? Was able to boot after doing this: nano /etc/initramfs-tools/modules # added ahci and ext4 update-initramfs -u
--- End Message ---
--- Begin Message ---
- To: 696737-done@bugs.debian.org, 607698-done@bugs.debian.org, 606496-done@bugs.debian.org, 603960-done@bugs.debian.org, 701827-done@bugs.debian.org, 686786-done@bugs.debian.org, 685681-done@bugs.debian.org, 685515-done@bugs.debian.org, 685047-done@bugs.debian.org, 685308-done@bugs.debian.org, 684639-done@bugs.debian.org, 683706-done@bugs.debian.org, 683705-done@bugs.debian.org, 683381-done@bugs.debian.org, 682753-done@bugs.debian.org, 682507-done@bugs.debian.org, 682008-done@bugs.debian.org, 680555-done@bugs.debian.org, 681673-done@bugs.debian.org, 680026-done@bugs.debian.org, 679795-done@bugs.debian.org, 675127-done@bugs.debian.org, 674855-done@bugs.debian.org, 672317-done@bugs.debian.org, 673649-done@bugs.debian.org, 605076-done@bugs.debian.org, 690752-done@bugs.debian.org, control@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sun, 25 Aug 2013 12:42:38 +0200
- Message-id: <201308251243.25305.holger@layer-acht.org>
reassign 701201 src:linux retitle 701201 libata.atapi_passthru16=0 is needed by some hardware forcemerge 690985 686954 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. 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, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---