2015-04-22, 16:54
How did you create the install media? If you didn't download the image version and use Win32DiskImager (as per the wiki instructions), then you didn't do it correctly
(2015-04-22, 17:51)Dengal Wrote: First Tnx for your help !!
I tried agin use win32diskimgar but still not working . After thet i tried download the chrombox recovery and plunged it in and im getting this screen
http://imgur.com/ZO7rqd4
http://imgur.com/dnCfZYr
(2015-04-22, 19:18)Dengal Wrote: I have to say i didn't work with to wiki instruction because i don't really understand it
I downloaded the two files (win32+openelec)
Then i extract the oe to the folder
Installed the win32 and find the extract oe file and wrote it on the DOK as you can see on the pic http://imgur.com/dnCfZYr
(2015-04-22, 19:25)fma965 Wrote: Hi how can i manually inject my MAC Address in to the uploaded stock firmwares (from the wiki) steamos seems to be having network issues when my mac is set to 00:00:00:00:00 my laptop with the stock firmware backup on broke.
(2015-04-22, 23:06)mauzzz Wrote: I’m having problems with wake from suspend while a video is paused.
My Asus Chromebox with OE 5.0.8 (and pulse eight cec adapter) suspends after 5 minutes when there is no playback (which includes pause). Plasma also suspends. The Chromebox will properly wake from suspend when the TV is turned on. All working as intended.
But when a video is paused and the box suspends, it will wake up (led on) with a black screen and frozen controls. I have to power cycle or reboot from prompt. I’m using the wake up script from the Kodi wiki.
Anyone else having this?
(2015-04-23, 06:58)Hammins Wrote: Hey Matt, I am having the exact problem with the MAC address being 00:00:00:00:00:00 for the ethernet as well. Wireless is fine. I believe I may have lost mine last year when I initially wiped my Chromebox and was not 100% aware of the problem. I just recently got back to working with the Chromebox again and was having issues in Ubuntu streaming steam and then switched to SteamOS (which is performing awesome now). but my router is rejecting the null MAC address.
When I flash with the EZscript to update (I have also done a factory reset back to chromeOS and re-flashed to current EZsetup) the script tells me that the firmware (for eth0) has no record of a MAC address. I have tried to use the firmware from the stock ASUS file from the wiki and it just tells me that it cannot be read. I have spent several days now avoiding coming on here and asking about this, just so I can get a grip on it myself, but I am out of my depth here. I have tried all kinds of boot time spoofing and other scripts, but only temporary solutions seem to work, nothing permanent.
I am now at the end of my rope. :sniffle:
(2015-04-23, 07:03)Matt Devo Wrote:(2015-04-23, 06:58)Hammins Wrote: Hey Matt, I am having the exact problem with the MAC address being 00:00:00:00:00:00 for the ethernet as well. Wireless is fine. I believe I may have lost mine last year when I initially wiped my Chromebox and was not 100% aware of the problem. I just recently got back to working with the Chromebox again and was having issues in Ubuntu streaming steam and then switched to SteamOS (which is performing awesome now). but my router is rejecting the null MAC address.
When I flash with the EZscript to update (I have also done a factory reset back to chromeOS and re-flashed to current EZsetup) the script tells me that the firmware (for eth0) has no record of a MAC address. I have tried to use the firmware from the stock ASUS file from the wiki and it just tells me that it cannot be read. I have spent several days now avoiding coming on here and asking about this, just so I can get a grip on it myself, but I am out of my depth here. I have tried all kinds of boot time spoofing and other scripts, but only temporary solutions seem to work, nothing permanent.
I am now at the end of my rope.
it's not a firmware issue - the "default" MAC address if you don't have a device-specific one is A0:00:BA0:0B:AD, not all zeroes. I'm not sure where that's coming from, but it's not a firmware issue. If I had to guess, it's a SteamOS issue resulting from it using a very old kernel which doesn't properly support the Haswell mobile hardware.
(2015-04-24, 07:10)brockftw Wrote: Anyone looking for a chromebox ? Turns out I don't need another one. All set up with openelec.