jaska wrote:

Joni Hoppen kirjoitti viestissään (lähetysaika Maanantai 16. Helmikuuta 2004 19:45):

...

I have a mother soyo SY-KT 400 DRAGON ULTRA with RAID onboard HighPoint HPT 372 and I could not install suse linux 9.0 when the Raid controler is enable on the Bios. When its enable I could not start boot even safemode the falow massage apears "kernel panic " so, what can I do to solve this problem? I need use Raid 1 to make mirror for two hds IDEs 80 gb.

I believe that http://www.highpoint-tech.com/USA/b372.htm is Your best place to start...

There is no direct support for SuSE 9.0, but maybe You can compile the source-code version... I have no experience with the source version.

I suspect "no direct support" may be untrue. Highpoint at that location has precompiled modules, but only up through SuSE 8.1. The fact that newer does not exist seems to imply some form of support from SuSE. In fact, ftp://ftp.sunet.se/pub/Linux/distributions/suse/suse/i386/9.0/boot/modules2.txt includes "hptraid", though it's indicated for hpt370 and not hpt3xx or hpt37x or hpt372. Furthermore, the installer does have RAID as configuration option in advanced partitioning. Does anyone have hpt372 RAID 1 working? I've gotten 9.0 installed on one disk and am now trying to figure out what to do to enable use of the native motherboard RAID 1. One place says a module can be used, but elsewhere says that to boot from ataraid requires support be compiled into the kernel. I started to try compiling a kernel using the instructions at http://www.tldp.org/HOWTO/ATA-RAID-HOWTO/nativeraid.html, but I don't seem to be able to pinpoint the location of the .config or config.txt file used to compile the OEM kernel so that I can use that as a starting point, and the sample config.txt link on that page is bad. -- "Surely God would not have created such a being as man to exist only a day! No, no, man was made for immortality." President Abraham Lincoln Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/

On Mon February 16 2004 5:04 pm, Ken Schneider wrote:

-----Original Message----- From: Richard To: suse , suse@suse.de Date: Mon, 16 Feb 2004 15:36:43 -0800 Subject: Re: [SLE] RAID HTP 372 on-board

<snip>

...

prime time. I have to change my position with this latest experience since the box, and SuSE's shallow support purchased by buying the box, have

You did not purchase support with the boxed set only the install programs and any other programs included on the DVD/CD's. Suse will provide limited install support. If you need more advanced support it is available for a price.

Ken Schneider

True. My beef was that the support was SO limited. I felt that I was not "installed" until the system was on my equipment and working as suggested. They felt, apparently, that once any file was copied to my hard drive, that I was "installed" and therefore they had no further responsibility or interest. In the future I will wait for FTP availability since the "limited" support that comes with the boxed set does not meet with what I expect from the phrase, "Installation Support." My misunderstanding. I thought I would get a working system. Richard

On Mon February 16 2004 9:13 pm, Hartmut Meyer wrote:

Hi,

Am Dienstag, 17. Februar 2004 02:20 schrieb Richard:

...

On Mon February 16 2004 5:04 pm, Ken Schneider wrote:

...

You did not purchase support with the boxed set only the install programs and any other programs included on the DVD/CD's. Suse will provide limited install support. If you need more advanced support it is available for a price.

True. My beef was that the support was SO limited. I felt that I was not "installed" until the system was on my equipment and working as suggested. They felt, apparently, that once any file was copied to my hard drive, that I was "installed" and therefore they had no further responsibility or interest. In the future I will wait for FTP availability since the "limited" support that comes with the boxed set does not meet with what I expect from the phrase, "Installation Support." My misunderstanding. I thought I would get a working system. Richard

The issue here is RAID. And *that* is not (and for good reasons never has been) covered by the "free" service:

http://www.suse.de/en/private/support/inst_support/

Greetings from Bremen hartmut

You are right, Hartmut, and at the risk of prolonging this peeve, something I dislike watching others do, my concern was that 9.0 will not even recognize the 372 controller as an additional IDE controller, without using the quasi-RAID services it is supposed to be capable of. I would be happy if 9.0 could simply see and allow access to disks attached to the controller in non-RAID mode, something 8.2, 8.1, 8.0,...were and are perfectly capable of doing. I am running 8.2 on the controller now, non-RAID, just to get access to more than four total IDE drives. 9.0 OTOH, kernel panics, as the original poster noted, in any case in which the additional controller is enabled in the system BIOS. FWIW, while I have the same chip, I have a different MB (his was Soyo, mine is DFI) so I do not think the problem is with his MB specifically, nor with the controller chip since 8.2 is humming along nicely, as we speak/write. While I may have gone on overlong about my experience and disdain for the limits of SuSE support, that does not change the fact that 9.0 kernel panics in exactly the same setup that 8.2 is perfectly happy with. Right now I am not sure that compiling a HPT source module would even be an acceptable solution, if I knew how to get around the different kernels involved, since the hang-up seems to be more basic than that in that it happens very early on in the boot process, at first recognition of attached drives. In fact when I previously did compile a module and asked the install process to apply it with the "force" option to hopefully obviate the discrepancy in kernel versions, it still paniced and stopped. My apologies if this has stepped on anyone's toes in feeling a need to defend SuSE support, but I think that the inability to install 9.0 when this chip, HPT 372N, is in the system, is a legitimate issue and concern, even though some may feel that I approached it in "attack mode." Richard

Hartmut Meyer wrote:

I don't know about the 372N (in particular not about the 'N'). Fact is, that we do have a HPT372 controller and have tested (succesfully) to install 9.0on it.

If you could send me the output of

hwinfo --pci

Knoppix doesn't have hwinfo. I tried running if from a floppy copied from SuSE 8.2, but that requires libhd.so.6, which isn't on the Knoppix CD. I tried to copy that from SuSE 8.2 too, but the only writable locations aren't in the path. How can I run hwinfo from a Knoppix boot?

that would help (me, not you). Of course, you would need to have the controller enabled in the BIOS, so you likely won't be able to get this output on a 9.0 system but you should be able to get it on a 8.2 (even the 8.2 rescue system).

How about lspci -v? This is from Soyo Dragon KT400 with RAID 1 enabled in HPT BIOS (W2K is installed on about 2/3 of the RAID): 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge Subsystem: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge Flags: bus master, 66Mhz, medium devsel, latency 8 Memory at e8000000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: ec000000-edffffff Prefetchable memory behind bridge: e0000000-e7ffffff Capabilities: [80] Power Management version 2 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: Soyo Computer, Inc: Unknown device a715 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at c000 [size=256] Capabilities: [c0] Power Management version 2 00:0f.0 RAID bus controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 05) Subsystem: Triones Technologies, Inc. HPT370A Flags: bus master, 66Mhz, medium devsel, latency 120, IRQ 10 I/O ports at c400 [size=8] I/O ports at c800 [size=4] I/O ports at cc00 [size=8] I/O ports at d000 [size=4] I/O ports at d400 [size=256] Expansion ROM at <unassigned> [disabled] [size=128K] Capabilities: [60] Power Management version 2 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dc00 [size=32] Capabilities: [80] Power Management version 2 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at e000 [size=32] Capabilities: [80] Power Management version 2 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at ee020000 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. VT8235 Bus Master ATA133/100/66/33 IDE Flags: bus master, medium devsel, latency 32 I/O ports at e400 [size=16] Capabilities: [c0] Power Management version 2 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e800 [size=256] Memory at ee021000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 -- "I place economy among the first and most important of republican virtues, and public debt as the greatest of the dangers to be feared." President Thomas Jefferson Team OS/2 ** Reg. Linux User #211409 ** Rotary ONLY since 1973 Felix Miata *** http://members.ij.net/mrmazda/

Joni brought his computer to me and I have already had some light into the matter. 1. The kernel panics when the IDE driver is loaded. This happens with both SuSe 9.0 installation CD's kernel, and my 2.4.21-166-default SuSE kernel. 2. With a HD attached on the native, non-RAID (from the VIA chipset) controller, and the others connected to the HighPoint, if you pass the "ide=reverse" kernel parameter, the installation CD kernel boots, and SuSE can be installed to the disk attached to the non-RAID controller. 3. I then connected another disk, in which I have SuSE and Gentoo installed, to the VIA IDE and tried to boot with it. SuSE's 2.4.21-166-default kernel panicked even if I passed the ide=reverse option. Gentoo's 2.6.2-love1 booted alright. 4. When using the Gentoo kernel (2.6.1-love1, IDE driver for HighPoint 372 enabled inside the kernel) the controller is recognized as ide2. The kernel then recognizes /dev/hde, which I do not know yet if it is only the first harddisk attached to the HighPoint, or the RAID 1 array (2 identical Seagate 80GB disks) which I defined in the HighPoint BIOS. 5. Once it was working I was able to partitionate /dev/hde and create ReiserFS on it. I then copied my small Gentoo installation (4GB) to it. 6. After doing this, I removed my own disk from the native IDE. The first disk from the array would boot, if connected to the native VIA IDE interface. Back to the RAID controller, this same disk's MBR is accessed all right, and GRUB starts. But it gets confused and does not boot, since (I think) the disk order changes in the BIOS. (please correct me if I'm wrong) I did'nt have time yet to test the second disk. I imagine that if it does boot as well, then RAID 1 was working at the time I copied Gentoo to /dev/hde (am I right?). This is as far as I have come, yet. I will be testing with LILO, and also checking if both disks are actually the same after copying Gentoo to /dev/hde. The only solution I can figure at the moment is installing SuSE into one of the array disks, with LILO as the bootloader, installing a 2.6 kernel, and then, via HighPoint's BIOS utility, cloning it to the other disk and creating the array. Then, if indeed the 2.6 kernel did write to both disks as a RAID 1 array when I copied Gentoo to /dev/hde, we *might* have SuSE 9.0, but with a different kernel, running and using RAID 1 on this controller. Seems like a lottery to me, but I'm keen to try. If anyone has some brilliant ideas could you please tell us? =) Thanks Anderson On Tue, 2004-02-17 at 11:55, Felix Miata wrote:

Hartmut Meyer wrote:

...

I don't know about the 372N (in particular not about the 'N'). Fact is, that we do have a HPT372 controller and have tested (succesfully) to install 9.0on it.

...

If you could send me the output of

...

hwinfo --pci

Knoppix doesn't have hwinfo. I tried running if from a floppy copied from SuSE 8.2, but that requires libhd.so.6, which isn't on the Knoppix CD. I tried to copy that from SuSE 8.2 too, but the only writable locations aren't in the path. How can I run hwinfo from a Knoppix boot?

...

that would help (me, not you). Of course, you would need to have the controller enabled in the BIOS, so you likely won't be able to get this output on a 9.0 system but you should be able to get it on a 8.2 (even the 8.2 rescue system).

How about lspci -v? This is from Soyo Dragon KT400 with RAID 1 enabled in HPT BIOS (W2K is installed on about 2/3 of the RAID):

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge Subsystem: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge Flags: bus master, 66Mhz, medium devsel, latency 8 Memory at e8000000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: ec000000-edffffff Prefetchable memory behind bridge: e0000000-e7ffffff Capabilities: [80] Power Management version 2

00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: Soyo Computer, Inc: Unknown device a715 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at c000 [size=256] Capabilities: [c0] Power Management version 2

00:0f.0 RAID bus controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 05) Subsystem: Triones Technologies, Inc. HPT370A Flags: bus master, 66Mhz, medium devsel, latency 120, IRQ 10 I/O ports at c400 [size=8] I/O ports at c800 [size=4] I/O ports at cc00 [size=8] I/O ports at d000 [size=4] I/O ports at d400 [size=256] Expansion ROM at <unassigned> [disabled] [size=128K] Capabilities: [60] Power Management version 2

00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dc00 [size=32] Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. USB Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at e000 [size=32] Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at ee020000 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. VT8235 Bus Master ATA133/100/66/33 IDE Flags: bus master, medium devsel, latency 32 I/O ports at e400 [size=16] Capabilities: [c0] Power Management version 2

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e800 [size=256] Memory at ee021000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 -- "I place economy among the first and most important of republican virtues, and public debt as the greatest of the dangers to be feared." President Thomas Jefferson

Team OS/2 ** Reg. Linux User #211409 ** Rotary ONLY since 1973

Felix Miata *** http://members.ij.net/mrmazda/