[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: fedora-list Digest, Vol 31, Issue 69



--- Paul Lewis <apflewis gmail com> wrote:

> Trying to follow the instuctions here;
> http://www.geocities.com/chriscmalcolm/index.htm
> Anyway I followed the directions but get a couple of
> odd things.
>
> The driver module is inserted,
>
> Sep  9 19:59:02 Host kernel: CnxADSL: module license
> 'unspecified' taints kernel.
>
> But then the following error messages are inserted into the logs, loads of them...
>
> Sep  9 19:59:02 Host kernel:
>/usr/src/CnxADSL-6.1.2.007-PIM-2.6-1.1-patched/KernelModule/ChipALCdsl.c:1533:
> spin_is_locked on uninitialized spinlock c8b85dec.
> Sep  9 19:59:02 Host kernel:
>
> If I stop and restart the service, I get the
> following in the logs, but
>
> Sep  9 20:02:22 Host pppd[3215]: Plugin
> /usr/lib/pppd/plugins/pppoatm.so loaded.
> Sep  9 20:02:22 Host pppd[3215]: PPPoATM plugin_init
> Sep  9 20:02:22 Host pppd[3215]: PPPoATM setdevname_pppoatm
> Sep  9 20:02:22 Host pppd[3215]: PPPoATM setdevname_pppoatm - SUCCESS
> Sep  9 20:02:22 Host pppd[3216]: pppd 2.4.0b1 started by root, uid 0
>
> What does this mean??
>
> Sep  9 20:02:22 Host kernel: CnxADSL: CmgmtOpen opening
> Sep  9 20:02:22 Host pppd[3216]: ioctl(ATM_SETBACKEND): No such device
> Sep  9 20:02:22 Host kernel: CnxADSL: CmgmtClose
> Closing Sep  9 20:02:22 Host pppd[3216]: Exit.
>
> Normally, I would expect to see the successful
> assignment of the IP
> addresses.
> Kernel is 2.6.9.1
>
Have you tried the instructions here
http://www.purplepixie.org/dave/archive/adsl-howto/
The problem is that they refer to kernel 2.4.X series.
Hope that this helps,

Antonio
Antionio,

Thanks muchly for your reply. I don't think I have problems with the process of building and installing on Core 3. The directions at http://www.geocities.com/chriscmalcolm/index.htm are more than clear on that score. The issue is that once I have built and loaded the kernel module the supporting pppoatm and pppd  it does not perform the way I was hoping it would.

I have seen references to "spinlock" error messages on the web and it does not look too serious, although once I know the system is working I would like to supress them. There are hints that the errors are inherent in the 2.6.9 kernels.

The issue  I was hoping to get feedback about is the last set of errors at the point where I would have hopped to see the ip addresses assigned.

Regards


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]