James Knott wrote:

I also use volume labels, rather than device ID.

Volume labels... meaning strings like 'Home', 'Root', 'Backups'? Device ID meaning sda or hda or "1st drive'.. or do you mean the UUID (something 'descriptive'[sic] like 0987e60c-9bac-455f-8e68-1b96472d987a or 513a8057-3764-670e-2013-03081620395c? The legacy BIOS doesn't know about labels or UUID only drive #'s (0,1,2...) modern boot loaders know about UUID's *w/o* the OS present. The new-model BIOS (called the "Extended Firmware Interface", or "EFI Bios") knows about UUID's. The only thing that reliably knows about labels is an already booted OS (so label access can be simulated by running a an 'init-rd' that sets up an initial environment to support os-dependent 'boot features' The error message you got "multiple active partitions" indicates it is a legacy bios and only knows where to read the boot sector by looking at what partition(singular) is *active*. That active boot partition then can have a loader that loads from a menu or has a more flexible boot strategy than just using the "1" active partition.

I bought this motherboard about 8 years ago and have always used it with IDE drives. I guess I'll be putting in the new motherboard sooner than planned.

Question -- does the motherboard SUPPORT sata drives, or are you using an ADD-IN card? 2nd question -- does the mother board allow you to choose whether or not to run boot "offboard" cards first.' (i.e. a yes/no question, usually). 3rd Q -- if it is an addin card, does it have the ability or does it provide a prompt when booting, to go into its configuration section? Ex. my LSI cards (put up a message during boot to press some key (I think it is "control-E") to edit the configuration. In the LSI-bios config, it there is an option to make it bootable or not, basically, by it enabling a handler for the BIOS disk call that allows it to reserve a BIOS-drive id (0x80 = 1st drive, 0x81 = 2nd...). I.e. scanning order of cards is usually controlled by the BIOS. Whether or not the card will present bootable devices is usually controlled by the card (i.e. a USB card, by default, usually doesn't present boot-devices at boot-time to the bios; however, many USB cards have the capability to present attached drives as 'bootable devices'). Even there, the builtin bios has to know whether or not to call the USB-boot code before or after calling it's built-in disk-devices scanner. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [03-23-14 19:58]:

Linda Walsh wrote:

...

James Knott wrote:

...

I also use volume labels, rather than device ID.

---

Volume labels... meaning strings like 'Home', 'Root', 'Backups'?

Device ID meaning sda or hda or "1st drive'.. or do you mean the UUID (something 'descriptive'[sic] like 0987e60c-9bac-455f-8e68-1b96472d987a or 513a8057-3764-670e-2013-03081620395c?

I have already reinstalled 13.1 and am now trying to get dovecot going again.

Pardon me, but you are being quite rude. Questions posed by you are/have been answered and you have driven on w/o the courtesy of an answer or explanation of what might have been wrong and what provided the solution. No one else will benefit from this conversation if you provide no explanation. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* James Knott [03-23-14 19:58]:

...

Linda Walsh wrote:

...

James Knott wrote:

...

I also use volume labels, rather than device ID.

---

Volume labels... meaning strings like 'Home', 'Root', 'Backups'?

Device ID meaning sda or hda or "1st drive'.. or do you mean the UUID (something 'descriptive'[sic] like 0987e60c-9bac-455f-8e68-1b96472d987a or 513a8057-3764-670e-2013-03081620395c? I have already reinstalled 13.1 and am now trying to get dovecot going again.

Pardon me, but you are being quite rude.

s'ok Patrick, I didn't take it as rude... just that he already went with a different "solution"... so no prob on my end.. and thanks... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

Astute question, but SATA probably is on his motherboard, unless it was rather old when "new". SATA started showing up on motherboards about 11 years ago. I even have one supporting SATA onboard that runs an ancient Sempron Socket A/462. http://www.biostar-usa.com

The mom board has built in SATA. I bought it about 8 years ago. It has a single core AMD 64 bit CPU with hyperthreading. On Saturday, a friend gave me an ASUS P8H67-M LX motherboard and I bought a 4 core Intel CPU & 8 GB of memory for it. I also picked up an IDE adapter for the new board, so I can continue to use my current DVD drives. Apparently SATA DVD drives in beige are somewhat scarce. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

jdd wrote:

Le 24/03/2014 13:05, James Knott a écrit :

...

a single core AMD 64 bit CPU with hyperthreading. On Saturday, a friend

for what it's worth, AFAIK AMD cpu never have hyperthreading (HT is due to a pentium bug)

jdd

It's an AMD Athlon 64 bit 4000+. It had hypersomething in it that was supposed to improve performance. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

On 03/24/2014 08:05 AM, James Knott wrote:

...

...

n Saturday, a friend gave me an ASUS P8H67-M LX motherboard and I bought a 4 core Intel CPU & 8 GB of memory for it. Nice! As I've pointed out before, more cores are good things to have with Linux! So is more memory :-)

Not so good. That momboard wouldn't work, so I wound up buying a new one anyway. Because I bought the CPU for his board, I wound up with a 1155 socket, rather than the newer 1150, which I would have gone with if I'd just gone out and bought a new MB in the first place. It would have also saved me a lot of aggravation. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org