From owner-freebsd-arm@FreeBSD.ORG Tue Dec 2 17:14:55 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B97A3E22 for ; Tue, 2 Dec 2014 17:14:55 +0000 (UTC) Received: from frontend3.warwick.net (mx2.warwick.net [204.255.24.104]) by mx1.freebsd.org (Postfix) with SMTP id 6D5AF6B3 for ; Tue, 2 Dec 2014 17:14:54 +0000 (UTC) Received: (qmail 27036 invoked from network); 2 Dec 2014 17:14:47 -0000 Received: from 70.44.113.83.res-cmts.sefg.ptd.net (HELO 70.44.113.83.res-cmts.sefg.ptd.net) (egunther@warwick.net@70.44.113.83) by frontend3.warwick.net with SMTP (b777bd8a-7a46-11e4-9f9e-0019bb38a71e); Tue, 02 Dec 2014 12:14:47 -0500 Message-ID: <1417540513.19371.1.camel@warwick.net> Subject: Re: Raspberry Pi composite video problem From: Eric Gunther To: freebsd-arm@freebsd.org Date: Tue, 02 Dec 2014 12:15:13 -0500 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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.7 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-MagicMail-UUID: b777bd8a-7a46-11e4-9f9e-0019bb38a71e X-MagicMail-Authenticated: egunther@warwick.net X-MagicMail-SourceIP: 70.44.113.83 X-MagicMail-EnvelopeFrom: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 17:14:55 -0000 > > > 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