Black screen after kernel has loaded 100%

[dachs]

Black screen after kernel has loaded 100%. Shortly before CD-ROM stops working you can see an X (or cross) an then the little rotating disk representing the usual sandglass. After that the screen stays black. Booting with different resolutions makes no difference. Pressing keys or moving the mouse won't wake up the screen.

On this machine is installed Ubuntu 7.04 for AMD64. The according live DVD will boot too.

Hardware: Mainboard Asus M2A-VM HDMI with onboard graphics (ATI 690G), Athlon64 X2 5000+, 2x 1024 MB MDT DDR2 800 MHz.

[dachs (a20)]

PS: This fault applies to Ubuntu 7.10 Beta and Xubuntu 7.10 Beta too (AMD64 versions).

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is it possible to boot into safe mode off the Live CD? Is it possible to log in to a virtual terminal by pressing "Ctrl+Alt+F1"? Thanks in advance.

[dachs (a20)]

Glad I can contribute in some way.

It is possible to boot into safe graphics mode off the live CD. After that boot process "Ctrl+Alt+F1" starts a terminal (full screen). Only I don't know how to terminate it other than with 'reboot', which is certainly not a bug of the beta.

If I should do anything else, just give me foolproof instructions.

[dachs (a20)]

Sorry! What I told you above is wrong. I had the 7.04 disk in my drive.

It is NOT possible to boot into safe graphics mode off the Xubuntu 7.10 beta live CD. I too tried "Ctrl+Alt+F1" when the drive had stopped working, but nothing happened. I don't have the Ubuntu CD available right now to test things with it, but I wanted to correct my mistake as soon as possible.

[dachs (a20)]

http://cdimage.ubuntu.com/dvd/20071002/gutsy-dvd-amd64.iso as a disc doesn't work either.

[Brian Murray (brian-murray)]

The alternate CD provides a text based installer. I wonder if that would work any better.

[dachs (a20)]

I used the "Install in text mode" from the menue of the Live DVD, which I assume ist the same thing. This way I could install Ubuntu. Now every time when booting and the Ubuntu logo should display, my CRT tells me "ATTENTION, SIGNAL FREQUENCY OUT OF RANGE, PLEASE CHANGE SIGNAL TIMING". The boot process ends up whith a black screen. I think I should mention here, that I excluded in the setup 640x420 and 800x600 resolutions from beeing used.

"Ctrl+Alt+F1" starts a terminal. Is there a way to change that signal frequency from within the terminal or via using the 7.04 live DVD? (I killed my previous installation of Feisty with the new one).

[dachs (a20)]

After searching the net from an other PC I did the following in the meantime:
- sudo apt-get install xorg-driver-fglrx
- edited xorg.conf (left only the resolutions, that my monitor supports).

Now during boot up the screen is still black when the Uguntu logo should display, but at last the graphical interface starts allright.

[Brian Murray (brian-murray)]

Could you provide us with the PCI ID of your video card? You can do this by executing 'sudo lspci -vvnn' and adding the output as an attachment to your bug report. Thanks in advance.

[dachs (a20)]

Can't determine which one of the numbers is the PCI ID. The whole part concerning the video controller reads:

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon X1200 Series [1002:791e] (prog-if 00 [VGA])
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:826d]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at f0000000 (64-bit, prefetchable) [size=128M]
        Region 2: Memory at fdcf0000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at de00 [size=256]
        Region 5: Memory at fdb00000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000

In my posting above there is again an error. The screen isn't black while the Ubuntu logo shoud display, but I get the message "signal frequency is out of range ...".

After I changed the settings in usplash.conf from xres=1920, yres=1440 to xres=1152, yres=870 I can see now the logo and progress bar during shutdown, but still not during bootup. (My monitor can't display 1920x1440).

[Brian Murray (brian-murray)]

I believe you also need to make the initrd again, this can be done via 'sudo initramfs -u', and then you should be able to see the splash screen while booting.

[dachs (a20)]

Yesterday 43 of my packages have been updated. Looks as if the 'right' one was amongst them. Because today logo and progress bar were visible during bootup too.

[dachs (a20)]

PS:

~$ sudo initramfs -u
sudo: initramfs: command not found

Shall I do something else?

[Brian Murray (brian-murray)]

It is actually 'sudo mkinitramfs -u'. However, if it has been resolved it seems to be a moot point.

[Bryce Harrington (bryce)]

Sounds like this is fixed now. if I've misunderstood, please reopen.

[dachs (a20)]

For the installed Gutsy the problem has vanished as described.

Yesterday I loaded the final ubuntu-7.10-dvd-amd64.iso and burned it. Now when I boot off that DVD the problem is not solved:
Splashscreen is visible, but after X and disk (see bug description) there is just a black screen with a blinking cursor.

"Ctrl+Alt+F1" does not have any effect, Crtl+Alt+Bbackspace causes a shutdown.

[wolfger (wolfger)]

This has been marked "incomplete" for over half a year now, but it does not appear that we are actually waiting for any information. Does the problem still exist? This looks like something that should either be closed, or set back to some other status (confirmed? in progress?)

[dachs (a20)]

I'm no longer using Gutsy. With Hardy I haven't experienced that problem yet. So I'll mark it fixed. Thank you!