Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well I hate to interrupt the modem questions -but I didn't wanna start a whole new thread but I really am amazed how pesky little there is on-line about my crappy Cheetah internal modem (now known to be Lucent-based chipset -now owned by Agere) (got routed to a weird Cheetah Africa modem web site ) in my Red Hat 7.2 box, It tells me it can't find it but it lists it as a possible manual install - which, of course I try but crappy thing still won't dial... Annoying! I will find it! But any input is appreciated!
Originally posted by kerozen well, it appears that i have all kernel source in place, gcc is installed, but each time i try to make the file CnxADSL.o, i get errors 2.
but the file appears in subfolder kernel module.
So i use it and get error about version of gcc and a tainted kernel.
Does anyone successfully make this file under mdk 9.2 (kernel 2.4.22-10 mdk and gcc 3.3.) ?
I have only been able to get the driver to work with one kernel (the original kernel that comes with knoppix which is what I am using).
If I use any debian stock kernel, or kernel that I compile myself I get the errors you have been having about gcc2/3. I have tried to compile new kernels with gcc 2.95 but this didn't work so I think I didn't do it right.
the way I got round it was using the kernel that came with knoppix (which I think must have been compiled with gcc 2.x), then I installed the debian package gcc-2.95. I don't know how mandrake works, but in debian this gives multiple gcc binaries, named gcc-2.95, gcc-3.3 etc.
I then had to change each of the makefiles in the Conexant source to use gcc-2.95 instead of gcc, this would then compile the module ok, and assuming I manually installed it into the correct location this would work.
I *think* the reason these gcc2/3 errors occur is because there is some proprietary code in dpcontroller.o.proprietary. I think that this must have been compiled with gcc2, hence all the errors. If I am correct, then this means that you must compile your module AND kernel with gcc2 or it won't work.
I have read some stuff on the internet concerning getting the module to work with gcc3 but the vast majority of the material documenting successful usage of this module seems to use gcc2.
I would love to be proved wrong about this gcc2 thing because it is a royal pain in the arse making sure that everything is compiled with gcc2. anybody?
Like you said, some people have results with gcc >3.3.1, but not on mandrake...
I know this, so i decided to try fedora core which seems to work with this card.
But during installation (at the beginning, when X start) i got a black screen...My quadro 4 isn't recognized...So i keep Mandrake, et i'll try fedora on another PC (celeron 766 and i815 integrated...) i will see.
basically I think these conexants are terrible. it seems to be mostly the appalling drivers that are the problem. Now that I have got it working in linux, it seems that the linux driver is actually more stable than the windows ones i've tried, but its such a problem getting it working, it took about 3 days of my time.
maybe its worth the £30 or so to get an external router, that doesn't need drivers..
I've been messing about for about a week trying to get this modem to run. Has anyone devised and posted a foolproof method? It seems all the info floating about merely adds to the confusion.
In the meantime, back to putting the kettle on and scratching the head...
well, thanks a lot whiteshark, but we are not talking about usb modem, but PCI modem !
this one, Conexant PCI adsl modem is sell by Olitec in my country (France), and they do not sell it with linux drivers.
So when i asked them where i can found a driver for linux, they answer me to buy another modem from them, a usb one....(of course !)
But i know some people successfully installed this PCI modem under linux, but not all distros.
it seems that the newer the kernel is, the badest the compilation is.
So to my mind, only some distros like debian, Fedora Core, RedHat 7-8-9 and maybe Mandrake 9.0 or 9.1 can compile this f....n' module CnxAdsl.o for the modem to run....
Men like me, who run Mdk 9.2 or newer, have very big problem to compile, due to the politic of Conexant to sell their newest drivers under linux....what a pity...
I haven't yet, but will get the dodgy instructions working! I'll post easy to follow instructions the day I get it done. Learning bucket-loads by the day
Just read the thread here and think I can clarify a few points for you. The thing about changing kcc to gcc affects the Makefile and nothing will build properly if you try using kcc unless you've got it installed. AFAIR this is some older compiler and is the same as gcc (or perhaps even an earlier version). You need to edit your Makefiles which you will find in various directories.
Somewhere near the top is a line like COMPILER=kcc and you need to change that to gcc - I think that's all but you might want to search the file for any 'kcc' reference. An already-altered version which works for RedHat is available for download with the other stuff I needed at http://www.purplepixie.org/dave/archive/adsl-howto
The gcc3 error is the same one I had - basically those versions of the modules just plain and simple don't seem to work with any kernel compiled with gcc3. In the end I reverted back a couple of distro. versions (you can't just use gcc2 to compile your new a funky kernel).
There are apparently newer drivers which seem to work on newer kernels at:
There is mainly two versions of the card
- Tigris
CnxtDslVendorId=0x14F1 \
CnxtDslArmDeviceId=0x1610 \
CnxtDslAdslDeviceId=0x1611 \
CnxtDslPhysicalDriverType=1
- Yukon (newer I suppose the values to insmod are thoses)
CnxtDslVendorId=0x14F1 \
CnxtDslArmDeviceId=0x1620 \
CnxtDslAdslDeviceId=0x1621 \
CnxtDslPhysicalDriverType=2
Olitec cards is a Yukon cards
it need to replace in cnxadsl.conf
CnxTyF.hex with CnxYkF.hex
(and maybe AutoWiringSelection 0 )
I had success to sync with Olitec card, just need to go one more step forth to connect.
Nota don't forget to
modprobe atm
before trying to insmod CnxADSL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
but I really am amazed how pesky little there is on-line about my crappy Cheetah internal modem (now known to be Lucent-based chipset -now owned by Agere) (got routed to a weird Cheetah Africa modem web site 
) in my Red Hat 7.2 box, It tells me it can't find it but it lists it as a possible manual install - which, of course I try but crappy thing still won't dial... 
