Framebuffer broken on IBM TP R50P

Bug #19106 reported by Ian Jackson
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Ben Collins

Bug Description

I'm using the hoary i386 installer CD on my IBM Thinkpad R50p.

I hit return to the first prompt, and get the usual bunches of scrolling kernel
messages. After a short while, the screen goes black and the system just sits
there.

Booting with the framebuffer disabled (debian-installer/no-framebuffer or
whatever the rune is) makes it work fine.

Revision history for this message
Ian Jackson (ijackson) wrote :

Kamion asked for my graphics card's PCI ID, so:

0000:01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL
Mobility T2] (rev 80) (prog-if 00 [VGA])
        Subsystem: IBM: Unknown device 054f
        Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 3000 [size=256]
        Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2

Revision history for this message
Colin Watson (cjwatson) wrote :

We'll need the corresponding line from 'lspci -n' output as well, in order to
get the PCI vendor and device IDs as well as the bus ID.

Revision history for this message
Ian Jackson (ijackson) wrote :

lspci -n says
...
0000:01:00.0 0300: 1002:4e54 (rev 80)
...

or, alternatively, from lspci -v -n:
0000:01:00.0 0300: 1002:4e54 (rev 80)
        Subsystem: 1014:054f
        Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 3000 [size=256]
        Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: <available only to root>

Revision history for this message
Ben Collins (ben-collins) wrote :

(In reply to comment #3)
> lspci -n says
> ...
> 0000:01:00.0 0300: 1002:4e54 (rev 80)

This is supported by the radeonfb driver. Seems like it isn't supported by the
vga16fb though. Can you boot with vga=771 and see if that works?

Revision history for this message
Ben Collins (ben-collins) wrote :

Also, test boot the Flight 2 cd's when they come out. It will contain the
vga16fb changes from Adam.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug and following up on it.

I am marking this bug Closed since there has been no response from you for over three months. We
would like to fix all existing issues, but need need feedback to help with debugging.

Should you still have a problem with the latest up to date Dapper kernel and packages, please reopen this bug. In this case, please answer the questions that have already been asked of you before and provide the log files and information required for debugging.

Changed in linux-source-2.6.15:
status: Needs Info → Rejected
Revision history for this message
Ian Jackson (ijackson) wrote :

I can reproduce this bug with:
 dapper d-i i386 final
 edgy d-i i386 final

With edgy I see two lines of text-mode console output: an error message about wait_for_sysfs serio somethingorother, and a message about starting klogd and syslogd, which then disappear very quickly.

If I boot the edgy d-i i386 cd and add vga=771 to the command line (under F6) then I don't see the two lines of output I mention above, but the rest of the installer works.

I haven't tried a herd cd.

Changed in linux-source-2.6.15:
status: Rejected → Unconfirmed
Revision history for this message
Carlos Diener / emonkey (emonkey) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks, Markus

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.