Your message dated Sun, 21 Jul 2013 14:32:43 +0200 with message-id <201307211433.01341.holger@layer-acht.org> and subject line dealing with old debian-installer bugs has caused the Debian Bug report #625290, regarding debian-installer: ide_generic doesn't get included in the initrd, harddisk not available 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.) -- 625290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625290 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-installer: ide_generic doesn't get included in the initrd, harddisk not available
- From: Holger Wansing <linux@wansing-online.de>
- Date: Tue, 3 May 2011 10:23:08 +0200
- Message-id: <20110503102308.fb1b4199.linux@wansing-online.de>
Package: debian-installer Severity: normal [This is a follow-up bugreport for #571035, which will been closed due to his longstanding and complex history] Used installation media: netinst cd: 'installer build 20110407-03:53' with kernel 2.6.37-2-486 Hi folks, I have an older Toshiba laptop 320CDS using an uncommon non-pci ide-controller, which is supported by ide_generic / ide-gd-mod kernel module, but not by any of the libata modules. Installation works fine, but the newly installed system does not start, root filesystem cannot be found, since the harddisk is not available. Manually fixing the initrd to include ide_generic solves this problem. ide_generic is an old driver and there were statements, that it should be removed in the future. But since the libata modules lack support for some controller(s) ide_generic had, there's probably a reason to keep ide_generic. I bought additional RAM for this machine to be able to provide installation logs (this was a lowmem machine before) and here are the logs. Maybe someone can find the reason, why ide_generic doesn't make it in the initrd. Don't hesitate to ask for any additional info. Thanks Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =Attachment: installation-logs.tar.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: control@bugs.debian.org, 704499-done@bugs.debian.org, 593258-done@bugs.debian.org, 606976-done@bugs.debian.org, 625290-done@bugs.debian.org, 605815-done@bugs.debian.org, 692001-done@bugs.debian.org, 657345-done@bugs.debian.org, 656327-done@bugs.debian.org
- Subject: dealing with old debian-installer bugs
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sun, 21 Jul 2013 14:32:43 +0200
- Message-id: <201307211433.01341.holger@layer-acht.org>
reassign 716710 preseed,release-notes forcemerge 704881 552563 tags 633128 + confirmed reassign 633128 src:linux,kernel-wedge affects 633128 debian-installer reassign 653391 archdetect forcemerge 653390 653391 reassign 655579 rootskel-gtk reassign 690246 partman-lvm affects 690246 debian-installer severity 699430 wishlist reassign 655124 kernel-wedge affects 655124 debian-installer thanks Hi, thank you for submitting bug reports concering debian-installer, 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 have been from a development phase where things were not stable and/or - they are very old and/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 - and that's 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 ---