Re: 11c11040, Re: agere modem for fedora 10?

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

 



Soumen,

A typical cause of the error:
incompatible module

is a message between complier versions in that used to assemble the
kernel and the suspect driver.  Check outputs of:

marv@marvlap:~$ gcc --version
gcc (Ubuntu 4.3.2-1ubuntu11) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

marv@marvlap:~$ cat /proc/version
Linux version 2.6.24-16-generic (buildd@palmer) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008

On my System the gcc versions 4.3.2 are properly matched.

MarvS


On Sun, Mar 22, 2009 at 4:46 AM, Axel Thimm <Axel.Thimm@xxxxxxxxxx> wrote:
> On Sun, Mar 22, 2009 at 08:24:57AM +0530, Soumen banerjee wrote:
>> Hello,
>> I made a little error. Axel here is right, there is no newer kernel
>> and i was on a slightly older kernel(the version numbers are so long
>> :-( ) and i've managed to update and install the ATRPMS package
>> <agrsm> and <kmdl-agrsm>. They installed fine. Now when i try to do
>>
>> modprobe agrsm
>> i get an incompatible modules error. same for
>> modprobe agrserial
>
> Have you checked dmesg? Maybe you use an i686 build on a i586 kernel
> or vice versa? Or are you even on x86_64? For x86_64 the driver will
> not work.
>
>> I wonder why kernel modules built for this specific kernel should be
>> incompatible?
>
> Only due to arch differences, e.g. i586 vs i686 vs i686-pae vs x86_64
> vs ppc vs etc.
>
>> @MarvS We have tried the dkms package before but it is an LZMA
>> compressed rpm which will be supported only on fc11.
>> Regards
>> Soumen
>>
>> On Sun, Mar 22, 2009 at 12:28 AM, Marvin Stodolsky
>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> > Soumen,
>> >
>> > The best route forward is do install dkms and then the dkms-agrsm package.
>> > THere after, the needed new drivers will be auto-compiled, when ever
>> > there is a kernel update, if you co-install the kernel/linux-headers
>> > along with the kernel package.  Usually there usage of the bulkier
>> > souce code can be avoided entirely.
>> >
>> > This is the BEAUTY of the new dkms tools.  It automates updates
>> > concurrent with the installation of new kernels, without need of
>> > active User participation.
>> >
>> > MarvS
>> >
>> > On Sat, Mar 21, 2009 at 6:13 AM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >> Hello,
>> >> I am willing to compile one of the agrsm packages in the pit from
>> >> source and actually patch my kernel with the hda_codec_read and
>> >> .....write lines but the point is that ive been repeatedly told that
>> >> this does not work for the newer kernels and that there are special
>> >> packages for the 27 seriaes of kernels. Is it right? If so what do i
>> >> have to do to make them comile on the newer kernels? If one of the
>> >> rpms could be made to install on my kernel, then also the problem gets
>> >> solved. What is the easiest way to do it?
>> >> Regards
>> >> Soumen
>> >>
>> >> On Sat, Mar 21, 2009 at 12:42 AM, Marvin Stodolsky
>> >> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>> Antonio,
>> >>>
>> >>> It is a 11c11040 modem, from Soumen's orginal disagnostic:
>> >>> =====
>> >>>  The modem codec file for the HDA card is: /proc/asound/card0/codec#1
>> >>> --------------------------------------------------------
>> >>> Codec: LSI ID 1040
>> >>> Address: 1
>> >>> Vendor Id: 0x11c11040
>> >>> =====
>> >>> ./scanModem fake
>> >>> did not so report simply because I haven't yet done an update (will do
>> >>> this weekend) with Soumen's hardware report in it.
>> >>>
>> >>> Soumen,
>> >>>
>> >>> Re: Failed dependencies:
>> >>>       /boot/vmlinuz-2.6.27.19-170.2.35.fc10.i586 is needed by
>> >>> agrsm-kmdl-2.6.27.19-170.2.35.fc10-0.20080808-2.fc10.i586
>> >>> ====
>> >>> is merely reporting that the agrsm drivers in the package were
>> >>> compiled specifically for the 2.6.27.19-170.2.35.fc10.  You either
>> >>> have to use that kernel for those drivers
>> >>> OR
>> >>> compile your own via the dkms route.
>> >>>
>> >>> MarvS
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Mar 20, 2009 at 2:17 PM, Antonio Olivares
>> >>> <olivares14031@xxxxxxxxx> wrote:
>> >>>> Soumen and Marvin,
>> >>>>
>> >>>> something appears wrong with this modem requiring 11c11040 drivers:
>> >>>>
>> >>>> I run scaModem fake and I do not get the 11c11040 drivers:
>> >>>>
>> >>>> [root@localhost ~]# ./scanModem fake 1002:4383 103c:30c2
>> >>>> Running PCIbus cases
>> >>>>
>> >>>>    Substituted test inputs:
>> >>>>  PCIDEV=1002:4383
>> >>>>  SUBSYS=103c:30c2
>> >>>>
>> >>>> Using scanout.fake data, and writing guidance to ModemData.txt
>> >>>> Writing DOCs/Conexant.txt
>> >>>> Writing DOCs/Smartlink.txt
>> >>>>  Writing residual guidance customized to your System.
>> >>>>   A subfolder Modem/  has been written,  containing these files with
>> >>>> more detailed Information:
>> >>>>  ------------------------------------------------------------------------------------------
>> >>>>  1stRead.txt  DOCs  ModemData.txt  scanout.fake tmp
>> >>>>    and in the DOCs subfolder:
>> >>>>  Conexant.txt   DriverCompiling.txt  InfoGeneral.txt  Rational.txt
>> >>>> Smartlink.txt  SoftModem.txt        Testing.txt      UNSUBSCRIBE.txt
>> >>>> wvdial.txt     YourSystem.txt
>> >>>> -------------------------------------------------------------------------------------------
>> >>>>       Please read 1stRead.txt first for Guidance.
>> >>>>
>> >>>>
>> >>>> [root@localhost ~]# ./scanModem fake 1002:4383 103c:30c2
>> >>>> Running PCIbus cases
>> >>>>
>> >>>>    Substituted test inputs:
>> >>>>  PCIDEV=1002:4383
>> >>>>  SUBSYS=103c:30c2
>> >>>>
>> >>>> Using scanout.fake data, and writing guidance to ModemData.txt
>> >>>> Writing DOCs/Conexant.txt
>> >>>> Writing DOCs/Smartlink.txt
>> >>>>  Writing residual guidance customized to your System.
>> >>>>   A subfolder Modem/  has been written,  containing these files with
>> >>>> more detailed Information:
>> >>>>  ------------------------------------------------------------------------------------------
>> >>>>  1stRead.txt  DOCs  ModemData.txt  scanout.fake tmp
>> >>>>    and in the DOCs subfolder:
>> >>>>  Conexant.txt   DriverCompiling.txt  InfoGeneral.txt  Rational.txt
>> >>>> Smartlink.txt  SoftModem.txt        Testing.txt      UNSUBSCRIBE.txt
>> >>>> wvdial.txt     YourSystem.txt
>> >>>> -------------------------------------------------------------------------------------------
>> >>>>       Please read 1stRead.txt first for Guidance.
>> >>>>
>> >>>>
>> >>>> [root@localhost ~]# cd Modem/
>> >>>> [root@localhost Modem]# dir
>> >>>> 1stRead.txt  DOCs  ModemData.txt  scanout.fake
>> >>>> [root@localhost Modem]# cat ModemData.txt | more
>> >>>>  Only plain text email is forwarded by the  Discuss@xxxxxxxxxxxxx List Server,
>> >>>>  as HTML can contain viruses. Use as the email Subject Line:
>> >>>>           YourName, YourCountry  kernel 2.6.27.19-170.2.35.fc10.i686.PAE
>> >>>>  With this Subject Line cogent experts will be alerted, and useful case names le
>> >>>> ft in the Archive.
>> >>>>  YourCountry will enable Country specific guidance. Linux experts in YourCountry
>> >>>>
>> >>>>  can be found through: http://www.linux.org/groups/index.html.
>> >>>> They will know your Country's modem code, which may be essential for dialup serv
>> >>>> ice.
>> >>>> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provid
>> >>>> er mail filters.
>> >>>>  So in a day, also check the Archived responses at http://www.linmodems.org
>> >>>> --------------------------  System information ----------------------------
>> >>>> CPU=i686,
>> >>>> Linux version 2.6.27.19-170.2.35.fc10.i686.PAE (mockbuild@xxxxxxxxxxxxxxxxxxxxxx
>> >>>> t.com) (gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) ) #1 SMP Mon Feb 23 1
>> >>>> 3:09:26 EST 2009
>> >>>>  scanModem update of:
>> >>>>
>> >>>> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/1
>> >>>>  There are no blacklisted modem drivers in /etc/modprobe*  files
>> >>>> No modem drivers are loaded
>> >>>> slamrTest=
>> >>>> Checking  /proc/bus/usb/devices
>> >>>>  USB modem not detected among /proc/bus/usb/devices.
>> >>>>
>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>> >>>>
>> >>>> A candidate modem is not evident among the PCI devices:
>> >>>> ------------------------------------------------
>> >>>> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller
>> >>>>  (rev 02)
>> >>>> 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA
>> >>>>  IDE Controller (rev 02)
>> >>>> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
>> >>>> 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Co
>> >>>> ntroller (rev 02)
>> >>>> 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400 GS (rev a1)
>> >>>> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit
>> >>>>  Ethernet Controller (rev 12)
>> >>>> 03:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Con
>> >>>> troller (rev 03)
>> >>>> 03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Contr
>> >>>> oller (rev 03)
>> >>>> 05:01.0 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem (rev 04)
>> >>>> 05:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)
>> >>>> 05:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC G
>> >>>> igabit Ethernet (rev 10)
>> >>>> ------------------------------------------------
>> >>>>  with USB and bridge devices not displayed.
>> >>>>
>> >>>>  If your modem is connected by an external serial cable,
>> >>>>  or mounted internally on an ISA card, scanModem would not access it.
>> >>>>  Try with Root permission
>> >>>>  $  wvdialconf  /etc/wvdial.conf
>> >>>>  to detect these modem types and some USB modems.
>> >>>>  If the detection is successful, read the DOCs/wvdial.txt .
>> >>>>  Edit the /etc/wvdial.conf with Root permission:
>> >>>>          gedit  /etc/wvdial.conf
>> >>>>  will be able to dial out with Root permission:
>> >>>>         wvdial
>> >>>>
>> >>>>  Many modems for which scanModem fails have Conexant chips.
>> >>>>  From http://www.linuxant.com/drivers/modemident.php
>> >>>>  get the ListModem tool, which will report on Conexant chipset modems
>> >>>>
>> >>>>  If the above tests fail, please provide any independent information available o
>> >>>> n your modem.
>> >>>>  If an alternative boot into Microsoft windows can be done, do mouse
>> >>>> clicks on:
>> >>>>   Start > Settings > Control Panel > Classical View (for Window XP) > System
>> >>>>> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
>> >>>> expand the graphic. Manufacturer information may be displayed. For example, CXT
>> >>>> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
>> >>>> and device information. From the Driver Details TAB, copy out the VENdor and DEV
>> >>>> ice information.
>> >>>> Next do the Query Modem and record the ATI specifications displayed such as:
>> >>>>    ATI3 - Agere SoftModem Version 2.1.22
>> >>>>    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
>> >>>> Try to identify the modem setup file, with name perhaps MODEM.INF.
>> >>>> If may contain chipset Vendor informaton.
>> >>>>
>> >>>>
>> >>>> Predictive  diagnostics for card in bus fake:
>> >>>>        Modem chipset not detected on
>> >>>> NAME="FakeName"
>> >>>> CLASS=FakeClass
>> >>>> PCIDEV=1002:4383
>> >>>> SUBSYS=103c:30c2
>> >>>> IRQ=fake
>> >>>> HDA=1002:4383
>> >>>> SOFT=1002:4383.HDA
>> >>>>
>> >>>>
>> >>>>  High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
>> >>>>  and many are supported by the ALSA audio+modem driver snd-hda-intel
>> >>>>  A modem was not detected on HDA card 1002:4383.
>> >>>>  If another modem card is present, then most likely 1002:4383 does not host a mo
>> >>>> dem.
>> >>>>  If another modem card has not been detected, then possibilities are:
>> >>>>        1) A Conexant modem chip is present on 1002:4383, as Conexant chips
>> >>>>  are frequently not detectable by ALSA diagnostics
>> >>>>        2) The modem may be of the older non-PCI Controller Chipset (hardware) t
>> >>>> ype.
>> >>>> Try detection with Root permission:
>> >>>>         wvdialconf  /etc/wvdial.conf
>> >>>>
>> >>>>  For candidate modem in:  fake
>> >>>>   FakeClass FakeName
>> >>>> [root@localhost Modem]#
>> >>>>
>> >>>> This I get from a previous email:
>> >>>>
>> >>>>>>>> Soumen
>> >>>>>>>>   is your Linux Mandriva or Fedora??
>> >>>>>>>>
>> >>>>>>>> Under CPU=i686,  Mandriva Linux release 2008.1 (Official) for i586
>> >>>>>>>> Kernel 2.6.24.4-custom, compiling is necessary. Packages must be
>> >>>>>>>> installed, providing:
>> >>>>>>>>         kernel-source-2.6.24.4-custom or similiar linux-headers. Check with
>> >>>>>>>> the Mandriva list if you are not familiar with compiling.
>> >>>>>>>>
>> >>>>>>>> Then for the modem hosted on:
>> >>>>>>>> ---------------------------------------------------
>> >>>>>>>>   0403 Audio device: ATI Technologies Inc SBx00 Azalia
>> >>>>>>>>      Primary device ID:  1002:4383
>> >>>>>>>>    Subsystem PCI_id  103c:30c2
>> >>>>>>>>    Softmodem codec or chipset from diagnostics: 0x11c11040
>> >>>>>>>>
>> >>>>>>>> See the resources at http://linux.zsolttech.com/linmodem/agrsm/
>> >>>>>>>> with example  http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html
>> >>>>
>> >>>> I see something wrong and even if it is the 11c11040 driver, I would
>> >>>> try to compile from source and follow the 11c11040 howto because the
>> >>>> rpm(s) fail to install.  This driver is a pain to work with and I feel
>> >>>> for you.  Why not install Ubuntu and get the precompiled one and get
>> >>>> done with it, otherwise build from source and hopefully the 11c11040
>> >>>> experts guide you through the process :)
>> >>>>
>> >>>> Regards,
>> >>>>
>> >>>> Antonio
>> >>>>
>> >>>>
>> >>>> On Fri, Mar 20, 2009 at 12:49 PM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>> Hello,
>> >>>>> Any progress on how i can install this rpm if i have a newer kernel
>> >>>>> than it supports?
>> >>>>> error: Failed dependencies:
>> >>>>>>        /boot/vmlinuz-2.6.27.19-170.2.35.fc10.i586 is needed by
>> >>>>>> agrsm-kmdl-2.6.27.19-170.2.35.fc10-0.20080808-2.fc10.i586
>> >>>>>
>> >>>>> Regards
>> >>>>> Soumen
>> >>>>>
>> >>>>> On Thu, Mar 19, 2009 at 12:12 AM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>> Hello,
>> >>>>>> I tried the agrsm-kmdl packages, they say they need /boot/vmlinuz of a
>> >>>>>> specific kernel subversion.
>> >>>>>> error: Failed dependencies:
>> >>>>>>        /boot/vmlinuz-2.6.27.19-170.2.35.fc10.i586 is needed by
>> >>>>>> agrsm-kmdl-2.6.27.19-170.2.35.fc10-0.20080808-2.fc10.i586
>> >>>>>> So what do i do? I am on a newer kernel...
>> >>>>>> Thanks
>> >>>>>> Soumen
>> >>>>>>
>> >>>>>>
>> >>>>>> On Wed, Mar 18, 2009 at 10:41 PM, Antonio Olivares
>> >>>>>> <olivares14031@xxxxxxxxx> wrote:
>> >>>>>>> There are the ATRPMS repositories which house the rpms for the
>> >>>>>>> 11c11040 chipset.  And there is always compiling from source.  For
>> >>>>>>> this 11c11040 chipset it is definitely a pain :(
>> >>>>>>>
>> >>>>>>> Here are the specs.  for the agrsm
>> >>>>>>> http://dl.atrpms.net/all/agrsm.spec
>> >>>>>>>
>> >>>>>>> Also the src rpm can be rebuilt?  (Sorry about this I do not know much
>> >>>>>>> about it)
>> >>>>>>> http://atrpms.net/dist/f10/agrsm/
>> >>>>>>>
>> >>>>>>> I hope that Axel has created these rpms, but I am not 100% certain :(
>> >>>>>>>
>> >>>>>>> Regards,
>> >>>>>>>
>> >>>>>>> Antonio
>> >>>>>>>
>> >>>>>>> On Wed, Mar 18, 2009 at 7:10 AM, Marvin Stodolsky
>> >>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>> Fedora users,
>> >>>>>>>>
>> >>>>>>>> Any suggestion to rpm-libs problem below?
>> >>>>>>>>
>> >>>>>>>> MarvS
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> ---------- Forwarded message ----------
>> >>>>>>>> From: Soumen banerjee <soumen08@xxxxxxxxx>
>> >>>>>>>> Date: Wed, Mar 18, 2009 at 1:14 AM
>> >>>>>>>> Subject: Re: 11c11040, Re: agere modem for fedora 10?
>> >>>>>>>> To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> Hello,
>> >>>>>>>> I have the newest version of rpm-libs offered by fedora in their
>> >>>>>>>> repositories. After i read about a bit i found that fedora does not
>> >>>>>>>> have support for an lzma compressed rpm as of v10 and will have it in
>> >>>>>>>> fc11. Is there an alternate process in case the rpm does not work?
>> >>>>>>>> Regards
>> >>>>>>>> Soumen
>> >>>>>>>>
>> >>>>>>>> On Tue, Mar 17, 2009 at 7:10 AM, Marvin Stodolsky
>> >>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>>> Check your rpmlib vrersion. It may be earlier than 4.4.6-1
>> >>>>>>>>>
>> >>>>>>>>> MarvS
>> >>>>>>>>>
>> >>>>>>>>> On Mon, Mar 16, 2009 at 1:27 AM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>> Hello,
>> >>>>>>>>>> I found the rpm-libs package in the repository and installed it. now
>> >>>>>>>>>> trying to install the package says that
>> >>>>>>>>>>
>> >>>>>>>>>> rpmlib(PayloadIsLzma) <= 4.4.6-1 is needed by dkms-agrsm-2.1.80-4mdv2009.0.i586
>> >>>>>>>>>>
>> >>>>>>>>>> even though rpmlib is installed. I tried using yum to autofix the
>> >>>>>>>>>> dependency but it does not recognize a dependency at all and says that
>> >>>>>>>>>> the package is unsigned. Please Help
>> >>>>>>>>>> regards
>> >>>>>>>>>> Soumen
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Mon, Mar 16, 2009 at 8:24 AM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>>> Hello,
>> >>>>>>>>>>> the package depends on rpmlibs and there isn't a package in the fedora
>> >>>>>>>>>>> repos called rpmlibs. What needs to be installed instead?
>> >>>>>>>>>>> Soumen
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Mon, Mar 16, 2009 at 7:38 AM, Marvin Stodolsky
>> >>>>>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>>>>>> install the dkms package from fedora,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> See the resources at http://linux.zsolttech.com/linmodem/agrsm/
>> >>>>>>>>>>>> Get the dkms-agrsm-2.1.80-4mdv2009.0.i586.rpm and install.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> See the example
>> >>>>>>>>>>>> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> See the attached.
>> >>>>>>>>>>>> After the drivers are loaded   & symbolic links made, the modem should
>> >>>>>>>>>>>> be found by
>> >>>>>>>>>>>> # wvdialconf
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> if successfull
>> >>>>>>>>>>>> # gedit /etc/wvdial.conf
>> >>>>>>>>>>>> removing the symbols ; < >
>> >>>>>>>>>>>> while putting in your personal info.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Please send to the List, not directly to me,
>> >>>>>>>>>>>> Others are more expert on the 11c11040 modem
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> MarvS
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> MarvS
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Sun, Mar 15, 2009 at 9:41 PM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>> Hello,
>> >>>>>>>>>>>>> have done it. what next?
>> >>>>>>>>>>>>> Soumen
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Mon, Mar 16, 2009 at 7:00 AM, Marvin Stodolsky
>> >>>>>>>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>> compiling is necessary. Packages must be
>> >>>>>>>>>>>>>>>> installed, providing:
>> >>>>>>>>>>>>>>>>         kernel-devel-2.6.27.15-170.2.24.fc10.i686
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Sun, Mar 15, 2009 at 8:33 PM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>>> Hello,
>> >>>>>>>>>>>>>>> Sorry for having been confusing.My linux is fedora 10
>> >>>>>>>>>>>>>>> 2.6.27.15-170.2.24.fc10.i686.
>> >>>>>>>>>>>>>>> Regards
>> >>>>>>>>>>>>>>> Soumen
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Mon, Mar 16, 2009 at 12:48 AM, Marvin Stodolsky
>> >>>>>>>>>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>>>> Soumen
>> >>>>>>>>>>>>>>>>   is your Linux Mandriva or Fedora??
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Under CPU=i686,  Mandriva Linux release 2008.1 (Official) for i586
>> >>>>>>>>>>>>>>>> Kernel 2.6.24.4-custom, compiling is necessary. Packages must be
>> >>>>>>>>>>>>>>>> installed, providing:
>> >>>>>>>>>>>>>>>>         kernel-source-2.6.24.4-custom or similiar linux-headers. Check with
>> >>>>>>>>>>>>>>>> the Mandriva list if you are not familiar with compiling.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Then for the modem hosted on:
>> >>>>>>>>>>>>>>>> ---------------------------------------------------
>> >>>>>>>>>>>>>>>>   0403 Audio device: ATI Technologies Inc SBx00 Azalia
>> >>>>>>>>>>>>>>>>      Primary device ID:  1002:4383
>> >>>>>>>>>>>>>>>>    Subsystem PCI_id  103c:30c2
>> >>>>>>>>>>>>>>>>    Softmodem codec or chipset from diagnostics: 0x11c11040
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> See the resources at http://linux.zsolttech.com/linmodem/agrsm/
>> >>>>>>>>>>>>>>>> with example  http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html
>> >>>>>>>>>>>>>>>> This is the longest term solution.  Ty
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Sun, Mar 15, 2009 at 1:05 PM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>>>>> Hello,
>> >>>>>>>>>>>>>>>>> attaching the modem data file.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Sun, Mar 15, 2009 at 9:51 PM, Marvin Stodolsky
>> >>>>>>>>>>>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>>>>>> Soumen,
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> There are several different Agere modem chipsets, with different drivers
>> >>>>>>>>>>>>>>>>>>  Browse http://linmodems.technion.ac.il and  download scanModem.gz .
>> >>>>>>>>>>>>>>>>>>  Within a Linux partition
>> >>>>>>>>>>>>>>>>>>    gunzip scanModem.gz
>> >>>>>>>>>>>>>>>>>>  To make it executable:
>> >>>>>>>>>>>>>>>>>>    chmod +x scanModem
>> >>>>>>>>>>>>>>>>>>  Run diagnositics with:
>> >>>>>>>>>>>>>>>>>>    ./scanModem
>> >>>>>>>>>>>>>>>>>> Only the ouput ModemData.txt should be sent to Discuss@xxxxxxxxxxxxx
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> MarvS
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> On Sun, Mar 15, 2009 at 5:48 AM, Soumen banerjee <soumen08@xxxxxxxxx> wrote:
>> >>>>>>>>>>>>>>>>>>> Hello,
>> >>>>>>>>>>>>>>>>>>> I have been here before with a mandriva 2008.1 install to get my agere
>> >>>>>>>>>>>>>>>>>>> mdem running and it worked. I have upgraded to fedora 10 now and i was
>> >>>>>>>>>>>>>>>>>>> trying to get this modem to work again. since fedora 10 carries the
>> >>>>>>>>>>>>>>>>>>> new 2.6.27 kernel, want to ask the exact process i should follow. I
>> >>>>>>>>>>>>>>>>>>> found some packages at ATRPMS for the 27 version of the kernel but
>> >>>>>>>>>>>>>>>>>>> they dont work with this exact subversion and my graphics driver works
>> >>>>>>>>>>>>>>>>>>> only with this version :-(
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> what is the process to set it up? My exact kernel version is:-
>> >>>>>>>>>>>>>>>>>>> 2.6.27.15-170.2.24.fc10.i686
>> >>>>>>>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>
> --
> Axel.Thimm at ATrpms.net
>


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

  Powered by Linux