Page 25 of 139 FirstFirst ... 1523242526273575125 ... LastLast
Results 241 to 250 of 1386

Thread: Graphics Resolution- Upgrade /Blank Screen after reboot

  1. #241
    Join Date
    Jan 2007
    Location
    Missouri
    Beans
    738
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by Blasphemist View Post
    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

  2. #242
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by Spr0k3t View Post
    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/+s...gs/+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.
    Last edited by MAFoElffen; June 1st, 2011 at 09:22 PM.

    "Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637
    Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags

  3. #243
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by mdwpm View Post
    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.
    Last edited by MAFoElffen; June 1st, 2011 at 07:03 PM.

    "Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637
    Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags

  4. #244
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    @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...16&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.
    Last edited by MAFoElffen; June 2nd, 2011 at 01:45 PM.

    "Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637
    Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags

  5. #245
    Join Date
    Feb 2010
    Location
    Nr BrandsHatch, S'oaks UK
    Beans
    1,241
    Distro
    Lubuntu 13.04 Raring Ringtail

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    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:
    Code:
    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:        yes
    Still 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:
    Code:
    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"
    EndSection
    Which does not look very hopeful. Full output in attached file: 'CompizEtcResults'
    Code:
    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:
    Code:
     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??
    Code:
    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.
    Attached Files Attached Files
    Last edited by bogan; June 2nd, 2011 at 11:52 AM. Reason: Add note Re: 'vt_handoff=7' re-appearing in Boot Menu . 2nd edit to change file name to grub.cfg

  6. #246
    Join Date
    Feb 2010
    Location
    Nr BrandsHatch, S'oaks UK
    Beans
    1,241
    Distro
    Lubuntu 13.04 Raring Ringtail

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    MAKoffen> The following are what should have been 'CompizEtcResults.txt'
    Code:
    alan@alan-MS-7318:~$ sudo bash ~/Downloads/Downloads/boot_info_script.sh
    Code:
    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:
    Code:
    Section "Device"
        Identifier    "Default Device"
        Option    "NoLogo"    "True"
    EndSection
    Code:
    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
    Code:
    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
    Code:
    Backend     : ini
    Code:
    Integration : trueProfile     : default
    Adding plugins
    Initializing core options...done
    Code:
    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
    Code:
    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...done
    Stopping at that point with a Terminal Prompt Cursor.
    Code:
    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.

  7. #247
    Join Date
    Feb 2010
    Location
    Nr BrandsHatch, S'oaks UK
    Beans
    1,241
    Distro
    Lubuntu 13.04 Raring Ringtail

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    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.
    Last edited by bogan; June 2nd, 2011 at 01:06 PM. Reason: Correct #Post number

  8. #248
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by bogan View Post
    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.
    Last edited by MAFoElffen; June 2nd, 2011 at 02:18 PM.

    "Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637
    Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags

  9. #249
    Join Date
    Dec 2008
    Beans
    13

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by MAFoElffen View Post
    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.

  10. #250
    Join Date
    Feb 2010
    Location
    Nr BrandsHatch, S'oaks UK
    Beans
    1,241
    Distro
    Lubuntu 13.04 Raring Ringtail

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    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.'

Page 25 of 139 FirstFirst ... 1523242526273575125 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •