Page 34 of 132 FirstFirst ... 2432333435364484 ... LastLast
Results 331 to 340 of 1312

Thread: Graphics Resolution- Upgrade /Blank Screen after reboot

  1. #331
    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

    FAO.. MAFolffen, I think I have struck Gold, see extract from jockey.log.i , below. Jockey,log was MT.




    Also fresh copies of:
    Code:
    hwinfo --framebuffer,monitor
    From 11.04 @ 21.15.00 15/06/11

    Checking Settings:
    Code:
    alan@alan-MS-7318:~$ sudo -i
    [sudo] password for alan: 
    root@alan-MS-7318:~# gedit /etc/default/grub
    Only CMD Line settings:' ro quiet splash. '
    (gedit:3536): Other gedit Warnings ignored.
    CMD LINUXBOOT LINE parameters: ro quiet splash only.
    alan@alan-MS-7318:~$[/CODE] {[ See!! I did not have to type in all those typos ( Freudian Slip ) 'Sudos', as long as I am careful not to do things sudo would object to. Note the first few lines may not be 100%, as I got m,xed up editing between the files ]}
    I found the jockey file quite by chance, looking for Xorg & Xconf
    But First:
    Code:
    hwinfo --framebuffer, From 11.04 @ 21.15.00 15/06/11
    Start file:
    Code:
    root@alan-MS-7318:~# hwinfo --framebuffer
    [  Hal- Gtk: Warnings ignored.  ]
    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
    root@alan-MS-7318:~#

    End File.

    Code:
    root@alan-MS-7318:~# hwinfo --monitor
    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
    root@alan-MS-7318:~#
    End File.

    Does not seem to me much different in those!

    Jockey.log.1 File, ex Ubuntu11.04 recorded 23.00 15/06/11 by bogan,
    running Vista and Ubuntu 10.04 in partitions on the same ( Boot ) Hard Drive, CPU is Core Duo E6500, Video card GeForce 7650 GS, nVidia Driver173, wLan WiFi RealTek b/g adapter + Get-Net USB WiFi n USB Dongle.
    ( The latter two are relevant because, booting to Ubuntu Classic/Gnome, or Ubuntu Unity, handles them quite differently, 3-4 secs for one versus up to three minutes for the other, and several failed attempts .)

    Originally the Jockey.log.1 file was13 pages long, @+/- 45 Lines/Page = 13*45, sayes Google: That Equals 585 and about one in four is an error ! , or say 140 Failures.

    Extract from File
    Start File Jockey.log.1 recorded 15.06.11 by bogan.
    Code:
    root@alan-MS-7318:~# gedit ~/var/log/jockey.log.1
    011-05-28 21:47:11,416 DEBUG: loading custom handler /usr/share/jockey/handlers/nouveau3d.py 
    2011-05-28 21:47:11,480 DEBUG: Instantiated Handler subclass __builtin__.Nouveau3DHandler from name Nouveau3DHandler 
    2011-05-28 21:47:11,481 DEBUG: Experimental 3D support for NVIDIA cards not available 
    2011-05-28 21:47:11,481 DEBUG: all custom handlers loaded 
    2011-05-28 21:47:11,482 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97ceaec> about HardwareID('modalias', 'pci:v00001106d00003327sv00000000sd00000000bc06sc00i00') 
    2011-05-28 21:47:11,524 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x97ceaec> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw2,') 
    2011-05-28 21:47:11,662 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
    ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^

    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^
    Note: by bogan. It goes on like this for another four pages, with minor variations, and then goes on:
    2011-05-28 21:47:12,259 DEBUG: nvidia.available: falling back to default
    2011-05-28 21:47:12,280 DEBUG: got handler
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^


    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^
    Code:
    2011-05-28 21:47:12,979 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x97dd7ac> about HardwareID('modalias', 'input:b0000v0000p0000e0000-e0,5,kramlsfw2,') 
    2011-05-28 21:47:12,979 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x97dd7ac> about HardwareID('modalias',
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^
    And a further four pages of ' OpenPrintingDriverDB' queries to the DB, finally to end :
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^
    Code:
    2011-05-28 21:47:12,985 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x97dd7ac> about HardwareID('modalias', 'input:b0019v0000p0003e0000-e0,1,k8E,ramlsfw') 
    2011-05-28 21:47:12,985 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x97dd7ac> about HardwareID('modalias', 'acpi:PNP0303:PNP030B:') 
    2011-05-28 21:47:14,144 DEBUG: nvidia_current is not the alternative in use 
    2011-05-28 21:47:15,232 DEBUG: nvidia_current is not the alternative in use 
    2011-05-28 21:47:44,807 DEBUG: nvidia_current is not the alternative in use 
    2011-05-28 21:50:45,780 DEBUG: Shutting down
    File Ends.
    What a mice little Black Screen that could produce.bogan.
    Explanation follows tomorrow, well maybe today, actually.
    Sorry the editing is such a mess, but here it is 6.45.am GMT. and I have been at it all night.

    According to the Preview here, the two part files are attached. Please post or e-mail me if they are lost.

    CHAO "
    Attached Files Attached Files
    "Better Solutions may bring Worsened Problems": After Lao Tse, b. circa 405BC. a contemporary of Confucius, who died circa 600BC.
    They did things differently in those days, apparently!!

  2. #332
    Join Date
    Jan 2008
    Beans
    28
    Distro
    Xubuntu 11.04 Natty Narwhal

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    I installed Xubuntu 11.04 with Alternate Install CD on HP Pavilion G7-1007EM notebook. Everything worked well until yesterday I forcibly powered off the machine. After that I can not get into X session or get into text terminal. The screen is black, keyboard is not working and the fan is spinning like crazy. I tried all the switches in the grub startup you proposed and nothing works. I also renamed xorg.conf to xorg.old (with help of Ubuntu 10.10 Live CD). I made Xubuntu 11.04 Desktop Live CD and it also doesn't work. Black screen, no mater which switches were used. I create Ubuntu 10.10 Desktop Live CD and it works.

    I think downgrading kernel will help. Is there any recipe how to downgrade the kernel in my situation without text terminal? I will downgrade to Xubuntu 10.10 if I don't find any solution.

  3. #333
    Join Date
    Mar 2007
    Beans
    76

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    I will try again this weekend. How do the ubuntu development group find out about these problems and come up with plans to fix them? this seems to be a user group and few very dedicated users who are trying to help everyone.

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

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by zajc View Post
    I installed Xubuntu 11.04 with Alternate Install CD on HP Pavilion G7-1007EM notebook. Everything worked well until yesterday I forcibly powered off the machine. After that I can not get into X session or get into text terminal. The screen is black, keyboard is not working and the fan is spinning like crazy. I tried all the switches in the grub startup you proposed and nothing works. I also renamed xorg.conf to xorg.old (with help of Ubuntu 10.10 Live CD). I made Xubuntu 11.04 Desktop Live CD and it also doesn't work. Black screen, no mater which switches were used. I create Ubuntu 10.10 Desktop Live CD and it works.

    I think downgrading kernel will help. Is there any recipe how to downgrade the kernel in my situation without text terminal? I will downgrade to Xubuntu 10.10 if I don't find any solution.
    My condolences. Your laptop hae an AMD Radeon HD 6470M video chipset that is behind a switched Intel video chipset. Here is what ATI says about it's own Linux support of the 6xxxs series chipsets:
    Switchable Graphic Chips Warning

    WARNING
    As of AMD Catalyst™ 10.12, there is no support for switchable graphics chips in Linux. This means you cannot switch between the low power consumption of the integrated graphics chip and the high performance of the discrete graphics chip. Some manufacturers allow the IGP to be turned off in the BIOS and use the discrete card only (but this is not good for battery life). Otherwise, you are stuck with both GPU's turned on and draining the battery while only being able to use the IGP. Carefully research before purchasing a laptop, or you may not be able to fully use the hardware you pay for.

    There is a bug raised against the inability to switch between integrated and discrete graphics cards
    ATI's own disclaimer is sort of misleading. They have been trying to support this in Linux. There is also work on this in this community. There is hope. Unfortunately, your idea on downgrading the kernel or to downgrade versions to 10.10 doesn't seem to be some of the viable answers for this chipset- as I see the same problems in 10.10 (as 11.04) with the ATI 6xxx chipsets. On ones that "are" working, there still seems to be an annoyance where there will be a "watermark" on the screen that says "AMD Unsupported Hardware" in the lower right of the screen.

    The reason it comes up successfully with 10,10 and 11,04 LiveCD's is that it is coming up with the graphics of the Intel Video Chipset and not natively with the ATI Graphics Chipset. That limits your resolutions, video performance and such to the low-graphics mode of the Intel chipset.. It see's the first chipset and not what is beyond it...

    Now that I've given my little disclaimer above... Let's jump in to this and see if we can get you going again... Once we do that, then we'll retrace ground others have broken and see if we get get any further with this. No promises, but at least we'll try right? If not better, then at least as well as what is in current workarounds.

    First we need to get you "running" with a "usable" laptop. Remove your power cord and battery. Press and hold your power button for 30 seconds. Replace your battery and power cord. On initial boot up, go into your BIOS setup menu > find the BIOS option to switch your switchable video graphics to the Intel Chipset. Save and Exit. Continue Boot. As long as you still have your xorg.conf renamed to xorg.old and there is no xorg.conf present, it should be able to boot with a graphical X-session.

    If your BIOS does not have an option in it's BIOS Setup Menu to switch between chipsets, then tell me. There may be a kernel mechanism that may allow you to switch between GPUs.

    Before we start making changes, we need a snapshot of what you have and what is going on. Please open a terminal and execute the following commands (individually), then post the results:
    Code:
    sudo lspci -vv | grep VGA
    
    grep -i switcheroo /boot/config-2.6.*
    
    sudo hwinfo --framebuffer
    
    sudo hwinfo --monitor
    
    xrandr -q
    
    lsb_release -sd || cat /etc/*release &&  uname -s -r &&  unity --version && /usr/lib/nux/unity_support_test -p
    
    glxgears
    
    dpkg --get-selections | grep fglrx*
    
    dpkg --get-selections | grep xserver-xorg*
    Which will give us the info on your system, video card and monitor as 11.04 see's them.

    If hwinfo returns a "command not found" please install via
    Code:
    sudo apt-get install hwinfo
    And run those commands again to post the info from above.

    The next 2 files to post are:
    Code:
    /etc/X!!/xorg.old  # You said you renamed your xorg.conf to this name.
    /var/log/xorg.0.log
    That will tell us an idea on what drivers you are using, how they are configured and what modules are being loaded...

    After that... (credit 3602 and updates from him on 2011.25.07 are now included), ATI and 3 other sources-- edited, translated, cleaned up and adapted from those instructions)
    You might want to print or copy these instructions down before you go on. You are going to reboot a couple times and you might want to have these instructions handy during all that...

    /* --- Radeon Binary Driver Install --- */
    Step 1:
    Create an "ATI_Drivers" directory in your download directory to download/store your ATI driver in... Example:
    Code:
    mkdir ~/Downloads/ATI_Drivers/
    Step 2:
    Download Catalyst v11.x at this link: ATI.
    /*
    Recommended Version
    - Note: 11.10 works, 11.9 does not work with unity/compiz, 11.8 works...
    */
    Put into the directory you created above: ~/Downloads/ATI_Drivers/

    Step 3:
    Code:
    sudo  rm /usr/share/ati/fglrx-uninstall.sh
    If this returns "no such file or directory" it's fine. Just means that that is not present, but we need to make sure it's gone before we reinstall. Proceed.

    Step 4:
    Code:
    sudo apt-get remove --purge fglrx*
    This will probably return a couple of warnings: /usr/share/lib/fglrx and /usr/share/lib32/fglrx not empty. If so. then do:
    Code:
    sudo rm -rf /usr/share/lib/fglrx
    and
    Code:
    sudo rm -rf /usr/share/lib32/fglrx
    " Quote from an update from 3602:
    In step Four, there is a possibility that the announced "not empty" directories are not the ones listed. When I tried to install Catalyst 11.6 yesterday, the removal of Catalyst 11.5 prompted four "not-empty" directories that are not the ones listed. After an execution of rm -rf commands, I got kernel panics. I don't know whether this is an isolated case, but I sure hope so.

    Also after step Four, there is a possibility that apt-get announces DKMS is not needed anymore since the FGLRX DKMS modules are removed. This only happens if the only DKMS modules are of the FGLRX, but if one is to remove DKMS as per apt-get's suggestion, the later FGLRX installation cannot proceed (since no DKMS modules will be able to install without the DKMS itself).

    So DKMS is not to be removed even if apt-get announces so.
    Proceed.

    Step 5:.

    COPY THIS DOWN on some papers before doing it!

    Reboot. When in the purple boot screen with flashing dots, press F1 key to get into the emergency recovery board (white-on-black screen). Do:
    Code:
    sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old
    Then
    Code:
    sudo reboot
    You will get a GUI.

    Step 6:

    cd into whatever directory you have the .run file in.
    Code:
    cd ~/Downloads/ATI_Drivers/
    You might want/need to ensure you have all the basic to do this:
    Code:
    
    sudo apt-get update
    sudo apt-get install build-essential cdbs fakeroot dh-make debhelper  debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases
    If you are using 64bit OS, be sure to inslude ia32-libs before proceeding.
    Code:
    sudo apt-get install ia32-libs
    Quote from 3602 before next step:
    Also there should be no need in chmodding the file... But, better safe than sorry, I guess.
    Then build the debian packages. Look to where is says natty below in red, if you are installing for onieric, replaced that with oneiric. Meaning that you have to tell it what distro and version of to build the debian packages for!
    Code:
    sudo chmod +x (your_Installation_filename).run
    sudo sh (your_installation_filename).run --buildpkg  Ubuntu/natty
    Wait. A Synaptic window might pop up if you're doing this for the first time. Let it go away on it's own.
    Later you'll see the xterm returning four packages built, similar to:
    Code:
    fglrx_(version_number)-0ubuntu1_(platform).deb, 
    fglrx-amdcccle_(version_number)-0ubuntu1_(platform).deb, 
    fglrx-dev_(version_number)-0ubuntu1_(platform).deb, 
    fglrx-modaliases_(version)number)-0ubuntu1_(platform).deb
    Now
    Code:
    sudo dpkg -i *.deb
    Wait.

    Generate a generic Config...
    Step 7:
    Code:
    sudo aticonfig --initial -f
    If you have dual monitors or have an X2 card (e.g. 4870X2 or 5970)
    Code:
    sudo aticonfig --initial -f
    sudo aticonfig --set-pcs-str="DDX,EnableRandR12,FALSE"
    Then
    Code:
    sudo reboot
    then test your install
    Code:
    fglrxinfo
    If the last command returns "MESA" then for some reason it is still not using the ATI driver and there would be further instructions... One of which is redoing all the above steps.

    You can also test
    Code:
     
    fgl_glxgears
    If you experience issues or a hang, you may need to disable fast TLS.

    [code]

    sudo aticonfig --tls=0

    [code]


    If you have Switchable graphics, it should work now. "fglxinfo" should show the intel driver in use. You should then be able to switch to the ATI Radeon driver.

    If you have any problems playing flash files in FireFox after installing this driver, you may have to add/install the FireFox Flash-Aid extension. On onieric, there is now an experemental hardware video decode accelration... only supposed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000-series or newer, you have UVD2... Message me with your card model and I'll message back with the package names.
    Last edited by MAFoElffen; November 2nd, 2011 at 03:22 PM.
    Multi-Boot= Various flavours of Windows, Linux and Unix... Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    Boot Info Script courtesy of community member meierfra

  5. #335
    Join Date
    Jun 2011
    Beans
    1

    Smile Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Yes bro...i got blank screen too..indicated that wubildr is missing....how to resolve Bro?

  6. #336
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by MYCALL View Post
    Yes bro...i got blank screen too..indicated that wubildr is missing....how to resolve Bro?
    Welcome to the Ubuntu Forums!

    Your blank screen does not seem to be caused by a Graphics Problem- "wubildr.mbr is corrupt or missing" is a common WUBI boot problem... Which also means that you are running a form of Windows and Ubuntu in the same partition via WUBI. This has a lot to to do with a particular boot file and what slammed it...

    The place you really want to look for current solutions to this and/or ask about this is at this link: "The WUBI Megathread"
    Multi-Boot= Various flavours of Windows, Linux and Unix... Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    Boot Info Script courtesy of community member meierfra

  7. #337
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by johnthei View Post
    I will try again this weekend. How do the ubuntu development group find out about these problems and come up with plans to fix them? this seems to be a user group and few very dedicated users who are trying to help everyone.
    I'm happy to see you back at this!!! I will be ready to help you through this.

    I don't know about others there... I feel lucky to test the development builds. As someone there put it // sort of sum's it all up: "WOOT! Let The Breakage Begin!"

    We sure get to see things break (in a bad way) before others are exposed to them... Hopefully so others will not have to be exposed to them. We get to come up with solutions on our own and see other's solutions to things. We have to be involved with Launchpad in reporting bugs and trying LP fixes.

    I go a little further by following graphics issues and fixes in Xorg, the development builds, the ubuntu-xswat and xorg-edger PPA's, Launchpad and the NVidia and ATI boards. I get a little different perspective on this as I also test various other development builds of Linux and Unix, not just with Ubuntu and it's derivatives(developmwent builds). I also submit and follow upstream bugs of GNU Grub, Kernel.org and Xorg.

    "Change" is an interest of mine. Fixing thinks that are broke 'is' my hobby.
    Last edited by MAFoElffen; June 17th, 2011 at 11:25 PM.
    Multi-Boot= Various flavours of Windows, Linux and Unix... Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    Boot Info Script courtesy of community member meierfra

  8. #338
    Join Date
    Mar 2007
    Beans
    76

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    i found that on the nvidia site, for my pc, it says i need driver 96.43.19.

    i think this driver is not recognized by 11.04 for some reason in the 'try me' mode or the install me mode. after installing it, 11.04 doesnt see it and the screen is useless.

    any suggestions now for something to try?

    in the terminal mode, i tried the sudo apt-getupdate and it did download a bunch of stuff but it all seems 11.04 related now, natty narwall and wants me to put the natty cd in.
    nothing happens when i put it in. i will reboot and just see what happens.
    Last edited by johnthei; June 18th, 2011 at 01:11 AM. Reason: adding stuff

  9. #339
    Join Date
    Mar 2007
    Beans
    76

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    well that was a waste of 10 minutes. still get the unreadable graphics when i put the cd in. also at work today i made a new cd just in case there was some problem with it.

    all i get when i say unreadable graphics on the Try Ubuntu, is what is my desktop, but it is very useless. I can see where i have a few things on my desktop, i can somewhat see the top tool bar just cos I know it is there, but he size and format of what i am seeing makes it look like the screen is on a very bad lsd trip, and i cannot do anything with it, clicking on something seems to work as a very unviewable screen will show up, and i cannot read what it says.

  10. #340
    Join Date
    Jun 2008
    Location
    Alexandria, Egypt
    Beans
    161
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Hi MAFoElffen:
    I have upgraded my system to a new kernel after that new kernel I cant login to any thing I tried the new kernel it gives me a purple screen and sometimes a termenal screen stops at battery check, I have tried the old kernel and its the same, tried to login to recovery mood I have the same thing a purple screen.

    I have tried the live CD to re-install my nvidia driver as you mention but with no luck,

    is there anything you can help me with ?

Page 34 of 132 FirstFirst ... 2432333435364484 ... 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
  •