2. Patch your sound driver file hda_codec.cto for export symbols needed by the drivers:
1. Use your favourite PLAIN TEXT editor, such as vi or gedit, and with root permission. This file is typically located at /usr/src/linux/sound/pci/hda/hda_codec.c
2. Add the lines EXPORT_SYMBOL(snd_hda_codec_read); and EXPORT_SYMBOL(snd_hda_codec_write); to the file, after the list of '#include' statements in the beginning.
3. Save the file.
3. Rebuild and install the new modules:
1. In /usr/src/linux, run the following commands:
2. sudo make oldconfig
3. sudo make modules NOTE: This command will take a while, and give lots of ouptut. Watch for any errors when it finishes. (Warnings are okay).
4. Copy the newly built module to your modules directory: sudo cp sound/pci/hda/snd_hda_intel.ko /lib/modules/`uname -r`/kernel/sound/pci/hda/snd-hda-intel.ko NOTE: Some systems (e.g. Ubuntu) deviate form this as the module's path. When in doubt, use a file search utility to search for an existing snd-hda-intel.ko file in /lib/modules/ and replace it with your patched version.
5. Restart your computer to activate the new module.
6. Verify that your sound still works.
4. Obtain the correct agrsm driver from the linmodems 11c11040 pit. The file you get depends on the ALSA version you found in step 1:
* If your ALSA modules version is 1.0.15 or older, get the file agrsm-HDA-20080721-ALSA15.tar.bz2
* If you have ALSA modules version 1.0.16 or newer, get the file agrsm-HDA-20080721.tar.bz2

NOTE: On some systems, only the ALSA15 package will compile properly, yet these systems ship with ALSA v.16 or newer. If this is the case, see footnote 1.
5. Unpack the archive with tar -jxvf (filename) and change to the newly created directory with cd agrsm-20080721
6. Compile the modem driver with make module If you get an error about an SNDRV_CARDS, make sure you downloaded the file with the -ALSA15 suffix. If so, and you still get the error, contact the Linmodems mailing list for assistance.
7. When the module has built, install the new modules:
1. sudo mkdir /lib/modules/`uname -r`/extra
2. sudo cp *.ko /lib/modules/`uname -r`/extra/
3. Register the new modules with sudo depmod -ae
8. Now load the new modules:
1. sudo modprobe agrmodem If this gives an error, check the output of dmesg | tail. If there is a version disagreement about symbol snd_cards then try again with sudo modprobe agrmodem --force-modversion
2. Then load the serial driver with sudo modprobe agrserial
9. Congratulations, your modem should now be working- check if the device node /dev/ttyAGS3 exists. This is the serial port you tell your dialling software to use.
10. If you receive a 'modem not responding' type error when dialling, check the output of dmesg | tail. If there is a 'No stream' error, you likely have the wrong version of the driver.


Footnote 1: For cases where the ALSA15 driver compiles on a system that shipped with ALSA 1.0.16 or newer, follow these steps: Obtain the ALSA-driver 1.0.15 source tarball, and the ALSA-driver 1.0.16 source tarball. Extract each to a separate directory. Copy the contents of folder alsa-driver-1.0.15/alsa-kernel/pci/hda/ TO alsa-driver-1.0.16/alsa-kernel/pci/hda/ (overwrite existing files.) Now resume the above steps with this modified ALSA version, starting with the step explaining how to modify hda_codec.c. HOWTO by Bjorn Wielens, last updated July 29, 2008 With additions and suggestions by Jacques Goldberg and Marvin Stodolsky.

Bump.

I ran scanModem to id the chip (11c11040) but cannot check slitaz when dialed up on another os and wanted to ask before going further because slitaz might be newer than those 2008 instructions or different from generic linux or lack the compile tools (it looks like I do need to install linux-source first).

I think martian is for dsp (not softmodem) but 11c11040 is a softmodem.

Thank you.

Does slitaz alsa have the patch for modems?

Thank you.

No, Slitaz uses the default linux kernel source. So, it doesnot have any special patches for particular modem that have not been merged in the main kernel tree.

You can do this on your own as your instructions are quite detailed. I am assuming you haven't tried the Howto above yourself and are asking what are the equivalent instructions in slitaz:


tazpkg install linux-source

# Just open the file and edit manually OR

sed -i 's/hda_hwdep.h>/hda_hwdep.h> \n EXPORT_SYMBOL(snd_hda_codec_read); \n EXPORT_SYMBOL(snd_hda_codec_write); /' /usr/src/linux/sound/pci/hda/hda_codec.c

cd /usr/src/linux

make oldconfig

make modules

cp sound/pci/hda/snd_hda_intel.ko /lib/modules/`uname -r`/kernel/sound/pci/hda/snd-hda-intel.ko



We have ALSA modules version 1.0.16 or newer. Once you are root, just remove "sudo" from your above HowTo instructions; you should be able to follow the steps

BTW, is this hardware driver related to martian: http://martian.barrelsoutofbond.org

Reposting to put this in sequence after the clock change-

I ran scanModem to id the chip (11c11040) but cannot check slitaz when dialed up on another os and wanted to ask before going further because slitaz might be newer than those 2008 instructions or different from generic linux or lack the compile tools (it looks like I do need to install linux-source first).

I think martian is for dsp (not softmodem) but 11c11040 is a softmodem.

Thank you.

Make modules gave many errors including definition errors on files beginning with _k and make errors of Error 1 and Error 2.

How do I fix it?

Thank you.

Start from the beginning again and try to just do

cd /usr/src/linux

make oldconfig

make modules

You should not get any errors. Now, try to change the /usr/src/linux/sound/pci/hda/hda_codec.c as per your instructions. Then do it agian. If you face errors, there is something wrong with the instructions.

I got the same errors.

Maybe someone can spot a clue in some of these scanModem excerpts-


SliTaz is not yet providing pre-compiled drivers for WinModems

Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html

(4) For guidance on automation see http://linmodems.technion.ac.il/archive-fourth/msg03734.html
and the scripts in the slmodem-2.9.n/scripts folder/

For AC97/MC97 soft modems. Initiate software access through code sponsor IBM:
http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52698
Coding of support for has Not yet begun PCI soft modems with PCI_IDs 11c1:048?

For your current kernel, the fourth line should be
EXTRAVERSION =
where has been read from your current kernel version: 2.6.30.6-slitaz.
But it this does not match what is Actually in the Makefile,
then it represents a Different kernel-header set then that of your kernel!!!

3) Set the dependencies of the current kernel.
For SuSE 9.0 and later, there is a command which does the following steps
# make cloneconfig && make dep
Also browse the excellent README.SuSE in the kernel-source/ folder
For other Distros, the following steps are necessary, within the kernel-source/ folder
copy the kernel-config file to .config
and DO SPECIFY that " . "
But where is it? For many Distros, it will be the file like
/boot/config-2.6.30.6-slitaz
matching the output of:
uname -r
Or it may be the target of a symbolic link: /boot/config -->
So
cp /boot/config-2.6.30.6-slitaz .config
For SuSE 8.0 and earlier versions it is:
cp /boot/vmlinuz.config .config
PLEASE do not omit that "." in .config as it is crucially necessary.
View .config with a text browser.
It is simply a listing of the code components used in the kernel and its modules:
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
etc.

4) The .config file will be read during
# make oldconfig
which feeds its specifications through a process specifying
the SAME inter-dependencies previously used in compiling your kernel,
and may generate additional .dot-config files . They can be displayed with:
# ls -al

5) Though it may be redundant after "make mrproper", it will do no harm to:
make clean
5a) For the SuSe Linux versions 8.0 and previous , there will exist files:
/boot/vmlinuz.autoconf.h
/boot/vmlinuz.version.h
They MUST be copied as:
cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h
cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h

6) Now build kernel-headers with:
make dep
for 2.4.n kernels or for 2.6.n kernels
make bzImage
during which you can walk your dog, take a shower, have tea, etc.
7) Check for resultant FileNames.h with:
ls include/linux/
and
cat include/linux/version.h
to verify the version.

COMPILING the MODEM DRIVERS can now finally be done.
Unpack the compiler kit for your modem drivers,
cd into its folder, read any README or INSTALL files,
make clean
FINALLY, your modem drivers will compiled by a command like
make OR make ModuleName
or perhaps
make all
During this process, some of the kernel-header code with be joined
with the supplied modem specific code, and ModemDrivers.o will be produced.
Follow and further instructions in the modem code resource
to install the drivers, often with:
make install

Modem chipset detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1025:0133
IRQ=22
HDA=8086:284b
SOFT=8086:284b.HDA
HDAchipVendorID=11c1
CHIP=0x11c11040
CodecClass=14f1
IDENT=agrsm
Driver=agrsm

For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 1025:0133
Softmodem codec or chipset from diagnostics: 0x11c11040
from Archives:
The HDA card softmodem chip is 0x11c11040


Support type needed or chipset: agrsm


Writing DOCs/Intel.txt

The AgereSystems/LSI agrsm code supports compiling of a agrmodem + agrsm driver pair.
One resource site is http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
Thereat get the agrsm_howto.txt and one of the agrsm-tools packages.
The initial agrsm_howto.txt compiling steps are only cogent to modems with PCI IDs:
11c1:0620, 11c1:048c and 11c1:048f chips.
They use the agrsm-20090418.tar.gz package.
The agrsm-tools sets a useful symbolic link and a agrsm-test utlity

For AgereSystems/LSI with Vendor 11c1 chips hosted on High Definition Audio cards, there may be support
through the agrsm resources (providing an agrmodem + agrserial driver pair) as an alternative to usage
of the snd-hda-intel driver + slmodemd helper. For the 11c11040 modem chip, ONLY the agrsm code is competent.
Your Linux distro's dkms package should be first installed, as it directs the installation of modem
specific dkms-agrsm resources, and also directs auto-installation of new drivers upon kernel upgrades.

Currently, the dkms-agrsm code is NOT competent for 2.26.28 and later kernels.
A short term fix is to install linux-image + linux-headers packages for earlier kernels.
For detailed instructions for Ubuntu Jaunty with 2.6.28 kernels, see http://linmodems.technion.ac.il/bigarch/archive-nineth/msg01316.html

The primary dkms-agrsm resource site is http://linux.zsolttech.com/linmodem/agrsm/
whereat a few different packaging types are available. Debian type installers (supporting Ubuntu too)
are copied to http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ . Thereat the current package
is the dkms-agrsm_2.1.80-6_i386.deb is for Agere/LSI chipsets hosted on High Definition Audio cards.
Read the Modem/DOCs/Agrsm.txt for details.



Completed candidate modem analyses.

The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.4.1
and the compiler used in kernel assembly: 4.4.1



Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.30.6-slitaz/build

However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.


Compressed files at: /usr/src/linux-2.6.30.6.tar.bz2

For Debian and some related distributions, a package kernel-kbuild-2.6-30 may be needed to support driver compiling.


If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev

If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:

Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb


Checking pppd properties:
-r-xr-xr-x 1 root root 402208 Sep 22 04:17 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html

To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd

Checking settings of: /etc/ppp/options
lock

In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html

Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.

Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================

Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/mwave", GROUP="dialout"
Within /etc/modprobe.conf files:

Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

If I ever get these changes working, will the next slitaz upgrade break them?

Thank you.

What does this mean?

"For your current kernel, the fourth line should be EXTRAVERSION = where has been read from your current kernel version: 2.6.30.6-slitaz. But it this does not match what is Actually in the Makefile, then it represents a Different kernel-header set then that of your kernel!!!"

How do I check it?

Thank you.

@slicel: I am trying to cook some of the Winmodem packages (there are quite a few) as suggested by you. Wait for sometime. Let me see if I can cook it for you. Then, you can see my receipts and use them to cook other similar winmodem packages (if you are interested).

Slitaz 3 wvdialconf fails with a "Killed" message, a modem "busy" message, or no message (it hangs/freezes).

Something called softirqd (or similar name) runs.

I did the following before running wvdialconf.

I installed the packages for setserial, wvdial, and agr modem (edit- and linux dialup).

I modprobed agrmodem and agrserial.

I created a blank /etc/wvdial.conf.

I created symbolic links according to the next instructions.


1) Next load the drivers
sudo modprobe agrmodem
sudo modprobe agrserial
which should announce creation of /dev/ttyAGS3

2) It is convient to create symbolic links, which dialer utilities will follow,
to the real port /dev/ttyAGS3 .
sudo ln -s /dev/ttyAGS3 /dev/ttySAGR
sudo ln -s /dev/ttyAGS3 /dev/modem
Check with:
ls -l /dev/ttyAGS3 /dev/ttySAGR /dev/modem
whose output should include:
/dev/modem --> /dev/ttyAGS3
/dev/ttySAGR --> /dev/ttyAGS3

3) The first critical functial test is:
sudo wvdialconf /etc/wvdial.conf
which searches through potential ports for modem responses.
A success will end with a section like:
--------
ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.40
ttySAGR<*1>: Speed 4800: AT -- OK
ttySAGR<*1>: Speed 9600: AT -- OK
ttySAGR<*1>: Speed 19200: AT -- OK
ttySAGR<*1>: Speed 38400: AT -- OK
ttySAGR<*1>: Speed 57600: AT -- OK
ttySAGR<*1>: Speed 115200: AT -- OK
ttySAGR<*1>: Max speed is 115200; that should be safe.
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttySAGR.
Modem configuration written to /etc/wvdial.conf.
ttySAGR: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
--------
Then you can proceed to try a dialout (see below).

Bump for softmodem problem 2 years without a fix.

Bump for softmodem problem 2 years without a fix.

slicel: please, let us know what exactly is the problem?
1) all softmodem driver receipts (as far as I know) are in repos now
2) download package and modprobe your_module
3) use wvdial (wvdial is used in 3g-modem; can you read the part of 3g-modem in script /sbin/hwsetup and test).

Your debugging help is really appreciated.

1) I appreciate the progress in adding dialup packages.
2) I installed and modprobed the agr softmodem (and see ttyAGS3) as stated in a previous post (around 4/9 or 4/10 or so).
3) I ran wvdialconf and reported the 3 different errors ("Killed," "busy," or hangs) as stated in a previous post (around 4/9 or 4/10 or so).

I never would have thought to follow the 3g webpage because I do not think I have 3g.

As stated in a previous post (around 4/9 or 4/10 or so), I installed (including depends through package manager)-

setserial
linux-dialup
agrmodem
wvdial

Do I need to install the packages below from the 3g directions or were they installed as depends of the packages above (I am not on the distro now to check) or are they wrong for the agr modem?

hwsetup
ppp
rp-ppoe
3g-modem

I upgraded everything on slitaz 3 xvesa a couple weeks ago before installing the agrmodem.

It would help to know rather than guess what packages are needed for all modems (or all softmodems).

If I can find out if I am missing packages, I then will try the 3g directions to shut down eth, unless that is only necessary for 3g.

Thank you.

The ppp and rp-ppoe already were installed.

The hwsetup did not appear in tazpkg search.

I did not install 3g-modem yet because I am not sure from the documentation if that is needed for my agr modem.

Edit- I reread the 3g page and found the link to hwsetup named as setup but I am not sure from the documentation if that is needed for my agr modem.

Shutting down eth before running wvdial did not fix the problem.

slicel: I think my post confused you a bit. I meant that setting up linmodem should be similar to 3g-modem. hwsetup script is already in slitaz 3.0 (/sbin/hwsetup). The setup script supports 3g-modem but not normal modems. We can add the support to it if you can help.

 tazpkg search-pkgname agrmodem 

shows you need linmodem-agrsm package. You already have linux-dialup. Then, you modprobe the modules (agrmodem, agrserial ) or add them to rcS.conf.

You can then either use ppp, which comes with 3.0, or use wvdial.

Wvdial is easy to setup. hwsetup has a simple function to do that and also has wvdialbox gui, which you can use after installing wvdial and doing

 hwsetup wvdial 

What we need your help in is to fill in the missing pieces:
1) Example: your edited /etc/wvdial.conf file
2) Add to group like dialup ; other permissions checks (some files (say /dev/modem ) must have correct permissions)
3) Any other steps in between modprobing and wvdial (i doubt that)
4) Any step after wvdial (e.g. DNS settup if not done automatically)

Just read from line 638 in setup() function of hwsetup script about 3g-modem. Duplicate the commands.

There is also a gnome-ppp package here : http://people.slitaz.org/~jozee/packages/3G_modem/ . You can try it too.

I am sorry if I am confused or unclear.

I went to http://doc.slitaz.org/en:guides:dialup after you mentioned 3g but maybe I should not have. I am not sure what 3g is.

I mentioned that I installed and modprobed agrmodem as a short way of saying that I installed linmodem-agrsm-2.1.80-7mdv2009.0_2.6.30.6.tazpkg.

I am still reading the rest of your post.

Do I need an /etc/wvdial.conf with content (it is blank now) before I run hwsetup wvdial?

I already had installed the linmodem-agrsm. linux-dialup, and wvdial packages that you mentioned.

I already had modprobed agrmodem and agrserial by adding them to rcS.conf.

I already had added users to groups lp, dialout, tty, and others, plus I was working as root.

Meanwhile, I will look at /sbin/hwsetup.

Thank you.

What is udev at /sbin/hwsetup line 641?

I ran line 645-

# ls /dev/ttyUSB* /dev/ttyACM* /dev/modem

The first 2 are no such directory.

The output prints /dev/modem in blue but it looks like /dev/modem is a dead end in the hwsetup code.

Entering line 653's wvdialbox in the run box or in terminal says sh not found.

Entering line 659's long nameserver command in terminal says sh: nameserver: not found.

At that point my ethernet internet connection broke and I had to reboot.

I do not see anything else to try before the 3g section seems to end at line 666.

Thank you.

/dev/ttyUSB* and /dev/ttyACM* are devices corresponding to 3g devices, you don't have them. do you still have /dev/ttyAGS3 ? if yes create a symbolic link named /dev/modem pointing to /dev/ttyAGS3.

ln -s /dev/ttyAGS3 /dev/modem

then try

wvdialconf

and try to connect with

wvdial

if it does not work may you post the output of following commands:

cat /etc/wvdial.conf
cat /etc/group 

?

Ernia, thank you for the help.

I did not think that I had ttyUSB and ttyACM but I already had run the agere versions (as reported in this thread) before jozee suggested the hwsetup code so I was trying anything I could in the hwsetup code.

Yes, I still have /dev/ttyAGS3 and I still have the symbolic links /dev/modem and /dev/ttySAGR that I created last week and reported earlier in this thread.

As stated in the other posts (particulary around 4/9 and 4/16)-

I installed, modprobed, and symbolic-linked and the failure occurred at wvdialconf, Step 3 of the post with 1-2-3 steps (around 4/9 or 4/10 or so).

The failure occurred at wvdialconf with the errors I reported so /etc/wvdial.conf is still blank.

I worked as root but also added users to groups lp, dialout, tty, and others. The full list is-

root:x:0:
lp:x:10:slicel
audio:x:20:slicel
nogroup:x:99:
www:x:80:
messagebus:x:25:
cdrom:x:1:slicel
dialout:x:2:slicel
disk:x:3:slicel
floppy:x:4:slicel
kmem:x:5:
tape:x:6:
tty:x:7:slicel
video:x:8:slicel
haldaemon:x:26:slicel
slicel:x:1000:
camera:x:9:slicel
scanner:x:11:slicel


Thank you.

sorry if i miss something from your post but you are really verbose and i i'm making a little of confusion between what you have done and what not.
i think that you should lack only /etc/wvdial.conf. if you have your modem working in another distro you could copy /etc/wvdial.conf from the other distro to slitaz. i've found this one if you want to try:

 [Dialer defaults]
# Lines begining with # are comments.
# wvdial will look for this file at  /etc/wvdial.conf
#  or  /home/LoginName/.wvdial.rc
Baud = 57600
Modem = /dev/ttySAGR
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
#  Lack of dialtone acquisition can be due to low line voltage,
#    a common problem in Italy.
#  Try inserting a "dial without waiting": X3
#  Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
#  In case of connection instabilities, specify a lower frequency:
#  Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2  +MS=34

## Outside the USA, a country setting may be needed
# Init3 = AT+CGI=hexadecimal_country_code

ISDN = 0
Modem Type = Analog Modem
Phone =  Dialout_phone_number
# if going through a switch board, a perhaps necessary pause can produced with a comma:
# Phone = 1,Dialout_phone_number
Username = LoginName
# if Internet Provider is MSN.net, use under Linux:   MSN/LoginName
Password = YourPassWord

## If CONNECT is achieved but browsing fails, try activating the following line
# Auto DNS = yes
##    To make a logfile wvdial.out
# wvdial 2>&1 | tee wvdial.out
# #  For some Internet providers, the following line is necessary
# Stupid Mode = yes
##  for other wvdial  options, do "man wvdial" or see the documentation in
##    /usr/share/doc/wvdial/
## End wvdial.conf

modify username and password, then try to wvdial, let me know what happens.
if connection starts but you can't browse post relative lines of /var/log/messages and the content of /etc/resolv.conf and output of route command.

This thread is verbose because I posted information from around the internet after a long time of not seeing any answers in the slitaz site or forum.

Yes, my intent from 4/9 was about /etc/wvdial.conf because the command wvdialconf failed.

I will take a look at your suggestion.

Thank you.

Wvdial gives another Killed message (after pasting ernia's code to /etc/wvdialconf).

Wvdialconf gave the Killed message that is the same as in the quote here.

Does this make sense to anyone?

Thank you.

http://old.nabble.com/results-td27386582.html

Modem Port Scan<*1>: S0   S1   S2   S3   Killed
-------
This establishes that drivers loading is OK.
The current problem is modem hardware detection even with the drivers loaded.

Since your hardware under ALSA analysis is:
-- 
Codec: LSI Si3054
Vendor Id: 0x11c13026

there should now be tested the slmodemd activation approach.
Use the  SLMODEMD_gcc4.4_alsa1.0.21.tar.gz previously sent.
With this package in your personal folder:
$ ls SL*
should show the package.  Then
$ tar zxf SLM*.tar.gz
$ ls -d SL*
to display the new folder.

Move in with:
$ cd  SLMODEMD_gcc4.4_alsa1.0.21
$ ls
to list the files, which you should browse. There is a file setup. Run with
$ sudo ./setup
This just copies slmodemd to /usr/sbin/slmodemd
and does not have to be repeated.

Thereafter when you open a console, it will suffice to:
$ sudo slmodemd -c USA --alsa modem:1
should activate the modem with annoucement of:
    /dev/ttySL0  ->  /dev/pts/N

Try this approach and report back.

MarvS

On Sat, Jan 30, 2010 at 7:51 AM, Jin  wrote:
> Linmodems
>
> J
>
> 

Bump.

I am not shure, if it is the correct driver, because there are differnt ones...

http://linmodems.technion.ac.il/packages/ltmodem/11c11040/

run as root:

wvdialconf /etc/wvdial.conf

which searches through potential ports for modem responses.
A success will end with a section like:
--------
ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.40
ttySAGR<*1>: Speed 4800: AT -- OK
ttySAGR<*1>: Speed 9600: AT -- OK
ttySAGR<*1>: Speed 19200: AT -- OK
ttySAGR<*1>: Speed 38400: AT -- OK
ttySAGR<*1>: Speed 57600: AT -- OK
ttySAGR<*1>: Speed 115200: AT -- OK
ttySAGR<*1>: Max speed is 115200; that should be safe.
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Kultex, thank you, that is the site from which I obtained most of the information on this thread and looks like the stage of the previous post (around 4/9 or 4/10 or so).

One site said to try to boot acpi=noacpi. I tried acpi=off because that version of the command is on the slitaz forum but it did not seem to help.

Another site said to disable alsa power saving-

http://eeek.borgchat.net/lists/linmodem/msg10573.html

I did that (intended for ubuntu) but it did not seem to help.

Is there a slitaz version of either of those ideas?

Edit- I ran agrsm-test and, even though I installed the driver package through slitaz package manager, the test said driver not found for boot kernel 2.6.30.6-slitaz.

Thank you.

sorry if I ask, but do you really need this analog modem? From anciant times (I think I did not use a analog modem for 10 years) I remeber, that this internal winmodems always caused troubles in linux and I all the times used external ones (I still have 3 elsas und 3 US-robottics in my oldies collection). My Portege R100 has also one of theese bustards, but in most linux OS it is not supported any more. The only one I think was puppy, where it showed up on lsmod.
And if you really need one and you dont find one of the old external at friends, I would recomand you to buy one zoom usb modem at ebay for some € or $

http://shop.ebay.com/i.html?_nkw=modem+analog+zoom+usb&_sacat=0&_trksid=p3286.m270.l1313&_sop=15&_dmpt=PCC_Modems&_odkw=modem+analog&_osacat=0&bkBtn=

they are small and run normally fine with usbserial driver - see

http://ahmedsharifalvi.wordpress.com/2009/02/28/configuring-citycell-zoom-usb-modem-on-fedora-linux/

In my opinion, its wasted time to continue working

if you really want to continue, I found here, that puppy supports it out of the box (search for agere in the post)

http://www.tuxradar.com/content/whats-best-lightweight-linux-distro

so run puppy - try it out, if it works (perhaps the modem is broken) see which driver is used ....

slicel: Your posts have been very confusing (to me at least). I still don't understand where exactly is the problem. Can we do step by step, please (just one step at a time)?

 modprobe agrmodem && modprobe agrserial 

Please confirm if modem is found or not : /dev/tty*

Kultex-

I need dialup. The hardware works because it works on windows. My last link says the modem's wvdialconf worked on linux (I think ubuntu). Thank you for the link that it works on puppy too. I will take a look.

Jozee-

Yes. The post from 4/9 or 4/10 or so (vanilla confusingly changes the display date) accurately states that the failure happened at wvdialconf, corresponding to step 3 of these instructions reported in that earlier post-

1) Next load the drivers
sudo modprobe agrmodem
sudo modprobe agrserial
which should announce creation of /dev/ttyAGS3

2) It is convient to create symbolic links, which dialer utilities will follow,
to the real port /dev/ttyAGS3 .
sudo ln -s /dev/ttyAGS3 /dev/ttySAGR
sudo ln -s /dev/ttyAGS3 /dev/modem
Check with:
ls -l /dev/ttyAGS3 /dev/ttySAGR /dev/modem
whose output should include:
/dev/modem --> /dev/ttyAGS3
/dev/ttySAGR --> /dev/ttyAGS3

3) The first critical functial test is:
sudo wvdialconf /etc/wvdial.conf
which searches through potential ports for modem responses.
A success will end with a section like:
--------
ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.40
ttySAGR<*1>: Speed 4800: AT -- OK
ttySAGR<*1>: Speed 9600: AT -- OK
ttySAGR<*1>: Speed 19200: AT -- OK
ttySAGR<*1>: Speed 38400: AT -- OK
ttySAGR<*1>: Speed 57600: AT -- OK
ttySAGR<*1>: Speed 115200: AT -- OK
ttySAGR<*1>: Max speed is 115200; that should be safe.
ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttySAGR.
Modem configuration written to /etc/wvdial.conf.
ttySAGR: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
--------
Then you can proceed to try a dialout (see below).

Instead of the success message, I get one of the 3 errors itemized in earlier posts this month, the first attempt in any session giving the "Killed" message that I reported, quoted, and linked.

Attempts to set acpi or alsa power_saving did not help but maybe slitaz looks for alsa settings differently.

The agrsm-test said driver not found for boot kernel 2.6.30.6-slitaz.

Modinfo agrmodem and agrserial say "vermagic: 2.6.30.6-slitaz SMP mod_unload 386."

Modinfo agrmodem has a depends of "snd" but I see no snd package in repos. I have libsndfile and libsndfile-dev installed. (Edit- I see snd in lsmod and agrmodem listed as a user of snd.)

Edit- I installed linux headers and linux source but they did not help. One depends was gcc, which the "Killed" link mentions, but it did not help.

Tazpg listed linux-source as 1mb but added about 500mb (half a gb) to my hd, a dangerous difference.


Thank you.

Puppy failed last year and puppy 4.3.1 failed today. One gui window says no modem detected while a help window says two modems detected and something for them loaded but the wvdial.conf looks generic as if wvdialconf did not run.

The ttyAGS3 has no permissions to execute and changing to execute is reset to no execute after reboot. Attempting wvdialconf with ttyAGS3 set to execute did not change anything.

Running wvdialconf as root gives a "Killed" message or freezes but running wvdialconf as a non-root user gives a message including-

ttySAGR: Device or resource busy
Modem Port Scan<*1>: SAGR

Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Edit- FYI- http://murga-linux.com/puppy/viewtopic.php?search_id=255019890&t=40234

How do I fix it?

Thank you.

Bump.

Bump.

Why does lspci not show my agere while tim's lspci shows his agere?

http://theseahawk.webs.com/pics/screen2.png

He could have a different agere or a different slitaz. I have slitaz 3 xvesa. He might have slitaz 3 xorg. I asked but he did not say what agere he had. He only said, "I'm using the Slitaz 3.0 Stable, (although when I boot it says cooking, I know I downloaded stable)."

http://forum.slitaz.org/index.php/discussion/1078/solved-linksys-wireless-card-help/#Item_16

How do I check and set the modem to hang up?

http://www.linux.org/docs/ldp/howto/Modem-HOWTO-18.html#minicom_test

Thank you.

Edit- slitaz minicom failed immediately after start with a "Killed" message.

As root, before making symbolic links, wvdialconf says modem not found. After making symbolic links as reported in this thread, wvdialconf says "Killed."

Minicom sometimes gets killed and sometimes does not. In both cases it loads defaults. When it works (is not Killed), how can I check, hang up, or reset my modem?

How do I prevent Killed?

Thank you.

I do not see "EXPORT_SYMBOL(" in the codec.

Does slitaz 3 have the alsa patch?

Thank you.

#  For the 11c11040 case you must determine your ALSA drivers version. You MUST be using the version of ALSA that came with your current kernel. If you have since upgraded to a newer version of the ALSA modules, you will need to revert to the old version (or if this is not possible, upgrade your kernel.) To find your ALSA module version, issue in a terminal the command:
cat /proc/asound/version

with a typical output like:
Advanced Linux Sound Architecture Driver Version 1.0.16.
Compiled on Jun 18 2008 for kernel 2.6.24-19-generic (SMP).
wherein the ALSA driver version is the 1.0.16 .
Remember this number, as other steps in this HOWTO depend on it!

# Patch your sound driver file hda_codec.cto for export symbols needed by the drivers:

   1. Use your favourite PLAIN TEXT editor, such as vi or gedit, and with root permission. This file is typically located at /usr/src/linux/sound/pci/hda/hda_codec.c
   2. Add the lines EXPORT_SYMBOL(snd_hda_codec_read); and EXPORT_SYMBOL(snd_hda_codec_write); to the file, after the list of '#include' statements in the beginning.
   3. Save the file. 

# Rebuild and install the new modules:

   1. In /usr/src/linux, run the following commands:
   2. sudo make oldconfig
   3. sudo make modules NOTE: This command will take a while, and give lots of ouptut. Watch for any errors when it finishes. (Warnings are okay).
   4. Copy the newly built module to your modules directory: sudo cp sound/pci/hda/snd_hda_intel.ko /lib/modules/`uname -r`/kernel/sound/pci/hda/snd-hda-intel.ko NOTE: Some systems (e.g. Ubuntu) deviate form this as the module's path. When in doubt, use a file search utility to search for an existing snd-hda-intel.ko file in /lib/modules/ and replace it with your patched version.
   5. Restart your computer to activate the new module.
   6. Verify that your sound still works.

# Obtain the correct agrsm driver from the linmodems 11c11040 pit. The file you get depends on the ALSA version you found in step 1:

    * If your ALSA modules version is 1.0.15 or older, get the file agrsm-HDA-20080721-ALSA15.tar.bz2
    * If you have ALSA modules version 1.0.16 or newer, get the file agrsm-HDA-20080721.tar.bz2