blank screen after upgrade to 64 bit ubuntu

Asked by Jacques Malaprade

Hi,
I would very much appreciate your help. I have bought a new HP Pavilion dv-6... which had Windows 7 pre-installed. I tried to make it a dual boot with success until I noticed I have installed Ubuntu 32 bit. I reinstalled the system to 64 bit and now I only get a blank screen on boot. I can boot into windows now but it won't boot into ubuntu. Can anyone please help. There is nothing on screen that would assist with tracing the error, even under restore mode.
Thanks,
Jacques

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xserver-xorg-video-ati Edit question
Assignee:
No assignee Edit question
Solved by:
Jacques Malaprade
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What video chip does it use?

Revision history for this message
Jacques Malaprade (malapradej) said :
#2

Hi,
Thanks for getting back.
Typed the following:
sudo lshw -C display
...
description: VGA compatible controller
product: NI Seymour [AMD Radeon HD 6470M]
vendor: ATI Technologies Inc
...

Revision history for this message
Jacques Malaprade (malapradej) said :
#3

I got it. Thanks to the help on this forum of course. Reading a bit further on I noticed the nomodeset option at boot, and then to install the proprietary drivers.
To make it easier for those who are also 'relatively' new to linux:
At GRUB2 boot selection (i.e. the menu you get when you have a more than one OS on the PC), move to linux ubuntu and type e. This will bring up parameters that you can add to the boot up process. Remove the text 'quite' and 'splash' and replace with 'nomodeset'. Type Ctrl-X or F10. The screen should now be set a lower resolution but you should be able to see everything on the GUI. If ubuntu asks you to update the driver, do this. If not go to System > Administration > Additional Drivers, and there should be the proprietary driver listed which you can install.
Worked for me. Now all I need to figure out why the this /dev/mapper/cryptswap1 message keeps on appearing at boot time. This will be for another post.