>Once you said 'here is my site for this certain soft updates', you can't
>excpect that people do not check it in a regular basis, did you announce
>anything or not.
I'm not expecting anything. I just find it amusing when people grab
stuff that has no instructions, don't look at what they've gra
On 04.08 Justin T. Gibbs wrote:
>
> Actually, I would say, "Apply the 2.4.3 patch. It will probably apply
> cleanly to your kernel. If it doesn't, and you don't know enough C
> to correct the problem, you shouldn't be playing around with kernel
> patches."
>
Below is inlined the patch that to
>> To be expected as you didn't apply the patch to scsi_lib.c that makes
>> scsi_unblock_host() actually run the device queues to start the system
>> back up again.
>>
>
>There is no patch for 2.4.3-ac3. You could say, well if you want 6.1.10,
>use plain 2.4.3.
Actually, I would say, "Apply the 2
On 04.07 Justin T. Gibbs wrote:
>
> That's not a sufficient way to upgrade. The tar files are there for
> people who are porting the driver to other platforms. You should always
> use the patches to upgrade as they often touch other portions of the
> Linux kernel that need fixes in order to wo
>Hi.
>
>Subject says it all.
>
>With latest updates, i just deleted the kernel aic7xxx subtree, put instead
>the updated (from people.freebsd.org) tree, and built. All went fine
>until (and including) 6.1.9.
That's not a sufficient way to upgrade. The tar files are there for
people who are porti
Hi.
Subject says it all.
With latest updates, i just deleted the kernel aic7xxx subtree, put instead
the updated (from people.freebsd.org) tree, and built. All went fine
until (and including) 6.1.9.
6.1.10 just stops after the init messages and stays there forever.
scsi0 : Adaptec AIC7XXX EISA
6 matches
Mail list logo
