开云体育

Hello Arnold, Yes, or connect up the HDMI display with a USB keyboard. --David KI6ZHD

David, " When your Rpi isn't connected to the network, what is in the /etc/resolv.conf file? Anything? Is DNSMasq running? " How would I know??? I suppose I could connect to the serial port for a

Hey Arnold, When your Rpi isn't connected to the network, what is in the /etc/resolv.conf file? Anything? Is DNSMasq running? --David

Somehow I missed putting this in the email. It IS in the DireWolf configuration. ADEVICE plughw:1,0 ACHANNELS 1 CHANNEL 0 # Home call MYCALL KQ6DI-4 I DO have PulseAudio removed. I don't think it is

Usually you would have something like "ADEVICE plughw:1,0" when running on the Raspberry Pi. I don't see ADEVICE in there which would result in using the "default" device. Did you make sure that

David, I should have provided you with the DireWolf configuration. The following is the configuration I have for this Zero. Anything not included is commented out. These are the only active

David, Correct, I am not using any Linux AX.25 Stack. I am also not including any HamLib support in the DireWolf build. The Hub I am using (that works) could have an external supply, but it wasn't

Hello Arnold, There have been random reports about these delays and I've seen it too. I didn't correlate it to being related to having a USB hub in front of the sound device but that's weird. In the

So I put the micro USB hub #2992 back in Without the WiFi USB thing, and my problem went away. However that USB Hub does have an ethernet port, although nothing is attached... Just the Sound USB

I asked this question before and didn't get any answer, so now I've done more testing and have a major clue. I have a Raspberry Pi Zero running DireWolf that has a very long transmit delay. First, I

I've been researching and trying to see if it's at all possible to run Dire Wolf with a virtual TNC over Bluetooth SPP for use with APRSDroid. I can easily do it over TCP/IP, but Bluetooth is more

Check out freedompop on sprint, aka cdma. Free 500 megs each month and easy to root and hotspot most devices.

David, thanks. My bad; I had not in fact read the 1.3 docs as you can guess. :) Figures that I am looking at the guts of source code instead of the obvious. All better now, though. -Mike K0FSJ

Hello Shimniok (no call given), I assume you've configured a Tracker beacon (tbeacon) in your direwolf.conf and also configured the use of your GPS using either the GPSNEMA or GPSD keywords. Looking

I'm running into a TBEACON error on RPi / direwolf 1.3. I searched github issues, googled, and searched yahoo groups -- to no avail. I figured I'd ask if anyone's seen this... On RPi 2, newly

Hello John, If things are working for an hour or so and then things start to break down, I would begin to suspect: - RFI from your radio getting back into the soundcard and/or Rpi and

David, sorry for the delay. Just to be sure I checked the patch level of Jessie: apt-get update apt-get upgrade apt-get dist-upgrade rpi-update reboot. still see the same error after an hour or so of

Just pulled and rebuilt from dev branch. That works for me (user is a gpio group member). Thanks!

This has been fixed. 67b11d4922ce538e55ab7853c1a449ad4de6ec83 in the 'dev' branch. Don't digipeat packets when the source is my call.

Nick B. wrote: Commit 58c2707f7d65b5b074b5e67e00c06a50fb968349, on the 'dev' branch, should fix this. Raspbian Jessie has a new 'gpio' group which was not in Wheezy. The logic for getting access to