It's being discussed with the Raspberry Pi developers.
Posts by milhouse
-
-
kappclark Not sure which smb.conf file you are referring to but presumably it's .kodi/.smb/smb.conf which you should not be editing it, as your changes will not be persisted across Kodi restarts - Kodi will overwrite your changes with its own settings, including client max protocol (if you set it to something other than "None" in Settings > Services > SMB Client). Your own settings should be added to .kodi/.smb/user.conf, although forcing Kodi to use only SMB1 has been supported via the GUI since 8.2.3 without any need to manually edit config files.
You also shouldn't be editing the server smb.conf either (for similar reasons) - use /storage/.config/samba.conf.
-
Do you have this problem without Plex? Can you try disabling Plex and see if the crashes continue?
-
@MrGrymReaper: No test confirmation = no fix.
I'm not sure this is a good solution for buggy motherboards, so probably just as well.
-
We'll take a PR.
-
You can just add "textmode" to the kernel command line and you'll boot into a console - this should be supported by all projects.
-
Does this happen with any DVD disc?
Can you run "cat /storage/.kodi/temp/kodi_crash.log | pastebinit" and paste the url.
-
Actually the file /storage/.kodi/temp/kodi_crash.log may be more useful - you can upload this from within 8.2.3.
-
Best I can suggest is to try the latest LE 9.0 build with 4.14.27 kernel, and also an experimental (though abandoned) 4.15.0 kernel.
4.14.27: LibreELEC Testbuilds for x86_64 (Kodi 18.0)
4.15.0: LibreELEC Testbuilds for x86_64 (Kodi 18.0)You could also try adding "radeon.dpm=0" to the kernel command line, as this has helped some users with AMD GPUs in the past.
Notebooks and laptops are not really the ideal target device for LibreELEC as these devices - with their switchable video, weak GPUs and other often niche and unsupported hardware (typically WiFi) - can be problematic.
I can't say for certain that your GPU is supported (it is 7 years old, and now pretty low spec) but it should be able to hardware accelerate 1080p H264/VC1/MPEG video. The question is whether you're able to switch the output from internal to external... this either needs a special driver (or configuration), or support in the kernel (LE 8 uses a much older 4.11.y kernel).
Although if all you want is a device to play video to an external HDMI display then maybe a Raspberry Pi3+ or similar ARM device will suffice (and be less of a problem). And probably use less power...
-
Could be a kernel bug. Or driver bug. Some Intel hardware is unable to access higher resolutions under Linux. Don't know why for sure. Take this example: LibreELEC Testbuilds for x86_64 (Kodi 18.0)
Filing a bug on Bugzilla Main Page might be your best option (file it under Product=DRI, then Component=DRM/Intel).
Be sure to submit a full dmesg with debug by adding "drm.debug=0x1e log_buf_len=1M" to the kernel command line.
-
All is as it should be.
4.9 | /proc/cpuinfo always shows Hardware = BCM2835 · Issue #2008 · raspberrypi/linux · GitHub - see third comment from pelwell. -
If you only associate with the 5GHz SSID then the Pi3+ won't connect on 2.4GHz. I'm not sure how (or if it's possible) to disable only the 2.4GHz radio.
And for my 8812au 5G wifi dongle I had to disable power management, does this work for the new wifi chip as well?
Power management is disabled by default - it's not a battery powered device.
-
About Milhouse OC settings:
sdram_freq=720
This is an huge settings: without heatsink on memory chip? Only with flirc case?
Without a heatsink on the memory chip, tested outside a case (although it also seems fine now I've put it in a FLIRC v1 case), and exhaustively tested with memtester.
BTW I've now stopped overclocking with:
Codearm_freq=1450 gpu_freq=560 over_voltage=6 force_turbo=1 sdram_freq=580 over_voltage_sdram=5 sdram_schmoo=0x02000020 dtparam=sd_overclock=100
and now use only the following:
Codegpu_freq=500 over_voltage=2 sdram_freq=580 over_voltage_sdram=5 sdram_schmoo=0x02000020 dtparam=sd_overclock=100
The large arm over_voltage=6 prevents the SoC from reducing voltage during the mid-level throttle at 1200MHz, and the 1450MHz (arm) and 560MHz (core) overclocks are simply not that beneficial (the over_voltage=6 was needed for core to hit 560MHz) while the mid-level voltage throttle is very useful at managing SoC temperature.
Performance (in LibreELEC) is also fine without force_turbo=1, so I've not bothered to enable that either with the 3+.
-
Thanks. I've included INTEL_IOMMU as well which accounts for a few extra options. Still think this is a motherboard issue/BIOS bug, though.
-
same problem here. Installation on VMWare.
Change your virtual hardware version to 12 or higher: VMware Knowledge Base
-
i cannot connect with samba to my computer. Windows 7 and libreelrc 8.2.4. with previous version it was possible. i did it always manually. in add source....samba.....smb://ipadr
can somebody help?
Did you just find a random Samba thread and decide to hijack it with your unrelated problem? Start a new thread please.
-
Can you try this img.gz: LibreELEC-Generic.x86_64-9.0-Milhouse-20180320003906-#0320-gc2a0368.img.gz
It includes these config changes: ZQ3
-
I can't help feeling this problem is caused by a bug in the motherboard BIOS, have you checked if your BIOS is latest? Googling this and related issues, a number of users have solved the issue with a BIOS update, or by using various combinations of BIOS options, eg. 211792.