Date: Tue, 02 Dec 2014 12:15:13 -0500 From: Eric Gunther <egunther@warwick.net> To: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi composite video problem Message-ID: <1417540513.19371.1.camel@warwick.net> In-Reply-To: <20141129105210.5a72a8ec@X220.alogt.com> References: <1417167767.23507.2.camel@warwick.net> <1417193156.3202.1.camel@warwick.net> <20141129084900.10050d11@X220.alogt.com> <1417229109.1835.2.camel@warwick.net> <20141129105210.5a72a8ec@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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 OK, so I can get a somewhat dependable situation with ssh, and it is much more comfortable than before to be able to see the files I am editing. I am typing this on a OpenSUSE 13.2 x86_64 computer, I think that maybe I am having configuration trouble on this end. If I plug into the internet so that the computer establishes a connection then plug the Pi in it persists. ********************** ********* BUT, I have to reiterate, that this is not my issue. I am hoping that someone here could help with the text being mis-formatted or mis-configured for the tv. I have tried /boot/msdos/config.txt Have tried framebuffer settings --- unreadable or still off screen Have tried overscan settings --- no useable change Have not tried firmware FreeBSD-10.1-RELEASE-arm-armv6-RPI-B.img Thanks for any help, --e
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1417540513.19371.1.camel>