|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
debian-user-digest Digest V2007 #2034
Date: Thu Jul 26 2007 - 22:45:11 EDT
Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2034
Today's Topics:
Re: Weird partition arrangements and [ "Nguyen, Cuong K."Date: Thu, 26 Jul 2007 21:54:57 -0400
From: "Nguyen, Cuong K." <cuongkieunguyen@gmail.com> To: debian-user@lists.debian.org
Subject: Re: Weird partition arrangements and broken GRUB Message-ID: <b36fe63b0707261854n7de8fcf4n9c456350f141c71d@mail.gmail.com> Content-Type: multipart/alternative;boundary="----=_Part_137286_9411913.1185501297515"
------=_Part_137286_9411913.1185501297515
Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inlineOn 7/26/07, Hamza Saglam <hamzasaglam@googlemail.com> wrote:
>
> Hi,
>
> After reading dozens of GRUB tutorials for a good few hours and not
> getting anywhere, I've decided to post on this mailing list regarding
> my problem. If it has been covered before please pardon me, I really
> can't see it :(
>
> Now before I start, I'd like to point out that we are both debian
> users both due to the nature of our work, we have to have a windows
> installation on our machines. Sad but true :(
>
> A friend of mine brought in his laptop after he said he couldn't get
> 'windows booting', and when I had a look at the partition table using
> gparted, I was presented with the following monstrosity:
>
> screenshot:
> http://***image.***bayimg.***com/oaeikaabk.jpg
> (please get rid of the 9 stars, the mailing list wouldn't accept my
> message without these)
>
>
> (for the text based readers), it looks a bit like:
> /dev/sda1 fat32 (boot)
> /dev/sda2 extended (lba)
> /dev/sda5 ntfs (boot)
> /dev/sda6 linux-swap
> /dev/sda3 ext3
>
> The first fat32 partition is the recovery files that came with the
> laptop, the rest is a bit of mess really :)
>
> Relevant bits from /boot/grub/menu.lst:
>
> title Debian GNU/Linux, kernel 2.6.18-4-686
> root (hd0,2)
> kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro
> initrd /boot/initrd.img- 2.6.18-4-686
> savedefault
>
> title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode)
> root (hd0,2)
> kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro single
> initrd /boot/initrd.img- 2.6.18-4-686
> savedefault
>
> title Microsoft Windows XP
> root (hd0,3)
> savedefault
> makeactive
> chainloader +1
>
> title Acer eRecovery Management
> root (hd0,0)
> savedefault
> makeactive
> chainloader +1
>
>
> I've tried all the possible combinations for the root directive of the
> Windows section, but it doesn't want to load windows.
>
> Is there any way I can address the ntfs partition within that extended
> partition, or do I need to modify the structure. (I'd very much prefer
> not changing the structure, even though it is quite messy)
>
>
> I am stuck so any help would be much appreciated.
>
> Many thanks.
> Hamza
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
If you look at my partition table, you may call it "messier" or "weirder":Disk /dev/sda: 100.0 GB, 100030242816 bytes 255 heads, 63 sectors/track, 12161 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sda1 1 784 6297448+ 12 Compaq diagnostics /dev/sda2 * 785 3356 20659590 7 HPFS/NTFS /dev/sda3 4507 12161 61488787+ f W95 Ext'd (LBA) /dev/sda4 3357 4506 9237375 7 HPFS/NTFS /dev/sda5 4507 7064 20547103+ 83 Linux /dev/sda6 7065 7203 1116486 82 Linux swap / Solaris /dev/sda7 11974 12161 1510078+ 82 Linux swap / Solaris /dev/sda8 7204 9635 19535008+ 83 Linux /dev/sda9 9636 11973 18779953+ 83 LinuxPartition table entries are not in disk order
And here is the menu.lst
## ## End Default Options ##
title Ubuntu, kernel 2.6.20-16-generic root (hd0,7) kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro quiet splash initrd /boot/initrd.img-2.6.20-16-genericquiet
savedefaulttitle Ubuntu, kernel 2.6.20-16-generic (recovery mode) root (hd0,7) kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro single initrd /boot/initrd.img-2.6.20-16-generic title Ubuntu, kernel 2.6.20-15-generic root (hd0,7) kernel /boot/vmlinuz-2.6.20-15-genericroot=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro quiet splash break=top initrd /boot/initrd.img-2.6.20-15-genericquiet
savedefaulttitle Ubuntu, kernel 2.6.20-15-generic (recovery mode) root (hd0,7) kernel /boot/vmlinuz-2.6.20-15-genericroot=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro single initrd /boot/initrd.img-2.6.20-15-generic title Ubuntu, memtest86+ root (hd0,7) 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/hda1
title Windows NT/2000/XP Recovery root (hd0,0)
savedefault
makeactive
chainloader +1# This entry automatically added by the Debian installer for a non-linux OS # on /dev/hda2
title Microsoft Windows XP Professional root (hd0,1)
savedefault
makeactive
chainloader +1# This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda5.
title Mandriva 2007 (on /dev/hda5) root (hd0,4) kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6 splash=silent initrd /boot/initrd.img
savedefault
boot# This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda5.
title Mandriva 2007 (recovery mode) (on /dev/hda5) root (hd0,4) kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6 initrd /boot/initrd.img
savedefault
boot# This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda5.
title failsafe (on /dev/hda5) root (hd0,4) kernel /boot/vmlinuz root=/dev/hda5 failsafe resume=/dev/hda6 initrd /boot/initrd.img
savedefault
bootVery similar to your case: I have one Recovery partition (sda1), one Windows XP Pro, one Ubuntu box, and one Mandriva box. Everything works just fine: by selecting on the boot menu, I can boot into any OS I want.
As about your case, here is my suggestion for menu.lst (not sure it will work, but worth giving a try)
title Debian GNU/Linux, kernel 2.6.18-4-686 root (hd0,2) kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro initrd /boot/initrd.img- 2.6.18-4-686savedefaulttitle Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode) root (hd0,2) kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/sda3 ro single initrd /boot/initrd.img- 2.6.18-4-686savedefaulttitle Microsoft Windows XP root (hd0,4)
savedefault
makeactive
chainloader +1title Acer eRecovery Management root (hd0,0)
savedefault
makeactive
chainloader +1The only change here is for XP partition: root (hd0,4) not (hd0,3) because your ntfs partition is sda5. Also, you may need just one partition to be bootable like me (you have two bootable).
Hope that this can help,
KC.
------=_Part_137286_9411913.1185501297515
Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline<br><br><div><span class="gmail_quote">On 7/26/07, <b class="gmail_sendername">Hamza Saglam</b> <<a href="mailto:hamzasaglam@googlemail.com">hamzasaglam@googlemail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi,<br><br>After reading dozens of GRUB tutorials for a good few hours and not<br>getting anywhere, I've decided to post on this mailing list regarding<br>my problem. If it has been covered before please pardon me, I really
root=/dev/sda3 ro<br> initrd /boot/initrd.img- 2.6.18-4-686<br> savedefault<br><br> title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode)<br> root (hd0,2)<br> kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro single<br> initrd /boot/initrd.img- 2.6.18-4-686<br> savedefault<br><br> title Microsoft Windows XP<br> root (hd0,3)<br> savedefault<br> makeactive<br> chainloader +1<br><br> title Acer eRecovery Management<br> root (hd0,0)<br> savedefault<br> makeactive<br> chainloader +1<br><br><br>I've tried all the possible combinations for the root directive of the <br>Windows section, but it doesn't want to load windows.<br><br>Is there any way I can address the ntfs partition within that extended<br>partition, or do I need to modify the structure. (I'd very much prefer<br> not changing the structure, even though it is quite messy)<br><br><br> I am stuck so any help would be much appreciated.<br><br>Many thanks.<br>Hamza<br><br><br>--<br>To UNSUBSCRIBE, email to <a href="mailto:debian-user-REQUEST@lists.debian.org"> debian-user-REQUEST@lists.debian.org</a><br>with a subject of "unsubscribe". Trouble? Contact <a href="mailto:listmaster@lists.debian.org">listmaster@lists.debian.org</a><br><br></blockquote></div><br>If you look at my partition table, you may call it "messier" or "weirder":
can't see it :(
Now before I start, I'd like to point out that we are both debian
users both due to the nature of our work, we have to have a windows
installation on our machines. Sad but true :(
A friend of mine brought in his laptop after he said he couldn't get
'windows booting', and when I had a look at the partition table using
gparted, I was presented with the following monstrosity:
screenshot:
http://***image.***bayimg.***com/oaeikaabk.jpg
(please get rid of the 9 stars, the mailing list wouldn't accept my
message without these)
(for the text based readers), it looks a bit like:
/dev/sda1 fat32 (boot)
/dev/sda2 extended (lba)
/dev/sda5 ntfs (boot)
/dev/sda6 linux-swap
/dev/sda3 ext3
The first fat32 partition is the recovery files that came with the
laptop, the rest is a bit of mess really :)
Relevant bits from /boot/grub/menu.lst:
title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,2)
kernel /boot/vmlinuz-2.6.18-4-686<br>quiet<br>savedefault<br><br>title Ubuntu, kernel 2.6.20-16-generic (recovery mode)<br>root (hd0,7)<br>kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro single<br>initrd /boot/initrd.img- 2.6.20-16-generic<br><br>title Ubuntu, kernel 2.6.20-15-generic<br>root (hd0,7)<br>kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro quiet splash break=top<br>initrd /boot/initrd.img- 2.6.20-15-generic<br>quiet<br>savedefault<br><br>title Ubuntu, kernel 2.6.20-15-generic (recovery mode)<br>root (hd0,7)<br>kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro single
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 784 6297448+ 12 Compaq diagnostics
/dev/sda2 * 785 3356 20659590 7 HPFS/NTFS
/dev/sda3 4507 12161 61488787+ f W95 Ext'd (LBA)
/dev/sda4 3357 4506 9237375 7 HPFS/NTFS
/dev/sda5 4507 7064 20547103+ 83 Linux
/dev/sda6 7065 7203 1116486 82 Linux swap / Solaris
/dev/sda7 11974 12161 1510078+ 82 Linux swap / Solaris
/dev/sda8 7204 9635 19535008+ 83 Linux
/dev/sda9 9636 11973 18779953+ 83 Linux
Partition table entries are not in disk order
And here is the menu.lst
## ## End Default Options ##
title Ubuntu, kernel 2.6.20-16-generic
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-genericroot (hd0,4)<br>kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6 splash=silent <br>initrd /boot/initrd.img<br>savedefault<br>boot<br><br><br># This entry automatically added by the Debian installer for an existing
initrd /boot/initrd.img-2.6.20-15-generic
title Ubuntu, memtest86+
root (hd0,7)
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/hda1
title Windows NT/2000/XP Recovery
root (hd0,0)
savedefault
makeactive
chainloader +1
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda2
title Microsoft Windows XP Professional
root (hd0,1)
savedefault
makeactive
chainloader +1
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hda5.
title Mandriva 2007 (on /dev/hda5)
2.6.18-4-686 root=/dev/sda3 ro single<br> initrd /boot/initrd.img- 2.6.18-4-686<br> savedefault<br><br> title Microsoft Windows XP<br> root (hd0,4)<br> savedefault<br> makeactive<br> chainloader +1<br><br> title Acer eRecovery Management<br> root (hd0,0)<br> savedefault<br> makeactive<br> chainloader +1<br><br>The only change here is for XP partition: root (hd0,4) not (hd0,3) because your ntfs partition is sda5. Also, you may need just one partition to be bootable like me (you have two bootable). <br><br>Hope that this can help,<br><br>KC.<br>
# linux installation on /dev/hda5.
title Mandriva 2007 (recovery mode) (on /dev/hda5)
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6
initrd /boot/initrd.img
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hda5.
title failsafe (on /dev/hda5)
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 failsafe resume=/dev/hda6
initrd /boot/initrd.img
savedefault
boot
Very similar to your case: I have one Recovery partition (sda1), one Windows XP Pro, one Ubuntu box, and one Mandriva box. Everything works just fine: by selecting on the boot menu, I can boot into any OS I want.
As about your case, here is my suggestion for menu.lst (not sure it will work, but worth giving a try)
title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,2)
kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro
initrd /boot/initrd.img- 2.6.18-4-686
savedefault
title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode)
root (hd0,2)
kernel /boot/vmlinuz-------=_Part_137286_9411913.1185501297515--
Date: Thu, 26 Jul 2007 21:00:44 -0500 (CDT) From: Jude DaShiell <jdashiel@shellworld.net> To: Erico <ericomtx@gmail.com>
Cc: debian-user@lists.debian.org
Subject: Re: laptop keyboard settings in debian etch Message-ID: <Pine.BSF.4.64.0707262057470.71161@freire2.furyyjbeyq.arg> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowedHave you run tasksel and selected the laptop option yet? If not doing that may make life a little better. I just got a Dell latitude c810 last night with no operating system on it and I'm going to put a form of Debian Linux on it. So this is something close to my first exposure to laptops.
Date: Thu, 26 Jul 2007 22:15:54 -0400
From: Hal Vaughan <hal@thresholddigital.com> To: debian-user@lists.debian.org
Subject: Re: Where is Lame in Sarge?
Message-Id: <200707262215.54964.hal@thresholddigital.com> Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineOn Thursday 26 July 2007, Bob Proulx wrote:
> Hal Vaughan wrote:
> > I know there's an issue with MySQL and permissions with an easy
> > work around, but other than that, I want to have time to check out
> > known issues before I upgrade a server.
>
> Wise plan. In fact setting up a Sarge machine as a victim for
> upgrade testing to Etch is a good idea.That's a possibility. I'd duplicate the list of packages on the server and test it that way. Of course, I couldn't do a *real* test unless I made sure all the programs were in use, which would mean a drop in replacement, which ain't going to happen unless I can replace a mostly full 300GB RAID (and most of that is my ripped CD collection -- just got a Squeezebox and installed Slimserver so I could listen to them outside the office).
> For servers the upgrade for me has gone quite easily. For desktops
> the biggest problem has been the name changes for many web browser
> plugins and also the movement of GNU FDL licensed documentation into
> non-free. This means I have had to add non-free to my sources where
> this was not previously needed and also needed to specifically
> install many of the now non-free documentation packages that were
> split out.In some ways server management can be much easier than a desktop. I'm rarely adding anything and once it's stabilized, there's not much that changes. I'm not worried about docs or anything like that on the server because I can use them on my workstation, which is Ubuntu because I like newer versions of eye candy.
> > On the other hand, what's the expected release date for Lenny going
> > Stable? With Etch going Stable in April, I figure I still have
> > another 8 - 9 months before Lenny is stable. :-)
>
> You are an optimist thinking 8-9 months! I think you have plenty of
> time well past that. Perhaps I should have said before security
> upgrades for Sarge are discontinued. That will almost certainly
> happen before Lenny releases. :-)I said 8-9 months because I was being diplomatic and didn't want to offend any of the few DDs left on the list! I figure I'll get the main server, which does file, print, dns, and audio serving (and a few other things like that) first, since that's less complex and all the services are easy to replace. The other is my work system, which is also a development system for the business (I can't afford to do it on 2 separate systems) and that would be a mess if things didn't upgrade smoothly.
Hal
Date: Thu, 26 Jul 2007 22:17:15 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca> To: debian-user@lists.debian.org
Subject: Re: Stability issuesMessage-ID: <20070727021715.GA15707@titan> Content-Type: text/plain; charset=us-ascii Content-Disposition: inlineOn Thu, Jul 26, 2007 at 09:50:02PM -0400, Mike Robinson wrote:
> Douglas Allan Tutty wrote:
> >Just curious: why not amd64? I'm running it on my Athlon64 3800+. The
> >_only_ thing I need 32-bit for is adobe flashplayer, for which I run a
> >chroot for the browser. That problem is fixed in Lenny/Sid but I didn't
> >want to go that route. After having done it, setting up the chroot was
> >rather simple and schroot makes running it a breeze.
>
> Can the binary nVidia video driver still be used in the 64-bit
> distribution? If
> so, I may try the amd64 route. The only thing I'd have to investigate is
> if there
> are any issues compiling MythTV for 64-bit.I'm using the nVidia pre-packaged debian stuff (its pre-built for Etch, as opposed to needing m-a for Sid). I have the kernel meta-package and the nvidia-kernel meta-packages installed so when one is updated, so is the other. I get a much clearer picture and less CPU usage when watching DVDs full-screen, deinterlaced blend with the nvidia driver.
I haven't tried MythTV since I only get three channels of poor quality. I use VLC for watching DVDs and listening to audio streams (e.g. CBC radio archives). Ensure that you have debian-multimedia in your sources.list. Note that I see lots of mythtv packages in aptitude.
Doug.
End of debian-user-digest Digest V2007 Issue #2034
Received on Thu Jul 26 22:42:50 2007
This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:05:31 EDT
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |