From owner-freebsd-arm@FreeBSD.ORG Mon Dec 1 08:17:24 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 0E43042A for ; Mon, 1 Dec 2014 08:17:24 +0000 (UTC) Received: from frontend1.warwick.net (wvtcvoicemail.wvtc.com [204.255.24.102]) by mx1.freebsd.org (Postfix) with SMTP id B61DD29B for ; Mon, 1 Dec 2014 08:17:23 +0000 (UTC) Received: (qmail 16014 invoked from network); 1 Dec 2014 08:17:21 -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 frontend1.warwick.net with SMTP (78f44b2e-7932-11e4-b685-001e0b616b8e); Mon, 01 Dec 2014 03:17:21 -0500 Message-ID: <1417421863.2564.1.camel@warwick.net> Subject: Re: Raspberry Pi composite video problem From: Eric Gunther To: Erich Dollansky Date: Mon, 01 Dec 2014 03:17:43 -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: 78f44b2e-7932-11e4-b685-001e0b616b8e X-MagicMail-Authenticated: egunther@warwick.net X-MagicMail-SourceIP: 70.44.113.83 X-MagicMail-EnvelopeFrom: Cc: freebsd-arm@freebsd.org 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: Mon, 01 Dec 2014 08:17:24 -0000 On Sat, 2014-11-29 at 10:52 +0800, Erich Dollansky wrote: > Hi, > > On Fri, 28 Nov 2014 21:45:09 -0500 > Eric Gunther wrote: > > > On Sat, 2014-11-29 at 08:49 +0800, Erich Dollansky wrote: > > > > > On Fri, 28 Nov 2014 11:45:56 -0500 > > > Eric Gunther 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