Announcement

Collapse
No announcement yet.

[Solved] Dual Boot-Issue

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    [Solved] Dual Boot-Issue

    Hey, I have an HP Pavilion Laptop running dual-boot: Windows Vista and Kubuntu 8.10

    When Kubuntu made software updates for me, and everything finished, it asked me to restart. And so I did. Now... when the computer starts and it asks me which OS to choose, it would give me 4 options:

    1. To choose Ubuntu 8.10 etc.
    2. To choose Ubuntu 8.10 Recovery
    3. To choose Ubuntu 8.10 memtest+ etc.
    4. Windows Vista

    But after Kubuntu made those updates for me... the options 1-3 Repeat themselves all over again ( as if I had TWO seperate Kubuntu operating systems )

    I tried recovery and all of that... and sometimes if I do a restart on Kubuntu, I get a "Konsole" window covering the whole screen, and can't have any GUI.

    So...how can I stay with only 'one' kubuntu and fix this all?

    Thanks in advance!
    The cyber-world is a whole different world indeed.
    Tags: None
    • Top
    • Bottom
    #2
    Re: Dual Boot-Issue

    Probably there is some problem with the file /boot/grub/menu.lst. If you can boot a Live CD, then mount the hard drive and copy that file, and post it here. Also while running in the Live CD, open the konsole and run
    Code:
    sudo blkid
    and copy that output and post it here, please.
    • Top
    • Bottom

    Comment

      #3
      Re: Dual Boot-Issue

      Originally posted by Daisuke
      I tried recovery and all of that...
      How did you do this recovery?
      Did you reinstall?
      Was this a clean install?

      Originally posted by Daisuke
      I get a "Konsole" window covering the whole screen, and can't have any GUI.
      Did you install any proprietary drivers for your video card?

      [mad]Berry
      Check out my website with Kubuntu how to's:  madberry.org
      • Top
      • Bottom

      Comment

        #4
        Re: Dual Boot-Issue

        Can you get onto a fully working session, not just seeing the terminal, by selecting your first option?

        If not try selecting the second instance of that option. If I remember correctly Grub duplicates entries when the kernel number or something similar changes.

        If you get a working session, the solution to remove the other entries at boot is simple. Edit /boot/grub/menu.lst
        To do this, I would enter
        Code:
        sudo kate /boot/grub/menu.lst
        into the terminal (you don't have to use kate if you prefer a different text editor).
        Enter your password and the text editor will open.
        Right at the bottom of the document you should see something like
        Code:
        ## ## End Default Options ##

title		Ubuntu 8.04
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.24-17-generic root=UUID=5e95eb94-52db-4a9d-b19c-36e6e5b772eb ro quiet splash 
initrd		/boot/initrd.img-2.6.24-17-generic
boot
quiet

title		Ubuntu 8.04 (recovery mode)
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.24-17-generic root=UUID=5e95eb94-52db-4a9d-b19c-36e6e5b772eb ro single 
initrd		/boot/initrd.img-2.6.24-17-generic
boot

### END DEBIAN AUTOMAGIC KERNELS LIST


root
title		Windows XP Professional
root		(hd0,2)
savedefault
makeactive
chainloader	+1
        Keep in mind that you will have 6 Ubuntu entries, rather than the two I have.

        To remove the unwanted boot options you could simply delete them here, save then close kate but I wouldn't recommend that just yet. The safer option is to simply edit the entries out.

        You may have noticed that most of the lines in the document begin with ##. If you add ## to the front of the options you no longer wish to see they will not be there next time you boot.
        For example if I edited my menu.lst to
        Code:
        title		Ubuntu 8.04
root		(hd0,0)
kernel		/boot/vmlinuz-2.6.24-17-generic root=UUID=5e95eb94-52db-4a9d-b19c-36e6e5b772eb ro quiet splash 
initrd		/boot/initrd.img-2.6.24-17-generic
boot
quiet

##title		Ubuntu 8.04 (recovery mode)
##root		(hd0,0)
##kernel		/boot/vmlinuz-2.6.24-17-generic root=UUID=5e95eb94-52db-4a9d-b19c-36e6e5b772eb ro single 
##initrd		/boot/initrd.img-2.6.24-17-generic
##boot

### END DEBIAN AUTOMAGIC KERNELS LIST


root
title		Windows XP Professional
root		(hd0,2)
savedefault
makeactive
chainloader	+1
        "Ubuntu 8.04 (recovery mode)" would not be visible at boot.

        Hope this helps steer you to a solution
        • Top
        • Bottom

        Comment

          #5
          Re: Dual Boot-Issue

          I'll try that right now and give you my response, thanks!
          The cyber-world is a whole different world indeed.
          • Top
          • Bottom

          Comment

            #6
            Re: Dual Boot-Issue

            Thanks everyone for all your help!! I edited the entries out (##) with kate. But before finishing, I'd like to ask a few more questions ...

            1. Can I safely delete those duplicated entries with kate so everything goes back to normal?

            2. Luckily, the terminal doesn't appear as a 'substitution' for the GUI anymore. But the reason I believe it happened was after I did the OS's regular software update (because on my PC with Kubuntu 8.04, the same thing happened). The double entry at the boot (both in my laptop and PC) ocurred after those software updates. Any particular reason for these incidents?

            3. And lastly, is it safe to do other tasks while those updates are running? I have 20 software updates right now and I'm not sure....
            The cyber-world is a whole different world indeed.
            • Top
            • Bottom

            Comment

              #7
              Re: Dual Boot-Issue

              1) It is perfectly safe to remove the entries from menu.lst providing you are sure they are the correct ones to remove. I recommended you to comment them out as a precautionary measure. If you are sure you want to delete them completely, feel free.

              2) If you study the entries carefully you will see that they are not exact duplicates. The kernel numbers have changed.

              3) I'm sure a bit of web-browsing will be fine while you upgrade, I know I normally do.
              • Top
              • Bottom

              Comment

                #8
                Re: Dual Boot-Issue

                Allright! Thanks again for everything. Everyone here are really a great help.

                Daisuke
                The cyber-world is a whole different world indeed.
                • Top
                • Bottom

                Comment

                  #9
                  Re: [Solved] Dual Boot-Issue

                  Maybe the entries weren't exactly the same.

                  If so, it's not a bug, it's a feature

                  If the kernel gets updated, you will have multiple entries in the GRUB menu, indicating different kernels (they will have slightly different numbers). Suppose your system fails, you could still select the older, working kernel version.
                  Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!
                  • Top
                  • Bottom

                  Comment

                    #10
                    Re: [Solved] Dual Boot-Issue

                    Allright, and how will I know I have selected the updated working entry? I edited the second 'duplicate entries' out. Was that the old one or the newly updated? Or is it the same... just a copy or something? Here, let me post what I currently have in the file:

                    Code:
                    ## ## End Default Options ##

title		Ubuntu 8.10, kernel 2.6.27-9-generic
uuid		ea810232-0e7b-495a-8627-8c228d63de17
kernel		/boot/vmlinuz-2.6.27-9-generic root=UUID=ea810232-0e7b-495a-8627-8c228d63de17 ro quiet splash 
initrd		/boot/initrd.img-2.6.27-9-generic
quiet

title		Ubuntu 8.10, kernel 2.6.27-9-generic (recovery mode)
uuid		ea810232-0e7b-495a-8627-8c228d63de17
kernel		/boot/vmlinuz-2.6.27-9-generic root=UUID=ea810232-0e7b-495a-8627-8c228d63de17 ro single
initrd		/boot/initrd.img-2.6.27-9-generic

##title		Ubuntu 8.10, kernel 2.6.27-7-generic
##uuid		ea810232-0e7b-495a-8627-8c228d63de17
##kernel		/boot/vmlinuz-2.6.27-7-generic ##root=UUID=ea810232-0e7b-495a-8627-8c228d63de17 ro quiet splash 
##initrd		/boot/initrd.img-2.6.27-7-generic
quiet

##title		Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
##uuid		ea810232-0e7b-495a-8627-8c228d63de17
##kernel		/boot/vmlinuz-2.6.27-7-generic ##root=UUID=ea810232-0e7b-495a-8627-8c228d63de17 ro single
##initrd		/boot/initrd.img-2.6.27-7-generic

title		Ubuntu 8.10, memtest86+
uuid		ea810232-0e7b-495a-8627-8c228d63de17
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title		Windows Vista/Longhorn (loader)
root		(hd0,0)
savedefault
makeactive
chainloader	+1
                    ... *thinking*
                    The cyber-world is a whole different world indeed.
                    • Top
                    • Bottom

                    Comment

                      #11
                      Re: [Solved] Dual Boot-Issue

                      Ubuntu 8.10, kernel 2.6.27-9-generic
                      Is the entry you have kept, and
                      Ubuntu 8.10, kernel 2.6.27-7-generic
                      is the entry you have removed.

                      A kernel upgrade from 2.6.27-7 to 2.6.27-9 is what caused the extra entries in the menu.

                      What is a kernel?
                      • Top
                      • Bottom

                      Comment

                        #12
                        Re: [Solved] Dual Boot-Issue

                        Oh, awesome then. Again, much thanks for everything.
                        The cyber-world is a whole different world indeed.
                        • Top
                        • Bottom

                        Comment

                        Previous template Next
                        Working...
                        X