[linrad] Re: segmentation fault
Hi Dan, There is no file /dev/sndstat. Can it be known by another name? Try the command ossinfo 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Leif, That command does not exist. This configurations appears to be ALSA with alsa-oss. There is a file /etc/asound.state that shows a CS46xx. This is the sound device. Below are the snd modules installed: snd_rtctimer3360 0 snd_intel8x0 31260 0 snd_ac97_codec 90720 1 snd_intel8x0 ac97_bus2048 1 snd_ac97_codec snd_seq_dummy 3588 0 snd_seq_oss28672 0 snd_seq_midi_event 6656 1 snd_seq_oss snd_seq44368 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 7436 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss38688 0 snd_mixer_oss 15360 1 snd_pcm_oss snd_pcm70152 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 20420 3 snd_rtctimer,snd_seq,snd_pcm snd47460 9 snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 7456 1 snd snd_page_alloc 9352 2 snd_intel8x0,snd_pcm rtc12120 1 snd_rtctimer Thanks - Dan # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Hello Dan, That command does not exist. This configurations appears to be ALSA with alsa-oss. There is a file /etc/asound.state that shows a CS46xx. This is the sound device. Below are the snd modules installed: snd_rtctimer3360 0 snd_intel8x0 31260 0 snd_ac97_codec 90720 1 snd_intel8x0 ac97_bus2048 1 snd_ac97_codec snd_seq_dummy 3588 0 snd_seq_oss28672 0 snd_seq_midi_event 6656 1 snd_seq_oss snd_seq44368 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 7436 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss38688 0 snd_mixer_oss 15360 1 snd_pcm_oss snd_pcm70152 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 20420 3 snd_rtctimer,snd_seq,snd_pcm snd47460 9 snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 7456 1 snd snd_page_alloc 9352 2 snd_intel8x0,snd_pcm rtc12120 1 snd_rtctimer This does not tell me anything. I have often had problems with ALSA in the past. I think it is because alsa-oss is not given much attention by the developers - they provide it for lazy people with old softwares who are (like me) reluctant to rewrite for the ALSA interface. I installed the latest Debian testing a couple of days ago. It came with alsa but without alsa-oss and it works perfectly well on the laptop. On the stationary computer I have the stable release of Debian and it uses OSS since the alsa plus alsa-oss package did not work properly. The (non-working) stationary has SND_LIB_VERSION_STR = 1.0.13 The well working lap-top does have the /dev/sndstat file: hp:/home/dsp# cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.14rc3 emulation code) Kernel: Linux hp 2.6.21-2-686-bigmem #1 SMP Wed Jul 11 05:05:14 UTC 2007 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel at 0xe858 irq 20 Audio devices: 0: AD198x Analog (DUPLEX) This was all automatically installed with the standard packages for Debian. There is no longer any alsa-oss package and Linrad compiles and runs without any problem under X11. (It is quite another thing that I had to modify both mousetest and the linrad main routine in order to make the screen work properly. These changes will come with Linrad-02.39) (There will also be a proper error message rather than a seg-fault in an error situation like the one you have right now: [1289]routine:set_analog_iofile:lsetad.c No usable device found for loudspeaker output.) It seems to me you should de-install alsa and alsa-oss and then install ALSA v1.0.14rc3. Maybe that would help. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Hi Dan, I followed that sequence and selected U, everything worked as described below. There is no option for selecting a sound card. It jumps to requesting baud rate, reporting lack of ability to perform input and output together, and then seg faulting. If there is only one possibillity Linrad will silently choose it. Look in the file soundboard_init.log, it may give a hint on what is going wrong. You were not prompted for choosing RDONLY or RDWR so you should find either User selected RDONLY or Only RDONLY available in the log file. Before requesting a sampling speed, Linrad should inform you about what device it selected on the top of the screen. Something like: For analog input: /dev/dsp opened in RDWR mode You should then see: Select radio interface: on line 10 on the screen followed by a list of modes. I guess you have it ok and have selected 1 or 2. Then you are prompted for input sampling rate. At this point you need true OSS to know what your hardware capabilities are. I suspect you are using alsa-oss and that does not behave correctly, it might suggest you can choose frequencies up tp 192 kHz. It seems you get this message: No device found for 8/16 bit output while input is open. You may use Linrad to watch spectra and record raw data. Linrad will now look for devices that can be used to output sound while processing recorded data. Does it stay on screen untill you press a key? The next step is searching for a writeable device. The soundboard_init.log file should have the details. Maybe there is no output that works properly - then there could be a segfault because I have not provided an error exit for this case which I have never seen. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Leif, You are correct. The output stays on the screen until the key is hit. The trace output is: /dev/dsp62 /dev/dsp /dev/dsp64 (/dev/dsp63 is missing) The error message segmentation fault appears in the terminal box. - Regards - Dan # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Leif, The log is: /dev/dsp opened as RDONLY 16bit format supported Max no of channels = 4 Max speed 192000 Hz Min sampling speed = 1000 Hz FLAG= 1 j=0 k=0 63:/dev/dsp 1000 - 192000 Hz 4 Chan. 16 bit RDONLY color=28 m=0 Checking /dev/dsp64 /dev/dsp selected by user for input. dev_flag=1 Only RDONLY available ui.input_mode=4 ui.rx_channels=1 ui.ad_channels =2 9600 Hz selected by user 9600 Hz reported by device Input format: 16 bit Read test OK No output device found while input is open. /dev/dsp0 /dev/dsp1 /dev/dsp2 /dev/dsp3 /dev/dsp4 /dev/dsp5 /dev/dsp6 /dev/dsp7 /dev/dsp8 /dev/dsp9 /dev/dsp10 /dev/dsp11 /dev/dsp12 /dev/dsp13 /dev/dsp14 /dev/dsp15 /dev/dsp16 /dev/dsp17 /dev/dsp18 /dev/dsp19 /dev/dsp20 /dev/dsp21 /dev/dsp22 /dev/dsp23 /dev/dsp24 /dev/dsp25 /dev/dsp26 /dev/dsp27 /dev/dsp28 /dev/dsp29 /dev/dsp30 /dev/dsp31 /dev/dsp32 /dev/dsp33 /dev/dsp34 /dev/dsp35 /dev/dsp36 /dev/dsp37 /dev/dsp38 /dev/dsp39 /dev/dsp40 /dev/dsp41 /dev/dsp42 /dev/dsp43 /dev/dsp44 /dev/dsp45 /dev/dsp46 /dev/dsp47 /dev/dsp48 /dev/dsp49 /dev/dsp50 /dev/dsp51 /dev/dsp52 /dev/dsp53 /dev/dsp54 /dev/dsp55 /dev/dsp56 /dev/dsp57 /dev/dsp58 /dev/dsp59 /dev/dsp60 /dev/dsp61 /dev/dsp62 /dev/dsp /dev/dsp64 - Dan # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Hi Dan, /dev/dsp opened as RDONLY 16bit format supported Max no of channels = 4 Max speed 192000 Hz Min sampling speed = 1000 Hz FLAG= 1 j=0 k=0 63:/dev/dsp 1000 - 192000 Hz 4 Chan. 16 bit RDONLY color=28 m=0 Checking /dev/dsp64 /dev/dsp selected by user for input. dev_flag=1 Only RDONLY available ui.input_mode=4 ui.rx_channels=1 ui.ad_channels =2 9600 Hz selected by user 9600 Hz reported by device Input format: 16 bit Read test OK No output device found while input is open. At this point it is clear that your device does not allow duplex. I tried to look for 82801DB/DBL/DBM but was unable to find out what that is. Seems to be some kind of general purpose controller. Anyway, Linrad should be perfectly happy even if there is no possibility to run duplex. The next part of your log file should give a useful output device while the input is not opened (for use when processing recorded files, SDR14 or network data) /dev/dsp0 /dev/dsp1 /dev/dsp2 /dev/dsp3 /dev/dsp4 /dev/dsp5 /dev/dsp6 /dev/dsp7 /dev/dsp8 /dev/dsp9 /dev/dsp10 /dev/dsp11 /dev/dsp12 /dev/dsp13 /dev/dsp14 /dev/dsp15 /dev/dsp16 /dev/dsp17 /dev/dsp18 /dev/dsp19 /dev/dsp20 /dev/dsp21 /dev/dsp22 /dev/dsp23 /dev/dsp24 /dev/dsp25 /dev/dsp26 /dev/dsp27 /dev/dsp28 /dev/dsp29 /dev/dsp30 /dev/dsp31 /dev/dsp32 /dev/dsp33 /dev/dsp34 /dev/dsp35 /dev/dsp36 /dev/dsp37 /dev/dsp38 /dev/dsp39 /dev/dsp40 /dev/dsp41 /dev/dsp42 /dev/dsp43 /dev/dsp44 /dev/dsp45 /dev/dsp46 /dev/dsp47 /dev/dsp48 /dev/dsp49 /dev/dsp50 /dev/dsp51 /dev/dsp52 /dev/dsp53 /dev/dsp54 /dev/dsp55 /dev/dsp56 /dev/dsp57 /dev/dsp58 /dev/dsp59 /dev/dsp60 /dev/dsp61 /dev/dsp62 /dev/dsp /dev/dsp64 The result is very odd. Linrad tries to open all these devices. The statement is rx_audio_out=open( dev_name, O_WRONLY|O_NONBLOCK, 0); for each one of the device files and they all give rx_audio_out=-1 which is an error. What does your /dev/sndstat file contain? The very first line should say something about what sound system you have. Something is wrong with it. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
Leif, There is no file /dev/sndstat. Can it be known by another name? - Dan The result is very odd. Linrad tries to open all these devices. The statement is rx_audio_out=open( dev_name, O_WRONLY|O_NONBLOCK, 0); for each one of the device files and they all give rx_audio_out=-1 which is an error. What does your /dev/sndstat file contain? The very first line should say something about what sound system you have. Something is wrong with it. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: segmentation fault
You come to the main screen that lists: A=Weak Signal CW B=Normal CW C=Meteor Scatter CW D=SSB E=FM G=QRSS CW H=TX TEST I=SOUNDCARD TEST MODE J=ANALOG HARDWARE TUNE M=Init Moon Tracking and EME DATABASE M=NEtwork Setup S=Global Parms Setup U=A/D and D/A setup for RX -THIS IS SOUNDCARD SETUP! So you want to type U to setup the soundcards and get to the screens I suggested. If you haven't done U and you select any of A,B,C,D, etc. it will take you to the U series of screens anyway. When you type D I really don't think it is requesting a baud rate, it is requesting a sampling rate. It is taking you to the U configure A/D and D/A [in other words, configure soundcard] series of screens as I indicated it would. I hope the above explanation is helpful. Keep us posted, and 73, W3SZ Roger Rehr http://www.nitehawk.com/w3sz Quoting Dan Sawyer [EMAIL PROTECTED]: Roger, Thank you again. I am not seeing what you describe. Linrad open in a menu page with uses, weak signal cw, etc.; another set of menus, init moon tracking, etc.; and a third process first file named ..., etc. There is no menu to select a sound card. I chose D for ssb. xlinrad requests a baud rate, reports input and output cannot be performed together and that the device found is /dev/dsp. Thanks, - Dan Roger Rehr wrote: Hi Dan, Thanks for the answers! So the version of nasm and the [32 bit] OS size are not problems. When setting up the soundcard in Linrad, you should have selected option [2], One Rx channel, I/Q [direct conversion receiver]. If you selected option [4], things would surely crash. You might post a listing of exactly what choices you made, a la: -- 1. You will be presented with the first of several soundcard selection screens. You will see a listing of your soundcards and below that list will be the request ?Select (first) device for Rx input by line number:? In my case, I use the M-Audio Delta 44 1 and 2 channels for input and so I select ?2?, for ?M-Audio Delta 44 1 / 2? and hit ?ENTER?. 2. Then I am asked ?Do you need more channels from the same soundcard? (Y/N)?. I type ?N?. If I were doing dual-polarity receive EME with the Delta44 I would still type ?N? because the Delta 44 multi device driver supports 4 channels. 3. Then I am asked to enter ?Sampling speed (Hz):? and I type ?96000? and hit ?ENTER?, and on the same screen I am then asked to enter ?No of bits (16/24):? and I type ?24? and again hit ?ENTER?. 4. The I am asked to ?Select a radio interface and given four choices: [1] one rx channel (normal audio), [2] one rx channel I/Q (direct conversion rx), [3] two rx channels (adaptive polarization/phasing), [4] two rx channels, I/Q. I choose [2] for terrestrial work and [4] for EME, so here I choose [2]. 5. The next screen asks me to ?Select device for Rx output? and I select [0] Realtek HD Audio output, my motherboard sound, and again hit ?ENTER?. I type enter again, and then I am back to the main screen and I type ?W? to save my choices. - You can edit to show what choices you made and exactly where you see the segfault [I am guessing after number [4], but I am not sure if it is before or after [5]. With this info it may be easier to piece things together. By the way, it is not a baud rate, it is sampling rate in samples per second that the computer asks for. Good Luck, keep us posted, and 73, W3SZ Roger Rehr http://www.nitehawk.com/w3sz Quoting Dan Sawyer [EMAIL PROTECTED]: Roger, Thank you again. See below. - Dan Roger Rehr wrote: Hi, Dan, I have a couple of more questions the answers to which might help to figure things out if you are still having problems with segmentation faults. As Leif noted, you should not worry about doing the hardware test. Go right to U to set up soundcards, then to D SSB OR A Weak Signal CW. 1. Were you using OSS from the first, before you started with Linrad? Yes, it supports system sound. 2. If so, did FC6 come with it installed or did you add it? Yes. I have updated the kernel and it is also configured for OSS. 3. Is the audio now working in Linrad when you go into D or A for example from the main screen? No. The D option asks for channels, the a baud rate. It reports input and output cannot work concurrently and then errors with a seg fault. 4. If not, what exactly happens when you to to U from the main screen? see 3. 5. What version of nasm are you using? nasm-0.98.39-3.2.2 6. What kernel version are you using? 2.6.21.1 7. Is your machine 64 bit or 32 bit and if 64 bit are you running 64 bit version of FC6? 32 bit If things are working you can ignore all of these questions ;) 73, W3SZ Roger Rehr http://www.nitehawk.com/w3sz Quoting Dan Sawyer [EMAIL PROTECTED]: All, xlinrad is now building and running. However attempts to perform the z command, hardware interface test, produces a segmentation fault. Other sound apps, mplayer, etc run fine.
[linrad] Re: segmentation fault
Roger, I followed that sequence and selected U, everything worked as described below. There is no option for selecting a sound card. It jumps to requesting baud rate, reporting lack of ability to perform input and output together, and then seg faulting. - Thanks again, Dan Roger Rehr wrote: You come to the main screen that lists: A=Weak Signal CW B=Normal CW C=Meteor Scatter CW D=SSB E=FM G=QRSS CW H=TX TEST I=SOUNDCARD TEST MODE J=ANALOG HARDWARE TUNE M=Init Moon Tracking and EME DATABASE M=NEtwork Setup S=Global Parms Setup U=A/D and D/A setup for RX -THIS IS SOUNDCARD SETUP! So you want to type U to setup the soundcards and get to the screens I suggested. If you haven't done U and you select any of A,B,C,D, etc. it will take you to the U series of screens anyway. When you type D I really don't think it is requesting a baud rate, it is requesting a sampling rate. It is taking you to the U configure A/D and D/A [in other words, configure soundcard] series of screens as I indicated it would. I hope the above explanation is helpful. Keep us posted, and 73, W3SZ Roger Rehr http://www.nitehawk.com/w3sz Quoting Dan Sawyer [EMAIL PROTECTED]: Roger, Thank you again. I am not seeing what you describe. Linrad open in a menu page with uses, weak signal cw, etc.; another set of menus, init moon tracking, etc.; and a third process first file named ..., etc. There is no menu to select a sound card. I chose D for ssb. xlinrad requests a baud rate, reports input and output cannot be performed together and that the device found is /dev/dsp. Thanks, - Dan Roger Rehr wrote: Hi Dan, Thanks for the answers! So the version of nasm and the [32 bit] OS size are not problems. When setting up the soundcard in Linrad, you should have selected option [2], One Rx channel, I/Q [direct conversion receiver]. If you selected option [4], things would surely crash. You might post a listing of exactly what choices you made, a la: -- 1. You will be presented with the first of several soundcard selection screens. You will see a listing of your soundcards and below that list will be the request ?Select (first) device for Rx input by line number:? In my case, I use the M-Audio Delta 44 1 and 2 channels for input and so I select ?2?, for ?M-Audio Delta 44 1 / 2? and hit ?ENTER?. 2. Then I am asked ?Do you need more channels from the same soundcard? (Y/N)?. I type ?N?. If I were doing dual-polarity receive EME with the Delta44 I would still type ?N? because the Delta 44 multi device driver supports 4 channels. 3. Then I am asked to enter ?Sampling speed (Hz):? and I type ?96000? and hit ?ENTER?, and on the same screen I am then asked to enter ?No of bits (16/24):? and I type ?24? and again hit ?ENTER?. 4. The I am asked to ?Select a radio interface and given four choices: [1] one rx channel (normal audio), [2] one rx channel I/Q (direct conversion rx), [3] two rx channels (adaptive polarization/phasing), [4] two rx channels, I/Q. I choose [2] for terrestrial work and [4] for EME, so here I choose [2]. 5. The next screen asks me to ?Select device for Rx output? and I select [0] Realtek HD Audio output, my motherboard sound, and again hit ?ENTER?. I type enter again, and then I am back to the main screen and I type ?W? to save my choices. - You can edit to show what choices you made and exactly where you see the segfault [I am guessing after number [4], but I am not sure if it is before or after [5]. With this info it may be easier to piece things together. By the way, it is not a baud rate, it is sampling rate in samples per second that the computer asks for. Good Luck, keep us posted, and 73, W3SZ Roger Rehr http://www.nitehawk.com/w3sz Quoting Dan Sawyer [EMAIL PROTECTED]: Roger, Thank you again. See below. - Dan Roger Rehr wrote: Hi, Dan, I have a couple of more questions the answers to which might help to figure things out if you are still having problems with segmentation faults. As Leif noted, you should not worry about doing the hardware test. Go right to U to set up soundcards, then to D SSB OR A Weak Signal CW. 1. Were you using OSS from the first, before you started with Linrad? Yes, it supports system sound. 2. If so, did FC6 come with it installed or did you add it? Yes. I have updated the kernel and it is also configured for OSS. 3. Is the audio now working in Linrad when you go into D or A for example from the main screen? No. The D option asks for channels, the a baud rate. It reports input and output cannot work concurrently and then errors with a seg fault. 4. If not, what exactly happens when you to to U from the main screen? see 3. 5. What version of nasm are you using? nasm-0.98.39-3.2.2 6. What kernel version are you using? 2.6.21.1 7. Is your machine 64 bit or 32 bit and if 64 bit are you running 64 bit version of FC6? 32 bit If things are working you can ignore
