linux-kernel - Re: Areca driver 2.6.19 on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <000301c719a9$70e4f8d0$2900a8c0@arecakevin>
Date:	Thu, 7 Dec 2006 10:43:09 +0800
From:	"Areca Support" <support@...ca.com.tw>
To:	"Bron Gondwana" <brong@...tmail.fm>, <filip@...oweb97.com>
Cc:	<linux-kernel@...r.kernel.org>, <erich@...ca.com.tw>
Subject: Re: Areca driver 2.6.19 on x86_64

Dear Sir,

This is Kevin Wang from Areca Technology, Tech-Support Team.
regarding your problem, please trying to disable ACPI in kernel loader.
if the problem happen as soon as driver loaded, it should be the IRQ
releated issue.
the motherboard bios didn't assigned a correct IRQ to controller, it makes
the driver can't initialize controller.
and in our experience, disable ACPI in kernel loader can solved this ussue
in some distro.


Best Regards,


Kevin Wang

Areca Technology Tech-support Division
Tel : 886-2-87974060 Ext. 223
Fax : 886-2-87975970
Http://www.areca.com.tw
Ftp://ftp.areca.com.tw

----- Original Message ----- 
From: "Bron Gondwana" <brong@...tmail.fm>
To: <filip@...oweb97.com>
Cc: <support@...ca.com.tw>; <linux-kernel@...r.kernel.org>;
<erich@...ca.com.tw>
Sent: Thursday, December 07, 2006 7:09 AM
Subject: Re: Areca driver 2.6.19 on x86_64


> On Wed, Dec 06, 2006 at 05:51:32PM +0100, filip@...oweb97.com wrote:
> > OS distro used:
> > CentOS 4.4 x86_64
> > Kernel 2.6.19 with hand-crafted config, that we are
> > able to use successfully with kernel 2.6.16.20.
>
> What patches were you applying to 2.6.16.20, since that didn't
> have an Areca driver in it I presume you're at least using that.
>
> > Have you any suggestions to resolve this issue ?
>
> 32 bit kernel?  I'm somewhat serious here, depending what applications
> you're running on the machine.
>
> Otherwise, no clue sorry - we're running 32 bit kernels everywhere
> even on the couple of new Core machines we have.
>
> Bron.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/