- This topic has 13 replies, 3 voices, and was last updated 8 years, 9 months ago by Aaron, N3MBH.
-
AuthorPosts
-
February 22, 2016 at 2:17 pm #1641Björn, PD5DJUser
Hi all,
I have prepared Openrepeater on my BeagleBone Black.
It is running fine but, on startup the USB soundcard wont init properly.
When I log into the webgui, and go to TX/RX Ports, and click on update etc.. etc.. the soundcard starts.Any idea what is going on???
73
Bjorn de PD5DJFebruary 22, 2016 at 6:27 pm #1642Aaron, N3MBHForum AdministratorGreetings Bjorn,
A couple things to check when you are experiencing this issue…- What sound device are you using and does it show up initially? From the command line, try “lsusb” and share the results.
- You can also try aplay -l and aplay -r and see if the results change any from before or after the issue. Share your results as well.
- When you go into TX/RX Ports while encountering the problem, does it is show input and out put audio selected or are the dropdowns unselected and you have to select and save?
Just trying to understand the scope of what you are experiencing. Thanks for your feedback.
73,
Aaron – N3MBH73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
- This reply was modified 8 years, 9 months ago by Aaron, N3MBH.
February 23, 2016 at 4:49 am #1644Björn, PD5DJUserHi Aaron thanks for the reply.
Here goes the answers on your questions 🙂
1.)
My USB Audio device is one cheap from from ebay: http://www.ebay.com/itm/Latest-Laptop-PC-Windows-USB2-0-3D-Virtual-7-1-Channel-Audio-Sound-Card-Adapter-/361495341332?hash=item542acd2914:g:VtoAAOSw5dNWkIXfWhen I run lsusb from a fresh boot I get the following:
debian@bbb-repeater:~$ lsusb Bus 001 Device 002: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub debian@bbb-repeater:~$
2.)
on running aplay -l I get this:debian@bbb-repeater:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 debian@bbb-repeater:~$
nothing happens.
After running aplay -r i get this:
debian@bbb-repeater:~$ aplay -r aplay: option requires an argument -- 'r' Try aplay --help' for more information. debian@bbb-repeater:~$
3.)
Yes after a fresh boot, going to the TX/RX setup, I can see the USB audio device is showing.
USB PnP sound device Left and Right, both in Green and Red (RX/TX)But at this time the usb device does not run.
Only after pressing:
Update Ports -> Rebuild & Restart Repeater -> Restart
The USB Audio device is runningBjorn
- This reply was modified 8 years, 9 months ago by Björn, PD5DJ.
February 23, 2016 at 12:20 pm #1646Aaron, N3MBHForum AdministratorHello Bjorn,
Thanks for all your reports. Sorry for the aplay -r command..brain slip. I meant aplay -l and arecord -l, but that doesn’t matter so much. Before leaving for work this morning I booted up my BBB that I made the image on and experienced the same result. I am also using a cheap sound card for testing with the CM108 chipset. It doesn’t respond right away. Everything appears to be correct. It just seems like the sound driver is slow to load or something. I am not certain why it would do this. I am using the same CM108 chipset on my Raspberry Pi 2 build and that works no problems. I think in my testing the card would stop working after some time on the BBB. I am wondering if the driver for the sound card is buggy. I might have to try a ‘apt-get update && apt-get dist-upgrade’ tonight and let you know if that fixes things. Thanks for your reports.73,
Aaron – N3MBH73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
- This reply was modified 8 years, 9 months ago by Aaron, N3MBH.
- This reply was modified 8 years, 9 months ago by Aaron, N3MBH.
February 23, 2016 at 3:43 pm #1649Björn, PD5DJUserHi Aaron
Updating and upgrading had no effect.
From my gues, Svxlink is starting too fast..
Maybe a dirty SLEEP delay would help..
But where to put it?, cant seem to find where it got autostarted.February 24, 2016 at 8:05 am #1650Devan, KD8MSTUserI am having the same issue with my Raspberry pi I agree it is acting like SVXLINK is just starting up too fast… if I go and run “sudo service svxlink restart” it comes back no problem but a full reboot the sound card fails to be seen.
February 24, 2016 at 9:09 am #1652Björn, PD5DJUserHmm we have to find where svxlink is autostarted.
I checked /etc/init.d and rc.local and cron’s but cant seem to find where it is autostarted..
If we know the script we can add a dirty ‘SLEEP 30’ command or something..February 24, 2016 at 3:29 pm #1653Björn, PD5DJUserI did a dirty trick, added the “service svxlink restart” in /etc/rc.local
I know this is not the way to go, but in the mean time this works..
February 24, 2016 at 4:03 pm #1654Devan, KD8MSTUserPersonal opinion is if it works then that’s the way to go hihi I’ll have to do the same on my raspberry Pi
February 24, 2016 at 7:49 pm #1656Aaron, N3MBHForum AdministratorSorry I hadn’t had a chance to reply to this yet. I didn’t think this was a problem on the RPI2, but it does seem to occur now on both. I am doing some mods and testing for some new functions on the RPI2, but maybe I just didn’t pickup on it before. Yes your solution of restarting or stopping/starting the svxlink service does seem to fix it. I will point Richard at this topic to see what his thoughts are since it did the shell work. Thanks for your feedback and for the temporary work around.
73,
Aaron – N3MBH73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
AuthorPosts
- You must be logged in to reply to this topic.