From: Paul on
On 01/30/10 05:48 PM, Aaron W. Hsu wrote:
> On Sat, 30 Jan 2010 01:08:44 -0500, Paul <pminottawa(a)yahoo.ca> wrote:
>
>> I got the same errors when I first tried to build the driver using the
>> kernel 2.6.29.6 huge kernel that is installed with Slackware64 13.
>
> Could you perchance take the generic.s kernel and use that? I'd like to
> see if the build fails when using that kernel with a properly defined
> initrd and such.
>
> Aaron W. Hsu
>

The 2.6.32.5 kernel comes from Slackware...it is an upgrade apparently.
It has a number of problems, one is that the ATI driver has ome
incompatibility with it and another is that as installed by slackpkg, it
doesn't install ATA drivers...it took me a while to figure that out.

I am looking into a patch ATI driver right now.
From: Henrik Carlqvist on
Paul <pminottawa(a)yahoo.ca> wrote:
>>> I got the same errors when I first tried to build the driver using the
>>> kernel 2.6.29.6 huge kernel that is installed with Slackware64 13.
>
> The 2.6.32.5 kernel comes from Slackware...it is an upgrade apparently.

If you are considering kernel 2.6.32.5 an upgrade for your Slackware
installation you are probably not running Slackware 13 but Slackware
current. The last kernel upgrade for Slackware 13 was the security fix
patches/packages/linux-2.6.29.6-3

If you are running Slackware current you should not expect anything to be
useful, Slackware current are for people prepared to voluteer as a beta
tester.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Paul on
On 01/31/10 12:26 PM, Henrik Carlqvist wrote:
> Paul<pminottawa(a)yahoo.ca> wrote:
>>>> I got the same errors when I first tried to build the driver using the
>>>> kernel 2.6.29.6 huge kernel that is installed with Slackware64 13.
>>
>> The 2.6.32.5 kernel comes from Slackware...it is an upgrade apparently.
>
> If you are considering kernel 2.6.32.5 an upgrade for your Slackware
> installation you are probably not running Slackware 13 but Slackware
> current. The last kernel upgrade for Slackware 13 was the security fix
> patches/packages/linux-2.6.29.6-3
>
> If you are running Slackware current you should not expect anything to be
> useful, Slackware current are for people prepared to voluteer as a beta
> tester.
>
> regards Henrik

Yep, that was the problem. Thanks.

I had always used current before, stupidly thinking it meant "current
state of the latest version". I had always used current in the past to
no ill end. 'guess it was just dumb luck. The only real question now is
why don't I have that dumb luck with lottery tickets.