Linrad on Ubuntu 12.04 problems
76 views
Skip to first unread message
Mike Sousa
May 6, 2017, 6:35:00 PM5/6/17
to Linrad
Hi
I've installed Linrad on Ubuntu 12.04. The process I followed:
$ svn checkout https://svn.code.sf.net/p/linrad/code/trunk linrad
$ cd linrad/
$ ./configure
.
.
.
$ make xlinrad64
.
.
.
$ ./xlinrad64
The following comes up:
I then wish to select an input (I'm using an RTL2832U dongle), so I press 'U'
The following shows up;
Selecting either 0 or 1 d doesn't do anything. The only I've found to get out of this view is to hit 'ESC', all other keys don't seem to do anything.
In fact, selecting any of the choices in the original screen brings me to the 'Select sound system' screen.
There are no errors or warnings reported on the terminal.
Any ideas or suggestions would be appreciated, thanks...
Leif Asbrink
May 14, 2017, 8:01:22 AM5/14/17
to lin...@googlegroups.com
Hello Mike,
> I've installed Linrad on Ubuntu 12.04. The process I followed:
>
> $ svn checkout https://svn.code.sf.net/p/linrad/code/trunk linrad
> $ cd linrad/
> $ ./configure
> .
> .
> .
> $ make xlinrad64
> .
> .
> .
> $ ./xlinrad64
>
>
> The following comes up:
>
>
a text client for E-mail and get inline images as attachments.
When I press 0 (to select ALSA) I get an error screen saying that
the alsa library is not installed. This error screen gives the
instruction Run ./configure --with-ALSA-64 to get install
instructions. (The command in red.)
The command is also printed in the console window from where
one can copy and paste it into the command line.
> In fact, selecting any of the choices in the original screen brings me to
> the 'Select sound system' screen.
>
> There are no errors or warnings reported on the terminal.
>
> Any ideas or suggestions would be appreciated, thanks...
Your observation is most unexpected. Maybe a problem with the
keyboard??
Look in lsetad.c, line4175:
lir_text(5,5,"Select sound system");
lir_text(5,7,"0=ALSA");
lir_text(5,8,"1=OSS");
getsys:;
await_keyboard();
if(kill_all_flag)return;
if(lir_inkey == '0')
{
ui.use_alsa|=NATIVE_ALSA_USED;
}
else
{
if(lir_inkey == '1')
{
ui.use_alsa&=~NATIVE_ALSA_USED;
}
else
{
goto getsys;
}
}
Add a line after await_keyboard like this:
fprintf(stderr,"\n keypress=%c, [%d]",lir_inkey,lir_inkey);
With this change you should see a line in the terminal
when you press 0 for alsa. Like this:
keypress=0, [48]
When you press ESC you should see the previous char
once more since ESC will not put the new data into lir_inkey.
The install procedure on a fresh Ubuntu 12.04 is:
The configure script will give the command how to install nasm.
$ apt-get install nasm
$ ./configure
$ make xlinrad64
$ ./xlinrad64
Linrad asks what screen you wish to use. When you select
one you will get an error message saying that the library is not
installed and you will get the appropriate command to install
the screen of your choice.
$ ./configure --with-X11-64 (if you selected X11 for your screen.)
The configure script will give the command how to install X11.
$ apt-get install libx11-dev
$ ./configure
$ make xlinrad64
$ ./xlinrad64
Feed in parameters of your choice, go to the setup ("U") and
press 0 for alsa. (Any key would bring you there...)
Please tell me what the extra line in lsetad.c prints in
the commant window.
73
Leif
> I've installed Linrad on Ubuntu 12.04. The process I followed:
>
> $ svn checkout https://svn.code.sf.net/p/linrad/code/trunk linrad
> $ cd linrad/
> $ ./configure
> .
> .
> .
> $ make xlinrad64
> .
> .
> .
> $ ./xlinrad64
>
>
> The following comes up:
>
>
> I then wish to select an input (I'm using an RTL2832U dongle), so I press
> 'U'
>
> The following shows up;
You mean the screen "Select sound system" I assume. I am using
> 'U'
>
> The following shows up;
a text client for E-mail and get inline images as attachments.
>
>
> Selecting either 0 or 1 d doesn't do anything. The only I've found to get
> out of this view is to hit 'ESC', all other keys don't seem to do anything.
I have made a fresh install on Ubuntu 12.04 today.
>
> Selecting either 0 or 1 d doesn't do anything. The only I've found to get
> out of this view is to hit 'ESC', all other keys don't seem to do anything.
When I press 0 (to select ALSA) I get an error screen saying that
the alsa library is not installed. This error screen gives the
instruction Run ./configure --with-ALSA-64 to get install
instructions. (The command in red.)
The command is also printed in the console window from where
one can copy and paste it into the command line.
> In fact, selecting any of the choices in the original screen brings me to
> the 'Select sound system' screen.
>
> There are no errors or warnings reported on the terminal.
>
> Any ideas or suggestions would be appreciated, thanks...
keyboard??
Look in lsetad.c, line4175:
lir_text(5,5,"Select sound system");
lir_text(5,7,"0=ALSA");
lir_text(5,8,"1=OSS");
getsys:;
await_keyboard();
if(kill_all_flag)return;
if(lir_inkey == '0')
{
ui.use_alsa|=NATIVE_ALSA_USED;
}
else
{
if(lir_inkey == '1')
{
ui.use_alsa&=~NATIVE_ALSA_USED;
}
else
{
goto getsys;
}
}
Add a line after await_keyboard like this:
fprintf(stderr,"\n keypress=%c, [%d]",lir_inkey,lir_inkey);
With this change you should see a line in the terminal
when you press 0 for alsa. Like this:
keypress=0, [48]
When you press ESC you should see the previous char
once more since ESC will not put the new data into lir_inkey.
The install procedure on a fresh Ubuntu 12.04 is:
The configure script will give the command how to install nasm.
$ apt-get install nasm
$ ./configure
$ make xlinrad64
$ ./xlinrad64
Linrad asks what screen you wish to use. When you select
one you will get an error message saying that the library is not
installed and you will get the appropriate command to install
the screen of your choice.
$ ./configure --with-X11-64 (if you selected X11 for your screen.)
The configure script will give the command how to install X11.
$ apt-get install libx11-dev
$ ./configure
$ make xlinrad64
$ ./xlinrad64
Feed in parameters of your choice, go to the setup ("U") and
press 0 for alsa. (Any key would bring you there...)
Please tell me what the extra line in lsetad.c prints in
the commant window.
73
Leif
Mike Sousa
May 16, 2017, 8:14:34 AM5/16/17
to Linrad
Hi Leif
Thanks for the reply. I rebuilt everything and was able to get into a runnable state. I selected my rtl3832U dongle as input and my sound card as output. On the terminal window was the following output:
$ ./xlinrad64
WELCOME TO LINRAD
This message is not an error, but an indication that setup
has not yet been done.
Setup file par_userint missing.
Use W to create a new par_userint file after setup.
Note that the following keys have a special meaning in Linrad:
ESC = terminate Linrad
X = Skip whatever process you are in and get one level
upwards in Linrads menu three.
G = Make a .gif file with a screen dump of your current screen.
----------- GLOBAL PARAMETERS SETUP -------------
(You might want to edit par_userint instead)
Press N for NEWCOMER mode.
Press S for normal mode.
Press E for expert mode.
Then press enter
=>N
Percentage of screen width to use(25 to 100):
=>50
Percentage of screen height to use (25 to 100):
=>40
Linrad will now open another window.
Minimize this window and click on the new window to continue.
Do not forget to save your parameters with 'W' in the main menuFound Elonics E4000 tuner
Exact sample rate is: 2000000.052982 Hz
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
.
. <there were many more of these -- mike>
.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1735
Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1767
Shutting down now!!!
$
Are these a problem?
Thanks...
'73' Mike
Leif Asbrink
May 17, 2017, 9:21:12 AM5/17/17
to lin...@googlegroups.com
Hello Mike,
> Thanks for the reply. I rebuilt everything and was able to get into a
> runnable state. I selected my rtl3832U dongle as input and my sound card as
> output. On the terminal window was the following output:
>
>
> $ ./xlinrad64
>
> WELCOME TO LINRAD
> This message is not an error, but an indication that setup
> has not yet been done.
.
.
.
This is an old version of Linrad and not a result from
the output, then X twice to get to the main menu where you can
save the settings so far.
Then go to U again and start to select an output device.
You have selected to use Portaudio. Did you get a list
of devices and selected one before all the error messages?
If you did, try to select another device.
In case you did not get a list of devices, say you do not
want to use portaudio. That will give you access to the soundcard
directly through ALSA.
Make sure your system is updated with all upgrades until today.
There have been many updates on the sound systems since 2012.
Ubuntu 12.04 is long term support, but I think no more than
5 years. If you are on a modern computer it might be clever
to install Ubuntu 16.04 to replace it with the most recent
long time support.
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> .
> . <there were many more of these -- mike>
> .
Most errors are harmless, they occur because Linrad tries to open
all the devices for output and those that fail will not become
available as a choice for Linrad output.
In case an error is fatal as it seems you have found: "Expression
not get a list to select from. Maybe a fresh install of Portaudio
from source could fix the problem. For thet, remove your portaudio
installation, then run ./configure --with-help and copy the
install instrections for portaudio into your command screen.
(Or run ALSA without Portaudio.)
In the event that the problem is a bug in ALSA you might install
4Front OSS and select OSS as your sound system:
http://www.opensound.com/download.cgi
73
Leif
> Thanks for the reply. I rebuilt everything and was able to get into a
> runnable state. I selected my rtl3832U dongle as input and my sound card as
> output. On the terminal window was the following output:
>
>
> $ ./xlinrad64
>
> WELCOME TO LINRAD
> This message is not an error, but an indication that setup
> has not yet been done.
.
.
This is an old version of Linrad and not a result from
> Exact sample rate is: 2000000.052982 Hz
At this point when you have the input OK, press Z to disable
the output, then X twice to get to the main menu where you can
save the settings so far.
Then go to U again and start to select an output device.
You have selected to use Portaudio. Did you get a list
of devices and selected one before all the error messages?
If you did, try to select another device.
In case you did not get a list of devices, say you do not
want to use portaudio. That will give you access to the soundcard
directly through ALSA.
Make sure your system is updated with all upgrades until today.
There have been many updates on the sound systems since 2012.
Ubuntu 12.04 is long term support, but I think no more than
5 years. If you are on a modern computer it might be clever
to install Ubuntu 16.04 to replace it with the most recent
long time support.
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> .
> . <there were many more of these -- mike>
> .
> Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1735
> Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
> 'src/hostapi/alsa/pa_linux_alsa.c', line: 1767
> Shutting down now!!!
All the error messages from ALSA are because of bugs outside Linrad.
> Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
> 'src/hostapi/alsa/pa_linux_alsa.c', line: 1767
> Shutting down now!!!
Most errors are harmless, they occur because Linrad tries to open
all the devices for output and those that fail will not become
available as a choice for Linrad output.
In case an error is fatal as it seems you have found: "Expression
'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 176" you would perhaps
not get a list to select from. Maybe a fresh install of Portaudio
from source could fix the problem. For thet, remove your portaudio
installation, then run ./configure --with-help and copy the
install instrections for portaudio into your command screen.
(Or run ALSA without Portaudio.)
In the event that the problem is a bug in ALSA you might install
4Front OSS and select OSS as your sound system:
http://www.opensound.com/download.cgi
73
Leif
Roger Rehr W3SZ
May 17, 2017, 9:45:56 AM5/17/17
to lin...@googlegroups.com
HI All,
Leif's advice is on the money.
Ubuntu 12.04 had end of life on April 28 of this year. This means no more security updates unless you join Ubuntu's paid program (Ubuntu Advantage) and pay for updates.
http://fridge.ubuntu.com/2017/03/15/ubuntu-12-04-precise-pangolin-reaches-end-of-life-on-april-28-2017/
I also would recommend updating to 14.04 and then to 16.04. It is a painless if somewhat lengthy process unless you have things like Apache server / mysql database server / mailservers / etc. with local configuration settings that could get overwritten if you are not careful. The update process does ask you if you want to keep old configuration files or overwrite them with new versions, but you need to pay close attention as the upgrade process proceeds.
If you are in doubt about the support status of your Ubuntu distro, you can type "ubuntu-support-status" at the command prompt and you will be so informed.
73,
Roger Rehr
W3SZ
Leif's advice is on the money.
Ubuntu 12.04 had end of life on April 28 of this year. This means no more security updates unless you join Ubuntu's paid program (Ubuntu Advantage) and pay for updates.
http://fridge.ubuntu.com/2017/03/15/ubuntu-12-04-precise-pangolin-reaches-end-of-life-on-april-28-2017/
I also would recommend updating to 14.04 and then to 16.04. It is a painless if somewhat lengthy process unless you have things like Apache server / mysql database server / mailservers / etc. with local configuration settings that could get overwritten if you are not careful. The update process does ask you if you want to keep old configuration files or overwrite them with new versions, but you need to pay close attention as the upgrade process proceeds.
If you are in doubt about the support status of your Ubuntu distro, you can type "ubuntu-support-status" at the command prompt and you will be so informed.
73,
Roger Rehr
W3SZ
On 5/17/2017 10:12 AM, Leif Asbrink
wrote
frankddr
May 18, 2017, 7:27:37 AM5/18/17
to lin...@googlegroups.com
Hello Leif.
How are you. I heard about your health problems.
Are you getting better?
Ciao and see you soon.
73' Francesco,IK2DDR
Cc:
Data: Wed, 17 May 2017 16:12:38 +0200
Oggetto: [Linrad] Re: Linrad on Ubuntu 12.04 problems
> > .
>
> > Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1735
> > Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
> > 'src/hostapi/alsa/pa_linux_alsa.c', line: 1767
> > Shutting down now!!!
> All the error messages from ALSA are because of bugs outside Linrad.
> Most errors are harmless, they occur because Linrad tries to open
> all the devices for output and those that fail will not become
> available as a choice for Linrad output.
>
> In case an error is fatal as it seems you have found: "Expression
> 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
> 'src/hostapi/alsa/pa_linux_alsa.c', line: 176" you would perhaps
> not get a list to select from. Maybe a fresh install of Portaudio
> from source could fix the problem. For thet, remove your portaudio
> installation, then run ./configure --with-help and copy the
> install instrections for portaudio into your command screen.
> (Or run ALSA without Portaudio.)
>
> In the event that the problem is a bug in ALSA you might install
> 4Front OSS and select OSS as your sound system:
>
> 73
>
> Leif
>
>
>
>
>
>
>
>
>
> --
> There is an excellent Linrad User Guide by Gaetan, ON4KHG, at:
> http://www.nitehawk.com/w3sz/Linrad%20Installation%20&%20Configuration%20User%20Guide%20-%20V1-0.pdf
> ---
> You received this message because you are subscribed to the Google Groups "Linrad" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linrad+un...@googlegroups.com.
> To post to this group, send email to lin...@googlegroups.com.
> Visit this group at https://groups.google.com/group/linrad.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages