Raspberry Pi composite video problem
Eric Gunther
egunther at warwick.net
Mon Dec 1 08:17:24 UTC 2014
On Sat, 2014-11-29 at 10:52 +0800, Erich Dollansky wrote:
> Hi,
>
> On Fri, 28 Nov 2014 21:45:09 -0500
> Eric Gunther <egunther at warwick.net> wrote:
>
> > On Sat, 2014-11-29 at 08:49 +0800, Erich Dollansky wrote:
> >
> > > On Fri, 28 Nov 2014 11:45:56 -0500
> > > Eric Gunther <egunther at warwick.net> wrote:
> > > .
> > > >
> > > > Eureka, I have logged in via ssh. Not sure what is different
> > > > although the last few things I did where:
> > > >
> > > > rechecked /etc/inetd.conf, /etc/rc.conf, /etc/services
> > > >
> > > > service sshd enable
> > > > service sshd reload
> > > >
> > > > And plugged in the client computer after the RPi had been
> > > > connected to the ethernet, worked using IP.
> > > >
> > > sshd can run without inetd.
> >
> > Thanks for telling me. Funny thing, it stopped working afterward and
> > cannot get it working again (ssh). Getting ssh working was, in a way,
> > beside the point. I would like to figure out how to fix the display
> > issue. If I had a working Ethernet connection to the Pi I could;
> > Download the firmware and put it on, Adjust configuration files
> > easier, and Report dmesg or similar message output to the list as
> > needed.
> >
> just put this into your rc.conf:
>
> inetd_enable="YES"
> inetd_flags="-wW -a whateveraddress"
>
> and this
>
> ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l
> ftp stream tcp6 nowait root /usr/libexec/ftpd ftpd -l
> ssh stream tcp nowait root /usr/sbin/sshd sshd -i -4
> ssh stream tcp6 nowait root /usr/sbin/sshd sshd -i -6
> telnet stream tcp nowait root /usr/libexec/telnetd telnetd
> telnet stream tcp6 nowait root /usr/libexec/telnetd telnetd
>
> into your inetd.conf.
>
> If all other things fail, you should be able to transfer files via ftp
> then.
I can report that I am able to:
ftp via seamonkey(browser) to user account on Pi from Workstation
scp a file from Pi to Workstation (root to user directory, ".txt" file)
ssh login from either direction.
Looks like the most likely problem is that I was using the wrong IP
address. The last part of the notation xx.xx.xxx.xx
^ here
Is different on either machine but the rest is the same. Probably moot
but I thought I might mention it. Anyway it took me a bit to notice the
difference. I used "service ftpd onestart" to get the ftpd to work.
Although this may not have been necessary...
"service -e" did not report enabled ftpd.
I will try again a couple of times to make sure it is not some magic.
Thanks again.
>
> Erich
More information about the freebsd-arm
mailing list