--- Jörg Spilker wrote:

Hello,

i recently bought a Highpoint RocketRaid 133 PATA Adapter. The adapter is equipped with 4 single disks (no RAID configuration). Unfortunately the hpt366 driver crashed after scanning the devices.

Are there any repositories containing newer version of the mentioned packages (in factory ?)

Or is there a better way to update the hpt driver?

Greetings, Jörg

I just went through the same type crap with an onboard it8212 raid controller. I filed a bug report, and got a run-around that it was a hardware problem; first a hard drive, then the power supply. I gave up with that, as this hardware works with every SUSE version up 'til now, as well as with Mandriva, Slackware, and PCLinuxOS. As an experiment, I created a grub menu.lst stanza to boot openSUSE 10.2 using the PCLinuxOS kernel and initrd, and copied the PCLinuxOS modules directory to the openSUSE /lib/modules directory. It booted up without issue, and the it8212 drives were recognized, mounted, and I could read and write files to them reliably. Gee, this broken hardware suddenly works just like it's supposed to. I then compared the .config files from the kernel sources of each, and found the SUSE kernel had a slew of entries for "pata_<whatever>" set to be created as modules. All were labled as either "experimental" or "very experimental", which is synonymous with "These modules are fucked, man!" I commented them all, and marked them as "is not set". then recompiled and installed the SUSE kernel and modules. It now boots without issue, and the drives on the controller are accessible exactly as they should be. I would suggest you do the same, with the present kernel sources, (mine are for 2.6.18.8-0.1) making sure that you set; CONFIG_BLK_DEV_HPT366=y or CONFIG_BLK_DEV_HPT366=m whichever you prefer. Without the "pata_<whatever>" modules, you should end up with a properly working kernel, and raid controller. Anyone that tells you that the "pata_*" modules are ready for prime time is in serious denial, and doesn't run one of these controllers. Remember the line "if it ain't broke, don't fix it"? This is a prime example, as it's the unnecessary fix that breaks what wasn't previously broken. Here's the list of what I took out; # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5535 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_ISAPNP is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_LEGACY is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PCMCIA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_QDI is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_WINBOND_VLB is not set Hope that helps you. It worked wonders for me. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org