On Saturday 16 September 2006 17:58, Volker Kuhlmann wrote: > An external modem is the simplest and most futureproof solution. > Secondhand externals go for less than a new internal. > > If you want to make the software work because buying new hardware is > against the grain, do not recompile the kernel. Just recompile the > ltmodem driver. Note you must have the kernel sources installed though! > > You should not need to config the kernel. If you do, specifically > /usr/src/linux/.config must be identical to the one used to make the > distro kernel. Then only run make oldconfig. Do not run make clean or > make mrproper. > > You can then compile ltmodem in a suitable place and replace the one or > two *.ko files with the ones compiled. > > This procedure will help if and only if the ltmodem source you're > compiling is newer than the one you have, and fixes the problem(s) with > your particular lucent chip. Lucent chips used to always work; now there > are too many varieties and some are said to not work. If the box in > question is 2 years old or more, your chances with that modem card are > very low, but do try another live boot CD.
Thanks for all the tips Volker. My neighbour is borrowing my modem for now so he can try out Linux, and I think he would be prepared to buy an external if it's the easiest solution. > A different distro isn't likely to help you. You're having a kernel > issue with a specific piece of hardware. Distros only differ by kernel > in: > * kernel version - newer supports more bleeding-edge hardware > * accidental bugs > * patches, fixes, improvements applied by the distro vendor > > Case 2 will help you only as a side effect, case 3 only if the vendor > applied something deliberately which pertains to your exact chip. > > > Yes it is inet.net.nz. I phoned them this afternoon and the guy on the > > help desk suggested I try tomorrow afternoon when there should be someone > > there who knows about Linux. > > Can you please remember to post (or email me privately) whether this ISP > needs the stupid mode in wvdial turned on? Please confirm your setp is > actually using wvdial, then try with both stupid setting and let me know > the result. I'm compiling an NZ ISP file with their specifics already > filled in. Thanks. I think I agree with Nick's post that wvdial is just another front end to pppd. I haven't got access to the computer at the moment to check out any details, but I did try adding 'Stupid mode = on' to /etc/wvdial.conf yesterday and it didn't make any difference. I would say it's fairly conclusive that the modem driver is the cause of the problems rather than the configuration. Tom
