On Saturday 13 May 2017 12:27:22 TJoseph Powderly wrote: > gene could you try not changing anything and just boot it > if the basic simple way to initially check it out , doesnt work, > then stop and look at whats going on, > dont change stuff in the beginning > Tomp, I have to fix the network stuff, and while /opt/vc/bin/tvservice does parse the EDID from the monitor, declaring the best for this monitor is 1920x1080, but the pi pays no attention, so I must tell it to boost the hdmi signal a bit, and tell it "hdmi_group=2" and "hdmi_mode=82" before the monitor will stop telling me its not a supported input. So some of this stuff, like actually getting a picture on the monitor, may as well be done up front, along with configuring the network so I can access it from another machine.
The most IMPORTANT part of all that is that once resolv.conf is configured, don't forget to make it immutable with a root chattr +i resolv.conf. If not, it will be cleared on the reboot and the network is dead in the water. I've been doing this for a while. Using hosts files does give me a network with stable addresses, and thats a must here. > i think you'd like to see something just work > > i'd really like you to have success with this > > The UDOO X86 Guide: Chapter One - Basic setup > https://www.youtube.com/watch?v=TBUXpMq06iU > > tomp I've not bought a UDOO. But the up-board, which has more stuff for 40 dollars less money, has I think been damaged, it takes, from a powerdown overnight boot, about 7 minutes to show me the UP logo, and the bios that I was able to get into once yesterday to turn the TCP chip off, is apparently a one way switch because all it will do is show the logo & mouse pointer, no response to any key except ctl-alt-del, which apparently reboots it back to the logo in about 2 seconds max. Bootable usb keys, or bootable usb hard drives, stuck in a usb port are ignored. Always have been. But it looks like I blew about $125 on the up-board. And the forum is loaded by complaints about poor support. So I'm back to seeing if I can make the pi see a keyboard that isn't from this machine. 4 keyboards have been tried on it, and all work alike, shitty lags & no keyup's rx'd about 25% of the time. I have looked at it, on the pi, with the usb tracer. ANAICT (the sd is also on the usb bus and that noise makes it hard to see a keystroke only data burst), but the keyboards are working normally from what I was able to pickout. Yeah, I'd like it to Just Work(TM) too, but this keyboard problem is being a cast iron bitch. We'll see what I do next when the update is done. Thanks Tomp. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
