Date   

Re: Portable Battery Problem

Larry Dighera <larry@...>
 

It sounds like the 5VDC battery bank is momentarily interrupting its current to
the RPi upon system halt, and subsequently reestablishing it.


On 13 May 2016 17:57:45 -0700, "larryiweaver@gmail.com
[Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@yahoogroups.com> wrote:

Some months back I purchased a new Anker 13000 MAh battery to replace an aging smaller capacity battery. The purpose of both batteries is to recharge tablets and to power a Raspberry Pi while mobile. When I finally got around to using the new battery to power the Pi I found that I could not shut the Pi down. Both a Pi 2B and a Pi 3 will just cycle a reboot over and over but will not shut down without pulling the power. The older battery never gave me any problems. They are both 5V batteries of different MAh ratings. Anyone have an idea as to what could cause this behavior? I would buy a different battery but how would I know if I would have the same problem with another battery.


Thanks,
Larry


Re: TeamViewer for Pi

Larry Dighera <larry@...>
 

On 05 May 2016 19:19:29 -0700, "kb1chu@aol.com [Raspberry_Pi_4-Ham_RADIO]"
<Raspberry_Pi_4-Ham_RADIO@yahoogroups.com> wrote:

I just got an email from TeamViewer about a request I made a few weeks ago..... https://www.teamviewer.com/raspberrypi/

This is very good news. Now we can control our Windows computers over the
Internet from the RPi and vice versa, and I would presume one RPi could control
another RPi as well.

The potential is awesome. Imagine running DXLab <http://dxlabsuite.com/> on
the Windows computer at your station location, and controlling it over the
Internet from anywhere in the world you can get an Internet connection.

Thank you for making the request of TeamViewer, and their responsiveness to
their users.

-------------------------------------------------------------------------
<https://www.teamviewer.com/raspberrypi/>

TeamViewer for Raspberry Pi

It is one small step for TeamViewer, but one giant leap for the technological
perspectives of a groundbreaking idea: The TeamViewer Host for Raspberry Pi
marks the turning point when the uncommitted talk about the Internet of Things
(IoT) ends, and its true application begins.

IoT in particular requires secure connections to devices that very often do not
come with graphical interfaces. That is precisely what the TeamViewer Host for
Raspberry PI enables you to do. It allows control of a variety of IoT
applications with our industry-leading TeamViewer solution, familiar to
millions of users around the world

The TeamViewer Host for Raspberry Pi is a system service that allows for the
unattended access of Raspberry Pi devices so that they can be maintained,
controlled, or managed.

„Our team had a lot of fun developing our new app for Raspbian OS – it was an
interesting challenge as we had to adapt our thinking and approach to a new
environment", says Mike Eissele, Vice President Engineering at TeamViewer. "But
our highly motivated team came through with flying colors. As a result, I am
happy to announce the release of this preview version in response to many
requests from the TeamViewer user community, and is our next step into the IoT
space.”

System Requirements

Raspberry Pi 2 or Raspberry Pi 3
(Raspberry Pi 1 and Zero currently not supported)

Raspbian 8.0 Jessie with X-Server or Framebuffer VT

35 MB disk space

Features included

TeamViewer Host for Raspberry Pi preview version offers a number of features
including but not limited to

Remote Control your Raspberry Pi from any other device running TeamViewer
Connect to your Pi using either the graphic interface or our unique
headless mode
Choose between dynamic and fixed password for your access

Following the preview we are confident to integrate even more features for the
upcoming final release.

Download and try the exclusive TeamViewer Host app preview for Raspbian 8.0.
Download TeamViewer for Raspberry Pi:
<http://download.teamviewer.com/download/linux/version_11x/teamviewer-host_armhf.deb>
-------------------------------------------------------------------------------


Re: Portable Battery Problem

mccrpt@...
 

Although Pi draws less than 1 Amp, most of these type batteries can deliver like 3 Amp limit.  It should be enough, but if having problems on the USB port of a battery then it might be the battery cannot supply the current necessary.  Probably has a variable fuse inside so when current exceeds a given value the fuse adds resistance to limit current.

Take a good look at the battery spec.

73, ron, n9ee/r


Re: Portable Battery Problem

Larry Weaver
 

Yes I do have the old battery and it works fine. I just got the new battery because I believe the older battery is losing capacity. The old battery has worked perfectly from the first day of use. Not so with the new battery. I am not shutting down either the Pi2 or 3 from terminal but from the Shutdown menu within the OS. Even doing a Reboot starts a Reboot cycle until I pull the power plug.

Thanks for responses,
Larry


Re: Portable Battery Problem

David Cooley
 

You need about 5.1v for the pi.  Is that doing a shutdown -h now?

Sent by MailWise – See your emails as clean, short chats.



-------- Original Message --------
From: "larryiweaver@... [Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@...>
Sent: Friday, May 13, 2016 05:57 PM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: [Raspberry_Pi_4-Ham_RADIO] Portable Battery Problem

 

Some months back I purchased a new Anker 13000 MAh battery to replace an aging smaller capacity battery. The purpose of both batteries is to recharge tablets and to power a Raspberry Pi while mobile. When I finally got around to using the new battery to power the Pi I found that I could not shut the Pi down. Both a Pi 2B and a Pi 3 will just cycle a reboot over and over but will not shut down without pulling the power. The older battery never gave me any problems. They are both 5V batteries of different MAh ratings. Anyone have an idea as to what could cause this behavior? I would buy a different battery but how would I know if I would have the same problem with another battery.


Thanks,

Larry 


Re: Portable Battery Problem

Clark Martin
 

Do you still have the old battery?  I would reconnect it and see if you have the same behavior.  There is no likely reason for the battery to cause this.  More likely there was some change in the Pi's configuration that caused it.

Clark Martin

KK6ISP

Yet another designated driver on the information super highway.


On May 13, 2016, at 5:57 PM, larryiweaver@... [Raspberry_Pi_4-Ham_RADIO] <Raspberry_Pi_4-Ham_RADIO@...> wrote:

 

Some months back I purchased a new Anker 13000 MAh battery to replace an aging smaller capacity battery. The purpose of both batteries is to recharge tablets and to power a Raspberry Pi while mobile. When I finally got around to using the new battery to power the Pi I found that I could not shut the Pi down. Both a Pi 2B and a Pi 3 will just cycle a reboot over and over but will not shut down without pulling the power. The older battery never gave me any problems. They are both 5V batteries of different MAh ratings. Anyone have an idea as to what could cause this behavior? I would buy a different battery but how would I know if I would have the same problem with another battery.



Portable Battery Problem

Larry Weaver
 

Some months back I purchased a new Anker 13000 MAh battery to replace an aging smaller capacity battery. The purpose of both batteries is to recharge tablets and to power a Raspberry Pi while mobile. When I finally got around to using the new battery to power the Pi I found that I could not shut the Pi down. Both a Pi 2B and a Pi 3 will just cycle a reboot over and over but will not shut down without pulling the power. The older battery never gave me any problems. They are both 5V batteries of different MAh ratings. Anyone have an idea as to what could cause this behavior? I would buy a different battery but how would I know if I would have the same problem with another battery.


Thanks,

Larry 


TeamViewer for Pi

Steve Black
 


Re: Puppy on a RPI 2+

Marty Hartwell
 

On 05/03/2016 10:29 AM, David Ranch dranch@trinnet.net
[Raspberry_Pi_4-Ham_RADIO] wrote:


Hello Marty,

I hadn't even considered a bad port on the Pi
It happens.. after all, what do you expect for $35?


I did test the cable and continuity tested good, however I
did try another one just in case, I didn't think there would be a
difference, I had use a different cable before with the same results
Continuity tests aren't nearly enough to really test an Ethernet cable
as there is so much more to Ethernet than that. I assume the other
cable you tried was from a computer that was already working? It has
all 8 conductors in the RJ45 connector, etc?
Yes working fine on a laptop that is being used as shack computer
currently running fldigi, flrig and
recently compiled Flnet and trying to see if I can figure it out, the
flnet manual is a little confusing to me
right now but I should be able to get it down.

But from past experience I am not sure I want to try to work with the
Comcast
Yeah.. I don't blame you


technical support. I will just purchase a USB wi-fi of my own, I
probably will want one anyway eventually.
Please note that the Raspberry Pi series of little computers can be
rather sensitive to the various wireless adapters out there as well as
their power draw. I would personally recommend that you connect any
wireless adapter through a POWERED usb hub. A good place to start for
wireless adapters is say:

https://www.adafruit.com/category/105

another excellent list of validated devices (USB, SD cards, etc) is:

http://elinux.org/RPi_VerifiedPeripherals


I have started on setting up this Pi and compile Fldigi and it's suite
of code to try a small compact digital
station, I not sure that I can do any better than just a small laptop
could but it will be somewhat fun anyway.
Yup.. there are lots of people on linuxham@yahoogroups.com that are
doing this. That would be the best place to get Fldigi help.
Yes I am a member there too.

I am one of those few people that don't mind doing trouble shooting on
PC's or rigs, I usually learn a lot more
if it doesn't go so smoothly the first few times.
That's absolutely the best approach. Linux is very flexible and
powerful, built by volunteers but with all that comes complexity a
difficulty.


Thanks for your help here, I may end up getting another Pi sometime
later, and see if that one works on my
cable network, but I won't hold my breath, now that the Pi 3 is out I
may run into a cheap Pi2 if so I will try it .
Yes.. very true and Rpi v3 has built-in Wifi. Btw, being a HAM,
you'll appreciate this but that little Wifi antenna on the Rpi v3
would be no match for say an USB Wifi dongle like:

https://www.adafruit.com/products/1030
Yes that looks nice, and I wonder if a person could use one of those and
connect a Pi through a mesh network.
That might be a nice thing to try on one of our SET exercises sometime.
I will have to ask our resident mesh
experts we have in the club.


Well going up to run those other commands you wanted see results from
earlier.


--David
KI6ZHD


New file uploaded to Raspberry_Pi_4-Ham_RADIO

Raspberry_Pi_4-Ham_RADIO@...
 

Hello,


This email message is a notification to let you know that
a file has been uploaded to the Files area of the Raspberry_Pi_4-Ham_RADIO
group.


File : /HSMM/23a-High Speed Multimedia Working Group.pdf
Uploaded by : n9lya <n9lya@nwcable.net>
Description :


You can access this file at the URL:
https://groups.yahoo.com/neo/groups/Raspberry_Pi_4-Ham_RADIO/files/HSMM/23a-High%20Speed%20Multimedia%20Working%20Group.pdf


To learn more about file sharing for your group, please visit:
https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398


Regards,


n9lya <n9lya@nwcable.net>


Re: Puppy on a RPI 2+

Marty Hartwell
 

Ok, will try it out tonight.
Marty

On 05/03/2016 02:54 PM, David Ranch dranch@trinnet.net [Raspberry_Pi_4-Ham_RADIO] wrote:


Hey Marty,

I have a suspicion of what's going on here (your subnet masks are somehow wrong on wired (/8 for IPv4 and /128 for IPv6) but could you send me the output of the following commands when your RPi is *working via wireless*?

lsmod
ifconfig -a

arp -an
ip -4 route route
ping -c 5 10.0.0.1

ip -6 neigh show
/sbin/ip -6 route show
ping6 -c 5 fe80::7454:7dff:fe9f:ab0d%eth0

cat /etc/gai.conf
cat /etc/network/interfaces

cat /etc/resolv.conf
#see if dhcpcd is running or not
ps aux | grep dh

--David



Re: Puppy on a RPI 2+

David Ranch <dranch@...>
 


Hey Marty,

I have a suspicion of what's going on here (your subnet masks are somehow wrong on wired (/8 for IPv4 and /128 for IPv6) but could you send me the output of the following commands when your RPi is *working via wireless*?

lsmod
ifconfig -a

arp -an
ip -4 route route
ping -c 5 10.0.0.1

ip -6 neigh show
/sbin/ip -6 route show
ping6 -c 5 fe80::7454:7dff:fe9f:ab0d%eth0

cat /etc/gai.conf
cat /etc/network/interfaces

cat /etc/resolv.conf
#see if dhcpcd is running or not
ps aux | grep dh

--David



Re: Puppy on a RPI 2+

David Ranch <dranch@...>
 


Hello Marty,

 

I hadn't even considered a bad port on the Pi

It happens.. after all, what do you expect for $35?


I did test the cable and continuity tested good, however I
did try another one just in case, I didn't think there would be a
difference, I had use a different cable before with the same results


Continuity tests aren't nearly enough to really test an Ethernet cable as there is so much more to Ethernet than that.  I assume the other cable you tried was from a computer that was already working?  It has all 8 conductors in the RJ45 connector, etc?


But from past experience I am not sure I want to try to work with the Comcast


Yeah.. I don't blame you


technical support. I will just purchase a USB wi-fi of my own, I
probably will want one anyway eventually.


Please note that the Raspberry Pi series of little computers can be rather sensitive to the various wireless adapters out there as well as their power draw.  I would personally recommend that you connect any wireless adapter through a POWERED usb hub.  A good place to start for wireless adapters is say:

   https://www.adafruit.com/category/105

another excellent list of validated devices (USB, SD cards, etc) is:

   http://elinux.org/RPi_VerifiedPeripherals


I have started on setting up this Pi and compile Fldigi and it's suite
of code to try a small compact digital
station, I not sure that I can do any better than just a small laptop
could but it will be somewhat fun anyway.


Yup.. there are lots of people on linuxham@... that are doing this.  That would be the best place to get Fldigi help.


I am one of those few people that don't mind doing trouble shooting on
PC's or rigs, I usually learn a lot more
if it doesn't go so smoothly the first few times.


That's absolutely the best approach.  Linux is very flexible and powerful, built by volunteers but with all that comes complexity a difficulty. 


Thanks for your help here, I may end up getting another Pi sometime
later, and see if that one works on my
cable network, but I won't hold my breath, now that the Pi 3 is out I
may run into a cheap Pi2 if so I will try it .


Yes.. very true and Rpi v3 has built-in Wifi.  Btw, being a HAM, you'll appreciate this but that little Wifi antenna on the Rpi v3 would be no match for say an USB Wifi dongle like:

  https://www.adafruit.com/products/1030  

--David
KI6ZHD


Re: installing RTL-SDR onto pi

David Ranch <dranch@...>
 

Hello Robert,

I can't speak for multimon-ng which I'm sure is a fine program but I doubt it can match Direwolf's heuristics in improving weak APRS packet decodes. Direwolf also gives clear descriptions of the heard symbols, etc Give the Direwolf + RTL Dongle document a read:

https://github.com/wb2osz/direwolf/blob/1.3/doc/Raspberry-Pi-SDR-IGate.pdf

You essentially run it just like how you ran multimon-ng in this email thread

--David


Re: installing RTL-SDR onto pi

David Cooley
 

That's the pipe symbol.  It's actually 2 vertical lines.  On the US keyboards it's usually the rightmost key above enter

Sent by MailWise – See your emails as clean, short chats.



-------- Original Message --------
From: "'Robert' rbaker@... [Raspberry_Pi_4-Ham_RADIO]" <Raspberry_Pi_4-Ham_RADIO@...>
Sent: Monday, May 2, 2016 08:11 PM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] installing RTL-SDR onto pi

 

Further to this, have since been able to get it working by adding more in the line

cmake ../ -DINSTALL_UDEV_RULES=ON -DDETACH_KERNEL_DRIVER=ON

 

Now I start doing the APRS side of it. Up to trying the following line, but can find what the symbol is infront of multimon-ng, it just looks like a line straight up and down.

 

 

rtl_fm -f 144.390M -s 22050 -p 2 -g 42.0 - | multimon-ng -a AFSK1200 -A -t raw -

Sorry for been a pain.

 

Cheers

 

Robert

 

 

From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
Sent: Tuesday, 3 May 2016 11:30 AM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] installing RTL-SDR onto pi

 

 

Hi All again.

 

Ok, restarted from scratch, and all went good until I did a rtl_test.

Now I get the following:

Found 1 device(s):

0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM

 

Kernel driver is active, or devic is claimed by second instance of librtlsdr.

In the first case, please either detach or blacklist the kernel module (dvd_usb_rtl28xxu), or enable automatic detaching at compile time.

 

Usb_claim_interface error -6

Failed to open rtlsdr device #0

 

I originally at in the blacklist.config:

Blacklist dvb_usb_rtl28xxu

Blacklist rtl_2832

Blacklist rtl_2830

 

But then removed them from the config when I got this error first, but made no difference.

 

Cheers

 

Robert

 

From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
Sent: Friday, 29 April 2016 3:19 AM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] installing RTL-SDR onto pi

 

 



Hello Robert,

I'm wondering why you don't just do:

apt-get install rtl-sdr

Best regards,
Larry
WB6BBB

On 28 Apr 2016 00:14:14 -0700, "rbaker@... [Raspberry_Pi_4-Ham_RADIO]"
<Raspberry_Pi_4-Ham_RADIO@...> wrote:

>Hi All.
>
> Now, installing the rtl-sdr info, but got a fair way through the instalation, but cant do a cmake bit.
>
> This is what Im doing.
>
> sudo nano /etc/modprobe.d/raspi-blacklist.conf
> Add the following lines to the end of the file so the OS does not load the default drivers for the dongle
> blacklist dvb_usb_rtl28xxu
> blacklist rtl_2832
> blacklist rtl_2830
> Reboot
> sudo reboot
> Create a directory for the new RTL software
> mkdir ~/rtl
> Install new rtl driver and software
> cd ~/rtl
> sudo apt-get install git build-essential cmake libusb-1.0-0-dev
> sudo git clone git://git.osmocom.org/rtl-sdr.git
> cd rtl-sdr
> mkdir build
> cd build
> cmake .. -DINSTALL_UDEV_RULES=ON
> make
> sudo make install
> sudo ldconfig
> Install Sox (this will help further test and troubleshoot the SDR RTL dongle)
> sudo apt-get install sox
>
> But I get to cmake .. -DINSTALL_UDEV_RULES=ON but get and error, not letting me to continue.
>
> Any suggestion what I may be doing wrong
>
> Regards
>
> Robert
>


Re: Puppy on a RPI 2+

Marty Hartwell
 

For got to say that zI will try this out maybe this evening, I will be
up in the shack for ARES net tonight.


Marty


On 05/02/2016 09:30 PM, David Ranch dranch@trinnet.net
[Raspberry_Pi_4-Ham_RADIO] wrote:


Wow.. that's rather interesting Marty! I don't know what to say other
than either you have a bad ethernet port or a bad ethernet cable. I
have ONCE seen a similar issue with a bad ethernet cable where pings
would work but FTP would not. Strange as it sounds, it was very
reproducible. Just for giggles on your WIRED connection, try the
following command that sends PING pings:

ping -s 1500 10.0.0.1

Does that work?

--David


Re: Puppy on a RPI 2+

Marty Hartwell
 

Hi


I hadn't even considered a bad port on the Pi, I did test the cable and
continuity tested good, however I
did try another one just in case, I didn't think there would be a
difference, I had use a different cable before
with the same results. I still think it is some setting somewhere that
is being caused by the odd Comcast
router I seem to have here. But from past experience I am not sure I
want to try to work with the Comcast
technical support. I will just purchase a USB wi-fi of my own, I
probably will want one anyway eventually.


I have started on setting up this Pi and compile Fldigi and it's suite
of code to try a small compact digital
station, I not sure that I can do any better than just a small laptop
could but it will be somewhat fun anyway.


I am one of those few people that don't mind doing trouble shooting on
PC's or rigs, I usually learn a lot more
if it doesn't go so smoothly the first few times.


Thanks for your help here, I may end up getting another Pi sometime
later, and see if that one works on my
cable network, but I won't hold my breath, now that the Pi 3 is out I
may run into a cheap Pi2 if so I will try it .


Marty


PS. If you run across something that you think might help let me know
and I can try it out easy enough.


On 05/02/2016 09:30 PM, David Ranch dranch@trinnet.net
[Raspberry_Pi_4-Ham_RADIO] wrote:


Wow.. that's rather interesting Marty! I don't know what to say other
than either you have a bad ethernet port or a bad ethernet cable. I
have ONCE seen a similar issue with a bad ethernet cable where pings
would work but FTP would not. Strange as it sounds, it was very
reproducible. Just for giggles on your WIRED connection, try the
following command that sends PING pings:

ping -s 1500 10.0.0.1

Does that work?

--David


Re: Puppy on a RPI 2+

Brian D Heaton
 

A better question might be if you get IPv6 addresses on the wifi connection and if the NAT is treated differently. I've seen some strangeness with provider IPv6 (mainly Comcast on Comcast-provided modem/router combos).

Cranking up the packet size on pings to the local gateway is a good first step. Since the same packet sizes were used in earlier pings from the RPI to the gateway (wired - works) and to 8.8.8.8 (beyond the router - doesn't work), I will be surprised if the "-s 1500" pings to the gateway fail.

This issue smells like a routing/NAT issue with a dash of IPv6 strangeness.

-Brian


On 5/2/2016 19:30, David Ranch dranch@... [Raspberry_Pi_4-Ham_RADIO] wrote:
 


Wow.. that's rather interesting Marty!  I don't know what to say other than either you have a bad ethernet port or a bad ethernet cable.  I have ONCE seen a similar issue with a bad ethernet cable where pings would work but FTP would not.  Strange as it sounds, it was very reproducible.  Just for giggles on your WIRED connection, try the following command that sends PING pings:

   ping -s 1500 10.0.0.1

Does that work?

--David



Re: installing RTL-SDR onto pi

Rob Baker
 

Further to this, have since been able to get it working by adding more in the line

cmake ../ -DINSTALL_UDEV_RULES=ON -DDETACH_KERNEL_DRIVER=ON

 

Now I start doing the APRS side of it. Up to trying the following line, but can find what the symbol is infront of multimon-ng, it just looks like a line straight up and down.

 

 

rtl_fm -f 144.390M -s 22050 -p 2 -g 42.0 - | multimon-ng -a AFSK1200 -A -t raw -

Sorry for been a pain.

 

Cheers

 

Robert

 

 

From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
Sent: Tuesday, 3 May 2016 11:30 AM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] installing RTL-SDR onto pi

 

 

Hi All again.

 

Ok, restarted from scratch, and all went good until I did a rtl_test.

Now I get the following:

Found 1 device(s):

0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM

 

Kernel driver is active, or devic is claimed by second instance of librtlsdr.

In the first case, please either detach or blacklist the kernel module (dvd_usb_rtl28xxu), or enable automatic detaching at compile time.

 

Usb_claim_interface error -6

Failed to open rtlsdr device #0

 

I originally at in the blacklist.config:

Blacklist dvb_usb_rtl28xxu

Blacklist rtl_2832

Blacklist rtl_2830

 

But then removed them from the config when I got this error first, but made no difference.

 

Cheers

 

Robert

 

From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
Sent: Friday, 29 April 2016 3:19 AM
To: Raspberry_Pi_4-Ham_RADIO@...
Subject: Re: [Raspberry_Pi_4-Ham_RADIO] installing RTL-SDR onto pi

 

 



Hello Robert,

I'm wondering why you don't just do:

apt-get install rtl-sdr

Best regards,
Larry
WB6BBB

On 28 Apr 2016 00:14:14 -0700, "rbaker@... [Raspberry_Pi_4-Ham_RADIO]"
<Raspberry_Pi_4-Ham_RADIO@...> wrote:

>Hi All.
>
> Now, installing the rtl-sdr info, but got a fair way through the instalation, but cant do a cmake bit.
>
> This is what Im doing.
>
> sudo nano /etc/modprobe.d/raspi-blacklist.conf
> Add the following lines to the end of the file so the OS does not load the default drivers for the dongle
> blacklist dvb_usb_rtl28xxu
> blacklist rtl_2832
> blacklist rtl_2830
> Reboot
> sudo reboot
> Create a directory for the new RTL software
> mkdir ~/rtl
> Install new rtl driver and software
> cd ~/rtl
> sudo apt-get install git build-essential cmake libusb-1.0-0-dev
> sudo git clone git://git.osmocom.org/rtl-sdr.git
> cd rtl-sdr
> mkdir build
> cd build
> cmake .. -DINSTALL_UDEV_RULES=ON
> make
> sudo make install
> sudo ldconfig
> Install Sox (this will help further test and troubleshoot the SDR RTL dongle)
> sudo apt-get install sox
>
> But I get to cmake .. -DINSTALL_UDEV_RULES=ON but get and error, not letting me to continue.
>
> Any suggestion what I may be doing wrong
>
> Regards
>
> Robert
>


Re: Puppy on a RPI 2+

David Ranch <dranch@...>
 


Wow.. that's rather interesting Marty!  I don't know what to say other than either you have a bad ethernet port or a bad ethernet cable.  I have ONCE seen a similar issue with a bad ethernet cable where pings would work but FTP would not.  Strange as it sounds, it was very reproducible.  Just for giggles on your WIRED connection, try the following command that sends PING pings:

   ping -s 1500 10.0.0.1

Does that work?

--David

8041 - 8060 of 14061