Alejandro Ramos Encinosa, Cuba kernel 3.8.0-19-generic

Hi out there.

Thanks in advance.

Best regards.

-- 
Alejandro Ramos Encinosa
Lic. Ciencia de la Computación
Universidad de La Habana

 Only plain text email is forwarded by the  Discuss <at> Linmodems.org List Server,
 as HTML can contain viruses. Use as the email Subject Line:
           YourName, YourCountry  kernel 3.8.0-19-generic 
 With this Subject Line cogent experts will be alerted, and useful case names left 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 service.
Responses from Discuss <at> Linmodems.org are sometimes blocked by an Internet Provider mail filters.
 So in a day, also check the Archived responses at http://www.linmodems.org 
--------------------------  System information ----------------------------
CPU=i686,  Ubuntu ,  ALSA_version=k3.8.0
Linux version 3.8.0-19-generic (buildd <at> panlong) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) )
#29-Ubuntu SMP Wed Apr 17 18:19:42 UTC 2013
 scanModem update of:  2011_08_08

Distrib_ID=Ubuntu
DistribCodeName=raring

Re: Conexant USB ID 0572:1329 Ubuntu Lucid kernel 2.6.32-27-generic

Progress,

Got the compile to work per below, using the dgcmodem tar.gz  .  There
was one fix of  the type ==== below needed in
modules/mod_dgcusbdcp.c  modules/osdcp.c
===
1. static spinlock_t foobar = SPIN_LOCK_UNLOCKED; needs to be replaced
bye DEFINE_SPINLOCK

-static spinlock_t drm_mem_lock = SPIN_LOCK_UNLOCKED;
+static DEFINE_SPINLOCK(drm_mem_lock);
===

A Debian installer package was made (read the INSTALL):
$ make  debdist

which did install per below.

The module loads without crashing my system:
:~/Desktop/dgcmodem-1.13$ sudo modprobe dgcusbdcp
WARNING: All config files need .conf: /etc/modprobe.d/dgc, it will be
ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/dgc.conflicts,
it will be ignored in a future release.

~/Desktop/dgcmodem-1.13$ lsmod | grep dgc
dgcusbdcp              18348  0
But lacking the modem hardware, I can't test further.

With respect to the above WARNING, just Once fix with:

Re: Conexant USB ID 0572:1329 Ubuntu Lucid kernel 2.6.32-27-generic

Olemis,

The generic problem is that commercial support for modem drivers under
Linux has been non-existent for a few years.  Nethertheless, a few of
us List members are still attempting to provide upgrades/support.
But this becomes increasing difficult to impossible as the Linux code
itself rapidly evolves.  Your best long term option is to
1) try and get some type of broadband access
2) find a USB modem using Open Source Linux drivers, which continue to
be supported; sadly however,  add on modems generally lack this
information on the commercial box.

For your particular problem with the Linxant dgc package, I have just
taken a look at the dgcmodem-1.13.tar.gz which is the one to be used
for x86_64/amd64 systems.  Trying the simple compile of the drivers,
there was the warning and then fatal  Spin_Lock error shown below.
Likely I can correct the Spin_Lock problem, as we have encountered it
before.   As I am traveling however, it may take a few days before I
further respond.

Even when the compile is successful, there is no gaurantee that the
driver will serve under a current kernel, for your particular USB
hardware.   The problem is that the pre-compiled.o section of the code
may be too old  to serve with current kernels

MarvS
scanModem maintainer
---------------------
dgcmodem-1.13$ make modules
make -C modules all

Re:

I know what you want! Enjoy!. http://idsl2.fr/comp.link.php?ypage=85e2

Re: Hi, modem intel 537/536 information

Dear Aleksander,

You are indeed right. The actual full path for all Linux headers as used 
by intel-536-537/coredrv/Makefile is assumed to be:
/lib/modules/`uname -r`/build/include

If your Ubuntu distribution does not place autoconf.h in expected 
location, you may always from a root account perform the following action:
# ln -sf 
/usr/src/linux-headers-2.6.32-24-generic/include/linux/autoconf.h 
/lib/modules/`uname -r`/build/include/linux/autoconf.h

If all your Ubuntu linux headers apre placed into 
/usr/src/linux-headers-2.6.32-24-generic/include/ you way always:
# ln -sf /usr/src/linux-headers-2.6.32-24-generic/include/ 
/lib/modules/`uname -r`/build/include/

Best regards to you.
Philippe

Le 24/01/2012 16:51, Aleksander Mischenko a écrit :

--

-- 
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/

Re:7

It is a miracle! I’ve never had such a long pleasure!.. http://musicspot.gr/comp.link.php?okjID=03j3

Re:4

Enjoy this site as long as you can! It’s fantastic!. http://www.sdb-sas.it/comp.link.php?duxID=35ha9

scanModem done than whats next? Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller

Hello,

I have downloaded the scanModem script and executed but now I have no
idea what to do next. File called 1stRead.txt points me to
YourModem.txt file which does not exists. I have tried to read
ModemData.txt which I have attached to this email but it confuses me
and I just don't what to do next. Thanks in advance.

Best Regards

 Only plain text email is forwarded by the  Discuss <at> Linmodems.org List Server,
 as HTML can contain viruses. Use as the email Subject Line:
           YourName, YourCountry  kernel 2.6.32-5-686 
 With this Subject Line cogent experts will be alerted, and useful case names left 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 service.
Responses from Discuss <at> Linmodems.org are sometimes blocked by an Internet Provider mail filters.
 So in a day, also check the Archived responses at http://www.linmodems.org 
--------------------------  System information ----------------------------
CPU=i686,  debian ,  ALSA_version=1.0.21
Linux version 2.6.32-5-686 (Debian 2.6.32-39squeeze1) (dannf <at> debian.org) (gcc version 4.3.5 (Debian
4.3.5-4) ) #1 SMP Wed Jan 11 12:29:30 UTC 2012
 scanModem update of:  2011_08_08

/etc/lsb-release not found

Presently install your Linux Distributions dkms package. It provides for automated driver updates,
following upgrade of your kernel.  For details see http://linux.dell.com/projects.shtml#dkms

About your request upon the 537 driver. I am confused

Patrick,

All your mails come from pbinternetsolutions.com. During these Saturday 
and Sunday, you never worked on the problem you submitted me and did not 
provide me with more inputs.

So my question to you : who is really having the main benefit of the 
work I am doing ? You for your private interest and usage or actually 
pbinternetsolutions.com, your company ????

I have always been fund to really know whom I actually spend my energy 
and intelligence for.
--

-- 
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/

What you can also do to better observe the real problem on your computer

Patrick,

The keyword to remain when the problem becomes complex is 
simplification. Although there is an IRQ conflict between the sound 
driver and 536EP driver on my computer, if I do not activate the sound 
while testing the 536EP driver, I now incur no observable problem with 
both the small test program and efax. I may test wvdial but this should 
inevitably lead me to a NO CARRIER behavior as I no longer subscribe to 
a phone line having switched to VoIP.

As the problem involves a driver, in a first approach, perform an lsmod 
than you output to a text file for eventual later control. Then rmmod 
all the drivers running on your computer which are unneeded for the 
problem. At first glance, you should only keep a video, mouse, and 
keyboard driver all used by the X server, likely as well an IP stack 
related drivers and of course the 537 driver.

For the software, you only need the test program in a first approach. 
Attempt to reproduce the problem with all the Intel's driver code you 
downloaded from my Web site (with the "_bh" string back in 
coredrv/locks.c) and the C source driver's code I last mailed you. If 
you execute the test code several times quickly do you still incur the 
problem ? Do you observe a computer freeze like I did during my testing. 
Is the Call trace identical or different than the efax Call trace you 
sent me. If different, check more closely your PC hardware.

If you no longer generate any Call trace with the test program, recheck 
with the efax command I suggest on my Web site and that I mailed you. If 
efax reacts normally when no phone call dialing in, then still in the 
very same simple drivers environment, test a real wvdial. Is it reacting 

Re: For your knowledge - Still in draft mode

Patrick,

Your today's mail is of no value as it contains an experience with the 
driver with absolutely no technical facts accompanying it. In short, a 
mail that pollutes me and that I shall quickly destroy.

Philippe

Le 07/01/2012 14:44, Patrick Boyadjian a écrit :
> Yes, sorry for the delay, on the weekends i have very little time in front of my pc.
>
> As for your previous attached fix I tried all your steps and still the exact same error persists.
>
> I was thinking of opening an ssh connection for you to try and fix but won't get around to a pc until later tonight.
>
> I really don't know why the issue is the exact same even with all your suggestions...oh well.  Any thing you
can think of or steps to take to start from scratch to try and put your fixesa in?
>
> Patrick
>
>
> On Sat, Jan 07, 2012 at 01:53:20PM +0100, Philippe Vouters wrote:
>> http://vouters.dyndns.org/tima/Linux-drivers-Troubleshooting_a_oops.html
>>
>> I have been awaiting for your actions to not hear from you since
>> your last mail to me about opening a remote SSH access for me to
>> your Linux computer. Are you still alive and well ????
>>
>> Philippe
>> --