[mythtv-users] Installation report: ECS Liva doesn't boot after Debian Installation. What am I missing?

[Hika van den Hoven]

Hoi Damian,

Thursday, May 14, 2015, 1:35:53 AM, you wrote:

> On 13/05/2015 19:59, Hika van den Hoven wrote:
>> Hoi Damian,
>>
>> Wednesday, May 13, 2015, 8:36:13 PM, you wrote:
>>
>>
>>>>> For my scenario--which again, involves just a kernel with built-in
>>>>> command line and no boot loader--I needed a small FAT32 partition on
>>>>> which to locate the kernel (/dev/mmcblk0p2 on mine). The device
>>>>> finds that partition and boots the kernel. I believe a similar
>>>>> partition is needed even if you use a boot loader, however, and it
>>>>> is on that partition where your bootloader files are to be kept
>>>>> (usually it's mounted under /boot). This small FAT32 partition is
>>>>> apparently stipulated in the UEFI spec, so unless you intend to boot
>>>>> and run your system in BIOS compatibility mode, it is my (not
>>>>> terribly well informed) understanding you'll need to create that
>>>>> partition before you'll get this to work.
>>>> I think you're right.  The Debian installer took care of convincing me
>>>> to do so before letting me go any further.
>>>>
>>>> This is what the SSD partitioning looks like now:
>>>>
>>>> #1      primary 38.8 MB B f ESP
>>>> #5      logial  31.2 GB   f ext4        /
>>>>
>>>> Like I said in the other sub-thread, the system boots fine now.
>>>>
>>>> So, Kudos to the debian-installer team.  If it had not been for my UEFI
>>>> ignorance, it would have gone well the first time.
>>>>
>>>> Augustine
>>> The UEFI thing caught me out initially too, but I worked it out in the end.
>>
>>> My Liva is running MythBuntu great!
>>
>>> One niggle I have got is that it seems to struggle if my projector is
>>> off when the Liva is turned on. When I do then turn the projector on, it
>>> can't find a signal. I think it's also lost the signal once or twice
>>> when the system has been left on and inactive for a while. Not much of a
>>> problem, but if anyone has found a fix for that I'd love to hear it!
>>
>>> Damian
>>> _______________________________________________
>>
>> How about explicitly enabling the videoport on moduleload, add to the
>> loadstring: `video=hdmi:e`
>> You need to have KMS enabled. so add `modeset=1` to your kernel
>> loadstring.
>> hdmi is a guess at the portname. It can be hdmi-0 or hdmi-1. You
>> should find it in your boot log.

> Thanks Hika,

> I have no idea what or where 'loadstring' is, but I will look it up! :-)

> Thanks again,
> Damian
> _______________________________________________

The kernel loadstring is in your bootloader, bootstrings for modules
are probably in /etc/modprobe.d/ but it can vary by distribution. Look
in there for a file nvidia.conf or intel.conf or whatever graphic
driver you're using. It's a string of parameters to give to your
kernel or kernelmodule when loading. modeset enables KMS (Kernel Mode
Setting) enabling at runtime control by the kernel over your graphics
settings. `video=hdmi:e` enables the given port while `video=hdmi:d`
disables it. Not depending on a probe whether there is something at
the other end. Very handy for dumb screens like old TV's or when it's
not always on.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens