Announcement

Collapse
No announcement yet.

usplash resolution

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    usplash resolution

    I have a clean install of 12.04 that's on my eSATA drive and I used it to preview 12.04 before. The usplash on that install is correct. I hope I'm referring to the correct screen. I'm talking about the screen with the gear logo and the dots underneath that you see after the grub menu and before the login screen.

    Anyways, on my upgrade install (from 11.10) which is my main, everyday installation, that screen is stretched and appears to be a lower resolution (the gear is larger)
    Where do I make that adjustment?

    Thanks

    ** edit: It appears I need to be looking for how to fix the Plymouth resolution, not the usplash any more... **
    Last edited by reikimaster; May 01, 2012, 11:52 AM. Reason: changed title

    #2
    I believe it's the /etc/default/grub file. In mine, it's the:

    # 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=1600x900

    Where the GRUB_GFXMODE= line controls the resolution used. At least, it's what controls the screen resolution for Grub.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      yeah the screen resolution for Grub is fine. It's after the Grub menu disappears that bugs me

      Comment


        #4
        I think you are referring to the Plymouth theme found in /lib/plymouth/themes/kubuntu-logo/

        With the changes to Plymouth recently comes this section in kubuntu-logo-script

        // This is the high quality lookup code, it searches background/ for a perfect
        // match and only if none could be found it resorts to scaling.
        // This however requires packing *all* images in background/ into the initrd,
        // which at the time of writing amounts to >28 MiB.
        // file = "background/" + maxWidth + "x" + maxHeight + ".png";
        // DebugBottom(file);
        //
        // image = Image(file);
        // if (!image) {
        // Debug("Found no perfect match");
        // image = Image("background.png");
        // image = image.Scale(maxWidth, maxHeight);
        // } else {
        // Debug("Found perfect match");
        // }
        // return image;
        };
        I read that to mean background.png will be scaled to the maximum resolution for your screen, but since you make no mention of a missing background image it appears this is not working for you. As a test I replaced the default background image with a 1920x1200.png and while I wont say my new Plymouth background is 1920x1200, it's close, maybe 1600x1200.

        Any changes made should be followed up with "sudo update-initramfs -u" in a Konsole to update Plymouth. I can't add much more to this, but surely someone will come along and sort this further for you.

        cheers
        Kubuntu 12.04 - Acer Aspire 5750G

        "I don't make a great deal of money, but I'm ok with that 'cause I don't hurt a lot of people in the process either"

        Comment


          #5
          Yeah I was thinking it had something to do with the "vt handoff - vt7" but I don't think so any more.
          In my Grub boot menu I have the main install listed first and farther down the menu is the entry for the 12.04 installation on my eSATA drive. Other than the UUIDs being different, the parameters look the same. However my main install has the usplash (plymouth screen?) all stretched and ugly looking while if I choose the install on the eSATA drive it looks fine. (Same as if I use Boot Options when restarting the machine and select to boot from the eSATA drive ... it has its own Grub install as well)

          The background.png is the same on the eSATA as it is on the main drive. So it has to be a setting somewhere (followed by the update-initramfs you mentioned).

          I think I have to start looking in the initramfs-tools/conf.d and see if there are differences in those.

          Comment

          Working...
          X