For what its worth the belkinunv driver works with Belkin F6C1100-UNV But i did get this kernel err, i have no idea how to read it but it says proc was the driver.. I couldnt restart upsmon because of flock/lockf.. maybe thats a good thing? Its probably[is] my fault that I smacked the cable, but it shouldnt barf like that. If this is all irrelevant then ignore. Thanks Oct 2 02:41:17 ez kernel: EIP: 0010:[<c017e4a7>] Not tainted Oct 2 02:41:17 ez kernel: EFLAGS: 00010206 Oct 2 02:41:17 ez kernel: Oct 2 02:41:17 ez kernel: EIP is at (2.4.18-3EZ-Aug2003) Oct 2 02:41:17 ez kernel: eax: 00000228 ebx: 00000006 ecx: c024a5c0 edx: 00000227 Oct 2 02:41:17 ez kernel: esi: d6abc000 edi: 00000001 ebp: c15a9960 esp: d6abded0 Oct 2 02:41:17 ez kernel: ds: 0018 es: 0018 ss: 0018 Oct 2 02:41:17 ez kernel: Process belkinunv (pid: 1587, stackpage=d6abd000) Oct 2 02:41:17 ez kernel: Stack: 00000006 00000286 00000000 bffff770 d6abc000 00000000 00000006 c016fb3c Oct 2 02:41:17 ez kernel: d8625000 00000001 bffff770 00000006 00000000 d6abc000 00000000 00000000 Oct 2 02:41:17 ez kernel: 00000000 d6abc000 d8625978 d8625978 00000006 00000000 d8625000 bffff770 Oct 2 02:41:17 ez kernel: Call Trace: [<c016fb3c>] Oct 2 02:41:17 ez kernel: [<c016bae2>] Oct 2 02:41:17 ez kernel: [<c016f9b0>] Oct 2 02:41:17 ez kernel: [<c0137fd5>] Oct 2 02:41:17 ez kernel: [<c0109e89>] Oct 2 02:41:17 ez kernel: [<c010a021>] Oct 2 02:41:17 ez kernel: [<c0108a13>] Oct 2 02:41:17 ez kernel: Oct 2 02:41:17 ez kernel: Oct 2 02:41:17 ez kernel: Code: ff 74 20 28 ff 35 80 7c 2a c0 e8 ca 9b 08 00 89 d9 83 c4 0c upsmon 2.0.0 belkinunv 0.06 rh7.3 2.4.18-3