On Tuesday 13 May 2008 14:45:39 Per Jessen wrote:
John wrote:
I'm curious about this subject. I tried to install 10.3 64bit onto intel ich7 in several way. What ever I did yast partitioned them to device mapper.... and the install failed out when it came to install the boot manager. Grub errors. All the files were correctly installed on the discs and the problem seemed to be entirely down to what the installer passed on to grub.
That sounds like a new bug report. Unless GRUB just doesn't support booting off such a RAID-setup.
/Per Jessen, Zürich
Yes it does but I'm still clearing my mind. This started in another thread. Comments were made about must be a hardware raid as they are automatic/transparent etc. Also that the kernel since 2.6 ( I think) doesn't support them. One thing that I'm sure has changed is that 2.4/5 used a different on disc format. I could only read my old drives with V4 knoppix. They mounted on V5 but showed garbage. I had to use that for data recovery on the previous motherboard which broke. Taking each in turn anything that boots and must subsequently load drivers -. eg linux - must use bios calls to load the drivers. I find it very hard to believe that these have been changed. They must function what ever drive arrangement is connected. The kernel clearly does support ich7 otherwise it wouldn't have been able to write the files or read them for that matter. There's an ext3 driver available for windoze now so it's easy to check if one is dual booting. In that case they are being read via the intel ich7 bios. Grub comes up with a numerical error which strongly suggests that it's been told to do something stupid. It to must make use of bios calls. The install partitioner maps the drives twice. Once to devicemapper and then again to individual discs. Confusing or what? Partitions are only mapped to device mapper though which I suppose helps. My motherboard came with a kernel patch to enable it to use the intel bios. The bios is loaded into memory. Same as a hard raid. No way to apply the patch unless it boots and the kernel can clearly cope with out it. All sounds like stinking fish to me. This is an installer problem. John -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org