AgereSystems/LSI 11c11040 chip modems and kernel 2.6.28 systems

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

 



Bjorn has made the observation that 11c11040 chip modems have not yet
been successfully used under the new 2.6.28 kernels.  Searching
through the List mail, this does sadly seem to be true.  So herein I
am giving more explicit instructions for  the temporary work around.
The major functional point is that Jaunty installation does support
the earlier 2.6.27 kernels, under which the 11c11040 chipset modems
have been well supported by the dkms-agrsm packages.

These instructions are given for the specific case of Ubuntu Jaunty
installations, but it should be obvious how to extend the instructions
to other  Systems.
Here are the URLs from which to start download of the necessary packages:
http://linmodems.technion.ac.il/packages/ltmodem/11c11040/  get the
   dkms-agrsm_2.1.80-6_i386.deb , agrsm-tools_0.0.1_all.deb  and
agrsm_howto.txt
>From the following URLs,  just get the primary package named, as the
dependencies are already satisfied on your Ubuntu system.
http://packages.ubuntu.com/jaunty/dkms
http://packages.ubuntu.com/intrepid-updates/linux-headers-2.6.27-11
http://packages.ubuntu.com/intrepid-updates/linux-headers-2.6.27-11-generic
http://packages.ubuntu.com/intrepid-updates/linux-image-2.6.27-11-generic

Should you have an alternate ethernet/wireless connection, the short
way to install the last four packages is to:
$ sudo gedit /etc/apt/sources.list
to add a line:
deb http://us.archive.ubuntu.com/ubuntu/ intrepid-updates main restricted
Then:
$ sudo apt-get update
after which:
$ sudo apt-get linux-headers-2.6.27-11-generic dkms
linux-image-2.6.27-11-generic
will suffice to get and install the four packages
Remember afterward to remove the additional line, though it will do no harm.

If the phone line is your only connection.  Then download all the
above manually, and copy to your personal folder.  Therein all the
*.deb packages will be co-installed by:
$ sudo dpkg -i *.deb

Afterwards, reboot using the -2.6.27-11-generic choice.
The agrmodem + agrserial drivers will be compiled and installed  automatically.
The first test to run is:
$ sudo agrsm-test
which hopefully will find the modem.

Apologies if some of you receive this message twice, but I'm not sure
whether all of you are on the list

MarvS




---------- Forwarded message ----------
From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
Date: Sun, May 10, 2009 at 1:19 PM
Subject: Re: 11c11040 probem Re: Rami, Syria kernel 2.6.28-11-generic
To: rami daoud <ramidawod34@xxxxxxxxx>
Cc: Linmodems <discuss@xxxxxxxxxxxxx>


Rami,

Please join the List through the SUBSCRIBE link at  http://www.linmodems.org
and send email to the List, not directly to individuals, to benefit
from the broadest experience!!

With  Linux unlike Microsoft, reinstallations are typically  NOT
necessary, and time wasteful

RE: > /var/lib/dpkg/info/dkms-agrsm.postinst: 2: /usr/sbin/dkms: not found
you have to install the dkms package first, then the dkms-agrsm and
agrsm-tools packages

Assuming Bjorn is correct, the quickest way to get online is to
download kernel 2.6.27-11-generic support by getting packages from:
http://packages.ubuntu.com/intrepid-updates/linux-headers-2.6.27-11
http://packages.ubuntu.com/intrepid-updates/linux-headers-2.6.27-11-generic
http://packages.ubuntu.com/intrepid-updates/linux-image-2.6.27-11-generic

just get the primary packages as the dependencies are already
supported  under Jaunty
They can be co-installed with with:
$ sudo dpkg -i linux*.deb

Then reboot with  the 2.6.27-11-generic kernel, and run the:
$ sudo agrsm-test

Once you have service under 2.6.27-11-generic, we can later work on
the 2.6.28 problems.

MarvS




On Sun, May 10, 2009 at 12:36 PM, rami daoud <ramidawod34@xxxxxxxxx> wrote:
> I formatted ubuntu and made clean installation and below is my second
> attempt via the terminal.
>
>
> To run a command as administrator (user "root"), use "sudo <command>".
> See "man sudo_root" for details.
> emil@emil-laptop:~$ sudo ifconfig ath0 down
> [sudo] password for emil:
> ath0: ERROR while getting interface flags: No such device
> emil@emil-laptop:~$
> emil@emil-laptop:~$ sudo ifconfig ath0 down
> ath0: ERROR while getting interface flags: No such device
> emil@emil-laptop:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:16:d4:f9:26:b8
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>           Interrupt:252 Base address:0xc000
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:44 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:3424 (3.4 KB)  TX bytes:3424 (3.4 KB)
> wlan0     Link encap:Ethernet  HWaddr 00:19:7e:5e:e6:02
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> wmaster0  Link encap:UNSPEC  HWaddr
> 00-19-7E-5E-E6-02-00-00-00-00-00-00-00-00-00-00
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> emil@emil-laptop:~$ sudo ifconfig wmaster0 down
> emil@emil-laptop:~$ sudo ifconfig wlan0 down
> emil@emil-laptop:~$ sudo ifconfig lo down
> emil@emil-laptop:~$
> emil@emil-laptop:~$ sudo ifconfig eth0 down
> emil@emil-laptop:~$ ifconfig
> emil@emil-laptop:~$ dir
> Examples  سطح\ المكتب  صور  عام  فيديو قوالب  مستندات موسيقى
> emil@emil-laptop:~$ sudo dpkg -i dkms*.deb agrsm*.deb
> Selecting previously deselected package dkms-agrsm.
> (Reading database ... 103898 files and directories currently installed.)
> Unpacking dkms-agrsm (from dkms-agrsm_2[1].1.80-5_i386.deb) ...
> Selecting previously deselected package agrsm-tools.
> Unpacking agrsm-tools (from agrsm-tools_0[1].0.1_all.deb) ...
> Setting up dkms-agrsm (2.1.80-5) ...
> /var/lib/dpkg/info/dkms-agrsm.postinst: 2: /usr/sbin/dkms: not found
> /var/lib/dpkg/info/dkms-agrsm.postinst: 3: /usr/sbin/dkms: not found
> /var/lib/dpkg/info/dkms-agrsm.postinst: 4: /usr/sbin/dkms: not found
> Setting up agrsm-tools (0.0.1) ...
> After installing agrsm drivers for 2.6.28-11-generic, run:
>  sudo agrsm-test
> to test for modem detection with wvdialconf
> emil@emil-laptop:~$ sudo agrsm-test
>  The agrsm drivers not found for boot kernel 2.6.28-11-generic .
>  Were they installed for a different kernel version?
>  Checking all installed module trees:
>  Exiting
> emil@emil-laptop:~$
>
>
> --- On Sun, 5/10/09, Bjorn Wielens <Uniacke1@xxxxxxxx> wrote:
>
> From: Bjorn Wielens <Uniacke1@xxxxxxxx>
> Subject: Re: 11c11040 probem Re: Rami, Syria kernel 2.6.28-11-generic
> To: "Marvin Stodolsky" <>
> Cc: "rami daoud" <ramidawod34@xxxxxxxxx>, "Linmodems"
> <discuss@xxxxxxxxxxxxx>
> Date: Sunday, May 10, 2009, 8:00 AM
>
> Marv and others,
> Typically, this kernel crash (pointer dereference in agrsm) is caused by
> a different version of ALSA than the drivers were "intended" for.
>
> cat /proc/asound/version will reveal the version of ALSA installed.
> My systems have 1.0.17 (and 1.0.18). There have been no success reports
> yet for your kernel, if I recall correctly, which suggests it may be
> using a newer alsa version.
> If this is the case, you may want to consider downgrading to an older
> version of (at least) the driver package, alsa-drivers-1.0.xx) where xx
> can be 18 or 17. Likely they must be built from source, which is
> available at http://alsa-project.org/
>
> Best,
> Bjorn.
>
> Marvin Stodolsky wrote:
>> Rami,
>>
>> This is a bad problem, below.  Possibly it might be alleviated by
>> blocking loading of other drivers.
>> But I cannot take more time tonight.
>>
>> Marvin
>> ----------------------
>
>
>


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux