Blank screen on tribe4 boot

Bug #133710 reported by plord
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Whilst booting x86_64 version of kubuntu gutsy tribe4 on a dell inspiron 9400 I just get a blank screen. The machine is on the network ( ping works ) and I see some ntp traffic, but I can't access the machine from either the keyboard or ssh, so I have no logs.

This also happens when booting with the safe vga option.

This means I can't install kubuntu :-(

Revision history for this message
plord (peter-plord) wrote :

Note that Feisty Fawn x86_64 cd boots fine, as does tribe 3 gusty gibbon. Its just tribe 4 which seems to get the graphics wrong.

Revision history for this message
plord (peter-plord) wrote :

tribe5 x86_64 also gives a blank screen on boot

Revision history for this message
plord (peter-plord) wrote :

Debugging further :-

1) remove the splash and quiet options from the boot line, added single to boot up in single user mode
2) run X -probeonly

This is what I see :-

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu
Current Operating System: Linux ubuntu 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64
Build Date: 26 July 2007
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 25 18:32:10 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in

Backtrace:
0: X(xf86SigHandler+0x6d) [0x4858ad]
1: /lib/libc.so.6 [0x2b6a9870e760]
2: /lib/libc.so.6 [0x2b6a9874ee49]
3: /lib/libc.so.6(__libc_malloc+0x93) [0x2b6a98750d73]
4: X(XNFalloc+0x18) [0x571258]
5: X(xf86CVTMode+0x41a) [0x4833aa]
6: /usr/lib/xorg/modules/drivers//vesa_drv.so [0x2b6a9a2460ba]
7: X(xf86ValidateModes+0x818) [0x495be8]
8: /usr/lib/xorg/modules/drivers//vesa_drv.so [0x2b6a9a2475c1]
9: X(InitOutput+0x9bd) [0x46867d]
10: X(main+0x275) [0x439cc5]
11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b6a986fab44]
12: X(FontFileCompleteXLFD+0x231) [0x4391a9]

Fatal server error:
Caught signal 11. Server aborting

Note that this notebook comes with ATI radeon X1400

Revision history for this message
plord (peter-plord) wrote :

Oh, I found the full log - see attached

Revision history for this message
plord (peter-plord) wrote :

Ah, some progress.

If I use X to generate a configuration file ( attached ) then X fires up.

So a work-around to boot tribe4/tribe5 is :-

1) boot up in single user mode
2) X -config
3) cp /root/xorg.conf.new /etc/X11/xorg.conf
4) init 3

Revision history for this message
wolfger (wolfger) wrote :

Is this still a bug after the Gutsy release, or can we close it?

Revision history for this message
wolfger (wolfger) wrote :

No response in 29 days. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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.