[ltp] Fedora installation on T40 and airo_mpi problem

linux-thinkpad@linux-thinkpad.org linux-thinkpad@linux-thinkpad.org
Fri, 7 Nov 2003 15:09:05 +0000 (GMT)

On Thu, 6 Nov 2003 I wrote:

> I'm however having trouble with the onboard Cisco wireless.
> As before, I've followed Fabrice Bellet's helpful instructions on
> installing the driver for the Cisco Aironet 3500 card at:
> http://bellet.info/~bellet/laptop/airo_mpi.HOWTO.txt
> and used them with the latest(?) 20031023 tarball.  There was an
> error in compilation:
> airo_mpi.c:258: error: redefinition of `PDE' /lib/modules/2.4.22-1.2115.nptl/build/include/linux/proc_fs.h:17:
> error: `PDE' previously defined here
> I'm not a programmer so my solution to this was to comment out the
> corresponding portion of code :)  Was it the correct thing to do?
> Also, had to "depmod -a" before modprobing: you might want to add
> this to the notes...
> Anyway, having done this, the card flashes in Managed mode, and I
> thought I was getting a connection, but it turns out I was connected
> to next door's WEP-less access point!  When I try and connect to my
> own Ad-Hoc network with a WEP password, it just won't work whatever I
> do.  When you set Ad-Hoc mode, the little wireless light doesn't even
> flash; Managed and Auto do.  I can't tell if it not working is
> because of Ad-Hoc or because of WEP: any clues?

I'll add a bit more information here.  The portion of code I had to
comment out in airo_mpi.c is as follows:

static inline struct proc_dir_entry *PDE(const struct inode *inode)
        return inode->u.generic_ip;

- this is because it's now duplicated in the Fedora 2.4.22 kernel in
proc_fs.h - or nearly, as follows:

static inline struct proc_dir_entry *PDE(const struct inode *inode)
        return (struct proc_dir_entry *)inode->u.generic_ip;

This doesn't seem to be present in proc_fs.h in 2.4.21 and previous,
which would indicate to an amateur like me that it's now superfluous.
And once commented out and airo_mpi compiled and loaded correctly,
can't be the cause of my WEP/Ad-Hoc problem?