Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.hardware > #2140 > unrolled thread

RocketRaid rr222x Family SATA Raid Cards support on DEBIAN

Started byGeber El <gabrielevigna@gmail.com>
First post2013-12-05 20:37 -0800
Last post2013-12-07 15:19 +0000
Articles 3 — 3 participants

Back to article view | Back to comp.os.linux.hardware


Contents

  RocketRaid rr222x Family SATA Raid Cards support on DEBIAN Geber El <gabrielevigna@gmail.com> - 2013-12-05 20:37 -0800
    Re: RocketRaid rr222x Family SATA Raid Cards support on DEBIAN philo  <philo@privacy.net> - 2013-12-06 14:59 -0600
    Re: RocketRaid rr222x Family SATA Raid Cards support on DEBIAN Kirk_Von_Rockstein <Kirk_Von_Rockstein@nowhere.invalid> - 2013-12-07 15:19 +0000

#2140 — RocketRaid rr222x Family SATA Raid Cards support on DEBIAN

FromGeber El <gabrielevigna@gmail.com>
Date2013-12-05 20:37 -0800
SubjectRocketRaid rr222x Family SATA Raid Cards support on DEBIAN
Message-ID<9f6f5c50-6afd-4f15-a526-495293f9e6ad@googlegroups.com>
I can't make my rr2220 PCI-E functioning with lates Debian kernel 3.2 (uname -r: 3.2.0-4-amd64) 'cause there is no support from the productor over the new kernel (max kernel version : 2.6)....
But WTF are they doing ?
I have found a kind of workaround page on Internet BUT, after some try, i've understand the described procedure is out of my knowledge...

Link --> http://ubuntuforums.org/showthread.php?t=1856162

Can someone give me some lights over this GREAT (for me, at least...) problem?

Drivers link --> http://www.highpoint-tech.com/USA_new/rr2200_download.htm

Sorry for my little bad English and Tank You all in advance,

Gabriele.

[toc] | [next] | [standalone]


#2141

Fromphilo  <philo@privacy.net>
Date2013-12-06 14:59 -0600
Message-ID<l7tdsb$sao$1@dont-email.me>
In reply to#2140
On 12/05/2013 10:37 PM, Geber El wrote:
> I can't make my rr2220 PCI-E functioning with lates Debian kernel 3.2 (uname -r: 3.2.0-4-amd64) 'cause there is no support from the productor over the new kernel (max kernel version : 2.6)....
> But WTF are they doing ?
> I have found a kind of workaround page on Internet BUT, after some try, i've understand the described procedure is out of my knowledge...
>
> Link --> http://ubuntuforums.org/showthread.php?t=1856162
>
> Can someone give me some lights over this GREAT (for me, at least...) problem?
>
> Drivers link --> http://www.highpoint-tech.com/USA_new/rr2200_download.htm
>
> Sorry for my little bad English and Tank You all in advance,
>
> Gabriele.
>



The instructions look pretty straightforward but certainly a lot of 
work. I'd use your older kernel and check with the manufacturer later 
and see if they come up with a new driver.

[toc] | [prev] | [next] | [standalone]


#2142

FromKirk_Von_Rockstein <Kirk_Von_Rockstein@nowhere.invalid>
Date2013-12-07 15:19 +0000
Message-ID<20131207095647.209@0.0.0>
In reply to#2140
On 2013-12-06, Geber El <gabrielevigna@gmail.com> wrote:
> I can't make my rr2220 PCI-E functioning with lates 
> Debian kernel 3.2 (uname -r: 3.2.0-4-amd64) 'cause there 
> is no support from the productor over the new kernel 
> (max kernel version : 2.6)....

> But WTF are they doing ?
> I have found a kind of workaround page on Internet BUT, 
> after some try, i've understand the described 
> procedure is out of my knowledge...
>
> Link --> http://ubuntuforums.org/showthread.php?t=1856162

The instructions in the above link are 
for the 2.4, 2.6, 3.0 kernel versions.
I think you would have to replace 3.0 for 3.2 in
each case or add it if you intend to use the 3.2 kernel version.
See below for an example starting @ </start_copy&edit>

> Can someone give me some lights over this GREAT (for me, at least...) problem?
>
> Drivers link --> http://www.highpoint-tech.com/USA_new/rr2200_download.htm
>
> Sorry for my little bad English and Tank You all in advance,
>
> Gabriele.

</start_copy&edit>
        Dowload the open source driver form the HighPoint website (cur ver. 1.3) http://www.highpoint-tech.cn/BIOS_Dr...03-0910.tar.gz
        Extract the driver to your home directory
        Open the Makefile.def located in the /inc/linux folder
        Replace the following:

        This
        Code:

        KERNEL_VER := 2.$(shell expr `grep LINUX_VERSION_CODE $(KERNELDIR)/include/linux/version.h | cut -d\  -f3` / 256 % 256)

        With
        Code:

        KERNEL_VER := $(shell uname -r | cut -f1-2 -d.)

        This
        Code:

        ifneq ($(KERNEL_VER), 2.6)

        ifneq ($(KERNEL_VER), 2.4)

        $(error Only kernel 2.4/2.6 is supported but you use $(KERNEL_VER))

        endif

        endif

        With

        Code:

        ifneq ($(KERNEL_VER), 3.2)
        ifneq ($(KERNEL_VER), 3.0)
	ifneq ($(KERNEL_VER), 2.6)
        ifneq ($(KERNEL_VER), 2.4)
        $(error Only kernel 2.4/2.6/3.0/3.2 is supported but you use $(KERNEL_VER))
        endif
        endif
        endif
	endif

        This

        Code:

        ifeq ($(KERNEL_VER), 2.6)

        With

        Code:

        ifeq ($(KERNEL_VER), $(filter $(KERNEL_VER),3.2 3.0 2.6))

        Save the file.
        Open os_linux.h and remove the linux/config.h include statement
        Open os_linux.c file and change the follwing

        From
        Code:

        blkdev_get(bdev, FMODE_READ)

        To
        Code:

        blkdev_get(bdev, FMODE_READ, NULL)

        Save.
        Open osm_linux.c and change the following:

        From

        Code:

        static int hpt_queuecommand (Scsi_Cmnd * SCpnt, void (*done) (Scsi_Cmnd *))

        to

        Code:

        static int hpt_queuecommand_lck (Scsi_Cmnd * SCpnt, void (*done) (Scsi_Cmnd *))

        Before the hpt_reset method, insert the lines below:
        Code:

        #ifdef DEF_SCSI_QCMD
        DEF_SCSI_QCMD(hpt_queuecommand)
        #else
        #define hpt_queuecommand hpt_queuecommand_lck
        #endif

        Save.
        Open install.sh and change section below from:

        Code:

        case ${KERNEL_VER} in
        	2.4 )
        	OBJ=o
        	MODVER=`modinfo -f%{kernel_version} ${PWD}/${TARGETNAME}.${OBJ}`
        	;;
        	2.6 )
        	OBJ=ko
        	MODVER=`modinfo -F vermagic ${PWD}/${TARGETNAME}.${OBJ} | cut -d' ' -f1`
        	;;
        esac

        to

        Code:

        case ${KERNEL_VER} in
        	2.4 )
        	OBJ=o
        	MODVER=`modinfo -f%{kernel_version} ${PWD}/${TARGETNAME}.${OBJ}`
        	;;
        	2.6 )
        	OBJ=ko
        	MODVER=`modinfo -F vermagic ${PWD}/${TARGETNAME}.${OBJ} | cut -d' ' -f1`
        	;;
        	3.0 )
        	OBJ=ko
        	MODVER=`modinfo -F vermagic ${PWD}/${TARGETNAME}.${OBJ} | cut -d' ' -f1`
        	;;
		3.2 )
        	OBJ=ko
        	MODVER=`modinfo -F vermagic ${PWD}/${TARGETNAME}.${OBJ} | cut -d' ' -f1`
        	;;
        esac



    The driver should compile and install properly after that.


    I know that some of these things could be automated with a patch program, 
    but i have no clue how to do it. if anyone is willing to tackle it, 
    or help me write it, please send me an e-mail.


    Hope this helps other people. 

    Last edited by krutoileshii; October 9th, 2011 at 10:05 PM. 
    
</end_copy&edit>

[toc] | [prev] | [standalone]


Back to top | Article view | comp.os.linux.hardware


csiph-web