Welcome, Guest. Please login or register.
April 21, 2014, 14:24:51 PM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Installing Pardus
| | |-+  Grub2 entry Pardus 2011
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: Grub2 entry Pardus 2011  (Read 6244 times)
scorptig
Newbie
*
Posts: 9


View Profile
« on: January 31, 2011, 07:36:11 AM »

Good Morning,

I've installed Pardus 2011 64 bit on some partitions, I am using Mint Linux 10.00 Isadora 64 bit Grub2 as bootloader.
Issue I get when I select Pardus from my selection
Code:
error : unknown command 'kernel'
error : you need to load the kernel first
Press any key to continue

So I've created 40_custom /etc/grub.d/40_custom
Code:
#!/bin/sh
exec tail -n +3 $0
echo "Adding Pardus" >&2
# 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.

menuentry "Pardus" {
set root=(hd0,6)
kernel /boot/kernel-2.6.37 splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}


My partition is sda7, I updated update-grub, it shows Pardus. Did my os-probe, all is fine.

I am using Nvidia video card.

Note when I installed Pardus I had occasional issues with Mouse freezing when I adjusted date and time, and started over. However I did succeed in Installing it in safe mode.

Also note when I chose my partitions /usr was not available in drop-down menu. I manually created it /usr and it works, I also use /var  along with / and /home.

Right now the issue is I cannot boot Pardus. I've done this before adding an entry. That's why I am writing in forum.

Note I did install Pardus on a 32 bit PC, and used it as boot loader after modifying menu.lst, no issues.

Thank you in advance for your response.
« Last Edit: January 31, 2011, 07:43:54 AM by scorptig » Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #1 on: January 31, 2011, 08:01:32 AM »

Hi, scorptig,

I too have an Nvidia card (specs below in my signature) and experienced problems booting Pardus 2011 (32-bit). I don't know if your problem is identical, but you might take a look at these threads and try adding the boot parameter " xorg=safe ":

http://worldforum.pardus-linux.nl/index.php?topic=3582.0
"2011 Won't Install." 24 Jan. 2011

http://worldforum.pardus-linux.nl/index.php?topic=3475.0
"Pardus 2011 Nvidia Install." 31 Oct. 2010.

http://worldforum.pardus-linux.nl/index.php?topic=3589.0
"Nvidia Driver on Pardus 2011." 26 Jan. 2011.

This allowed me to boot Pardus, then I blacklisted the Nouveau driver and installed the proprietary Nvidia driver(s). It was a relatively simple fix and things have worked fine for me since then.

Just for reference, below is my Legacy GRUB stanza for Pardus 2011. I multiboot Linux (including Debian 6.0 Squeeze, which uses GRUB2); I installed 2011's Legacy GRUB to my MBR and it is successfully booting all my distros (although I had to do some manual tweaking of their GRUB entries):

Code:
title Pardus 2011
uuid 5b2d3d30-4195-477e-93c7-9a84c7a94928
kernel /boot/kernel-2.6.37 root=UUID=5b2d3d30-4195-477e-93c7-9a84c7a94928
resume=/dev/sda6 splash quiet blacklist=nouveau
initrd /boot/initramfs-2.6.37

HTH.
Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
scorptig
Newbie
*
Posts: 9


View Profile
« Reply #2 on: January 31, 2011, 09:30:28 AM »

Thank you for your reply, tried it no success, same error.
Other option, install Pardus use it's boot-loader and edit menu.lst accordingly.
May well try that later today..
Thanks again..
Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #3 on: February 01, 2011, 06:42:19 AM »

@scorptig,

Sorry to hear that didn't work for you. Although I'm still fumbling around with GRUB 2 basics myself, I do have another suggestion you might try ... I think I spotted a couple of mistakes in your GRUB 2 entry for Pardus 2011.

You could modify your GRUB 2 stanza to look like this:

menuentry "Pardus" {
set root=(hd0,6)
linux /boot/kernel-2.6.37 root=UUID=[fill in value of your root partition] resume=UUID=[fill in value of your swap partition] splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}

The end result would be:

Code:
menuentry "Pardus" {
set root=(hd0,6)
linux /boot/kernel-2.6.37 root=UUID= resume=UUID= splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}

You can find out the UUIDs of your hard drive's partitions by typing this command as root:

Code:
# blkid

It should produce output that looks somewhat like the following:

Code:
root@luisbienteveo:/home/david# blkid
/dev/sda1: UUID="63f75e7a-ca71-43f9-b798-4f8c6983b47b" TYPE="ext4"
/dev/sda3: LABEL="PARDUS_ROOT" UUID="5b2d3d30-4195-477e-93c7-9a84c7a94928" TYPE="ext4"
/dev/sda5: UUID="a2497eba-f580-463e-960f-ef99e6bf4be1" TYPE="ext4"
/dev/sda6: LABEL="SWAP" UUID="a0da1423-a715-4c8d-b65d-1d638f54c84f" TYPE="swap"
/dev/sda10: LABEL="_Fedora-14-i686-" UUID="1d9610d9-bc51-4081-9058-fef04dc97af7" TYPE="ext4"
/dev/sda11: UUID="150c29e6-7944-48e0-a6d9-7d7fede7586d" TYPE="ext4"
[. . .]

Then run
Code:
sudo update-grub
and see if Mint's GRUB 2 will boot Pardus.

Finally, just in case you'd like some additional background on GRUB 2, I found these two resources to be very helpful:

http://www.dedoimedo.com/computers/grub-2.html
Dedoimedo. "GRUB 2 Bootloader: Full Tutorial."

http://ubuntuforums.org/showthread.php?t=1195275
"The GRUB 2 Guide." 23 June 2009.

HTH,
=david
Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
scorptig
Newbie
*
Posts: 9


View Profile
« Reply #4 on: February 02, 2011, 00:43:40 AM »

Good Evening,

I tried the new modifications

my 40_custom reads now like this

Code:
#!/bin/sh
exec tail -n +3 $0
echo "Adding Pardus" >&2
# 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.

menuentry "Pardus" {
set root=(hd0,6)
linux /boot/kernel-2.6.37 root=UUID="54636f7a-34b5-486f-a670-a095a22bd821" resume=UUID="31bd2d6e-4566-4cb9-aefd-2146ea41735f" splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}

did my
Code:
sudo chmod +x  /etc/grub.d/40_custom

also did my
Code:
sudo update-grub
& reboot

Code:
error: unknown filesystem
error: you need to load the kernel first

here is a copy of my current 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 part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set 06f295c9-d6dc-448c-9f84-ccf76130aef1
if loadfont /share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
set locale_dir=($root)/boot/grub/locale
set lang=en
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
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
insmod png
if background_image /boot/grub/linuxmint.png ; then
  set color_normal=white/black
  set color_highlight=white/light-gray
else
  set menu_color_normal=white/black
  set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Linux Mint 10 64-bit, 2.6.35-25-generic (/dev/sda1)' --class linuxmint --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=4e638c9a-65ff-40b1-a407-613d62cf4456 ro   quiet splash
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry 'Linux Mint 10 64-bit, 2.6.35-25-generic (/dev/sda1) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
echo 'Loading Linux 2.6.35-25-generic ...'
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=4e638c9a-65ff-40b1-a407-613d62cf4456 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-25-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### 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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 4e638c9a-65ff-40b1-a407-613d62cf4456
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, with Linux 2.6.35-25-generic (on /dev/sdb1)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set 2cbab62f-81df-455c-955b-d2e409955f86
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=2cbab62f-81df-455c-955b-d2e409955f86 ro quiet splash
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry "Ubuntu, with Linux 2.6.35-25-generic (recovery mode) (on /dev/sdb1)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set 2cbab62f-81df-455c-955b-d2e409955f86
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=2cbab62f-81df-455c-955b-d2e409955f86 ro single
initrd /boot/initrd.img-2.6.35-25-generic
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
echo "Adding Pardus" >&2
# 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.

menuentry "Pardus" {
set root=(hd0,6)
linux /boot/kernel-2.6.37 root=UUID="54636f7a-34b5-486f-a670-a095a22bd821" TYPE="ext4" resume=UUID="31bd2d6e-4566-4cb9-aefd-2146ea41735f" TYPE="swap" splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}
### 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 ###

Thank in you in advance for your support, I await any other possibilities.

Note I did a Fresh Install using xorg=safe of Pardus 2011 64 bit, without boot loader

And I did a fresh install of Mint-Linux 10.00 Isadora 64 bit, which serves as bootloader for all OS on my two hard drives.

Also I did
Code:
sudo blkid
results :

Code:
sudo blkid
/dev/sda1: UUID="4e638c9a-65ff-40b1-a407-613d62cf4456" TYPE="ext4"
/dev/sda2: UUID="06f295c9-d6dc-448c-9f84-ccf76130aef1" TYPE="ext4"
/dev/sda3: UUID="03d90448-f1fc-4fa0-a5b0-83b0f3df09eb" TYPE="ext4"
/dev/sda5: UUID="20014abd-8427-4e53-b275-ed946889ec93" TYPE="ext4"
/dev/sda6: UUID="31bd2d6e-4566-4cb9-aefd-2146ea41735f" TYPE="swap"
/dev/sda7: UUID="54636f7a-34b5-486f-a670-a095a22bd821" TYPE="ext4"
/dev/sda8: UUID="9e86f6cb-459a-48ce-8eea-07d7b5552cef" TYPE="ext4"
/dev/sda9: UUID="0fe52d39-0237-4799-a020-fa8d3b9f8ef3" TYPE="ext4"
/dev/sda10: UUID="f14b4e40-1b01-48d1-a85b-75c893da15c4" TYPE="ext4"
/dev/sdb1: UUID="2cbab62f-81df-455c-955b-d2e409955f86" TYPE="ext4"
/dev/sdb2: UUID="423ac920-e958-4576-8a56-3c5c70215f2f" TYPE="ext4"
/dev/sdb3: UUID="cf48f1f6-d99b-4e38-aa02-61710c89b50e" TYPE="ext4"
/dev/sdb5: UUID="246b831a-ec0b-44e2-bb40-730b5817884d" TYPE="ext4"
/dev/sdb6: UUID="c5a638d7-e78e-4217-a7b0-ccfc5e5efd33" TYPE="swap"
/dev/sdb7: UUID="849c3466-0fe2-4a69-82f8-5899fa25b78e" TYPE="ext4"
/dev/sdb8: UUID="42716fbe-b8a3-4261-a788-afa99b0c5716" TYPE="ext4"

That code is very handy, thank you.

Looking forward to some feedback.
Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #5 on: February 02, 2011, 06:26:58 AM »

@scorptig,

You're welcome. Sorry that didn't work, either ... However, I think I found the mistakes. (I should have been paying closer attention and noticed the error in your root partition numbering the first time! That is the critical error, I believe.)  Embarrassed

Your Pardus root partition is /sda7, and your swap partition is /sda6, correct? If so, I believe that you only need to make a couple of minor corrections: the GRUB 2 numbering of your Pardus root partition; and removing some extraneous quotation marks and file type labels.

How about trying this variation:

Code:
menuentry "Pardus" {
set root=(hd0,7)
linux /boot/kernel-2.6.37 root=UUID=54636f7a-34b5-486f-a670-a095a22bd821
resume=UUID=31bd2d6e-4566-4cb9-aefd-2146ea41735f splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}

Please note what I changed here:

The root should be numbered as (hd0,7) not (hd0,6) [which is the Legacy GRUB numbering system].

You do not need the quotation marks after the UUID designations, e.g.:

root=UUID="54636f7a-34b5-486f-a670-a095a22bd821" should be

root=UUID=54636f7a-34b5-486f-a670-a095a22bd821

(The same is true for the UUID designation of your swap partition: resume=UUID=31bd2d6e [...])

Also, I don't think that you need to add the filesystem types (e.g., "TYPE="ext4") in the GRUB 2 stanza. That may be introducing problems unnecessarily.

If that fails, you might also try this stanza:

Code:
menuentry "Pardus" {
set root='(hd0,msdos7)'
linux /boot/kernel-2.6.37 root=UUID=54636f7a-34b5-486f-a670-a095a22bd821
resume=UUID=31bd2d6e-4566-4cb9-aefd-2146ea41735f splash=silent quiet vga=0x31a
initrd /boot/initramfs-2.6.37
}

Although I know the '(hd0,msdos7)' looks rather strange, I'm patterning it after the GRUB 2 stanza which my Debian Squeeze installation had automatically set up for Pardus. (Note: In this case, I'm not using GRUB 2 to control my computer's MBR; rather, GRUB 2 is installed to my Debian root partition (/sda12) and Pardus' Legacy GRUB is on the MBR and is controlling my multiboot setup).

With a bit of luck, maybe this time will work for you. I'll keep my fingers crossed.

P.S.
I may be approaching the limit of my competency with this. I'm an "expert" on GRUB 2 in the same sense as the Internet's definition of "expert": "Someone from out of town, with a PowerPoint presentation."  Smiley
« Last Edit: February 02, 2011, 20:39:47 PM by kalwisti » Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
scorptig
Newbie
*
Posts: 9


View Profile
« Reply #6 on: February 02, 2011, 21:23:09 PM »

Thanks for new modifications, I think we are getting closer.

My current 40_custom file

Code:
#!/bin/sh
exec tail -n +3 $0
echo "Adding Pardus" >&2
# 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.

menuentry "Pardus" {
set root=(hd0,7)
linux /boot/kernel-2.6.37 root=UUID=54636f7a-34b5-486f-a670-a095a22bd821 resume=UUID=31bd2d6e-4566-4cb9-aefd-2146ea41735f splash=silent quiet blacklist=nouveau
initrd /boot/initramfs-2.6.37
}

Code:
#!/bin/sh
exec tail -n +3 $0
echo "Adding Pardus" >&2
# 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.

menuentry "Pardus" {
set root=(hd0,msdos7)
linux /boot/kernel-2.6.37 root=UUID=54636f7a-34b5-486f-a670-a095a22bd821 resume=UUID=31bd2d6e-4566-4cb9-aefd-2146ea41735f splash=silent quiet blacklist=nouveau
initrd /boot/initramfs-2.6.37
}

I added note blacklist=nouveau because I had a HW detect hardware error

Next I get following error when attempting to load Pardus in both instances.

Resume: Could not stat the resume device file "UUID=31bd2d6e-4566-4cb9-aefd-2146ea41735f "
Please type in the full path name to try again or press Enter to boot the system:

Now note at this point I was looking at this current post, the original response from yourself kalwisti

your code :

Code:
title Pardus 2011
uuid 5b2d3d30-4195-477e-93c7-9a84c7a94928
kernel /boot/kernel-2.6.37 root=UUID=5b2d3d30-4195-477e-93c7-9a84c7a94928
resume=/dev/sda6 splash quiet blacklist=nouveau
initrd /boot/initramfs-2.6.37

How would that be written within 40_custom, as above I tried it, had original errors.
Set root is not present above
I tried also set root=uuid(5b2d3d30-4195-477e-93c7-9a84c7a94928)

In all instances I did sudo update-grub
Thank you, awaiting your response.
Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #7 on: February 02, 2011, 21:57:37 PM »

Hi,

That's good news; it looks like progress is being made. The only problem, as I said, is that I'm approaching the limits of my knowledge and experience.

I can try Googling some more tonight after work. In the meantime, here's a couple of additional variations you could try; this is what occurs to me off the top of my head:

In your 40_custom GRUB 2 entry, try changing

resume=UUID=31bd2d6e [ ... etc.]

to

resume=/dev/sda6

Also, try removing the blacklist=nouveau parameter and replace it with xorg=safe

As a final variant, you could try removing the blacklist=nouveau parameter entirely and not replacing it with anything.

Perhaps one of these will do the trick. If they don't work, please report back what sort of error messages you get with each variation and I will do some more research. I'm not ready to give up yet.

< Edit: >

scorptig wrote:

Quote
How would that be written within 40_custom, as above I tried it, had original errors.
Set root is not present above
I tried also set root=uuid(5b2d3d30-4195-477e-93c7-9a84c7a94928)

To clarify, I should mention here that you do not want to use that UUID=5b2d3d30 [... etc.] value because that UUID is specific to my system (where Pardus' root is located on the /sda3 partition). We must use the UUID for your system so that GRUB 2 is pointed to the correct partition (/sda7). That's what we're trying to accomplish in the GRUB stanzas discussed above.

P.S.
Another idea / suggestion: You might consider registering as a user at the LinuxQuestions forum ( http://www.linuxquestions.org/ ). There are some very knowledgeable folks there, with years of Linux experience, who can probably give you better advice. Also, the Linux Mint forum has users who are very familiar with GRUB 2, since so many versions of Mint use it by default. I'm not currently running Mint, but I have in the past, and I had a positive experience with their User Forum -- it was active, with friendly and helpful people. Since you are using Isadora and its GRUB 2 is managing your MBR, I think it would be a perfectly legitimate place to ask.

« Last Edit: February 03, 2011, 02:00:12 AM by kalwisti » Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
scorptig
Newbie
*
Posts: 9


View Profile
« Reply #8 on: February 03, 2011, 09:09:12 AM »

Hi again did try earlier

Code:
resume=UUID=31bd2d6e [ ... etc.]

to

resume=/dev/sda6

It loaded stuff it could find with error, I'll be more specific tomorrow. Getting late I had a few Network issues and issues with another Workstation, suddenly 10 hours vanished. I do appreciate your knowledge base, it helps. I am also thinking of doing two other tests.
One install where my current Mint Linux, Pardus 64 bit and see how that works out. I am familiar with menu.lst and adding entries is easy.
Then another variation on my tests, install Sabayon Linux and see how it's boot loader works with Pardus.
Along the way I am sure more data will be collected.

I'll go through your new suggestions, and give you details on what I encounter.

Thanks again
Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #9 on: February 03, 2011, 10:46:27 AM »

Maybe >this manual< will help to get it done

And a very wise remark from this manual:
Quote
If you're asking me, at the time being, you should use GRUB legacy as your default bootloader, because it is production quality and has known, established support channels. Running GRUB 2 will place you in a minority.
And if you decide to use GRUB Legacy, there is also this "Adding a GRUB 2 item in the boot-menu of Pardus" Wiki.
« Last Edit: February 03, 2011, 13:03:14 PM by atolboo » Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #10 on: February 04, 2011, 18:34:07 PM »

Yes, atolboo's how-to worked for me when I added a grub 2 distro to Pardus' boot manager. 

I also had no problems when I used Kanotix' Grub 2 as main grub menu, as it added Pardus with no problems, as well as another distro.  In case you want to compare. grub.cfg file:

Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set 0985bf93-2eb7-4a56-9cfd-a3bd2c3ac800
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set 0985bf93-2eb7-4a56-9cfd-a3bd2c3ac800
insmod png
if background_image /boot/grub/Kanotix64Penguins.png ; then
  set color_normal=light-blue/black
  set color_highlight=white/blue
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Kanotix64 GNU/Linux, Linux 2.6.32-21-generic" {
insmod ext2
set root=(hd1,5)
search --no-floppy --fs-uuid --set 0985bf93-2eb7-4a56-9cfd-a3bd2c3ac800
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=0985bf93-2eb7-4a56-9cfd-a3bd2c3ac800 ro quiet vga=791 splash quiet
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 98747aee747acf0e
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry "Pardus 2011 RC [2.6.37] (on /dev/sdb6)" {
insmod ext2
set root=(hd1,6)
search --no-floppy --fs-uuid --set 999cbea6-0cec-4b7a-a380-842d0707bac3
linux /boot/kernel-2.6.37 root=UUID=999cbea6-0cec-4b7a-a380-842d0707bac3 resume=/dev/sdb8 quiet splash blacklist=nouveau
initrd /boot/initramfs-2.6.37
}
menuentry "Other OS, with Linux 2.6.35-24-generic (on /dev/sdb7)" {
insmod ext2
set root=(hd1,7)
search --no-floppy --fs-uuid --set f35f01f0-49e8-4855-a426-1b76f4173033
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=f35f01f0-49e8-4855-a426-1b76f4173033 ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic
}
menuentry "Other OS, with Linux 2.6.35-24-generic (recovery mode) (on /dev/sdb7)" {
insmod ext2
set root=(hd1,7)
search --no-floppy --fs-uuid --set f35f01f0-49e8-4855-a426-1b76f4173033
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=f35f01f0-49e8-4855-a426-1b76f4173033 ro single
initrd /boot/initrd.img-2.6.35-24-generic
}
### 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 ###
Logged
scorptig
Newbie
*
Posts: 9


View Profile
« Reply #11 on: February 05, 2011, 00:53:36 AM »

OK in reply to proposed modifications to my 40_custom, did those.
New issues.
However, I decided on two tests, to install Pardus on my hard drive sda

Code:
/root sda1
/usr /sda2
/var /sda3
/home /sda5
/swap /sda6

So during install process added xorg=safe
Anyway as far as initial install, really no issues smooth, fast, I think 10 minutes, anyway the issue is upon reboot

It simply does not load Pardus, it stays on sda and does nothing.

So if i cannot boot a fresh install where Pardus boot loader is selected, then this is another issue alltogether.

So at  this point I had to install Mint Linux back as it serves as my boot loader, I might wait till next 64 bit release of Pardus.

However I do have Pardus working on my other computer, a 32 bit AMD XP-2400+ unit..

Thanks for all the help, I've added bookmarks to my grub section.
Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #12 on: February 05, 2011, 06:37:41 AM »

However, I decided on two tests, to install Pardus on my hard drive sda

Code:
/root sda1
/usr /sda2
/var /sda3
/home /sda5
/swap /sda6

So during install process added xorg=safe
. . . [A]nyway the issue is upon reboot

It simply does not load Pardus, it stays on sda and does nothing.

So if i cannot boot a fresh install where Pardus boot loader is selected, then this is another issue alltogether.

Hi, scorptig,

Would you mind clarifying a couple of things here?

In this test, did you install Pardus's Legacy GRUB to the MBR and let it control the boot process? (This is what I'm guessing).

Or was Mint's GRUB 2 controlling the MBR? If so, did you install Pardus's Legacy GRUB to its root partition (/sda1)?

Another possibility could be that this was caused by a corrupted download and/or a bad burn. Although I imagine that you've already considered these factors ... did you check to make sure the md5sum and the sha1sum of the downloaded .iso are correct? Did you perform a media check of the burned DVD before you installed it?

This certainly sounds like strange behavior. It may be possible that you've uncovered a bug with the 64-bit version. (I'm reluctant to try experimenting with it myself on my main PC because I don't have any spare partitions currently, and the 32-bit version of 2011 is working fine for me, so I'd like to avoid messing it up).

However I do have Pardus working on my other computer, a 32 bit AMD XP-2400+ unit..

Could you clarify this statement a bit, please? Does it mean that you successfully installed the 32-bit version of 2011 on this machine, and that it booted without any problems?

If that is the case, it seems to suggest that either (a). there is some sort of problem / bug with the 64-bit version, or (b). there is some sort of major incompatibility problem with the hardware on that particular computer.

Perhaps atolboo and/or Lisa can tell us if there are open bugs on the 64-bit version which describe similar behavior(s). I looked at the Pardus Bugzilla tracker but it was my first time using it, and I didn't find much information. (My fault for searching ineffectively, probably).

You're very welcome for the help. I'm sorry I don't have enough in-depth knowledge to solve your problem with the 64-bit version of Pardus 2011.

Have a good weekend,
=david

Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #13 on: February 05, 2011, 20:44:40 PM »

Hi kalwisti and scorptig!

I'm so far confused about the nature of the bug, so I wouldn't know how to begin posting it.


My difference between scorptig's install and mine is that he had installed Pardus on his already existing Linux OS distro that uses grub2.  I on the other hand installed kanotix w/ grub2 on top of an already existing Pardus and its grub on MBR. 
I will have to try testing this later by doing it the other way around.  I always let any distro I install install its grub to the MBR, in my case, on the first hard drive that has XP.  If I want to use another grub menu, I re-install the one I like.  In the case of Pardus, I use the Pardus installation disk recover utility do this (recover), and then log in, and manually add a grub2 entry in the Boot Manager as atolboo described.

I also see a difference in scorptig's grub.cfg that mine does not contain:
"insmod part_msdos"
I looked this up thinking it was a bug, but it isn't according to this:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/663137

Maybe if you add:
Code:
insmod part_msdos
insmod ext2
after your custom_40 Pardus entry, above line, set root
I'm just guessing here. 
Logged
kalwisti
Pardus fellow craft
**
Gender: Male
Posts: 131



View Profile
« Reply #14 on: February 05, 2011, 21:50:19 PM »

My difference between scorptig's install and mine is that he had installed Pardus on his already existing Linux OS distro that uses grub2.  I on the other hand installed kanotix w/ grub2 on top of an already existing Pardus and its grub on MBR. 

Hi, Lisa,
Thanks for chiming in on this thread.

I know from experience that Pardus' Legacy GRUB (when controlling the MBR) can boot GRUB 2-based distros without a problem. At different times, I have installed Mint, Ubuntu and Debian Squeeze -- all of which use GRUB 2 as their bootloader. (Actually, at the moment I'm also trying out Salix OS [a very nice Slackware-based distro], which uses LILO as its default bootloader. I got Pardus to boot it successfully after some trial and error).

Although I know how to manually edit GRUB stanzas in /boot/grub/menu.lst, Pardus' Boot Manager utility makes it easier to edit these stanzas and to multiboot. I'm very impressed with it; since I haven't seen it in other Linux distros, I assume it's one of those tools which are unique to Pardus.

I will have to try testing this later by doing it the other way around. 

I no longer have a spare PC to experiment with (I spruced up the old Frankencomputer and gave it to a friend who was interested in trying Linux), so I can't test this firsthand without possibly borking my production machine -- which I prefer not to do. Like you, I haven't tried installing a GRUB 2-based distro, let its GRUB 2 take over the MBR, and then try to boot Pardus with it ...

I always let any distro I install install its grub to the MBR, in my case, on the first hard drive that has XP.  If I want to use another grub menu, I re-install the one I like. 

My installation strategy is slightly different than yours. Based on suggestions I've read in several different forums, when I install a new Linux distro in my multiboot setup, I always choose to install its GRUB (or LILO) to the root partition of the new distro. (With my installs, I typically create a root (/) partition and a separate /home partition). I don't let it take over the existing MBR (which is controlled by Pardus).

Once the installation is complete, I boot into Pardus and use the Disk Manager utility and Dolphin to access the root partition of the newly installed distro. Then I copy the new distro's menu.lst into a blank text file and save it. Finally, I open Pardus' Boot Manager utility, paste in the necessary info from the text file, and reboot to see if I can boot into the new distro. After one has gained some experience, it usually works on the first attempt but sometimes the GRUB entry will require minor tweaking.

Have a good weekend,
=david
Logged

Registered Linux User # 442201

Pardus 2011.2 (KDE 4.6.5, kernel 2.6.37.6)

AMD Athlon II X2 240 (Regor) 2.8 GHz, 4 GB RAM, Seagate Barracuda 320 GB HD, Nvidia GeForce 6150SE nForce 430 integrated GPU, Samsung SH-S222L DVD-RW
Pages: [1] 2 Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!