From owner-freebsd-arm@FreeBSD.ORG Sat Nov 29 11:49:49 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 271EED55 for ; Sat, 29 Nov 2014 11:49:49 +0000 (UTC) Received: from frontend2.warwick.net (lm-3.warwick.net [204.255.24.103]) by mx1.freebsd.org (Postfix) with SMTP id E05D0CD3 for ; Sat, 29 Nov 2014 11:49:47 +0000 (UTC) Received: (qmail 19337 invoked from network); 29 Nov 2014 11:43:07 -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 frontend2.warwick.net with SMTP (e2b1dd32-77bc-11e4-865f-001f2909bf3e); Sat, 29 Nov 2014 06:43:07 -0500 Message-ID: <1417261402.2448.3.camel@warwick.net> Subject: Re: Raspberry Pi composite video problem From: Eric Gunther To: Erich Dollansky Date: Sat, 29 Nov 2014 06:43:22 -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: e2b1dd32-77bc-11e4-865f-001f2909bf3e 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: Sat, 29 Nov 2014 11:49:49 -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 tried multiple ways of accessing the Pi and have not been able to replicate it (ssh,ftp, or telnet success). I just looked at this post again and saw that you had written a wW (lower case w followed by an uppercase w), which is what I initially thought but in my haste didn't notice on second check. I will respond Monday, after I have had a chance to try again. > > I emphasize that this is to more quickly and efficiently fix > > the display. I realize that you mentioned that you are not able to > > help with the composite video. So no thoughts on whether the > > firmware would help that problem? That is, text off the screen. > > > I have the B+ only. The 10.1 firmware should be able to handle the > older model without a problem. OK, thanks, that is what I expected. Should I start a new thread about the questions I have about the video, considering that I have strayed off the original topic? I will just put my questions below. Thanks, --e > Erich What is the way to adjust the low level video input settings aside from /boot/msdos/config.txt? /boot/msdos/uenv.txt? Do I need to compile a kernel with a console driver, or alternate console driver, to use for the display?