Results 1 to 8 of 8

Thread: No loginscreen after upgrade from 9.10 to 10.04

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Beans
    15

    Re: No loginscreen after upgrade from 9.10 to 10.04

    Hi - were you able to figure out the problem? I've spent all day doing it without any luck. I just bought a new server with Intel rmm3, and thought that I'll keep that in the data center and do all the installation etc. remotely.

    However, in the initial testing that I'm doing, I'm not able to even get past the installation screen. I earlier tried vga=789 and other modes - these worked with Ubuntu 8.04, but not with 10.04 (probably because it is grub2). I tried to boot with Ubuntu 32bit Desktop, and it did show the "green" screen briefly, but then showed the Ubuntu desktop just fine.

  2. #2
    Join Date
    May 2010
    Beans
    2

    Re: No loginscreen after upgrade from 9.10 to 10.04

    Quote Originally Posted by marquivon View Post
    Hi - were you able to figure out the problem?
    Hi marquivon and Magnus1234

    No, sorry. Even though we spent several days trying to fix this issue, the problem persists.
    Funny thing is, that if you attach a display directly, everything works fine. I need to point out, that when connecting via RMM3, we can see the bootup process up to a certain extend and then, the screen goes black. But there has to be a solution somewhere...

    Anybody?
    Last edited by gartoffel; June 2nd, 2010 at 05:26 PM.

  3. #3
    Join Date
    Jun 2010
    Beans
    2

    Re: No loginscreen after upgrade from 9.10 to 10.04

    Hi,

    Is there any news about this problem?
    I have tried to modify some grub settings however it does not help.

    I think it should solve in server version somehow. Other case we have to replace Ubuntu with Debian.

  4. #4
    Join Date
    Aug 2009
    Beans
    1

    Re: No loginscreen after upgrade from 9.10 to 10.04

    Hello!

    We had the same problem with an intel server equipped with console module. Setting kernel parameters like vga= did not help.
    Just as in the op's case the directly connected screen worked, but we saw a blank screen after a few seconds on the virtual console software.

    However the fact that it went away only in the middle of the booting process give us a clue. We figured out that the cause of the problem is the loading of the vga16fb module.

    So we added these lines into /etc/modprobe.d/blacklist-framebuffer.conf:

    blacklist vga16fb
    blacklist vgastate (but maybe this line is unnecessary)

    and the problem went away.

    Hope this helps someone!
    Cheers!

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
  •