Re: Problem with soundmodem on Eee PC

Re: Problem with soundmodem on Eee PC

[Christof Bodner]

Hi, 

I asked a similar question some time ago.
http://markmail.org/message/d3oe24nro6245eac

But up 'til now I did not solve the problem...

73 de OE8BCK, Christof

-- 
             (0-0)
---------oOO--(_)--OOo-----------------------------------------------
 Christof Bodner <Christof.Bodner@gmx.net>
   Linux - Life is too short for reboots
         - First they ignore you. Then they laugh at you. Then they
           fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: mailto:Christof.Bodner@gmx.net
Tel.:  +43-650-7215383
ICQ:   22085157
QTH:   JN76DO
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net)
Fingerprint 5222 4DEA 773A 60B3 22F9  D244 15EF 6645 B15D A60F
---------------------------------------------------------------------

Problem with soundmodem on Eee PC

[Julian Moss]

Is this the right place to ask about the soundmodem AX25 soundcard driver?

I am trying to get APRS running on an Eee PC Surf 2G which has had
Eeebuntu (based on Ubuntu 9.0) installed in place of the original
Xandros.

The version of soundmodem I installed from the repository would not
decode anything. In the diagnostic scope display I saw straight lines
in the trace which you can see in my blog posting here:
http://www.g4ilo.com/2009/09/eee-im-getting-nowhere.html .

I found a posting in a list here
http://osdir.com/ml/linux.hams/2005-10/msg00058.html which suggested
that this is caused by soundmodem opening the sound card at an
unsupported sample rate of 9600. The post included a hack to make it
use 11025.

I downloaded the source code tar.gz from here
http://www.baycom.org/~tom/ham/soundmodem/ and compiled it. I noticed
that the diagnostic scope display in my version froze after a couple
of seconds. I applied the changes given in the above posting, though I
noted that the line numbers in the config app code were slightly
different from those given.

Although the diagnostic is unusable the modified soundmodem itself
seemed to work and decodes APRS received from my radio. However I have
noticed that after some fairly short period of time, perhaps an hour
or so, nothing is decoded and I have to restart the computer to get it
going again. This obviously makes it unusable in practise.

I am at a loss what to try next, since the source code is too complex
for me to try to debug it. Has anyone got this working reliably on an
Eee PC?
-- 
Julian, G4ILO
G4ILO's Shack: www.g4ilo.com

Re: Problem with soundmodem on Eee PC

[Alan Crosswell]

Julian,

Soundmodemconfig's diagnostic has a known issue that the scope will
sometimes freeze even though the modem is running fine.

Please send your soundmodem.conf XML file that is typically saved in
/etc/ax25/ which will help diagnose your issue.  You can use
"plughw:0,0" for example which is a software shim that will compensate
for a hardware sampling rate that doesn't match.  What kind of sound
hardware are you using?  motherboard sound card, PCI, USB?   Also, what
is the kernel release?  Do a:

uname -a
dmesg
lspci

If you look in the dmesg output or in /var/log/messages (name varies
depending on the linux distro you are using) you might see some error
messages that correlate with the soundmodem failing.

Just to assure you, once you get these issues with your sound hardware
diagnosed, soundmodem itself will run for months or years with no
problems.  I have several soundmodem-based digipeaters running that
would have been up for several years except for the occasional lose of
mains power.





Julian Moss wrote:
> Is this the right place to ask about the soundmodem AX25 soundcard driver?
>
> I am trying to get APRS running on an Eee PC Surf 2G which has had
> Eeebuntu (based on Ubuntu 9.0) installed in place of the original
> Xandros.
>
> The version of soundmodem I installed from the repository would not
> decode anything. In the diagnostic scope display I saw straight lines
> in the trace which you can see in my blog posting here:
> http://www.g4ilo.com/2009/09/eee-im-getting-nowhere.html .
>
> I found a posting in a list here
> http://osdir.com/ml/linux.hams/2005-10/msg00058.html which suggested
> that this is caused by soundmodem opening the sound card at an
> unsupported sample rate of 9600. The post included a hack to make it
> use 11025.
>
> I downloaded the source code tar.gz from here
> http://www.baycom.org/~tom/ham/soundmodem/ and compiled it. I noticed
> that the diagnostic scope display in my version froze after a couple
> of seconds. I applied the changes given in the above posting, though I
> noted that the line numbers in the config app code were slightly
> different from those given.
>
> Although the diagnostic is unusable the modified soundmodem itself
> seemed to work and decodes APRS received from my radio. However I have
> noticed that after some fairly short period of time, perhaps an hour
> or so, nothing is decoded and I have to restart the computer to get it
> going again. This obviously makes it unusable in practise.
>
> I am at a loss what to try next, since the source code is too complex
> for me to try to debug it. Has anyone got this working reliably on an
> Eee PC?
>   

Re: Problem with soundmodem on Eee PC

[J. Lance Cotton]

On 09/09/2009 05:32 PM, Julian Moss wrote:
> I found a posting in a list here
> http://osdir.com/ml/linux.hams/2005-10/msg00058.html which suggested
> that this is caused by soundmodem opening the sound card at an
> unsupported sample rate of 9600. The post included a hack to make it
> use 11025.

I was the one who posted that original problem. My solutions were:

1) Use a different soundcard that supported the requested sample rate.

2) Use the ALSA sound system instead of the OSS system, which I think is 
now standard on Ubuntu and most other 2.6 Linuxes. I had been sticking 
with OSS for a while because I found the commercial (paid) OSS system to 
be very stable on the old SuSE distro I was running. I now use Ubuntu 
and the ALSA system will re-sample whatever audio comes in from whatever 
soundcard to give the software what it asked for.

Works well.

-Lance

-- 
J. Lance Cotton, KJ5O
joe@lightningflash.net
http://kj5o.lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat 
the cookies.

Re: Problem with soundmodem on Eee PC

[Dave Platt]

> 2) Use the ALSA sound system instead of the OSS system, which I think is 
> now standard on Ubuntu and most other 2.6 Linuxes. I had been sticking 
> with OSS for a while because I found the commercial (paid) OSS system to 
> be very stable on the old SuSE distro I was running. I now use Ubuntu 
> and the ALSA system will re-sample whatever audio comes in from whatever 
> soundcard to give the software what it asked for.

That's true, *if* you specify the "plughw:" ALSA device as the one
to use.  This utilizes a library plugin which will perform sample-rate
and sample-depth conversion on the fly, so that the application will
get the rate it expects.

If you use the direct "hw:" device specification, the application
is restricted to only those exact sample rates / widths / formats
that the hardware supports.  If the app tries to request an unsupported
configuration, the attempt to open the device will fail and the
app won't get any audio in/out over the channel.

The current version of the soundmodem configurator has "plughw:"
available in the menu of device choices for ALSA.  It also has
some fixes to audio-channel management that are needed with some
ALSA devices (e.g. some USB audio converters).  Older versions
of the soundmodem app may not work well with some devices when
using ALSA.

I have a feeling that some of the soundmodem utility code
(e.g. the scope) may need some of the same "restart cleanly
after an error" fixes that the main modem code required, in
order to work properly with ALSA.

Re: Problem with soundmodem on Eee PC

[Christof Bodner]

Hi,

Soundmodem stopped to work in Ubuntu 8.04, in 7.10 it works fine with
OSS. Today I tried it again with ALSA plughw: and it stopped after
receiving the first packet. That was reproduceable and occured in the
soundmodemconfig modem diagnostic as well as in the soundmodem itself.

grx,
Christof

Am Samstag, den 12.09.2009, 16:12 -0700 schrieb Dave Platt:
> > 2) Use the ALSA sound system instead of the OSS system, which I think is 
> > now standard on Ubuntu and most other 2.6 Linuxes. I had been sticking 
> > with OSS for a while because I found the commercial (paid) OSS system to 
> > be very stable on the old SuSE distro I was running. I now use Ubuntu 
> > and the ALSA system will re-sample whatever audio comes in from whatever 
> > soundcard to give the software what it asked for.
> 
> That's true, *if* you specify the "plughw:" ALSA device as the one
> to use.  This utilizes a library plugin which will perform sample-rate
> and sample-depth conversion on the fly, so that the application will
> get the rate it expects.
> 
> If you use the direct "hw:" device specification, the application
> is restricted to only those exact sample rates / widths / formats
> that the hardware supports.  If the app tries to request an unsupported
> configuration, the attempt to open the device will fail and the
> app won't get any audio in/out over the channel.
> 
> The current version of the soundmodem configurator has "plughw:"
> available in the menu of device choices for ALSA.  It also has
> some fixes to audio-channel management that are needed with some
> ALSA devices (e.g. some USB audio converters).  Older versions
> of the soundmodem app may not work well with some devices when
> using ALSA.
> 
> I have a feeling that some of the soundmodem utility code
> (e.g. the scope) may need some of the same "restart cleanly
> after an error" fixes that the main modem code required, in
> order to work properly with ALSA.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
             (0-0)
---------oOO--(_)--OOo-----------------------------------------------
 Christof Bodner <Christof.Bodner@gmx.net>
   Linux - Life is too short for reboots
         - First they ignore you. Then they laugh at you. Then they
           fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: mailto:Christof.Bodner@gmx.net
Tel.:  +43-650-7215383
ICQ:   22085157
QTH:   JN76DO
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net)
Fingerprint 5222 4DEA 773A 60B3 22F9  D244 15EF 6645 B15D A60F
---------------------------------------------------------------------

Re: Problem with soundmodem on Eee PC

[Dave Platt]

Christof Bodner wrote:
> Hi,
> 
> Soundmodem stopped to work in Ubuntu 8.04, in 7.10 it works fine with
> OSS. Today I tried it again with ALSA plughw: and it stopped after
> receiving the first packet. That was reproduceable and occured in the
> soundmodemconfig modem diagnostic as well as in the soundmodem itself.

Two questions:

- Which version are you using?

- If you run it from the command line, are there any diagnostic
   or error messages printed when it receives or transmits?

Re: Problem with soundmodem on Eee PC

[Christof Bodner]

Hi Dave,

I am using the soundmodem provided by the Ubuntu team
$ dpkg-query -W soundmodem
soundmodem	0.10-6

This is the output of soundmodemconfig:

on_configtree_selection_changed
selection: cfg: default  chan: Channel 0
Modulator: afsk Demodulator: afsk
Modulator: parameter bps value 1200
Modulator: parameter f0 value 1200
Modulator: parameter f1 value 2200
Modulator: parameter diffenc value 1
Demodulator: parameter bps value 1200
Demodulator: parameter f0 value 1200
Demodulator: parameter f1 value 2200
Demodulator: parameter diffdec value 1
Minimum sampling rate: 9600
Audio IO: type alsa
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
Real sampling rate: 9600
Joining TxThread
Joining RxThread
Releasing IO
Modulator: afsk Demodulator: afsk
Modulator: parameter bps value 1200
Modulator: parameter f0 value 1200
Modulator: parameter f1 value 2200
Modulator: parameter diffenc value 1
Demodulator: parameter bps value 1200
Demodulator: parameter f0 value 1200
Demodulator: parameter f1 value 2200
Demodulator: parameter diffdec value 1
Minimum sampling rate: 9600
Audio IO: type alsa
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
Real sampling rate: 9600
delete event
on_configtree_selection_changed
Modulator mode: afsk
Demodulator mode: afsk
Packet IO mode: MKISS
Joining TxThread
Joining RxThread
Releasing IO
selection: cfg: -  chan: -
podex@rosi-atom:~$ sudo soundmodemconfig -v 4
on_configtree_selection_changed
selection: cfg: default  chan: Channel 0
Modulator: afsk Demodulator: afsk
Modulator: parameter bps value 1200
Modulator: parameter f0 value 1200
Modulator: parameter f1 value 2200
Modulator: parameter diffenc value 1
Demodulator: parameter bps value 1200
Demodulator: parameter f0 value 1200
Demodulator: parameter f1 value 2200
Demodulator: parameter diffdec value 1
Minimum sampling rate: 9600
Audio IO: type alsa
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
Real sampling rate: 9600
Joining TxThread
Joining RxThread
Releasing IO
Modulator: afsk Demodulator: afsk
Modulator: parameter bps value 1200
Modulator: parameter f0 value 1200
Modulator: parameter f1 value 2200
Modulator: parameter diffenc value 1
Demodulator: parameter bps value 1200
Demodulator: parameter f0 value 1200
Demodulator: parameter f1 value 2200
Demodulator: parameter diffdec value 1
Minimum sampling rate: 9600
Audio IO: type alsa
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
Real sampling rate: 9600
Joining TxThread
Joining RxThread
Releasing IO
Modulator: afsk Demodulator: afsk
Modulator: parameter bps value 1200
Modulator: parameter f0 value 1200
Modulator: parameter f1 value 2200
Modulator: parameter diffenc value 1
Demodulator: parameter bps value 1200
Demodulator: parameter f0 value 1200
Demodulator: parameter f1 value 2200
Demodulator: parameter diffdec value 1
Minimum sampling rate: 9600
Audio IO: type alsa
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
Real sampling rate: 9600
Joining TxThread
Joining RxThread
Releasing IO
delete event
on_configtree_selection_changed
Modulator mode: afsk
Demodulator mode: afsk
Packet IO mode: MKISS
selection: cfg: -  chan: -

I started the oscilloscope twice and the spectrum analyzer once. The
display got stuck after the first packet arrived. The output of
soundmodem itself is

$ sudo soundmodem -v 4
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: unknown node "text"
sm[20838]: mkiss: ifname sm0 mtu 256 hwaddr OE8BCK-2 ipaddr 10.0.0.1
netmask 255.255.255.0 broadcast 10.0.0.255
sm[20838]: unknown node "text"
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
ALSA: Using sample rate 9600, sample format 2, significant bits 16,
buffer size 3276, period size 102
sm[20838]: unknown kiss packet: 0x80 0xa2
sm[20838]: unknown kiss packet: 0x20 0xa2

$ dmesg
[45458.558881] mkiss: AX.25 Multikiss, Hans Albas PE1AYX
[45458.562150] mkiss: ax0: crc mode is auto.
[45458.576058] mkiss: sm0: Trying crc-smack
[45458.668378] mkiss: sm0: Trying crc-flexnet
[45591.993672] mkiss: ax0: crc mode is auto.
[45592.005084] mkiss: sm0: Trying crc-smack
[45592.099000] mkiss: sm0: Trying crc-flexnet

It decoded not a single packet, but transmitting was a little bit
strange. No, I did not transmit to the ether, only to my loudspeakers.
It seemed that there was a holdup, as there were no packets for some
secondes and then came a lot of them. But it could also be sent this way
from the ahavi and cups daemons which produce them. It did not change
the behaviour after restarting having unloaded the ax25 and mkiss
modules. 

73 de OE8BCK,
Christof

Am Sonntag, den 13.09.2009, 11:26 -0700 schrieb Dave Platt:
> Christof Bodner wrote:
> > Hi,
> > 
> > Soundmodem stopped to work in Ubuntu 8.04, in 7.10 it works fine with
> > OSS. Today I tried it again with ALSA plughw: and it stopped after
> > receiving the first packet. That was reproduceable and occured in the
> > soundmodemconfig modem diagnostic as well as in the soundmodem itself.
> 
> Two questions:
> 
> - Which version are you using?
> 
> - If you run it from the command line, are there any diagnostic
>    or error messages printed when it receives or transmits?
-- 
             (0-0)
---------oOO--(_)--OOo-----------------------------------------------
 Christof Bodner <Christof.Bodner@gmx.net>
   Linux - Life is too short for reboots
         - First they ignore you. Then they laugh at you. Then they
           fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: mailto:Christof.Bodner@gmx.net
Tel.:  +43-650-7215383
ICQ:   22085157
QTH:   JN76DO
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net)
Fingerprint 5222 4DEA 773A 60B3 22F9  D244 15EF 6645 B15D A60F
---------------------------------------------------------------------

Re: Problem with soundmodem on Eee PC

[David A. Ranch]

The new version of Ubuntu switched sound systems to PulseAudio:

http://www.ubuntu.com/testing/804rc

I've heard other reports about issues with soundmodem and Pulse.  I
would recommend to try to re-compile soundmodem from sources.  The
current sources version is 0.14.  If that doesn't help, I'd recommend
you back down to less of a bleeding edge distro.  I chose the exact
opposite approach and have everything running on Centos 5.3 but it took
a lot of work.

--David


Christof Bodner wrote:
> Hi Dave,
> 
> I am using the soundmodem provided by the Ubuntu team
> $ dpkg-query -W soundmodem
> soundmodem	0.10-6
> 
> This is the output of soundmodemconfig:
> 
> on_configtree_selection_changed
> selection: cfg: default  chan: Channel 0
> Modulator: afsk Demodulator: afsk
> Modulator: parameter bps value 1200
> Modulator: parameter f0 value 1200
> Modulator: parameter f1 value 2200
> Modulator: parameter diffenc value 1
> Demodulator: parameter bps value 1200
> Demodulator: parameter f0 value 1200
> Demodulator: parameter f1 value 2200
> Demodulator: parameter diffdec value 1
> Minimum sampling rate: 9600
> Audio IO: type alsa
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> Real sampling rate: 9600
> Joining TxThread
> Joining RxThread
> Releasing IO
> Modulator: afsk Demodulator: afsk
> Modulator: parameter bps value 1200
> Modulator: parameter f0 value 1200
> Modulator: parameter f1 value 2200
> Modulator: parameter diffenc value 1
> Demodulator: parameter bps value 1200
> Demodulator: parameter f0 value 1200
> Demodulator: parameter f1 value 2200
> Demodulator: parameter diffdec value 1
> Minimum sampling rate: 9600
> Audio IO: type alsa
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> Real sampling rate: 9600
> delete event
> on_configtree_selection_changed
> Modulator mode: afsk
> Demodulator mode: afsk
> Packet IO mode: MKISS
> Joining TxThread
> Joining RxThread
> Releasing IO
> selection: cfg: -  chan: -
> podex@rosi-atom:~$ sudo soundmodemconfig -v 4
> on_configtree_selection_changed
> selection: cfg: default  chan: Channel 0
> Modulator: afsk Demodulator: afsk
> Modulator: parameter bps value 1200
> Modulator: parameter f0 value 1200
> Modulator: parameter f1 value 2200
> Modulator: parameter diffenc value 1
> Demodulator: parameter bps value 1200
> Demodulator: parameter f0 value 1200
> Demodulator: parameter f1 value 2200
> Demodulator: parameter diffdec value 1
> Minimum sampling rate: 9600
> Audio IO: type alsa
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> Real sampling rate: 9600
> Joining TxThread
> Joining RxThread
> Releasing IO
> Modulator: afsk Demodulator: afsk
> Modulator: parameter bps value 1200
> Modulator: parameter f0 value 1200
> Modulator: parameter f1 value 2200
> Modulator: parameter diffenc value 1
> Demodulator: parameter bps value 1200
> Demodulator: parameter f0 value 1200
> Demodulator: parameter f1 value 2200
> Demodulator: parameter diffdec value 1
> Minimum sampling rate: 9600
> Audio IO: type alsa
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> Real sampling rate: 9600
> Joining TxThread
> Joining RxThread
> Releasing IO
> Modulator: afsk Demodulator: afsk
> Modulator: parameter bps value 1200
> Modulator: parameter f0 value 1200
> Modulator: parameter f1 value 2200
> Modulator: parameter diffenc value 1
> Demodulator: parameter bps value 1200
> Demodulator: parameter f0 value 1200
> Demodulator: parameter f1 value 2200
> Demodulator: parameter diffdec value 1
> Minimum sampling rate: 9600
> Audio IO: type alsa
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> Real sampling rate: 9600
> Joining TxThread
> Joining RxThread
> Releasing IO
> delete event
> on_configtree_selection_changed
> Modulator mode: afsk
> Demodulator mode: afsk
> Packet IO mode: MKISS
> selection: cfg: -  chan: -
> 
> I started the oscilloscope twice and the spectrum analyzer once. The
> display got stuck after the first packet arrived. The output of
> soundmodem itself is
> 
> $ sudo soundmodem -v 4
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: unknown node "text"
> sm[20838]: mkiss: ifname sm0 mtu 256 hwaddr OE8BCK-2 ipaddr 10.0.0.1
> netmask 255.255.255.0 broadcast 10.0.0.255
> sm[20838]: unknown node "text"
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
> buffer size 3276, period size 102
> sm[20838]: unknown kiss packet: 0x80 0xa2
> sm[20838]: unknown kiss packet: 0x20 0xa2
> 
> $ dmesg
> [45458.558881] mkiss: AX.25 Multikiss, Hans Albas PE1AYX
> [45458.562150] mkiss: ax0: crc mode is auto.
> [45458.576058] mkiss: sm0: Trying crc-smack
> [45458.668378] mkiss: sm0: Trying crc-flexnet
> [45591.993672] mkiss: ax0: crc mode is auto.
> [45592.005084] mkiss: sm0: Trying crc-smack
> [45592.099000] mkiss: sm0: Trying crc-flexnet
> 
> It decoded not a single packet, but transmitting was a little bit
> strange. No, I did not transmit to the ether, only to my loudspeakers.
> It seemed that there was a holdup, as there were no packets for some
> secondes and then came a lot of them. But it could also be sent this way
> from the ahavi and cups daemons which produce them. It did not change
> the behaviour after restarting having unloaded the ax25 and mkiss
> modules. 
> 
> 73 de OE8BCK,
> Christof
> 
> Am Sonntag, den 13.09.2009, 11:26 -0700 schrieb Dave Platt:
>> Christof Bodner wrote:
>>> Hi,
>>>
>>> Soundmodem stopped to work in Ubuntu 8.04, in 7.10 it works fine with
>>> OSS. Today I tried it again with ALSA plughw: and it stopped after
>>> receiving the first packet. That was reproduceable and occured in the
>>> soundmodemconfig modem diagnostic as well as in the soundmodem itself.
>> Two questions:
>>
>> - Which version are you using?
>>
>> - If you run it from the command line, are there any diagnostic
>>    or error messages printed when it receives or transmits?

Re: Problem with soundmodem on Eee PC

[Alan Crosswell]

I had pulse problems on Fedora which I solved by removing the libalsa  
pulse plugin package. However, I am currently running FC11 with pulse  
with no problems.  I think a newer version may have solved it.
/a
PS: I also had a show-stopper with a USB audio device which turned out  
to be caused by OHCI vs UHCI (I think). Turns out the audio didn't  
work on the front (keyboard/mouse) USB ports of a Dell R200 server but  
worked fine on the rear ports.



On Sep 14, 2009, at 2:29 AM, "David A. Ranch" <dranch@trinnet.net>  
wrote:

>
> The new version of Ubuntu switched sound systems to PulseAudio:
>
> http://www.ubuntu.com/testing/804rc
>
> I've heard other reports about issues with soundmodem and Pulse.  I
> would recommend to try to re-compile soundmodem from sources.  The
> current sources version is 0.14.  If that doesn't help, I'd recommend
> you back down to less of a bleeding edge distro.  I chose the exact
> opposite approach and have everything running on Centos 5.3 but it  
> took
> a lot of work.
>
> --David
>
>
> Christof Bodner wrote:
>> Hi Dave,
>>
>> I am using the soundmodem provided by the Ubuntu team
>> $ dpkg-query -W soundmodem
>> soundmodem    0.10-6
>>
>> This is the output of soundmodemconfig:
>>
>> on_configtree_selection_changed
>> selection: cfg: default  chan: Channel 0
>> Modulator: afsk Demodulator: afsk
>> Modulator: parameter bps value 1200
>> Modulator: parameter f0 value 1200
>> Modulator: parameter f1 value 2200
>> Modulator: parameter diffenc value 1
>> Demodulator: parameter bps value 1200
>> Demodulator: parameter f0 value 1200
>> Demodulator: parameter f1 value 2200
>> Demodulator: parameter diffdec value 1
>> Minimum sampling rate: 9600
>> Audio IO: type alsa
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> Real sampling rate: 9600
>> Joining TxThread
>> Joining RxThread
>> Releasing IO
>> Modulator: afsk Demodulator: afsk
>> Modulator: parameter bps value 1200
>> Modulator: parameter f0 value 1200
>> Modulator: parameter f1 value 2200
>> Modulator: parameter diffenc value 1
>> Demodulator: parameter bps value 1200
>> Demodulator: parameter f0 value 1200
>> Demodulator: parameter f1 value 2200
>> Demodulator: parameter diffdec value 1
>> Minimum sampling rate: 9600
>> Audio IO: type alsa
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> Real sampling rate: 9600
>> delete event
>> on_configtree_selection_changed
>> Modulator mode: afsk
>> Demodulator mode: afsk
>> Packet IO mode: MKISS
>> Joining TxThread
>> Joining RxThread
>> Releasing IO
>> selection: cfg: -  chan: -
>> podex@rosi-atom:~$ sudo soundmodemconfig -v 4
>> on_configtree_selection_changed
>> selection: cfg: default  chan: Channel 0
>> Modulator: afsk Demodulator: afsk
>> Modulator: parameter bps value 1200
>> Modulator: parameter f0 value 1200
>> Modulator: parameter f1 value 2200
>> Modulator: parameter diffenc value 1
>> Demodulator: parameter bps value 1200
>> Demodulator: parameter f0 value 1200
>> Demodulator: parameter f1 value 2200
>> Demodulator: parameter diffdec value 1
>> Minimum sampling rate: 9600
>> Audio IO: type alsa
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> Real sampling rate: 9600
>> Joining TxThread
>> Joining RxThread
>> Releasing IO
>> Modulator: afsk Demodulator: afsk
>> Modulator: parameter bps value 1200
>> Modulator: parameter f0 value 1200
>> Modulator: parameter f1 value 2200
>> Modulator: parameter diffenc value 1
>> Demodulator: parameter bps value 1200
>> Demodulator: parameter f0 value 1200
>> Demodulator: parameter f1 value 2200
>> Demodulator: parameter diffdec value 1
>> Minimum sampling rate: 9600
>> Audio IO: type alsa
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> Real sampling rate: 9600
>> Joining TxThread
>> Joining RxThread
>> Releasing IO
>> Modulator: afsk Demodulator: afsk
>> Modulator: parameter bps value 1200
>> Modulator: parameter f0 value 1200
>> Modulator: parameter f1 value 2200
>> Modulator: parameter diffenc value 1
>> Demodulator: parameter bps value 1200
>> Demodulator: parameter f0 value 1200
>> Demodulator: parameter f1 value 2200
>> Demodulator: parameter diffdec value 1
>> Minimum sampling rate: 9600
>> Audio IO: type alsa
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> Real sampling rate: 9600
>> Joining TxThread
>> Joining RxThread
>> Releasing IO
>> delete event
>> on_configtree_selection_changed
>> Modulator mode: afsk
>> Demodulator mode: afsk
>> Packet IO mode: MKISS
>> selection: cfg: -  chan: -
>>
>> I started the oscilloscope twice and the spectrum analyzer once. The
>> display got stuck after the first packet arrived. The output of
>> soundmodem itself is
>>
>> $ sudo soundmodem -v 4
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: unknown node "text"
>> sm[20838]: mkiss: ifname sm0 mtu 256 hwaddr OE8BCK-2 ipaddr 10.0.0.1
>> netmask 255.255.255.0 broadcast 10.0.0.255
>> sm[20838]: unknown node "text"
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> ALSA: Using sample rate 9600, sample format 2, significant bits 16,
>> buffer size 3276, period size 102
>> sm[20838]: unknown kiss packet: 0x80 0xa2
>> sm[20838]: unknown kiss packet: 0x20 0xa2
>>
>> $ dmesg
>> [45458.558881] mkiss: AX.25 Multikiss, Hans Albas PE1AYX
>> [45458.562150] mkiss: ax0: crc mode is auto.
>> [45458.576058] mkiss: sm0: Trying crc-smack
>> [45458.668378] mkiss: sm0: Trying crc-flexnet
>> [45591.993672] mkiss: ax0: crc mode is auto.
>> [45592.005084] mkiss: sm0: Trying crc-smack
>> [45592.099000] mkiss: sm0: Trying crc-flexnet
>>
>> It decoded not a single packet, but transmitting was a little bit
>> strange. No, I did not transmit to the ether, only to my  
>> loudspeakers.
>> It seemed that there was a holdup, as there were no packets for some
>> secondes and then came a lot of them. But it could also be sent  
>> this way
>> from the ahavi and cups daemons which produce them. It did not change
>> the behaviour after restarting having unloaded the ax25 and mkiss
>> modules.
>>
>> 73 de OE8BCK,
>> Christof
>>
>> Am Sonntag, den 13.09.2009, 11:26 -0700 schrieb Dave Platt:
>>> Christof Bodner wrote:
>>>> Hi,
>>>>
>>>> Soundmodem stopped to work in Ubuntu 8.04, in 7.10 it works fine  
>>>> with
>>>> OSS. Today I tried it again with ALSA plughw: and it stopped after
>>>> receiving the first packet. That was reproduceable and occured in  
>>>> the
>>>> soundmodemconfig modem diagnostic as well as in the soundmodem  
>>>> itself.
>>> Two questions:
>>>
>>> - Which version are you using?
>>>
>>> - If you run it from the command line, are there any diagnostic
>>>   or error messages printed when it receives or transmits?
> --
> To unsubscribe from this list: send the line "unsubscribe linux- 
> hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>