Your message dated Wed, 17 Jul 2013 01:36:44 +0200 with message-id <201307170137.05268.holger@layer-acht.org> and subject line dealing with old boot related bugs has caused the Debian Bug report #583735, regarding system boot fails after 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 owner@bugs.debian.org immediately.) -- 583735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583735 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: system boot fails after installation
- From: Németh Márton <nm127@freemail.hu>
- Date: Sun, 30 May 2010 10:45:56 +0200
- Message-id: <4C0225C4.2020503@freemail.hu>
Package: installation-reports Boot method: CDRW media in a CD-ROM drive Image version: http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/debian-testing-i386-netinst.iso Date: 2010-05-29 18:00 Machine: Desktop PC with Gigabyte GA-586TX3 motherboard ( http://www.gigabyte.com/products/product-page.aspx?pid=1574 ) Processor: # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 0 model name : 05/00 stepping : 1 cpu MHz : 100.221 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr cx8 pge bogomips : 200.44 clflush size : 32 power management: Memory: 64MB # cat /proc/meminfo MemTotal: 60948 kB MemFree: 10920 kB Buffers: 652 kB Cached: 40372 kB SwapCached: 0 kB Active: 25332 kB Inactive: 18284 kB Active(anon): 2688 kB Inactive(anon): 0 kB Active(file): 22644 kB Inactive(file): 18284 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 60948 kB LowFree: 10920 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 4 kB Writeback: 0 kB AnonPages: 2616 kB Mapped: 2048 kB Slab: 4240 kB SReclaimable: 2412 kB SUnreclaim: 1828 kB PageTables: 292 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 30472 kB Committed_AS: 5564 kB VmallocTotal: 966648 kB VmallocUsed: 1292 kB VmallocChunk: 964416 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 4096 kB DirectMap4k: 4096 kB DirectMap4M: 61440 kB Partitions: This state is shown after I booted the system from CD in rescue mode: # fdisk -l Disk /dev/hdb: 1281 MB, 1281982464 bytes 255 heads, 63 sectors/track, 155 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000c6a25 Device Boot Start End Blocks Id System /dev/hdb1 * 1 140 1124518+ 83 Linux /dev/hdb2 141 155 120487+ 5 Extended /dev/hdb5 141 155 120456 82 Linux swap / Solaris # cat /proc/partitions cat /proc/partitions major minor #blocks name 3 64 1251936 hdb 3 65 1124518 hdb1 3 66 1 hdb2 3 69 120456 hdb5 Output of lspci -knn (or lspci -nn): # lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation 430TX - 82439TX MTXC [8086:7100] (rev 01) 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01) 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) Kernel driver in use: PIIX_IDE 00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01) Kernel driver in use: uhci_hcd 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 01) 00:09.0 VGA compatible controller [0300]: S3 Inc. 86c764/765 [Trio32/64/64V+] [5333:8811] (rev 54) 00:0a.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] Kernel driver in use: 8139too 00:0b.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 50) Subsystem: First International Computer, Inc. Device [0925:1234] Kernel driver in use: uhci_hcd 00:0b.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 50) Subsystem: First International Computer, Inc. Device [0925:1234] Kernel driver in use: uhci_hcd 00:0b.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 51) Subsystem: First International Computer, Inc. Device [0925:1234] Kernel driver in use: ehci_hcd Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Clock/timezone setup: [ ] User/password setup: [O] Install tasks: [O] Install boot loader: [E] Overall install: [ ] Comments/Problems: I used the netinst CD image with the following version identifier: This is a Debian 6.0 (squeeze) installation CD-ROM. It was built 20100217-22:18; d-i 20100211. I haven't connected the network for the first time just let the installation process go from CD. The grub-pc was installed. After rebooting the system prints the a short grub message line and resets immediately. This repeats until I boot again from CD. The drive setup is as follows: Primary master: none Primary slave: hard disk Secondary master: CD-ROM drive Secondary slave: none
--- End Message ---
--- Begin Message ---
- To: 695961-done@bugs.debian.org, 657431-done@bugs.debian.org, 657430-done@bugs.debian.org, 618929-done@bugs.debian.org, 612135-done@bugs.debian.org, 583735-done@bugs.debian.org, 572446-done@bugs.debian.org
- Subject: dealing with old boot related bugs
- From: Holger Levsen <holger@layer-acht.org>
- Date: Wed, 17 Jul 2013 01:36:44 +0200
- Message-id: <201307170137.05268.holger@layer-acht.org>
Hi, thank you for submitting installation reports, much appreciated. I read through all the ("boot" related) bugs mentioned here and am closing them now as - 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 were (very) old. If I've closed a bug incorrectly please do reply or just file a new one - thats often better, as the bug log will be more clear. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---