Graphics Resolution- Upgrade /Blank Screen after reboot

[MAFoElffen]

// Updated As Of: 2015.1.10, Version 14.10

Are you having these problems?
- Error- "Cannot display this graphics mode"
- GRUB_GXFMODE-auto results in Blank screen problems on Startup? (this includes purple or black screen, flashing cursor, stuck at splash screen...)
- No Grub Menu?

Note: Keep checking back to this post and the next 2, as I edit them with the latest changes and workarounds.

The Table Of Contents (http://ubuntuforums.org/showthread.php?t=1743535&p=10740087#post10740087) (<-- Link) is on page 2. It has links to many graphics tutorials, workarounds and fixes in this thread.


Preface
Linux distributions such as Ubuntu, basically and simplistically run in layers like this--> You have a Linux kernel running. On top of that layer, you have a terminal session- running to interact with other layers. On top of that, you have an GUI, XTerminal session, X-Windows, XServer or also known as an XSession running to have a visually interactive session running. In each version of Ubuntu (and of distro's) an honest and earnest attempt is made to make each new version easier to use for a new user, in a way that is pleasing to the eye. Each of these changes does mean underlying changes in how things relate to each other layer... on a base that is trying to cover a myriad of hardware combinations, that users will install that distribution onto. Sometimes all of these combinations cannot be "foreseen." (For instance when a certain video card type is made by over a dozen different vendors...) These techniques are similar to the same problems in Unix and XServer (XServer Host & Client)...

Here is a short quick-reference of Linux short-cuts and hot-keys to help you get around and to help diagnose graphics problems in an Linux XSession. Some are also helpful later in just everyday kind of tasks. Like I said, this is only an abbreviated list, but I included them here because they do come in handy in diagnostics and the correction of boot and video errors:

<Ctrl><Alt><F1>
Switch to the first text terminal. Under Linux you can have several (6 in standard setup) terminals opened at the same time. Terminals start as tty0 and go up from there. Most of the time the normal boot text console, that is present "under" the GUI or XSession (in Ubuntu) is tty1, so you would press <Cntrl><Alt><F2> to get to it...

<Ctrl><Alt><Fn> (n=1..6)
Switch to the nth text terminal.

tty<Enter>
Print the name of the terminal in which you are typing this command.

<Ctrl><Alt><F7>
Switch to the first GUI terminal (if X-windows is running on this terminal).

<Ctrl><Alt><Fn> (n=7..12)
Switch to the nth GUI terminal (if a GUI terminal is running on screen n-1). On default, nothing is running on terminals
8 to 12, but you can run another server there.

<Tab>
(In a text terminal) Autocomplete the command if there is only one option, or else show all the available options.
THIS SHORTCUT IS VERY HANDY! This also works at LILO or GRUB prompt!

<ArrowUp>
Scroll and edit the previous command history. You can then use that command as is or edit it to change. Press <Enter> to execute.

<Arrow><Down>
As above, but go back to the next command in history.

<Shift><PgUp>
Scroll terminal output up. Work also at the login prompt in the tty text console, so you can scroll through your bootup messages to find errors and messages. Does not work to see terminal output that has been "cleared."

<Shift><PgDown>
As above, but scrolls terminal output down.

<Ctrl><Alt><+>
(in X-windows) Change to the next X-server resolution (if you set up the X-server to more than one resolution in /etc/X11/XF86Config). For multiple resolutions on my standard XVGA card/monitor, I have the following line in the file /etc/X11/xorg.conf (the first resolution starts on default, the largest determines the size of the "virtual screen"):
Modes "1440x900" "1024x768" "800x600" "640x480" "512x384" "480x300" "400x300" "1152x864" Whichever resolution you have as first in this line will be the default.

<Ctrl><Alt><->
(in XWindows) Change to the previous XServer resolution.

<Ctrl><Atl><Backspace>
Linux Ubuntu version 10.10 and previous- Kill the current X-session.

<Right-Alt><SysReq><k>
Linux Ubuntu version 11.04 and later- Kill the current X-session.

-- The "Linux shortcut keys" are just that, meaning Linux is already booted. to use them-- although "some" of them do work in the Grub CLI. *such as the <Tab> for autocomplete)

Basically, between the grub menu and the GUI Desktop Manager (GDM or LightDM), where you are getting a blank screen the only short-cut keys that "may" be available are the <ctrl><alt><F1 the F6> keys and <ctrl><alt><F7> key... which I mentioned, may not work even if you were not having graphical problems.. But if they do, you have some options.


General
Yes, with every new release of a distribution of Ubuntu, there seems to be similar and reoccurring problems that arise with "graphics" when trying the run a LiveCD and after the initial install and first boot. These are my notes that have help people through many releases of Ubuntu, up through Ubuntu desktop variants and server.

Basically, we want to make sure that the Grub menu boots. then verify that the kernel is booting, then that the XServer Session starts and displays.

Troubleshooting Flow Chart
This is to break this down into steps:
Step 1. Do you have a Grub Menu?
- Yes: Go to step 2...
- No: While booting, Press shift key (don't hold down) multiple times to see if the Grub menu will come up.
- - If yes on Menu, go to step 2
- - If no, use a LiveCD to chroot >> Change /etc/default/grub/ (line) GRUB_HIDDEN_TIMEOUT=00. and rerun "update-grub" Or you can do that chroot'ed from a LiveCD... instructions second half of post #3.
(Note- that will display a warning on boot- saying that timeout cannot be set to '0'... but it will display the menu, then and have no apparent challenges with that)
- - - If yes on Grub Menu go to Step 2
- - - If No, go to my fix on "Forcing Grub To Show Menu"... Link in Post #2
- - - - If yes on menu, go to Step 2
- - - - If No, reinstall grub and Start Step 1 from Beginning... Because it seems that Grub is not booting.

Step 2 "Does the Linux Kernel Boot?" At Grub Menu, go into edit mode and boot into a text console (see instructions below)
- Yes. Go to Step 3
- No. Messages will be verbose on what is loading, what are warnings and what are error messages. Shortcut keys will start to work as the kernel modules load. If if stops at an error, you will be able to use the shortcut navigation cuts to review the errors. Depending on the error, if it is a kernel error, you may be able to reinstall or renew the kernel image. If it is a device module, at least you have somewhere to go to reload that device module or driver.,,, Goal is to get a "booting kernel."

Step 3. From the Grub Menu, try to boot in Rescue mode/low graphics.
- If Yes, look for additional drivers and install recommended driver.
- If No, goto Step 4 to verify that linux kernel will boot.

Step 4. Can you boot a graphical XSesion from a text console session? From the command line type


sudo service gdm start # substitute "lightdm" when appropriate
- Yes No black screen/No problem... should boot straight from the grub menu.
- No. Reboot and start testing and changing gfx_modes and kernel boot graphical modes, still booting into the text console before you try to start an XSession. Going this way, you will have more of a possible chance to be able to toggle between a graphical session or text terminal session (sometimes). ...and at a text console, at least you have the ability to install files and make changes to config files. And if you can get back into a command prompt, you could then stop the gdm service that is locked.

You can stop the graphical desktop manager (gdm or lightdm) service via


sudo service gdm stopNote-- Changes/Updates. GDM was used through v11.04. v11.10, v12.04 and newer used LightDM as the Desktop Manager. If so use "lightdm" is place of "gdm."

Digging in and opening up the hood:
If you can successfully boot grub, you are at least past point one. You can use grub as a jumping off-point- To test and see what graphical modes do work. Modes in Grub and where the linux kernel boots into does have a direct relationship to mode problems/successes when an Xorg Xsession starts.

Here, I can mention LiveCD'es. See post 3 for notes on using these techniques with a LiveCD. To me, a LiveCD in hand, is a very valuable diagnostics and recovery tool. If you can successfully boot and display a LiveCD on your PC... You are almost there.

A note about temporarily "editing" the kernel boot line...
This is an example of the menu entries of a Ubuntu menu item that will display when you press "e" in a Grub menu:


recordfail
load_video
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-efi=hd1msdos2 --hint-baremetal=ahci1,msdos2 32939def-1f4a-4134-9b56-bed2319a9216
else
search --no-floppy --fs-uuid --set=root 32939def-1f4a-4134-9b56-bed2319a9216
fi
echo 'Loading Linux 3.16.0-28...'
linux /boot/vmlinuz-3.16.0-28-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash
initrd /boot/initrd.img-3.16.0-28-generic
The Linux kernel boot line in indicated above in red.

Note: Something that had changed starting with version Natty 11.04 and GNU Grub 1.99~rc1... Look at the kernel boot line again, below:


linux /boot/vmlinuz-3.16.0-28-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash
What we used to do to help display error messages was to remove the options in blue ( quiet splash ) and type in " nosplash --verbose text " at the end of the boot line to boot into a text console (and have all the messages displayed).

Note on the "text" option. It had stopped working as of Kernel 3.x.x. I had a Launchpad and Upstream Linux (kernel.org) bug opened on that. It is working now. It works again now. So if you have an earlier version that does not work with that, then use "singlle".

Between 11.04 and 12.04, there was a kernel boot option " vt_handoff=7 "). This option is no longer there, preparing for systemd. That option's purpose was (from the wiki)


For a smooth boot process, we want to display something other than a black screen as early as possible and leave it on screen until the desktop is ready. vt.handoff=7 is part of this. We have the boot loader display an aubergine background (we wanted to have an Ubuntu logo as well, but there are problems with different aspect ratios between the boot loader and the real system, so this is the next best thing). vt.handoff=7 then causes the kernel to maintain the current contents of video memory on virtual terminal 7, which is a new "transparent" VT type. The first time that the kernel is told to switch away from VT 7, either from Plymouth or manually (Alt-F1, etc.), these contents are lost and VT 7 reverts to text mode.

The upshot is that, when everything is working correctly, you get an aubergine background on the way out of the boot loader, then at some point Plymouth displays a logo and a progress indicator on top of that, and then the display manager comes up and smoothly replaces that with a login prompt.
So if we want to see all the error messages, we now also have to remove this from the boot line temporarily while trying to find problems.

So to boot into a text console to verify that the system is booting into Linux, we edit the above kernel boot line to look like this:


linux /boot/vmlinuz-3.16.0-28-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro nosplash --verbose text
After editing, press <cntrl><x> and it will try to boot the menu entries. If and after the kernel boots in text mode, you will have more options to change things going into an Xsession.

If the kernel didn't boot, check the displayed error messages. You may have a kernel image problem, where you may have to reinstall the kernel image... or a device driver/module problem.

If you can boot the linux kernel and you know the package name of the driver you need... Reboot and get into the grub menu, cursor to the main boot menu item. press "e" > go to the kernel boot line and append " text " to the end of the line. Press ctrl-x to boot the kernel... it will boot into a text console mode. Login as you > install the driver via apt-get or aptitude...

Now that "text" kernel option is back again, that is now the accepted way to boot to a text console. If that does not work, then use "S" (capital S) for single mode. If you have nvidia graphics use nomodeset and look near the end of this post. If you have radeon, use "radeon.modeset=0") If you really want to see what is going on, turn on debug via "--verbose debug drm.debug=0xe plymouth:debug "

Going on
If still no Xsession. I usually check the /home/username/.xsession-errors file for errors. where can see if there is a problem with loading a driver or in the /var/log/Xorg.0.log file. Then I go to grub... Another log to now check is var/log/kernel.log to see if vmap allocation is running out of memory on startup (look at the nvidia tips). Then I look at the /var/log/Xorg.0.log file.

The Grub menu does not usually display if Ubuntu is the only OS. If you are having problems not seeing the grub menu on boot, hold down the "shift" key. Even if the menu is set to "silent" or not to be shown, grub should be listening for the shift key to interrupt the boot sequence. On some machines, holding the shift key down continuously will cause a keyboard overflow-- if it does, press the shift key multiple times instead. If it still doesn't bring up the Grub menu, commenting out /etc/default/grub/ line


# GRUB_HIDDEN_TIMEOUT=00
sometimes helps with that... But I found a way to hardcode it in and force it to show, even on difficult hardware:
Look at post #2 > Forcing Grub to Show Menu

If that still doesn't bring it up after that, reinstall grub.

Uncommenting the line in the /etc/default/grub that says


#GRUB_GFXMODE=680x480

helps if you give it another hint "should" work to see graphics in that mode...

I found out just by testing different things that if you set the resolution and the graphics hint like this


GRUB_GFXMODE=1024x768x16
# Or
GRUB_GFXMODE=1024x768x32

... that is set it to a 1024x768 resolution in 16bit graphics mode or 32bit graphics mode. This is not documented, but dfound that through my GNU, Xorg and kernel notes and further tests.

Here is where a lot of the "blank screen" problems arise:
If no setting is found in /etc/default/grub, Grub2 uses the resolution established in /etc/grub.d/00_header, which is set at default to auto. The else on that is supposed to be that, but if it errors, sets to text mode, which is why some graphics errors just error out to text mode. If it "thinks" it is in a valid mode but actually isn't (or is actually locked up without returning that error code) then it is simply blank.

In simple terms- In "auto" or if a specific graphics mode is not specified "explicitly", it tries different modes until the first one is found that does not return an error code. If that mode happens to be out of range and locks up before it returns that error code, you get a blank screen... If the mode specified is a known supported resolution mode by height and width (ex: 800x600), it is still going to roll through the different color depths and it still may be going out of range by an unsupported color depth setting it is trying...

***That is why that last hint works. It sets if in a resolution and mode that is close to something that it might be when the graphics layer starts up (Plymouth and X).

One way to test this would be to press <ctrl><alt><F1> or <cntrl><alt><F2>, then <ctrl><alt><F7>, which is supposed to be the "toggle hot-keys" between a graphics session and a text session... but I'll tell you now, that crtl-alt-F2 does not work on some of the boxes I have here that have "no" existing problems with graphics... So that may not be a valid test. Booting as above instructions noted > Into a text console if this didn't work. This will narrow things down to verify that the kernel has booted and that there "is" an XSession problem. When there is a problem with that, it means the modes get locked trying to switch from one to another. If is has problems going to and from virt tty's, make the Grub term and console settings closer to what the graphics should be, by giving it hints.

To try different kernel boot options, using "e" at the grub menu. Go to the kernel boot line... try these options (one at a time/not together):


nomodeset # note- remeber that "#", denotes a comment, do not type that or anything after that... just notes to you.
nouveau.modeset=0
radeon.modeset=0
i915.modeset=0
xforcevesa
## vga=xxx # Note- where xxx is a vesa mode that your card supports, such as 771 # this worked previously, but is now deprecated and only work on earlier versions
video=uvsesafb:mode_option=1024x768-32,mtrr=3,scroll=ywrap,noedid # use that noedid option if you get a bad edid read error in the xorg log
video=DVI-D:1024x768-16@60

These options, again, would be added near the end of the line, after the kernel name, For other boot options, look here:
http://ubuntuforums.org/showthread.php?t=1613132
Like this:


linux /boot/vmlinuz-3.16.0-28-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash video=uvsesafb:mode_option=1024x768-32,mtrr=3,scroll=ywrap

Another thing you can try is to drop down the the grub CLI (command line interface) via pressing "c" while in the grub menu... While you are in the Grub CLI, you can use it to test the variable setting, set them to other settings and to see what modes your video supports.-- instead changing things (hard edits) and rebooting to see if it worked... Just just "set" and "unset" viables to change your environment variable from the command line. Such as to set the screen resolution, you should set the variable $vbe_mode before loading vbe and/or gfxmterm (default mode is 0x101 i.e. 640x480 8bpp) Test your graphics... What I last said adapted and translates to


set gfxmode=1024x768x16
load_video
insmod gfxterm
From the CLI you could use


GRUB> echo $linux_gfx_mode
to see what the video mode it is currently set to... It will most likely be set at "keep". If you then


echo $gfxmode
it will most likely say "auto' which is the default.
[/code]
Then use


GRUB> vbeinfo
to get the video modes as grub sees them on your hardware. Get ready with your "pause" key as may get as many as 3 screens of info will go by faster than you can possibly read. When ready to read more, hit the enter key. "vbetest" will tell you what video mode in hex it is currently set to. You can then use these modes in the kernel boot line and append/adding a vga=xxx, where xxx is the mode. Note that this XXX value must correspond to a resolution that you had set the gfxmode to.

Note: The 1915 driver and natty currently have know bugs with vbeinfo and the "vga=xxx" kernel switch. Please use hwinfo (below) instead, then see the i915 notes at the end of this post.

From a grub CLI, you can see video modes via


vbeinfo

From a Linux text console session, you can use (updated, the util hwinfo went away...)


sudo lshw -numeric -class video
sudo lspci -vvn | grep -i VGA
to find video GPU's installed
To see what modes your system supports, use


xrandr -q


sudo xrandr -q > ~/video_results.txt
To save the result to a file in your Home Directory.

On some installs, the utility "lshw" is installed by defualt, but if not


sudo apt-get install lspci
This utiltity is very small and it well worth the few bytes of space it uses and the few seconds it takes to install. Besides showing what GPU is installed, it will show which driver module it is currently using (or not).

Change to grub default file (/etc/default/grub) 00_header, line that says "set gfxmode=auto" to "set gfxmode-1024x768x16" to the kernel boot line in 10_linux section... Unfortunately for most who are reading this thread, this program will not help them "until" they get a working graphical Xsession. Once they do, they could use this program to tweak their session or to Customize the default "startup" of their Grub Menu.

After you make changes to any grub file, remember to run


sudo update-grub

to pick up the changes.

On the info returned from


xrandr -q
That will give you hints on what you can set as a resolution. It returns modes that your installed video card supports in a hex number format. For instance it may say 00x0303, which is 771 decimal. You could use that the converted decimal number in the kernel boot line with a "vga=xxx" switch such as


linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro nosplash video=VGA:1024x768-16@60
You can use the info returned in grub using vbeinfo the same way... If you are not sure what to do with these results, post them here, ensuring that you highlight the results and press the "#" button to wrap the results with code tags

All this is too find a Mode that your hardware supports so that you can set them manually. Once you find a mode that work, then you can make it permanent.

Now that I found something that works, how do I make it permanent?
In a terminal:


cd/etc/default
sudo gedit grub
Edit the line "GRUB_CMDLINE_LINUX_DEFAULT". Add your new options, for example:


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=VGA:1024x768-16@60
Now in a terminal run


sudo update-grub
Now each time you update grub and in configures the files, it will pick up these changes.

Noteworthy Notes

***NEW*** The "video=..." kernel boot option replaces and enhances what the old "vga=..." used to be. That old "vga=xxx" option now does not work (deprecated). The current-- The "video=..." is kernel boot option tells the kernel KMS driver on what resolution and/or frequency to use. For this to work, KMS must not be disabled (see above). The format of that option is as follows:


video=<connection:<resolution>[-colorDepth][@refreshrate][OtherOptions]

That tag is expanded in capabilities now. Too much to list on this 1st Post. I promise to go into detail on what this option can do and how to use that in another post and link to that from Post #2.

xrandr is a very powerful graphics kind of utility that is worth learning. I use it a lot to override settings and/or for testing and diagnostics... The changes will only effect the current session, meaning if there is a reboot, gone. But, I also use this in a startup.desktop file to make it work as if it were persistent... Can also be used from scripts.

Notes on for some Laptops:
Will inform your BIOS to use provisions for Linux:


acpi_osi=Linux
Will fix some backlighting Problems:

Hi,
The best workaround for solving backlight ISSUE was for me:
Autorun "setpci -s 00:02.0 F4.B=00" each boot.

Steps:
1) edit rc.local

gksudo gedit /etc/rc.local2) Add the command before EXIT 0

setpci -s 00:02.0 F4.B-03) Restart.
You should now be able to boot in UNITY where nomodeset was unable.

Notes about nvidia cards and SLI
The "nomodeset" kernel bootline switch usually works for most nVidia cards, but now all.

Especially for nvidia cards, I usually just into a text mode by going to a text console via grub edit ('e") append " text " to the end of the kernel boot line and boot{"ctrl-x') and after a login type


sudo apt-get update
sudo nvidia-installer --uninstall # this may return not found, but do it just in case it is there.
sudo apt-get remove nvidia-*
sudo apt-get install linux-headers-('uname -r')
sudo apt-get install nvidia-current
sudo nvidia-xconfig
sudo apt-get update
(Note- This example assumes that you have a GeoForce 6xxx or better card) then try to start the GUI via
sudo service gdm startFor Unix and Linux, some versions of Xorg will not boot when there are multiple physical instances of the same video card installed (which bridged SLI cards are) until the proprietary video driver is installed. If you have SLI and a LiveCD will not boot: Remove one SLI card > Boot the LiveCD and install the system > Install the video drivers... Install the second physical card.

There is another problem coming up with natty and the Geoforce 9800 where the kernel is misallocating and running out of allocated addressed video memory while trying to boot. This has been resolved by allocating more memory by adding "vmalloc=192MB" to the kernel boot line.

One other problem on the order modules are loading:


sudo echo RUN+="/sbin/modprobe nvidia" > /etc/udev/rules.d/90-modprobe.rules
sudo echo options nouveau modeset=0 > /etc/modprobe.d/nouveau-kms.conf
sudo update-initramfs -u

ATI TIPS:
Note that some ATI cards need flgrlx and some do not... If not then this workaround sometimes works:

Steps for ATI users:

1. Get to a terminal session or TTY Console

2. Edit the sources list to include the the Conical Partner Repo's:


sudo vim /etc/apt/sources.list
Then


sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get update
sudo apt-get remove --purge fglrx*
sudo apt-get install fglrx
sudo apt-get upgrade
sudo reboot
The above only works for some but not all, depending on what card you have and whether it actually is supported by additional drivers (proprietary). All at the moment, mostl seem to need "nomodeset radeon mode=X", where x= 0 or 1... Some ATI cards are not working with the current natty kernel, but are working with the older 2.6.37 kernel or the proposed 2.6,38.9 kerne (please see post 2)l


Intel i915GM
There is a known bug with this chipset and Natty. Some of the workarounds include using "i915modeset=0" and some "i815modeset=1" in the kernel boot line and going to /etc/default/grub to

Andy Whitcroft wrote on 2010-12-02 as part of Launchpad Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683775:

As a work-around we can turn this off by adding the line below to /etc/default/grub and running update-grub:
GRUB_GFXPAYLOAD_LINUX=text
There is also an upstream Debian Bug with this driver that says if you try to use a "vga=xxx" switch on a Linux 2.6.x kernel and this driver, you will get a black screen. It further says if you use anything besides the i915's driver's internal framebuffers, it will get a black screen. So-- the "i915modeset=0" also has to be set in the kernel boot line to turn off KMS.

***NEW*** The 'video" boot option works on these using the vesafb driver. The vesafb driver is a generic driver for a graphic framebuffer for intel GPU's. (Linux Kernel's doc's on that still say you can access, this via the vga= option, although the code now does not support that "vga" option.) Here is an example using that appended kernel boot option


video=vesafb:nomtr,ypan,invers


Notes on KMS:

This thread was inspired by the addition of this Wiki entry and how it's application "changed" how things worked or failed:

Quoted from the Ubuntu Wiki (editted):
KernelModeSetting

Kernel mode-setting (KMS) shifts responsibility for selecting and setting up the graphics mode from X.org to the kernel. When X.org is started, it then detects and uses the mode without any further mode changes.

Configuring KMS

KMS is enabled by default for the -intel, -ati, and -nouveau drivers. It is not available for any other drivers at this time.

If you need to manually adjust mode settings, the video= boot parameter is used. For example,

video=LVDS-1:d -- Disables the LVDS
video=VGA-1:e -- Enables VGA-1

Turning it off

If you need to turn KMS *off* do the following depending on the hardware in question:

# ATI Radeon:
echo options radeon modeset=0 > /etc/modprobe.d/radeon-kms.conf

# Intel:
echo options i915 modeset=0 > /etc/modprobe.d/i915-kms.conf

# Nvidia (this should revert you to using -nv or -vesa):
echo options nouveau modeset=0 > /etc/modprobe.d/nouveau-kms.conf

For some users (particularly users with encrypted volumes) KMS is enabled very early in the boot process and in order to pick up these changes you need to run
sudo update-initramfs -u

For more "detailed" testing and configuration techniques and options (geared more for the advanced level user), please read this Wiki pages:
https://wiki.ubuntu.com/X/Config/Resolution
https://wiki.ubuntu.com/X/Config#hal

And for a more detailed, consolidated list of Kernel Parameters, please see:
http://www.kernel.org/doc/Documentation/kernel-parameters.txt

If All Else Fails? See Post 2 for links to tutorials and detailed instructions

If you need help or ideas, post to this thread or start your own thread with your issue. Please include some info about your hardware, what is does or where it stops. To help with that, please include the result of:


sudo lspci -vvn | grep -i VGA
sudo lshw -numeric -class video
cat /var/log/Xorg.0.log
ls -l ~/.Xauthority

[MAFoElffen]

Revised: 2023.01.16

There is wealth of info buried in this sticky. I've gone through and updated some of these posts to get them current. I decided users really needed a way to quickly find the info they need in this thread. So here we go...


TABLE Of CONTENTS
(Links to Posts)

Kernel Series 6.2.0 to 6.5.0 Compile Error Work-Around (https://ubuntuforums.org/showthread.php?t=2494273&p=14175164#post14175164)

KMS, Grub Edits and Modesets (http://ubuntuforums.org/showpost.php?p=10740083&postcount=1)

Modesetting and the LiveCD (http://ubuntuforums.org/showpost.php?p=10740097&postcount=3)

Mounting An Installed System From the LiveCD (http://ubuntuforums.org/showpost.php?p=10740097&postcount=3)

Installing NVidia Binary Drivers (http://ubuntuforums.org/showpost.php?p=10909540&postcount=280)

Installing NVidia Packaged Drivers (http://ubuntuforums.org/showpost.php?p=11467050&postcount=797)

Finding the Right NVidia Driver from the Card ID (http://ubuntuforums.org/showpost.php?p=10910784&postcount=284)

Installing ATI Binary Drivers (http://ubuntuforums.org/showpost.php?p=10950714&postcount=334)

Installing ATI Packaged Drivers (http://ubuntuforums.org/showpost.php?p=11467052&postcount=798)

EDID and modelines (http://ubuntuforums.org/showpost.php?p=10925558&postcount=310)

Modelines I (http://ubuntuforums.org/showpost.php?p=10898850&postcount=258)

Modelines II (http://ubuntuforums.org/showpost.php?p=10907238&postcount=275)

Adding The Old Hot-Key Back in for Kill-X (http://ubuntuforums.org/showpost.php?p=10899861&postcount=262)

Kernel 3.x.x Linux Patches for pre- Oneiric Releases (http://ubuntuforums.org/showpost.php?p=10924650&postcount=306)

Installing Xubuntu/XFCE with an Older Intel Chipset (http://ubuntuforums.org/showpost.php?p=11389175&postcount=721)

Resetting .Xauthority permissions file For Logging into X (http://ubuntuforums.org/showpost.php?p=11404605&postcount=766)

mkxauth Script to reset .Xauthority file (http://ubuntuforums.org/showthread.php?t=1743535&p=13514576#post13514576)

Temporalrily Booting Into a TTY Text Console (http://ubuntuforums.org/showpost.php?p=11383888&postcount=715)

Trouble Booting a LivdCD? (http://ubuntuforums.org/showpost.php?p=11409489&postcount=783)

Forcing Grub to Show Menu (http://ubuntuforums.org/showpost.php?p=11469860&postcount=800)

Temporarily Editing Grub Menu for Boot Options (http://ubuntuforums.org/showpost.php?p=11491229&postcount=812)

Server Graphics I - Blank Screen After Install / 1st Boot (http://ubuntuforums.org/showpost.php?p=11547960&postcount=845)

Server Graphics II - Aubergine Theming (http://ubuntuforums.org/showpost.php?p=11548061&postcount=846)

I Ran Update Manager, Now I have a Blank Screen (http://ubuntuforums.org/showpost.php?p=11553268&postcount=859)

The "video" Kernel Boot Option Explained (http://ubuntuforums.org/showthread.php?t=1743535&page=132&p=13204829#post13204829)



--
Latest: Added link to Kernel 6.5.0 / NVidia Compile work-around.

[MAFoElffen]

To do this from a LiveCD... The first screen you will see is a black or purplish screen with an icon centered at the lower part of the screen. This icon will be a keyboard and person.

http://doc.ubuntu-fr.org/_media/installation/live_cd_maverick1.png?cache=

Press escape.

https://help.ubuntu.com/community/LiveCD?action=AttachFile&do=get&target=804+Live+1+.png

Press escape.

At that screen, instead of picking a language, press the <esc> key. Actually you can do anyhting here, but escape is faster. It should get you to this screen:

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-Options.png

At this screen, it is a Casper/Isolinux Menu. Look at the lower right of the menu, where it says "F6 Other" Pressing <F6> will bring us this screen (below):

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other.png

Here (above) there is some of the most common boot up options, where you want to try "nomodeset"

If that doesn't work, if you press <F1> for help and while in the "help menu" pressed <F6> or <F7> you would be presented with more common boot options. where you can select them with <enter> or <space> such as ...

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other-Manual.png

And when you press <esc> those entries are retained and then you can edit them. If you edit them, add your options after the double dashes ("--") That will be the linux boot line.

What I do in my installs is to use the "try" option. That way I can ensure the hardware is being found, everything works... And If I install from the Live Image and the installer errors out, I can review the syslogs that are in the live image's memory. (I also have a way out / instead of locked up)

To mount an installed system from a LiveCD:
(This example is to install drivers, but similarly could be used to mount a system and reinstall grub or kernel image)

1. Boot a Live-CD,
2. Find your "Installed" partition, e.g. /dev/sda5 (where you've installed the OS ... the "/" partition)


sudo mount /dev/sda5 /mnt
3. If you have a dedicated boot partition: sudo mount /dev/sda3 /mnt/boot


sudo mount -o bind /dev /mnt/dev
sudo mount -o bind /sys /mnt/sys
sudo mount -t proc /proc /mnt/proc
4. "changeroot" to /mnt


sudo chroot /mnt /bin/bash
5. Now you're "on" the installed system, see the chroot man page for details

Do what you need to do from there, like install drivers, install a kernel, install grub, etc. Once you are through, Press <cntrl><x> or just enter the command "exit". That gets you out of the chroot. Then unmount your mounts... If you don't... oh well.

[KazukiFlame]

hi, i booted up with a blank screen. i've tried pressing the shortcut keys you mention, none of them worked. i think most of those shortcut assume that you could bootup into linux to begin with. but i can't do anything at the bootloader right now aside from ctrl+alt+del.

[dathrien]

I had the same problem.
Solved with uncommenting(delete #) GRUB_GFXMODE=640x480 in /etc/default/grub
Do not forget to run sudo update-grub in a terminal afterwards.

[dugh]

hi, i booted up with a blank screen. i've tried pressing the shortcut keys you mention, none of them worked. i think most of those shortcut assume that you could bootup into linux to begin with. but i can't do anything at the bootloader right now aside from ctrl+alt+del.

Same here, none of the shortcuts (control-alt-f1 to get to text login) or boot options (like nomodeset and so forth) work. I just get a blank screen after the grub stage.

I didn't get a blank screen when booting up to the live usb of ubuntu 11.04, nor with 10.10, although there were other issues. I only get the blank screen when booting up to an installed 11.04.

[pssturges]

Same here, none of the shortcuts (control-alt-f1 to get to text login) or boot options (like nomodeset and so forth) work. I just get a blank screen after the grub stage.

I didn't get a blank screen when booting up to the live usb of ubuntu 11.04, nor with 10.10, although there were other issues. I only get the blank screen when booting up to an installed 11.04.

Me too. I upgraded from 10.10, now I get grub then a black screen. Recovery mode is the same. If I select an older kernel I can get into recovery mode but that's it. I can't even seem to get a terminal.

Phil

[emerick7]

I'm getting the blank screen as well...
<ctrl><alt><F1> or <cntrl><alt><F2>, then <ctrl><alt><F7> does not work. Ctrl-alt-del seems to be the only recognized keystrokes.

I tried commenting out /etc/default/grub/ GRUB_HIDDEN_TIMEOUT=00. I also tried uncommenting the line in the /etc/default/grub that says gfxmode=680x480. Neither of those options worked.

You lost me though when modifying boot loader settings. I'm able to run sudo hwinfo --framebuffer, but am not sure why to do with this info...

[MAFoElffen]

hi, i booted up with a blank screen. i've tried pressing the shortcut keys you mention, none of them worked. i think most of those shortcut assume that you could bootup into linux to begin with. but i can't do anything at the bootloader right now aside from ctrl+alt+del.
Between the grub menu and the GUI GDM, where you are getting a blank screenm the only short-vut keys that "may" be available are the <ctrl><alt><F1 the F6> keys and <ctrl><alt><F7> key... which I mentioned, may not work even if you were not having graphical problems..

1. Make sure Grub boots and you can get a menu. After booting grub, you are at least past point one. Use grub as a jumping off-point- To test and see what graphical modes do work. Modes in Grub and where the linux kernel boots into // have a direct relationship to mode problems/successes when an Xorg Xsession starts.

2. Boot into a text console to verify that the system is booting into Linux.

3. After kernel boots in text mode you will have more options to change things going into an Xsession.

-- The "Linux shortcut keys" are just that, meaning Linux is already booted. to use them-- although "some" of them do work in the Grub CLI. *such as the <Tab> for autocomplete)


I'm getting the blank screen as well...
<ctrl><alt><F1> or <cntrl><alt><F2>, then <ctrl><alt><F7> does not work. Ctrl-alt-del seems to be the only recognized keystrokes.

I tried commenting out /etc/default/grub/ GRUB_HIDDEN_TIMEOUT=00. I also tried uncommenting the line in the /etc/default/grub that says gfxmode=680x480. Neither of those options worked.

You lost me though when modifying boot loader settings. I'm able to run sudo hwinfo --framebuffer, but am not sure why to do with this info...
So-- lets break this down into steps/into a troubleshooting flow chart-->

Step 1. Do you have a Grub Menu?
- Yes: Go to step 2...
- No: Whiie booting, Press shift key (don't hold down) multiple times to see if the Grub menu will come up
- - If yes on Menu, go to step 2
- - If no, comment out /etc/default/grub/ GRUB_HIDDEN_TIMEOUT=00. and rerun grub-update (from a LiveCD)
- - - If yes on Grub Menu go to Step 2
- - - If No, reinstall grub and Start Step 1 from Beginning... Becuase it seems that Grub is not booting.
Step 2 "Does the Linux Kernel Boot?" At Grub Menu, go into edit mode and boot into a text console (instructions above)
- Yes. Go to Step 3
- No. Messages will be verbose on what is loading, what are warnings and what are error messages. Shortcut keys will start to work as the kernel modules load. If if stops at an error, you will be able to use the shortcut navigation cuts to review the errors. Depending on the error, if it is a kernel error, you may be able to reinstall or renew the kernel image. If it is a device module, at least you have somewhere to go to reload that device module or driver.,,, Goal is to get a "booting kernel."
Step 3. Can you boot a graphical Xseesion from a text console session? From the command line type


sudo service gdm start
- Yes No black screen/No problem... should boot straight from the grub menu.
- No. Reboot and start testing and changing gfx_modes and kernel boot graphical modes, still booting into the text console before you try to start an Xsession. Going this way, you will have more of a possible chance to be able to toogle between a graphical session or text terminal session (sometimes). ...and at a text console, at least you have the abilty to install files and make changes to config files.

See psot #2 for more info.

[emerick7]

First off thanks for the reply.

I'm at Step 2 right now... it gets stuck on "Stopping GNOME Display Manager." It seems to hang there, until I hit the enter key. At that point, I'm able to use CTRL-ALT-F1/F2 to get into the command line.

sudo service gdm start gives me gdm start/running then a process ID. CTRL-ALT-F7 brings me to the same screen though.

Also, I tried appending vga=318 but that did not have any effect.


In case this helps, after "Stopping GNOME Display Manager," it says:


speech-dispatch disabled...
*PulseAudio configured for per-user sessions
saned disabled; edit /etc/default/saned
*Enabling additional executable binary formats binfmt-support
*Starting web server apache2
/etc/rc2.d/S99acpi-support: line 7: /usr/share/acpi-support/power-funcs: No such file or directory
cups start/running, process 1084
{then it has a blinking _}


Once again, thanks for the troubleshooting!

[RWShore]

My system has a Radeon graphics card - partial output from hwinfo is

Hardware Class: framebuffer
Model: "(C) 1988-2005, ATI Technologies Inc. RV620"
Vendor: "(C) 1988-2005, ATI Technologies Inc. "
Device: "RV620"
SubVendor: "ATI ATOMBIOS"
SubDevice:
Revision: "01.00"
Memory Size: 16 MB

I tried to install Natty but got the empty screen described in here. I've just got the system back up under Maverick and am not anxious to go through that again. I'd like to be able to test the grub settings for Natty before committing to the upgrade. Unfortunately I can't boot the stand-alone Natty CD (64 bit) either - the cursor shows on the screen, I can type stuff, but nothing happens (good or bad).

Is there any way to intercept or control the CD boot so I can try to figure out video settings that may be messing me up?

[MAFoElffen]

My system has a Radeon graphics card - partial output from hwinfo is

Hardware Class: framebuffer
Model: "(C) 1988-2005, ATI Technologies Inc. RV620"
Vendor: "(C) 1988-2005, ATI Technologies Inc. "
Device: "RV620"
SubVendor: "ATI ATOMBIOS"
SubDevice:
Revision: "01.00"
Memory Size: 16 MB

I tried to install Natty but got the empty screen described in here. I've just got the system back up under Maverick and am not anxious to go through that again. I'd like to be able to test the grub settings for Natty before committing to the upgrade. Unfortunately I can't boot the stand-alone Natty CD (64 bit) either - the cursor shows on the screen, I can type stuff, but nothing happens (good or bad).

Is there any way to intercept or control the CD boot so I can try to figure out video settings that may be messing me up?
BINGO! = Yes there is. All the info above will work with/from LiveCD... The Initial Menu Screen" that asks if you want to "Try , Install or..." Is a Grub menu-- meaning you can edit. diagnose, test and/or change things from there to try to get the LiveCD to boot graphically on your hardware. Once you find the settings that work with the LiveCD, you have the for your install.

With your hardware, I'm thinking a " nomodeset " option might work and it might not display "3D Unity" (just a guess/I might be wrong) but should be fine with "Classic."

[C.C.C.P.]

Two days ago I've upgraded to Ubuntu 11.04. When I logged in, I saw a message showing me that I got a problem with my GPU. I thought it is a problem with driver, I tried to reinstall it, and it gave me nothing. I could boot in to safe graphics mode, but when I login into new Ubuntu 11.04 I can see desktop, but cant see start menu, also Alt+F2 not working, shortcuts to terminal are also not working. I got an NVIDIA 9700m, and used 16:10, 1680*1050 resolution before, didnt have any problems during upgrade to 10.10 from 10.04 and others, this is the first time I see this problem! Is it related with Unity, or new kernel?
- lshw
showed me that my GPU is recognised. But still experiencing the problem, and can't fix it. I'm attaching the screen, so maybe someone can help me. Reconfiguration of xorg.conf didn't give any result. Can anybody help me? I really would like to see new Unity.
I'm using an Asus G50-A1
Got a GeForce 9700m 512 MB

[MAFoElffen]

Two days ago I've upgraded to Ubuntu 11.04. When I logged in, I saw a message showing me that I got a problem with my GPU. I thought it is a problem with driver, I tried to reinstall it, and it gave me nothing. I could boot in to safe graphics mode, but when I login into new Ubuntu 11.04 I can see desktop, but cant see start menu, also Alt+F2 not working, shortcuts to terminal are also not working. I got an NVIDIA 9700m, and used 16:10, 1680*1050 resolution before, didnt have any problems during upgrade to 10.10 from 10.04 and others, this is the first time I see this problem! Is it related with Unity, or new kernel?
- lshw
showed me that my GPU is recognised. But still experiencing the problem, and can't fix it. I'm attaching the screen, so maybe someone can help me. Reconfiguration of xorg.conf didn't give any result. Can anybody help me? I really would like to see new Unity.
I'm using an Asus G50-A1
Got a GeForce 9700m 512 MB
That card should work fine(?) What driver shows as active in additional drivers?

I have a lot of Asus mobos and nVidia cards here. (Big fan of both) In past I'd say just use the proprietary drivers, but with natty, installing these drivers will automatically blacklist nouveau even if those are installed...Meaning there is going to be some drawbacks. (Mainly no unity)

[hreichgott]

Hi, this happened with me too, with an ATI Radeon 6310 card.
Ubuntu 10.10 installed fine and ran fine, except not with the proper resolution, so after a lot of work with the open source drivers I gave up and downloaded ATI's proprietary Catalyst driver. I got the right resolution and all was well.
Ubuntu 11.04 installed ok, but the boot appeared to hang on "checking battery state".
Eventually I tried booting into low graphics mode and reinstalled the ATI proprietary Catalyst driver. Now all is well again.
Would have been nice even if 11.04 had behaved the same way as 10.10 with this graphics card! Or at least, something other than hanging on boot, or a blank screen. Lots of people out there have ATI Radeon cards...

[neonman123]

I upgraded from Maverick to natty this morning and got a blank screen on re-boot, but did hear the gui startup sound from the speakers. I have this (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00783647) motherboard with integrated graphics, and is usually hooked up to a tv with an s-video cable. Everything loads fine with a vga monitor hooked up until you plug in an s-video cable to a tv and go to the graphics menu and click detect monitors the display on the vga will bug out, then go normal if you disconect the s-video cable and detect monitors again. This setup was working fine with maverick so I'm wondering if I just need to change some setting or possibly if natty dropped support for this graphics setup and I need to install drivers.

[pssturges]

I've got grub, but I don't seem to be able to even get a console. Following the instructions in the original post, I press e and can edit the info but I'm not entirely sure which line to edit. When entering " text " do I enter the quotation marks and what about the trailing space?

Thanks
Phil

[emerick7]

Hey MAFoElffen... any suggestions on what to try? I've ran through your post and nothing seems to be doing the trick (http://ubuntuforums.org/showpost.php?p=10746567&postcount=10).

Thanks!

[calebsdaddio]

So I'm getting a message after booting up Ubuntu 11.o4 that says "recommand mode 1280x1024". Not sure what to do. Probably my onboard video driver probs? Can anyone fill me in?
Screen goes blank and I can tell that Ubuntu is loading but just not on my screen.

[MAFoElffen]

I upgraded from Maverick to natty this morning and got a blank screen on re-boot, but did hear the gui startup sound from the speakers. I have this (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00783647) motherboard with integrated graphics, and is usually hooked up to a tv with an s-video cable. Everything loads fine with a vga monitor hooked up until you plug in an s-video cable to a tv and go to the graphics menu and click detect monitors the display on the vga will bug out, then go normal if you disconect the s-video cable and detect monitors again. This setup was working fine with maverick so I'm wondering if I just need to change some setting or possibly if natty dropped support for this graphics setup and I need to install drivers.
Uh... The link you posted says your mobo has no onboard video, which means that you "are" using "some" type of video card... which you discribe as having VGA and svideo ports...

What Video card are you using?

[MAFoElffen]

First off thanks for the reply.

I'm at Step 2 right now... it gets stuck on "Stopping GNOME Display Manager." It seems to hang there, until I hit the enter key. At that point, I'm able to use CTRL-ALT-F1/F2 to get into the command line.

sudo service gdm start gives me gdm start/running then a process ID. CTRL-ALT-F7 brings me to the same screen though.

Also, I tried appending vga=318 but that did not have any effect.

In case this helps, after "Stopping GNOME Display Manager," it says:

Once again, thanks for the troubleshooting!
@emerick7-- I'm sorry if I missed it, but I don't see where you posted what video card you are using(?) ... also, you said you tried "vga=318"...

If you could post the results from


sudo hwinfo --framebuffer
or
sudo hwinfo --framebuffer > ~/video_results.txt
Please insure that you highlighlight it and press the "#" button to wrap code tags around it. That will tell us what video you have and what modes are available to it.

[MAFoElffen]

I've got grub, but I don't seem to be able to even get a console. Following the instructions in the original post, I press e and can edit the info but I'm not entirely sure which line to edit. When entering " text " do I enter the quotation marks and what about the trailing space?

Thanks
Phil
LOL- Okay... I'll edit the first post today. Look for those additions/changes there fist post.

I will add some more "basic" explanations and examples. Someone told me it was on the verge of a geek-alert... Mmeaning it was fine as a highly technical article, but the technical level was in reality, a bit high for a new comer.. I'll try to broaden that level.

[taygan]

First of all, THANK YOU SO MUCH for an excellent troubleshooting thread. It helped me isolate my problem.

Clean install Natty 11.02 on a Gateway M-1625 with a ATI Radeon x1270 (RS690M). Note that this Radeon is no longer supported by fglrx (ATI Catalyst). After pulling my hair out for 24 hours, and trying every combination on the grub menu, I finally fixed my "blinking cursor/blank screen/fixing recursive fault but reboot is required" by downgrading the kernel to 2.6.37

First, the USB stick live desktop i386 booted to Unity fine, but Unity won't run installed (no 3D graphics??) - guess that's another issue. Next I tried installing over my 10.10 partition. It booted to rescue (recovery?) and low graphics most of the time. I thought it was a bad install so I formatted the partition and did a CLEAN install of Natty 11.04.

Grub always boots fine, it was hanging/black screen/sometimes blinking cursor after selecting the kernel. I tried many many combinations on the kernel boot line (pressing e from the grub menu): deleting everything ("quiet" "splash" and the "vt...7" thing) on the line after "ro" and trying different options (I always used "nosplash" to see what was going on - remember don't use the " when using options - it's just for reading clarity)

"nosplash text" + "nomodeset" or "radeon.modeset=0" or "xforcevesa" would SOMETIMES work, but would often hang at "fixing recursive fault but restart is needed" Other times it would hang after 3 lines, or after a few screenfuls, depending on the options, and sometimes changing with the SAME options. Grrr...

Finally, it looks like acpi is mucking things up with the latest kernel for me: The options "ro acpi=off nosplash text" can consistently get me booted to a terminal. Then from the terminal "sudo service start gdm" gets to the gdm logon screen. On the logon screen I must choose "classic (no effects)" and then I can get to gnome.

From there I downloaded the older kernel and installed it from the .debs found in the Ubuntu Kernel Mainline PPA,

If I select "older Linux Kernels" (I think that's what it says) from the grub menu and boot to 2.6.37 everything seems to work fine.

Older debs found here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/

for 32-bit i386 download and install in this order:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706_2.6.37-02063706.201103281005_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-image-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb

if you're running amd64, be sure to download the headers-all, headers-amd64, and image-amd64 - but I don't know if this workaround is needed with the 64-bit kernel.

Be sure to install (click on) the .debs in order: headers-all, headers-i386(amd64), and image-i386(amd64)!

Thanks to this blog post for the inspiration:

http://www.khattam.info/howto-install-linux-kernel-2-6-36-or-2-6-37-in-debian-squeeze-testing-or-ubuntu-or-any-debian-based-distribution-without-compiling-2010-11-13.html

[emerick7]

@MAFoElffen... Here are my results of hwinfo --framebuffer:


02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.5WU5JOR4rxD
Hardware Class: framebuffer
Model: "Intel(r)915GM/910ML/915MS Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r)915GM/910ML/915MS Graphics Controller"
SubVendor: "Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 704 kB
Memory Range: 0xc0000000-0xc07affff (rw)
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

If I use:

GRUB_CMDLINE_LINUX_DEFAULT="quiet i915.modeset=0 acpi_osi=Linux"
When I reboot it does not hang on a blank screen, but on the Ubuntu splash screen, the one with the 5 orange progress dots.

[neonman123]

Uh... The link you posted says your mobo has no onboard video, which means that you "are" using "some" type of video card... which you discribe as having VGA and svideo ports...

What Video card are you using?

it says integrated in the link and it is integrated, there is only one pcie expansion slot and it is being taken by another card. I'm definitely not using a video card. I'm not sure what video chipset it is, I do know that the Intel 945GT chipset is what the board is based around.

[MAFoElffen]

@MAFoElffen... Here are my results of hwinfo --framebuffer:


02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.5WU5JOR4rxD
Hardware Class: framebuffer
Model: "Intel(r)915GM/910ML/915MS Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r)915GM/910ML/915MS Graphics Controller"
SubVendor: "Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 704 kB
Memory Range: 0xc0000000-0xc07affff (rw)
Mode 0x0305: 1024x768 (+1024), 8 bits # decimal--> 773
Mode 0x0317: 1024x768 (+2048), 16 bits # 791
Mode 0x0318: 1024x768 (+4096), 24 bits # 792
Mode 0x0312: 640x480 (+2560), 24 bits # 786
Mode 0x0314: 800x600 (+1600), 16 bits # 788
Mode 0x0315: 800x600 (+3200), 24 bits # 789
Mode 0x0301: 640x480 (+640), 8 bits # 769
Mode 0x0303: 800x600 (+832), 8 bits # 771
Mode 0x0311: 640x480 (+1280), 16 bits # 785
Config Status: cfg=new, avail=yes, need=no, active=unknownIf I use:

GRUB_CMDLINE_LINUX_DEFAULT="quiet i915.modeset=0 acpi_osi=Linux"When I reboot it does not hang on a blank screen, but on the Ubuntu splash screen, the one with the 5 orange progress dots.
From the results you posted above from hwinfo--> Look at the numbers above in red... These are what are the decimal equivalents of the hex values that where returned. I remember you saying you thried to use vga=318... which should have been vga=792.
*** EXCEPT that there is an upstream Debian BUG that notes that using an "vga=XXX" in the kernel boot line with the 2.6.x of the kernel and your video driver (i915) will result in a black screen... It als notes that it can;t ise any framebuffer except it's own driver's, else it will also result in a black screen. So--

You could try adding this line


i915modeset=0
to /etc/modprobe.d/i915-kms.conf. What this option does is turns off KMS (kernel mode set), and uses the i915 driver and framebuffer....

If you've been getting this far, you can add that option to the Rescue mode item in Grub, start failsafe mode from there and get your cards recommended driver installed...

You could change also change GFXMODE=640x480 to:


GFXMODE=1024x768x24;1024x768x16;1024x769x8;800x600 x24;800x600x16;800x600x8;640x480x24;640x480c16;640 x480x8
or any of those alone.

[MAFoElffen]

it says integrated in the link and it is integrated, there is only one pcie expansion slot and it is being taken by another card. I'm definitely not using a video card. I'm not sure what video chipset it is, I do know that the Intel 945GT chipset is what the board is based around.
I see that now, but no-where do I see what video chipset it "is: using for that. There is an easier way to find out --> run hwinfo --framebuffer and post the reselsults here. Remember to highlight the results and press the "#" button to enclose is in code tags.

[emerick7]

@MAFoElffen: I added i915modeset=0 to i915-kms.conf (it was a new file), and also tried the GFXMODE options, with no luck. When I reboot, I'm getting the familiar black screen.

[neonman123]

I see that now, but no-where do I see what video chipset it "is: using for that. There is an easier way to find out --> run hwinfo --framebuffer and post the reselsults here. Remember to highlight the results and press the "#" button to enclose is in code tags.

I'm getting sudo:hwinfo:command not found when I type sudo hwinfo or sudo hwinfo --framebuffer or sudo hwinfo --framebuffer | more

[emerick7]

I'm getting sudo:hwinfo:command not found when I type sudo hwinfo or sudo hwinfo --framebuffer or sudo hwinfo --framebuffer | more

Try
sudo apt-get install hwinfo

[MAFoElffen]

If I use:

GRUB_CMDLINE_LINUX_DEFAULT="quiet i915.modeset=0 acpi_osi=Linux"When I reboot it does not hang on a blank screen, but on the Ubuntu splash screen, the one with the 5 orange progress dots.


acpi_os_name= [HW,ACPI] Tell ACPI BIOS the name of the OS Format: To spoof as Windows 98: ="Microsoft Windows"

acpi_osi= [HW,ACPI] empty param disables _OSI
+ acpi_osi= [HW,ACPI] Modify list of supported OS interface strings
+ acpi_osi="string1" # add string1 -- only one string
+ acpi_osi="!string2" # remove built-in string2
+ acpi_osi= # disable all strings acpi_serialize [HW,ACPI] force serialization of AML methods
[acpi_osi=Linux was generally a workaround the tell the BIOS of a laptop that the OS was compatible with linux to prevent the cooling fans from running continuously (especially on older Tosiba Laptops)... have you tried using acpi=off? ...and what is this on?

[neonman123]

I see that now, but no-where do I see what video chipset it "is: using for that. There is an easier way to find out --> run hwinfo --framebuffer and post the reselsults here. Remember to highlight the results and press the "#" button to enclose is in code tags.



> hal.1: read hal dataprocess 2253: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.il6towt04X5
Hardware Class: framebuffer
Model: "Intel(r) 82945GM Chipset Family Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r) 82945GM Chipset Family Graphics Controller"
SubVendor: "Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 704 kB
Memory Range: 0xd0000000-0xd07affff (rw)
Mode 0x033c: 1920x1440 (+1920), 8 bits
Mode 0x034d: 1920x1440 (+3840), 16 bits
Mode 0x033a: 1600x1200 (+1600), 8 bits
Mode 0x034b: 1600x1200 (+3200), 16 bits
Mode 0x035a: 1600x1200 (+6400), 24 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

[emerick7]

acpi_osi=Linux was generally a workaround the tell the BIOS of a laptop that the OS was compatible with linux to prevent the cooling fans from running continuously (especially on older Tosiba Laptops)... have you tried using acpi=off? ...and what is this on?

acpi=off has the same effect of hanging on the splash screen. This is an HP/Compaq tc4200.

(For a sec I thought it was working... the splash screen was working while it was checking disks for errors, but froze when that was finished...)

[MAFoElffen]

> hal.1: read hal dataprocess 2253: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.il6towt04X5
Hardware Class: framebuffer
Model: "Intel(r) 82945GM Chipset Family Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r) 82945GM Chipset Family Graphics Controller"
SubVendor: "Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 704 kB
Memory Range: 0xd0000000-0xd07affff (rw)
Mode 0x033c: 1920x1440 (+1920), 8 bits # 828
Mode 0x034d: 1920x1440 (+3840), 16 bits # 845
Mode 0x033a: 1600x1200 (+1600), 8 bits # 826
Mode 0x034b: 1600x1200 (+3200), 16 bits # 843
Mode 0x035a: 1600x1200 (+6400), 24 bits # 858
Mode 0x0307: 1280x1024 (+1280), 8 bits # 775
Mode 0x031a: 1280x1024 (+2560), 16 bits # 794
Mode 0x031b: 1280x1024 (+5120), 24 bits # 795
Mode 0x0305: 1024x768 (+1024), 8 bits # 773
Mode 0x0317: 1024x768 (+2048), 16 bits # 791
Mode 0x0318: 1024x768 (+4096), 24 bits # 792
Mode 0x0312: 640x480 (+2560), 24 bits # 786
Mode 0x0314: 800x600 (+1600), 16 bits # 788
Mode 0x0315: 800x600 (+3200), 24 bits # 789
Mode 0x0301: 640x480 (+640), 8 bits # 769
Mode 0x0303: 800x600 (+832), 8 bits # 771
Mode 0x0311: 640x480 (+1280), 16 bits # 785
Config Status: cfg=new, avail=yes, need=no, active=unknown

So... The above in blue is your Video. The results hwinfo returned is in green and is in hex format. The numbers in red to the right of each mode, is the decimal equivalent to each (hex) mode, which you could use to set the kms in the kernel boot line by adding/using a vga=xxx, where xxx is that decimal mode...

For example, adding vga=791 to the kernel boot line would try to set the graphics mode at 1024x768x16...

You have a little more of a challenge... That is the modes that your video display chipset is capable of displaying, but... You are going through your Svideo port to a TV. You have to find a display mode your TV supports. I know I connect my media server to a 37" TV to play videos and network series rewinds... and the highest resolution my TV itself supports is 1024x769x24. You're going to have to remember or find what works for yours.

[MAFoElffen]

I'm getting sudo:hwinfo:command not found when I type sudo hwinfo or sudo hwinfo --framebuffer or sudo hwinfo --framebuffer | more
Sorry, sometimes I aasume everyone has it installed...
You can easily install it via


sudo apt-get install hwinfo

[MAFoElffen]

acpi=off has the same effect of hanging on the splash screen. This is an HP/Compaq tc4200.

(For a sec I thought it was working... the splash screen was working while it was checking disks for errors, but froze when that was finished...)
Leave the boot line how you had it before the last post and edit /etc/default/grub as per this Launchpad Bug workaround:

Andy Whitcroft (https://launchpad.net/%7Eapw) wrote on 2010-12-02:

As a work-around we can turn this off by adding the line below to /etc/default/grub and running update-grub:
GRUB_GFXPAYLOAD_LINUX=text
that is supposed to work for your hardware. Latter updates after that, fixed it for some, but not for others, so it is still an open bug. The "workaround" might help you in the meanwhile.

Seems the open bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683775

Is one that you might what to join in on and follow...

[alleseter86]

After rebooting black screen, nothing worked, grub menu did not work,but when I closed the lid of my netbook and opened it again after a few minutes, screen worked perfectly, so did ubuntu 11.04 :)

I hope this helps!

I have a samsung N120 with Intel graphic card

[neonman123]

So... The above in blue is your Video. The results hwinfo returned is in green and is in hex format. The numbers in red to the right of each mode, is the decimal equivalent to each (hex) mode, which you could use to set the kms in the kernel boot line by adding/using a vga=xxx, where xxx is that decimal mode...

For example, adding vga=791 to the kernel boot line would try to set the graphics mode at 1024x768x16...

You have a little more of a challenge... That is the modes that your video display chipset is capable of displaying, but... You are going through your Svideo port to a TV. You have to find a display mode your TV supports. I know I connect my media server to a 37" TV to play videos and network series rewinds... and the highest resolution my TV itself supports is 1024x769x24. You're going to have to remember or find what works for yours.

wow that was a fast response, I've been trying to change these settings but cannot boot straight into the grub menu (just goes straight to gui) is there a way to edit the kernal boot throught the gui? I've been searching but nothing I find seems to work. it is an old tv so it should be 786, 785, or 769

[MAFoElffen]

wow that was a fast response, I've been trying to change these settings but cannot boot straight into the grub menu (just goes straight to gui) is there a way to edit the kernal boot throught the gui? I've been searching but nothing I find seems to work. it is an old tv so it should be 786, 785, or 769
The files are set to root previledges, so to edit them, you going to have to start a terminal:


cd /boot/grub/grub.cfg
sudo gedit /boot/grub/grub.cfg
...If you remember to save a copy of it in your home directory somewhere, as everytime you ran update-grub (or any grub update) it would overwrite it.

So find "/etc/default/grub"


cd /etc/default/
sudo gedit grub

and edit the line:


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=786"

Doing it this way will pick up the edits each time update-grub is run... So update the grub.cfg now via


sudo update-grub

to pick up these changes.

For trying new modes... you should be able to bring up the Grub menu by pressing the shift key a few times as it's booting up...

[emerick7]

No dice with GRUB_GFXPAYLOAD_LINUX=text. Any other ideas or am I getting near the end of the road? I'd rather not quit and reload with 10.10 now if you or others have ideas, but let me know if I'm at the point where that's my only option.

Can you tell if my issue is related to this bug? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/727594

[MAFoElffen]

No dice with GRUB_GFXPAYLOAD_LINUX=text. Any other ideas or am I getting near the end of the road? I'd rather not quit and reload with 10.10 now if you or others have ideas, but let me know if I'm at the point where that's my only option.

Can you tell if my issue is related to this bug? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/727594 Yes, and it seems to be older and the umbrella of other i915 duplicate bugs.

One more thing I ca think of-- Add this to you kernel boot line and try it (really reaching here from another "somewhat" related problem):


vmalloc=192MB

[neonman123]

The files are set to root previledges, so to edit them, you going to have to start a terminal:


cd /boot/grub/grub.cfg
sudo gedit /boot/grub/grub.cfg
...If you remember to save a copy of it in your home directory somewhere, as everytime you ran update-grub (or any grub update) it would overwrite it.

So find "/etc/default/grub"


cd /etc/default/
sudo gedit grub
and edit the line:


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=786"
Doing it this way will pick up the edits each time update-grub is run... So update the grub.cfg now via


sudo update-grub
to pick up these changes.

For trying new modes... you should be able to bring up the Grub menu by pressing the shift key a few times as it's booting up...

ok I did the edit to the grub file and it did change the resolution on the vga monitor, but did not help with s-video output. it's not actually outputting anything to s-video with vga plugged in, and with s-video only pluged in it gives a brief signal at the purple splash screen but I don't get the ubuntu logo and it stops any output again. now i did find out that if i hold shift on boot and select the previous version of linux it will output to s-video and vga at the same time just fine.

[MAFoElffen]

ok I did the edit to the grub file and it did change the resolution on the vga monitor, but did not help with s-video output. it's not actually outputting anything to s-video with vga plugged in, and with s-video only pluged in it gives a brief signal at the purple splash screen but I don't get the ubuntu logo and it stops any output again. now i did find out that if i hold shift on boot and select the previous version of linux it will output to s-video and vga at the same time just fine.
Hmm... So that may be related to a similar kernel problem that "taygan" was having here:

First of all, THANK YOU SO MUCH for an excellent troubleshooting thread. It helped me isolate my problem.

Clean install Natty 11.02 on a Gateway M-1625 with a ATI Radeon x1270 (RS690M). Note that this Radeon is no longer supported by fglrx (ATI Catalyst). After pulling my hair out for 24 hours, and trying every combination on the grub menu, I finally fixed my "blinking cursor/blank screen/fixing recursive fault but reboot is required" by downgrading the kernel to 2.6.37

First, the USB stick live desktop i386 booted to Unity fine, but Unity won't run installed (no 3D graphics??) - guess that's another issue. Next I tried installing over my 10.10 partition. It booted to rescue (recovery?) and low graphics most of the time. I thought it was a bad install so I formatted the partition and did a CLEAN install of Natty 11.04.

Grub always boots fine, it was hanging/black screen/sometimes blinking cursor after selecting the kernel. I tried many many combinations on the kernel boot line (pressing e from the grub menu): deleting everything ("quiet" "splash" and the "vt...7" thing) on the line after "ro" and trying different options (I always used "nosplash" to see what was going on - remember don't use the " when using options - it's just for reading clarity)

"nosplash text" + "nomodeset" or "radeon.modeset=0" or "xforcevesa" would SOMETIMES work, but would often hang at "fixing recursive fault but restart is needed" Other times it would hang after 3 lines, or after a few screenfuls, depending on the options, and sometimes changing with the SAME options. Grrr...

Finally, it looks like acpi is mucking things up with the latest kernel for me: The options "ro acpi=off nosplash text" can consistently get me booted to a terminal. Then from the terminal "sudo service start gdm" gets to the gdm logon screen. On the logon screen I must choose "classic (no effects)" and then I can get to gnome.

From there I downloaded the older kernel and installed it from the .debs found in the Ubuntu Kernel Mainline PPA,

If I select "older Linux Kernels" (I think that's what it says) from the grub menu and boot to 2.6.37 everything seems to work fine.

Older debs found here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.37.6-natty/)

for 32-bit i386 download and install in this order:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706_2.6.37-02063706.201103281005_all.deb (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706_2.6.37-02063706.201103281005_all.deb)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.37.6-natty/linux-headers-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37.6-natty/linux-image-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.37.6-natty/linux-image-2.6.37-02063706-generic_2.6.37-02063706.201103281005_i386.deb)

if you're running amd64, be sure to download the headers-all, headers-amd64, and image-amd64 - but I don't know if this workaround is needed with the 64-bit kernel.

Be sure to install (click on) the .debs in order: headers-all, headers-i386(amd64), and image-i386(amd64)!

Thanks to this blog post for the inspiration:

http://www.khattam.info/howto-install-linux-kernel-2-6-36-or-2-6-37-in-debian-squeeze-testing-or-ubuntu-or-any-debian-based-distribution-without-compiling-2010-11-13.html
So Installing an earliar version of the kernel as he described (above) my help you... If you need the debs for the AMD64 / 64bit kernel debs... let me now and I'll post them.

[emerick7]

Unfortunately, vmalloc=192MB didn't work.

[pssturges]

LOL- Okay... I'll edit the first post today. Look for those additions/changes there fist post.

I will add some more "basic" explanations and examples. Someone told me it was on the verge of a geek-alert... Mmeaning it was fine as a highly technical article, but the technical level was in reality, a bit high for a new comer.. I'll try to broaden that level.

Most of it ws fine for me just a few clarrifications needed here and there.

After struggling with this for the best part of 2 days, I've finally made some progress, however small.

Even with the revised changes to the kernel boot line you suggested, I couldn't even get into text mode. This particular system is a laptop with nvidia 8600m GS graphics. I eventually booted it with an external monitor connected and it boots into a console pretty much whatever I put in grub. The output is displayed on the laptop screen only. It just seems to need be connected to a monitor to force it into some other mode or something.

Anyhow, nvidia-current is already installed and I have created an xorg.conf. When I try to start gdm i get "gdm start/running, process 2591" then it quickly returns to the command prompt.

Below is the output from "hwinfo --framebuffer":



02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.04O_qA0Mq31
Hardware Class: framebuffer
Model: "NVIDIA G86 Board - e416h01 "
Vendor: "NVIDIA Corporation"
Device: "G86 Board - e416h01 "
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 14 MB
Memory Range: 0xcd000000-0xcddfffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Mode 0x0349: 1400x1050 (+5600), 24 bits
Mode 0x034a: 1600x1200 (+6400), 24 bits
Mode 0x0352: 2048x1536 (+8192), 24 bits
Mode 0x0360: 1280x800 (+1280), 8 bits
Mode 0x0361: 1280x800 (+5120), 24 bits
Mode 0x0362: 768x480 (+768), 8 bits
Mode 0x0364: 1440x900 (+1440), 8 bits
Mode 0x0365: 1440x900 (+5760), 24 bits
Mode 0x0368: 1680x1050 (+1680), 8 bits
Mode 0x0369: 1680x1050 (+6720), 24 bits
Mode 0x037c: 1920x1200 (+1920), 8 bits
Mode 0x037d: 1920x1200 (+7680), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown



I'm not really sure where to go from here.
Any help would be much appreciated.

Thanks
phil

[neonman123]

Hmm... So that may be related to a similar kernel problem that "taygan" was having here:

So Installing an earliar version of the kernel as he described (above) my help you... If you need the debs for the AMD64 / 64bit kernel debs... let me now and I'll post them.

I'm experiencing the same issue with that earlier version as well, the kernel that does work for me is 2.6.35-28 is there a way to just make that load by default for right now?

[drymnfr]

Upgraded from 10.10 to 11.04 on Friday. Screen went black on reboot.

Previous versions(for example: 2.6.35-28 ) would boot up fine.

Dell Latitude D630
Graphics card: NVIDIA Quadro NVS 135M

Thanks to all the suggestions, after 2 days of trying different things suggested in this thread, I finally got my system to boot with 2.6.38-8.

1) changed /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="acpi=off splash"
and subsequently ran

sudo update-grub

I haven't checked Unity desktop yet, but Gnome desktop is working normally as before.

[danealle]

i cannot even go to grub menu.. my screen just flicker switching from terminal to blank each seconds.. what to do.?
the only key combination it recognises is <ctrl>+<alt>+<del>
my laptop (vaio E series) uses ATI radeon which works previously on 10.10, with 4 Gb of ram..
using i5..
i uses ubuntu, like 2 month maybe..

[itsbatmansilly]

so i tried to upgrade from the last version to the current 11.04

made a live usb, and it worked flawlessly whilst booting from usb

install seemed to go well

now when i boot from HDD i get splash screen, log in to my user account as usual, then all hell breaks loose

generic ubuntu background occasinally interupted with flashing boxes of text, that seem to be various upgrade requests, etc but no desktop, nothing as far as hot keys working blah

again, running 11.04 off of live usb is working fine.

wtf? lol any ideas for this total idiot?

[MAFoElffen]

Most of it ws fine for me just a few clarrifications needed here and there.

After struggling with this for the best part of 2 days, I've finally made some progress, however small.

Even with the revised changes to the kernel boot line you suggested, I couldn't even get into text mode. This particular system is a laptop with nvidia 8600m GS graphics. I eventually booted it with an external monitor connected and it boots into a console pretty much whatever I put in grub. The output is displayed on the laptop screen only. It just seems to need be connected to a monitor to force it into some other mode or something.

Anyhow, nvidia-current is already installed and I have created an xorg.conf. When I try to start gdm i get "gdm start/running, process 2591" then it quickly returns to the command prompt.

Below is the output from "hwinfo --framebuffer":



02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.04O_qA0Mq31
Hardware Class: framebuffer
Model: "NVIDIA G86 Board - e416h01 "
Vendor: "NVIDIA Corporation"
Device: "G86 Board - e416h01 "
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 14 MB
Memory Range: 0xcd000000-0xcddfffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Mode 0x0349: 1400x1050 (+5600), 24 bits
Mode 0x034a: 1600x1200 (+6400), 24 bits
Mode 0x0352: 2048x1536 (+8192), 24 bits
Mode 0x0360: 1280x800 (+1280), 8 bits
Mode 0x0361: 1280x800 (+5120), 24 bits
Mode 0x0362: 768x480 (+768), 8 bits
Mode 0x0364: 1440x900 (+1440), 8 bits
Mode 0x0365: 1440x900 (+5760), 24 bits
Mode 0x0368: 1680x1050 (+1680), 8 bits
Mode 0x0369: 1680x1050 (+6720), 24 bits
Mode 0x037c: 1920x1200 (+1920), 8 bits
Mode 0x037d: 1920x1200 (+7680), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

I'm not really sure where to go from here.
Any help would be much appreciated.

Thanks
phil
Hmm. I know this chip was Ubuntu challenged until about a little over a year ago when they made some driver changes, but has been fine since then, through the 195 series of drivers.

NVidia 8600 graphics on which/what kind of laptop? Laptop's add a few more variables such as "backlighting." I have quite a few various nvidia cards here and I've always had a liking for their chipdets. What I've noticed on them is that from the start "nomodeset" usually turns off KVM long enough to get the nVidia drvers loaded...

Please post your xorg.conf and your ~/.xsession.errors and we'll see what may be going on.

[MAFoElffen]

Upgraded from 10.10 to 11.04 on Friday. Screen went black on reboot.

Previous versions(for example: 2.6.35-28 ) would boot up fine.

Dell Latitude D630
Graphics card: NVIDIA Quadro NVS 135M

Thanks to all the suggestions, after 2 days of trying different things suggested in this thread, I finally got my system to boot with 2.6.38-8.

1) changed /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="acpi=off splash"and subsequently ran

sudo update-grubI haven't checked Unity desktop yet, but Gnome desktop is working normally as before.
This "is" a good thing.

[MAFoElffen]

I'm experiencing the same issue with that earlier version as well, the kernel that does work for me is 2.6.35-28 is there a way to just make that load by default for right now?
YES--


sudo apt-get install startup-manager
This program will install and running it will allow you to "pick" whatever you want to run as the "first" or "default" startup option.

REALLY IMPORTANT AND A FAVOR TO US ALL
For those of you who's PC was only fixed by rolling back your kernels back from 2.6.38.x to 2.6.37.x (or earlier)... Please do "us" all a big favor and Submit this "BUG" to Launchpad!!!! PLEASE?

"I" see this as a big bug. It isn't up at Launchpad reported as any kind of a problem at the moment. If it isn't up at launch pad with some subscribers, It's not going to get noticed, nor fixed...

If you do report is up there, post the bug number here so others may subscribe to it to add support.

This goes for the "vmalloc=" / virtual memory allocation error... I can't report it because it isn't happening to me, but need those that it does affect to report it.

[MAFoElffen]

i cannot even go to grub menu.. my screen just flicker switching from terminal to blank each seconds.. what to do.?
the only key combination it recognises is <ctrl>+<alt>+<del>
my laptop (vaio E series) uses ATI radeon which works previously on 10.10, with 4 Gb of ram..
using i5..
i uses ubuntu, like 2 month maybe..
@danealle

1. What pc do you have with what kind of Graphics?
2. Was your install/upgrade of 11.04 a distribution upgrade from 10.10 to 11.04 or from a LiveCD?
3. Do you have a 11.04 LiveCD and does it boot on your PC?
4. Is Ubuntu the only operating system on your PC?

[MAFoElffen]

so i tried to upgrade from the last version to the current 11.04

made a live usb, and it worked flawlessly whilst booting from usb

install seemed to go well

now when i boot from HDD i get splash screen, log in to my user account as usual, then all hell breaks loose

generic ubuntu background occasinally interupted with flashing boxes of text, that seem to be various upgrade requests, etc but no desktop, nothing as far as hot keys working blah

again, running 11.04 off of live usb is working fine.

wtf? lol any ideas for this total idiot?
What is your PC and what graphics card does it have?

[1Nyco1]

This problem with nvidia video drivers is plaguing so many who upgraded to 11.04 I've tried deleting & reinstalling both drivers (in sequence) to no avail. I can get my programs to appear in 1360X768 resolution, but not in any other. I've scanned dozens of posts on Ubuntuforums & other sites about this. No solutions are working, but a bug report has been filed (Medium importance!). There are several extremely complicated recipes posted. None work and most result in other functional problems. And it's affected several other popular graphics chips.
Hey, I'm not a programmer. I've used Ubuntu for two years and loved it. I've recommended it to many of my friends & colleagues. I deeply resent Cannonical releasing a major upgrade with a serious flaw. There are thousands of Ubuntu users who cannot use their computers because of this highly touted "upgrade". GET IT FIXED! Linux/Ubuntu's reputation for device driver problems will be further degraded the longer this goes on. If you want to gain user base with casual Windows users this is NOT the way to do it.

[emerick7]

acpi=off splash did not work for me. Did you have any other settings modified, or what that the only line you changed?

[malapica]

I'm completely new to Linux world. Never tried it before.
And today I have decided to try it.

Downloaded 11.04 iso, burned it....and....nothing...

I boot from DVD and get to menu where I am asked to choose between "try it..." and "install" (also I can choose language)

I choose to try it.

Shortly after that I'm presented with black screen, some music and mouse pointer that I am able to move around. Nothing more, nothing less...

So I try your advice to press "e" when in that menu...but only thing that it does is selecting first language that starts with e in the list.

What are my options?
I think of myself to be very skilled in windows...but with Linux I'm completely lost :(

I would really like to try Linux...

My laptop is Toshiba Satellite M40-184 G3

And yeah...why would you put 11.04 onto your site when it has that sort of problems? How will that persuade someone in diving into Linux world?

I like the penguin guy...

Thanks!

[MAFoElffen]

acpi=off splash did not work for me. Did you have any other settings modified, or what that the only line you changed?
I forget, have you tried adding


acpi_osi="Linux"

If the acpi=off or noacpi didn't work, remove it.

[taygan]

acpi=off splash did not work for me. Did you have any other settings modified, or what that the only line you changed?

try "nosplash" instead of "splash" to see what else is going on.

[taygan]

downgrade/acpi=off workaround filed as a launchpad bug:

"Natty 11.04 crashes on startup: acpi=off OR downgrading to Kernel 2.6.37 allows boot."

https://bugs.launchpad.net/ubuntu/+bug/775899

[MAFoElffen]

I'm completely new to Linux world. Never tried it before.
And today I have decided to try it.

Downloaded 11.04 iso, burned it....and....nothing...

I boot from DVD and get to menu where I am asked to choose between "try it..." and "install" (also I can choose language)

I choose to try it.

Shortly after that I'm presented with black screen, some music and mouse pointer that I am able to move around. Nothing more, nothing less...

So I try your advice to press "e" when in that menu...but only thing that it does is selecting first language that starts with e in the list.

What are my options?
I think of myself to be very skilled in windows...but with Linux I'm completely lost :(

I would really like to try Linux...

My laptop is Toshiba Satellite M40-184 G3

And yeah...why would you put 11.04 onto your site when it has that sort of problems? How will that persuade someone in diving into Linux world?

I like the penguin guy...

Thanks!Welcome.

My disclaimer- I don't work for or get any kind of ben'ies from Conical. I am just an enthusiastic Ubuntu User with a little time on my hands. People here have helped me in the past and I am here to pass that along. That is what "Community Support" is all about.

Like I said before, once Ubuntu is set up... Out of all the Operating System I "have" to use, try, test, develop on-and-for > Ubuntu is where I live and spend most of my time (by choice). Does it work on all equipment out-of-the-box on all equipment combinations? It's trying it's honest best. (Just imagine all the combinations it's trying to cover...)

Saying that:
At the screen you described (Try/Instal...) Press <F6> which will present you with additional boot options. The one you want to try with your hardware should be the one with "nomodeset".

Tell me if it works for you.

[MAFoElffen]

I'm completely new to Linux world. Never tried it before.
And today I have decided to try it.

Downloaded 11.04 iso, burned it....and....nothing...

I boot from DVD and get to menu where I am asked to choose between "try it..." and "install" (also I can choose language)

I choose to try it.

Shortly after that I'm presented with black screen, some music and mouse pointer that I am able to move around. Nothing more, nothing less...

So I try your advice to press "e" when in that menu...but only thing that it does is selecting first language that starts with e in the list.

What are my options?
I think of myself to be very skilled in windows...but with Linux I'm completely lost :(

I would really like to try Linux...

My laptop is Toshiba Satellite M40-184 G3

And yeah...why would you put 11.04 onto your site when it has that sort of problems? How will that persuade someone in diving into Linux world?

I like the penguin guy...

Thanks!Welcome.

My disclaimer- I don't work for or get any kind of ben'ies from Conical. I am just an enthusiastic Ubuntu User with a little time on my hands. People here have helped me in the past and I am here to pass that along. That is what "Community Support" is all about.

Like I said before, once Ubuntu is set up... Out of all the Operating System I "have" to use, try, test, develop on-and-for > Ubuntu is where I live and spend most of my time (by choice). Does it work on all equipment out-of-the-box on all equipment combinations? It's trying it's honest best. (Just imagine all the combinations it's trying to cover...)

Saying that:
At the screen you described (Try/Install...) Press <F6> which will present you with additional boot options. The one you want to try with your hardware should be the one with "nomodeset".

Tell me if it works for you.

[HalvorOslo]

Instead of trying to read any of the information you provide, which surely would only lead me into a headache, I'll simply ask whether I could solve the problem that I now have by simply doing a reinstall?

I'll describe the symptoms.

1. I was not in an upgrade situation when the issue manifested. I was simply restarting the pc for some ordinary reason.

2. When I came to the graphical logon screen, it was changed. I'm ucsing 10.04.1 (I think) and build 2.6.32.31. Instead of the "soft" purplish look it now had a "hard" (like Windows 3.1) look, a black background, a grey box with a blue pc icon at the top, and the default user box had an "air force blue" background.

3. What happens when I enter the usual password is that either the logon screen comes back, or I hear the three rapid tamtam drum sounds and I'm in the black.

I googled "ubuntu terminal reinstall" and I have tried a few commands that didn't help me any (sudo apt-get dist-upgrade, sudo apt-get install -f, sudo dpkg-reconfigure -phigh -a)

Now, either can someone tell me how I fix this, btw. I'm on a communal pc that is really BAD, but noone in charge bothers to fix it. (That's why I installed ubuntu on it in the first place - it had only Windows XP Pro.) Or could my initial request solve the problem, i.e. would the appropriate command to do a reinstall perhaps solve the problem? If so, what is that command?

I could also mention that not too long after the most recent upgrade of build ubuntu started to drop out of its gui displaying a series of messages that didn't make any sense to me (one about PulseAudio, I don't remember the others). For the many weeks that this has been occurring (several times a day) I have simply dealt with it by hitting ctrl-alt-del repeatedly until it reboots.

[malapica]

Saying that:
At the screen you described (Try/Install...) Press <F6> which will present you with additional boot options. The one you want to try with your hardware should be the one with "nomodeset".

Tell me if it works for you.


Nothing happens when I press F6 :(

I've noticed "System Settings" when I click that upper right power button (along side with Suspend, Restart and Shut down)

[MAFoElffen]

Nothing happens when I press F6 :(

I've noticed "System Settings" when I click that upper right power button (along side with Suspend, Restart and Shut down)
I'm trying to imagine just what screen you are at. If it is asking for a keyboard, press the <esc> key fist.
This thread should help you get to the right screen you want on the LiveCD:
https://help.ubuntu.com/community/LiveCDBootOptions

[MAFoElffen]

Instead of trying to read any of the information you provide, which surely would only lead me into a headache, I'll simply ask whether I could solve the problem that I now have by simply doing a reinstall?

I'll describe the symptoms.

1. I was not in an upgrade situation when the issue manifested. I was simply restarting the pc for some ordinary reason.

2. When I came to the graphical logon screen, it was changed. I'm ucsing 10.04.1 (I think) and build 2.6.32.31. Instead of the "soft" purplish look it now had a "hard" (like Windows 3.1) look, a black background, a grey box with a blue pc icon at the top, and the default user box had an "air force blue" background.

3. What happens when I enter the usual password is that either the logon screen comes back, or I hear the three rapid tamtam drum sounds and I'm in the black.

I googled "ubuntu terminal reinstall" and I have tried a few commands that didn't help me any (sudo apt-get dist-upgrade, sudo apt-get install -f, sudo dpkg-reconfigure -phigh -a)

Now, either can someone tell me how I fix this, btw. I'm on a communal pc that is really BAD, but noone in charge bothers to fix it. (That's why I installed ubuntu on it in the first place - it had only Windows XP Pro.) Or could my initial request solve the problem, i.e. would the appropriate command to do a reinstall perhaps solve the problem? If so, what is that command?

I could also mention that not too long after the most recent upgrade of build ubuntu started to drop out of its gui displaying a series of messages that didn't make any sense to me (one about PulseAudio, I don't remember the others). For the many weeks that this has been occurring (several times a day) I have simply dealt with it by hitting ctrl-alt-del repeatedly until it reboots.
!. What is your hardware base, video card and monitor?
2. You said your are on 10.04? What version do you "want" to be on?

I am assuming that since the way you described it so far, that it is a 32bit install. Instead of reinstalling. You may be able to repair what is there. More info on what you have and were using is going to be needed or I'm just going to be guessing what is there.

[malapica]

I'm trying to imagine just what screen you are at. If it is asking for a keyboard, press the <esc> key fist.
This thread should help you get to the right screen you want on the LiveCD:
https://help.ubuntu.com/community/LiveCDBootOptions

This is the screen:
http://www.ubuntu.com/sites/www.ubuntu.com/files/active/natty/01-welcome.jpg

I choose my language and click "Try Ubuntu"... few moments after that i get black screen, welcome music, and mouse pointer that i'm able to move.

Hope this helps

[emerick7]

Neither acpi=off or acpi=Linux works, and nosplash doesn't seem to make a difference... same old black screen.

[pssturges]

Hmm. I know this chip was Ubuntu challenged until about a little over a year ago when they made some driver changes, but has been fine since then, through the 195 series of drivers.

NVidia 8600 graphics on which/what kind of laptop? Laptop's add a few more variables such as "backlighting." I have quite a few various nvidia cards here and I've always had a liking for their chipdets. What I've noticed on them is that from the start "nomodeset" usually turns off KVM long enough to get the nVidia drvers loaded...

Please post your xorg.conf and your ~/.xsession.errors and we'll see what may be going on.

First off thankyou very much for your ongoing help. It really is appreciated.

This is a medion akoya laptop. I've had it about 2 years and installed Ubuntu the first day I had it (probably 9.04ish). I had some wifi & audio driver issues but video was fine. I had similar problems to those I'm experiencing now when I upgraded to 10.10. At the time I didn't have the time or energy to persue a fix so I re-installed 10.04. With the release of 11.04, I thought I'd give it another go. I initially updated the machine to 10.10, which went smoothly and the machine booted properly. I then updated to 11.04 and came up with the black screen once again.

Anyhow, here's my xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 270.41.06 (buildmeister@swio-display-x86-rhel47-07.nvidia.com) Mon Apr 18 15:15:12 PDT 2011


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection



and my .xsession-errors:

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_AU.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
Xlib: extension "GLX" missing on display ":1".
Xlib: extension "GLX" missing on display ":1".
Xlib: extension "GLX" missing on display ":1".
Xlib: extension "GLX" missing on display ":1".
Xlib: extension "GLX" missing on display ":1".
Xlib: extension "GLX" missing on display ":1".
GNOME_KEYRING_CONTROL=/tmp/keyring-vCWsTU
GNOME_KEYRING_CONTROL=/tmp/keyring-vCWsTU
SSH_AUTH_SOCK=/tmp/keyring-vCWsTU/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-vCWsTU
SSH_AUTH_SOCK=/tmp/keyring-vCWsTU/ssh
30/04/2011 22:26:38 Autoprobing TCP port in (all) network interface
30/04/2011 22:26:38 Listening IPv6://[::]:5900
30/04/2011 22:26:38 Listening IPv4://0.0.0.0:5900
30/04/2011 22:26:38 Autoprobing selected port 5900
30/04/2011 22:26:38 Advertising security type: 'TLS' (18)
30/04/2011 22:26:38 Advertising authentication type: 'VNC Authentication' (2)
30/04/2011 22:26:38 Advertising security type: 'VNC Authentication' (2)
sendto: Network is unreachable
Starting Dropbox...Initializing nautilus-gdu extension
Initializing nautilus-dropbox 0.6.7
** (nm-applet:1663): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:1663): DEBUG: foo_client_state_changed_cb
/usr/lib/pymodules/python2.7/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)
Dropbox isn't running!
Done!
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.


** (process:1660): WARNING **: recent-manager-provider.vala:125: Desktop file for vlc was not found
** (process:1660): DEBUG: zeitgeist-datahub.vala:174: Inserting 15 events
** (nm-applet:1663): DEBUG: foo_client_state_changed_cb
** (process:1660): DEBUG: zeitgeist-datahub.vala:174: Inserting 1 events

** (gnome-settings-daemon:1611): WARNING **: Connection failed, reconnecting...
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
after 11 requests (11 known processed) with 0 events remaining.
ICE default IO error handler doing an exit(), pid = 1651, errno = 11

HP Linux Imaging and Printing System (ver. 3.11.1)
System Tray Status Service ver. 2.0

Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
dropbox: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
yelp: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
The application 'gnome-terminal' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
the application.
vino-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

** (process:1660): WARNING **: zeitgeist-datahub.vala:218: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
** (process:1660): DEBUG: zeitgeist-datahub.vala:58: Zeitgeist-daemon disappeared from the bus, exitting...
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

HP Linux Imaging and Printing System (ver. 3.11.1)
System Tray Status Service ver. 2.0

Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

xcb_connection_has_error() returned true
Window manager warning: Lost connection to the display ':1';
most likely the X server was shut down or you killed/destroyed
the window manager.


Thanks agin for your help,
Phil

[MAFoElffen]

acpi=Linux
Not "acpi=Linux" It's:


acpi_osi="Linux"

The only suggestion I have beyond that is too start trying earlier kernels (see end of first post).

[MAFoElffen]

This is the screen:
http://www.ubuntu.com/sites/www.ubuntu.com/files/active/natty/01-welcome.jpg




At that screen, instead of picking a language, press the <esc> key and it should get you to this screen:

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-Options.png

At this screen, it is a Grub Menu. Look at the lower right of the menu, where it says "F6 Other" Pressing <F6> will bring us this screen (below):

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other.png

Here (above) there is some of the most common boot up options, where you want to try "nomodeset"


If that doesn't work, if you press <F1> for help and while in the "help menu" pressed <F6> or <F7> you would be pressented with more common boot options. where you can select them with <enter> or <space> such as ...

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other-Manual.png

And when you press <esc> those entries are retaained and then you can edit them and boot or boot them as presented..

[emerick7]

Gotcha... still nothing though. I've tried about every scenario of all the suggestions that I can think of... none of the earlier kernels seem to work either.

Is there anything gdm-related I can try reloading?

If I'm outta options, is it possible to do a clean install of 10.10 via command-line? Or do I need to add it to a USB and load that way?

[MAFoElffen]

Gotcha... still nothing though. I've tried about every scenario of all the suggestions that I can think of... none of the earlier kernels seem to work either.

Is there anything gdm-related I can try reloading?


sudo apt-get ubuntu-desktop
sudo apt-get install -f # <-- which means to fix broken packages
sudo dpkg-reconfigure -phigh -a

[emerick7]

After

sudo apt-get install ubuntu-desktop -f
sudo dpkg-reconfigure -phigh -a
I got:


*Setting console screen modes and fonts
cron stop/waiting
dpkg-maintscript-helper: error: couldn't identify the package"

and then it stopped. Rebooted and the same black screen problem was happening.

[drymnfr]

acpi=off splash did not work for me. Did you have any other settings modified, or what that the only line you changed?

Sorry for the late response.

I did not have to change any other settings. I was slowly checking off all the suggestions recommended in this thread, for the black screen after reboot problem. The only thing that works for me is

acpi=off

The other related things i tried, but did not work for me, are:
pci=noacpi
acpi=noirq
irqpoll
noapic
acpi_osi="Linux"

Also, I checked and Unity desktop works fine as well.

Since I've added "acpi=off", the only problem I now have is that the system freezes on Shut Down. I have to press the power button to turn off. Restart option works fine. Everything else seems normal, wired network, wireless network, printing, etc all work fine.

[taygan]

Sorry for the late response.

I did not have to change any other settings. I was slowly checking off all the suggestions recommended in this thread, for the black screen after reboot problem. The only thing that works for me is

acpi=off

The other related things i tried, but did not work for me, are:
pci=noacpi
acpi=noirq
irqpoll
noapic
acpi_osi="Linux"

Also, I checked and Unity desktop works fine as well.

Since I've added "acpi=off", the only problem I now have is that the system freezes on Shut Down. I have to press the power button to turn off. Restart option works fine. Everything else seems normal, wired network, wireless network, printing, etc all work fine.

Just curious if you have the same problem I do. Have you tried installing the older kernel?

[drymnfr]

Just curious if you have the same problem I do. Have you tried installing the older kernel?

My problems started only after a distribution upgrade from 10.10 to 11.04.

Previous kernels on my system include 2.6.35-28, 2.6.32-25, 2.6.31-21 etc., All these work fine, with or without "acpi=off".

It is for the most current 11.04 kernel 2.6.38-8 that needs the "acpi=off", or else it is the "black screen", which would happen right after I selected the kernel in grub.

[taygan]

My problems started only after a distribution upgrade from 10.10 to 11.04.

Previous kernels on my system include 2.6.35-28, 2.6.32-25, 2.6.31-21 etc., All these work fine, with or without "acpi=off".

It is for the most current 11.04 kernel 2.6.38-8 that needs the "acpi=off", or else it is the "black screen", which would happen right after I selected the kernel in grub.

Ah ha! Would you mind signing on to the bug I filed?

"Natty 11.04 crashes on startup: acpi=off OR downgrading to Kernel 2.6.37 allows boot."

https://bugs.launchpad.net/ubuntu/+bug/775899

Thanks!

[HalvorOslo]

!. What is your hardware base, video card and monitor?
2. You said your are on 10.04? What version do you "want" to be on?

I am assuming that since the way you described it so far, that it is a 32bit install. Instead of reinstalling. You may be able to repair what is there. More info on what you have and were using is going to be needed or I'm just going to be guessing what is there.

The processor is x86 Family 15 Model 2 Stepping 7 GenuineIntel ~1992MHz

Video Card: Intel(R) 82845G/GL/GE/PE/GV Graphics Controller

Monitor: Dell E772p

As for wanting to be on any specific version of Ubuntu I upgraded relatively recently from Hardy Heron and I have no wish to make any changes unless I'm told that would be beneficial.

[tattwood833]

Hello Hello,
This thread has been incredibly useful so far, and I think I am on the verge of a breakthrough.

So my system boots to a blank screen, a blank screen with a fully moving cursor.

I can <CTRL><ALT><F1> in to a terminal no problems.
I've been able to do a sudo apt-get update and upgrade no problems... so I am guessing the kernel loads and we have no problems there.

*THOUGHT* it was a graphics problem, so tried some of the grub edits suggested in the first post in the thread, not much joy there...

Although something that keeps coming up in every graphical situation I try:

chroot: etc/apparmor/initramfs : No such file or directory
Apparmor Profiles fail to load

or some such...

So this starts suggesting to me that it isn't a "Blank Screen" / Graphic issue at all, that I am missing some stuff - the apparmor stuff - but I don't know what that is?

Or indeed where to go and get it...

Any suggestions?

Thanks in advance


Tommy Tomato x

[malapica]

At that screen, instead of picking a language, press the <esc> key and it should get you to this screen:

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-Options.png

At this screen, it is a Grub Menu. Look at the lower right of the menu, where it says "F6 Other" Pressing <F6> will bring us this screen (below):

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other.png

Here (above) there is some of the most common boot up options, where you want to try "nomodeset"


If that doesn't work, if you press <F1> for help and while in the "help menu" pressed <F6> or <F7> you would be pressented with more common boot options. where you can select them with <enter> or <space> such as ...

https://help.ubuntu.com/community/LiveCDBootOptions?action=AttachFile&do=get&target=Boot-F6-Other-Manual.png

And when you press <esc> those entries are retaained and then you can edit them and boot or boot them as presented..

That does not work for me :( I cannot get to Grub menu...:confused:
When I press esc nothing happens...:confused::confused:

[malapica]

Pressing esc before that "Try Ubuntu" window helped :)

nomodeset worked for me...im in :D

thank you for your help and patience

one more question. If I decide to install Ubuntu I guess I will have to use same option. What does it mean in "long term". Do I need to install some drivers? do I miss anything using nomodeset?

Thanks!

[tattwood833]

so I've done some noodling about the apparmor stuff...
Although I don't really know what I'm doing.

I've done

sudo apt-get install apparmor-profiles

which looked like it was doing something and helping...:o

but then I still get

chroot: cannot execute etc/apparmor/initframs : no such file or directory:(

so I tried doing a sudo apt-get install initframs

worth a punt I thought, but that doesn't exist.. so no..

where do I go from here?:confused:

Thanks again for all your helps

Tommy Tomato x


Hello Hello,
This thread has been incredibly useful so far, and I think I am on the verge of a breakthrough.

So my system boots to a blank screen, a blank screen with a fully moving cursor.

I can <CTRL><ALT><F1> in to a terminal no problems.
I've been able to do a sudo apt-get update and upgrade no problems... so I am guessing the kernel loads and we have no problems there.

*THOUGHT* it was a graphics problem, so tried some of the grub edits suggested in the first post in the thread, not much joy there...

Although something that keeps coming up in every graphical situation I try:

chroot: etc/apparmor/initramfs : No such file or directory
Apparmor Profiles fail to load

or some such...

So this starts suggesting to me that it isn't a "Blank Screen" / Graphic issue at all, that I am missing some stuff - the apparmor stuff - but I don't know what that is?

Or indeed where to go and get it...

Any suggestions?

Thanks in advance


Tommy Tomato x

[danealle]

@danealle

1. What pc do you have with what kind of Graphics?
2. Was your install/upgrade of 11.04 a distribution upgrade from 10.10 to 11.04 or from a LiveCD?
3. Do you have a 11.04 LiveCD and does it boot on your PC?
4. Is Ubuntu the only operating system on your PC?

1-i uses sony vaio E series. i don't know what kind of graphics, but it worked perfectly with Ubuntu 10.10.
2-upgraded from update manager.
3-currently working on it, will keep you informed, thank you.:D
4-yes.

[danealle]

my live cd worked well for starters.. but after i downloaded additional drivers for my laptop,(ATI/AMDproprietary FGLRX graphics driver) the windows disappear.. there are only files, no windows at all.. so i pressed <ctrl><alt><del> to restart and same happen when i logged in ubuntu.. i tried logging in using classic ubuntu, the system is like ubuntu 10.10.. why is there no windows when log in ubuntu.?
P/s: 11.04 seems slower than 10.10..
i am considering to use 10.04 long term support.. is it wise.?

[MAFoElffen]

my live cd worked well for starters.. but after i downloaded additional drivers for my laptop,(ATI/AMDproprietary FGLRX graphics driver) the windows disappear.. there are only files, no windows at all.. so i pressed <ctrl><alt><del> to restart and same happen when i logged in ubuntu.. i tried logging in using classic ubuntu, the system is like ubuntu 10.10.. why is there no windows when log in ubuntu.?
P/s: 11.04 seems slower than 10.10..
i am considering to use 10.04 long term support.. is it wise.?
Assuming since you lost graphics by installing fglrx on ATI, that you fall into the ATI/fglrx bug that is going on...

Look near the end of the first post under the ATI notes for the script to uninstall the fglrx drivers... Somewhere said that these drivers "lost support for" with this version (so far) and running this script should/might get you back up.

[MAFoElffen]

so I've done some noodling about the apparmor stuff...
Although I don't really know what I'm doing.

I've done

sudo apt-get install apparmor-profiles

which looked like it was doing something and helping...:o

but then I still get

chroot: cannot execute etc/apparmor/initframs : no such file or directory:(

so I tried doing a sudo apt-get install initframs

worth a punt I thought, but that doesn't exist.. so no..

where do I go from here?:confused:

Thanks again for all your helps

Tommy Tomato x
I'm looking into and testing...

[MAFoElffen]

Sorry for the late response.

I did not have to change any other settings. I was slowly checking off all the suggestions recommended in this thread, for the black screen after reboot problem. The only thing that works for me is

acpi=offThe other related things i tried, but did not work for me, are:
pci=noacpi
acpi=noirq
irqpoll
noapic
acpi_osi="Linux"

Also, I checked and Unity desktop works fine as well.

Since I've added "acpi=off", the only problem I now have is that the system freezes on Shut Down. I have to press the power button to turn off. Restart option works fine. Everything else seems normal, wired network, wireless network, printing, etc all work fine.
noacpi or acpi=off <> Freeze On Wakeup from suspend, some freezes on shutdowns... YES.

If it works, there is a trade off. It is turning off all acpi calls. If we could figure out just what specific acpi call it was that was affecting it, then maybe...

I see this as a temporary work-around, but not as a fix. Yes, I see it as a possible kernel BUG just by with having to use it.

[HalvorOslo]

Instead of trying to read any of the information you provide, which surely would only lead me into a headache, I'll simply ask whether I could solve the problem that I now have by simply doing a reinstall?

I'll describe the symptoms.

1. I was not in an upgrade situation when the issue manifested. I was simply restarting the pc for some ordinary reason.

2. When I came to the graphical logon screen, it was changed. I'm ucsing 10.04.1 (I think) and build 2.6.32.31. Instead of the "soft" purplish look it now had a "hard" (like Windows 3.1) look, a black background, a grey box with a blue pc icon at the top, and the default user box had an "air force blue" background.

3. What happens when I enter the usual password is that either the logon screen comes back, or I hear the three rapid tamtam drum sounds and I'm in the black.

I googled "ubuntu terminal reinstall" and I have tried a few commands that didn't help me any (sudo apt-get dist-upgrade, sudo apt-get install -f, sudo dpkg-reconfigure -phigh -a)

Now, either can someone tell me how I fix this, btw. I'm on a communal pc that is really BAD, but noone in charge bothers to fix it. (That's why I installed ubuntu on it in the first place - it had only Windows XP Pro.) Or could my initial request solve the problem, i.e. would the appropriate command to do a reinstall perhaps solve the problem? If so, what is that command?

I could also mention that not too long after the most recent upgrade of build ubuntu started to drop out of its gui displaying a series of messages that didn't make any sense to me (one about PulseAudio, I don't remember the others). For the many weeks that this has been occurring (several times a day) I have simply dealt with it by hitting ctrl-alt-del repeatedly until it reboots.

The processor is x86 Family 15 Model 2 Stepping 7 GenuineIntel ~1992MHz

Video Card: Intel(R) 82845G/GL/GE/PE/GV Graphics Controller

Monitor: Dell E772p

[emerick7]

@MAFoElffen: Any other suggestions for me to try?

[jfhopkin]

I think "grub-update" in the instructions should be "update-grub"? Or is that something else?

[MAFoElffen]

@MAFoElffen: Any other suggestions for me to try?
I had an idea... it was untested, but an idea none the less.

I was working working on how to roll back just the GDM (itself) from the commandline... I did it. That was a mistake and waste of time. Then I looked at implementing specific graphical services within the kernel... It got to specific as per what services got implemented (for certain chipsets).

After chasing ghost with that all day... Looks like there are many current gnome updates tonight to fix various things, so...

From the tty text console, you can get these updates and (others) via:


sudo apt-get update
sudo apt-get upgrade

And see if these gnome updates helped in any way...

[MAFoElffen]

I think "grub-update" in the instructions should be "update-grub"? Or is that something else?
You are right. It is most likely my typo... But I need help to tell me where. I don't see that typo in the first three posts. Was is in a later post? (Which post # so I can correct...)

[fonsi2099]

Just the same problem!!! any solution or idea, Gurubunteros thanks,
Please make the 11.04 not to similar to windows, the first impressions are like Windows it's not working!!
Thanyk for any update that works for all, and not only for the newst Hardware and for gurus..
:guitar:

[gilch]

I have a AMD-64 computer.
nvidia (???)
I have been working for a couple of years on Ubuntu (10.10 worked fine). I upgraded to 11, and then it seems to work, but it was very "jerky" and slow.
Then something appeared somehow offering to upgrade something about my driver (It said "Recommended"). I did that.

When I rebooted, I could see some icons on the left and some things on the top of the screen, but the main screen was blank. I went to the top right and clicked where I thought restart should be and it worked and I could get out and sign in on my dual boot of Win 7, where I am now.

I need help ! ! !
Gilles

[MAFoElffen]

(Duplicate Post)

[MAFoElffen]

I have a AMD-64 computer.
nvidia (???)
I have been working for a couple of years on Ubuntu (10.10 worked fine). I upgraded to 11, and then it seems to work, but it was very "jerky" and slow.
Then something appeared somehow offering to upgrade something about my driver (It said "Recommended"). I did that.

When I rebooted, I could see some icons on the left and some things on the top of the screen, but the main screen was blank. I went to the top right and clicked where I thought restart should be and it worked and I could get out and sign in on my dual boot of Win 7, where I am now.

I need help ! ! !
Gilles
A couple things you should try.

First, reboot.
At the grub menu, select Ubuntu. >
At the Login screen, select your username. >
The password box will appear...
At the same time, there will be startup options that appear in the bar at the bottom of the screen, halfway across will be a pull-down box that will allow you to select Ubuntu, Ubuntu "Classic." Ubuntu Classic without affects... etc.
http://img59.imageshack.us/img59/8084/loginoptions.png
Select the Classic. The classic is the old, familiar gnome desktop.

Select it > type in your password and go on. It will remember and stay at whatever you selected last as the option.

When you do that, it will start Ubuntu without Unity. We want to see if it will display your graphics in that desktop... Narrowing down what might be wrong.

I'll stop there to get some feedback on what happened , so I don't throw a lot of things at you at once and lose you.

[MAFoElffen]

@gilch...

Seems that a few days ago there was an update to compiz where (depending when it updated) there might have been a probkem with dependencies in the package...



Let me repeat that. A required dependency for Unity was NOT installed during the upgrade. There were compiz-plugins installed, but the compiz and compiz-gnome packages were not installed.

Installed compiz. Logged out, logged in to "Ubuntu" session, and there's Unity. If I'm feeling like wasting more time on this I will remove the Radeon card and see if the problem was just that compiz was missing.

If one of the sessions I mentioned in the post previous works for you, you should be able to start up the Synaptic Package Manager > Search on "compiz" > Mark the package "compiz" for reinstallation > Apply/

That "may" fix your problem.

[gilch]

I did that, and I did get the familiar desktop, but only visible were the icons and text on top and bottom of the screen. Nothing showed in the big screen. It said there were updates available. I did ask for them, I could see them download as usual, but when it came to "Applying changes", that box stayed blank. It worked because after a while I got the message "System up to date". Then... back to Win7 where I am now.
(Thanks for helping, by the way; I know, I can only eat Pablum, a little bit at a time).
Gilles

[oceallaighm]

I just thought that I would post for information purposes.

Clean install of Ubuntu 11.04 X86_64 in dual boot configuration with Windows 7 64 bit.

Toshiba Laptop L300D-10Q AMD 64X2 Dual Core TK-57, 4GB Ram, 500GB HD, ATI Raedon X1200 Graphics card.

Installation successful and I get Grub loading giving both the Ubuntu and Windows options and the Memtest86 option as well.

First observation of Grub screen the white text and the border seem blurred, this was not the case with Grub in Ubuntu 10.10 or earlier.

I select Ubuntu to boot, the screen goes blank and there is no hard disk activity, (note Windows 7 boots successfully). CTRL+ALT+F1 seems to activate Grub/hard disk and Ubuntu 11.04 loads the GDM, from here if I select Ubuntu Classic (no effects) I can successfully log into Ubuntu 11.04. Once in everything seems to work.

So far I have not been able to establish what the problem is, whether it is with Grub or with X.org or perhaps even a kernel module issue?

Obviously as Ubuntu 11.04 starts successfully after CTRL+ALT+F1 there does not seem to be anything in the log files of use. And the only error I see is one about:-
radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [drm:drm_edid_block_valid] *ERROR* Raw EDID:
which I have been getting since Ubuntu 9.10 or 10.04 and I don't know why as I have no HDMI device or port attached?

I have been looking at the thread, a lot of it is beyond me.

[gilch]

A couple things you should try.

First, reboot.
At the grub menu, select Ubuntu. >
At the Login screen, select your username. >
The password box will appear...
At the same time, there will be startup options that appear in the bar at the bottom of the screen, halfway across will be a pull-down box that will allow you to select Ubuntu, Ubuntu "Classic." Ubuntu Classic without affects... etc.
http://img59.imageshack.us/img59/8084/loginoptions.png
Select the Classic. The classic is the old, familiar gnome desktop.

Select it > type in your password and go on. It will remember and stay at whatever you selected last as the option.

When you do that, it will start Ubuntu without Unity. We want to see if it will display your graphics in that desktop... Narrowing down what might be wrong.

I'll stop there to get some feedback on what happened , so I don't throw a lot of things at you at once and lose you.
I am not sure if my answer went to the right place. I had not Quoted your message. So I am trying again.

I did go to Classic Ubuntu, and I did get the familiar desktop, but only visible were the icons and text on top and bottom of the screen. Nothing showed in the big screen. It said there were updates available. I did ask for them, I could see them download as usual, but when it came to "Applying changes", that box stayed blank. It worked because after a while I got the message "System up to date". Then... back to Win7 where I am now.
(Thanks for helping, by the way; I know, I can only eat Pablum, a little bit at a time).
Gilles

[MAFoElffen]

I just thought that I would post for information purposes.

Clean install of Ubuntu 11.04 X86_64 in dual boot configuration with Windows 7 64 bit.

Toshiba Laptop L300D-10Q AMD 64X2 Dual Core TK-57, 4GB Ram, 500GB HD, ATI Raedon X1200 Graphics card.

Installation successful and I get Grub loading giving both the Ubuntu and Windows options and the Memtest86 option as well.

First observation of Grub screen the white text and the border seem blurred, this was not the case with Grub in Ubuntu 10.10 or earlier.

I select Ubuntu to boot, the screen goes blank and there is no hard disk activity, (note Windows 7 boots successfully). CTRL+ALT+F1 seems to activate Grub/hard disk and Ubuntu 11.04 loads the GDM, from here if I select Ubuntu Classic (no effects) I can successfully log into Ubuntu 11.04. Once in everything seems to work.

So far I have not been able to establish what the problem is, whether it is with Grub or with X.org or perhaps even a kernel module issue?

Obviously as Ubuntu 11.04 starts successfully after CTRL+ALT+F1 there does not seem to be anything in the log files of use. And the only error I see is one about:-
radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [drm:drm_edid_block_valid] *ERROR* Raw EDID:
which I have been getting since Ubuntu 9.10 or 10.04 and I don't know why as I have no HDMI device or port attached?

I have been looking at the thread, a lot of it is beyond me.

Your laptop has a ATI Radeon® X1250 for video. These instruction here might be the easiest for you:

Steps for ATI users:
1. When the boot hangs, press ctrl+alt+f1.
2. Login as user with root privileges.
3. Type "cd /usr/share/ati" and press enter.
4. Type "sudo sh ./fglrx-uninstall.sh" and press enter.
5. Type "sudo reboot".
Another thing would be to use the rescue mode to boot (at the grub menu) > pick the failsafe / low graphics mode, then install you "additional drivers" graphics driver for your ATI card.

Be aware that with your hardware, unfortunately, you just might fall into this Bug here:
https://bugs.launchpad.net/ubuntu/+bug/775899
If you do, follow the instructions in post 2.

[MAFoElffen]

I am not sure if my answer went to the right place. I had not Quoted your message. So I am trying again.

I did go to Classic Ubuntu, and I did get the familiar desktop, but only visible were the icons and text on top and bottom of the screen. Nothing showed in the big screen. It said there were updates available. I did ask for them, I could see them download as usual, but when it came to "Applying changes", that box stayed blank. It worked because after a while I got the message "System up to date". Then... back to Win7 where I am now.
(Thanks for helping, by the way; I know, I can only eat Pablum, a little bit at a time).
Gilles
In that case... Press <cntrl><alt><F1>
Enter your login/password
Type:


sudo apt-get update
sudo apt-get upgrade
sudo reboot

To install your updates and restart.

[oceallaighm]

Many thanks for you reply MAFoElffen.

In reverse order, the X1200/50 to the best of my knowledge is no longer supported by ATI's propriety drivers, support was discontinued in late 2008, early 2009. So, I can only use fglrx driver and have done successfully in the past 4 releases of Ubuntu. So a propriety driver is not an option.

If as suggested I remove the fglrx driver what will the system use? Note, once I hit CTRL+ALT+F1 Ubuntu goes straight to GDM not to a terminal login. Also, the desktop works, has the correct resolution and is stable as I run the applications.

The only issues are the black screen and the fact that I have to hit CTRL+ALT+F1 each time to get to GDM, not a problem I can do it, it is just a nuisance to have to, and yes it is slow to boot!

(Addition:) I have read through the thread in full and as far as my understanding goes, I think that I might need to revert to an earlier kernel say the 2.6.37.x as mentioned. How do I go about getting these, through back ports or PPA?

(Update:)
I enabled proposed updates in the repository and included was the 2.6.38-9 kernel, I took all of the updates and disabled the repository and restarted the laptop. Current position is that I can now boot from Grub and get to GDM without having to do CTRL+ALT+F1, however, alas in this game there is always an however, there is definitely a delay from when I hit enter on Grub to the monitor/screen being detected of about 28 secs, I then briefly get the Ubuntu image and 5 secs later I get GDM, so it now works, though it seems a lot slower to start than Ubuntu 10.10. I'll have a look at that later but unfortunately my 10.10 installation is now in an external usb chassis.

[gilch]

In that case... Press <cntrl><alt><F1>
Enter your login/password
Type:


sudo apt-get update
sudo apt-get upgrade
sudo reboot

To install your updates and restart.
Done that, except that Ctr Alt F1 did not work, but I could use Applications - Accessories - Terminal, and I gave the commands in terminal. It seemed to do what it was supposed to. I rebooted, and I was back to a totally blank screen this time, not even top line showing. So I had to power off, in order to get back to Win7.
Gilles

[skclewis]

I am having the same issue. I am using an Emachine E727 with the Intel Mobile 4 Series and GMA 4500M. I tried the suggestions in the posts and was able to get the desktop when I edited Grub to read nomodeset. However when I edited grub.conf to read the same nothing happens. I went to Bugzilla and opened a bug report #649521 under gdm. So if anyone having the same issue can post under that bug as suggested in this post.

[meddyuk]

Hiya, ive just upgraded to Natty Narwal, from Maverick. Maverick worked fine on my Desktop, however i dont seem to be able to boot properly with this current upgrade.

When booting up, my monitor displays "out of range - 1280 x 1024" and stays like that for a good 2 minutes. Then i get a blank screen. The grub doesnt run. I press shift multiple times but that doesnt do anything, it then boots up to the log in screen and i am able to log in.

I've just installed start up manager and selected 1260x765 and it sorted it. Grub is now there.

[jj97403]

1. 11.04
2. Dell
3. Inspiron 300m
4. No video after grub (usually), but recovery/low graphics mode works just fine.

Can I make low graphics mode "default" so I don't have to boot into recovery every time?

[MAFoElffen]

Many thanks for you reply MAFoElffen.

In reverse order, the X1200/50 to the best of my knowledge is no longer supported by ATI's propriety drivers, support was discontinued in late 2008, early 2009. So, I can only use fglrx driver and have done successfully in the past 4 releases of Ubuntu. So a propriety driver is not an option.

If as suggested I remove the fglrx driver what will the system use? Note, once I hit CTRL+ALT+F1 Ubuntu goes straight to GDM not to a terminal login. Also, the desktop works, has the correct resolution and is stable as I run the applications.

The only issues are the black screen and the fact that I have to hit CTRL+ALT+F1 each time to get to GDM, not a problem I can do it, it is just a nuisance to have to, and yes it is slow to boot!

(Addition:) I have read through the thread in full and as far as my understanding goes, I think that I might need to revert to an earlier kernel say the 2.6.37.x as mentioned. How do I go about getting these, through back ports or PPA?

(Update:)
I enabled proposed updates in the repository and included was the 2.6.38-9 kernel, I took all of the updates and disabled the repository and restarted the laptop. Current position is that I can now boot from Grub and get to GDM without having to do CTRL+ALT+F1, however, alas in this game there is always an however, there is definitely a delay from when I hit enter on Grub to the monitor/screen being detected of about 28 secs, I then briefly get the Ubuntu image and 5 secs later I get GDM, so it now works, though it seems a lot slower to start than Ubuntu 10.10. I'll have a look at that later but unfortunately my 10.10 installation is now in an external usb chassis.
ROTFLMAO! Well good. I was just trying to do KMS reseach... with emphasis on "trying"... when I saw your post. KMS ia very bleak on documentation anywhere that I can find so far. I can't seem to get anyone to talk about it from the dev area, the documentation team or the kernel team... But I did spent a few moments on the Kernel Team's blog to see that they are trying to get through 984 kernel bugs with natty!

That 28 second or longer delay when Natty boots?. As far as I can tell. I've noticed that has been somewhat normal since natty alpha2, at least when booting into Unity. With Ubuntu Classic, it seems to be fatser/less time. KMS was "supposed" to speed up the Xorg boot prcocess, then they throw some sand into it... nevermnid that. (Curious how Gnome 3.x is going to turn out.)

Happy to hear that the proposed kernel 2.6.38-9 worked out for you. If you look at this:


Please subscribre/join this Launchpad bug:
https://bugs.launchpad.net/ubuntu/+bug/775899
Because it sounds as you are affected by it, along with a few more from here:
http://ubuntuforums.org/showpost.php...6&postcount=60 (http://ubuntuforums.org/showpost.php?p=10758896&postcount=60)
The more peope affected we can get to join this bug, the more weight is going to be leveraged for them to fic it (hoping).

The instructions for rolling back to an earleir natty kernel are in this post:
http://ubuntuforums.org/showpost.php...9&postcount=23 (http://ubuntuforums.org/showpost.php?p=10751479&postcount=23)

The link for the kernel mainline ppa is here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/)
Follow the naming convention there for the natty kernels and whether i386 (32bit) or AMD64 (64bit) and follow the instructions in post 2. Basically, you would just click on and install the following .deb's in this order:
linux-headers-XXXXXX_all.deb
linux-headers-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)
linux-image-XXXXXX_i386.deb (if you have 64bit, choose amd64 version)

If you click on the link for that file and install in that order = success.
The above instructions also work to try out the kernels in the mainline ppo that are not released yet.- If you follow the mainline ppa's "link" above and follow those links to the kernel v2.6.39-rcx-natty, such as here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.39-rc4-natty/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.39-rc4-natty/)

Well, when we were testing Natty beta1 and beta2, some us were testing natty using the 2.6.39 release candidates (and loving it). We "were" told about a couple weeks before natty "released" that 2.6.39 was not planned to be released with Natty (11.04), but rather wait for Oneric (11.10)... but if it works for you , go for it.

Please ensure that you join the bug mentioned in this post (above), so that The LP Bug Team knows that it "affects" people and needs to be resolved.

[MAFoElffen]

I am having the same issue. I am using an Emachine E727 with the Intel Mobile 4 Series and GMA 4500M. I tried the suggestions in the posts and was able to get the desktop when I edited Grub to read nomodeset. However when I edited grub.conf to read the same nothing happens. I went to Bugzilla and opened a bug report #649521 under gdm. So if anyone having the same issue can post under that bug as suggested in this post.
So... what graphics does that have?
You said you changed the kernel boot line in Grub (on the fly) with "nomodeset" and it went successfully to a desktop... but you editted which file? Hint; Look near end of 1st post under "Making Changes Permanent"...


Now that I found something that works, how do I make it permanent?
In a terminal:


cd/etc/default sudo gedit grub
Edit the line "GRUB_CMDLINE_LINUX_DEFAULT". Add your new options, for example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
Now in a terminal run


sudo update-grub
Now each time you update grub and in configures the files, it will pick up these changes.
but going nomodeset, may only be a temporary change you might need to be able to install an additional driver, depending on what video hardware you have...

So again I ask- what video hardware do you have?

[MAFoElffen]

1. 11.04
2. Dell
3. Inspiron 300m
4. No video after grub (usually), but recovery/low graphics mode works just fine.

Can I make low graphics mode "default" so I don't have to boot into recovery every time?
Look at post 101: http://ubuntuforums.org/showpost.php?p=10772630&postcount=101
You could use safe mode (which is the low graphics mode).
It will remember your last choice.

I know that laptop has Intel graphics, but what does


sudo hwinfo --framebuffer
Or...


lspci -nn | grep VGA
show as your video chipset?

[ikt]

Does anyone have no problem with 32 bit 11.04 but issues with 64 bit 11.04?

[MAFoElffen]

Does anyone have no problem with 32 bit 11.04 but issues with 64 bit 11.04?
I'm running 3 i386 boxs and 2 AMD64 boxs. I am having less issues with the 32bit versions, but I also think that's got something to do with the hardware I'm using, the age and all the "pieces" in them.. My 32bit boxes are limited to that by hardware.

[drymnfr]

Thank you MAFoElffen and everyone else, for all your help.

Background:
If you remember, the only thing that worked for me before, was changing my /etc/default/grub with
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off quiet splash"

The problem I had after that was that the system freezes on Shut Down.


I kept troubleshooting. The only instructions I had not tried(from MAFoElffen's to do list) was the vga=xxx option, so I decided to try that today.

I got a list of mode numbers from here - http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers

Happy to say that a few of them worked for me and the best one is vga=824

The following line is now in my /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=824"

and subsequently ran


sudo update-grub

Everything is normal as before. No black screen after grub. Shutdown problems gone, obviously. All kernels, including 2.6.38-9, 2.6.38-8, 2.6.35-28 boot fine.

[MAFoElffen]

Thank you MAFoElffen and everyone else, for all your help.

Background:
If you remember, the only thing that worked for me before, was changing my /etc/default/grub with
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off quiet splash"

The problem I had after that was that the system freezes on Shut Down.
I kept troubleshooting. The only instructions I had not tried(from MAFoElffen's to do list) was the vga=xxx option, so I decided to try that today.

I got a list of mode numbers from here - http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers

Happy to say that a few of them worked for me and the best one is vga=824

The following line is now in my /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=824"and subsequently ran


sudo update-grubEverything is normal as before. No black screen after grub. Shutdown problems gone, obviously. All kernels, including 2.6.38-9, 2.6.38-8, 2.6.35-28 boot fine.
Wahoo!

That's why I specifically mention using "hwinfo --framebuffer" which will return the modes that "your" installed hardware says it supports. Less to have to try. The hardest part in that is converting the hex values to decimal to use in the " vga=xxx "

[neo9900]

I am also at an end to what to try.

I have a Alienware laptop running a Nvidia GTX 460M graphics card.

I do get the grub screen. The operating system does boot, but I get a black screen and I cannot change to another terminal either. The only way I can boot and see anything is with nomodeset.

I have been able to boot to command line using the text and nomodeset option. I then tried to install the Nvidia graphics via:

sudo apt-get install nvidia-current
sudo nvidia-xconfig

I would still get the black screen. So, I then downloaded the correct drivers from Nvidia's site and installed them at the command line. It appeared to work. It installed without any errors and said it uninstalled the old drivers. Still I get a black screen.

After the above step, I was unable to boot into gui mode at all with nomodeset. I went in and renamed the xorg.conf file to .old. Now I can boot into gui again using the nomodeset option.

I am at a complete loss to what to try next. I do not want to have to boot with nomodeset forever, as I only get 640x480 graphics. Any help is very much appreciated.

[MAFoElffen]

I am also at an end to what to try.

I have a Alienware laptop running a Nvidia GTX 460M graphics card.

I do get the grub screen. The operating system does boot, but I get a black screen and I cannot change to another terminal either. The only way I can boot and see anything is with nomodeset.

I have been able to boot to command line using the text and nomodeset option. I then tried to install the Nvidia graphics via:

sudo apt-get install nvidia-current
sudo nvidia-xconfig

I would still get the black screen. So, I then downloaded the correct drivers from Nvidia's site and installed them at the command line. It appeared to work. It installed without any errors and said it uninstalled the old drivers. Still I get a black screen.

After the above step, I was unable to boot into gui mode at all with nomodeset. I went in and renamed the xorg.conf file to .old. Now I can boot into gui again using the nomodeset option.

I am at a complete loss to what to try next. I do not want to have to boot with nomodeset forever, as I only get 640x480 graphics. Any help is very much appreciated.

Please post your current xorg.conf and the results from these commands


sudo hwinfo --frambuffer
sudo hwinfo --monitor
xrandr
xranr -q
That should give us an ideo of what your hardware is, what it is capable of and what driver is loaded.

[neo9900]

This is from xorg.conf.backup. I had to rename it to that to even get into the gui with nomodeset.


xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 270.41.06 (buildmeister@swio-display-x86-rhel47-07.nvidia.com) Mon Apr 18 15:15:12 PDT 2011


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection


sudo hwinfo --framebuffer:

hal.1: read hal dataprocess 2951: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.ku_DuSHewh1
Hardware Class: framebuffer
Model: "Intel(R)Sandybridge Mobile Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(R)Sandybridge Mobile Graphics Controller"
SubVendor: "Intel(R)Sandybridge Mobile Graphics Chipset Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 31 MB + 960 kB
Memory Range: 0xb0000000-0xb1feffff (rw)
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown


sudo hwinfo --monitor

hal.1: read hal dataprocess 2957: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
30: None 00.0: 10002 LCD Monitor
[Created at monitor.95]
Unique ID: rdCR.9DWjcioxsx1
Hardware Class: monitor
Model: "983RG 173WD1 LCD Monitor"
Vendor: LGD "983RG 173WD1"
Device: eisa 0x02d4
Resolution: 1600x900@60Hz
Size: 382x215 mm
Detailed Timings #0:
Resolution: 1600x900
Horizontal: 1600 1648 1696 1784 (+48 +96 +184) -hsync
Vertical: 900 902 905 912 (+2 +5 +12) -vsync
Frequencies: 65.17 MHz, 36.53 kHz, 40.06 Hz
Detailed Timings #1:
Resolution: 1600x900
Horizontal: 1600 1648 1696 1784 (+48 +96 +184) -hsync
Vertical: 900 902 905 912 (+2 +5 +12) -vsync
Frequencies: 97.75 MHz, 54.79 kHz, 60.08 Hz
Config Status: cfg=new, avail=yes, need=no, active=unknown


xrandr:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0

xrandr -q:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 61.0*
800x600 61.0

[MAFoElffen]

This is from xorg.conf.backup. I had to rename it to that to even get into the gui with nomodeset.
Ah,,, I think I see something here. One more thing to post... the results of


lspci | grep VGA

[neo9900]

lspci | grep VGA:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: nVidia Corporation GF106 [GeForce GTX 460M] (rev a1)

[MAFoElffen]

lspci | grep VGA:
That's what I thought. You "really" have both a Sandy Bridge graphics chipset and an nVidia Chipset. I'm assuming that the Sandy Bridge is "onboard" and the nVidia is in a slot?

Hmm, I thought by the resoltuions that it was an old laptop...

On a lot of modern motherboards (which if it has a Sandy Bridge, it is), they usually automatically disable the onboard video when a PCI or PCIE video is installed...

Yours is not disabled. Older boards had a jumper to disable the onboard video... Since you didn't mention the Sandy Bridge, I figure you thought is was diabled and not being used.

It looks like (at least with the utilities) that it thinks the primary is still the Sandy Bridge... and with other current issues with "Sandy Bridge," maybe you should look at disabling that to take it out of the picture.

All the data you gave me is going to "change" once you do that, Afterwards, post "hwinfo --framebuffer " again.

[mwedemeier]

ignore.

[neo9900]

I do not know how to disable the Sandy Bridge. Do you have any suggestions on how to do that? It is a laptop, so there isn't much room to mess around in it.

PS. I have this laptop set up for dual boot. The video card works fine in Windows 7 and it also worked fine in Ubuntu 10.10.

Thanks again.

[MAFoElffen]

I do not know how to disable the Sandy Bridge. Do you have any suggestions on how to do that? It is a laptop, so there isn't much room to mess around in it.

PS. I have this laptop set up for dual boot. The video card works fine in Windows 7 and it also worked fine in Ubuntu 10.10.

Thanks again.Wait one. What make and model laptop? (Maybe I can figure this out from that info...)

[neo9900]

Wait one. What make and model laptop? (Maybe I can figure this out from that info...)

It is an ALIENWARE M17XR3.

[MAFoElffen]

It is an ALIENWARE M17XR3.
So it's a Dell SLI Gaming laptop.

Highest res is 1920x1080x24... It doesn't say anything about the Sandy Bridge chipset for this Laptop(?)

Hmmm.
Select an older kernel image in your grub menu, boot with the nomodeset option > find additional drivers... Reboot using the older kernel image (around 2.6.37... you said you had 10.10 on it before).

If that doesn't work, rename your xorg.conf > go to /etc/default/grub...


sudo cd /etc/default
sudo gedit grub
Uncomment the "GFXMODE=640x480" line in /etc/default/grub in this section


# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
Edit it to this:


GRUB_GFXMODE=1920x1080x24
Then go to this line (same file):


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Edit to this:


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
I would say to add a VGA Vesa modeset, to that line, such as vga=795... But since we have some kind of problem quesrying the nvidia chipset to find those modes,,, That's kind of hard to guess those, so
Then run


sudo update-grub
That "should" work.

I'm thinking that in previous versions of Ubuntu, the Video was not really "changed" until the Graphics Session started. It then used the settings in Xorg, the "drivers" and conf files to change that. The last 2 versions starting taking kernel modesets to "prep it" previous to the Graphics Session start. This current version of Ubuntu is now querying and trying to set the graphics from the grub level before the kernel even starts. At that level, those initial quesries are confused on your hardware, so we might have to prep the graphics manually.

Using the older kernel? Well that would prevent an invalid parameter or mode from locking up the graphs session by not passing it along to Xorg. Installing an older grub would do the same thing, by not passing on the newer parameters.. Problem with the 2 options in this paragraph, is that they are only a temporary workaround, until that bug was resolved..

[neo9900]

I do see something about Sandy Bridge in the Bios. I cannot disable it though, it is greyed out.

I did try your second option and I can get into ubuntu. It does not appear to be running at 1920x1080 though. The resolution is 1024x768.


I didn't go the drivers route b/c I do not know which drivers I should get at this point.

I guess I will have to just get used to the desktop being small. I appreciate your help.

[MAFoElffen]

I do see something about Sandy Bridge in the Bios. I cannot disable it though, it is greyed out.

I did try your second option and I can get into ubuntu. It does not appear to be running at 1920x1080 though. The resolution is 1024x768.


I didn't go the drivers route b/c I do not know which drivers I should get at this point.

I guess I will have to just get used to the desktop being small. I appreciate your help.
If, while in GUI desktop, Additional Drivers... does it see any additional drivers for your hardware? By the last lspci "I know" there's nvidia there. But yes, the Sandy Bridge says 1024v768 as it highest, and for some reaoson it's using the Sandy Bridge.

I'm thinking if you install the nvidia drivers from the natty repo, that it's going to start using the nVidia chip... then just getting the modes from the nVdia chip, getting them configured and use them.

It really shouldn't have tp be thiis hard, but this point in time does seem a bit transitional and challenging. This may be a wait and let things get worked out a ltttle and try again later.

I do know that helping people with Sandy Bridge Chipsets has been a challenge in itself lately.

[neo9900]

When I go to additional drivers, it does show an Nvidia accelerated graphics driver. It says at he bottom that this driver is activated but not currently in use.

Is the following command to get the driver from the Natty Repo?

sudo apt-get install nvidia-current
sudo nvidia-xconfig

I tried this before I ever posted on here. It led to the same black screen that I originally had. I can try it again if you think I should.

[MAFoElffen]

When I go to additional drivers, it does show an Nvidia accelerated graphics driver. It says at he bottom that this driver is activated but not currently in use. .Which means that it is installed but not set as active. (It says it's is already at the stage of apt-get install, but before the config of nvidia-xconfig) There is a button on the right of that that says "Activate." When you press that, it runs nvidia xconfig and creates the xorg.conf. If it gives you a black screen, rename or deltee your /etc/X11/xorf.conf to get back.

Is the following command to get the driver from the Natty Repo?


sudo apt=get install nvidia-current
sudo nvidia-xconfig
I tried this before I ever posted on here. It led to the same black screen that I originally had. I can try it again if you think I should.Yes, but see above...

I would run it again and try. There have been updates to this to try to fix things since the release. If it doesn't. you now know how to get yourself back. Then we could look at your xorg.conf and see if there's something there we could do.

[neo9900]

There is no button that says activate. The only buttons on that window are Remove, Help and Close.

[MAFoElffen]

There is no button that says activate. The only buttons on that window are Remove, Help and Close.Please try this (as a test for us all)

# Outdated - See post #280 #
sudo apt-get install linux-headers-2.6.38-8-generic
sudo apt-get install linux-image-2.6.38-8-generic
sudo apt-get install nvidia-common
sudo apt-get install nvidia-current
sudo nvidia-xconfig
That should reinstall the kernel headers and kernel image... Then reinstall the nvidia drivers using the correct (updated) kernel header files.

[neo9900]

The good news is I didn't get the black screen upon reboot. It did however stop on reboot at the line 'Stopping System V runlevel Compatibility [OK]'

I was able to switch over to tty1. When I typed in startx. I got Fatal Server Error: no screens found.

[MAFoElffen]

The good news is I didn't get the black screen upon reboot. It did however stop on reboot at the line 'Stopping System V runlevel Compatibility [OK]'

I was able to switch over to tty1. When I typed in startx. I got Fatal Server Error: no screens found.
That is strange!

Commad for... is


sudo service gdm start

[neo9900]

When I type

sudo service gdm start

It says


start: Job is already running: gdm

[MAFoElffen]

The good news is I didn't get the black screen upon reboot. It did however stop on reboot at the line 'Stopping System V runlevel Compatibility [OK]'

I was able to switch over to tty1. When I typed in startx. I got Fatal Server Error: no screens found.
Olay then... Lets get you back current another way.

# Outdaed - See post 280 #
sudo apt-get install linux-generic
sudo apt-get install nvidia-common
sudo apt-get install nvidia-current
sudo nvidia-xconfig

[neo9900]

I appreciate your help btw. I'm sorry I'm being such a pain in the butt.


I did try what you said. No difference. I can switch between ttys but the gui startup hangs in the same spot.

FYI: If I remove nomodeset in startup, I get the black screen again. So, I'm just leaving it in.

[MAFoElffen]

I appreciate your help btw. I'm sorry I'm being such a pain in the butt.

I did try what you said. No difference. I can switch between ttys but the gui startup hangs in the same spot.

FYI: If I remove nomodeset in startup, I get the black screen again. So, I'm just leaving it in.
Yes, leave in for now.

Then rename your xorg.conf to anything (so it doesn't use the nvidia drivers) and that should get you back to 4 posts back...

Doesn't seem this is fixed in the repo's yet.

[neo9900]

Okay, I renamed it. I knew to do that, I just wanted to wait until you wanted me to do that.

[MAFoElffen]

Okay, I renamed it. I knew to do that, I just wanted to wait until you wanted me to do that.
for kicks, post your last xorg.conf... so I can take a look at.

[neo9900]

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 270.41.06 (buildmeister@swio-display-x86-rhel47-07.nvidia.com) Mon Apr 18 15:15:12 PDT 2011

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection

[MAFoElffen]

Okay, I renamed it. I knew to do that, I just wanted to wait until you wanted me to do that.
Here's the LP Bug you want to subscribe too.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/772207
It's a dupe of another bug... but they have "mis-referenced" that other bug at the moment.

[neo9900]

Here's the LP Bug you want to subscribe too.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/772207
It's a dupe of another bug... but they have "mis-referenced" that other bug at the moment.

Okay, Thank you for all your help. I do appreciate it.

[skatona]

before I read all 15 pages worth of possible fixes, I must say that this upgrade to 11.04 is one of the worst I have ever had the unfortunate pleasure of experiencing. it is so bad that I almost went back to windows. thank goodness 10.10 is rock solid. I will wait for the release after 11.04 before trying again. when you have a solid release and hit the upgrade button to get the next one, it should upgrade your system, not trash it and not even be able to boot up. in my opinion, which is not even worth the normal 2 cents, 11.04 should not have been made available. very disappointing.

[klm3030]

I agree 100% with skatona (above), this is the sorriest piece of untested garbage that Ubuntu has released yet. At the very least users should be warned not to install on machine with Nvidia graphics. What makes it even worse is there seems to be no one in charge of fixing it, just a bunch of try this, try that with the result of am even more messed up machine. I will be going back to 10.10 and looking for a new Linux OS.

[MAFoElffen]

# nvidia-xconfig: X configuration file generated by nvidia-xconfig... (EDITTED)
@neo9900-- I'm wondering if these edits would work?


# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 270.41.06 (buildmeister@swio-display-x86-rhel47-07.nvidia.com) Mon Apr 18 15:15:12 PDT 2011

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Mode "1920x1080" "1024x768" "800x600" "640x480"
EndSubSection
EndSectionIf they don't back out again. If they do, add the other supported modes to the mode line in the screen section.

[neo9900]

When I made these changes, it boots to the splash screen and then just sits there. I did try adding nosplash in on startup, but it seemed to have no effect.

[MAFoElffen]

When I made these changes, it boots to the splash screen and then just sits there. I did try adding nosplash in on startup, but it seemed to have no effect.
Okay- you know to back out.

I started this Launchpad Bug on behalf of the User community. I don't know that it will get anywhere unless peep's start subscribing to it. I'm hoping the dev's don't mark it as invalid- as I am not directly affected.
Xorgs HAL causes Purple Screen or Black Screen on GDM startup.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/781445

I had you in mind on part of it, when I noted that HAL doesn't look past the Sandy Bridge to "other" chipsets such as on your laptop.

HAL is the Xorg module that queries the hardware and is supposed to return its valid data back to Xorg to use. I am leaning towards thhis module causing the majority of these graphics problems that the community is now experiencing.

HAL is used by xrandr to query hardward and is used in the construction of the xorg.conf file.

All these "work-arounds" and such are essentially bypassing this module by having the user set the graphics "manually." People should rightfully expect that an automated install or an update "is" just that.

[neo9900]

Thanks for the update. I did subscribe to that bug report.

[drs305]

@ MAFoElffen,

Is this solution applicable to only a completely blank screen or also one with a blinking cursor.

I have to admit I haven't read every post in this thread, but I haven't found too many with 'blinking' referenced.

The reason I'm asking is that many users get a blinking cursor in Natty, add the 'nomodeset' option, and are then able to boot and install the Nvidia drivers. Is that related in any way to this issue? If not, is there a way to differentiate between a blinking cursor because of a video driver issue and what is happening here.

Thanks.

[MAFoElffen]

@ MAFoElffen,

Is this solution applicable to only a completely blank screen or also one with a blinking cursor.

I have to admit I haven't read every post in this thread, but I haven't found too many with 'blinking' referenced.

The reason I'm asking is that many users get a blinking cursor in Natty, add the 'nomodeset' option, and are then able to boot and install the Nvidia drivers. Is that related in any way to this issue? If not, is there a way to differentiate between a blinking cursor because of a video driver issue and what is happening here.

Thanks.
It seems that may be "some" if it happens on the X-Window start before the graphics intit. (Dis happen in 2 of my tests with natty beta1)

Test would be boot kernel in text console, success = kernel is booting. > Start service GDM dailure most likely = graphics session itself.

[MAFoElffen]

I updated the first 3 posts with what is current on workarounds, current Launchpad and Upstream bugs.

Seems to be a current debate with the Ubuntu LP triage team on "where" to point the main bug to... But the GNU Grub dev's do seem to agree that it is an upstream grub bug on GNU Grub 1.99~rc1.

[sindhughanti]

Hi
I have a system with RHEL 5 installed on it.
I installed Edubuntu 10.04 LTSP side-by-side without installing the boot-loader.
Now I can detect Edubuntu thro RHEL, but have to make an entry for Edubuntu in the grub menu through RHEL. Kindly help me with this.
How do I do this? I need to know how i can find the kernel version number etc. Detailed help would be appreciated as i am new to this. Thanks
(I dint know where to post this, but pls help!):(

[MAFoElffen]

Hi
I have a system with RHEL 5 installed on it.
I installed Edubuntu 10.04 LTSP side-by-side without installing the boot-loader.
Now I can detect Edubuntu thro RHEL, but have to make an entry for Edubuntu in the grub menu through RHEL. Kindly help me with this.
How do I do this? I need to know how i can find the kernel version number etc. Detailed help would be appreciated as i am new to this. Thanks
(I dint know where to post this, but pls help!):(
Welcome to Ubuntu,,,

This sticky to to help people correct "graphics problems." You would most likely be better helped IF you started a new thread in this forum area... Asking for help with your problem. But no matter, you are already off topic. (I can't say too much // I will be off topic from this thread...)

Red Hat 5.x uses GNU Grub Legacy and Edubuntu 10.04 uses GNU Grub2... You can boot (chainload) each other from each other, but they both have to be installed to do it and one has to be over the other (primary). Instructions for that are beyond just an offhand offtopic question.

IMHO- I "would" install grub2 from edubuntu. Grub2 should automatically find rhel in the update-grub process and add it to it's menu. If it doesn't-- I have some examples of chainloading from Grubs2 to Grub Legacy...

Anyways --> Please start a new thread so you can get help and where you can be helped with that.

[sindhughanti]

Welcome to Ubuntu,,,

This sticky to to help people correct "graphics problems." You would most likely be better helped IF you started a new thread in this forum area... Asking for help with your problem. But no matter, you are already off topic. (I can't say too much // I will be off topic from this thread...)

Red Hat 5.x uses GNU Grub Legacy and Edubuntu 10.04 uses GNU Grub2... You can boot (chainload) each other from each other, but they both have to be installed to do it and one has to be over the other (primary). Instructions for that are beyond just an offhand offtopic question.

IMHO- I "would" install grub2 from edubuntu. Grub2 should automatically find rhel in the update-grub process and add it to it's menu. If it doesn't-- I have some examples of chainloading from Grubs2 to Grub Legacy...

Anyways --> Please start a new thread so you can get help and where you can be helped with that.

Thanks MAFoElffen,
First of all, I am really sorry to interrupt this thread!
can u pls provide me with details on this thread where i started it! Step-by-step would be very helpful. I can access only RHEL as of now. So I dont know how to install grub2 from edubuntu. My further queries will be on the new thread.
http://ubuntuforums.org/showthread.php?p=10822899#post10822899
I would be really grateful!! Pls ! Thanks :)

[johnthei]

this is extremely confusing to those of us who are not versed in all the code commands, and all the possible fixes. I just unplug the hard drive Ubuntu is on now, and use windows sp on another drive. at least it starts. I have tried several fixes for the nvidia problem. none work yet. I considered buying a separate video card but I see some non-nvidia cards have their own problems.

[rbellah]

Three Installs, one of which was an upgrade all ended in the graphics problem, pretty much locked out of any way to adjust or get in to 11.4, Is there a fix to boot in once a install has finished?

[MAFoElffen]

this is extremely confusing to those of us who are not versed in all the code commands, and all the possible fixes. I just unplug the hard drive Ubuntu is on now, and use windows sp on another drive. at least it starts. I have tried several fixes for the nvidia problem. none work yet. I considered buying a separate video card but I see some non-nvidia cards have their own problems.
Yes iit is... As I said in my Bug Report at Launchpad:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/781445


Normal users should not have to be highly skilled "techies" to manually bypass a broken part of a system to make a released distribution work during an install or distribution upgrade!
I have a lot of Nvidia and ATI cards here. I personally prefer nvidia. I jsut expect that they need an extra step to get installed, but I like the results.

Most nvidia cards I install in boxes--
- I install the system.
- I reboot the for the first time using the recovery mode option of the grub menu. (Usually the 2nd menu item)
- I use the safe mode (low graphics) to boot into the gnome desktop.
- I find additional drivers and install recommended.
- I reboot.
That's what the majority of nvidia "owners" should expect on any install of any distribution of linux or unix.. There are always exceptions, but.

There had been a problem where some where getting a "bad" driver or installed a driver that was not for "their" card,. but an unistall/rienstall would usaaly take care of that.


Three Installs, one of which was an upgrade all ended in the graphics problem, pretty much locked out of any way to adjust or get in to 11.4, Is there a fix to boot in once a install has finished?
I admit there is a lot of info packed into those first 3 posts... Helping people through their problems is why this sticky is open for posts and feedback- I try to tailor responses to that person, their hardware and their problem. This community is users helping users. That's how I was helped and I learned when I first started. Now I get to pay that back to others.

What hardware do you have? (PC and video card)
What \version of Ubuntu are you installing?
Where does is end up for you? (Description)

That is a good start.

[Blasphemist]

First, this is a great thread and I use it frequently. I was looking into a thread about fan control and pointed out the person might need to use acpi_osi="Linux". Someone else corrected me saying to use acpi_osi=\"Linux\". I tried looking at the grub2 1.99 manual to verify and couldn't find a thing that told me which is correct. I did find these things here-
http://www.gnu.org/software/grub/manual/grub.html#linux

14.3.24 linux

— Command: linux file ...
Load a Linux kernel image from file. The rest of the line is passed verbatim as the kernel command-line. Any initrd must be reloaded after using this command (see initrd).

On x86 systems, the kernel will be booted using the 32-bit boot protocol. Note that this means that the ‘vga=’ boot option will not work; if you want to set a special video mode, you will need to use GRUB commands such as ‘set gfxpayload=1024x768’ or ‘set gfxpayload=keep’ (to keep the same mode as used in GRUB) instead. GRUB can automatically detect some uses of ‘vga=’ and translate them to appropriate settings of ‘gfxpayload’. The linux16 command (see linux16) avoids this restriction.
So when we are using the vga= when we haven't determined if the poster has 32 or 64 bit might that explain some things? Also and related, I know you are already using this but I loved the phase of the moon thing and knew you would with all the work you've put into this.

‘GRUB_GFXPAYLOAD_LINUX’
Set to ‘text’ to force the Linux kernel to boot in normal text mode, ‘keep’ to preserve the graphics mode set using ‘GRUB_GFXMODE’, ‘widthxheight’[‘xdepth’] to set a particular graphics mode, or a sequence of these separated by commas or semicolons to try several modes in sequence. See gfxpayload.
Depending on your kernel, your distribution, your graphics card, and the phase of the moon, note that using this option may cause GNU/Linux to suffer from various display problems, particularly during the early part of the boot sequence. If you have problems, set this option to ‘text’ and GRUB will tell Linux to boot in normal text mode.

Anyway, unless I see something from you, I'll try to figure out the proper acpi_osi= entry.

[MAFoElffen]

First, this is a great thread and I use it frequently. I was looking into a thread about fan control and pointed out the person might need to use acpi_osi="Linux". Someone else corrected me saying to use acpi_osi=\"Linux\". I tried looking at the grub2 1.99 manual to verify and couldn't find a thing that told me which is correct. I did find these things here-
http://www.gnu.org/software/grub/manual/grub.html#linux
It's Both and you were both correct. But I'd have to explain that... It a grub parser thang.

The linux kernel set mode switch is


acpi_osi="Linux"
So you would type it that way if you where adding it to the kernel boot line (in grub menu edit mode) or trying it from the Grub Command Line Interface...

But when you try to make it permanent in /etc/default/grub, you add it to a variable, that the update-grub parser reads and builds into a kernel boot line:


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblahblah"
That is a vairiable that update-grub "parses"... Notice that "that" variable's expression is opened and closed with a quotation mark also.

In order to include the switch's quotation marks inside that- we have to use the / character before it to use it as an escape character of a quatation mark.... so if comes out as having to be wriiten as


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=/"Linux/" "
Just to come out right after the parser. That is a grub scripting/parsing limitation. You have to use the escape character for the quotaion inside the variable so that it doesn't do this

See's the first quotation mark of the variable > Sees first quotation mark of the mode set switch <> but thinks it was the closing quotation mark of the variable.

Does that explain why it's written both ways, but ends up as the first?



So when we are using the vga= when we haven't determined if the poster has 32 or 64 bit might that explain some things? Also and related, I know you are already using this but I loved the phase of the moon thing and knew you would with all the work you've put into this.


Anyway, unless I see something from you, I'll try to figure out the proper acpi_osi= entry.
The VGA switch still seems to work on both, sort of (see below). The only warning I've found so far, (that I know of yet) is don't use a vga switch on a box with an i915 vidoe chipset. There's an open bug on that / will cause a black screen just by using that switch with that chipset.

I thought GNU was spot-on when they included that "phase of the moon" quotation in their man page. I thought it was both hilarious and true!!!

The vga switch is one of those things that are "phase of the moon." I set both the GRUB_GFXMode (all 3 parms) and the vga switch, just to cover it both ways. If a 32bit kernel can't take a VGA switch, it "doesn't take it... it just seems to ignore it instead of causing any error. Some 32bit kernels still seem to be taking it fine. But it is hit and miss. Try it and if it doesn't. work, well, then I try something else...

Here's something "different" for you to look at...
http://ubuntuforums.org/showpost.php?p=10834400&postcount=10

[Randal Graves]

Hi, these types of fixes are probably too advanced for me but i figured id give it a shot.

I just installed Ubuntu 11.04 on my computer coming from windows xp. When I first installed it everything was fine. I installed wine and transferred over all my music, files, etc. I then tried to adjust my dual monitors so they wouldnt show as 'mirror' and every since then and more specifically when i adjusted the resolution, my graphics are blurry especially around in the launchmenu in Unity. When I load thru Gnome the gfx is a lot better but still not good..

Im loading Ubuntu from a flash drive, I first tried 'upgrade' and then I tried 'erase and reinstall', neither of those are fixing my problem.

When I load from safe mode the graphics are fine and ive checked for additional drivers with no luck.

Everything else seems to work fine.






Unity SS

http://www.up-urs.net/files/1305771767Screenshot.png

hwinfo --framebuffer


> hal.1: read hal dataprocess 1901: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.TIM8629z9tC
Hardware Class: framebuffer
Model: "ATI V380"
Vendor: "ATI Technologies Inc."
Device: "V380"
SubVendor: "ATI RV370"
SubDevice:
Revision: "01.00"
Memory Size: 16 MB
Memory Range: 0xec000000-0xecffffff (rw)
Mode 0x0382: 320x200 (+320), 8 bits
Mode 0x030d: 320x200 (+640), 15 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+960), 24 bits
Mode 0x0320: 320x200 (+1280), 24 bits
Mode 0x0392: 320x240 (+320), 8 bits
Mode 0x0393: 320x240 (+640), 15 bits
Mode 0x0394: 320x240 (+640), 16 bits
Mode 0x0395: 320x240 (+960), 24 bits
Mode 0x0396: 320x240 (+1280), 24 bits
Mode 0x03a2: 400x300 (+400), 8 bits
Mode 0x03a3: 400x300 (+800), 15 bits
Mode 0x03a4: 400x300 (+800), 16 bits
Mode 0x03a5: 400x300 (+1200), 24 bits
Mode 0x03a6: 400x300 (+1600), 24 bits
Mode 0x03b2: 512x384 (+512), 8 bits
Mode 0x03b3: 512x384 (+1024), 15 bits
Mode 0x03b4: 512x384 (+1024), 16 bits
Mode 0x03b5: 512x384 (+1536), 24 bits
Mode 0x03b6: 512x384 (+2048), 24 bits
Mode 0x03c2: 640x350 (+640), 8 bits
Mode 0x03c3: 640x350 (+1280), 15 bits
Mode 0x03c4: 640x350 (+1280), 16 bits
Mode 0x03c5: 640x350 (+1920), 24 bits
Mode 0x03c6: 640x350 (+2560), 24 bits
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0383: 640x400 (+1280), 15 bits
Mode 0x0384: 640x400 (+1280), 16 bits
Mode 0x0385: 640x400 (+1920), 24 bits
Mode 0x0386: 640x400 (+2560), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0310: 640x480 (+1280), 15 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+1920), 24 bits
Mode 0x0321: 640x480 (+2560), 24 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0313: 800x600 (+1600), 15 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+2400), 24 bits
Mode 0x0322: 800x600 (+3200), 24 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0316: 1024x768 (+2048), 15 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+3072), 24 bits
Mode 0x0323: 1024x768 (+4096), 24 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x0319: 1280x1024 (+2560), 15 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+3840), 24 bits
Mode 0x0324: 1280x1024 (+5120), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

[johnthei]

MAFoElffen:

Thanks I will try some of this over the weekend. I don't have time during the week to do much work on it. I will report back sucess or failure...

[MAFoElffen]

Hi, these types of fixes are probably too advanced for me but i figured id give it a shot.

I just installed Ubuntu 11.04 on my computer coming from windows xp. When I first installed it everything was fine. I installed wine and transferred over all my music, files, etc. I then tried to adjust my dual monitors so they wouldnt show as 'mirror' and every since then and more specifically when i adjusted the resolution, my graphics are blurry especially around in the launchmenu in Unity. When I load thru Gnome the gfx is a lot better but still not good..

Im loading Ubuntu from a flash drive, I first tried 'upgrade' and then I tried 'erase and reinstall', neither of those are fixing my problem.

When I load from safe mode the graphics are fine and ive checked for additional drivers with no luck.

Everything else seems to work fine.

Unity SS (editted)

hwinfo --framebuffer


> hal.1: read hal dataprocess 1901: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.TIM8629z9tC
Hardware Class: framebuffer
Model: "ATI V380"
Vendor: "ATI Technologies Inc."
Device: "V380"
SubVendor: "ATI RV370"
SubDevice:
Revision: "01.00"
Memory Size: 16 MB
Memory Range: 0xec000000-0xecffffff (rw)
Mode 0x0382: 320x200 (+320), 8 bits
Mode 0x030d: 320x200 (+640), 15 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+960), 24 bits
Mode 0x0320: 320x200 (+1280), 24 bits
Mode 0x0392: 320x240 (+320), 8 bits
Mode 0x0393: 320x240 (+640), 15 bits
Mode 0x0394: 320x240 (+640), 16 bits
Mode 0x0395: 320x240 (+960), 24 bits
Mode 0x0396: 320x240 (+1280), 24 bits
Mode 0x03a2: 400x300 (+400), 8 bits
Mode 0x03a3: 400x300 (+800), 15 bits
Mode 0x03a4: 400x300 (+800), 16 bits
Mode 0x03a5: 400x300 (+1200), 24 bits
Mode 0x03a6: 400x300 (+1600), 24 bits
Mode 0x03b2: 512x384 (+512), 8 bits
Mode 0x03b3: 512x384 (+1024), 15 bits
Mode 0x03b4: 512x384 (+1024), 16 bits
Mode 0x03b5: 512x384 (+1536), 24 bits
Mode 0x03b6: 512x384 (+2048), 24 bits
Mode 0x03c2: 640x350 (+640), 8 bits
Mode 0x03c3: 640x350 (+1280), 15 bits
Mode 0x03c4: 640x350 (+1280), 16 bits
Mode 0x03c5: 640x350 (+1920), 24 bits
Mode 0x03c6: 640x350 (+2560), 24 bits
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0383: 640x400 (+1280), 15 bits
Mode 0x0384: 640x400 (+1280), 16 bits
Mode 0x0385: 640x400 (+1920), 24 bits
Mode 0x0386: 640x400 (+2560), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0310: 640x480 (+1280), 15 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+1920), 24 bits
Mode 0x0321: 640x480 (+2560), 24 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0313: 800x600 (+1600), 15 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+2400), 24 bits
Mode 0x0322: 800x600 (+3200), 24 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0316: 1024x768 (+2048), 15 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+3072), 24 bits
Mode 0x0323: 1024x768 (+4096), 24 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x0319: 1280x1024 (+2560), 15 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+3840), 24 bits
Mode 0x0324: 1280x1024 (+5120), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

It's aSomewhat related. but separate problem than this thread. It seems to be an issue with Dual Monitors and COMPIZ:
http://ubuntuforums.org/showthread.php?t=1743667
http://ubuntuforums.org/showthread.php?t=1158095

There are a few Bug Reports on it up at LP and I've been trying to help someone for about 3 days in PM, with the same issue.

You know, why not... I just got an old 32bit box and an agp ATI Wonder card. Tonight I'll throw it together and see if I can recreate and go from there.

In the mean while:
What driver are you using?
Please post your ~/.xsessionerrors.log, /etc/X11/xorg.conf and the results of"


sudo hwinfo --monitor
xrandr -q

[cglacet]

Hello,

I have a similar problem :

Normal boot : empty screen but with ubuntu background
Text boot : I can log in and then I'm able to start graphical session (startx). My background loads corectly and I get a strange window titled "unlock keyring" (again perfectly displayed, even with shadows and round borders) but nothing more.
If I type my password and validate, then nothing append.
From here all I can do is ctrl+alt+del (open shutdown menu - correctly displyed) or lock my session (crtl+L) and open a terminal. For instance, these are the only two things I was able to do.



Is my problem related to this thread?
I'm lost... Help me :confused:

I have a Radeon HD 3450 (ATI technologies Inc RV620) and I run on a 64bits machine

Thank you already.

edit : when I log as root, I have the same purple default background and a loading cursor that never stops.

[Randal Graves]

Thanks for trying to help! Hopefully I can keep up :)


hwinfo --monitor

> hal.1: read hal dataprocess 1672: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
28: None 00.0: 10000 Monitor
[Created at monitor.95]
Unique ID: rdCR.xhbKsVh65S4
Hardware Class: monitor
Model: "HP LE2001w"
Vendor: HWP "HP"
Device: eisa 0x2841 "HP LE2001w"
Serial ID: "CNT013D03K"
Resolution: 720x400@70Hz
Resolution: 640x480@60Hz
Resolution: 800x600@60Hz
Resolution: 1024x768@60Hz
Resolution: 1280x720@60Hz
Resolution: 1280x1024@60Hz
Resolution: 1600x900@60Hz
Size: 442x249 mm
Detailed Timings #0:
Resolution: 1600x900
Horizontal: 1600 1624 1704 1800 (+24 +104 +200) +hsync
Vertical: 900 901 904 1000 (+1 +4 +100) +vsync
Frequencies: 108.00 MHz, 60.00 kHz, 60.00 Hz
Driver Info #0:
Max. Resolution: 1600x900
Vert. Sync Range: 48-76 Hz
Hor. Sync Range: 24-85 kHz
Bandwidth: 108 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown

29: None 00.1: 10000 Monitor
[Created at monitor.95]
Unique ID: jyhG.xhbKsVh65S4
Hardware Class: monitor
Model: "HP LE2001w"
Vendor: HWP "HP"
Device: eisa 0x2841 "HP LE2001w"
Serial ID: "CNT013D03K"
Resolution: 720x400@70Hz
Resolution: 640x480@60Hz
Resolution: 800x600@60Hz
Resolution: 1024x768@60Hz
Resolution: 1280x720@60Hz
Resolution: 1280x1024@60Hz
Resolution: 1600x900@60Hz
Size: 442x249 mm
Detailed Timings #0:
Resolution: 1600x900
Horizontal: 1600 1624 1704 1800 (+24 +104 +200) +hsync
Vertical: 900 901 904 1000 (+1 +4 +100) +vsync
Frequencies: 108.00 MHz, 60.00 kHz, 60.00 Hz
Driver Info #0:
Max. Resolution: 1600x900
Vert. Sync Range: 48-76 Hz
Hor. Sync Range: 24-85 kHz
Bandwidth: 108 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown


xrandr -q


Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 442mm x 249mm
1600x900 60.0 +
1280x1024 60.0
1440x900 59.9*
1280x720 60.0
1024x768 60.0
800x600 60.3
640x480 60.0
720x400 70.1
DVI-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 257mm
1440x900 59.9*+
1280x1024 75.0 60.0
1280x960 60.0
1152x864 75.0
1024x768 75.1 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 66.7 60.0
720x400 70.1
S-video disconnected (normal left inverted right x axis y axis)

Not sure if this is what you meant but here is the terminal results.



brooks@AugustWest:~$ ~/.xsessionerrors.log./etc/X11/xorg.conf
bash: /home/brooks/.xsessionerrors.log./etc/X11/xorg.conf: No such file or directory

And here is the system log file which I think is what you want (tho maybe not all of it?)

13.312] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 19 10:30:20 2011
[ 13.313] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 13.313] (==) No Layout section. Using the first Screen section.
[ 13.313] (==) No screen section available. Using defaults.
[ 13.313] (**) |-->Screen "Default Screen Section" (0)
[ 13.313] (**) | |-->Monitor "<default monitor>"
[ 13.313] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 13.313] (==) Automatically adding devices
[ 13.313] (==) Automatically enabling devices
[ 13.314] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 13.314] Entry deleted from font path.
[ 13.314] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 13.314] Entry deleted from font path.
[ 13.314] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 13.314] Entry deleted from font path.
[ 13.314] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 13.314] Entry deleted from font path.
[ 13.314] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 13.314] Entry deleted from font path.
[ 13.314] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[ 13.314] (==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 13.314] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 13.314] (II) Loader magic: 0x81ffde0
[ 13.314] (II) Module ABI versions:
[ 13.314] X.Org ANSI C Emulation: 0.4
[ 13.314] X.Org Video Driver: 10.0
[ 13.314] X.Org XInput driver : 12.3
[ 13.314] X.Org Server Extension : 5.0
[ 13.315] (--) PCI:*(0:1:0:0) 1002:5b60:1002:0602 rev 0, Mem @ 0xec000000/33554432, 0xefde0000/65536, I/O @ 0x0000dc00/256, BIOS @ 0x????????/131072
[ 13.316] (--) PCI: (0:1:0:1) 1002:5b70:1002:0603 rev 0, Mem @ 0xefdf0000/65536
[ 13.316] (II) Open ACPI successful (/var/run/acpid.socket)
[ 13.316] (II) LoadModule: "extmod"
[ 13.332] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 13.332] (II) Module extmod: vendor="X.Org Foundation"
[ 13.332] compiled for 1.10.1, module version = 1.0.0
[ 13.332] Module class: X.Org Server Extension
[ 13.332] ABI class: X.Org Server Extension, version 5.0
[ 13.332] (II) Loading extension MIT-SCREEN-SAVER
[ 13.332] (II) Loading extension XFree86-VidModeExtension
[ 13.332] (II) Loading extension XFree86-DGA
[ 13.332] (II) Loading extension DPMS
[ 13.332] (II) Loading extension XVideo
[ 13.332] (II) Loading extension XVideo-MotionCompensation
[ 13.332] (II) Loading extension X-Resource
[ 13.332] (II) LoadModule: "dbe"
[ 13.333] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 13.334] (II) Module dbe: vendor="X.Org Foundation"
[ 13.334] compiled for 1.10.1, module version = 1.0.0
[ 13.334] Module class: X.Org Server Extension
[ 13.334] ABI class: X.Org Server Extension, version 5.0
[ 13.334] (II) Loading extension DOUBLE-BUFFER
[ 13.334] (II) LoadModule: "glx"
[ 13.335] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 13.335] (II) Module glx: vendor="X.Org Foundation"
[ 13.335] compiled for 1.10.1, module version = 1.0.0
[ 13.335] ABI class: X.Org Server Extension, version 5.0
[ 13.335] (==) AIGLX enabled
[ 13.335] (II) Loading extension GLX
[ 13.335] (II) LoadModule: "record"
[ 13.336] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 13.336] (II) Module record: vendor="X.Org Foundation"
[ 13.336] compiled for 1.10.1, module version = 1.13.0
[ 13.336] Module class: X.Org Server Extension
[ 13.337] ABI class: X.Org Server Extension, version 5.0
[ 13.337] (II) Loading extension RECORD
[ 13.337] (II) LoadModule: "dri"
[ 13.338] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 13.338] (II) Module dri: vendor="X.Org Foundation"
[ 13.338] compiled for 1.10.1, module version = 1.0.0
[ 13.338] ABI class: X.Org Server Extension, version 5.0
[ 13.338] (II) Loading extension XFree86-DRI
[ 13.338] (II) LoadModule: "dri2"
[ 13.339] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 13.339] (II) Module dri2: vendor="X.Org Foundation"
[ 13.339] compiled for 1.10.1, module version = 1.2.0
[ 13.339] ABI class: X.Org Server Extension, version 5.0
[ 13.339] (II) Loading extension DRI2
[ 13.339] (==) Matched fglrx as autoconfigured driver 0
[ 13.339] (==) Matched ati as autoconfigured driver 1
[ 13.339] (==) Matched vesa as autoconfigured driver 2
[ 13.339] (==) Matched fbdev as autoconfigured driver 3
[ 13.349] (==) Assigned the driver to the xf86ConfigLayout
[ 13.349] (II) LoadModule: "fglrx"
[ 13.351] (WW) Warning, couldn't open module fglrx
[ 13.351] (II) UnloadModule: "fglrx"
[ 13.351] (II) Unloading fglrx
[ 13.351] (EE) Failed to load module "fglrx" (module does not exist, 0)
[ 13.351] (II) LoadModule: "ati"
[ 13.352] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 13.352] (II) Module ati: vendor="X.Org Foundation"
[ 13.352] compiled for 1.10.0, module version = 6.14.0
[ 13.352] Module class: X.Org Video Driver
[ 13.352] ABI class: X.Org Video Driver, version 10.0
[ 13.352] (II) LoadModule: "radeon"
[ 13.353] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 13.353] (II) Module radeon: vendor="X.Org Foundation"
[ 13.353] compiled for 1.10.0, module version = 6.14.0
[ 13.353] Module class: X.Org Video Driver
[ 13.353] ABI class: X.Org Video Driver, version 10.0
[ 13.353] (II) LoadModule: "vesa"
[ 13.354] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 13.354] (II) Module vesa: vendor="X.Org Foundation"
[ 13.354] compiled for 1.10.0, module version = 2.3.0
[ 13.354] Module class: X.Org Video Driver
[ 13.354] ABI class: X.Org Video Driver, version 10.0
[ 13.354] (II) LoadModule: "fbdev"
[ 13.355] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 13.355] (II) Module fbdev: vendor="X.Org Foundation"
[ 13.355] compiled for 1.10.0, module version = 0.4.2
[ 13.355] ABI class: X.Org Video Driver, version 10.0
[ 13.355] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
ATI Mobility Radeon HD 4670, ATI FirePro M5750,
ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3000 Graphics, ATI Radeon HD 4200, ATI Radeon 4100,
ATI Mobility Radeon HD 4200, ATI Mobility Radeon 4100,
ATI Radeon HD 4290, ATI Radeon HD 4250, AMD Radeon HD 6310 Graphics,
AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
AMD Radeon HD 6250 Graphics, CYPRESS,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
AMD Firestream 9350, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
ATI Radeon HD 5900 Series, ATI Radeon HD 5900 Series,
ATI Mobility Radeon HD 5800 Series,
ATI Mobility Radeon HD 5800 Series,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 5700 Series,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
ATI Mobility Radeon Graphics, CEDAR,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
ATI Radeon HD 5450, CEDAR, AMD Radeon HD 6900M Series,
Mobility Radeon HD 6000 Series, BARTS, BARTS,
Mobility Radeon HD 6000 Series, Mobility Radeon HD 6000 Series,
BARTS, BARTS, BARTS, BARTS, AMD Radeon HD 6800 Series,
AMD Radeon HD 6800 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, CAICOS, CAICOS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
CAICOS
[ 13.379] (II) VESA: driver for VESA chipsets: vesa
[ 13.379] (II) FBDEV: driver for framebuffer: fbdev
[ 13.379] (++) using VT number 7

[ 13.380] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 13.380] (II) [KMS] Kernel modesetting enabled.
[ 13.380] (WW) Falling back to old probe method for vesa
[ 13.380] (WW) Falling back to old probe method for fbdev
[ 13.380] (II) Loading sub module "fbdevhw"
[ 13.380] (II) LoadModule: "fbdevhw"
[ 13.381] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 13.381] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 13.381] compiled for 1.10.1, module version = 0.0.2
[ 13.381] ABI class: X.Org Video Driver, version 10.0
[ 13.382] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 13.382] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 13.382] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 13.382] (==) RADEON(0): Default visual is TrueColor
[ 13.382] (==) RADEON(0): RGB weight 888
[ 13.382] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 13.382] (--) RADEON(0): Chipset: "ATI Radeon X300 (RV370) 5B60 (PCIE)" (ChipID = 0x5b60)
[ 13.382] (II) RADEON(0): PCIE card detected
[ 13.382] drmOpenDevice: node name is /dev/dri/card0
[ 13.382] drmOpenDevice: open result is 9, (OK)
[ 13.382] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 13.382] drmOpenDevice: node name is /dev/dri/card0
[ 13.382] drmOpenDevice: open result is 9, (OK)
[ 13.382] drmOpenByBusid: drmOpenMinor returns 9
[ 13.382] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 13.383] (II) RADEON(0): KMS Color Tiling: enabled
[ 13.383] (II) RADEON(0): KMS Pageflipping: enabled
[ 13.383] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[ 13.439] (II) RADEON(0): Output VGA-0 has no monitor section
[ 13.496] (II) RADEON(0): Output DVI-0 has no monitor section
[ 13.496] (II) RADEON(0): Output S-video has no monitor section
[ 13.567] (II) RADEON(0): EDID for output VGA-0
[ 13.568] (II) RADEON(0): Manufacturer: HWP Model: 2841 Serial#: 16843009
[ 13.568] (II) RADEON(0): Year: 2010 Week: 13
[ 13.568] (II) RADEON(0): EDID Version: 1.3
[ 13.568] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 13.568] (II) RADEON(0): Sync: Separate
[ 13.568] (II) RADEON(0): Max Image Size [cm]: horiz.: 44 vert.: 25
[ 13.568] (II) RADEON(0): Gamma: 2.20
[ 13.568] (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 13.568] (II) RADEON(0): Default color space is primary color space
[ 13.568] (II) RADEON(0): First detailed timing is preferred mode
[ 13.568] (II) RADEON(0): redX: 0.650 redY: 0.335 greenX: 0.282 greenY: 0.616
[ 13.568] (II) RADEON(0): blueX: 0.146 blueY: 0.085 whiteX: 0.313 whiteY: 0.329
[ 13.568] (II) RADEON(0): Supported established timings:
[ 13.568] (II) RADEON(0): 720x400@70Hz
[ 13.568] (II) RADEON(0): 640x480@60Hz
[ 13.568] (II) RADEON(0): 800x600@60Hz
[ 13.568] (II) RADEON(0): 1024x768@60Hz
[ 13.568] (II) RADEON(0): Manufacturer's mask: 0
[ 13.568] (II) RADEON(0): Supported standard timings:
[ 13.568] (II) RADEON(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 13.568] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 13.568] (II) RADEON(0): #2: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 13.568] (II) RADEON(0): Supported detailed timing:
[ 13.568] (II) RADEON(0): clock: 108.0 MHz Image Size: 442 x 249 mm
[ 13.568] (II) RADEON(0): h_active: 1600 h_sync: 1624 h_sync_end 1704 h_blank_end 1800 h_border: 0
[ 13.568] (II) RADEON(0): v_active: 900 v_sync: 901 v_sync_end 904 v_blanking: 1000 v_border: 0
[ 13.568] (II) RADEON(0): Ranges: V min: 48 V max: 76 Hz, H min: 24 H max: 85 kHz, PixClock max 175 MHz
[ 13.568] (II) RADEON(0): Monitor name: HP LE2001w
[ 13.569] (II) RADEON(0): Serial No: CNT013D03K
[ 13.569] (II) RADEON(0): EDID (in hex):
[ 13.569] (II) RADEON(0): 00ffffffffffff0022f0412801010101
[ 13.569] (II) RADEON(0): 0d140103682c1978eeb7b5a655489d25
[ 13.569] (II) RADEON(0): 155054a1080081c08180950001010101
[ 13.569] (II) RADEON(0): 010101010101302a40c8608464301850
[ 13.569] (II) RADEON(0): 1300baf91000001e000000fd00304c18
[ 13.569] (II) RADEON(0): 5511000a202020202020000000fc0048
[ 13.569] (II) RADEON(0): 50204c4532303031770a2020000000ff
[ 13.569] (II) RADEON(0): 00434e543031334430334b0a20200027
[ 13.569] (II) RADEON(0): EDID vendor "HWP", prod id 10305
[ 13.569] (II) RADEON(0): Using EDID range info for horizontal sync
[ 13.569] (II) RADEON(0): Using EDID range info for vertical refresh
[ 13.569] (II) RADEON(0): Printing DDC gathered Modelines:
[ 13.569] (II) RADEON(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz)
[ 13.569] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 13.569] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 13.569] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 13.569] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 13.569] (II) RADEON(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz)
[ 13.569] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 13.569] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 13.569] (II) RADEON(0): Printing probed modes for output VGA-0
[ 13.569] (II) RADEON(0): Modeline "1600x900"x60.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz)
[ 13.569] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 13.569] (II) RADEON(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 13.569] (II) RADEON(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 13.569] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 13.569] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 13.570] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 13.570] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 13.626] (II) RADEON(0): EDID for output DVI-0
[ 13.626] (II) RADEON(0): Manufacturer: VSC Model: b71e Serial#: 16843009
[ 13.626] (II) RADEON(0): Year: 2006 Week: 35
[ 13.626] (II) RADEON(0): EDID Version: 1.3
[ 13.626] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 13.626] (II) RADEON(0): Sync: Separate
[ 13.626] (II) RADEON(0): Max Image Size [cm]: horiz.: 41 vert.: 26
[ 13.626] (II) RADEON(0): Gamma: 2.20
[ 13.626] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
[ 13.626] (II) RADEON(0): Default color space is primary color space
[ 13.626] (II) RADEON(0): First detailed timing is preferred mode
[ 13.626] (II) RADEON(0): redX: 0.640 redY: 0.349 greenX: 0.284 greenY: 0.617
[ 13.626] (II) RADEON(0): blueX: 0.142 blueY: 0.067 whiteX: 0.313 whiteY: 0.329
[ 13.626] (II) RADEON(0): Supported established timings:
[ 13.626] (II) RADEON(0): 720x400@70Hz
[ 13.626] (II) RADEON(0): 640x480@60Hz
[ 13.626] (II) RADEON(0): 640x480@67Hz
[ 13.626] (II) RADEON(0): 640x480@72Hz
[ 13.626] (II) RADEON(0): 640x480@75Hz
[ 13.626] (II) RADEON(0): 800x600@56Hz
[ 13.626] (II) RADEON(0): 800x600@60Hz
[ 13.626] (II) RADEON(0): 800x600@72Hz
[ 13.626] (II) RADEON(0): 800x600@75Hz
[ 13.627] (II) RADEON(0): 832x624@75Hz
[ 13.627] (II) RADEON(0): 1024x768@60Hz
[ 13.627] (II) RADEON(0): 1024x768@70Hz
[ 13.627] (II) RADEON(0): 1024x768@75Hz
[ 13.627] (II) RADEON(0): 1280x1024@75Hz
[ 13.627] (II) RADEON(0): 1152x864@75Hz
[ 13.627] (II) RADEON(0): Manufacturer's mask: 0
[ 13.627] (II) RADEON(0): Supported standard timings:
[ 13.627] (II) RADEON(0): #0: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 13.627] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 13.627] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 13.627] (II) RADEON(0): Supported detailed timing:
[ 13.627] (II) RADEON(0): clock: 106.5 MHz Image Size: 410 x 257 mm
[ 13.627] (II) RADEON(0): h_active: 1440 h_sync: 1520 h_sync_end 1672 h_blank_end 1904 h_border: 0
[ 13.627] (II) RADEON(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 934 v_border: 0
[ 13.627] (II) RADEON(0): Serial No: QCW063507079
[ 13.627] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 82 kHz, PixClock max 145 MHz
[ 13.627] (II) RADEON(0): Monitor name: Q19wb
[ 13.627] (II) RADEON(0): EDID (in hex):
[ 13.627] (II) RADEON(0): 00ffffffffffff005a631eb701010101
[ 13.627] (II) RADEON(0): 2310010308291a782edc55a359489e24
[ 13.627] (II) RADEON(0): 115054bfef8095008180814001010101
[ 13.627] (II) RADEON(0): 0101010101019a29a0d0518422305098
[ 13.627] (II) RADEON(0): 36009a011100001c000000ff00514357
[ 13.627] (II) RADEON(0): 3036333530373037390a000000fd0038
[ 13.627] (II) RADEON(0): 4b1e520e000a202020202020000000fc
[ 13.627] (II) RADEON(0): 0051313977620a202020202020200082
[ 13.627] (II) RADEON(0): Printing probed modes for output DVI-0
[ 13.627] (II) RADEON(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 13.627] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 13.627] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 13.627] (II) RADEON(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 13.627] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 13.628] (II) RADEON(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
[ 13.628] (II) RADEON(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 13.628] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 13.628] (II) RADEON(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 13.628] (II) RADEON(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 13.628] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 13.628] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 13.628] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 13.628] (II) RADEON(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
[ 13.628] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 13.628] (II) RADEON(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 13.628] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 13.628] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 13.628] (II) RADEON(0): EDID for output S-video
[ 13.628] (II) RADEON(0): Output VGA-0 connected
[ 13.628] (II) RADEON(0): Output DVI-0 connected
[ 13.628] (II) RADEON(0): Output S-video disconnected
[ 13.628] (II) RADEON(0): Using exact sizes for initial modes
[ 13.628] (II) RADEON(0): Output VGA-0 using initial mode 1440x900
[ 13.628] (II) RADEON(0): Output DVI-0 using initial mode 1440x900
[ 13.628] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 13.628] (II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:2000000 visible:1e52000
[ 13.628] (II) RADEON(0): EXA: Driver will not allow EXA pixmaps in VRAM
[ 13.628] (**) RADEON(0): Display dimensions: (440, 250) mm
[ 13.628] (**) RADEON(0): DPI set to (83, 91)
[ 13.628] (II) Loading sub module "fb"
[ 13.628] (II) LoadModule: "fb"
[ 13.629] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 13.629] (II) Module fb: vendor="X.Org Foundation"
[ 13.629] compiled for 1.10.1, module version = 1.0.0
[ 13.629] ABI class: X.Org ANSI C Emulation, version 0.4
[ 13.629] (II) Loading sub module "ramdac"
[ 13.629] (II) LoadModule: "ramdac"
[ 13.629] (II) Module "ramdac" already built-in
[ 13.629] (II) Loading sub module "exa"
[ 13.629] (II) LoadModule: "exa"
[ 13.630] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 13.630] (II) Module exa: vendor="X.Org Foundation"
[ 13.630] compiled for 1.10.1, module version = 2.5.0
[ 13.630] ABI class: X.Org Video Driver, version 10.0
[ 13.630] (II) UnloadModule: "vesa"
[ 13.630] (II) Unloading vesa
[ 13.630] (II) UnloadModule: "fbdev"
[ 13.630] (II) Unloading fbdev
[ 13.630] (II) UnloadModule: "fbdevhw"
[ 13.630] (II) Unloading fbdevhw
[ 13.630] (--) Depth 24 pixmap format is 32 bpp
[ 13.630] (II) RADEON(0): [DRI2] Setup complete
[ 13.630] (II) RADEON(0): [DRI2] DRI driver: r300
[ 13.631] (II) RADEON(0): Front buffer size: 5244K
[ 13.631] (II) RADEON(0): VRAM usage limit set to 23223K
[ 13.631] (==) RADEON(0): Backing store disabled
[ 13.631] (II) RADEON(0): Direct rendering enabled
[ 13.631] (II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
[ 13.631] (II) RADEON(0): Setting EXA maxPitchBytes
[ 13.631] (II) EXA(0): Driver allocated offscreen pixmaps
[ 13.631] (II) EXA(0): Driver registered support for the following operations:
[ 13.631] (II) Solid
[ 13.631] (II) Copy
[ 13.631] (II) Composite (RENDER acceleration)
[ 13.631] (II) UploadToScreen
[ 13.631] (II) DownloadFromScreen
[ 13.631] (II) RADEON(0): Acceleration enabled
[ 13.631] (==) RADEON(0): DPMS enabled
[ 13.631] (==) RADEON(0): Silken mouse enabled
[ 13.631] (II) RADEON(0): Set up textured video
[ 13.631] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 13.682] (--) RandR disabled
[ 13.682] (II) Initializing built-in extension Generic Event Extension
[ 13.682] (II) Initializing built-in extension SHAPE
[ 13.682] (II) Initializing built-in extension MIT-SHM
[ 13.682] (II) Initializing built-in extension XInputExtension
[ 13.682] (II) Initializing built-in extension XTEST
[ 13.682] (II) Initializing built-in extension BIG-REQUESTS
[ 13.682] (II) Initializing built-in extension SYNC
[ 13.682] (II) Initializing built-in extension XKEYBOARD
[ 13.682] (II) Initializing built-in extension XC-MISC
[ 13.682] (II) Initializing built-in extension SECURITY
[ 13.682] (II) Initializing built-in extension XINERAMA
[ 13.682] (II) Initializing built-in extension XFIXES
[ 13.682] (II) Initializing built-in extension RENDER
[ 13.682] (II) Initializing built-in extension RANDR
[ 13.682] (II) Initializing built-in extension COMPOSITE
[ 13.682] (II) Initializing built-in extension DAMAGE
[ 13.682] (II) Initializing built-in extension GESTURE
[ 13.696] (II) AIGLX: Trying DRI driver /usr/lib/dri/r300_dri.so
[ 13.725] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 13.725] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 13.725] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 13.725] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 13.725] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 13.726] (II) AIGLX: Loaded and initialized r300
[ 13.726] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 13.777] (II) RADEON(0): Setting screen physical size to 380 x 238
[ 13.790] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[ 13.805] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 13.805] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 13.805] (II) LoadModule: "evdev"
[ 13.806] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.806] (II) Module evdev: vendor="X.Org Foundation"
[ 13.806] compiled for 1.10.0.902, module version = 2.6.0
[ 13.806] Module class: X.Org XInput Driver
[ 13.806] ABI class: X.Org XInput driver, version 12.3
[ 13.806] (II) Using input driver 'evdev' for 'Power Button'
[ 13.806] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.806] (**) Power Button: always reports core events
[ 13.806] (**) Power Button: Device: "/dev/input/event1"
[ 13.807] (--) Power Button: Found keys
[ 13.807] (II) Power Button: Configuring as keyboard
[ 13.807] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 13.807] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 13.807] (**) Option "xkb_rules" "evdev"
[ 13.807] (**) Option "xkb_model" "pc105"
[ 13.807] (**) Option "xkb_layout" "us"
[ 13.809] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 13.809] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 13.809] (II) Using input driver 'evdev' for 'Power Button'
[ 13.810] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.810] (**) Power Button: always reports core events
[ 13.810] (**) Power Button: Device: "/dev/input/event0"
[ 13.810] (--) Power Button: Found keys
[ 13.810] (II) Power Button: Configuring as keyboard
[ 13.810] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 13.810] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 13.810] (**) Option "xkb_rules" "evdev"
[ 13.810] (**) Option "xkb_model" "pc105"
[ 13.810] (**) Option "xkb_layout" "us"
[ 13.813] (II) config/udev: Adding input device HDA Intel Speaker at Ext Rear Jack (/dev/input/event10)
[ 13.813] (II) No input driver/identifier specified (ignoring)
[ 13.814] (II) config/udev: Adding input device HDA Intel HP Out at Ext Front Jack (/dev/input/event11)
[ 13.814] (II) No input driver/identifier specified (ignoring)
[ 13.814] (II) config/udev: Adding input device HDA Intel Line In at Ext Rear Jack (/dev/input/event5)
[ 13.814] (II) No input driver/identifier specified (ignoring)
[ 13.815] (II) config/udev: Adding input device HDA Intel Mic at Ext Front Jack (/dev/input/event6)
[ 13.815] (II) No input driver/identifier specified (ignoring)
[ 13.815] (II) config/udev: Adding input device HDA Intel Mic at Ext Rear Jack (/dev/input/event7)
[ 13.815] (II) No input driver/identifier specified (ignoring)
[ 13.815] (II) config/udev: Adding input device HDA Intel Speaker at Ext Rear Jack (/dev/input/event8)
[ 13.815] (II) No input driver/identifier specified (ignoring)
[ 13.816] (II) config/udev: Adding input device HDA Intel Speaker at Ext Rear Jack (/dev/input/event9)
[ 13.816] (II) No input driver/identifier specified (ignoring)
[ 13.818] (II) config/udev: Adding input device Dell Dell USB Keyboard (/dev/input/event2)
[ 13.818] (**) Dell Dell USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 13.818] (II) Using input driver 'evdev' for 'Dell Dell USB Keyboard'
[ 13.818] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.818] (**) Dell Dell USB Keyboard: always reports core events
[ 13.818] (**) Dell Dell USB Keyboard: Device: "/dev/input/event2"
[ 13.818] (--) Dell Dell USB Keyboard: Found keys
[ 13.818] (II) Dell Dell USB Keyboard: Configuring as keyboard
[ 13.818] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input2/event2"
[ 13.818] (II) XINPUT: Adding extended input device "Dell Dell USB Keyboard" (type: KEYBOARD)
[ 13.818] (**) Option "xkb_rules" "evdev"
[ 13.818] (**) Option "xkb_model" "pc105"
[ 13.818] (**) Option "xkb_layout" "us"
[ 13.821] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[ 13.821] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.821] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.821] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.821] (**) Logitech USB Receiver: always reports core events
[ 13.821] (**) Logitech USB Receiver: Device: "/dev/input/event3"
[ 13.821] (--) Logitech USB Receiver: Found keys
[ 13.821] (II) Logitech USB Receiver: Configuring as keyboard
[ 13.821] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input3/event3"
[ 13.821] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 13.821] (**) Option "xkb_rules" "evdev"
[ 13.821] (**) Option "xkb_model" "pc105"
[ 13.821] (**) Option "xkb_layout" "us"
[ 13.823] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event4)
[ 13.823] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 13.823] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.823] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.823] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.823] (**) Logitech USB Receiver: always reports core events
[ 13.823] (**) Logitech USB Receiver: Device: "/dev/input/event4"
[ 13.824] (--) Logitech USB Receiver: Found 20 mouse buttons
[ 13.824] (--) Logitech USB Receiver: Found scroll wheel(s)
[ 13.824] (--) Logitech USB Receiver: Found relative axes
[ 13.824] (--) Logitech USB Receiver: Found x and y relative axes
[ 13.824] (--) Logitech USB Receiver: Found absolute axes
[ 13.824] (II) evdev-grail: failed to open grail, no gesture support
[ 13.824] (--) Logitech USB Receiver: Found keys
[ 13.824] (II) Logitech USB Receiver: Configuring as mouse
[ 13.824] (II) Logitech USB Receiver: Configuring as keyboard
[ 13.824] (II) Logitech USB Receiver: Adding scrollwheel support
[ 13.824] (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 13.824] (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 13.824] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/input/input4/event4"
[ 13.824] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 13.824] (**) Option "xkb_rules" "evdev"
[ 13.824] (**) Option "xkb_model" "pc105"
[ 13.824] (**) Option "xkb_layout" "us"
[ 13.825] (II) Logitech USB Receiver: initialized for relative axes.
[ 13.825] (WW) Logitech USB Receiver: ignoring absolute axes.
[ 13.825] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 13.825] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 13.825] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 13.825] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 13.825] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 13.825] (II) No input driver/identifier specified (ignoring)
[ 14.362] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 14.362] (II) RADEON(0): Using hsync ranges from config file
[ 14.362] (II) RADEON(0): Using vrefresh ranges from config file
[ 14.362] (II) RADEON(0): Printing DDC gathered Modelines:
[ 14.362] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 14.362] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 14.362] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 14.362] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 14.362] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 14.362] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 14.362] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 14.362] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 14.362] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 14.362] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 14.362] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 14.362] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 14.362] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 14.362] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 14.362] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 14.363] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 14.363] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 14.363] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 14.477] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 14.477] (II) RADEON(0): Using hsync ranges from config file
[ 14.477] (II) RADEON(0): Using vrefresh ranges from config file
[ 14.477] (II) RADEON(0): Printing DDC gathered Modelines:
[ 14.478] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 14.478] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 14.478] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 14.478] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 14.478] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 14.478] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 14.478] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 14.478] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 14.478] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 14.478] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 14.478] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 14.478] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 14.478] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 14.478] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 14.478] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 14.478] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 14.478] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 14.478] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 14.594] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 14.594] (II) RADEON(0): Using hsync ranges from config file
[ 14.594] (II) RADEON(0): Using vrefresh ranges from config file
[ 14.594] (II) RADEON(0): Printing DDC gathered Modelines:
[ 14.594] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 14.594] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 14.594] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 14.595] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 14.595] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 14.595] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 14.595] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 14.595] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 14.595] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 14.595] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 14.595] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 14.595] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 14.595] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 14.595] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 14.595] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 14.595] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 14.595] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 14.595] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 14.709] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 14.709] (II) RADEON(0): Using hsync ranges from config file
[ 14.709] (II) RADEON(0): Using vrefresh ranges from config file
[ 14.709] (II) RADEON(0): Printing DDC gathered Modelines:
[ 14.709] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 14.709] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 14.709] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 14.709] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 14.709] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 14.709] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 14.709] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 14.709] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 14.709] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 14.709] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 14.709] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 14.709] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 14.709] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 14.709] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 14.710] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 14.710] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 14.710] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 14.710] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 28.030] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 28.030] (II) RADEON(0): Using hsync ranges from config file
[ 28.030] (II) RADEON(0): Using vrefresh ranges from config file
[ 28.030] (II) RADEON(0): Printing DDC gathered Modelines:
[ 28.030] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 28.030] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 28.030] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 28.030] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 28.031] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 28.031] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 28.031] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 28.031] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 28.031] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 28.031] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 28.031] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 28.031] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 28.031] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 28.031] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 28.031] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 28.031] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 28.031] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 28.031] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 28.146] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 28.146] (II) RADEON(0): Using hsync ranges from config file
[ 28.146] (II) RADEON(0): Using vrefresh ranges from config file
[ 28.146] (II) RADEON(0): Printing DDC gathered Modelines:
[ 28.146] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 28.146] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 28.146] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 28.146] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 28.146] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 28.146] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 28.146] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 28.146] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 28.146] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 28.146] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 28.146] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 28.146] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 28.146] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 28.146] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 28.146] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 28.146] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 28.146] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 28.146] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 28.290] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 28.291] (II) RADEON(0): Using hsync ranges from config file
[ 28.291] (II) RADEON(0): Using vrefresh ranges from config file
[ 28.291] (II) RADEON(0): Printing DDC gathered Modelines:
[ 28.291] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 28.291] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 28.291] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 28.291] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 28.291] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 28.291] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 28.291] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 28.291] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 28.291] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 28.291] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 28.291] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 28.291] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 28.291] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 28.291] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 28.291] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 28.291] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 28.291] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 28.291] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 30.025] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 30.025] (II) RADEON(0): Using hsync ranges from config file
[ 30.025] (II) RADEON(0): Using vrefresh ranges from config file
[ 30.025] (II) RADEON(0): Printing DDC gathered Modelines:
[ 30.025] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 30.025] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 30.025] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 30.025] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 30.025] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 30.025] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 30.025] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 30.025] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 30.026] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 30.026] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 30.026] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 30.026] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 30.026] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 30.026] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 30.026] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 30.026] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 30.026] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 30.026] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 37.044] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 37.044] (II) RADEON(0): Using hsync ranges from config file
[ 37.044] (II) RADEON(0): Using vrefresh ranges from config file
[ 37.044] (II) RADEON(0): Printing DDC gathered Modelines:
[ 37.044] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 37.044] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 37.044] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 37.044] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 37.044] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 37.044] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 37.044] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 37.044] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 37.044] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 37.044] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 37.044] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 37.044] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 37.044] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 37.044] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 37.044] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 37.044] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 37.044] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 37.044] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 200.621] (II) RADEON(0): EDID vendor "VSC", prod id 46878
[ 200.621] (II) RADEON(0): Using hsync ranges from config file
[ 200.621] (II) RADEON(0): Using vrefresh ranges from config file
[ 200.621] (II) RADEON(0): Printing DDC gathered Modelines:
[ 200.621] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 200.621] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 200.621] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 200.621] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 200.621] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 200.621] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 200.621] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 200.622] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 200.622] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 200.622] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 200.622] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 200.622] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 200.622] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 200.622] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 200.622] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 200.622] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 200.622] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 200.622] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)

[Breslau]

Hey all,

skimmed the thread and didn't see my exact issue, so here goes

- upgraded from 10.10 through update manager

- first boot went into CLI after dumping some error messages about starting X and not finding nvidia stuff

- yes i have nvidia

- found the nvidia drivers are still/already installed

- booted again, got into grub and chose the generic non pae kernel

- X starts OK, i get the message about "ubuntu classic.. ", but desktop is up and running

any reason for me not to continue on with this kernel? is there a workaround to get the kernel working the upgrade installs as the default?

TIA

[MAFoElffen]

Thanks for trying to help! Hopefully I can keep up :)

On the way out the door at the moment. Will look at this again when I get back in... but initially looks likes it fails to load a module early in the xorg load... Could be a clue there. Will have to look closer when I get back in.

[johnthei]

I had a bit of time unexpectedly to try stuff. great. total disaster. I saw multiple 'solutions' so I tried one: Sudo apt-get install Nvidia-current running in the only mode {ubuntu Classic] that works. Recovery console has useless graphics, classic is only one running that I can see anything on and work with

I got to terminal, did the sudo and great...got 4 files to download, it did, and then I rebooted.

Dead black screen saying on the monitor Input signal out of range, change settings to 1280 x 1024.

I am back to Windows XP on a different hard drive, to access this forum.
I found from prior info I have GEforce 4MX nvidia, it is integrated into the motherboard, not a seperate video card.

I think I may have to go back to 9.4 version, I think that was the last one I had any 'luck' with. the 10 versions did NOT have graphics that worked even with 22 different attempt to do all sorts of work arounds from all the notes I have on this video problem.

oh the classic graphics are 1024 x 768 it seems. I did see also after the downloads the proprietary drivers, had a new one but it said it was activated but not in use...

which is something I remember seeing allot in the 10.04 version problems, no matter what I did it did not go to 'in use'

[johnthei]

oh I could not get a safe mode low graphics to boot, no idea how. did not work whatever i tried, so that is why i tried the sudo apt-get install nvidia-current.

[MAFoElffen]

oh I could not get a safe mode low graphics to boot, no idea how. did not work whatever i tried, so that is why i tried the sudo apt-get install nvidia-current.
Get to any kind of text console... even if you have to follow the instructions to edit the kernel boot line to boot into tty text.

From the command line, your going to remane the xorg.conf so that it's not found. That will get it to not use the driver you just installed and get you back to were you were... and to remove the driver.


sudo mv /etc/X11/xorg.conf /etc/x11.conf.old
sudo apt-get remove --purge nvidia-current
sudo reboot

The last command will shut everything down cleanly and reboot your pc. At the grub menu press the "e" key > go down to the line that starts with the word "linux" go about 2/3rds of that line // after where it has the kernel and after where it says "splash" and add "nomodeset" > hit <cntrl><x>... It will boot. Pick Ubuntu Classic at the login.

After it boots in the graphical session > Adminstration > Find Additional drivers > Tell me what it says...

From a terminal


sudo hwinfo --framebuffer
and post the results. I would like to see what linux says the card and chipset is.

[MAFoElffen]

@Randahl Graves-


On the way out the door at the moment. Will look at this again when I get back in... but initially looks likes it fails to load a module early in the xorg load... Could be a clue there. Will have to look closer when I get back in.
Do you know if your Radeon card requires"fglrx"? I kno wsome do because support dropped for their cards and there is no others support for them except that // then some don't need it because their is other drivers that do sopport them. The reason I ask, is that your config said it match up the fglrx driver as yours > then it fails to load and goes south from there

Could you post your /boot/grub.grub.cfg and /etc/default/grub please? Just curious what kernel and what grub is passing it..

[MAFoElffen]

Hello,

I have a similar problem :

Normal boot : empty screen but with ubuntu background
Text boot : I can log in and then I'm able to start graphical session (startx). My background loads corectly and I get a strange window titled "unlock keyring" (again perfectly displayed, even with shadows and round borders) but nothing more.
If I type my password and validate, then nothing append.
From here all I can do is ctrl+alt+del (open shutdown menu - correctly displyed) or lock my session (crtl+L) and open a terminal. For instance, these are the only two things I was able to do.



Is my problem related to this thread?
I'm lost... Help me :confused:

I have a Radeon HD 3450 (ATI technologies Inc RV620) and I run on a 64bits machine

Thank you already.

edit : when I log as root, I have the same purple default background and a loading cursor that never stops.

Not sure at the moment. When did this problem start? Was this after an upgrade or fresh install? Was the version of Ubuntu tunning graphics in this version at all before that? Did you notice any security updates or errors during updates? .

Have you installed any video drivers for it yet? Did you ever have graphics in Ubuntu? (Info please - For a start...)

[MAFoElffen]

Hey all,

skimmed the thread and didn't see my exact issue, so here goes

- upgraded from 10.10 through update manager

- first boot went into CLI after dumping some error messages about starting X and not finding nvidia stuff

- yes i have nvidia

- found the nvidia drivers are still/already installed

- booted again, got into grub and chose the generic non pae kernel

- X starts OK, i get the message about "ubuntu classic.. ", but desktop is up and running

any reason for me not to continue on with this kernel? is there a workaround to get the kernel working the upgrade installs as the default?

TIA
Okay then <> trying to follow this. Is your linux kernel 32bit or 64bit? Assuming 32bit since you mentioned PAE. Is this desktop or server... as standard 32bit kernel would be generic, with server as PAE(?)

But anyway, it sounds like you instead used an older kernel(?) and everything works fine?

Sort of clarify those points and we'll go on... because using the old kernel is just a short-term workaround. There is a way to tewll the current kernel to either ignor being new or to try to set it up correctly... The "auto," find the settings and set it for you is confused at the moment.

[Breslau]

Okay then <> trying to follow this. Is your linux kernel 32bit or 64bit? Assuming 32bit since you mentioned PAE. Is this desktop or server... as standard 32bit kernel would be generic, with server as PAE(?)

But anyway, it sounds like you instead used an older kernel(?) and everything works fine?

Sort of clarify those points and we'll go on... because using the old kernel is just a short-term workaround. There is a way to tewll the current kernel to either ignor being new or to try to set it up correctly... The "auto," find the settings and set it for you is confused at the moment.

right now i'm on 2.6.38-8-generic

the upgrade made 2.6.38-generic-pae the default boot kernel


*should* be desktop/32 bit

[Randal Graves]

Good morning. I only have one monitor hooked up at the moment, dunno if that matters. (Graphics are still bad)


/etc/defualt/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"




boot/grub/grub.cfg

# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=cb57544a-5084-4fe2-aa54-a49f35e2cb69 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=cb57544a-5084-4fe2-aa54-a49f35e2cb69 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

[Blasphemist]

right now i'm on 2.6.38-8-generic

the upgrade made 2.6.38-generic-pae the default boot kernel


*should* be desktop/32 bit

I've seen a couple video issue related posts now where the pae kernel has issues but not the generic. I'd like to know if you need the pae kernel, 4GB or more of memory and 32 bit cpu, or if it is just the default 32 bit kernel now. If you don't need it this may need reported as a bug. It looks like to me, but I am no expert on this, like the grub2 documentation shows how to set the default kernel. https://help.ubuntu.com/community/Grub2#Boot a Specific Kernel Manually. There may well be a better/safer way to set this.

[Breslau]

I've seen a couple video issue related posts now where the pae kernel has issues but not the generic. I'd like to know if you need the pae kernel, 4GB or more of memory and 32 bit cpu, or if it is just the default 32 bit kernel now. If you don't need it this may need reported as a bug. It looks like to me, but I am no expert on this, like the grub2 documentation shows how to set the default kernel. https://help.ubuntu.com/community/Grub2#Boot a Specific Kernel Manually. There may well be a better/safer way to set this.


well i used the startupmanager to set the kernel i'm on now to the default.

don't even know what pae gives you

[Blasphemist]

This is the information on the pae kernel that I read. I believe it may be default now for 32 bit to cover for people with 4GB + of memory.

[Breslau]

This is the information on the pae kernel that I read. I believe it may be default now for 32 bit to cover for people with 4GB + of memory.


ok, i'm under 4 here

[MAFoElffen]

This is the information on the pae kernel that I read. I believe it may be default now for 32 bit to cover for people with 4GB + of memory.
Did you have a link for that?

I'm a little confused on this now also... -generic was 32bit desktop. -pae was 32bit server... -pae was optimised f0r server services and the graphics/desktop services on it "sucked." But the graphics issues and bad perfomance for desktop was okay, because that wasn't where the priorities on a server kernel should be. That was my experience on it through natty testing. Up through a month ago, there still was a separate 32bit -pae for server and 32bit -generic for desktops.

Why did I want to see those 2 grub files? The grub.cfg file is built by the files contained in /boot/grub.d and /etc/default/grub... Grub.cfg is not "the file" you change, but you can see what is affected by grub.defaults by looking at these 2 files. (You can also see what "has" been edited and changed, by looking at these 2 files...)

Yes, it "is" 32bit, ...and if they use startup-manager, it edits straigth to the grub.cfg... It is not permanent nor what is supposed to be "correct" but it works. ...and doesn't check or care if it is 32bit. But it's edits still work most of the time. Because of that, one update (automatic. scheduled or manually) of update-grub > startup-manager's edits are lost > the user will have to re-run the startup-manager again to recreate what it did before. (It that is what they are using...)

[Blasphemist]

Did you have a link for that?

I'm a little confused on this now also... -generic was 32bit desktop. -pae was 32bit server... -pae was optimised f0r server services and the graphics/desktop services on it "sucked." That was my experience on it through natty testing. Up through a month ago, there still was a separate 32bit -pae for server and 32bit -generic for desktops.

Why did I want to see those 2 grub files? The grub.cfg file is built by the files contained in /boot/grub.d and /etc/default/grub... Grub.cfg is not "the file" you change, but you can see what is affected by grub.defaults by looking at these 2 files. (You can also see what "has" been edited and changed, by looking at these 2 files...)

Yes, it "is" 32bit, ...and if they use startup-manager, it edits straigth to the grub.cfg... It is not permanent nor what is supposed to be "correct" but it works. ...and doesn't check or care if it is 32bit. But those edits still work most of the time. Because of that, one update (automatic. scheduled or manually) of update-grub and the user will have to run the startup-manager again to recreate what it did before.
This is what I read about the pae kernel.
http://en.wikipedia.org/wiki/Physical_Address_Extension
Note this from the OS support section.

Linux
The Linux kernel includes full PAE mode support starting with version 2.3.23,[6] enabling access of up to 64 GB of memory on 32-bit machines. A PAE-enabled Linux-kernel requires that the CPU also support PAE. As of 2009,[7] some common Linux distributions have started to use a PAE-enabled kernel as the distribution-specific default[7] because it adds the NX bit. [8]
There are a number of threads regarding X issues and this kernel. I just answered one and wasn't sure just what the best option for setting the default kernel to generic is. He has pae and generic and only generic works. In that post I noted another thread where the OP just removed the pae and generic was promoted automatically. http://ubuntuforums.org/showthread.php?t=1761593&page=2

[MAFoElffen]

Good morning. I only have one monitor hooked up at the moment, dunno if that matters. (Graphics are still bad)


/etc/defualt/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
boot/grub/grub.cfg
[CODE]#if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root cb57544a-5084-4fe2-aa54-a49f35e2cb69
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=cb57544a-5084-4fe2-aa54-a49f35e2cb69 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}

You have an RV370 and all your config files look pretty much untouched and unmodified.


ATI has dropped suppport for all RV200-500 cards starting with 9.4 and future drivers for linux and windows
So you're stuch with opensource drivers. If there was an older propietary driver installed, it would have had to have been removed before update processes for it to find the opensource drivers. Instruction for all that are here:
https://help.ubuntu.com/community/RadeonDriver
Those instruction have been updated for natty.

In which issues with that is still changing:
"Changed in xserver-xorg-driver-ati": as recent as 20110.2.03
So, yes. If fglrx was propietary, then it had to be uninstalled for the new opensource drivers to be found, installed and used. (last status of that for this card.) Instructions for that are in the link above. Also note that you should also open your /etc/default/grub file and edit the following.

Change the line


# GRUB_GFXMODE=640x480
to


GRUB_GFXMODE=640x480x24
Change the line


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
To


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
And add a line saying


GRUB_GFXPAYLOAD=text

Run


sudo update-grub

[Randal Graves]

Thanks for the info, I'll see what I can do and report back.

[pssturges]

Hi,

After 3 weeks of frustration trying to get this to work I'm about at the end of my capabilities (and patience!). I started by upgrading from 10.10, but in attempt to fix the problem I did a fresh install. About 10 fresh installs later I'm not a whole lot closer to getting this fixed.

My system is a Medion Akoya laptop with Nvidia 8600m gs graphics.

Here's where I'm at so far:

1) 11.04 live cd boots
2) fresh install successful
3) new system boots without proprietry drivers. It doesn't seem to be able to detect my screen's native resolution (1400x900) where as 10.04 does.
4) install nvidia-current, run nvidia-xconfig
5) after reboot grub appears then black screen. After about 30 sec no more hdd activity.
6) reboot and manually edit grub kernel boot line as follows:

linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash acpi=off nomodeset
This works usually once! The system boots, nvidia drivers are loaded and the everything seems to work as it should.
7) Subsequent reboots do not work no matter how I edit the kernel boot line!
8 ) removing xorg.conf allows system to boot again without nvidia drivers.
9) when the blank screen occurs, I can't get a terminal by pressing <ctrl><Alt>F1 etc. Screen stays blank
10) adding "text" to kernel boot line yealds blanks screen also.

I have tried going back to 2.6.37 and also grub 1.98 without success(although I'm not 100% confident I did this correctly)

The really frustrating thing is that some things that I have tried have work once! If I have success with something, I try a reboot to confirm and it will not work anymore. Even some of the things I have descibed above work most of the time but not always!

At this point in time I feel as though I'm going around in circles and don't have a clear plan of attack. If someone could give me some sort of guidance as to where to go from here, it would be much appreciated.

Phil

[johnthei]

I had a bit of time unexpectedly to try stuff. great. total disaster. I saw multiple 'solutions' so I tried one: Sudo apt-get install Nvidia-current running in the only mode {ubuntu Classic] that works. Recovery console has useless graphics, classic is only one running that I can see anything on and work with

I got to terminal, did the sudo and great...got 4 files to download, it did, and then I rebooted.

Dead black screen saying on the monitor Input signal out of range, change settings to 1280 x 1024.

I am back to Windows XP on a different hard drive, to access this forum.
I found from prior info I have GEforce 4MX nvidia, it is integrated into the motherboard, not a seperate video card.

I think I may have to go back to 9.4 version, I think that was the last one I had any 'luck' with. the 10 versions did NOT have graphics that worked even with 22 different attempt to do all sorts of work arounds from all the notes I have on this video problem.

oh the classic graphics are 1024 x 768 it seems. I did see also after the downloads the proprietary drivers, had a new one but it said it was activated but not in use...

which is something I remember seeing allot in the 10.04 version problems, no matter what I did it did not go to 'in use'

Tried a new approach. Installed fresh 9.10 version, reformat everything. then enabled nvidia driver. all works. then start upgrade of everything, everything the upgrade manager wants, 10., 10.10, all fine. get to 11.04 upgrade to it. takes lots of time doing each of these.
New grub. hum. all other versions gone. still good resolution.
then it wont boot, back the dead black screen saying wrong resolution.

I dont know how to get anywhere again with dead black screen, no command seems to do a thing.



So I try to reformat again, with disc of 10.4 or 10.10. fails. gets so far on each, some problem wont let disc load and install.
go back to 9.10 version, start it all again, as of now I am up the the most current 10.10 with all the updates. it wants to upgrade to 11.04.

so after all this time used up this weekend, I will wait til later when I get time, and put 11.04 on separate partition I think, so I can try the 100 fixes on it without having to do all of this over and over again.

[MAFoElffen]

(EDITED)
Medion Akoya laptop with Nvidia 8600m gs graphics.

1) 11.04 live cd boots
2) fresh install successful
3) new system boots without proprietry drivers. It doesn't seem to be able to detect my screen's native resolution (1400x900) where as 10.04 does.
4) install nvidia-current, run nvidia-xconfig
5) after reboot grub appears then black screen. After about 30 sec no more hdd activity.
6) reboot and manually edit grub kernel boot line as follows:

linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash acpi=off nomodesetThis works usually once! The system boots, nvidia drivers are loaded and the everything seems to work as it should.
7) Subsequent reboots do not work no matter how I edit the kernel boot line!
8 ) removing xorg.conf allows system to boot again without nvidia drivers.
9) when the blank screen occurs, I can't get a terminal by pressing <ctrl><Alt>F1 etc. Screen stays blank
10) adding "text" to kernel boot line yealds blanks screen also.
11) tried going back to 2.6.37 and grub 1.98 without success

PhilI need to know 2 things before we start...
A. Is the kernel 32bit or 64bit?
B. Is the video chipset the only video chipset? Well your laptop falls into a sort of gray area of time in technology were for a while there was a type or grouping of laptops called "gaming laptops" that explored certain technologies. Your "brand," like others, had offered some of these with nvidia graphics and others with radeon graphics... There was some of these gaming laptops (and I'm not familiar with your brand, so I need feedback from you or others to tell me) that had those chipsets "behind" other video chipsets (sandy bridge, optimus, etc.). The current bug with these is that the current basic linux processes, as they try to query and set graphics, are seeing the first chipset and stopping <> not seeing the chipsets beyond that. If it is one of "these," then tell me first and don't do any of the instructions below, because the instructions and advice for those will be completely different!!!

Here's my plan:
1. Lets get you backed off to what should be a somewhat measurable current starting place.
2. Then we'll get you configured in a manner that should accept the changes we are going to try.
3. We will apply patches and fixes to correct some common problems and ommission that have come up.
4. Then we are going to load our drivers and our changes.

Getting back to a starting point:
Remove, purge and reinstall Grub version 1.99 from a current 11.04 LiveCD. follow the instructions from here, Item number 12:
http://ubuntuforums.org/showthread.php?t=1195275

Gathering Data.
What would be helpful here is for you to run


sudo hwinfo --framebuffer
sudo hwinfo --monitor
And post the results here. Reasons?

a. If the data from --framebuffer says the hardware is anything other than nvidia, stop right there. That would indicate that your nvidia chipset is "behind" another video chipset. If it comes to this, look here:
http://www.martin-juhl.dk/

b. ACPI=off currently in your kernel boot line. If that worked as a workaround for you and it helped <> It might have helped with your graphics, but will cause other problems, especially with laptops. I have a workaround for that by manually setting the GFXMODE and VGA mode. We need data from the above commands to do that.

Look at the data returned by both those commands. Look for a resolution that (closely) matches between the 2. We pick the resolution from the --framebuffer list. We take the hex "mode" of that resolution and comvert it to a decimal number. (it will be 3 digits then, example 771.) We will use that in a kernel boot setmode switch, vga=xxx, where xxx= the decimal number you came up with from your hex graphics mode.

Use the same resolution (thst you got the hex/decimal mode number from) and we will add it to grub's default file. Open a terminal and


cd /etc/default/
sudo gedit grub
The first line we want to change in this file looks like this:


# GRUB_GFXMODE-640x480
The new default is auto (notice this is currently commented out). The default is 1.98 was set at 640x480. This version is having a problem sometime when this is set to auto - querying and setting to an invalid mode. So we are going to set this manually, by all 3 parameters, instead of the 2...


GRUB_GFXMODE=640x480x24
You could actually set this to any mode returned in the data from "hwinfo --framebuffer." You can also add multiple resolutions by separating them with a semi-colon. What it is supposed to do, if set that way, is to go through the list until it finds one that works. This "mode" sets the grub menu resolution > But this mode also gets passed on to the kernel and to xorg through kms. By setting this manually, we are trying to pass it "valid" modes.

(By setting the above 2, GFXMODE and vga=xxx, you should no longer need the acpi=off switch.)

While we are in this file, we have more changes to do... Add this line


GRUB_GFXPAYLOAD_LINUX=text
Which is a workaround to tell the kerenl to ignore invalid graphics calls on boot and not pass them on. Next we are going to add our boot options.


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset vga=xxx vmalloc-192MB acpi_osi=/"Linux/" "
Remember to substitute the xxx in the vga switch to the mode you picked for your resolution. The nomodeset is hopefully just "temporary," until your drivers are loaded, but we'll see.

Save and exit. Run update-grub to pick up the changes. Reboot.

Now to install a patch/fix kind of thing. Start up synaptic > search on "linux-headers-generic" What you are looking for the the generic linux kernel headers that are installed. Select and mark this for re-install and apply. In you have -server or -pae, you would do those instead... There was a problem somewhere along the way in the natty repo's where this got missing or corrupted on some machines. When the graphics drivers are installed, it uses these files to create them for the current kernel.

Next, you have previous nvidia drivers on your system and some of them keave resident files that conflict with some of the newer drivers... So we will remove purge them and install the ones I think you need....


sudo apt-get remove --purge nvidia*
This will remove all your nvidia installs that are there now.

Now you have to download the correct driver for "your" card. You can try doing nvidia-current if you think that will help, but for some people, that brought about the same problems.

Use the nvidia'---> 173 driver, . (i think the normal choices are 96 for really old cards, the 173 is for go 5 to 9 series, and the 185 is for later... but don't quote me on that!)


sudo apt-get update
sudo apt-get install nvidia-common
sudo apt-get install nvidia-settings
sudo apt-get install nvidia-glx-173
Obviously change the 173 to your number if your card is not in the Geofroce 5 to 9 series'. This installed the drivers manually.

Now you have to configure them:


sudoo nvidia-xconfig
Reboot. If it comes up in a graphics mode, start a termeinal and run


sudo nvidia-settings
Chnange your settings how you want, then apply and exit.

If it didn't come up at all, rename your xorg.conf and reboot to get back...

If your graphics still works, re-edit your /etc/default/grub file and remove the "nomodeset" switch from the kernel boot line > rerun update-grub and reboot. If it didn't comeup, re=add it back to the grub default file...

If after it did come up... and then if you are having problems with Compiz > then run:


compiz --replace

[MAFoElffen]

Tried a new approach. Installed fresh 9.10 version, reformat everything. then enabled nvidia driver. all works. then start upgrade of everything, everything the upgrade manager wants, 10., 10.10, all fine. get to 11.04 upgrade to it. takes lots of time doing each of these.
New grub. hum. all other versions gone. still good resolution.
then it wont boot, back the dead black screen saying wrong resolution.

I dont know how to get anywhere again with dead black screen, no command seems to do a thing.

So I try to reformat again, with disc of 10.4 or 10.10. fails. gets so far on each, some problem wont let disc load and install.
go back to 9.10 version, start it all again, as of now I am up the the most current 10.10 with all the updates. it wants to upgrade to 11.04.

so after all this time used up this weekend, I will wait til later when I get time, and put 11.04 on separate partition I think, so I can try the 100 fixes on it without having to do all of this over and over again.
1. What is your hardware (Desktop or laptop, CPU, Video)?
2. What ar you trying to install (32bit or 64bit0?
3. By the last paragraph, I'm thinking your plan would be great, because then we could
compare wat conf files and drivers are working and what can be tested, without severing you from the outside world.

[johnthei]

1. What is your hardware (Desktop or laptop, CPU, Video)?
2. What ar you trying to install (32bit or 64bit0?
3. By the last paragraph, I'm thinking your plan would be great, because then we could
compare wat conf files and drivers are working and what can be tested, without severing you from the outside world.

HP desktop, A320N pavillion i think it is, [at work now on other pc] 32 bit has built in graphics not separate video card.

yes, partitioning to its own area seems to me like something to try. on the installs a few times I got asked questions about grub and other stuff, a few times I just guessed as to what I thought was best, the default new install instead of keeping current editions.

will report back when i get time later this week to continue on it.
be seeing you

[spek578]

All right so i can install and boot into 32 bit 10.04 fine, but if i try a 64bit of ANY distro i get a black screen on live cd or after install, and the only way i can see anything is if i close the lid of my laptop and then open it. im on a gateway nv7915u with intel core i3.

[Randal Graves]

Change the line


# GRUB_GFXMODE=640x480
to


GRUB_GFXMODE=640x480x24
Change the line


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
To


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
And add a line saying


GRUB_GFXPAYLOAD=text
Run


sudo update-grub


Ok, I have my friend helping me and we edited the grub code. After editing the code we rebooted and tried to load Unity but received a message telling me I didnt have the hardware to run Unity, it then forced me to use Classic. I then went to monitor preferences and when I tried to activate the second monitor i got this error messge:


The selected configuration for displays does not fit available size requested =(3040, 900), minimum=(320-200), maximum=(1600,1600)After I rebooted I was able to use the dual monitors after turning down the resolution to 800 on both monitors to a combined width of 1600. So, Its working but the res sucks. Seems like were getting somewhere :D


I can live with this setup so I guess the only questions left are:

Will I ever be able to run Unity?

Can I fix the res?

[MAFoElffen]

Ok, I have my friend helping me and we edited the grub code. After editing the code we rebooted and tried to load Unity but received a message telling me I didnt have the hardware to run Unity, it then forced me to use Classic. I then went to monitor preferences and when I tried to activate the second monitor i got this error messge:

After I rebooted I was able to use the dual monitors after turning down the resolution to 800 on both monitors to a combined width of 1600. So, Its working but the res sucks. Seems like were getting somewhere :D

I can live with this setup so I guess the only questions left are:

Will I ever be able to run Unity?

Can I fix the res?
Run this command in a terminal


/usr/lib/nux/unity_support_test -p

It will tell you if you have the required hardware and packages to run Unity3D. Don't dispare if it says you "can't." There is a Unity2D version that has the same look and feel of Unity3D without the 3D effects. It will run on older hardware.

You can install it via synaptic > search for the package "unity-2d" then install >apply.

Congrats on sysccess (even if the res sucks so far). Subscribe to the 2 monitor radeon bug, they are still working on work-arounds and fixes for that. I'll keep me eyes and ears open and (you know) when I find one, I'll put it here and try to forward what I found to you.

Someone did give me a few ATI cards to play with and to test these problesm on.

[pssturges]

I need to know 2 things before we start...
A. Is the kernel 32bit or 64bit?
B. Is the video chipset the only video chipset? Well your laptop falls into a sort of gray area of time in technology were for a while there was a type or grouping of laptops called "gaming laptops" that explored certain technologies. Your "brand," like others, had offered some of these with nvidia graphics and others with radeon graphics... There was some of these gaming laptops (and I'm not familiar with your brand, so I need feedback from you or others to tell me) that had those chipsets "behind" other video chipsets (sandy bridge, optimus, etc.). The current bug with these is that the current basic linux processes, as they try to query and set graphics, are seeing the first chipset and stopping <> not seeing the chipsets beyond that. If it is one of "these," then tell me first and don't do any of the instructions below, because the instructions and advice for those will be completely different!!!

Here's my plan:
1. Lets get you backed off to what should be a somewhat measurable current starting place.
2. Then we'll get you configured in a manner that should accept the changes we are going to try.
3. We will apply patches and fixes to correct some common problems and ommission that have come up.
4. Then we are going to load our drivers and our changes.

Getting back to a starting point:
Remove, purge and reinstall Grub version 1.99 from a current 11.04 LiveCD. follow the instructions from here, Item number 12:
http://ubuntuforums.org/showthread.php?t=1195275

Gathering Data.
What would be helpful here is for you to run


sudo hwinfo --framebuffer
sudo hwinfo --monitor
And post the results here. Reasons?

a. If the data from --framebuffer says the hardware is anything other than nvidia, stop right there. That would indicate that your nvidia chipset is "behind" another video chipset. If it comes to this, look here:
http://www.martin-juhl.dk/

b. ACPI=off currently in your kernel boot line. If that worked as a workaround for you and it helped <> It might have helped with your graphics, but will cause other problems, especially with laptops. I have a workaround for that by manually setting the GFXMODE and VGA mode. We need data from the above commands to do that.



First of MAFoElffen, thankyou for your time and persistance in helping me solve this issue. It is very much appreciated.

As far as I know the nvidia 8600 is the only video chipset. I have had the laptop for 3 years and never seen any mention of anything else.

Now, for the purposes of solving this issue, I have temporarily replaced the hdd with a fresh one and done a fresh install of 32bit Ubuntu 11.04. So consider it a blank canvas!

The info you asked for:

phil@phil-laptop:~$ sudo hwinfo --monitor
process 2838: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
30: None 00.0: 10000 Monitor
[Created at fb.71]
Unique ID: rdCR.EY_qmtb9YY0
Hardware Class: monitor
Model: "Generic Monitor"
Vendor: "Generic"
Device: "Monitor"
Resolution: 640x480@73Hz
Driver Info #0:
Max. Resolution: 640x480
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-38 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown


phil@phil-laptop:~$ sudo hwinfo --framebuffer
process 2857: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.04O_qA0Mq31
Hardware Class: framebuffer
Model: "NVIDIA G86 Board - e416h01 "
Vendor: "NVIDIA Corporation"
Device: "G86 Board - e416h01 "
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 14 MB
Memory Range: 0x09650000-0x0a44ffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Mode 0x0349: 1400x1050 (+5600), 24 bits
Mode 0x034a: 1600x1200 (+6400), 24 bits
Mode 0x0352: 2048x1536 (+8192), 24 bits
Mode 0x0360: 1280x800 (+1280), 8 bits
Mode 0x0361: 1280x800 (+5120), 24 bits
Mode 0x0362: 768x480 (+768), 8 bits
Mode 0x0364: 1440x900 (+1440), 8 bits
Mode 0x0365: 1440x900 (+5760), 24 bits
Mode 0x0368: 1680x1050 (+1680), 8 bits
Mode 0x0369: 1680x1050 (+6720), 24 bits
Mode 0x037c: 1920x1200 (+1920), 8 bits
Mode 0x037d: 1920x1200 (+7680), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknow

The things I notice of significane are the errors produced by these commands and that the monitor is showing a max resolution of 640x480. Do you think that is significant? The native res of the screen should be 1440x900.

Cheers
Phil

[MAFoElffen]

The info you asked for:

phil@phil-laptop:~$ sudo hwinfo --monitor
process 2838: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
30: None 00.0: 10000 Monitor
[Created at fb.71]
Model: "Generic Monitor"
Vendor: "Generic"
Device: "Monitor"
Resolution: 640x480@73Hz
Driver Info #0:
Max. Resolution: 640x480
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-38 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
Yes, This does seem strange and bothers me too. That was what it said about the "laptop" LCD screen? Query the monitor again with this (should get a lot more detail back):


xrandr -q

[pssturges]

Yes the laptop LCD. Nothing else connected.



xrandr -q
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
** 1024x768 * * * 61.0**
** 800x600 * * * *61.0 *
** 640x480 * * * *60.0 *


Just for kicks I thought I'd try the same commands under lucid.



xrandr -q
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
LVDS-1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 367mm x 229mm
** 1440x900 * * * 60.0*+
** 1152x864 * * * 60.0 *
** 1024x768 * * * 59.9 *
** 800x600 * * * *59.9 *
** 640x480 * * * *59.4 *
** 720x400 * * * *59.6 *
** 640x400 * * * *60.0 *
** 640x350 * * * *59.8 *
VGA-1 disconnected (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)
DVI-D-2 disconnected (normal left inverted right x axis y axis)



Very different...



sudo hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer
**[Created at bios.464]
**Unique ID: rdCR.04O_qA0Mq31
**Hardware Class: framebuffer
**Model: "NVIDIA G86 Board - e416h01 "
**Vendor: "NVIDIA Corporation"
**Device: "G86 Board - e416h01 "
**SubVendor: "NVIDIA"
**SubDevice:*
**Revision: "Chip Rev"
**Memory Size: 14 MB
**Memory Range: 0xcd000000-0xcddfffff (rw)
**Mode 0x0300: 640x400 (+640), 8 bits
**Mode 0x0301: 640x480 (+640), 8 bits
**Mode 0x0303: 800x600 (+800), 8 bits
**Mode 0x0305: 1024x768 (+1024), 8 bits
**Mode 0x0307: 1280x1024 (+1280), 8 bits
**Mode 0x030e: 320x200 (+640), 16 bits
**Mode 0x030f: 320x200 (+1280), 24 bits
**Mode 0x0311: 640x480 (+1280), 16 bits
**Mode 0x0312: 640x480 (+2560), 24 bits
**Mode 0x0314: 800x600 (+1600), 16 bits
**Mode 0x0315: 800x600 (+3200), 24 bits
**Mode 0x0317: 1024x768 (+2048), 16 bits
**Mode 0x0318: 1024x768 (+4096), 24 bits
**Mode 0x031a: 1280x1024 (+2560), 16 bits
**Mode 0x031b: 1280x1024 (+5120), 24 bits
**Mode 0x0330: 320x200 (+320), 8 bits
**Mode 0x0331: 320x400 (+320), 8 bits
**Mode 0x0332: 320x400 (+640), 16 bits
**Mode 0x0333: 320x400 (+1280), 24 bits
**Mode 0x0334: 320x240 (+320), 8 bits
**Mode 0x0335: 320x240 (+640), 16 bits
**Mode 0x0336: 320x240 (+1280), 24 bits
**Mode 0x033d: 640x400 (+1280), 16 bits
**Mode 0x033e: 640x400 (+2560), 24 bits
**Mode 0x0345: 1600x1200 (+1600), 8 bits
**Mode 0x0346: 1600x1200 (+3200), 16 bits
**Mode 0x0347: 1400x1050 (+1400), 8 bits
**Mode 0x0348: 1400x1050 (+2800), 16 bits
**Mode 0x0349: 1400x1050 (+5600), 24 bits
**Mode 0x034a: 1600x1200 (+6400), 24 bits
**Mode 0x0352: 2048x1536 (+8192), 24 bits
**Mode 0x0360: 1280x800 (+1280), 8 bits
**Mode 0x0361: 1280x800 (+5120), 24 bits
**Mode 0x0362: 768x480 (+768), 8 bits
**Mode 0x0364: 1440x900 (+1440), 8 bits
**Mode 0x0365: 1440x900 (+5760), 24 bits
**Mode 0x0368: 1680x1050 (+1680), 8 bits
**Mode 0x0369: 1680x1050 (+6720), 24 bits
**Mode 0x037c: 1920x1200 (+1920), 8 bits
**Mode 0x037d: 1920x1200 (+7680), 24 bits
**Config Status: cfg=new, avail=yes, need=no, active=unknown



Much the same...

"sudo hwinfo --monitor" produces absolutely no output...strange.

Hope that helps
Phil

[johnthei]

1. What is your hardware (Desktop or laptop, CPU, Video)?
2. What ar you trying to install (32bit or 64bit0?
3. By the last paragraph, I'm thinking your plan would be great, because then we could
compare wat conf files and drivers are working and what can be tested, without severing you from the outside world.

=============
I am at 10.10 version now, so if I choose the UPGRADE to 11.04, will it give me the option of partitioning the HD so I can have 11.04 separate, or should I use the 11.04 disc and add it that way?
I don't want to get so far into an upgrade and find out that I cannot partition the HD to keep 11.04 separate and have to go all the way back to 9.10 version to start all over...

[bogan]

Blank Screen crashes after upgrade to 11.04
Upgrading using the Update-Manager upgrade option, from Ubuntu 10.10 to Natty 11.04, ended with a crash to a blank screen with no mouse pointer, a flashing cursor and two flashing lights on the keyboard.
On rebooting I too have blank screen hang-up problems and Grub Menu difficulties, though the screen is not really black, it has a noticeable blue tinge.
After such a hang-up either the Grub Menu locked-up with no keyboard response or there was no Grub Menu but a blank screen with a white panel centred on it, with the text: "Analogue RGB 93KHz/59Hz. Out of range."
After some time, this panel scrolls at random around the screen a la Screen Saver, also with no keyboard response. These problems were overcome, if not cured, by using a 19" 1280x1024 Monitor instead of a 21.5" 1920x1080 Touch Screen Monitor, connected by a DVI-d cable instead of a VGA cable, and using a fully cold start re-boot after a crash;
ie. Holding the reset button down for at least 30 seconds, with the computer power switch off and the power cable removed.( A cure for other start-up sequence hang-ups suggested by the Medion Helpline).
The crashes after selecting Ubuntu 2.6.38-8, either normal, (modified as suggested by MAFoElffen in these threads,) or recovery, continued.
I repeatedly tried all the suggested ways of getting into a graphics screen that I could apply, without success. Most of which just did not work at all.
( For example, neither a 10.10 nor an 11.04 LiveCD gave a different Grub menu screen when 'esc' was pressed; whilst trying to edit the Grub files failed as the files were 'read only').
After trying the Mount sequence outlined on page 19 of the thread, I gave up and formatted the system file partition, downloaded the 11.04 .Iso file, ran it as a try-out and as it seemed to run with no problems I installed Natty from that.

Eureka! --- At least partially.---
It booted and ran with the 19" 1280x1024 Monitor connected by DVI-d cable. But with a VGA cable it still gave the 'Out of Range' message; however, it no longer hung-up, but, after an “Auto Adjusting” message, rebooted directly into Windows.
With the 21.5" 1920x1080 Touch Screen Monitor, connected by a DVI-d cable, after a crash, on re-booting it went from the Grub menu to a blank mauve screen and then hung-up on a black and white striped screen, (see 2. below). A fully cold reboot corrected this.
I also now have a different set of problems. Though I am not sure they belong to this thread:
1.The first few boots gave a Grub menu on a mauve (Magenta?) screen with the time-out counting down to default auto-boot. Later, however, the time-out no longer showed or operated, but at the moment it is working; though I have not altered any of the Grub files, or run update-grub, in the mean time.
2. On resuming from Suspend or Hibernation it crashes with a screen that is a series of black and white horizontal stripes; the mouse cursor is active but no keyboard response. The 'black' lines have a lot of single pixels of varied colours, which I suspected is a hangover from the screen-saver that was running when I put it to sleep. When booted from the LiveCD, going to Suspend or Hibernate crashed to a text screen with an 'state-error' message about the RaLink USB Wireless Adapter and an 'invalid RTChipset' ( the Wlan link works OK ) it then shut down and rebooted to the Grub menu.
3. The desktop has no 'Panels' and I could not find a way to create one, as the help file assumes there is a top and bottom Panel by default - hence there is no way that the Application and System Menus can be accessed, only listed for configuration: the Places menu is only spasmodically shown, depending on what windows are open. Right Mouse clicks in the title bar have no effect.
When booted from the LiveCD the Applications, Places and System/ Preferences/ Administration menu titles are in the top Panel, similarly to 10.10; but it does not have a Launchpad on the left of the screen, and there is a Notification Panel at the bottom..
The Gnome-Panel files from the 11.04CD are v. 2.32.1-0ubuntu6.3, whereas those from the installed 11.04 show those, also v. 2.32.1-0ubuntu6.5 updated 24/05/11.
{ Edit: I found an answer to this. See next entry. Switch to Ubuntu Classic.}
4. Booting into the recovery mode and selecting 'Resume' after running a File System Check, produced a hang-up at the stage of: “Checking Battery State...” with a flashing cursor but no keyboard response.
Should I start a separate thread for each of the above?

This refers to a Medion MS7318 MD 8822 PC with an Intel Core Duo E6400 CPU, which runs 32bit Vista and has a VIA Chip-set, but an nvidia GeForce 7650 GS graphics card with v173 driver, not the current one. Ubuntu10.04 is in sda6, 10.10 was in sda8 but was overwritten by 11.04 and no longer shows in the Grub menu.
I also have a Medion MD8342 running Windows7 with Ubuntu10.10 in sda6, on an external HDD; it would not install to the Boot Hdd as that already has four partitions.

After the successful(sic?) re-installation, now probably irrelevant, here are some more details:
The main problem seems to have been a failure to mount the 11.04 root, though it mounted from the Desktop and seemed normal when accessed. After a cold reboot, the 1.99~rcl Grub menu showed on a black screen and the time-out was not active nor referred to in the text; selecting the 2.6.38-8-generic recovery entry, produced a full screen of text including:
Code #
Autorun...Autorun DONE.
UFS Cannot open root device 'sda8' or unknown-block(0,0)
Please append a correct "root=" boot option; here are available options:
{ but no options followed, what did was:}
Kernel Panic - not syncing: UFS: unable to mount root fs on unknown-block(0,0)
Pid; 1, comm: swapper Not tainted 2.6.38-8-generic#42-Ubuntu
Call trace: {there followed a list of ten calls to various mount and other addresses ending with:}
kernel_thread_helper x0x6/0x10
End code.
It then locked up with a flashing cursor but no keyboard response.
Exactly the same response came when the first item was selected after editing the Grub menu to add 'nomodset' and splash '-verbose text' and deleting the 'vt.handoff=7' entry.

Sorry it is so long but you ask for as much detail as possible.
Any work round suggestions welcome.

[bogan]

I found a partial answer to my problem 3. above. Lack of Panels in Natty Desktop Screen.

Evidently the Natty 11.04 LiveCd was set to boot into the Ubuntu Classic display, whereas the installed version is called UBUNTU.
From the Control Centre -'System Settings' in the menu shown by clicking the extreme right top corner Icon - select 'Login Screen'.
Click on 'Unlock' and enter password.
Choose the 'Select' Button
From the drop-down menu select: 'Ubuntu Classic' entry and 'Close'
Hey Presto the Menus are now in the title bar which is now a Panel.

So I can now right click on it and make up my own LaunchPad, which Classic does not have by default.

Thanks to the Desktop forum for this solution, slightly modified to suit 11.04.

[Blasphemist]

I found a partial answer to my problem 3. above. Lack of Panels in Natty Desktop Screen.

Evidently the Natty 11.04 LiveCd was set to boot into the Ubuntu Classic display, whereas the installed version is called UBUNTU.
From the Control Centre -'System Settings' in the menu shown by clicking the extreme right top corner Icon - select 'Login Screen'.
Click on 'Unlock' and enter password.
Choose the 'Select' Button
From the drop-down menu select: 'Ubuntu Classic' entry and 'Close'
Hey Presto the Menus are now in the title bar which is now a Panel.

So I can now right click on it and make up my own LaunchPad, which Classic does not have by default.

Thanks to the Desktop forum for this solution, slightly modified to suit 11.04.

I can help make sense of some of this. You did provide lots of detail.

The live natty cd runs (see this page) https://wiki.ubuntu.com/DemystifyingUnityGraphicsHardwareRequirements

/usr/lib/nux/unity_support_test -p
A failure to support unity causes the live cd to show the classic desktop. You can run this to see what fails the test. Fixing this may be possible by using some of what is in this thread to get better video performance.

This is the official documentation on the nvidia open source driver install.
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia

The nvidia web site shows this as the proprietary driver for your card. http://www.nvidia.com/object/linux-display-ia32-270.41.19-driver.html
This is how nvidia says to install it.

Installation instructions: Once you have downloaded the driver, change to the directory containing the driver package and install the driver by running, as root, sh ./NVIDIA-Linux-x86-270.41.19.run

One of the last installation steps will offer to update your X configuration file. Either accept that offer, edit your X configuration file manually so that the NVIDIA X driver will be used, or run nvidia-xconfig

[johnthei]

ok, i started to put 11.04 on its own partition...I am confused how to make it. I made about half the drive a partition but did not make some other part it says it needs...so I backed out and stopped.

[Blasphemist]

It probably wanted to create a swap, do create one just larger than the amount of RAM that you have.

[MAFoElffen]

Blank Screen crashes after upgrade to 11.04
Upgrading using the Update-Manager upgrade option, from Ubuntu 10.10 to Natty 11.04, ended with a crash to a blank screen with no mouse pointer, a flashing cursor and two flashing lights on the keyboard.
On rebooting I too have blank screen hang-up problems and Grub Menu difficulties, though the screen is not really black, it has a noticeable blue tinge.
After such a hang-up either the Grub Menu locked-up with no keyboard response or there was no Grub Menu but a blank screen with a white panel centred on it, with the text: "Analogue RGB 93KHz/59Hz. Out of range."
After some time, this panel scrolls at random around the screen a la Screen Saver, also with no keyboard response. These problems were overcome, if not cured, by using a 19" 1280x1024 Monitor instead of a 21.5" 1920x1080 Touch Screen Monitor, connected by a DVI-d cable instead of a VGA cable, and using a fully cold start re-boot after a crash;
ie. Holding the reset button down for at least 30 seconds, with the computer power switch off and the power cable removed.( A cure for other start-up sequence hang-ups suggested by the Medion Helpline).
The crashes after selecting Ubuntu 2.6.38-8, either normal, (modified as suggested by MAFoElffen in these threads,) or recovery, continued.
I repeatedly tried all the suggested ways of getting into a graphics screen that I could apply, without success. Most of which just did not work at all.
( For example, neither a 10.10 nor an 11.04 LiveCD gave a different Grub menu screen when 'esc' was pressed; whilst trying to edit the Grub files failed as the files were 'read only').
After trying the Mount sequence outlined on page 19 of the thread, I gave up and formatted the system file partition, downloaded the 11.04 .Iso file, ran it as a try-out and as it seemed to run with no problems I installed Natty from that.

Eureka! --- At least partially.---
It booted and ran with the 19" 1280x1024 Monitor connected by DVI-d cable. But with a VGA cable it still gave the 'Out of Range' message; however, it no longer hung-up, but, after an “Auto Adjusting” message, rebooted directly into Windows.
With the 21.5" 1920x1080 Touch Screen Monitor, connected by a DVI-d cable, after a crash, on re-booting it went from the Grub menu to a blank mauve screen and then hung-up on a black and white striped screen, (see 2. below). A fully cold reboot corrected this.
I also now have a different set of problems. Though I am not sure they belong to this thread:
1.The first few boots gave a Grub menu on a mauve (Magenta?) screen with the time-out counting down to default auto-boot. Later, however, the time-out no longer showed or operated, but at the moment it is working; though I have not altered any of the Grub files, or run update-grub, in the mean time.
2. On resuming from Suspend or Hibernation it crashes with a screen that is a series of black and white horizontal stripes; the mouse cursor is active but no keyboard response. The 'black' lines have a lot of single pixels of varied colours, which I suspected is a hangover from the screen-saver that was running when I put it to sleep. When booted from the LiveCD, going to Suspend or Hibernate crashed to a text screen with an 'state-error' message about the RaLink USB Wireless Adapter and an 'invalid RTChipset' ( the Wlan link works OK ) it then shut down and rebooted to the Grub menu.
3. The desktop has no 'Panels' and I could not find a way to create one, as the help file assumes there is a top and bottom Panel by default - hence there is no way that the Application and System Menus can be accessed, only listed for configuration: the Places menu is only spasmodically shown, depending on what windows are open. Right Mouse clicks in the title bar have no effect.
When booted from the LiveCD the Applications, Places and System/ Preferences/ Administration menu titles are in the top Panel, similarly to 10.10; but it does not have a Launchpad on the left of the screen, and there is a Notification Panel at the bottom..
The Gnome-Panel files from the 11.04CD are v. 2.32.1-0ubuntu6.3, whereas those from the installed 11.04 show those, also v. 2.32.1-0ubuntu6.5 updated 24/05/11.
{ Edit: I found an answer to this. See next entry. Switch to Ubuntu Classic.}
4. Booting into the recovery mode and selecting 'Resume' after running a File System Check, produced a hang-up at the stage of: “Checking Battery State...” with a flashing cursor but no keyboard response.
Should I start a separate thread for each of the above?

This refers to a Medion MS7318 MD 8822 PC with an Intel Core Duo E6400 CPU, which runs 32bit Vista and has a VIA Chip-set, but an nvidia GeForce 7650 GS graphics card with v173 driver, not the current one. Ubuntu10.04 is in sda6, 10.10 was in sda8 but was overwritten by 11.04 and no longer shows in the Grub menu.
I also have a Medion MD8342 running Windows7 with Ubuntu10.10 in sda6, on an external HDD; it would not install to the Boot Hdd as that already has four partitions.

After the successful(sic?) re-installation, now probably irrelevant, here are some more details:
The main problem seems to have been a failure to mount the 11.04 root, though it mounted from the Desktop and seemed normal when accessed. After a cold reboot, the 1.99~rcl Grub menu showed on a black screen and the time-out was not active nor referred to in the text; selecting the 2.6.38-8-generic recovery entry, produced a full screen of text including:
Code #
Autorun...Autorun DONE.
UFS Cannot open root device 'sda8' or unknown-block(0,0)
Please append a correct "root=" boot option; here are available options:
{ but no options followed, what did was:}
Kernel Panic - not syncing: UFS: unable to mount root fs on unknown-block(0,0)
Pid; 1, comm: swapper Not tainted 2.6.38-8-generic#42-Ubuntu
Call trace: {there followed a list of ten calls to various mount and other addresses ending with:}
kernel_thread_helper x0x6/0x10
End code.
It then locked up with a flashing cursor but no keyboard response.
Exactly the same response came when the first item was selected after editing the Grub menu to add 'nomodset' and splash '-verbose text' and deleting the 'vt.handoff=7' entry.

Sorry it is so long but you ask for as much detail as possible.
Any work round suggestions welcome.
Yes... You have multiple things going on...

First what might help you with some of these problems is to run 2 commands. Open a terminal or tty text console and run:


sudo apt-get install linux-headers
# --OR __
sudo apt-get install linux-headers-generic

# EDITED - use this instead
sudo apt-get install linux-headers-'uname -r'
This should cover 2 of your suspected problems... There was a problem were an dist-update or early iso LiveCD was installing a corrupt or missing (not installed) header files. This was causing a lockup at boot at the "checking battery status" prompt and also causing graphics driver problems during an update, because the drivers use the header files to build for that version of the kernel. Bad header files would also cover some keyboard problems.

After that you would have to remove and install your video card drivers (think you said nvidia v173). If that was that "only" driver on there, you could probably get away with a reinstall through sysnaptic. If not, then through the commandline, first by purging and then install, which would remove it completely and start fresh.

When you are through with those, run


sudo apt=get update
sudo apt-get upgrade
To bring everything current on updates.

Sounds like some of it is hanging your X11 session between your monitor and your video card-- leaving it in a state that only a cold hardware reset is getting rid of that state. The above may help with that, but I'm not sure it will. There's multiple things going on here.

Lets try to weed through some of these other things... on what is current "now"

1. Click the bootinfoscript clink in my signature and follow the instructions. Post the results here. That will show us how your install is laid out and what your current grub,cfg says.
2. Question-> You have 10.10 and 11.04 installed on different partitions right? Is the version of grub now installed that is calling both- which version? 1.98 or 1.99?
3. Please run "sudo hwinfo --framebuffer" and post the results. If hwinfo is not installed yet, install it via "sudo apt-get install hwinfo". This will tell us how linux sees your video card and the modes it's reporting back to it.
4. Please post the results of "xrandr -q" This will tell us the modes reported back from your monitor to linux.
5. Please post your/etc/X11/xorg.conf file.
6. Question- Do you still have the suspend problem?

Edit-- To answer a few more points to check them off your list> Grub 1.99- Timer active but not displaying the "count down" is a current upstream bug and GNU is working on it. I am concerned on the root error <> You say it boots sometimes and sometimes not?

[bogan]

Thanks,Blasphemist, for your clarification and the very useful and informative links.
I have seen a lot of references to Unity in the forums but do not have a clue what it is or does; and this is not the only about Linux tecnical WordSpeak that is a mystery to me. I have both "Linux For Dummies" and "The Complete Manual For Linux", sponsored by Computer Buyer magazine; neither mention it, nor most of the commands I see referred to in this and related threads.
I already have the nvidia 270.41.19 driver installed for WINDOWS 7 & VISTA, but was surprised that Update-Manager did not find it, and was a bit put off doing it manually by the commands needed.
Surely purging the default driver will leave me without a graphics Screen ??.
I will screw up my courage and do the deed as soon as I can get round to it.

Thanks also to MAFoElffen, who confirms the need to purge and reinstall the correct nvidia driver; I have made a separate post to reply to his queries.

Code as requested:
# ( All the hash symbol does is to delete the highlighted text!! Another Bug ??)
alan@alan-MS-7318:~$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 7650 GS/PCI/SSE2
OpenGL version string: 2.1.2 NVIDIA 173.14.30
Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity supported: yes
End Code
It does not look to me as if anything tested was missing or wrong.

[bogan]

MAFoElffen posted:,
Quote -------------------------------------------------------------------------------------------------------
Lets try to weed through some of these other things... on what is current "now"

1. Click the bootinfoscript clink in my signature and follow the instructions. Post the results here. That will show us how your install is laid out and what your current grub,cfg says.
2. Question-> You have 10.10 and 11.04 installed on different partitions right? Is the version of grub now installed that is calling both- which version? 1.98 or 1.99?
3. Please run "sudo hwinfo --framebuffer" and post the results. If hwinfo is not installed yet, install it via "sudo apt-get install hwinfo". This will tell us how linux sees your video card and the modes it's reporting back to it.
4. Please post the results of "xrandr -q" This will tell us the modes reported back from your monitor to linux.
5. Please post your/etc/X11/xorg.conf file.
6. Question- Do you still have the suspend problem?

Edit-- To answer a few more points to check them off your list> Grub 1.99- Timer active but not displaying the "count down" is a current upstream bug and GNU is working on it. I am concerned on the root error <> You say it boots sometimes and sometimes not?

End Quote --------------------------------------------------------------------------------------

Thanks, MAFoElffen, for your helpful response. The following are temporary responses to your queries:
( before purging and reinstalling linux-headers or nvidia drivers): {Sorry I cannot get the Hash symbol to do its duty.}
Answers to your Queries and output fro code entries.
1. BootInfoScript. See Results1.txt file.( I'll enclose it as an attachment if I can find out how to do that. I seem to have forgotten.
2. As in my post, Grub showing both 11.04 & 10.10 is v. 1.99~rcl
3. hwinfo --framebuffer. See text below. I also include hwinfo --monitor as you asked several other Blank Screen's victims for it.
4.& 5. xandr -q output and my 11.04 //etc/X11/xorg.conf file contents are also below.
6. I still have the same problems when resuming from Suspend or Hibernate.
At least I do using the 21.5 Touch Screen 1920x1080 Monitor; I have not tried again with the 19" 1280x1024 Monitor, which I am using now in Linux 11.04 to post this, ( With the RT WLan ralink card working OK in spite of error messages)
Your query headed 'Edit--': Generally it boots OK if the shut down was a normal one or due to a switch off, but not followinag a hang-up or crash, unless I do a fully cold reboot as described in my original post.
Whether the Grub menu shows the Timer or not seems to be quite unpredictable; at the moment it is absent.
The failure to mouint root only occurred with the update installation, not with it installed from the 11.04 LiveCD - which is the latest version available.

Code ------------------------------------------------------------------------------------------------

alan@alan-MS-7318:~$ sudo hwinfo --frame buffer
> hal.1: read hal dataprocess 2497: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.GzKE7w1g_o8
Hardware Class: framebuffer
Model: "NVIDIA G73 Board - p489h0 "
Vendor: "NVIDIA Corporation"
Device: "G73 Board - p489h0 "
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 256 MB
Memory Range: 0xc0000000-0xcfffffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

EndCode---------------------------------------------------------------

alan@alan-MS-7318:~$ sudo hwinfo --monitor
> hal.1: read hal dataprocess 2561: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
39: None 00.0: 10002 LCD Monitor
[Created at monitor.95]
Unique ID: rdCR.HMiVxGBktk3
Hardware Class: monitor
Model: "MD30699PU"
Vendor: MED
Device: eisa 0x89dd "MD30699PU"
Serial ID: "702016264"
Resolution: 720x400@70Hz
Resolution: 640x480@60Hz
Resolution: 640x480@72Hz
Resolution: 640x480@75Hz
Resolution: 800x600@56Hz
Resolution: 800x600@60Hz
Resolution: 800x600@72Hz
Resolution: 800x600@75Hz
Resolution: 1024x768@60Hz
Resolution: 1024x768@70Hz
Resolution: 1024x768@75Hz
Resolution: 1280x1024@75Hz
Resolution: 1280x1024@60Hz
Size: 376x301 mm
Detailed Timings #0:
Resolution: 1280x1024
Horizontal: 1280 1328 1440 1688 (+48 +160 +408) +hsync
Vertical: 1024 1025 1028 1066 (+1 +4 +42) +vsync
Frequencies: 108.00 MHz, 63.98 kHz, 60.02 Hz
Driver Info #0:
Max. Resolution: 1280x1024
Vert. Sync Range: 50-75 Hz
Hor. Sync Range: 31-83 kHz
Bandwidth: 108 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown

End Code -------------------------------------------------------

alan@alan-MS-7318:~$ sudo xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 50.0* 51.0
1280x960 52.0
1152x864 53.0 54.0 55.0 56.0
1024x768 57.0 58.0 59.0
960x600 60.0
960x540 61.0
896x672 62.0
840x525 63.0 64.0 65.0 66.0
832x624 67.0
800x600 68.0 69.0 70.0 71.0 72.0 73.0
800x512 74.0
720x450 75.0
680x384 76.0 77.0
640x512 78.0 79.0
640x480 80.0 81.0 82.0 83.0
576x432 84.0 85.0 86.0 87.0
512x384 88.0 89.0 90.0
416x312 91.0
400x300 92.0 93.0 94.0 95.0
320x240 96.0 97.0 98.0

End Code -----------------------------------------------
gedit /etc/X11/xorg.conf ->

Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection

End Text ---------------------------------------------------------------------

Code ------------------------------------------------------------------------

alan@alan-MS-7318:~$ sudo bash ~/Desktop/boot_info_script.sh
[sudo] password for alan:
Text in /Desktop/Results1.txt
End Code ------------------------------------------------------------------

I had to divide it into two, as it was too large; Results1Part1.txt and RESULTS1Part2.txt I hope I got it right. If not let me know and I will send the contents of the original file. Edited, 01:45 28/05/11

[bogan]

MAFoElffen posted:,
Quote -------------------------------------------------------------------------------------------------------

First what might help you with some of these problems is to run 2 commands. Open a terminal or tty text console and run:
Code:
sudo apt-get remove --purge linux-headers sudo apt-get remove --purge linux-headers-generic sudo apt-get install linux-headers sudo apt-get install linux-headers-generic
End Quote

When I did this I got a line saying:
"Virtual packages like " Linux-Headers" can't [sic] be removed.
Same thing when I did it from a root terminal.
I ran sudo apt-get update & upgrade and am now going to reboot and go to bed. Time here: 0:59 hours.

[MAFoElffen]

Note: 2011.27.05 (Off Topic)

I'm going to be in-and-out this weekend. Will check this thread and try to respond in a timely manner, but-

1. I have 26 scsi ultra drives to individually test, low-level format, partition and set up in 3 SCSI hardware RAID 5's...
2. I have 8 IDE ATi Ultra drives to individually test, low-level format partition and set up in 1 hardware RAID 5...
3. I have 3 IDE ATI Ultra drives to to individually test, low-level format partition and set up in 1 software RAID 5...
4. I have to set these up in a 10.10 Oceiric Server for testing.

Going to be a busy weekend... But will try to stay "current" on this thread.

[mdwpm]

So I'm getting a message after booting up Ubuntu 11.o4 that says "recommand mode 1280x1024". Not sure what to do. Probably my onboard video driver probs? Can anyone fill me in?
Screen goes blank and I can tell that Ubuntu is loading but just not on my screen.

Exactly where I am after a clean install of 11.04. Have you made any progress?

[Blasphemist]

Exactly where I am after a clean install of 11.04. Have you made any progress?

It sounds to me like your graphics driver isn't providing a mode that high. Please start with the troubleshooting flow chart in post 1 of this thread. That will help me know more about the specifics of what can best be done to resolve this. What video card do you have by the way? I don't want to start asking you to do this or that until I know how your boot process goes. Walk through that troubleshooting flow chart and post the results please.

[Blasphemist]

MAFoElffen posted:,
Quote -------------------------------------------------------------------------------------------------------

First what might help you with some of these problems is to run 2 commands. Open a terminal or tty text console and run:
Code:
sudo apt-get remove --purge linux-headers sudo apt-get remove --purge linux-headers-generic sudo apt-get install linux-headers sudo apt-get install linux-headers-generic
End Quote

When I did this I got a line saying:
"Virtual packages like " Linux-Headers" can't [sic] be removed.
Same thing when I did it from a root terminal.
I ran sudo apt-get update & upgrade and am now going to reboot and go to bed. Time here: 0:59 hours.

I'm looking over your posts bogan. Let me know when you're back at this and if things are any different this morning. In the mean time I'll go through the results and detail you posted above.

Thanks

[bogan]

Hi! Blasphemist & MAFoElffen, It is 07:00 hours, and I am back at the keyboard after a few hours in bed and a cup of Coffee, but no sleep; my mind was too busy rehearsing what to do next.
But first, thanks both for your recent posts, sorry there's so much of it to go through when you are so busy, here is some more!! but there is no urgency.

What I did do, was to put Ubuntu11.04, with the 1280x1024 Monitor, to sleep with Suspend, I had to press the reset button to wake it up and it resumed into the Stripey Screen, as described in my original post.
One added thing I found, was that although none of the other keyboard keys, nor Ctrl+ combinations, had any noticeable effect; pressing 'esc' turned off the Mouse Pointer, another 'esc' turned it back on again.
Also I found there is a small area in the middle of the screen, two stripes in height and about a third of the screen width horizontally, where the Pointer changes to a Text Cursor. So, presumably, there is a script box, hiding there behind the stripes; though I could not find any key combination, except 'esc', which altered anything in that area.
As a matter of interest, I also have access to a Dell One19T, running 64bit Windows7, with an Intel G41 Express Chipset Gem video display adapter, (according to Unity_support_test it is '2010030 Development x86/MMX/SSE2', and it gives it a full house of 'Yes's).
Booted from the 11.04 LiveCD, it behaved the same way as in my Vista PC:
Pressing 'esc' in the Try Ubuntu/Install Ubuntu screen has no effect,
Try Ubuntu opens the same screen without Panels, but with a menu list that only shows when the Mouse Pointer is hovered on the Title bar, and is dependent on what is displayed in the Desktop; with an empty Desktop it contains: File, Edit, View, Places, and Help.
Ubuntu is set as the default boot session.
Unlike in my Vista machine the Launcher for Applications does not work in the same way, and shows a title bar saying 'Search Applications', with a meniu selector button on the righthand side, but a blank black screen until selection is made:
On my machine the screen shows three catagories of applications, and I was distracted from noticing the All Applications menu button.
I have that Dell PC running alongside me, so I can read the instructions and edit entries or commands without having to switch windows or workplaces.
I have the sole Admin rights for it; though it is not mine, but for the use of any residents. So I do not think it appropriate to Install Lunix on it. I dont have broadband in my appartment, but can bring my equipment down to use the WiFi Web connection.

When I booted my machine into 11.04,after running apt-get upgrade and update, but not having reinstalled the video drivers; the only differences I could see were that when Places menu was listed in the Title bar, it no longer included entries for System/Preferences & Administration, as it had sometimes done previously, and the Main Menu Launcher (sometimes) actually displayed the menus and they worked, not just a menu configuration program. [ ahem! when I tried it again it did not repeat itself.]
I include the output of vbeinfo from a terminal; a lot of commands I would expect find, get the same output; for instance: 'ls', nautilus-actions and others.
The reason I wanted to run it is that when I ran it from the Grub Cli the list of supported video cards did not include anything I recognized.
Code ---------------------------------------------------
alan@alan-MS-7318:~$ sudo vbeinfo
[sudo] password for alan:
sudo: vbeinfo: command not found
alan@alan-MS-7318:~$ sudo apt-get install vbeinfo
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package vbeinfo
EndCode--------------------------------------------------------

So I ran it again from the Grub Cli and this is part of what it showed:
...supported video modes:
Legand: P=Packed,D=Direct color,...
Adapter 'Cirrus CLGD 5446 PCI Video Driver': no info available
Adapter 'Bochs PCI Video Driver': no info available
Adapter 'VESA BIOS Extension Video Driver': VBE info:
version: 3.0 OEM software rev: 5.115
total memory: 262144 KiB
The list of resolutions include:
0x101 640 x 480 x 8 P
0x111 640 x 480 x 16 D
0x112 640 x 480 x 32 D no entry for x24
0x107 1280 x 1024 x 8 P
0x117 1280 x 1024 x 16 D also entry for x32
EDID version: 1.3
Preferred mode: 1280x1024
Adapter 'VGA Video Driver': No info available

EndCode ------------------------------------

Perhaps this means something to you, to me it is gibberish.:confused:

[Blasphemist]

bogan-

I know how the short nights go. One thing I'd like to pass on is this site. http://castrojo.tumblr.com/post/4795149014/the-power-users-guide-to-unity Jorge has a good guide to differences in unity as it is quite different than the gnome we were used to. Some of what you've posted seem like not quite recognizing that something is how unity works. Like how application menus show in the panel. This page may also help explain unity. http://en.wikipedia.org/wiki/Unity_(user_interface)

But back to the issues. I'm having some trouble sorting out in my head just where things stand with each monitor and each computer. For the time being I'd ignore the vbeinfo results, especially with it showing Cirrus video, but we'll keep it in the back of our minds. Have you installed nvidia drivers yet? Let's focus on that and the kernel headers first if it is booting correctly. Are you where a boot from power off is successful?

[mdwpm]

It sounds to me like your graphics driver isn't providing a mode that high. Please start with the troubleshooting flow chart in post 1 of this thread. That will help me know more about the specifics of what can best be done to resolve this. What video card do you have by the way? I don't want to start asking you to do this or that until I know how your boot process goes. Walk through that troubleshooting flow chart and post the results please.

OK, thank you.

Here's the run down.

My graphics card is an older 64-MB AGP, Radeon 9000 (RV250).

I tried to install 11.04 on a clean HD after I burned the iso image and copied it to CD with Infrarecorder. That got me no where except to the “oversize recommend mode 1280x1024” error and then my monitor turned off.

I then downloaded and burned a copy of the alternate iso and used it to install. Got to the same place as above. The next time I tried to install from the alternate CD I pressed the 'shift' key which dumped me to a screen where I could choose: “Run Ubuntu with Linux 2.6.38.8-generic (recovery mode)” which I chose.

From there I ended up at a menu of several choices of which I chose: “Run Ubuntu in low-graphics mode for just one session”. There was also an option to reconfigure my graphics card at this menu. But that is a dead end. When I choose it I get right back to that menu.

So I am booted into and running 11.04 in recovery/low graphics mode. I have my wireless running and have been able to 'reload' the Ubuntu packages thereby getting them up to date. In fact I'm posting this from Ubuntu/Firefox.

What I don't know how to do is check and, if necessary, change the driver for my graphics card.

Would appreciate a 'nudge' in the right direction or, with these symptoms, where to enter into your excellent flowchart.

Thanks again,
Jim

[Blasphemist]

OK, thank you.

Here's the run down.

My graphics card is an older 64-MB AGP, Radeon 9000 (RV250).

I tried to install 11.04 on a clean HD after I burned the iso image and copied it to CD with Infrarecorder. That got me no where except to the “oversize recommend mode 1280x1024” error and then my monitor turned off.

I then downloaded and burned a copy of the alternate iso and used it to install. Got to the same place as above. The next time I tried to install from the alternate CD I pressed the 'shift' key which dumped me to a screen where I could choose: “Run Ubuntu with Linux 2.6.38.8-generic (recovery mode)” which I chose.

From there I ended up at a menu of several choices of which I chose: “Run Ubuntu in low-graphics mode for just one session”. There was also an option to reconfigure my graphics card at this menu. But that is a dead end. When I choose it I get right back to that menu.

So I am booted into and running 11.04 in recovery/low graphics mode. I have my wireless running and have been able to 'reload' the Ubuntu packages thereby getting them up to date. In fact I'm posting this from Ubuntu/Firefox.

What I don't know how to do is check and, if necessary, change the driver for my graphics card.

Would appreciate a 'nudge' in the right direction or, with these symptoms, where to enter into your excellent flowchart.

Thanks again,
Jim

This is the link to installing the open source driver for your card. https://help.ubuntu.com/community/RadeonDriver

It's possible that you'll need to remove fglrx so you may need this link. https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver#Problem:%20%20Need% 20to%20fully%20remove%20-fglrx%20and%20reinstall%20-ati%20from%20scratch

You'll see from this link that there is a command you can run to see if you can run unity. https://wiki.ubuntu.com/DemystifyingUnityGraphicsHardwareRequirements

/usr/lib/nux/unity_support_test -p

The open source radeon driver should enable KMS, kernel mode settings. This thread covers that in quite a bit of detail, and takes us to the troubleshooting flow chart. Start at step one. You should be able to press shift to get the grub menu but if that isn't working, and it sounds like you did have trouble with that, boot to the cd again so that you can get to grub editing. As step one shows, the goal is to comment out the grub hidden timeout so you can get the grub menu.

Then you go on to step 2. I'm going out for just a few minutes and then I'll boot to grub and get refreshed on doing what you need there. Hopefully this and the open source driver will solve your issues but I'll stay on this with you.

Jim

[Blasphemist]

Jim, if you have trouble getting to a grub edit screen but can get to a command prompt as it sounds like you were, do this.
Run the commands as follows:

cd /etc/default
sudo vi grub

Arrow to the location you want to edit and then press lower case i for insert. Make your insertion, backspace and delete also work in that mode. Press escape to exit insert mode. Type :wq to write and quit.

Run this to update your changes to grub, and then reboot.

sudo update-grub

[bogan]

Blasphemist posted:
Quote --------------------------------------------
I'm looking over your posts bogan. Let me know when you're back at this and if things are any different this morning. In the mean time I'll go through the results and detail you posted above.
.....Are you where a boot from power off is successful?
EndQuote -------------------------------

Hi! Blasphemist, Short answer to above: Yes. Mostly.
Long answer: See attached File BootInfo3

Thanks for your Link for manuals
For Some reason this thread is currently not showing anything posted since 8 hours ago - your post to Jim,
luckily I had seen you later post to me, so here goes.

Unfortunatly, I seem to put a hex on things and the attachment would not operate: Error invalid file but it is omly 5.6 Kb so it is not that.

Here is the full text:

Hi! Blasphemist, Short answer to above: Yes. Mostly.
Long answer: I just read a quote from Henry Kissinger that the Chinese believe a solution is an entry ticket to another problem. To paraphrase Lao Tse: The Problem has got better but the Solution has got worse.
I am not going to apologise for my ignorance about Unity or Gnome, Symantic, Compiz, X sessions, or how the new 11.04 differs from previous versions. I have searched diligently for manuals and got virtually nothing. None of the following worked:
//ubuntu-manual.org
www.ubuntupocketguide.com/download (http://www.ubuntupocketguide.com/download) man.html (there was an error inthe link, it should have been 'main', but it still did not get me a manual.)
wwwq.googlubuntu.com
www.gnu.org/software/grub/manual.html#linux (http://www.gnu.org/software/grub/manual.html#linux)
(Except,on the sixth attempt, PocketHandbook, which does not mention Unity.
So thanks for the further links.

I just found that:


sudo 'Unity' mangives me a manual. WoW!!
I also just realised that " Press # to enclose high-lighted Code in a box", meant: "Click on the '#' Icon above.", not: "Press the '#' key on your keyboard".

So, bitching over, The current situation is that:
1. I have not had any difficulty with the Grub menu, or in booting into Ubuntu 11.04 for what seems to be a long time; though I can not pinpoint exactly what actions cured that.
2. Suspend and Hibernate still crash to the Stripey Screen on reset button resume. That is with both Monitors, (I have not tried it on the DEll 64bit).
3. After running 'sudo apt-get remove --purge linux-headers-generic' was rejected, I ran 'sudo apt-get update' & 'sudo apt-get upgrade', The first gave a screen of text with 'failed to resolve' messages, and ended with a warning that it might not have been correctly installed. When I ran it again now, to get the exact message, it ran to completion without error messages.
4. I found, in another post, advice to run 'sudo apt-get install --reinstall linux-headers-2.6.38-8-generic', so I tried that. It gave a screen of text with 'failed to resolve' messages, as did apt-get update, and ended with the suggestion to run sudo apt-get upgdrade -fix_missing, ( or some such,) which I tried and got the same as before. When I ran --reinstall linux-headers... again now to get the exact message it ran to completion without error messages, as had apt-get update.
5.Trying to install the nvidia video drivers has confirmed all my previous ambivalence about it. First, I decided, at this stage, not to do the 'remove --purge' bit, and I am very glad of it now. I tried the 'Additional Drivers' route, as that seemed to be the simplest.
It only listed v173 and the 'current', which showed: 'Not Active'. The nvidia ReadMe file said to be sure it was the right version, but I could not find out what version it was, so I went no further.
I then tried to run the downoaded .run file directly from a root terminal; after a few moments, it opened a graphics window with the follwing message:


NVIDIA Accelerated Graphics Driver for Linux-x86 (270.41.19)
ERROR: You appear to be running an X server; please exit X before
installing. For further details, please see the section INSTALLING
THE NVIDIA DRIVER in the README available on the Linux driver
download page at www.nvidia.com (http://www.nvidia.com/).
|OK| There is, as might be expected, no info as to how to do that.
The nVidia Install info says "Before you begin..,exit the X Server and terminate all OpenGL applications...You should also set the default runlevel such that it will boot to a VGA console, and not directly into X,...elsewhere it says: Remove the Nouveau driver before installing NVIDIA.( I've done that)...Elsewhere again it says:...and change your default runlevel.

I dont have clue how to do all that and the nVidia Info file lists numbers of alterations to Xconfguration files and elsewhere that are necessary.
There is an option to boot to a 'Recovery Console' in 'Login Screen'; but if I set that, how am I going to get back to Ubuntu Classic.
Is there a Cli command that will allow me to do that?

It frightens me stiff; and I thought Windows was complex and difficult to find what you want, when I went from the AMIGA to a PC.

It is especially ironic that to find a simple introduction to Linux and how to use it, that I had to go to a file intended to tell you how to install a Driver: - AppendicsJ, Tips for New Linux Users > > NVIDIA Accelerated Linux Graphics Driver README and Installation Guide.
So, for now at least, I am leaving the video driver as it is, until I can study what I have got so far.

6. I agree that a lot of the trouble I found with the Menus and Screen modes of display was that there had been no easily accessible information about the changes; which were so great that it was - and still is, in some cases -impossible to know where to look, or to find and run programs.
7. I have managed to make a work-round and set up things to suit my needs, though it is a bit of a bodge-up. It would help if I could get the Applications Launcher to work as it does when booted to Ubuntu, and not to Ubuntu Classic, but presumably that is a feature only available in Unity.

Signing off to watch the Monaco Grand Prix. Bogan.

[Blasphemist]

Bogan, hope your enjoying the race. You have been having lots of challenges. Trust me, by far the majority of installs are quite painless. There are just so many variations of platform and other variables that there will always be puzzles that happen to challenge us. To top it off Unity is the start of a transition away from Gnome 2.x as Gnome development is now on Gnome 3 and its shell. I made a usb stick with a bunch of ubunutu and other linux flavors on it including Fedora 15. I love the Gnome 3 shell and it is quite like the unity plugin on Gnome 2.

The command you gave for the unity manual isn't quite right. The unity manual command is the same as for other command manuals.

man unity
This manual isn't very complete in my opinion and not real helpful but is a start. I still recommend the unity power users guide from Jorge as previously posted and it has links to other sites that are helpful. There are also more helpful sites and posts on here every day.

As for you running unity, from what I can see you should be able to run it with the driver you have installed. For your question about the launcher capability in classic, I recommend Docky and not unity. There is another option, unity 2D, that you could install but I wouldn't go there just yet. In classic, you can install Docky from the software center.

You'll see a lot of posts in these forums that tell you to use commands for things that can be done from GUI programs. That is likely the best way to do things for a number of reasons but can be off putting for many users, especially those new to Linux. In your case, Synaptic package manager could have been used to fix your packages and headers but I believe you are past that now anyway.

Many of us are willing to jump into things before we know everything we should about what we are about to do. You now seem to be in a position to study up on the nvidia open source and proprietary drivers, which of them best support your gpu and just how to install them. MAFoElffen has done a lot of that study and research and posted a lot of great help in this thread. The only pc that I support that uses nvidia is running linux mint and hasn't had any issues for me to address. It's my brothers laptop and I haven't wanted fix what isn't broken. Still, I've worked with some people on nvidia issues and done my own learning. Google is your friend for finding information as are these forums. I'm not sure you aren't running the best driver for you so I recommend doing research and asking questions here before changing to another driver version. I recommend that you start with figuring out what version if any you think is going to work better that what you have installed. Ask questions here about what makes you think it will improve things. It's likely that in doing that research you'll see how to implement that driver but ask questions about that too, before you are in the middle of it. I think you've already come to this conclusion. There are a number of commands you can use to help see just what the details are of what you are running now that are described in this thread.

It sounds to me like you do have to login at boot. If you are by some chance using auto login, I recommend you change that for now. At the login screen you can choose the session type, for that session. That choice is sticky meaning at the next boot your previous choice is the default but you can change at each login. Does that answer your question about getting back to classic after using unity or the recovery console?

Lastly, I wish this had all gone smoother for you but it is really true that if it had you wouldn't have learned nearly as much. Most installs don't require nearly all this work and then when something doesn't work as expected or understood the user is more lost than you will be. Glass half full you know.

[bogan]

Blasphemist posted:

It sounds to me like you do have to login at boot. If you are by some chance using auto login, I recommend you change that for now. At the login screen you can choose the session type, for that session. That choice is sticky meaning at the next boot your previous choice is the default but you can change at each login. Does that answer your question about getting back to classic after using unity or the recovery console?Hi! again.
Actually, I AM using Auto Login, and had not seen the consequences; I have put the Login Screen Launcher at the top-right of the top Panel, for ease of access.
Yes. That largely answers my worries about getting trapped in a default boot to a Console. What about terminating all OpenGL applications?
Will booting to the Recovery Console evert that need?

I had not tried the Recovery mode since I first installed 11,04, when I only chose the 'Resume' and the 'Reboot after file system check' options, both of which crashed or hung-up. Now both work OK and:

sudo service gdm start gets me into what appears to be a normal Classic screen.
So that rather confirms that something we have done has solved that issue, and the cup is a lot more than half-full!!

Presumably, to install the driver, I need to reset the default, or use the Resume mode, and stay in the Cli prompt. That is, I assume the Failsafe Graphics mode would employ the Xconfig system and OpenGL apps.
One of the Links you gave:

'http://en.wikipedia.org/wiki/Unity_(user_interface)'was very valuable; the other:

'http://library.gnome.org/users/user-guide/stable/panels-addobject.html.en' failed to connect, with a screen I had never seen before, showing possible alternative sites. I tried three times, unsuccessfully, but now, six hours later, it connects OK. { This thread is currently not showing posts between 6 & 15 hours ago, so I can't check on whether the links I quote here are yours or not.

'http://castrojo.tumblr.com/post/4795149014/the-power-users-guide-to-unity' also worked fine.}

One thing I have learnt from the Wiki Link you gave, and it surprised me, was that Unity was installed as part of 10.10. The only things I had noticed, compared with 10.04 was the different Information Bar and the silly idea of moving the Window Buttons from the top-right to the top-left.
I fully agree with the comments; to anyone who has to use both Windows and Linux, it is thoroughly confusing and annoying; no sooner I get used to one and I have to swap to the other.
I had also noticed the 'Create Launcher' menu entry, but did not see any relevance or significance.

I have just spent a couple of hours on my Windows7 PC, setting my Ubuntu10.10 screen up to match what I have done on My Vista machine, which is what I am using at present.
Interestingly, the 1.98 Grub2, on Ubuntu 10.10, also does not always show the time delay before booting to the default, nor does it operate.
On the other hand it resumes from Suspend OK, except I had to use the reset button to awaken it, and it did not replace the gedit window I had left open.

I am pretty sure that nvidia v. 270.41.19 is the correct and best driver for my Display Adaptor, and it is that which I downloaded and tried to install. But, presumably, it is not the one that Aditional Drivers calls 'Current', as, from what I have read, it would have to have been installed already for it to be Activated.

That's it for now, or it will not be my cup that is overflowing. Alan

There seems to be something wrong with the thread, it is showing nothing for the last 5 hours.

[Blasphemist]

bogan-

If you want to install the nvidia 270 driver there are options but to prevent future kernel issues, I recommend you do it following this using the PPA and synaptic package manager.

If you choose the PPA, just go to system>administration>synaptic package manager. In synaptic, go to settings>repositories>other software(tab)>add+ then put the ppa address in. Reload when asked.

https://launchpad.net/~ubuntu-x-swat/+archive/x-updates?field.series_filter=maverick
This PPA can be added to your system manually by copying the lines below and adding them to your system's software sources.
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu natty main
deb-src http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu natty main

I gave you the GUI way given what I think your preferences are. This is the link to the command line method.
https://help.launchpad.net/Packaging/PPA/InstallingSoftware

Either way, I believe after a reboot, though that may not be necessary, you should be able to activate this driver version through additional drivers and configure using the nvidia software.

There are other installation options, and I think you started down that route by downloading the script from nvidia. I believe that script brings with it a 50 page readme of instructions from what I've read. Again, when your kernel is next updated you'll have to go through this again if you choose that method.

Edit, this is the link to the readme for the 270 driver. http://us.download.nvidia.com/XFree86/Linux-x86/270.41.19/README/index.html

[DePariah]

Hi everyone, Like every man and his dog I seem to be having trouble with the black screen /of sheer boredom/. I am trying to install Ubuntu Studio on my:

'Acer Aspire Timeline X 5820TG"
four gig of ram,
one gig AMD Radeon card (sticker says HD 6550M if that helps)
Intel Core i5-480M @ 2.66 Ghz

I can get bast the black screen to console mode (i think you call it) by using "nomodeset" but as for what to do then im not sure. I can log in, but I can't get to the standard mode by the original post :-( Anyway thanks for your time to anyone who replies :-)

[Blasphemist]

I need to ask some questions about what has happened and what you've done so far.
1. It sounds like you now do have the grub menu. Have you tried booting into rescue mode/low graphics? If so, how did that go?
2. If that didn't work, did you try step 4 (loading gdm from the command prompt)? The command for that is in step 4.

sudo service gdm start

I think the next step is to install a driver but the results of these questions will help determine how to go about that. If I understand what's gone on so far, following steps 3 and 4 and what happens tells us how to proceed.

[Blasphemist]

By the way, I believe you have hybrid/switchable graphics between the radeon HD and the built in Intel. There are bugs in fglrx, the default open source driver, jockey (the additional drivers app.) and the x server.

Your card is new enough that my first reference for the open source driver doesn't mention your card, and that is not even considering the hybrid graphics. This month, a new ATI closed source driver has been released. Here is the link to that. http://blogs.amd.com/play/2011/05/10/the-amd-catalyst%E2%84%A2-11-5-driver-%E2%80%93-what%E2%80%99s-new/

I'll keep looking into how the hybrid graphics complicates making a choice on drivers in anticipation of hearing back from you.

[Blasphemist]

Also, I don't find the 6550 radeon hd in the 6000 series. Please run this command and post the results.

lspci -nn | grep VGA

[bogan]

Blasphemist - Queries about Video Driver installation.

To paraphrase Lao Tse again:- An Answer is a free ticket to another Question.
Actually, several questions:

Q 1: What is a PPA? {Answer from Help: a Personal Package Archive is a Repository.}

...go to System>Administration>synaptic package manager>settings(tab)> >Repositories>other software(tab)>add+...Q 2. There is a button: 'Add Volume', or one for: "Add...". Presumably, the later is the one, but which entry do I select or untick?

...and then put the ppa address in...Q 2a: Is the "address" the same as the "Apt line", asked for if I select 'Add...'

Q 3: How do I know what the ppa address is? {Answer from Help: Install a PPA...

Q 3a: Which PPA do I Install. Q 3b: Where do I find it?

...On the PPA's overview page, look for the heading that reads Adding this PPA to your system. Make a note of the PPA's location, which should look similar to: ppa:mozillateam/firefox-stableQ3c: Is it my imagination? or is there not a hidden closed loop in this sequence? I need the address to Install it, so that I can read the overview page, to get the location in order to Add it!

Q 3d: Is "address" and "location" the same ?
{ By the above example, the 'location' is only part of the APT line.}

Excerpt from Software Sources>'software-properties-gtk' Box:

The APT line includes the type, location and components of a repository, for example:
'deb http//archive.ubuntu.com/ubuntu natty main'.Q 4: Is 'Installing' the same as the effect of 'Add the source' and Reloading when asked?

......Copy[ing] the lines below and add[ing] them to your systems software sources.Q 5: Does this mean that the entries must be added to the list in the Software Sources window that opens when System>Administration>synaptic package manager>Repositories>other software(tab)>settings(tab) is selected?

Q 6: Are the lines to be copied the 'APT lines', referred to above?
If they are, then I guess you have broken the closed loop.

Sorry to be so pedantic, but I find the trees difficult to see for the forest of lunixspeak.

If this had been the Amiga, or even a Microsoft system, all I would have to do is download the driver and run it. I never thought I would consider Windows simple and straight-forward. That is near to Blasphemy!!

My Hex is still active; the link you gave for the nVidia.../index.html file gave me:

" Oops! This link appears to be broken." But luckily, I had already downloaded the Pdf; most of what I have referred to I got from there.

Regarding my worries about getting trapped in Console Mode and your solution:
On my machine there is no list of options in the Log-in window, either when booting to Ubuntu or to Ubuntu Classic, regardless of whether auto-login is active or not . The options in the Login Screen Application only apply to the next reboot. Only if I select Recovery mode are there options. Was that what you meant?

I just tried it out and it is very long-winded, I have to use 'sudo gdm start' as the low-graphics option brings up a window saying:

Ubuntu is running in low-graphics mode.
Your screen, graphics card and input device settings
could not be detected correctly.
You will need to configure these yourself. |OK| Is that of major significance related to the Blank screen problem?
Clearly it would allow me to resume normal Graphics, and it is not dependent on the auto log-in being switched off.

--Other Issues:
Since reinstalling the generics headers there are changes to how Suspend & Hibernate are acting - I even managed to get Suspend to Resume properly, including re-opening the gedit file I had open - but I will send a separate Post for that:
Should I send it to a different Thread? Say Desktop, or 'I updated, now I have this error'?

I'm still very confused about Unity, and whether it is running in the Ubuntu boot mode or Ubuntu Classic. The first has Dash and a Launch Dock, but not Preference & Administration Menus, ( though Main Menu configures them ) nor any Panels; ( although the help file and man unity say there must be at least one Panel, by default): whereas Classic does not have Dash or a Launch Dock, the top-left Icon shows the Application menu, but it does have two Panels, and the full set of menus.

There is still something wrong with the Thread display, there are several gaps of 5 to 6 hours of Posts that are missing. So I am unable to refer back to some of your and MaFoElffen's replies. Luckily I have copies of most of them in the Subscription advisories.
I only got MAFoEffen's Post imediately after I Posted the above.
The Grub menu was titled GNU GRUB version 1.99~rcl -13ubuntu3, so I assumed that was what was running.

The CPU is an intel 2 Core 13-530 , That was a Screwup it is i my Windows 7 PC, running Ubuntu 10.10 without problems. The actual CPU is an Intel Cor 2 Duo 32bit E6400 2.13 GHz and does not have an embedded GPU, so there is just the nVidia G73 GeForce 7650 Gs video Adapter card.
I will do the things you recommend and get back to you with the output.

[MAFoElffen]

Thanks, MAFoElffen, for your helpful response. The following are temporary responses to your queries:
( before purging and reinstalling linux-headers or nvidia drivers): {Sorry I cannot get the Hash symbol to do its duty.}
Answers to your Queries and output fro code entries.
1. BootInfoScript. See Results1.txt file.( I'll enclose it as an attachment if I can find out how to do that. I seem to have forgotten.
2. As in my post, Grub showing both 11.04 & 10.10 is v. 1.99~rcl
3. hwinfo --framebuffer. See text below. I also include hwinfo --monitor as you asked several other Blank Screen's victims for it.
4.& 5. xandr -q output and my 11.04 //etc/X11/xorg.conf file contents are also below.
6. I still have the same problems when resuming from Suspend or Hibernate.
At least I do using the 21.5 Touch Screen 1920x1080 Monitor; I have not tried again with the 19" 1280x1024 Monitor, which I am using now in Linux 11.04 to post this, ( With the RT WLan ralink card working OK in spite of error messages)
Your query headed 'Edit--': Generally it boots OK if the shut down was a normal one or due to a switch off, but not followinag a hang-up or crash, unless I do a fully cold reboot as described in my original post.
Whether the Grub menu shows the Timer or not seems to be quite unpredictable; at the moment it is absent.
The failure to mouint root only occurred with the update installation, not with it installed from the 11.04 LiveCD - which is the latest version available.

Sorry about the delay. I'm having my own adventure here. Through refurbishing 50 drives... 5 RAID arrays setups, 2 mounted to my server <> But 3 of my external SCSI Raid Arrays don't wont to mount... the Kernel is corrupting the remapped SCSI BIOS memory space/area on my server causing it to "lose" with my scsi controller...

Okay,--
- Your boot info script says you are still running GNU Grub v1.98 on the root of both drives. Natty 11.04 uses GNU Grub v1.99~rc1, which passes variables not in the version you have installed.You are going to need that version to apply the next fixed (for your suspend problem).
- Edit file /ect/grub with root privileges. Example, from a terminal


cd /etc/default
sudo gedit grub
Go this line


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
And change it to


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=\"Linux\" vga=795"
Go to this line


# GRUB_GFXMODE=640x480
And change it to read


GRUB_GFXMODE=1280x1024x24
Which will tell grub to use a 1280x1025x24 mode for it's menu.

If Grub boots it's menu into that res, then the kernel should see it have an easier time booting into that res... If the kernel boots into that res, then Xorg should see it and migth have an easier time booting that res... These edits should get you consistant.

But I see in a post after the above referenced "Quote" that by vbeinfo that it sees this video chipset-->


Legand: P=Packed,D=Direct color,...
Adapter 'Cirrus CLGD 5446 PCI Video Driver': no info available
Adapter 'Bochs PCI Video Driver': no info available
Adapter 'VESA BIOS Extension Video Driver': VBE info:
version: 3.0 OEM software rev: 5.115
total memory: 262144 KiB
The list of resolutions include:
0x101 640 x 480 x 8 P
0x111 640 x 480 x 16 D
0x112 640 x 480 x 32 D no entry for x24
0x107 1280 x 1024 x 8 P
0x117 1280 x 1024 x 16 D also entry for x32
EDID version: 1.3
Preferred mode: 1280x1024
Adapter 'VGA Video Driver': No info available
Which is confusing to me... and may also be confusing to Linux. This concerns me...

It is saying that it is recognising a video chipset that is not supported and whose highest resolution is 1280 Width x 1024h Heigth x 16bit Depth... and not finding or recognising an nvidia chipset.

This could mean 2 things, either the chipset is being mispcognised (by vbeinfo or a bad driver install) or the chipset is behind another chipset and linux is seeing the first chipset and nothing beyond it (such as what is going on with Sandy Bridge and Optimus chipsets).

Please run


lspci -nn | grep VGA
Which will tell us what video chipsets exist on your PC.

What I haven't seen yet from you is your xorg.conf file and you mention what the nvidia settings app say what settings your have... Please also post /etc/X11/xorg.conf.

Edit-- Reading more on your posts... and seems you are getting res'es but unity/compiz problems(?) I'm looking and reading on/catching up where you are now.

Have you tried running(?)


compiz --replace

[MAFoElffen]

OK, thank you.

Here's the run down.

My graphics card is an older 64-MB AGP, Radeon 9000 (RV250).

I tried to install 11.04 on a clean HD after I burned the iso image and copied it to CD with Infrarecorder. That got me no where except to the “oversize recommend mode 1280x1024” error and then my monitor turned off.

I then downloaded and burned a copy of the alternate iso and used it to install. Got to the same place as above. The next time I tried to install from the alternate CD I pressed the 'shift' key which dumped me to a screen where I could choose: “Run Ubuntu with Linux 2.6.38.8-generic (recovery mode)” which I chose.

From there I ended up at a menu of several choices of which I chose: “Run Ubuntu in low-graphics mode for just one session”. There was also an option to reconfigure my graphics card at this menu. But that is a dead end. When I choose it I get right back to that menu.

So I am booted into and running 11.04 in recovery/low graphics mode. I have my wireless running and have been able to 'reload' the Ubuntu packages thereby getting them up to date. In fact I'm posting this from Ubuntu/Firefox.

What I don't know how to do is check and, if necessary, change the driver for my graphics card.

Would appreciate a 'nudge' in the right direction or, with these symptoms, where to enter into your excellent flowchart.

Thanks again,
Jim
Ubuntu say's this card supports Unity... but I'm working out how:

I have a test box running with this chipset (with no problems), but I have everything set up in Grub to help it succeed. I am currently trying to get unity and compiz working on it--- but am stuck on another priority project that supersedes my time on that as yet. It is working at 1280x1024x24.

Your's should be using the opensourced "RADEON" driver (xserver-xorg-video-ati) which should have installed as a defaut on a clean install of 11.04. As a default, this driver does not need an xorg.conf to run... But the jury is out with me at this moment whether adding a config file might help with some of the problems we are having.

If yours does have an xorg,conf file, please post it here.

Pleaset run:


dmesg | grep drm
to see if it's using KMS, if drm got initialized and set up, with maybe mention of the framebuffer and modes set, etc.

Then run


LIBGL_DEBUG=verbose glxinfo
Which will tell us your OpenGL information. The data returned from those 2 commands will tell us a lot in the way hhow your driver is configured and a few things that might cause Unity problems.

[MAFoElffen]

Hi everyone, Like every man and his dog I seem to be having trouble with the black screen /of sheer boredom/. I am trying to install Ubuntu Studio on my:

'Acer Aspire Timeline X 5820TG"
four gig of ram,
one gig AMD Radeon card (sticker says HD 6550M if that helps)
Intel Core i5-480M @ 2.66 Ghz

I can get bast the black screen to console mode (i think you call it) by using "nomodeset" but as for what to do then im not sure. I can log in, but I can't get to the standard mode by the original post :-( Anyway thanks for your time to anyone who replies :-)
Concensus says that the fglx driver does work with this card and 11.04/Unity/Compiz... but the Mesa (opensource) driver does.

Please Run


lspci -nn | grep VGA
sudo hwinfo --framebuffer
Then go into synaptic to see what version of Mesa you are running: Mesa (7.11.x) or Mesa (7.10.x)... Depending on the chipset version, you may have to upgrade the version of Mesa to get hardware acceleration.for untiy. then run


dmesg | grep drm
LIBGL_DEBUG=verbose glxinfo

[pssturges]

Yes the laptop LCD. Nothing else connected.



xrandr -q
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
** 1024x768 * * * 61.0**
** 800x600 * * * *61.0 *
** 640x480 * * * *60.0 *


Just for kicks I thought I'd try the same commands under lucid.



xrandr -q
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
LVDS-1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 367mm x 229mm
** 1440x900 * * * 60.0*+
** 1152x864 * * * 60.0 *
** 1024x768 * * * 59.9 *
** 800x600 * * * *59.9 *
** 640x480 * * * *59.4 *
** 720x400 * * * *59.6 *
** 640x400 * * * *60.0 *
** 640x350 * * * *59.8 *
VGA-1 disconnected (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)
DVI-D-2 disconnected (normal left inverted right x axis y axis)



Very different...



sudo hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer
**[Created at bios.464]
**Unique ID: rdCR.04O_qA0Mq31
**Hardware Class: framebuffer
**Model: "NVIDIA G86 Board - e416h01 "
**Vendor: "NVIDIA Corporation"
**Device: "G86 Board - e416h01 "
**SubVendor: "NVIDIA"
**SubDevice:*
**Revision: "Chip Rev"
**Memory Size: 14 MB
**Memory Range: 0xcd000000-0xcddfffff (rw)
**Mode 0x0300: 640x400 (+640), 8 bits
**Mode 0x0301: 640x480 (+640), 8 bits
**Mode 0x0303: 800x600 (+800), 8 bits
**Mode 0x0305: 1024x768 (+1024), 8 bits
**Mode 0x0307: 1280x1024 (+1280), 8 bits
**Mode 0x030e: 320x200 (+640), 16 bits
**Mode 0x030f: 320x200 (+1280), 24 bits
**Mode 0x0311: 640x480 (+1280), 16 bits
**Mode 0x0312: 640x480 (+2560), 24 bits
**Mode 0x0314: 800x600 (+1600), 16 bits
**Mode 0x0315: 800x600 (+3200), 24 bits
**Mode 0x0317: 1024x768 (+2048), 16 bits
**Mode 0x0318: 1024x768 (+4096), 24 bits
**Mode 0x031a: 1280x1024 (+2560), 16 bits
**Mode 0x031b: 1280x1024 (+5120), 24 bits
**Mode 0x0330: 320x200 (+320), 8 bits
**Mode 0x0331: 320x400 (+320), 8 bits
**Mode 0x0332: 320x400 (+640), 16 bits
**Mode 0x0333: 320x400 (+1280), 24 bits
**Mode 0x0334: 320x240 (+320), 8 bits
**Mode 0x0335: 320x240 (+640), 16 bits
**Mode 0x0336: 320x240 (+1280), 24 bits
**Mode 0x033d: 640x400 (+1280), 16 bits
**Mode 0x033e: 640x400 (+2560), 24 bits
**Mode 0x0345: 1600x1200 (+1600), 8 bits
**Mode 0x0346: 1600x1200 (+3200), 16 bits
**Mode 0x0347: 1400x1050 (+1400), 8 bits
**Mode 0x0348: 1400x1050 (+2800), 16 bits
**Mode 0x0349: 1400x1050 (+5600), 24 bits
**Mode 0x034a: 1600x1200 (+6400), 24 bits
**Mode 0x0352: 2048x1536 (+8192), 24 bits
**Mode 0x0360: 1280x800 (+1280), 8 bits
**Mode 0x0361: 1280x800 (+5120), 24 bits
**Mode 0x0362: 768x480 (+768), 8 bits
**Mode 0x0364: 1440x900 (+1440), 8 bits
**Mode 0x0365: 1440x900 (+5760), 24 bits
**Mode 0x0368: 1680x1050 (+1680), 8 bits
**Mode 0x0369: 1680x1050 (+6720), 24 bits
**Mode 0x037c: 1920x1200 (+1920), 8 bits
**Mode 0x037d: 1920x1200 (+7680), 24 bits
**Config Status: cfg=new, avail=yes, need=no, active=unknown



Much the same...

"sudo hwinfo --monitor" produces absolutely no output...strange.

Hope that helps
Phil

Just wondering if anyone has any more thoughts/input with my issue. I have made no progress since the post above (#194). If not is there anywhere you can suggest I find some help?

Cheers
Phil

[Blasphemist]

Phil=

I read all of your post and the responses to it. I agree that if you have switchable graphics there is a challenge ahead. There may be solutions as a number of people are on it but there is a known bug with switchable graphics.

I can't tell exactly which pc you have. You posted that it is a Medion Akoya but do you have further model numbering or naming? There are some of those with switchable graphics but the ones I saw were with ATI cards not nvidia. But, I didn't look at all models.

Your posts have only shown 14MB of video memory so I don't think we are seeing everything yet. Please run these to get a look at what card or cards are seen. Please post the results.

lspci -v

sudo lshw -c Display

[DePariah]

Also, I don't find the 6550 radeon hd in the 6000 series. Please run this command and post the results.

lspci -nn | grep VGA

Hi Blasphemist, firstly I just wanted to say thank you for your time :-) and secondly I wanted to say that I have Ubuntu Studio up and running /huzzah/ I installed standard Natty, then used the instructions on the Ubuntu Studio website to "upgrade." That being said though, when booting up I my screen still plays weird.

That is to say I get a strange "glitchy" bar of pixels running horizontal across the top of the screen, the screen then cuts out for a few seconds, then resumes as normal. I know this does not really effect the functionality but it is rather bugging me - have you any idea what is causing it?

The command you asked me to run gave me this result:

storm@Paragon-5820TG:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5600 Series] [1002:68c1]
storm@Paragon-5820TG:~$


Cheers, and again thanks for your time
DePariah.

[DePariah]

Hi MAFoElffen (http://ubuntuforums.org/member.php?u=1044547) (and thanks for your time - much appreciated) I ran the first set of commands and this is what i got:

storm@Paragon-5820TG:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5600 Series] [1002:68c1]
storm@Paragon-5820TG:~$ sudo hwinfo --framebuffer
[sudo] password for storm:
sudo: hwinfo: command not found
storm@Paragon-5820TG:~$

[Spr0k3t]

Going through this issue with an upgraded mythbuntu. Tried doing an install from scratch but getting the same issue. Looks like there's a lot to read up about this issue, so I'm going to tag this thread and come back to it. Yuck, it's almost as bad as the nvidia driver nightmare back on the upgrade from 5.10 to 6.06.

Just a quick question though, is there a solid fix for this issue yet or should I roll back the end user to previous install until the issue is sorted out?

[pssturges]

Phil=

I read all of your post and the responses to it. I agree that if you have switchable graphics there is a challenge ahead. There may be solutions as a number of people are on it but there is a known bug with switchable graphics.

I can't tell exactly which pc you have. You posted that it is a Medion Akoya but do you have further model numbering or naming? There are some of those with switchable graphics but the ones I saw were with ATI cards not nvidia. But, I didn't look at all models.

Your posts have only shown 14MB of video memory so I don't think we are seeing everything yet. Please run these to get a look at what card or cards are seen. Please post the results.

lspci -v

sudo lshw -c Display

Thanks for you help. I'm not quite sure what you mean by "switchable graphics". I assume you mean the dual video card thing mentioned throughout this thread. I don't believe I have this type of hardware, although I can't be certain. My laptop is a Medion Akoya MD97310.

Here is the info you asked for:


phil@phil-laptop:~$ sudo lshw -c Display
*-display UNCLAIMED
description: VGA compatible controller
product: G86 [GeForce 8600M GS]
vendor: nVidia Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller cap_list
configuration: latency=0
resources: memory:ce000000-ceffffff memory:d0000000-dfffffff memory:cc000000-cdffffff ioport:2000(size=128)
phil@phil-laptop:~$

and

phil@phil-laptop:~$ sudo lspci -v
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0a <?>

00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: cc000000-ceffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Capabilities: [88] Subsystem: Mitac Device 8227
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [140] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) (prog-if 00 [UHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 1800 [size=32]
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) (prog-if 00 [UHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at 1820 [size=32]
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) (prog-if 20 [EHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at fc204800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0, IRQ 46
Memory at fc200000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: f6000000-f7ffffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f1ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: f8000000-f9ffffff
Prefetchable memory behind bridge: 00000000f2000000-00000000f3ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=07, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: fa000000-fbffffff
Prefetchable memory behind bridge: 00000000f4000000-00000000f5ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at 1840 [size=32]
Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) (prog-if 00 [UHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 1860 [size=32]
Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) (prog-if 00 [UHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1880 [size=32]
Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at fc204c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=08, sec-latency=32
Capabilities: [50] Subsystem: Mitac Device 8227

00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel modules: iTCO_wdt

00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 18a0 [size=16]
Kernel driver in use: ata_piix

00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0])
Subsystem: Mitac Device 8227
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 45
I/O ports at 18d8 [size=8]
I/O ports at 18cc [size=4]
I/O ports at 18d0 [size=8]
I/O ports at 18c8 [size=4]
I/O ports at 18e0 [size=32]
Memory at fc204000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/4 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Kernel driver in use: ahci
Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: medium devsel, IRQ 10
Memory at c0000000 (32-bit, non-prefetchable) [size=256]
I/O ports at 1c00 [size=32]
Kernel modules: i2c-i801

01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8600M GS] (rev a1) (prog-if 00 [VGA controller])
Flags: fast devsel, IRQ 16
[virtual] Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at cc000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 2000 [size=128]
Capabilities: [60] Power Management version 2
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel modules: nouveau, nvidiafb

02:00.0 Network controller: Ralink corp. RT2860
Subsystem: Ralink corp. Device 2790
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f6000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: rt2800pci
Kernel modules: rt2860sta, rt2800pci

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0, IRQ 44
I/O ports at 4000 [size=256]
Memory at f8000000 (64-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at f2000000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Capabilities: [48] Vital Product Data
Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [84] Vendor Specific Information: Len=4c <?>
Capabilities: [100] Advanced Error Reporting
Capabilities: [12c] Virtual Channel
Capabilities: [148] Device Serial Number 10-00-00-00-10-ec-81-36
Capabilities: [154] Power Budgeting <?>
Kernel driver in use: r8169
Kernel modules: r8169

phil@phil-laptop:~$


sudo lshw -c Display produced the same output under lucid, but "sudo lspci -v" produced slightly different results so I thought I'd post them also:

phil@phil-laptop:~$ sudo lspci -v
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel modules: intel-agp

00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: cc000000-ceffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Capabilities: [88] Subsystem: Mitac Device 8227
Capabilities: [80] Power Management version 3
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [140] Root Complex Link <?>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 1800 [size=32]
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at 1820 [size=32]
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) (prog-if 20)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at fc204800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at fc200000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: f6000000-f7ffffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f1ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: f8000000-f9ffffff
Prefetchable memory behind bridge: 00000000f2000000-00000000f3ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=07, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: fa000000-fbffffff
Prefetchable memory behind bridge: 00000000f4000000-00000000f5ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [90] Subsystem: Mitac Device 8227
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at 1840 [size=32]
Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 1860 [size=32]
Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1880 [size=32]
Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at fc204c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) (prog-if 01)
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=08, sec-latency=32
Capabilities: [50] Subsystem: Mitac Device 8227

00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel modules: iTCO_wdt

00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Mitac Device 8227
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 18a0 [size=16]
Kernel driver in use: ata_piix

00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) (prog-if 01)
Subsystem: Mitac Device 8227
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 29
I/O ports at 18d8 [size=8]
I/O ports at 18cc [size=4]
I/O ports at 18d0 [size=8]
I/O ports at 18c8 [size=4]
I/O ports at 18e0 [size=32]
Memory at fc204000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable+
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA <?>
Kernel driver in use: ahci
Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
Subsystem: Mitac Device 8227
Flags: medium devsel, IRQ 10
Memory at c0000000 (32-bit, non-prefetchable) [size=256]
I/O ports at 1c00 [size=32]
Kernel modules: i2c-i801

01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8600M GS] (rev a1)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at cc000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 2000 [size=128]
Capabilities: [60] Power Management version 2
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information <?>
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

02:00.0 Network controller: RaLink RT2860
Subsystem: RaLink Device 2790
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f6000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/5 Enable-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Kernel driver in use: rt2860
Kernel modules: rt2860sta

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
Subsystem: Mitac Device 8227
Flags: bus master, fast devsel, latency 0, IRQ 28
I/O ports at 4000 [size=256]
Memory at f8000000 (64-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at f2000000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Capabilities: [48] Vital Product Data <?>
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [84] Vendor Specific Information <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [12c] Virtual Channel <?>
Capabilities: [148] Device Serial Number 36-81-ec-10-00-00-00-10
Capabilities: [154] Power Budgeting <?>
Kernel driver in use: r8169
Kernel modules: r8169

phil@phil-laptop:~$

Thanks again,
Phil

[rykel]

Are you having these problems?
- Error- "Cannot display this grahics mode" *SNIPPED* If All Else Fails? See Post 2--[/B][/COLOR]

omg, is Natty so BAD that it takes such a long, convoluted post just to get it to start into a GUI?!

[bogan]

HI! MKafoEffen, Hope your weekend was more satisfying than mine.Thanks for finding time to read my screeds and attempting to understand what is going on.
Much appreciated!!
The edit note I added to my last post, #222, was wrong.
Sorry. I messed up, the Intel i3-530 is in my Windows7/Ubunutu10.10 Medion 8341.
The Vista machine, we are dealing with, is a Medion MD8822 ( The MS-7318 reference is the MotherBoard ) and it has an Intel Core2 Duo 32bit E6400 2.13 GHz CPU, 2Gig DDR2 RAM, and a nVidia GeForce 7650 GS Video Adapter card, with 256 MB of Video memory.
I just double-checked with CPU-Z that my brain memory is still working, though it needs upgrading badly.
There is definitely only the 7650 card, confirmed in Device manager.

Blasphemist - HI again and thanks for your last post, though I cant find it now, the latest \post displayed is #231, 6 hours ago: my last Post does not show.

Is the 14MB video memory, you quote from my posts, tied into the malloc error I have seen mentioned?
Sorry again. I confused myself, that quote was from a post to Phil . but should I set the malloc entry.

Please understand that although I have been using Ubuntu since the days you booted into a CLI, - no choice - mount the HDD, - if you were rich enough to have one -and then had to set up an X session and choose what graphics interface you wanted, etc - etc - etc, I have mostly only ever used Linux for a Back-Up to the Amiga or to a PC, Word Processing, or some Graphics processing where it had a speed advantage.
One fault I acknowledge: I dont RTFH. ( the H stand for Help-Files ) except to find out what version is running. I got so used to failing to find what I needed to know from Microsoft and Windows "help" or 'Search' that I got out of the habit of looking there as the first option, except to find out what version of a program was running; preferring to Google, or dredge through Forums or Wiki.
In the last few days I have learnt my mistake: though the Unity Helpfile is an exception, stating things which just do not agree with the screen display, or what happens when a specific action is taken.

A Starter Question: In a Windows Shell a command followed by a '?', displays the Parameter options for that command and what each does.
In the Grub Cli, after pressing 'e', and then 'c', or 'Ctrl+c' to get into the Grub CLI, the next, but only first, time 'Tab' is pressed, it shows a list of all the available commands, ( surprisingly not including Sudo ) but not what they do.
Apart from
man <cmd> is there an equivalent parameter, command or action, in Unity or Unbuntu?

To detail the current situation and summarize the things that seem to have been effective, and at the same time answer some of your queries:

Please note the report in my previous Post to Blasphemist, about the warning message I got when I tried running Recovery/Low-Graphics Mode.

The Grub menu displayed is entitled:
GNU GRUB version 1.99~rcl-13ubuntu3. It is on a Magenta screen, in a box including instructions/options.
To start with, the note re 'Time-out to Auto-select and boot default', is below the box and runs down from 8s. As soon as an 'up' or 'down' curser key is pressed, the time-out message clears, and the Auto-Boot no longer operates. Hence the impression its appearance was random.

The menu itself, ( with no saved alterations to the Linux boot line, or other boot config files,) operates now, and runs, apparently without problems; except occaisionaly, after a crash, or following a failed Resume from Suspend or Hibernate. When it either hangs-up or boots to the Stripey Screen.

In accord with nVidia instructions re preparing to install the 270 Video driver. I have removed the nouveau driver:

sudo apt-get install --purge XServer-xorg-video.nouveauand altered the other "DRIVER=xxx" entries and put one in for "DRIVER=nVIDIA".
nVidia also recommended as important, checking the X11>>Xconf log file , and I found a single error message:
EE: Failed to install "nv" I did not run:

sudo apt-get install --purge remove linux-headers-generic ... as it refused, but I did run:
sudo apt-get install --purge remove linux-header-2.6.38-8-generic sudo apt-get upgrade sudo apt-get update sudo update-grubI used the Startup-Manager to set the Resolution to 1280x1024x24.
I downloaded and ran the nVidia 270 Driver, but I exited when it said X.... and OpenGL applications must be terminated before Installing the Driver.

That's about it for now. The next thing ( after some other Grub ) is to carry out your list, Should I try them out singly as a strict investigation to see which works? or all at one go? I have previously tried most of them from the Grub Menu Console, to no noticeable curative effect. Now that I get the Grub Menu regularly, and it works normally, it is not so easy to see if a change resulted in any improvement
. So my inclination is to grasp the whole bunch of nettles.
What is your advice? Is it important?

[mdwpm]

Ubuntu say's this card supports Unity... but I'm working out how:

I have a test box running with this chipset (with no problems), but I have everything set up in Grub to help it succeed. I am currently trying to get unity and compiz working on it--- but am stuck on another priority project that supersedes my time on that as yet. It is working at 1280x1024x24.

Your's should be using the opensourced "RADEON" driver (xserver-xorg-video-ati) which should have installed as a defaut on a clean install of 11.04. As a default, this driver does not need an xorg.conf to run... But the jury is out with me at this moment whether adding a config file might help with some of the problems we are having.

If yours does have an xorg,conf file, please post it here.

Pleaset run:


dmesg | grep drm
to see if it's using KMS, if drm got initialized and set up, with maybe mention of the framebuffer and modes set, etc.

Then run


LIBGL_DEBUG=verbose glxinfo
Which will tell us your OpenGL information. The data returned from those 2 commands will tell us a lot in the way hhow your driver is configured and a few things that might cause Unity problems.

Jim, thanks.

Well Since we last talked I swapped out the ATI card for a GeForce (Nvidia) 6200 with more RAM (it's also an AGP card). And I'm essentially in the same place as before, dealing with the 'oversize recommend mode 1280x102'4 error.

The 'dmesg | grep drm' doesn't do anything in my terminal - just gives me another prompt. If I run just 'dmesg' I get 10 pages returned. Do you want to post all of that or is there a certain section we're interested in?

Inputting 'libgl debug=verbose' returns:

name of display: :1.0
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".

To recap. I can load 11.04 by choosing recovery mode, editing that to include 'nosetmode' and Ctrl-X to boot to a menu where I have to choose load in failsafe mode. I can also get to a grub prompt.

Jim

PS: Jim, please holf off on chasing this down for now. I've decided just to do another fresh install and start from square one with your orginial troubleshooting guide. I'll post as necessary. I've learned a lot in the past 5 days following this thread, maybe it will help me solve my own problems.

[Blasphemist]

Phil-

I found this on your pc's specs.

Medion Akoya MD97310 Specifications:

- Intel Core 2 Duo T5800 running at 2.0GHz.
- Nvidia GeForce 8600M GS with 512MB dedicated memory
- 320GB HDD
- 17-inch screen with maximum resolution of 1440x900 (16:10 cinema format)
- Wireless 802.11 b/g/n
- 4GB memory
- DVI and HDMI audio/video out
- 1.3-megapixel camera with built-in microphone
- Blu-Ray drive with DVD/CD writer
- Comprehensive software included (BullGuard, Corel MediaOne, Corel Draw Essential Edition 3, CyberLink YouCam, Google Desktop, CyberLink Suite (MediaShow, PowerDirector, PowerDVD 8, PowerProducer), Microsoft Office Home and Student 2007, Microsoft Works, Nero 8 Essentials)
- 6-channel audio out (Analogue + S/P-DIF)
- 4 in 1 Memory Card Reader (SD/MMC/MS/MS Pro)
- Speakers with built-in subwoofer
- Ethernet
I don't think the switchable graphics, and yes you did understand what I meant by that. I found this from someone selling this with ubuntu on it. It is the same as yours from Lucid except that yours didn't show the Mitac device as an unknown subsystem. I believe the Mitac device is for sound.

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GS (rev a1) (prog-if 00 [VGA])
Subsystem: Mitac Unknown device 8227
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at ca000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at c8000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at 2000 [size=128]
Capabilities: <access denied>
In natty, it isn't showing nouveau as in use, it doesn't show any driver in use. That may just be from the boot process not having been completed.

In all of this, I don't see anywhere that natty has detected your laptop monitor. It may well be the issue. Did you ever go through all MAOElffen originally posted back to you? If so what were the results?

In your results from last week quoted below, I don't think the error at the top is a big deal. I get that on one of my laptops. But look at the highlighted part.

phil@phil-laptop:~$ sudo hwinfo --monitor
process 2838: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
30: None 00.0: 10000 Monitor
[Created at fb.71]
Model: "Generic Monitor"
Vendor: "Generic"
Device: "Monitor"
Resolution: 640x480@73Hz
Driver Info #0:
Max. Resolution: 640x480
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-38 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
I'd expect to see in the first highlighted line that it is an LCD Monitor and in the other lines that it knows what your display is. It just seems to see one there but can't tell any specifics on it. Again, this is where I think the issue is.

So how do we solve that? Honestly I don't know though it seems like that should be a known process. I'll research that. In the mean time please answer my question above about what you did from the original response.

[Blasphemist]

Going through this issue with an upgraded mythbuntu. Tried doing an install from scratch but getting the same issue. Looks like there's a lot to read up about this issue, so I'm going to tag this thread and come back to it. Yuck, it's almost as bad as the nvidia driver nightmare back on the upgrade from 5.10 to 6.06.

Just a quick question though, is there a solid fix for this issue yet or should I roll back the end user to previous install until the issue is sorted out?

What I'm seeing from these forums is that there are kernel changes and grub changes, and maybe more such as x, that have converged to cause multiple issues to show up with the symptoms that MFAoElffen created this thread to help with. There are multiple symptoms and solutions. Some are more involved, some are fairly simple. I don't have experience as long as you do but I'd recommend you take a closer look at the start of the thread at least to get a handle on the detail of your issue.

[Blasphemist]

Hi MAFoElffen (http://ubuntuforums.org/member.php?u=1044547) (and thanks for your time - much appreciated) I ran the first set of commands and this is what i got:

storm@Paragon-5820TG:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5600 Series] [1002:68c1]
storm@Paragon-5820TG:~$ sudo hwinfo --framebuffer
[sudo] password for storm:
sudo: hwinfo: command not found
storm@Paragon-5820TG:~$

DePariah-

How's this, a blasphemist trying to help a pariah! :D

You may be in deep. Having two vga controllers can be complex to work out. Here are some posts that may help to determine the right direction for you.

This is from askubuntu.

http://askubuntu.com/questions/2419/switching-between-graphics-cards
The current answer is-
Your model has an AMD discrete graphics card, so you have two options:
try the latest closed-source Catalyst Driver for login/logout card switching, or
try vga_switcheroo and open-source graphics drivers with the graphical vga switching already installed: http://www.youtube.com/watch?v=-S5-BVFk0G0
I can't so far tell what the status is of vgaswitcheroo is. This is the link and a quote from it.

http://airlied.livejournal.com/70348.html
hybrid graphics on Linux
So someone thought it would be a good idea to make laptops with two graphics chips in them and switch betweem them to save power.

Now other OSes support this to varying degrees, I think XP + MacOSX require a logout cycle and Vista/Win7 can dynamically switch while running, while Linux basically falls over in a heap.

So I sat down today with a Lenovo W500 which has an Intel GM45 and AMD Radeon 3650 Mobility in it, and I wrote a patch to try and get closer to the XP/MacOSX level.

The result of one days straight hacking is at:
http://people.freedesktop.org/~airlied/vgaswitcheroo/

The patch is totally focused on the Lenovo W500, other switchers will need to add stuff to this codebase.

Looking further for vgaswitcheroo, I found that I think it is in the kernel and that this site may have software to use it. It's a deb package and I don't find it in the software center.
http://www.ctic.com.br/software/ucc
http://www.ctic.com.br/software/ucc/vga.png?attredirects=0
Following further.
http://linux-hybrid-graphics.blogspot.com/

Testers needed:
If you have a Linux hybrid graphics laptop and a bit of time for
testing, please have a look at the links below:

--> AMD hybrid cards: try the latest Catalyst Driver for login/logout card switching.

--> Switching on/off card:
http://linux-hybrid-graphics.blogspot.com/2010/07/using-acpicall-module-to-switch-onoff.html

[bogan]

oMg
Little Bugs Have bigger Bugs on top to stop them working.
But Bugs dont work, not even small ones.
So a tiny Bug is just as strong and better at lurking
In loops that close and code that opens
Apps that hang, Windows blank and Menus not working.
But the Bug you can rely on is an upgrade too many
That stops you starting but leaves you f###ing.

Preffered hash: 'art', not a bit of 'luck',

Add or insert your own flavour.

I decided to go the Whole-Hog and make all the advised edit changes to the grub files at once, without waiting for advice.


So I went Application>Accessories>System Tools where there is supposed to be an entry for Root Terminal, as there was in earlier Ubuntu versions, but which went missing about 10.04.
What do I find? you will never guess, if you have not peeked!

Someone with sense of humerous[sic' it most be a leg-pull ] irony has changed it to a Guest Session!
So I went the 'sudo -i' route
and entered the code:

alan@alan-MS-7318:/$ sudo -i
[sudo] password for alan:
root@alan-MS-7318:~# cd /etc/default
root@alan-MS-7318:/etc/default# sudo gedit grub After a pause the gedit file opened in its window, whilst in the Terminal was the following message and there was a Prompt Cursor, which flashed when the Terminal Window was Clicked on. At the time, in view of the lack of a Prompt, or any Keyboard response, I assumed it was a crash and did a restart. I did not pay much attention to the gedit Window.

(gedit:2196): Gtk-WARNING **: Attempted to store changes into `/root/.local/share/recentlyused.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.3ZJHWV':No such file or directory (gedit:2196): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recentlyused.xbel', but failed: No such file or directory.2nd attempt after a cold Re-Boot:

[sudo] password for alan:
root@alan-MS-7318:~# cd /etc/default
root@alan-MS-7318:/etc/default# sudo gedit grub
root@alan-MS-7318:/etc/default# There was an immediate switch back to the prompt - with a flashing cursor - with no pause, or text shown and then immediately overwritten. This confirmed my beleive that there had been a crash.
3rd Attempt after cold ReBoot, and, much later the 4th:

root@alan-MS-7318:/etc/default# sudo gedit grub
(gedit:1841): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.N2T6VV': No such file or directory
(gedit:1841): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory..This time, the 4th. Attempt,There ere 6 of these warnings.
I then edited in the advised code:


Go this line:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
And change it to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=\"Linux\" vga=795"

Go to this line: Code: # GRUB_GFXMODE=640x480
And change it to read: GRUB_GFXMODE=1280x1024x24I also ran sudo update-grub, and rebooted, with crossed fingers.Dont Miss Our Next Installment.

The sour cream, if cream it was, came when I had edited this file, but not saved it, when Firefox crashed to an empty Firefox Screen, as if newly run but with no content loaded. I had to use the File>Quit menu option to get out of it, accompaniod by several varied screens - incluing,for a moment, the Stripey screen I have described in connection with Suspend problems. Of course, I also lost what I had entered in the 'New Reply' Box.
And I also lost the Edit entry from another crash later.

Quick Late News: It works still,but much slower to boot.
vbeinfo is still the same: nothing on nvidia version, only Besa

[DePariah]

DePariah-

How's this, a blasphemist trying to help a pariah! :D

You may be in deep. Having two vga controllers can be complex to work out. Here are some posts that may help to determine the right direction for you.

This is from askubuntu.

I can't so far tell what the status is of vgaswitcheroo is. This is the link and a quote from it.


Looking further for vgaswitcheroo, I found that I think it is in the kernel and that this site may have software to use it. It's a deb package and I don't find it in the software center.
http://www.ctic.com.br/software/ucc
http://www.ctic.com.br/software/ucc/vga.png?attredirects=0
Following further.
http://linux-hybrid-graphics.blogspot.com/

************************************************** ****************************

Ahaha a Blasphemist (http://ubuntuforums.org/member.php?u=1165520) helping a Pariah, nice :D

Hey thanks for the links - ill hit them up and see how things go :-)
Cheers till /a possible/ next time

~DePariah

[MAFoElffen]

HI! MKafoEffen, Hope your weekend was more satisfying than mine.Thanks for finding time to read my screeds and attempting to understand what is going on.
Much appreciated!!
The edit note I added to my last post, #222, was wrong.
Sorry. I messed up, the Intel i3-530 is in my Windows7/Ubunutu10.10 Medion 8341.
The Vista machine, we are dealing with, is a Medion MD8822 ( The MS-7318 reference is the MotherBoard ) and it has an Intel Core2 Duo 32bit E6400 2.13 GHz CPU, 2Gig DDR2 RAM, and a nVidia GeForce 7650 GS Video Adapter card, with 256 MB of Video memory.
I just double-checked with CPU-Z that my brain memory is still working, though it needs upgrading badly.
There is definitely only the 7650 card, confirmed in Device manager.

Blasphemist - HI again and thanks for your last post, though I cant find it now, the latest \post displayed is #231, 6 hours ago: my last Post does not show.

Is the 14MB video memory, you quote from my posts, tied into the malloc error I have seen mentioned?
Sorry again. I confused myself, that quote was from a post to Phil . but should I set the malloc entry.

Please understand that although I have been using Ubuntu since the days you booted into a CLI, - no choice - mount the HDD, - if you were rich enough to have one -and then had to set up an X session and choose what graphics interface you wanted, etc - etc - etc, I have mostly only ever used Linux for a Back-Up to the Amiga or to a PC, Word Processing, or some Graphics processing where it had a speed advantage.
One fault I acknowledge: I dont RTFH. ( the H stand for Help-Files ) except to find out what version is running. I got so used to failing to find what I needed to know from Microsoft and Windows "help" or 'Search' that I got out of the habit of looking there as the first option, except to find out what version of a program was running; preferring to Google, or dredge through Forums or Wiki.
In the last few days I have learnt my mistake: though the Unity Helpfile is an exception, stating things which just do not agree with the screen display, or what happens when a specific action is taken.

A Starter Question: In a Windows Shell a command followed by a '?', displays the Parameter options for that command and what each does.
In the Grub Cli, after pressing 'e', and then 'c', or 'Ctrl+c' to get into the Grub CLI, the next, but only first, time 'Tab' is pressed, it shows a list of all the available commands, ( surprisingly not including Sudo ) but not what they do.
Apart from is there an equivalent parameter, command or action, in Unity or Unbuntu?

To detail the current situation and summarize the things that seem to have been effective, and at the same time answer some of your queries:

Please note the report in my previous Post to Blasphemist, about the warning message I got when I tried running Recovery/Low-Graphics Mode.

The Grub menu displayed is entitled: It is on a Magenta screen, in a box including instructions/options.
To start with, the note re 'Time-out to Auto-select and boot default', is below the box and runs down from 8s. As soon as an 'up' or 'down' curser key is pressed, the time-out message clears, and the Auto-Boot no longer operates. Hence the impression its appearance was random.

The menu itself, ( with no saved alterations to the Linux boot line, or other boot config files,) operates now, and runs, apparently without problems; except occaisionaly, after a crash, or following a failed Resume from Suspend or Hibernate. When it either hangs-up or boots to the Stripey Screen.

In accord with nVidia instructions re preparing to install the 270 Video driver. I have removed the nouveau driver:

sudo apt-get install --purge XServer-xorg-video.nouveauand altered the other "DRIVER=xxx" entries and put one in for "DRIVER=nVIDIA".
nVidia also recommended as important, checking the X11>>Xconf log file , and I found a single error message: I did not run:

sudo apt-get install --purge remove linux-headers-generic ... as it refused, but I did run:
sudo apt-get install --purge remove linux-header-2.6.38-8-generic sudo apt-get upgrade sudo apt-get update sudo update-grubI used the Startup-Manager to set the Resolution to 1280x1024x24.
I downloaded and ran the nVidia 270 Driver, but I exited when it said X.... and OpenGL applications must be terminated before Installing the Driver.

That's about it for now. The next thing ( after some other Grub ) is to carry out your list, Should I try them out singly as a strict investigation to see which works? or all at one go? I have previously tried most of them from the Grub Menu Console, to no noticeable curative effect. Now that I get the Grub Menu regularly, and it works normally, it is not so easy to see if a change resulted in any improvement
. So my inclination is to grasp the whole bunch of nettles.
What is your advice? Is it important?
So... That card is close ennough to the card on thie box I'm answering you from. :p

It is using nVidia proprietary, Two times Geoforce 6800 GTX Utra's, bridged SLI, two monitors... Natty 11.04.

nVdia Driver= 173

No problems at all running Natty or Untiy.


# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 260.19.06 (buildd@yellow) Mon Oct 4 15:59:51 UTC 2010


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
# commented out by update-manager, HAL is now used and auto-detects devices
# Keyboard settings are now read from /etc/default/console-setup
# InputDevice "Keyboard0" "CoreKeyboard"
# commented out by update-manager, HAL is now used and auto-detects devices
# Keyboard settings are now read from /etc/default/console-setup
# InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

# commented out by update-manager, HAL is now used and auto-detects devices
# Keyboard settings are now read from /etc/default/console-setup
#Section "InputDevice"
#
# # generated from default
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Device" "/dev/psaux"
# Option "Emulate3Buttons" "no"
# Option "ZAxisMapping" "4 5"
#EndSection

# commented out by update-manager, HAL is now used and auto-detects devices
# Keyboard settings are now read from /etc/default/console-setup
#Section "InputDevice"
#
# # generated from default
# Identifier "Keyboard0"
# Driver "kbd"
#EndSection

Section "Monitor"

# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "HSP LM02"
HorizSync 30.0 - 83.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 55.0
VertRefresh 43.0 - 72.0
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6800 Ultra"
BusID "PCI:3:0:0"
Screen 0
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6800 Ultra"
BusID "PCI:3:0:0"
Screen 1
EndSection

Section "Screen"

# Removed Option "metamodes" "nvidia-auto-select +0+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
But this is running 11.04 64bit

Note... Rember in my previous instructions on purge old... Install driver version 173 instead of using nvidia-current? That "some" people problem were stemming from using nviddia-current itself?

Notice that Jockey says "installed but not active"... but it is active, in use and working fine. Just a jockey bug on that.

Still worth a try....

[Spr0k3t]

What I'm seeing from these forums is that there are kernel changes and grub changes, and maybe more such as x, that have converged to cause multiple issues to show up with the symptoms that MFAoElffen created this thread to help with. There are multiple symptoms and solutions. Some are more involved, some are fairly simple. I don't have experience as long as you do but I'd recommend you take a closer look at the start of the thread at least to get a handle on the detail of your issue.

Thanks Jim... looks like restore to 10.10 worked like a charm using partimage, every time I attempt to upgrade and follow through with the possible fixes, none of them work just yet. Primarily, I believe it revolves around the upgrade of grub, the release of the the kernel, and how the video handoff is done. If there was a way to override the methods of the handoff being done, I'm sure it would be a surefire fix.

Nevertheless, thanks for the informative and major kudos to MFAoElffen for putting up with all of us. Going to try and recreate the issue with a few custom compiled kernels

[MAFoElffen]

Thanks Jim... looks like restore to 10.10 worked like a charm using partimage, every time I attempt to upgrade and follow through with the possible fixes, none of them work just yet. Primarily, I believe it revolves around the upgrade of grub, the release of the the kernel, and how the video handoff is done. If there was a way to override the methods of the handoff being done, I'm sure it would be a surefire fix.

Nevertheless, thanks for the informative and major kudos to MFAoElffen for putting up with all of us. Going to try and recreate the issue with a few custom compiled kernels
And don't forget there was a new release of Xorg also.

Yes, I think they are all (grub, kernel and Xorg) tied together in this problem and they haven't worked out all the possible combinations yet. I tried to submit an Ubuntu Launch Pad Bug... That sort of got lost in translation as I tried to point what should have been "the bigger picture" and their triage team was tunnel-vision focused on just pointing fingers at "nvidia" drivers, even though I assured them the same problems were occuring with other chipsets. I've been collecting data from other chipsets on test boxes here to show them it is a bigger problem:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/781445

So then I submitted a Bug Report with GNU on Grub... where the invalid data and processes seem to start... I'm not sure they have a lot of people doing bug reports, but it seems a logical place to start:
https://savannah.gnu.org/bugs/?33318

I guess the only two places I haven't submitted bugs to yet are kernel.org and x.org. I should file another bug with Xorg, I'm thinking that maybe I should, just to see where it goes. It might help for other people to "join" those bugs...

As for "If there was a way to override the methods of the handoff being done..." Look at the 4 work-arounds in post 2. The first 3 disable or ignor the invalid calls. The fourth trieds to manually set the parameters, that if left on "auto" picks up and passes invalid data somewhere.

It still seems to me that the processes kicked off when GFXMODE is left as auto... and it quesries the hardware... then passes on the data returned... IS BROKE. People shouldn't have to manually set these parameters to over-ride those processes = Basic users should NOT have to become techies just to run a vanilla install of a major distribution.

[MAFoElffen]

Jim, thanks.

Well Since we last talked I swapped out the ATI card for a GeForce (Nvidia) 6200 with more RAM (it's also an AGP card). And I'm essentially in the same place as before, dealing with the 'oversize recommend mode 1280x102'4 error.

The 'dmesg | grep drm' doesn't do anything in my terminal - just gives me another prompt. If I run just 'dmesg' I get 10 pages returned. Do you want to post all of that or is there a certain section we're interested in?

Inputting 'libgl debug=verbose' returns:

name of display: :1.0
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".
Xlib: extension "GLX" missing on display ":1.0".

To recap. I can load 11.04 by choosing recovery mode, editing that to include 'nosetmode' and Ctrl-X to boot to a menu where I have to choose load in failsafe mode. I can also get to a grub prompt.

Jim

PS: Jim, please holf off on chasing this down for now. I've decided just to do another fresh install and start from square one with your orginial troubleshooting guide. I'll post as necessary. I've learned a lot in the past 5 days following this thread, maybe it will help me solve my own problems.
From what that tells me, you didn't have the Radeon nor the GLX drivers loaded. A reinstall of those drivers might have helped... but now we are on a new adventure with different hardware and drivers. You said you switch to nvidia with same problems right? Now your going to reinstall...

I'll wait. ](*,) (I am patient, LOL)

Tip--> Re-download a "current: ISO image of the LiveCD for that reinstall. They do make changes to that image to it to keep it updated with what is current.

[MAFoElffen]

@Phil, DePariah, etc... with switched graphics chipsets.

With the current nvidia drivers and "usual" opensource ncidia drivers available "through" Ubuntu, you are limited to the resolutions of the "swicthing" or "video controlling" chipset, because things are not being seen past it... But things are changing everyday. Currently there is another project (Bumblebee) that concerns your switched video hardware and news says they are "there."

This post explains what is going on with your laptop's hardware and switched video chipsets:
http://ubuntuforums.org/showpost.php?p=10304516&postcount=1
It also has instructions on how to find out if your hardwaare is one of these. Don't despair that it says you are at a dead end and that there is no hope. That post was written before the Bumblebee Project got off the ground.

Here is the article on the Bumblebee Project and the "Optimus Solved" announcement:
http://www.martin-juhl.dk/

Here is where git repo's are for this project:
https://github.com/z0rc/debumblebee

Hope this covers your hardware and helps you out. Tell me how it goes.

Note: Switched Sandy Bridge chipsets with NVidia or ATI, Switched Intel with ATI- are still unsupported so far as I knpw, at this date. They are still limited to the highest resolutions of the Sandy Bridge or Intel video chipsets. Using respective Nvidia or ATI drivers will end up as blackscreens on throe laptops also.

[bogan]

MAFoffen> You lost me on the last Post you sent.
The Code seems to have had its head cut off, and I am not sure of the significance or of the source from which it was output. So many of these commands seem to have very similar looking results.

All it tells me is that you have two Ge-force 6800 Ultra cards, and two Monitors with auto-selection set. The first part of that was clear from the text.

I re-ran:

root@alan-MS-7318:~# /usr/lib/nux/unity_support_test -p
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 7650 GS/PCI/SSE2
OpenGL version string: 2.1.2 NVIDIA 173.14.30
..
All yeses:
..
.GL version is 1.4+: yes
Unity supported: yesStill the same as before.
So I can only assume you mean that that driver may have been badly installed or corrupted, and I should purge it, and re-install the same, rather than the 270 version that nVidia recommend. Whilst you have the 260 version which, ( in the Windows7 version ) gave a lot of problems.

Here, or in CompizEtcResults, attached, are the other things you asked for:

sudo gedit /etc/X11/xorg.conf
As before, this gave a screen full of errors such as:
(gedit:3558): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.6SMRWV': No such file or directory,and opened a gedit Window with:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
gedit xconf.failsafe gave similar Warnings with the text:
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSectionWhich does not look very hopeful. Full output in attached file: 'CompizEtcResults'

sudo compiz --replace
....The first three lines were:
Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...yes
[LOG]: Moving Internal Files
.....//ending with a Terminal Prompt Cursor which only responded to 'Crtl+Alt+Del',
although I closed down everything else that was running.That resulted in 5 or 6 lines of text and a normal Terminal Prompt in a cleared screen.
Something about Windows was all I could read.
The rest of the output is in the attached File 'CompizEtcResults' together with the output from rerunning the unity_support_test, and the xconf and xconf.failsafe files
There is also, in the file Result3.txt, (Probably in two parts, it is so big) the results of re-running:
sudo bash ~/Downloads/Downloads/boot_info_script.sh. [ I noted, from Results3.txt that entry: 'vt_handoff=7' was still in the grubmenu file, and it still appeared in the Boot grub menu display: so I tried to re-edit that bit out. However, the Grub_CMDline_LINUX_DEFAULT line was correct, I do not know where it came from.
Edit: I do now! Removing it from /boot/grub/grub.cfg stopped it returning. Bogan.

In /etc/default/grub and in /boot/grub/grub.cfg, there are lines such as /etc/grub.d/30: but there are no such files as 'grub.d', in the either folder!! Should there be??

lspci -nn | grep VGA
02:00.0 VGA compatible controller [0300]: nVidia Corporation G73 [GeForce 7650 GS] [10de:0390] (rev a1)Regarding my note, in a previous Post, that pressing 'esc' in the 'TryUbuntu/InstallUbuntu screen when booting from a 11.04 LiveCD, did not work with the version I have, as described in your Post2. I found out that if you press any key in the first screen, (the one with a standing man Icon at the bottom) that the language choice scree opens, with the Function keys listed at the bottom. Contrary to your instructions, you then have press 'Enter' to choose a language; as pressing the F6 Other Options function key will not take effect until you do so. Then the Ubuntu menu opens up. The Function keys work as you describe.

Unfortunately, Manage Attachments would not accept my CompizEycResults.txt file, so I will send its contents as a separate Post as soon as I can get it sorted:(.
Edit. See note inserted just above the lsci entry,above.
The LINUX cmdline 'vt_handoff=7' entry in /etc/default/grub had been removed. But it continued to appear in the Boot Menu on start-up. Removing it from '/boot/grub/grub.cfg', stopped it returning. Bogan.

[bogan]

MAKoffen> The following are what should have been 'CompizEtcResults.txt'

alan@alan-MS-7318:~$ sudo bash ~/Downloads/Downloads/boot_info_script.sh
boot_info_script version: 0.60 [17 May 2011]
"gawk" could not be found, using "busybox awk" instead.
This may lead to unreliable results.
Identifying MBRs...
Computing Partition Table of /dev/sda...
Computing Partition Table of /dev/sdb...
Searching sda1 for information...
Searching sda2 for information...
Searching sda5 for information...
Searching sda6 for information...
Searching sda7 for information...
Searching sda8 for information...
Searching sda9 for information...
Searching sdb1 for information...
Searching sdb2 for information...
Finished. The results are in the files "Results3.Part1.txt" & "Results3.Part2.txt"attached.[/CODEsudo gedit /etc/X11/xorg.conf

(gedit:3558): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.6SMRWV': No such file or directory
(gedit:3558): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory
(gedit:3558): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.OA4BWV': No such file or directory
(gedit:3558): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory[/CODE]And it opened a gedit Window with:

Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
sudo gedit /etc/X11/xorg.conf.failsafe

(gedit:2115): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.286BWV': No such file or directory
(gedit:2115): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory,and opened a gedit Window with:
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
alan@alan-MS-7318:~$ sudo compiz --replace

Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...yes
[LOG]: Moving Internal Files
[LOG]: Copying subdirectory from /home/alan/.compiz/session to /home/alan/.compiz-1/session
[LOG]: Copied file /home/alan/.compiz/session/10b4a1079fff882b7613061939381503500000013980030 to /home/alan/.compiz-1/session/10b4a1079fff882b7613061939381503500000013980030
[LOG]: Copied file /home/alan/.compiz/session/10ea0e17d911b3d4bb130622706723249900000012550030 to /home/alan/.compiz-1/session/10ea0e17d911b3d4bb130622706723249900000012550030
[LOG]: Copied file /home/alan/.compiz/session/1028a7a45b60fda58d130622910299521300000012810030 to /home/alan/.compiz-1/session/1028a7a45b60fda58d130622910299521300000012810030
[LOG]: Copied file /home/alan/.compiz/session/10720ed1a8f4895ad7130625602180979300000012610030 to /home/alan/.compiz-1/session/10720ed1a8f4895ad7130625602180979300000012610030
[LOG]: Copied file /home/alan/.compiz/session/1012dafc7b8025ad2813062621443206300000012460030 to /home/alan/.compiz-1/session/1012dafc7b8025ad2813062621443206300000012460030
[LOG]: Copied file /home/alan/.compiz/session/1099ce6f4c5d44d2d5130632722573531700000013120030 to /home/alan/.compiz-1/session/1099ce6f4c5d44d2d5130632722573531700000013120030
[LOG]: Copied file /home/alan/.compiz/session/10e7e56a349d8af52d130632738539850000000013210030 to /home/alan/.compiz-1/session/10e7e56a349d8af52d130632738539850000000013210030
[LOG]: Copied file /home/alan/.compiz/session/103a7a2b507ee7c74d130634281269324200000012600030 to /home/alan/.compiz-1/session/103a7a2b507ee7c74d130634281269324200000012600030
[LOG]: Copied file /home/alan/.compiz/session/108f567588dee75c1130635630836268900000012580030 to /home/alan/.compiz-1/session/108f567588dee75c1130635630836268900000012580030
[LOG]: Copied file /home/alan/.compiz/session/1035f7a9247d9bd14c130643254286955300000013500030 to /home/alan/.compiz-1/session/1035f7a9247d9bd14c130643254286955300000013500030
[LOG]: Copied file /home/alan/.compiz/session/1052db1653453bc163130677587419733400000014420030 to /home/alan/.compiz-1/session/1052db1653453bc163130677587419733400000014420030
[LOG]: Copied file /home/alan/.compiz/session/101714947a76eb772d13065909408594200000012500030 to /home/alan/.compiz-1/session/101714947a76eb772d13065909408594200000012500030
[LOG]: Copied file /home/alan/.compiz/session/10593eca41ea939ebd13063583388708100000014030030 to /home/alan/.compiz-1/session/10593eca41ea939ebd13063583388708100000014030030
[LOG]: Copied file /home/alan/.compiz/session/104cb75805e906b12130642985872435700000012930030 to /home/alan/.compiz-1/session/104cb75805e906b12130642985872435700000012930030
[LOG]: Copied file /home/alan/.compiz/session/10bad4b3a11faf422130677924922441200000014380030 to /home/alan/.compiz-1/session/10bad4b3a11faf422130677924922441200000014380030
[LOG]: Copied file /home/alan/.compiz/session/105bbe5fbb17b97145130657043966217300000012720030 to /home/alan/.compiz-1/session/105bbe5fbb17b97145130657043966217300000012720030
[LOG]: Copied file /home/alan/.compiz/session/106fd9b73ee526ffd6130657092664124600000012380030 to /home/alan/.compiz-1/session/106fd9b73ee526ffd6130657092664124600000012380030
[LOG]: Copied file /home/alan/.compiz/session/10ff817c416a159759130658014823365500000012940030 to /home/alan/.compiz-1/session/10ff817c416a159759130658014823365500000012940030
[LOG]: Copied file /home/alan/.compiz/session/106b3b4e53e4dbc12a130657142977865100000012680030 to /home/alan/.compiz-1/session/106b3b4e53e4dbc12a130657142977865100000012680030
[LOG]: Copied file /home/alan/.compiz/session/10a854612e13a35698130659686227618000000012540030 to /home/alan/.compiz-1/session/10a854612e13a35698130659686227618000000012540030
[LOG]: Copied file /home/alan/.compiz/session/10cc85ee05c94a7a09130661079274939000000012830030 to /home/alan/.compiz-1/session/10cc85ee05c94a7a09130661079274939000000012830030
[LOG]: Copied file /home/alan/.compiz/session/10629582441aec3def130665728974211200000013030030 to /home/alan/.compiz-1/session/10629582441aec3def130665728974211200000013030030
[LOG]: Copied file /home/alan/.compiz/session/107cb07d305f111875130667129671218100000013050030 to /home/alan/.compiz-1/session/107cb07d305f111875130667129671218100000013050030
[LOG]: Copied file /home/alan/.compiz/session/109c16249583ce0fc2130667865729116800000012870030 to /home/alan/.compiz-1/session/109c16249583ce0fc2130667865729116800000012870030
[LOG]: Copied file /home/alan/.compiz/session/1049a3f0e1f28fbe4f130669542992489900000012950030 to /home/alan/.compiz-1/session/1049a3f0e1f28fbe4f130669542992489900000012950030
[LOG]: Copied file /home/alan/.compiz/session/10b7b62d289bbceef8130670151637360000000017840030 to /home/alan/.compiz-1/session/10b7b62d289bbceef8130670151637360000000017840030
[LOG]: Copied file /home/alan/.compiz/session/10d05cfff1e7c8d1d613065419764841400000012640030 to /home/alan/.compiz-1/session/10d05cfff1e7c8d1d613065419764841400000012640030
[LOG]: Copied file /home/alan/.compiz/session/10cf9321f93c32a64b130682989223232500000013170030 to /home/alan/.compiz-1/session/10cf9321f93c32a64b130682989223232500000013170030
[LOG]: Copied file /home/alan/.compiz/session/10e93a1dffc200082130656187191094300000012990030 to /home/alan/.compiz-1/session/10e93a1dffc200082130656187191094300000012990030
[LOG]: Copied file /home/alan/.compiz/session/1066a0599b32dc1025130677631253474700000014560030 to /home/alan/.compiz-1/session/1066a0599b32dc1025130677631253474700000014560030
[LOG]: Copied file /home/alan/.compiz/session/1036bcbbee8723dbeb130682499535213100000012850030 to /home/alan/.compiz-1/session/1036bcbbee8723dbeb130682499535213100000012850030
[LOG]: Copied file /home/alan/.compiz/session/1035a950a32aeb080413067807433614100000016720030 to /home/alan/.compiz-1/session/1035a950a32aeb080413067807433614100000016720030
[LOG]: Copied file /home/alan/.compiz/session/10f7ebefccbb596ab130678090032376100000013020030 to /home/alan/.compiz-1/session/10f7ebefccbb596ab130678090032376100000013020030
[LOG]: Copied file /home/alan/.compiz/session/10bc27e41390b1126e130678134484538500000015990030 to /home/alan/.compiz-1/session/10bc27e41390b1126e130678134484538500000015990030
[LOG]: Copied file /home/alan/.compiz/session/103b527c5bff35c5dc130658910293057100000012950030 to /home/alan/.compiz-1/session/103b527c5bff35c5dc130658910293057100000012950030
[LOG]: Copied file /home/alan/.compiz/session/1071be039a94990b0613068237135898400000012750030 to /home/alan/.compiz-1/session/1071be039a94990b0613068237135898400000012750030
[LOG]: Copied file /home/alan/.compiz/session/10498b6f42e6062042130682490994874900000013090030 to /home/alan/.compiz-1/session/10498b6f42e6062042130682490994874900000013090030
[LOG]: Copied file /home/alan/.compiz/session/10a92625f8137c698130685875969732200000012870030 to /home/alan/.compiz-1/session/10a92625f8137c698130685875969732200000012870030
[LOG]: Copied file /home/alan/.compiz/session/10a99aef17d8329df013068381464802600000013140030 to /home/alan/.compiz-1/session/10a99aef17d8329df013068381464802600000013140030
[LOG]: Copied file /home/alan/.compiz/session/10a2db985f24535bbb130684099594707900000013000030 to /home/alan/.compiz-1/session/10a2db985f24535bbb130684099594707900000013000030
[LOG]: Copied file /home/alan/.compiz/session/10adddf95440616326130686320295329800000012980030 to /home/alan/.compiz-1/session/10adddf95440616326130686320295329800000012980030
[LOG]: Copied file /home/alan/.compiz/session/108077d84f4b655296130687189324518200000013000030 to /home/alan/.compiz-1/session/108077d84f4b655296130687189324518200000013000030
[LOG]: Copied file /home/alan/.compiz/session/10a7fe2ae34e3cbff6130687811938294400000012700030 to /home/alan/.compiz-1/session/10a7fe2ae34e3cbff6130687811938294400000012700030
[LOG]: Copied file /home/alan/.compiz/session/1037a94782fb9d35bb130687841690503700000012560030 to /home/alan/.compiz-1/session/1037a94782fb9d35bb130687841690503700000012560030
[LOG]: Copied file /home/alan/.compiz/session/1038939bad4f9c65c8130675233098177000000014330030 to /home/alan/.compiz-1/session/1038939bad4f9c65c8130675233098177000000014330030
[LOG]: Copied file /home/alan/.compiz/session/105ce0a17881208cc130677903913316700000014470030 to /home/alan/.compiz-1/session/105ce0a17881208cc130677903913316700000014470030
[LOG]: Successfully moved internal files
Backend : ini

Integration : trueProfile : default
Adding plugins
Initializing core options...done
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 1
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0
Window created on XQueryTree, map state isViewable? 0

Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing mousepoll options...done
Initializing vpswitch options...done
Initializing animation options...done
Initializing snap options...done
Initializing expo options...done
Initializing move options...done
Initializing place options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing wall options...done
Initializing ezoom options...done
Initializing workarounds options...done
Initializing staticswitcher options...done
Initializing resize options...done
Initializing fade options...done
Initializing scale options...done
Initializing session options...doneStopping at that point with a Terminal Prompt Cursor.

Crtl+Alt+Del'
5 or 6 lines of text to a cleared screen.
Something about Windows, was all I could read.

Sorry for the catastrophic mess-up.

[bogan]

HI! Blasphemist & MAKoffen. I am hiding my head in shame.
I had a real sense of triumph, that I had actually managed to solve one of my problems on my own, without any need to go to helpfiles, or of your very much gratefully welcomed and breathlessly awaited asistance.
Quote: "Reality is always paradoxical" & from the same source, loosely translated, "An Answer is a free-ticket to another Question"; Lao Tse, b.604BC and a contempory of Confucius, about 4OOBC. They lived along time in those days.
Quote: First Posted by Bogan, in an edit to Post #245.

Edit. See note inserted just above the lsci entry,above.
The LINUX cmdline 'vt_handoff=7' entry in /etc/default grub was removed from' /etc/default/grub'.But it continued to appear in the Boot Menu on start-up. Removing it from '/boot/grub/grub.cfg', stopped it returning. Bogan. Edit. (note referred to above:
I noted, from Results3.txt that the entry 'vt_handoff=7' was still in the grubmenu file, and it still appeared in the Bootgrubmenu display:so I tried to re-edit that bit out. However, the Grub_CMDline_LINUX_DEFAULT line was correct, I do not know where it came from.
Edit: I do now! Removing it from /boot/grub/grub.cfg stopped it returning. Bogan. As you probably realised, my solution to the Problem of the mysterious re-appearance, in the grub boot menu, of the 'vt_handoff=7' entry, after editing it out in the LINUX cmd line, in /etc/default/grub, was a false and rather misleading self inflicted injury to my self-esteem.
It worked fine, at first, but I had not taken sudo update-grub into account in dis-regarding the warning at the top of Grub.cfg.
When I next ran that command, Grub cheerfully put it back again.
So now I need your expertise, I know grub constructs the grub.cfg, it says so when it runs. But where does it get the data from? I have no idea.

[MAFoElffen]

HI! Blasphemist & MAKoffen. I am hiding my head in shame.
I had a real sense of triumph, that I had actually managed to solve one of my problems on my own, without any need to go to helpfiles, or of your very much gratefully welcomed and breathlessly awaited asistance.
Quote: "Reality is always paradoxical" & from the same source, loosely translated, "An Answer is a free-ticket to another Question"; Lao Tse, b.604BC and a contempory of Confucius, about 4OOBC. They lived along time in those days.
Quote: First Posted by Bogan, in an edit to Post #245.
Edit. (note referred to above: As you probably realised, my solution to the Problem of the mysterious re-appearance, in the grub boot menu, of the 'vt_handoff=7' entry, after editing it out in the LINUX cmd line, in /etc/default/grub, was a false and rather misleading self inflicted injury to my self-esteem.
It worked fine, at first, but I had not taken sudo update-grub into account in dis-regarding the warning at the top of Grub.cfg.
When I next ran that command, Grub cheerfully put it back again.
So now I need your expertise, I know grub constructs the grub.cfg, it says so when it runs. But where does it get the data from? I have no idea.
YES-- vt_handoff is a hard-coded default. You can remove it temporarily from the command line at "Grub menu edit," for one-time each, or you can edit it out of grub.cfg... but as you found, once you rum update grub, grub.cfg will get updated and it will appear. I only remove it (and add "--verbose text") as a diagnostic tool to be able to read all the kernel boot and error messages. After the diagnostocs... then I remove "nomodeset --verbose text" and run update-grub again. With nvidia, after you install a working nvidia driver, you no longer need the nomodeset.... and vt_handoff=7 suppresses messages during bootup.

Yes, I thought I implied to purge and reinstall, installing the driver you needed instead of using the generic process of nvidia-current that I used to recommend. People were having better luck that way. telling me that for them, using nvidia-current was a problem but using the individual, specific driver for their card, then they were okay.

[mdwpm]

From what that tells me, you didn't have the Radeon nor the GLX drivers loaded. A reinstall of those drivers might have helped... but now we are on a new adventure with different hardware and drivers. You said you switch to nvidia with same problems right? Now your going to reinstall...

I'll wait. ](*,) (I am patient, LOL)

Tip--> Re-download a "current: ISO image of the LiveCD for that reinstall. They do make changes to that image to it to keep it updated with what is current.


Jim, I'm back after swapping the ATI AGP card for this GeForce6200.

You'll recall I installed Ubuntu 11.04 from alternate 11.04 iso I downloaded from Ubuntu site and burned to a CD with Infrarecorder. Installation is 'fresh' on a hard drive with no other operating system(s) on it. A previous attempt to install from the regular 11.04 iso did not work. Booting up from that CD resulted in a screen on my monitor that said 'Oversize Recommand 1280x1024' error and my monitor was turned off.

My basic system is as follows:

Asus P4PE MotherBoard (Intel 82845PE MCH/Intel 82801DB ICH4 chipsets)
Intel Pentium 4 (2.4GHz)
1 GB RAM
EVGA/GeForce 6200 AGP video card with 512MB memory
Kogi Monitor (Model L7TH TA)

My Problem:

Ubuntu is installed on my hard drive. To run Ubuntu I must select 'Run in Recovery Mode', edit that by inserting 'nomodeset' and then boot by pressing Ctrl-X. That takes me to a screen with further options at which I must select 'start in failsafe mode'. Any other procedure or selection to boot Ubuntu leads to the 'Oversize Recommand 1280x1024' screen error.

Updates:

After installing 11.04 and booting in safe mode, I installed the ndiswrapper and got my WIFI dongle working. Using the Synaptic Package Manager and the Update Manager I have updated all packages and the program as of June 2.

Various Codes:

- Code 'LIBGL_DEBUG=verbose glxinfo' returns:

LIBGL_DEBUG=verbose glxinfo

name of display: :1.0

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Error: couldn't find RGB GLX visual or fbconfig



Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".


- Code 'sudo hwinfo –framebuffer' returns:

> hal.1: read hal dataprocess 13304: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files

- Code ' lspci -nn | grep VGA' returns:

01:00.0 VGA compatible controller [0300]: nVidia Corporation NV44A [GeForce 6200] [10de:0221] (rev a1)


- Code ' /usr/lib/nux/unity_support_test -p' returns:

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Xlib: extension "GLX" missing on display ":1.0".

Error: unable to create the OpenGL context

Things I've tried:

I have tried setting the VGA value by editing the startup script. I've tried VGA=775, 794 and 795 (corresponding to mode 1280x1024, 8,12 and 24-bit). Same result each time.

I received notification to download the updated nvidia driver – I downloaded the 'recommended' one. Instructions say to restart to complete installation. Doing so results in the 'Oversize' error. Can only boot in recovery mode and failsafeX mode but the driver is never installed. The system>administration>additional drivers drop-down indicates the driver is activated but not installed. I'm thinking because I have to start in recovery mode the installation is not completing.

I tried nvidia-xconfig in terminal and received:

jim@ubuntu:~$ sudo nvidia-xconfig

[sudo] password for jim:

Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

How to complete installation of the driver from failsafe mode? I'm in need of another 'nudge'!

Thank you.

[bogan]

:redface:MAFoElffen > Checking back through your Posts for the exact syntax for the purge and reinstall video drivers commands. I see that I have invested a lot of effort in finding incorrect spellings of your name. Apologies, especially as I have an unusual name myself: 'PFEIL' ( Vie Pfeil und Bogan ) so I am used to imaginative versions; that must be my excuse.
Thanks for your very prompt response. I do not know how you manage to deal with all the projects you have in hand, and still find time for perusing all the data you need for making sense of our individual varied problems.
I have had an email from nvidia - actually six of them - announcing the availability of version 275.33 for Windows, though for my Card it reccomends version 275.27, and that's a Beta !!
For Lunix they still offer 270.48.19, which I downloaded and is the 'driver you needed' and the 'individual, specific driver for their card', to quote your Post.
But You probably get nVidia newsletters anyway. I wonder who will be brave enough to try it, not me!

What is Jockey? Is that what you also call Synaptic? I have only ever come across 'Jockey' before as the name of an Icon design.'