Raspberry Pi composite video problem

[Eric Gunther]

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 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?