[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#274659: marked as done (more red screen)

Your message dated Sun, 20 Mar 2011 17:56:56 +0100
with message-id <20110320165656.GY7161@const.famille.thibault.fr>
and subject line Re: Bug#273192: swapped colors with 2.6 kernel
has caused the Debian Bug report #273192,
regarding more red screen
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

273192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273192
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports


Debian-installer-version: pre-rc2 sarge-i386-businesscard.iso

uname -a: Linux alfred 2.6.6-1-k7 #1 Wed May 12 18:19:40 EST 2004 i686 GNU/Linux
Date: 2-OCT-2004 16:00
Method: boot from CD, entering 'linux26', packages from 
        ftp.de.debian.org with local HTTP proxy

Machine: made from components. Peculiarities: ethernet+firewire,
IDE + SCSI disks, onboard USB 1.1 + extra USB 2.0
Processor: Athlon 1800+
Memory: 512 MByte
Root Device: /dev/hdd

Disk /dev/hdd: 10.2 GB, 10260710400 bytes
255 heads, 63 sectors/track, 1247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdd1   *           1         510     4096543+   b  W95 FAT32
/dev/hdd2             511        1247     5919952+   5  Extended
/dev/hdd5             511         767     2064321    b  W95 FAT32
/dev/hdd6            1175        1247      586341   83  Linux
/dev/hdd7             768         798      248976   82  Linux swap
/dev/hdd8   *         799        1174     3020188+  83  Linux

Partition table entries are not in disk order

output of lspci:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
0000:00:09.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
0000:00:0b.0 SCSI storage controller: Advanced Micro Devices [AMD] 53c974 [PCscsi] (rev 10)
0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 04)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
0000:00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 30)
0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
0000:02:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
0000:02:09.0 USB Controller: NEC Corporation USB (rev 41)
0000:02:09.1 USB Controller: NEC Corporation USB (rev 41)
0000:02:09.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [0]

base install and bare minimum second stage install OK,
but it started with a red screen.


--- End Message ---
--- Begin Message ---
We haven't had more reports recently (and some people have reported
it as fixed). I believe this bug has somehow been fixed in the kernel


--- End Message ---

Reply to: