LINUX DRIVER HELP NEEDED! Emergency! Casino cash and massive rep awards for help!

[AustinChief]

Ok, I have loaded the driver for an ATTO fibre channell card on CentOs and now need to get it to work with Debian... (someone supposedly loaded it successfully on Ubuntu so it should work on Debian)..

Following the exact same procedure as before.. I get an error during make install.

Error is as follows...

/root/lnx_drv_celerity_250/atto_cfg.c: In function âattocfg_read_versionâ:
/root/lnx_drv_celerity_250/atto_cfg.c:209: error: âstruct device_driverâ has no member named âkobjâ
/root/lnx_drv_celerity_250/atto_cfg.c: At top level:
/root/lnx_drv_celerity_250/atto_cfg.c:315: warning: initialization from incompatible pointer type


more info to follow...

[AustinChief]

snippets of code referencing that function...


static ssize_t attocfg_read_version (struct device_driver *driver,
struct kobject *kobj,
char *buffer)


{
PATTOCFG_HBA_DRVR this_drvr;
/* Search for the HBA driver with the matching kobj */
for (this_drvr = hba_drvr;
this_drvr->type != ATTO_DRVR_NONE;
this_drvr++)
{
if (this_drvr->kobj == &driver->kobj)
{
if (this_drvr->read_version)
return (*this_drvr->read_version) (driver, buffer);
else
return 0;
}
}
return 0;
}


static DRIVER_ATTR (file_version,
S_IRUSR | S_IRGRP | S_IROTH,
attocfg_read_version,
NULL);


Is there something about the way Debian handles kobjects that I am missing? (btw this is code from the manufacturer, not me)

[FAX]

Is the pointer referenced above a "pointer" or an array?

FAX

[AustinChief]

Is the pointer referenced above a "pointer" or an array?

FAX

The second error? (actually just a warning).. I think that is related to the first error... if I can get the first error to stop, then I will look at the second one if it still exists.


This is I think the key to it all...

/root/lnx_drv_celerity_250/atto_cfg.c: In function attocfg_read_version:
/root/lnx_drv_celerity_250/atto_cfg.c:209: error: struct device_driver has no member named kobj

[FAX]

I'm going to be little help, I'm afraid, Mr. AustinChief. My lead programmer is gone for the day and not answering his phone. I'm sorry.

All I could find is some discussion regarding fusion/mpt drivers and that when similar errors are encountered when installing certain Atto SCSI controllers, the "fusion" drivers are expected to work.

My apologies. Had this question come up a couple of hours ago, we might have been able to assist.

FAX

[AustinChief]

I'm going to be little help, I'm afraid, Mr. AustinChief. My lead programmer is gone for the day and not answering his phone. I'm sorry.

All I could find is some discussion regarding fusion/mpt drivers and that when similar errors are encountered when installing certain SCSI controllers, the "fusion" drivers are expected to work.

My apologies. Had this question come up a couple of hours ago, we might have been able to assist.

FAX

No worries, if nothing else I can try again Monday... but was hoping to finish tonight.

[penguinz]

http://bj.soulinfo.com/projects/scst/qla_isp/README.scst

http://john.parnefjord.se/node/8

[AustinChief]

http://bj.soulinfo.com/projects/scst/qla_isp/README.scst

http://john.parnefjord.se/node/8

The card is ATTO Celerity FC-24XL

Looks to be the Intel IOP331 chipset???

[AustinChief]

BTW.. there is a big BET riding on this. Up to 6 ice cream sandwhiches are on the line!

[googlegoogle]

http://www.attotech.com/support/trouble/linux.html

[AustinChief]

http://www.attotech.com/support/trouble/linux.html

Well beyond that stage.

[CrazyPhuD]

I'd be willing to bet you have a kernel incompatibility issue. Which kernel was it designed for and what kernel are you trying to run it on?

[CrazyPhuD]

Well beyond that stage.

As much as you say this is likely it....

Red Hat or SUSE running 2.6.25 kernel, make file error

*

Kernel version 2.6.25 release has broken all ATTO product Linux drivers. Please use 2.6.24 on earlier kernels until this has been resolved. (Rev 5/1/2008)
*

Note: as/of 4/30/2008, the currently posted Linux drivers for ATTO host adapters have been tested with x32 and x64 kernel versions up to 2.6.24. Please contact ATTO Tech Support to see if there is a beta driver for newer kernels. (Rev 5/1/2008)

Linux tends to change it's subsystems around quite a bit, especially the driver interfaces. If your kernel is post 2.6.24 you likely are SOL.

[AustinChief]

As much as you say this is likely it....



Linux tends to change it's subsystems around quite a bit, especially the driver interfaces. If your kernel is post 2.6.24 you likely are SOL.

yeah, I know... but having just installed it on a CentOS box with the same basic kernel... I think it is more a Debian header file issue

[CrazyPhuD]

yeah, I know... but having just installed it on a CentOS box with the same basic kernel... I think it is more a Debian header file issue

CENTOS 5 is 2.6.18

http://www.centos.org/

Recent Debian is 2.6.26

In 2.6.24 I believe they made major changes to the kobject infrastructure. While I don't know the specifics, is could be a complete overhaul.

If you know your way around the linux kernel you *might* be able to modify the driver to use the new kernel, but even then I would likely not recommend it.

Too good of a chance you're going to have kernel or data integrity issues.

[CrazyPhuD]

BTW uname -a if you want to see the kernel version on the box.

[CrazyPhuD]

If you want to run Debian, install 4.0 will give you a 2.6.18 kernel versus 5.0 which gives you a 2.6.26.

[CrazyPhuD]

One last option to get a 2.6.25+ driver for this card

Novell(i.e. SUSE) claims support for this card. Their current kernel version is 2.6.27. It stands to reason that they should have an updated driver version.

http://www.novell.com/partnerguide/product/203348.html

You may be able to find it in the opensuse source or the SUSE enterprise linux edition.

[AustinChief]

CENTOS 5 is 2.6.18

http://www.centos.org/

Recent Debian is 2.6.26

In 2.6.24 I believe they made major changes to the kobject infrastructure. While I don't know the specifics, is could be a complete overhaul.

If you know your way around the linux kernel you *might* be able to modify the driver to use the new kernel, but even then I would likely not recommend it.

Too good of a chance you're going to have kernel or data integrity issues.

I think you nailed it right here.... I am looking for an update... and considering rolling debian back a version.