Posts by dipswitch

Just tested it with my spo-comm minipc. Wont boot. See this thread: thread-6041.html

Quote from vitorp07

Did you test if @piotrasd's build can boot on your hardware?
thread-1266-post-12814.html#pid12814

Just tested it. It wont boot from that release either

I flashed the latest build, but the the remote still isnt working (mxiii-1gb). Do i need to copy a remote.conf file? And if so, where do i find the remote.conf for the mxiii-1gb?

Quote from Demetris

Will release a new build to fix remotes then when I have time I will see if I can help you

Sent from the Island of Venus

Thanks! Can you also add support for mce remote again?

Quote from Skripo

While booting, my screen displays all the boot commands that are being executed. What command do I need to execute to turn off verbose boot?

I've noticed this only on the 802 builds. 805 seems fine.

I found out that, when the remote isnt working anymore after a update, you need to copy te remote.conf file to the configfiles smb share on the device. This is when LE is installed to internal storage. I immediately believe this is common practice but, maybe it can be mentioned in the first post, in order for people not having to search/experiment with this. Just my two cents..

Quote from lrusak

You can do it using grub2, however, we use syslinux.

When grub2 is able to facilitatie 32bit efi boot (and therefore making LE more universal compatible), is there a reason for sticking with syslinux?

As some forum members probably already noticed, i'm trying to get an industrial minipc to work with LE.

One of the things that keep intervening with good operation of the device, is the lack of support for 32bit efi systems.

Short explanation: EFI is the successor for the old bios based system. This is the first code being loaded once a computer is powered on. EFI (extensible firmware interface) comes in to flavours: 32 and 64bit. Keep in mind: this has nothing to do with the microarchitecture of the computers processor.

Now comes the weird part: there are computers being sold that have modern 64bit (multicore) cpu's, but are fitted with a 32bit efi. This means often that one can't boot 64bit operating systems, even when the cpu supports this. Sometimes this goes in hand with a max memory limitation of, for example, 2gb memory.

For this reason: Microsoft windows 10 comes in multiple bootable versions: both 32 and 64bit for legacy bios systems, and 32 and 64bit for efi systems. So this means that, for a windows system, a pc with 32bit efi can be used to run win10 (probably other versions too).

The problem is that lots of linux distributions, this includes LE, come with only an 64bit efi boot option. The 32bit efi files are not included This means that if you have a 32bit efi, and no option to boot in legacy (CSM/bios) mode, you can't boot LE and therefore arent able to install it.

For my particular case, i've tested a few distro's. None of them came with the necessary 32bit efi boot files.

I've found this article: 32-Bit UEFI Boot Support - Ask Ubuntu

I then copied the bootia32.efi file to the efi folder on the memstick which i had ubuntu on, and it immediately booted fine (64bit ubuntu with 32bit efi boot, nice )

I was hoping the same trick would work for LE, but unfortunately it didn't. So up to this date no 32bit efi booting for LE.

Maybe the developers can find a way to included 32bit efi booting capabilitys for LE?

I found other threads on the forum from people asking for this feature, even developers telling they didn't succeed in making it work. Maybe progress has been made on this matter?

Quote from chewitt

From the logs you've give us it looks like the correct drivers are loaded, Xorg is running, something is being output. If the result is still a black screen I have to guess it's an issue with connectors/cables or something funky about the TV itself. If I had local access to the box to experiment I could test a bit more, but remotely.. I'm out of sensible suggestions. Have you tested with it on a different TV?

I did some more testing, only to conclude that this really is a LE problem. I was able to boot Ubuntu (64bit) , once it booted i gave me no problems whatsoever. I got an instant 1080p60 output over hdmi.

Next up was Knoppix. This also gave me no problems, again 1080p60 over hdmi perfectly. Keep in mind: this all was done with exactly the same hdmi cable and display. The LE problems keep occuring on both a fullhd computer display and my television (panasonic 42" fullhd over hdmi).

What is weird is that LE , once the LE bootlogo disappears and the GUI should appear, it does output a 1080p60 signal over hdmi, but just gives a blank screen. Also the text terminal only displays a blinking cursor, again perfectly in 1080p60.

See attached screenshots for more info.

I was thinking, could it be something else that keeps X from showing the gui? Since everything is working and i've got a 1080p output over hmdi, could it be some hardware component stalling the system?

Quote from chunk1982

Have you tried copying your remote.Config file to the box?

Sent from my SM-G930F using Tapatalk

I'm confused. I thought the remote.conf file procedure was only for s805 builds? Where would i find the remote.conf file for the s802 mxiii-1gb?

I just discovered a strange problem: after upgrading to 8.0.1a my mxiii-1gb only can be controlled with the televisions remote through cec . Both my mce remote and the box's own remote don't work anymore. The red light of the mce remote does flicker when keys are pressed, but the box doesnt respond. Can this be fixed?

Quote from chewitt

jTAXtwo things:

a) cp /etc/x11/xorg-nvidia.conf /storage/.config/xorg.conf .. then edit the file so modedebug is "true" and reboot, then "cat /var/log/Xorg.0.log | paste" again so we can see debug output. There is a single GPU detected, but maybe something is wonky.

b) wget 96-nvidia.rules -O /storage/.config/udev.rules.d/96-nvdia.rules .. then reboot and see if the card prefers the older 340.xx driver instead of the 357.xx one.

jTAX

After the last command, for the old drivers, the result is the same. A blank screen, it does have a output, just nothing in it .

I've added some pics of the device. As you can see theres almost nothing to config in the bios.

Quote from chewitt

Please run "lsmod | paste" and share the URL; let's see if there is more than one GPU detected. If there is and the BIOS doesn't provide options for disabling one of the cards we can blacklist modules to prevent them loading and confusing Xorg.

MhSa

What is weird is that the hdmi output does output a signal, only without "content". So now in test setup it does 1080p/60 on my monitor. And in case of the television it also outputs 1080p.

To sum things up: it seems that the device boot's LE fine, but it only fails to output on hdmi. Could this be an issue duo to it having two gpu's? (intel and nvidia)?

Quote from Nicolas

Do you have the TV connected to your nvidia card via hdmi? If so you could try using a dvi to hdmi adapter.
I have this issue ever since i am using a n3700 board. Over hdmi I don't get a picture with dvi to hdmi everything works.

Also you can check if the nvidia (pcie device) is set as primery display at the bios. You can also try to dissable onboard intel video.

Maybe this will do the trick

The spo comm device has an onboard nvidia gpu, it is not a seperate card. There is only a hdmi and a d-sub output. The phoenix bios of this device is terrible, there is nothing to configure related to the gpu(s). (and nothing related to booting efi/csm :s )
[hr]

Quote from chewitt

It looks like everything is up and working .. run "/usr/lib/kodi/kodi-xrandr | paste" so we can see the Xorg modes available. You can also switch modes by running "xrandr --output HDMI-1 --mode 0x1be" (where 0x1be is a valid mode shortcode). You might need to see if other modes are within range of what the monitor will handle?

DcFW

This is weird: it says DVI-D-0 . The spo comm doesnt have a dvi output.... Or am i misinterpreting (yes im a noob )

xrandr --output HDMI-1 --mode 0x1be results in "warning: output HDMI-1 not found; ignoring"

when i do xrandr --output HDMI-0 --mode 0x1be it results in "xrandr: cannot find mode 0x1be"

Tried xrandr --output HDMI-0 --mode 0x1f5 . This results in nothing, just the prompt, and the screen stays black.

[hr]

Quote from chewitt

If installing on another machine results in something that boots .. do CTL+ALT+F3 on the "hung" screen and you should see a local console (because it hasn't hung, it's just not showing output). At the console run "cat /var/log/Xorg.0.log | paste" and "journalctl -b 0 --no-pager | paste" and share the URL's generated. You should also be able to do "ifconfig" and see the IP address and then SSH in to the box.

Thank you for your reply.

LRTS

NZCP

What happened is: i wasnt able to ssh in to the box, since i couldnt enable ssh in the first welcome screen. I then connected the box not with hdmi but on analalog d-sub vga. It then booted fine, showed the gui, and i was able to enable ssh. Then i shut it down, connected it again through hdmi, and did as you told.

Strangely enough, when connected on hdmi, when i do CTL-ALT-F3, i only get a blinking cursos and no prompt. Typing text also results in nothing.
[hr]

Quote from Klojum

LibreELEC Generic is a full 64-bit build. so if your machine is a 32-bit only box, it wil not only not boot, but also not run the 64bit Linux OS.

FYI, the last 32bit build available is the OpenELEC v5.0.8 build.

The problem is not the cpu's microarchitecture. The Intel D2550 cpu is a multi core 64bit processor. The problem is the bios/efi being not able to boot in 64bit efi, only in 32bit efi. I know, this is weird. But there are more devices that suffer from this issue. For example a budget laptop that i encountered some time ago; had a intel z*** atom with 32bit efi. So it was only able to run 32bit windows even when the cpu was a native 64bit intel cpu. That cpu also had a 2gb memory limit; that is intel preventing that cpu to become "to good". This is why there are 32bit bootable efi media and 64bit bootable efi media.

My Spo Book Nano Ion 3 device, wich is actually a Giadatech MI-D2550GT-R , gives me a lot of pain.

First, it refuses to boot from usb flash drive. As i understand it only supports 32bit efi. Since LE only supports 64bit efi, whatever i try, it refuses to boot. Booting for example knoppix works fine. I have the latest bios revision installed.

Second, when i install LE on its harddrive in another machine, and put de disc back in the ion 3, it boots, shows te LE boot logo, initiates the gui, and then freezes on a black screen (Kodi interface is not seen).

The device holds an Atom D2550 with integrated graphics, and an Nvidia GT610 gpu (yey, motion-adaptive de-interlace ).

Is there any way to get this machine to run LE?

This is the device: spo-comm GmbH spo-book NANO ION3 - Digital Signage Entry Model with NVIDIA Graphics Card

Quote from yonatandror

How to install?

Used the LE USB-SD Creator and yours S82 file.
In the Minix pressed power+reset.
It started some kind of process and immediately threw an error message.
Something with "beyond repair".

Am I doing something wrong?
Do I need to create special boot dir or something?
(I previously installed OE on the Minix).

Update:
I have changed the partition to 0x81 and then I was able to boot and load LE.
I see the main screen but the remote doesn't work (Harmony 650).
It seems something was changed or lost.
Are you familiar with this issue?
I am kinda of stuck now because I cant do anything with the device and menus....

Display More

It seems obvious: when testing new firmware ALWAYS use the original remote. Using a harmony only adds another "uncertainty" in the chain. Also you can plug in a usb keyboard on your device to configure it, for example enable ssh.