Bug#631997: linux-image-2.6.39-2-486: black screen after grub menu

06-29-2011, 01:40 AM

Package: linux-2.6
Version: 2.6.39-2
Severity: grave
Justification: renders package unusable

My computer never boots with 2.6.39-2-486 or 2.6.38. Currently I am running a
custom built 2.6.30 kernel. When I boot with 2.6.39 or 2.6.38 the screen goes
black after I select the kernel in grub. Nothing ever comes up. cntl-alt-f1
does nothing. This happens whether I have modeset=1 or 0. I have a radeon
graphics card.

I just recovered from being dead in the water after upgrading udev because my
kernel was too old. Now, it seems I can't upgrade my kernel. I have an up to
date wheezy box as of a couple of weeks ago. I have had to back down the udev
so that everything is not broke.

$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System
Controller (rev 25)
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge
(rev 01)
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev
1b)
00:04.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 0e)
00:04.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20)
00:0d.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
00:0e.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
00:0f.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10)
00:10.0 Multimedia audio controller: Rockwell International Device 4310
00:10.1 Communication controller: Rockwell International Riptide HSF 56k PCI
Modem
00:10.2 Input device controller: Rockwell International Device 4312
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon
7200]

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** Network interface configuration:

auto lo
iface lo inet loopback

allow-hotplug eth0
auto eth0

auto wlan0
iface wlan0 inet static
address 192.168.10.1
netmask 255.255.255.0
network 192.168.10.1
broadcast 192.168.10.255

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller [1022:7006] (rev 25)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 32
Region 0: Memory at ec000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at e8012000 (32-bit, prefetchable) [size=4K]
Region 2: I/O ports at 1010 [disabled] [size=4]
Capabilities: <access denied>
Kernel driver in use: agpgart-amdk7

00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge [1022:7007] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=36
I/O behind bridge: 00009000-00009fff
Memory behind bridge: e8100000-e81fffff
Prefetchable memory behind bridge: f0000000-f7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 1b)
Subsystem: ASUSTeK Computer Inc. Device [1043:8006]
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Kernel driver in use: parport_pc

00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
Region 4: I/O ports at 1000 [size=16]
Capabilities: <access denied>
Kernel driver in use: VIA_IDE

00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 0e) (prog-if 00 [UHCI])
Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 10
Region 4: I/O ports at 1020 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd

00:04.4 SMBus [0c05]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] (rev 20)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin ? routed to IRQ 9

00:0d.0 Network controller [0280]: Ralink corp. RT2561/RT61 802.11g PCI [1814:0301]
Subsystem: Ralink corp. EW-7108PCg [1814:2561]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: rt61pci

00:0e.0 Network controller [0280]: Ralink corp. RT2561/RT61 802.11g PCI [1814:0301]
Subsystem: Ralink corp. EW-7108PCg [1814:2561]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e8008000 (32-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: rt61pci

00:0f.0 Ethernet controller [0200]: Accton Technology Corporation SMC2-1211TX [1113:1211] (rev 10)
Subsystem: Hewlett-Packard Company Device [103c:9207]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 1400 [size=256]
Region 1: Memory at e8010000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: 8139too

00:10.0 Multimedia audio controller [0401]: Rockwell International Device [127a:4310]
Subsystem: Risq Modular Systems, Inc. Device [1235:4310]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at 1040 [size=64]
Capabilities: <access denied>
Kernel driver in use: RIPTIDE

00:10.1 Communication controller [0780]: Rockwell International Riptide HSF 56k PCI Modem [127a:4311]
Subsystem: Risq Modular Systems, Inc. Device [1235:4311]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e8020000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: hsfpcibasic2

00:10.2 Input device controller [0980]: Rockwell International Device [127a:4312]
Subsystem: Risq Modular Systems, Inc. Device [1235:4312]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Region 0: Memory at e8011000 (32-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: <access denied>

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon R100 QD [Radeon 7200] [1002:5144] (prog-if 00 [VGA controller])
Subsystem: ATI Technologies Inc Radeon 7000/Radeon [1002:001a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at e8100000 (32-bit, non-prefetchable) [size=512K]
[virtual] Expansion ROM at e8180000 [disabled] [size=128K]
Capabilities: <access denied>

** USB devices:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 001 Device 003: ID 04f9:0180 Brother Industries, Ltd MFC-7420
Bus 001 Device 004: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser

-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30.090924 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.39-2-486 depends on:
ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy
ii initramfs-tools [linux-initra 0.99 tools for generating an initramfs
ii linux-base 3.2 Linux image base package
ii module-init-tools 3.16-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.39-2-486 recommends:
ii firmware-linux-free 3 Binary firmware for various driver

Versions of packages linux-image-2.6.39-2-486 suggests:
pn grub-pc | extlinux | lilo <none> (no description available)
pn linux-doc-2.6.39 <none> (no description available)

Versions of packages linux-image-2.6.39-2-486 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.30 Binary firmware for various driver
ii firmware-linux-nonfree 0.30 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
ii firmware-ralink 0.30 Binary firmware for Ralink wireles
pn xen-hypervisor <none> (no description available)

-- debconf information:
linux-image-2.6.39-2-486/postinst/ignoring-ramdisk:
linux-image-2.6.39-2-486/prerm/removing-running-kernel-2.6.39-2-486: true
linux-image-2.6.39-2-486/postinst/depmod-error-initrd-2.6.39-2-486: false
* linux-image-2.6.39-2-486/postinst/missing-firmware-2.6.39-2-486:

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110629014015.4897.24433.reportbug@localhost.loca ldomain">http://lists.debian.org/20110629014015.4897.24433.reportbug@localhost.loca ldomain

06-29-2011, 02:35 AM

On Tue, 2011-06-28 at 21:40 -0400, Brent S. Elmer wrote:
> Package: linux-2.6
> Version: 2.6.39-2
> Severity: grave
> Justification: renders package unusable
>
> My computer never boots with 2.6.39-2-486 or 2.6.38. Currently I am running a
> custom built 2.6.30 kernel.

Please could yo test some of the earlier versions from
<http://snapshot.debian.org/package/linux-2.6/> to find which was the
last working version?

> When I boot with 2.6.39 or 2.6.38 the screen goes
> black after I select the kernel in grub. Nothing ever comes up. cntl-alt-f1
> does nothing. This happens whether I have modeset=1 or 0. I have a radeon
> graphics card.
[...]

What if you select the 'recovery mode' menu item? Do you see any
messages from the kernel?

Ben.

--
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.

06-29-2011, 03:12 AM

On Wed, 2011-06-29 at 03:35 +0100, Ben Hutchings wrote:

Please could yo test some of the earlier versions from
<http://snapshot.debian.org/package/linux-2.6/> to find which was the
last working version?

> When I boot with 2.6.39 or 2.6.38 the screen goes
> black after I select the kernel in grub. Nothing ever comes up. cntl-alt-f1
> does nothing. This happens whether I have modeset=1 or 0. I have a radeon
> graphics card.
[...]

What if you select the 'recovery mode' menu item? Do you see any
messages from the kernel?

Ben.

I will try the earlier versions when I get a chance.* It may not be very soon since that computer is at my church and I will be on vacation for a week.* By the way, since I will be using snapshot, is there a config file for APT that I can put something to handle the snapshots being expired?* See bug 595801.* It is a pain when going to snapshot in synaptic and getting the release file expired message.* I drop out to the command line and do apt-get -o 'Acquire::Check-Valid-Until=false' update from the command line to get around it.

recovery mode does not work either.* Still an endless black screen after grub with no messages from the kernel.

Brent

06-29-2011, 03:22 AM

On Tue, 2011-06-28 at 23:12 -0400, Wendy Elmer wrote:
[...]
> I will try the earlier versions when I get a chance. It may not be
> very soon since that computer is at my church and I will be on
> vacation for a week. By the way, since I will be using snapshot, is
> there a config file for APT that I can put something to handle the
> snapshots being expired? See bug 595801. It is a pain when going to
> snapshot in synaptic and getting the release file expired message. I
> drop out to the command line and do apt-get -o
> 'Acquire::Check-Valid-Until=false' update from the command line to get
> around it.

Sorry, I have no better idea.

> recovery mode does not work either. Still an endless black screen
> after grub with no messages from the kernel.

What processor and how much RAM does this systeam have?

Ben.

--
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.

06-29-2011, 12:18 PM

On Wed, 2011-06-29 at 04:22 +0100, Ben Hutchings wrote:
> On Tue, 2011-06-28 at 23:12 -0400, Wendy Elmer wrote:
> [...]
> > I will try the earlier versions when I get a chance. It may not be
> > very soon since that computer is at my church and I will be on
> > vacation for a week. By the way, since I will be using snapshot, is
> > there a config file for APT that I can put something to handle the
> > snapshots being expired? See bug 595801. It is a pain when going to
> > snapshot in synaptic and getting the release file expired message. I
> > drop out to the command line and do apt-get -o
> > 'Acquire::Check-Valid-Until=false' update from the command line to get
> > around it.
>
> Sorry, I have no better idea.
>
> > recovery mode does not work either. Still an endless black screen
> > after grub with no messages from the kernel.
>
> What processor and how much RAM does this systeam have?
>
> Ben.
>

It is an AMD Athlon 850 MHZ. It is maxed out at a whopping 256 MB ram.
It is an old HP computer which has very oddball hardware that I am
trying to keep crippling along because the church doesn't have the money
to buy a better one. The reason I am running the old custom kernel is
because it has an oddball conexant riptide sound card that I have to
special handle in the kernel build(3rd party driver and firmware) in
order to make it work and it is a pain.

Brent

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309349901.4874.7.camel@belmer">http://lists.debian.org/1309349901.4874.7.camel@belmer

06-29-2011, 12:18 PM

On Wed, 2011-06-29 at 04:22 +0100, Ben Hutchings wrote:
> On Tue, 2011-06-28 at 23:12 -0400, Wendy Elmer wrote:
> [...]
> > I will try the earlier versions when I get a chance. It may not be
> > very soon since that computer is at my church and I will be on
> > vacation for a week. By the way, since I will be using snapshot, is
> > there a config file for APT that I can put something to handle the
> > snapshots being expired? See bug 595801. It is a pain when going to
> > snapshot in synaptic and getting the release file expired message. I
> > drop out to the command line and do apt-get -o
> > 'Acquire::Check-Valid-Until=false' update from the command line to get
> > around it.
>
> Sorry, I have no better idea.
>
> > recovery mode does not work either. Still an endless black screen
> > after grub with no messages from the kernel.
>
> What processor and how much RAM does this systeam have?
>
> Ben.
>

It is an AMD Athlon 850 MHZ. It is maxed out at a whopping 256 MB ram.
It is an old HP computer which has very oddball hardware that I am
trying to keep crippling along because the church doesn't have the money
to buy a better one. The reason I am running the old custom kernel is
because it has an oddball conexant riptide sound card that I have to
special handle in the kernel build(3rd party driver and firmware) in
order to make it work and it is a pain.

Brent

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309349901.4874.7.camel@belmer">http://lists.debian.org/1309349901.4874.7.camel@belmer

07-14-2011, 11:00 PM

The last working kernel is 2.6.32-35.

-----Original Message-----

From: Ben Hutchings <ben@decadent.org.uk>

To: Brent S. Elmer <webe3vt@aim.com>; 631997 <631997@bugs.debian.org>

Sent: Tue, Jun 28, 2011 10:35 pm

Subject: Re: Bug#631997: linux-image-2.6.39-2-486: black screen after grub menu

On Tue, 2011-06-28 at 21:40 -0400, Brent S. Elmer wrote:

> Package: linux-2.6

> Version: 2.6.39-2

> Severity: grave

> Justification: renders package unusable

>

> My computer never boots with 2.6.39-2-486 or 2.6.38. Currently I am running a

> custom built 2.6.30 kernel.

Please could yo test some of the earlier versions from

<http://snapshot.debian.org/package/linux-2.6/> to find which was the

last working version?

> When I boot with 2.6.39 or 2.6.38 the screen goes

> black after I select the kernel in grub. Nothing ever comes up. cntl-alt-f1

> does nothing. This happens whether I have modeset=1 or 0. I have a radeon

> graphics card.

[...]

What if you select the 'recovery mode' menu item? Do you see any

messages from the kernel?

Ben.

--

Ben Hutchings

In a hierarchy, every employee tends to rise to his level of incompetence.