Your message dated Sun, 21 Jul 2013 14:32:43 +0200 with message-id <201307211433.01341.hol...@layer-acht.org> and subject line dealing with old debian-installer bugs has caused the Debian Bug report #657345, regarding [debian-installer] Debian Installer fails to boot 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.) -- 657345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debian-installer Severity: important --- Please enter the report below this line. --- Dear Debian Team!A fresh burned DVD with debian squeeze 6.0.3 amd64 fails to boot at my system.It displays only the first line "ISOLinux .... something something .. at al" Following boot scenarious fails: - Debian Squeeze 6.0.3 amd64 - dvd 1 : Burned to a DVD - Debian Squeeze 6.0.3 amd64 - dvd 1 : written to a USB stick - Debian Squeeze 6.0.3 amd64 - netinstall : CD and USB stick - Debian Live Squeeze 6.0.3 amd64 written to a DVD - GRML64 2011.12 - Debian Wheezy Netinstaller (today downloaded) Internal IDE DVD Writer was exchanged to a USB DVD Writer. Same results. The disks and sticks were verified on my Laptop. They did boot there. Following scenarios did boot: - Debian Lenny 5.0.1 amd64 - ISO 1 - FreeBSD 8.2 amd64 DVD 1 - Knoppix 6.7In my opinion it might be related to a change at syslinux bootcode change at the time where lenny got developed to squeeze. Other distributions like knoppix use ISOLinux which did boot on my system. FreeBSD of course dont use syslinux too. I'm not sure if that error is related to syslinux or the debian-installer, because grml which rely on syslinux too, dont boot on that hardware.Why did i not recognize that error before? My system was last installed when Lenny was testing. After that, only dist-upgrades.I know it might be hard to impossible for you to reproduce this error because you dont have my hardware, but i'm reporting that bug knowing that.My Hardwareconfiguration: Asus M3A32 MVP Deluxe / BIOS 2202 (up to date) AMD Phenom 1090T BenQ IDE DVD writer Best Regards Georg Gast <---- lspci --nn ---->00:00.0 Host bridge [0600]: ATI Technologies Inc RD790 Northbridge only dual slot PCI-e_GFX and HT3 K8 part [1002:5956] 00:02.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A) [1002:5978] 00:06.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port C) [1002:597c] 00:0a.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F) [1002:597f] 00:0b.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx1 port A) [1002:5980] 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380] 00:13.0 USB controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387] 00:13.1 USB controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388] 00:13.2 USB controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389] 00:13.3 USB controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a] 00:13.4 USB controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b] 00:13.5 USB controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386] 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 14)00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c]00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d] 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Juniper [Radeon HD 5700 Series] [1002:68b8] 01:00.1 Audio device [0403]: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series] [1002:aa58] 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller [11ab:4364] (rev 12) 03:00.0 Multimedia video controller [0400]: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder [14f1:8852] (rev 02) 04:00.0 RAID bus controller [0104]: 3ware Inc 9650SE SATA-II RAID PCIe [13c1:1004] (rev 01) 05:06.0 Multimedia audio controller [0401]: Creative Labs CA0106 Soundblaster [1102:0007]<---- lspci --vv ----> --- System information. --- Architecture: amd64 Kernel: Linux 3.1.0-1-amd64 Debian Release: wheezy/sid 500 testing ftp.de.debian.org 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---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, Holgersignature.asc
Description: This is a digitally signed message part.
--- End Message ---