Re: ODROID XU4 and UEFI - Re: Cautionary tale: how to kill an SDCard with one simple command
On Wednesday 25 July 2018 00:49:55 Brian Sammon wrote:
> On Sat, 21 Jul 2018 15:42:41 -0400
>
> Gene Heskett <gheskett@shentel.net> wrote:
> > > https://odroidinc.com/products/odroid-xu4
> >
> > I have one, bricked, it has a uefi bios and at the time, the linux
> > installer had no clue how to deal with it. The only option I could
> > find in the bios was to disable the tcp chip, which bricked it, and
> > a jtag programmer and adapter worth more than the odroid is required
> > to restore it. This is NOT mentioned ANYPLACE is the sales
> > propaganda on their site or in this link. Had they not been drinking
> > the windows koolaid, it
>
> I'm a little confused by this. Are you saying that they put UEFI on
> the ODROID XU4 so that it could run Windows? As you said, this is not
> mentioned anyplace in the marketing info, but I can't find it
> mentioned anywhere else either. I also see no claims that the XU4
> could run Windows.
>
> Did you ever discuss this with Hardkernel (preferably in a public
> forum like https://forum.odroid.com/)? Did they acknowledge or deny
> the UEFI situation?
They acknowledged it, and told me how to fix it, but the fix cost more
than the odroid, a jtag programmer and a special cable that cost well
over $125 is required. And someone else recently advised me that UEFI
bypassing in the bios was only legal on x86 stuffs. If thats so, I'd
push for legislation to outlaw the whole concept as it is unfair
competition to me, and microsoft should owe damages to everyone that got
burnt as I did. In any event, I've not been back to their site and if
they starve I could care less. Get screwed once, shame on them, twice,
shame on me.
The only possible mention is at
<https://forum.odroid.com/viewtopic.php?f=138&t=20593>
Smarter folks than I might be able to build a workaround, but they were
pretty carefull how that subject was covered. u-boot might be able to
deal with it, but I haven't studied up on that enough to say. The rock64
gets around it but I've no clue how that works either.
I have successfully built the linux-rt kernels on both the pi and the
rock64, but now I cannot find a utility that will actually update the sd
cards boot code to install the replacement code, and questions about how
to do this seem to be ignored on all the revelant forums. zero answers
other than a few links to code from 2011 & 2012 that seems to be
unrelated have been supplied. I do know that dpkg knows how to deal with
it as I've seen its onscreen log while doing it on the rock64, but it
doesn't seem to be covered in the dpkg man pages. Also a stumbling
block, make doesn't know how to "make" a vmlinuz, only huge vmlinux, and
no initrd's. But I have made those. example:
ls -l /media/slash/v4.16.18-rt10/
total 798300
drwxr-xr-x 33 gene gene 4096 Jul 20 00:42 arch
drwxr-xr-x 3 gene gene 4096 Jul 21 07:08 block
-rw-r--r-- 1 gene gene 744766 Jul 21 08:08 built-in.o
drwxr-xr-x 2 gene gene 4096 Jul 21 06:52 certs
-rw-r--r-- 1 gene gene 148020 May 27 18:39
config-4.4.126-rockchip-ayufan-239
-rw-r--r-- 1 gene gene 18693 Jul 20 00:42 COPYING
-rw-r--r-- 1 gene gene 98556 Jul 20 00:42 CREDITS
drwxr-xr-x 4 gene gene 12288 Jul 21 08:15 crypto
drwxr-xr-x 125 gene gene 12288 Jul 21 18:47 Documentation
drwxr-xr-x 136 gene gene 4096 Jul 21 08:08 drivers
drwxr-xr-x 2 gene gene 4096 Jul 21 07:11 firmware
drwxr-xr-x 73 gene gene 12288 Jul 21 07:40 fs
drwxr-xr-x 29 gene gene 4096 Jul 20 16:52 include
drwxr-xr-x 2 gene gene 4096 Jul 21 08:08 init
drwxr-xr-x 2 gene gene 4096 Jul 21 07:03 ipc
-rw-r--r-- 1 gene gene 2245 Jul 20 00:42 Kbuild
-rw-r--r-- 1 gene gene 287 Jul 20 00:42 Kconfig
drwxr-xr-x 17 gene gene 12288 Jul 21 07:03 kernel
drwxr-xr-x 13 gene gene 20480 Jul 21 08:15 lib
drwxr-xr-x 5 gene gene 4096 Jul 20 00:42 LICENSES
-rw-r--r-- 1 gene gene 446794 Jul 20 00:42 MAINTAINERS
-rw-r--r-- 1 gene gene 62082 Jul 20 00:42 Makefile
drwxr-xr-x 3 gene gene 12288 Jul 21 06:57 mm
-rw-r--r-- 1 gene gene 19130 Jul 21 06:51 modules.builtin
-rw-r--r-- 1 gene gene 27819 Jul 21 08:10 modules.order
-rw-r--r-- 1 gene gene 637973 Jul 21 08:10 Module.symvers
drwxr-xr-x 68 gene gene 4096 Jul 21 07:59 net
-rw-r--r-- 1 gene gene 148020 May 27 18:39 oldconfig
-rw-r--r-- 1 gene gene 722 Jul 20 00:42 README
drwxr-xr-x 28 gene gene 4096 Jul 20 00:43 samples
drwxr-xr-x 14 gene gene 4096 Jul 21 06:51 scripts
drwxr-xr-x 10 gene gene 4096 Jul 21 07:04 security
drwxr-xr-x 25 gene gene 4096 Jul 21 07:11 sound
-rw-r--r-- 1 gene gene 3918000 Jul 21 08:10 System.map
drwxr-xr-x 31 gene gene 4096 Jul 20 00:43 tools
drwxr-xr-x 2 gene gene 4096 Jul 21 06:51 usr
drwxr-xr-x 4 gene gene 4096 Jul 21 07:48 virt
-rwxr-xr-x 1 gene gene 220318224 Jul 21 08:10 vmlinux
-rw-r--r-- 1 gene gene 590810760 Jul 21 08:09 vmlinux.o
It took something just over 1 hour to build that on the rock64. On an
120GB SSD mounted to /media/slash via a sata to usb-3 adapter, so I
wasn't beating the sd card to death. What I'd like to do is copy that sd
to the eMMC module, plugged in but empty ATM and do the installs to the
eMMC memory, so it boots from a known good boot, but will use the eMMC
as the bootable medium if the sd card is removed. That way I'd have a
fallback rescue path if the install on the eMMC card is broken. Just
plug the sd card back in and push the power button.
Perhaps I am a dreamer?
--
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>
Reply to: