[FreeMan xbmc]

I seem to be down to 0 space free on my SSD in my Kodi box, so "curl -L -O http://mrchromebox.tech/setup-kodi.sh" is failing to write.

xbmc@xbmc:~$ curl -L -O http://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0   185    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1045  100  1045    0     0   1860      0 --:--:-- --:--:-- --:--:--  1860
(23) Failed writing body

A) Is it possible/reasonable to write it to the same USB stick that I'm going to use to install the new firmware and the libreElec install?
B) After deleting quite a few actor .jpg images (Windows said it was > 50MB worth), I'm still showing 0 space available:

xbmc@xbmc:~$ df
Filesystem     1K-blocks     Used Available Use% Mounted on
udev              944604        4    944600   1% /dev
tmpfs             192092     2704    189388   2% /run
/dev/sda1       13257232 12625776         0 100% /
none                   4        0         4   0% /sys/fs/cgroup
none                5120        8      5112   1% /run/lock
none              960452        4    960448   1% /run/shm
none              102400        4    102396   1% /run/user
/dev/sdb1       15142928       80  15142848   1% /media/TRAVELDRIVE

Any suggestions?

[Matt Devo]

I seem to be down to 0 space free on my SSD in my Kodi box, so "curl -L -O http://mrchromebox.tech/setup-kodi.sh" is failing to write.

xbmc@xbmc:~$ curl -L -O http://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh
(23) Failed writing body

Any suggestions? 

 
use the correct url (https vs http) and the download won't fail.

[FreeMan xbmc]

Copy pasted directly from the OP of this thread!

It actually worked once, then refused to create the install on a really old USB stick, so I was doing it again.

Also:
xbmc@xbmc:~$ curl -L -O https://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   185    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1045  100  1045    0     0   2127      0 --:--:-- --:--:-- --:--:--  2127
(23) Failed writing body


Finally got it to recognize that there was some free space on the drive, it downloaded & I've got it installed.

As has been my experience every time in the past, exporting the video library works just fine, but I cannot get it to reimport it on the new setup. Not your fault at all, this seems to be an XMBC/Kodi issue from when I started using it almost 10 years ago.

Thanks again for putting all this together, Matt - greatly appreciate your efforts and support!

[nickr]

Matt, long time no see, I haven't been round here much. 

I have a chromebox which is in a tricky part of the house. The wifi is the only way to connect without doing non-waf wall ripping. 

I recently upgraded everything to libreelec 9 and added pci=nomsi to the command lines. 

However the wifi is not working well. We have a mysql database and I noticed this on the kodi wiki page, does this mean you effectively cannot use a mysql database with wifi?

System-->LibreELEC-->Network: Wait for network before starting Kodi: On if using a external mysql database; otherwise Off (breaks Wi-Fi, only use for wired/ethernet connections)

[Matt Devo]

Matt, long time no see, I haven't been round here much. 

I have a chromebox which is in a tricky part of the house. The wifi is the only way to connect without doing non-waf wall ripping. 

I recently upgraded everything to libreelec 9 and added pci=nomsi to the command lines. 

However the wifi is not working well. We have a mysql database and I noticed this on the kodi wiki page, does this mean you effectively cannot use a mysql database with wifi?

System-->LibreELEC-->Network: Wait for network before starting Kodi: On if using a external mysql database; otherwise Off (breaks Wi-Fi, only use for wired/ethernet connections)

 that was true at the time I added it to the wiki, which was for LE 7? I have no idea if that still holds true, I suspect it probably works much better now. Have you tried with the setting on?  What isn't working well?

[Walrus]

I just upgraded to LibreElec 9 (Leia), and I can't seem to access my shares anymore. Fought for hours last night and gave up. Here is my setup:

Main HTPC is running Windows 7, serves as the media server (2x internal 4tb hard drives), mysql for syncing, and runs Kodi for our main TV.
Bedroom Chromebox running LibreElec standalone (not dual boot).

When the main HTPC and Chromebox were running the same version of Kodi 17 (I think 17.3) I had everything working fine. A few months ago I tried updating both to a newer version of 17, and ran into the same share problem.

Last night I upgraded the main HTPC to Kodi 18.1. Then I updated the Chromebox to LibreElec 9 (which I think is 18.0 ?). To do so, I had to backup, then do a fresh install due to the FAT partition being too small. When I tried restoring from the backup, it fails, says the backup is corrupt or something, so I'm having to re-setup everything. When I try to add a network location (\\192.168.1.107 which is the HTPC location) it fails/doesn't find anything. Is it due to the 18.1 and 18.0 not matching?

Or is there some problem with windows 7 and SMBv1?

kernel/driver bug in LE9.0, use workaround posted on wiki (edit /flash/syslinux.cfg)    

I have no idea what I am doing with putty/ssh, but I was able to follow the wiki and add the pci=nomsi after quiet. The wiki is wrong, the location was /flash/syslinux.cfg as you posted.

I still can't get it to work. Once I've added 192.168.1.107/Movies as a network location, it says success, but then asks me to lock the location and a username and password, and a slider bar to remember the location. I leave them blank, as on the windows machine I don't have a username or pass. I hit OK, and the window closes and reopens... endless loop.

Edit: Doing some reading, I'm thinking it might be because I don't have a username or password set to log in to the windows machine. An additional step is to create an additional local account on the windows machine (with username & password 'kodi'), and then under the main windows account, share the folders with the local 'kodi' account. Then.. on the LibreElec machine, add the network location and use 'kodi' for the username and password. I'll report back once I try this.

[FreeMan xbmc]

I don't know if this is an issue with Kodi, LibreElec or Kore...

I got my ASUS CN60 updated to the latest EUFI BIOS & a standalone LibreElec 9.0.0 install over the weekend. Now, when I hit pause during playback of any video, if I let it sit long enough that the screen dims (it's set at the 3 minute default) it takes ages for it to wake up. I hit play, and it has literally been sitting for more than 3 minutes (actually more like 5) doing nothing.

I'm using the official Kore remote on my Android phone as my remote. I just walked up to the keyboard that I have plugged into the Chromebox and hit the space bar and the screen immediately woke up. A second press of the spacebar and it started playing. A few moments later it paused, then started then paused again - I'm assuming these are because of the play/pause presses I sent from the phone. Now it's paused and doesn't seem to be interested in resuming, at least not from the remote.

While I was typing this, the screen dimmed, then suddenly it woke up and started playing again. Then it paused, resumed, paused, resumed, etc. from me mashing the remote key, and now it's paused but the remote thinks it's playing.

I've also noticed that when waking it up even with no video playing, it's very very slow to respond. Out of frustration, I'll end up mashing a few buttons on the remote (arrow left/right, menu home, etc) and when it finally wakes up, it will replay all the random key strokes.

Any suggestions on what to look for or check? I never had any issues like this running 17.x on the pared back somewhat updated really old Kudibuntu setup I'd been running. Because I've not made any network/hardware changes, I doubt that it's a network related issue (though anything is possible), so I think it's definitely related to the LE update. I doubt that it's anything your fault and I'm not attempting to/interested in assigning blame, I'm just looking to get it fixed.

Thanks!

[Matt Devo]

I don't know if this is an issue with Kodi, LibreElec or Kore...

I got my ASUS CN60 updated to the latest EUFI BIOS & a standalone LibreElec 9.0.0 install over the weekend. Now, when I hit pause during playback of any video, if I let it sit long enough that the screen dims (it's set at the 3 minute default) it takes ages for it to wake up. I hit play, and it has literally been sitting for more than 3 minutes (actually more like 5) doing nothing.

I'm using the official Kore remote on my Android phone as my remote. I just walked up to the keyboard that I have plugged into the Chromebox and hit the space bar and the screen immediately woke up. A second press of the spacebar and it started playing. A few moments later it paused, then started then paused again - I'm assuming these are because of the play/pause presses I sent from the phone. Now it's paused and doesn't seem to be interested in resuming, at least not from the remote.

While I was typing this, the screen dimmed, then suddenly it woke up and started playing again. Then it paused, resumed, paused, resumed, etc. from me mashing the remote key, and now it's paused but the remote thinks it's playing.

I've also noticed that when waking it up even with no video playing, it's very very slow to respond. Out of frustration, I'll end up mashing a few buttons on the remote (arrow left/right, menu home, etc) and when it finally wakes up, it will replay all the random key strokes.

Any suggestions on what to look for or check? I never had any issues like this running 17.x on the pared back somewhat updated really old Kudibuntu setup I'd been running. Because I've not made any network/hardware changes, I doubt that it's a network related issue (though anything is possible), so I think it's definitely related to the LE update. I doubt that it's anything your fault and I'm not attempting to/interested in assigning blame, I'm just looking to get it fixed.

Thanks!

 sounds potentially networking related, if a physical keyboard shows no issues but the Android remote does.  Not sure if it's on the Kodi side or LE side, but either the Linux support forum here or the LE forums might give you a wider audience for the issue.  

one note, if you're using a LAN connection (vs wifi), be sure to implement the fix in the wiki troubleshooting section, since it mitigates a kernel bug that cripples the Ethernet throughput

[FreeMan xbmc]

 

 sounds potentially networking related, if a physical keyboard shows no issues but the Android remote does.  Not sure if it's on the Kodi side or LE side, but either the Linux support forum here or the LE forums might give you a wider audience for the issue.  

one note, if you're using a LAN connection (vs wifi), be sure to implement the fix in the wiki troubleshooting section, since it mitigates a kernel bug that cripples the Ethernet throughput  

It seems that it may have been a network issue. I avoid wireless whenever possible, so I implemented the `pci=nomsi` fix and that's definitely helped with browsing videos (non-library files), and it seems to be waking up from the paused state much better too.
Thanks again for your work and support!

[giant25]

Hey Matt, do you know if a bug report has been submitted for the kernel issue crippling throughout? Just curious. Seems like a pain to keep explaining this as folks upgrade....

[Matt Devo]

Hey Matt, do you know if a bug report has been submitted for the kernel issue crippling throughout? Just curious. Seems like a pain to keep explaining this as folks upgrade....

 I'm not sure yet if it's a kernel bug that disproportionally affects Chromebox users (since they all have the RT8168 Ethernet chip), or if the kernel change simply exposed a coreboot bug that had laid dormant (due to AER not being enabled).  It's on my to-do list to figure that out, then can proceed with how to fix

[MrBuyakah]

Edit: Doing some reading, I'm thinking it might be because I don't have a username or password set to log in to the windows machine. An additional step is to create an additional local account on the windows machine (with username & password 'kodi'), and then under the main windows account, share the folders with the local 'kodi' account. Then.. on the LibreElec machine, add the network location and use 'kodi' for the username and password. I'll report back once I try this. 

This works as it's exactly what I am doing due to Windows only supporting SMBv2 and up.  I went a little further and only allowed that "kodi" user read only access to my shares.

[malcolmbarr]

Help!

I have installed standalone Libreelec 9.01 on a CN60 Chromebox using the EZ setup script. I have also added the "pci=nomsi" line to grub.cfg as explained in the wiki. But my ethernet link is still unusably bad with buffering occurring all the time when the bitrate of the source material is at all high. The step of adding to grub.cfg does not appear to have meaningfully changed the ethernet performance, and I have checked to see the pci-nomsi addition is there after 'quiet'.

This is accessing media stored locally on the network via SMB. Accessing the same media over the network via SMB from a windows PC, all works well.

Any help much appreciated.

[Matt Devo]

Help!

I have installed standalone Libreelec 9.01 on a CN60 Chromebox using the EZ setup script. I have also added the "pci=nomsi" line to grub.cfg as explained in the wiki. But my ethernet link is still unusably bad with buffering occurring all the time when the bitrate of the source material is at all high. The step of adding to grub.cfg does not appear to have meaningfully changed the ethernet performance, and I have checked to see the pci-nomsi addition is there after 'quiet'.

This is accessing media stored locally on the network via SMB. Accessing the same media over the network via SMB from a windows PC, all works well.

Any help much appreciated.

on a fresh install of LE9 in conjunction with my UEFI firmware, the proper file to edit is /flash/syslinux.cfg, not grub.cfg

[malcolmbarr]

Thanks for the reply. However, when I open the syslinux.cfg it has no content, and I get the message ‘new file’ at the bottom of the screen.

I was using this Chromebox for OpenELEC but then put it into storage. Coming to it again, I followed the instructions on Ypur site to boot from a Ubuntu USB stick and then reinstall the core boot, etc, and then installed Libreelec. All works well apart from the buffering issue.

Should I put the ‘pci=nomsi’ line in a new syslinux.cfg? The fact the line ending ‘quiet’ is not there suggests to me I shouldn’t......