On Sunday 28 May 2017 07:53:32 Mark wrote:

> On 05/28/2017 01:00 AM, Gene Heskett wrote:
> > Unforch, with that in the box, I'd have to buy another box to put
> > the 7i90 and 7i42TA's in. And eventually I am out of space behind
> > the lathe. Not to mention the board might be $65, but memory for it,
> > and a psu that might fit in this nice new box, and I'm north of an
> > additional $200 to switch back to a wintel system and a fight to get
> > it installed with the UEFI bios.  I thought of that when I bought an
> > "up" board with a quad core atom on it, no bigger than the pi. But
> > it comes with a UEFI bios enabled so you can only install windows 10
> > on it, and if you turn off the UEFI, you've bricked the SOB, and I
> > am not about to throw another $350 in a jtag programmer and 50 more
> > for the flashrom clipon just to rescue a 100 dollar board. UEFI is
> > something microsoft shoved down our throats in another attempt to
> > create a captive customer. Why the industry as a whole, didn't sue
> > them out of existence is beyond me. They promised it could be turned
> > off if you wanted to install something else, but they by damn didn't
> > tell American Megatrends it had to work if it was turned off.
> >
> > Just one of the reasons there are only glass windows in this house.
> >
> > I'll stop before the air gets even bluer.
> >
> > Cheers, Gene Heskett
>
> Never had any issues installing Linux of various flavors on a desktop
> or server with UEFI.  Course I dealt mainly with Dell and HP servers
> and desktops.  This was at work at the Lab.  And this HP laptop I'm
> typing this email on has UEFI.  Not sure why you need to disable the
> UEFI to attempt to install Linux.  Methinks these injuries are mainly
> self-inflicted for no apparent reason.
>
> Mark
>
I fixed a usb disk intended for a backup usage, up with the debian 8 
installer. It would not even admit the disk was plugged in. It looked at 
it, as evidenced by a couple flickers of the access light on the disk 
housing, but wouldn't touch it with a 20 foot pole.  I did the same 
thing with a 32Gb u-sd card, didn't recognize it.  I finally found the 
bios access key (no docs to be had, in the box or online that I could  
find, tried to join their forum, three times, never received the 
confirmation message) The forum messages I did read were mostly people 
bitching about the lack of support.

Wandering thru the bios looking for the UEFI disabler, which I never 
found in so many words, the only thing related was an option to disable 
the TCP chip, so I did.  Bricked it. A jtag programmer is the only way 
to recover. $400 to reboot a $100 computer? Screwem, and the camel that 
rode in on them.

If I could find another quad core atom powered board, no bigger than the 
pi, and whose forum showed some support in the form of answered 
questions, I might take another stab at it, but I've probably thrown a 
thousand or more at this pi scene and had it working very well, but a 
firmware update applied by rpi-update has made me start from scratch 
several times since the 2nd of May. That fixed the piss-poor keyboard 
response problems. Now if I can fix the spi clocking problems, and 
figure out a way to make dpkg understand the kernel version is pinned, I 
should be good to go again. I think I'd do as a previous install did, 
name the kernel and kernel7 images with unique names, and specify, in 
boot/config.txt, the kernel its supposed to boot. Then apt, apt-get, and 
dpkg can shovel shit around in the /boot tree to their hearts content 
and my realtime kernel will still be there.

Each one of these experiences is a learning event. The problem is as much 
my poor short term memory as anything else. But as soon as I put 
something in Dee's tummy for breakfast, that unique kernel name will be 
put into effect. The next thing in this recovery is to install an even 
newer rt kernel that fixes the keyboard problems.  That renaming may be 
the best way to pin it.

Cheers Mark, 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to