Your message dated Sat, 20 Jul 2013 00:54:38 +0200 with message-id <201307200054.58292.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #549373, regarding Netinstall from USB-stick fails due to kernel mismatch. 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.) -- 549373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549373 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Netinstall from USB-stick fails due to kernel mismatch.
- From: Dinyar Rabady <dinyar@rabady.at>
- Date: Fri, 2 Oct 2009 22:02:16 +0200
- Message-id: <72d553010910021302g34e45893k74b49959ac34172f@mail.gmail.com>
Package: installation-reports Boot method: Netinstall via USB-Stick Image version: http://d-i.debian.org/daily-images/amd64/20091001-00:00/netboot/debian-installer/amd64/ Date: Friday, October 2nd '09 Machine: Thinkpad x61s Processor: Intel Core 2 Duo Memory: 2 GB Partitions: <df -Tl will do; the raw partition table is preferred> 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: [ ] Load installer modules: [E] Detect hard drives: [E] Partition hard drives: [E] Install base system: [ ] Clock/timezone setup: [ ] User/password setup: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: After I chose the mirror (I tried several and also tried to chose stable and sid instead of testing via priority=medium) I am shown a message reading: No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you're installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. Continue the install without loading kernel modules? In the console at Alt-F4 I found the line: "anna[2297] WARNING **: no packages for kernel in archive" I haven't changed any settings, merely followed the instructions at http://www.debian.org/releases/stable/amd64/ch04s03.html.en#usb-copy-flexible and used the daily images. -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Sent from Vienna, Austria
--- End Message ---
--- Begin Message ---
- To: 550064-done@bugs.debian.org, 549373-done@bugs.debian.org, 548864-done@bugs.debian.org, 548864-done@bugs.debian.org, 546402-done@bugs.debian.org, 545923-done@bugs.debian.org, 545433-done@bugs.debian.org, 542025-done@bugs.debian.org, 538770-done@bugs.debian.org, 528847-done@bugs.debian.org, 541987-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 20 Jul 2013 00:54:38 +0200
- Message-id: <201307200054.58292.holger@layer-acht.org>
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 have been from a development phase where things were not stable and/or - they are very old, more than 3 years. 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 ---