Bug#661157: [installation-reports] trouble with X and an Radeon HD 3600 Series
Package: installation-reports Boot method: netinst Date: 23/02/1991 Machine: Dell Studio 17 Processor: Intel(R) Core(TM)2 Duo CPU T9400 Memory: 4Go Partitions: proc /proc proc defaults 0 0 UUID=33f9366e-859f-4c56-ad18-d2f18359ddaa / xfs defaults 0 1 UUID=2ae0ae9c-cea4-4cae-a918-efc21f095d26 /home ext4 defaults 0 2 UUID=04163A31163A23D8 /media/win1 ntfs defaults 0 0 UUID=386C29316C28EB78 /media/win2 ntfs defaults 0 0 nas-01-DD-7D.home:/media /media/san nfs user 0 0 UUID=e1c8b528-f176-44f0-ae1a-443952c518f9 none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Output of lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Dell Device [1028:02a0] 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 03) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) 00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M LPC Interface Controller [8086:2919] (rev 03) Subsystem: Dell Device [1028:02a0] 00:1f.2 SATA controller [0106]: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] [8086:2929] (rev 03) Subsystem: Dell Device [1028:02a0] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03) Subsystem: Dell Device [1028:02a0] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV635 [Mobility Radeon HD 3650] [1002:9591] Subsystem: Dell Device [1028:02a0] 01:00.1 Audio device [0403]: ATI Technologies Inc RV635 HDMI Audio [Radeon HD 3600 Series] [1002:aa20] Subsystem: Dell Device [1028:02a0] Kernel driver in use: snd_hda_intel 04:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4235] Subsystem: Intel Corporation Device [8086:1121] Kernel driver in use: iwlwifi 08:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe [14e4:1698] (rev 10) Subsystem: Broadcom Corporation Device [14e4:9698] Kernel driver in use: tg3 09:01.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) Subsystem: Dell Device [1028:02a0] Kernel driver in use: firewire_ohci 09:01.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22) Subsystem: Dell Device [1028:02a0] Kernel driver in use: sdhci-pci 09:01.2 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12) Subsystem: Dell Device [1028:02a0] Kernel driver in use: r592 09:01.3 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 12) Subsystem: Dell Device [1028:02a0] Kernel driver in use: r852 Base System Installation
Re: Planning for final lenny point release (5.0.10)
[Cc list trimmed] On Thu, 2012-02-23 at 15:03 -0700, dann frazier wrote: On Tue, Feb 14, 2012 at 04:55:32PM -0700, dann frazier wrote: On Tue, Feb 14, 2012 at 09:36:38PM +, Adam D. Barratt wrote: -kernel, -boot - were there any plans for a final kernel and/or d-i upload for lenny? If so we need to get those sorted asap. There are some security fixes for the kernel queued - nothing major. I had planned to see if the CVE-2011-4127 fix from the recent 2.6.27.y update applied cleanly/sanely. But, I'd also be ok w/ shipping what we have now. Evidently this reply got dropped somewhere by listz, at any rate... I prepared the above, tested it on amd64, and I'm currently preparing a build for hppa. I don't know of anything else that needs to change in d-i. My recommendation would be to either: fwiw, the packages in o-p-u right now which contain udebs are freetype, libpng and openssl. Those all appear to be used in the gtk initrd at least (openssl only on some architectures) although I'm not sure if that makes a difference to whether we want to do a respin. A) upload this build to security. If we have all builds by Monday (02.27), go ahead and release a DSA and proceed with a d-i spin. If not, reject go w/ what we have. Assuming the technical side still works, I do worry a little that a new DSA three weeks after the announced EOL for security support might confuse people. I suppose we could do a last-minute kernel update via o-p-u, although I don't know if we have any idea how many people actually upgrade to EOL point releases in the relatively short period before the move to archive.d.o. Phil: any thoughts / preferences? Regards, Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1330116286.27081.23.ca...@jacala.jungle.funky-badger.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Feb 25 00:04 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * FAILED BUILD: amd64 Feb 25 00:05 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * FAILED BUILD: amd64 Feb 25 00:06 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * FAILED BUILD: amd64 Feb 25 00:06 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * FAILED BUILD: amd64 Feb 25 00:07 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Feb 25 00:07 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: amd64 Feb 25 00:08 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * FAILED BUILD: amd64 Feb 25 00:09 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * FAILED BUILD: i386 Feb 25 00:03 buildd@biber build_cdrom_isolinux http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log * FAILED BUILD: i386 Feb 25 00:04 buildd@biber build_cdrom_gtk http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log * FAILED BUILD: i386 Feb 25 00:04 buildd@biber build_cdrom-xen http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log * FAILED BUILD: i386 Feb 25 00:05 buildd@biber build_netboot http://d-i.debian.org/daily-images/i386/daily/build_netboot.log * FAILED BUILD: i386 Feb 25 00:06 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Feb 25 00:06 buildd@biber build_netboot-xen http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log * FAILED BUILD: i386 Feb 25 00:07 buildd@biber build_hd-media http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log * FAILED BUILD: i386 Feb 25 00:08 buildd@biber build_hd-media_gtk http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log * FAILED BUILD: ia64 Feb 25 00:14 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * FAILED BUILD: ia64 Feb 25 00:15 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: mips Feb 25 00:09 buildd@lucatelli build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * FAILED BUILD: mips Feb 25 00:10 buildd@lucatelli build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * FAILED BUILD: mips Feb 25 00:11 buildd@lucatelli build_r4k-ip22_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_netboot-2.6.log * FAILED BUILD: mips Feb 25 00:12 buildd@lucatelli build_r5k-ip32_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r5k-ip32_netboot-2.6.log * FAILED BUILD: mips Feb 25 00:14 buildd@lucatelli build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_sb1-bcm91250a_netboot-2.6.log * FAILED BUILD: mips Feb 25 00:16 buildd@lucatelli build_miniiso http://d-i.debian.org/daily-images/mips/daily/build_miniiso.log * FAILED BUILD: s390 Feb 25 00:02 buildd@zandonai build_generic http://d-i.debian.org/daily-images/s390/daily/build_generic.log * FAILED BUILD: sparc Feb 25 00:07 buildd@sompek build_cdrom http://d-i.debian.org/daily-images/sparc/daily/build_cdrom.log * FAILED BUILD: sparc Feb 25 00:08 buildd@sompek build_netboot http://d-i.debian.org/daily-images/sparc/daily/build_netboot.log * FAILED BUILD: sparc Feb 25 00:09 buildd@sompek build_miniiso http://d-i.debian.org/daily-images/sparc/daily/build_miniiso.log Totals: 65 builds (28 failed, 0 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1s15zx-0005p3...@ravel.debian.org
