RE: > isn't there any other solution? Not until someone with good COMM code knowledge can make a fix. But the 2.6.28 kernels serve fine on an otherwise Ubuntu 9.10 Karmic system. Then is what I'm using now on a MacBook, because I haven't full tamed touchpad/mouse irregularity under the 2.6.31 kernels. MarvS On Sun, Nov 22, 2009 at 12:30 PM, Mirko Zanda <mirkuz9991@xxxxxxxxx> wrote: > if i have to keep 2.6.28 kernel i prefer keep on staying on jaunty... > isn't there any other solution? > > 2009/11/22, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>: >> Mirko, >> >> The core problem then is that under 2.6.31 kernels, the dialout using >> the slamr driver is failing with: >> No Carrier >> Though Amtonio reports success upto 2.8.30 kernels on a SLACK system >> You can use 2.6.28 kernels on a Karmic system. However to compile, >> you will have to install gcc-4.3 and linux-headers matching your >> kernel. >> >> Note that I have prepared some slamr install packages at >> http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ >> >> MarvS >> >> On Sat, Nov 21, 2009 at 8:16 PM, Mirko Zanda <mirkuz9991@xxxxxxxxx> wrote: >>> well, i'm sorry i wasn't really clear in my last mail. i actually have >>> been using this modem since 8.04, it is a motorola sm56 modem. i did >>> install sl-modem-daemon,sl-modem-source, (all the dipendencies he >>> asked), compiled and installed the modules. i've also made the file >>> >>> /etc/modprobe.d/mirko.conf >>> >>> >>> with inside: >>> install slamr modprobe --ignore-install ungrab-winmodem ; modprobe >>> --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 >>> /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) >>> >>> >>> (mirko.conf and its content was given me by Marvin for 9.04, so i >>> think it may work this time too) >>> >>> wvdial.conf is alright. i'm actually copying the file from the old >>> system to the new one, and there is no chance for it to change... >>> >>> if you need more info here i am. >>> >>> >>> ---Mirko >>> >>> 2009/11/21, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>: >>>> Mirko, >>>> >>>> There are a few chipsets which are under Microsoft all called sm56. >>>> Only the 1057:3052 chipset is supported in principle by slamr. >>>> But in practice, the last kernel supported is 2.8.30, with a "No >>>> Carrier" error reported for 2.8.31 >>>> >>>> Did you even have slamr support under earlier kernels? >>>> If not best download and run scanModem. Then send us the output >>>> ModemData.txt >>>> >>>> MarvS >>>> >>>> On Sat, Nov 21, 2009 at 2:01 PM, Jacques Goldberg >>>> <Jacques.Goldberg@xxxxxxx> wrote: >>>>> Excuse me Mirko but every human is allowed and bound to make mistakes: >>>>> did >>>>> you remember to have >>>>> >>>>> Carrier Check = no >>>>> >>>>> in your wvdial.conf ? >>>>> >>>>> >>>>> If your problem is more serious than that, can you please supply us with >>>>> your ModemData.txt generated by scanModem , and a copy of the output of >>>>> wvdial when you try to connect ? >>>>> >>>>> (http://linmodems.technion.ac.il#scanModem , if you did not use >>>>> scanModem >>>>> before) >>>>> >>>>> >>>>> Jacques >>>>> >>>>> Mirko Zanda wrote: >>>>> >>>>>> i'm trying to get sm56 working on ubuntu on 9.10 but it keeps saying >>>>>> no carrier... i'm sure wvdial.conf is ok because it works in previous >>>>>> versions. anyone who can help? >>>>>> >>>>> >>>>> >>>> >>> >> >
