RocketPorts and Linux

I have found the root of the rocketport problem. The kernel distributions come with a rocket.o module that is incompatible with our hardware. When an upgrade is performed, the new rocket.o is found and it breaks everything.

The new rocket.o is installed in

/lib/modules/<kernel-version>-default/kernel/drivers/char/rocket.o

and is no good for us.

Meanwhile the driver on the comtrol website works 100% and is exactly what we want. The current compiled version is in /project/gsp/bat/rocketport and I tend to just copy it over the kernel-installed one. This will presumably be necessary for each kernel upgrade.

When rocket.o (the correct one) is modprobed, it prints out the port allocations to /var/log/messages:

Jul 6 08:41:28 dogbolter kernel: RocketPort device driver module, version 2.11, 12-Aug-2003 Jul 6 08:41:28 dogbolter kernel: Comtrol PCI controller #0 ID 0x1 found in bus:slot:fn 00:0d.0 at address 1000, 4 AIOP(s) (RocketPort 32 port w/external I/F) Jul 6 08:41:28 dogbolter kernel: Installing RocketPort 32 port w/external I/F, creating /dev/ttyR0 - 31 Jul 6 08:41:28 dogbolter kernel: Comtrol PCI controller #1 ID 0x4 found in bus:slot:fn 00:0e.0 at address 1480, 1 AIOP(s) (RocketPort 4 port w/quad cable) Jul 6 08:41:28 dogbolter kernel: Installing RocketPort 4 port w/quad cable, creating /dev/ttyR32 - 35

This is the correct order on dogbolter and sets the Bat system up nicely.

Rob.