Posts by Da Flex

That's great, Denis! Another laptop stays alive.

You can mark the thread as solved now.

RPi and PC are both USB host devices. You want to use your RPi in USB client mode, but that's impossible.

Blacklist the nouveau driver like this:

• mount -o remount,rw /flash

• Open the config file by editor with nano /flash/syslinux.cfg

• Edit the append line like this:

APPEND boot=UUID=<YOUR_BOOT_UUID> disk=UUID=<YOUR_DISK_UUID> quiet initcall_blacklist=nouveau

• Store the config file by key combo STRG + O
  

• Leave the editor by key combo STRG + X

If this doesn't work, try nouveau_init instead of nouveau at the append line.

It's not tested by me, I'm just an RPi user.

PS: Can you post the output of "lsmod" when you're logged in by SSH on LE?

Quote from fichtennadel

This forum is named "Bug Reports", and that's what I did: report a bug.

It's not against the rules to post it here, but personally I would call it a development discussion, which has an own sub-forum.

Development builds usually have bugs. You can use a stable built.

Do you use the right config.txt option?

"Switchable Graphics" doesn't enforces iGPU usage, so it doesn't help.

Maybe chewitt can explain whether the "nouveau" driver has to be blacklisted, or if there is no need to do that, because the driver doesn't exist on LE. I'm asking because setting the eGPU driver on the blacklist usually enforces iGPU usage.

Yes, disable the eGPU in BIOS. You have a good chance to run LE with the iGPU.

That's the relevant driver modules on Ubuntu:

video 49152 3 dell_wmi,dell_laptop,nouveau

Try to load the "nouveau" driver on LE. My research says the driver has issues with Kodi, so it's probably not available on LE for good reasons.

PS: If "nouveau" isn't on LE, it could be a good idea to stay with Ubuntu. When you autostart Kodi on it, you maybe have all you need.

He came from this thread where he said it's OK on Raspbian Buster. I think it's about internal WiFi, because he didn't mentioned an adapter.

Manufacturers often change hardware revisions of some electronic parts. So the explanation you're asking for could be a different hardware revision of your display, compared to the one of add-on developer. Maybe you're lucky, and the necessary changes of the source code are pretty small.

It's very unlikely to find someone with the same hardware here, who solved your issue. The driver of your case display works for most of the output, so I bet it's a driver problem (not fully compatible to your display).

If you have programming skills, you could try to find the source code of the LCDproc add-on, and adapt it for your needs. Because your hardware is quite exotic, I think that's your only option.

OK, then I'm running out of ideas, too. Maybe you still have guarantee, and get a replacement. Try it on a friends TV before you replace it.

Download a full Linux, like Ubuntu, and run it in "live" mode. If everything works, look for the loaded driver modules, and try to load them on LE.

I think that's a good way to figure out the usability of an "old laptop".

Thanks for the tests. I compared your guisettings.xml to mine. I found a difference, which could be the cause:

<setting id="audiooutput.dtspassthrough">true</setting>

Set this setting to false.

LE creates symlinks for all mounts. Some services can't go beyond such a symlink.

chapas :

Does it work if you define two separate buttons instead of one switch button?