Page 18 of 137 FirstFirst ... 816171819202868118 ... LastLast
Results 171 to 180 of 1366

Thread: Graphics Resolution- Upgrade /Blank Screen after reboot

  1. #171
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    @Randahl Graves-

    Quote Originally Posted by MAFoElffen View Post
    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..
    Concurrent coexistance of Windows, Linux and Unix...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot

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

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

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

    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...)
    Last edited by MAFoElffen; May 20th, 2011 at 06:36 AM.
    Concurrent coexistance of Windows, Linux and Unix...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot

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

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by Breslau View Post
    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.
    Concurrent coexistance of Windows, Linux and Unix...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot

  4. #174
    Join Date
    May 2011
    Beans
    5

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

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

  5. #175
    Join Date
    May 2011
    Beans
    7

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Good morning. I only have one monitor hooked up at the moment, dunno if that matters. (Graphics are still bad)


    /etc/defualt/grub
    Code:
    # 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
    Code:
    # 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 ###
    Last edited by Randal Graves; May 20th, 2011 at 12:57 PM.

  6. #176
    Join Date
    Oct 2010
    Location
    Pikes Peak
    Beans
    1,175
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by Breslau View Post
    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.
    Jim
    Toshiba Satellite L505-S6946
    Precise, Fedora, Kororaa, Bodhi

  7. #177
    Join Date
    May 2011
    Beans
    5

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

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

  8. #178
    Join Date
    Oct 2010
    Location
    Pikes Peak
    Beans
    1,175
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    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.
    Jim
    Toshiba Satellite L505-S6946
    Precise, Fedora, Kororaa, Bodhi

  9. #179
    Join Date
    May 2011
    Beans
    5

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

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

  10. #180
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Graphics Resolution- Upgrade /Blank Screen after reboot

    Quote Originally Posted by Blasphemist View Post
    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...)
    Last edited by MAFoElffen; May 21st, 2011 at 06:34 PM.
    Concurrent coexistance of Windows, Linux and Unix...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot

Page 18 of 137 FirstFirst ... 816171819202868118 ... 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
  •