Yeah, i do think is the BIOS. Anyway no biggy, the important thing is the usb improvement.
Wiki should be updated to note the Logitech k400 has no limitations now.
(2015-12-11, 10:33)Veronica Wrote: [ -> ]Yeah, i do think is the BIOS. Anyway no biggy, the important thing is the usb improvement.
Wiki should be updated to note the Logitech k400 has no limitations now.
Think it still misbehaves on the dev mode boot screen, which is what the wiki note is referring to
Hi!
I bought an Asus Chromebox about a year ago, and immediately installed Lubuntu and Kodi. However, I haven't been 100% satisfied with the setup.
When using the Lubuntu desktop, i often got some kind of kernel error, so I chose to ditch the GUI and boot straight into Kodi instead. The problem now is that I can't edit system settings other than through terminal over SSH, and functions like USB auto mounting and wireless internet are not working.
OpenElec is not an option, since I'm running a separate Airplay channel for streaming audio and control my surround receiver. Debian or Ubuntu are OK.
Does there exist a distro that:
• Let me boot straight into Kodi without having to manually log in with a keyboard (Kodi on top of a desktop is fine)
• Is as lightweight as possible
• Auto mounting of USB stick and hard drives is possible
• Supports sharing of external USB devices over SMB
• Built on Debian or Ubuntu
Except for the last line,
OpenElec will do all the above.
Is it possible to install Kodibuntu, boot straight to the desktop environment and then start Kodi automatically? If I run Kodi on top of the desktop I can have services such as auto-mount running in background
(2015-12-11, 22:17)hansibull Wrote: [ -> ]Is it possible to install Kodibuntu, boot straight to the desktop environment and then start Kodi automatically? If I run Kodi on top of the desktop I can have services such as auto-mount running in background
maybe, but that's a better question for the Linux support forum, since it has nothing to do with the ChromeBox specifically. Most people here are running OpenELEC anyway.
(2015-12-11, 22:17)hansibull Wrote: [ -> ]Is it possible to install Kodibuntu, boot straight to the desktop environment and then start Kodi automatically? If I run Kodi on top of the desktop I can have services such as auto-mount running in background
Yes. When you reboot it will boot to the last session used. Kodibuntu has lubuntu and kodi sessions so if you remain in lubuntu and open kodi from there when you reboot, a login screen will show up, there you have to put your password and it will login to lubuntu desktop, unless you pick another session from login screen (kind of like lockscreen for Windows).
Would be better if you watch YouTube videos of kodibuntu to learn how it works.
(2015-12-11, 06:13)Matt Devo Wrote: [ -> ] (2015-12-11, 06:08)Veronica Wrote: [ -> ]But that's the first time i see it does something like that.
Before the seabios menu used the whole display, at list for Linux <=14.04 if i recall well and openelec long time ago.
it's possibly related to the updated video BIOS included in the most recent update. Hard to say since I can't reproduce it here
Darn, thought that the recent USB3-related fixes in SeaBIOS would allow me to use during boot my cheap wireless keyboard instead of grabbing that old wired keyboard but no.
Otherwise would not bothered updating the BIOS. But I did and now I see that the changes in the video BIOS part
made things a lot worse in my setup. At least with my pretty old TV.
Now when selecting the boot device I can see only the second line of the text. The first line where it says the current version of the BIOS is trimmed and no setting of the TV image size can bring it back. Also the leftmost two characters are cropped.
But that's not all.... now after each reboot of my chromebox the TV ends up in the overscan mode (16:9) and not "Just Scan" (1:1 pixel size name for Samsung TVs). Need to manually change it each time to fullscreen no overscan mode. Am angry at myself to have updated the BIOS...
So a question to @Matt: how can I flash back a previous version of BIOS? A version prior the changes made in the video part?
I'm having a problem with "No signal" on the HDMI port connected to my dual-boot Chromebox after a reboot. I have a new Samsung UN65JU6500 4k TV and have read through this forum. I've tried creating an autostart.sh in /storage/.config, which looks like this:
(
#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60
) &
However, the Chromebox still won't boot until I actually unplug the HDMI cable, boot, and then manually run "xrandr --output HDMI1 --mode 1920x1080 -r 60" after ssh comes up. In fact, with the HDMI cable disconnected, the Chromebox boots to:
~# xrandr --prop
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
HDMI1 disconnected (normal left inverted right x axis y axis)
aspect ratio: Automatic
supported: Automatic, 4:3, 16:9
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
HDMI2 disconnected (normal left inverted right x axis y axis)
aspect ratio: Automatic
supported: Automatic, 4:3, 16:9
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
After booting and manually running xrandr output from above, I see:
~ # xrandr --prop
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1872mm x 1053mm
EDID:
00ffffffffffff004c2d440c01000001
2a180103808e50780a23ada4544d9926
0f474abdef80714f81c0810081809500
a9c0b300010104740030f2705a80b058
8a00501d7400001e023a801871382d40
582c4500501d7400001e000000fd0018
4b0f511e000a202020202020000000fc
0053414d53554e470a202020202001ab
020342f1535f101f041305142021225d
5e62636407160312290907071507503d
04c083010000e2000f6e030c001000b8
3c21108001020304e3060501e50e6061
6566011d80d0721c1620102c2580501d
7400009e662156aa51001e30468f3300
501d7400001e00000000000000000000
000000000000000000000000000000b3
aspect ratio: Automatic
supported: Automatic, 4:3, 16:9
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
3840x2160 30.00 + 25.00 24.00 29.97 23.98
4096x2160 24.00 23.98
1920x1080 60.00* 50.00 59.94 30.00 25.00 24.00 29.97 23.98
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 59.98
1280x1024 75.02 60.02
1440x900 59.90
1366x768 59.79
1280x800 59.91
1152x864 75.00
1280x720 59.97 60.00 50.00 59.94
1024x768 75.08 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32
720x576 50.00
720x576i 50.00
720x480 60.00 59.94
720x480i 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
aspect ratio: Automatic
supported: Automatic, 4:3, 16:9
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
audio: auto
supported: force-dvi, off, auto, on
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Any idea on what could be going on? Please let me know if there's any other info I can provide that might help. I've also tried putting HDMI1 in PC and UHD color as suggested earlier in this thread. I'm on the latest Firmware on my Samsung TV. Thanks.
(2015-12-12, 21:07)Diodato Wrote: [ -> ]Darn, thought that the recent USB3-related fixes in SeaBIOS would allow me to use during boot my cheap wireless keyboard instead of grabbing that old wired keyboard but no.
Otherwise would not bothered updating the BIOS. But I did and now I see that the changes in the video BIOS part
made things a lot worse in my setup. At least with my pretty old TV.
Now when selecting the boot device I can see only the second line of the text. The first line where it says the current version of the BIOS is trimmed and no setting of the TV image size can bring it back. Also the leftmost two characters are cropped.
But that's not all.... now after each reboot of my chromebox the TV ends up in the overscan mode (16:9) and not "Just Scan" (1:1 pixel size name for Samsung TVs). Need to manually change it each time to fullscreen no overscan mode. Am angry at myself to have updated the BIOS...
So a question to @Matt: how can I flash back a previous version of BIOS? A version prior the changes made in the video part?
I'm not sure how those issues would be video BIOS related, because it's not doing anything other than setting a single video mode on startup. Whether your TV overscans or not, or how it sets the video mode, should not be related to what the video BIOS is doing when initialized at boot. I can create a test firmware for you though which reverts only the video BIOS, so we can determine if it fact it is the issue. PM me for the script link.
(2015-12-12, 23:46)giant25 Wrote: [ -> ]I'm having a problem with "No signal" on the HDMI port connected to my dual-boot Chromebox after a reboot. I have a new Samsung UN65JU6500 4k TV and have read through this forum. I've tried creating an autostart.sh in /storage/.config, which looks like this:
Any idea on what could be going on? Please let me know if there's any other info I can provide that might help. I've also tried putting HDMI1 in PC and UHD color as suggested earlier in this thread. I'm on the latest Firmware on my Samsung TV. Thanks.
is this a box you just set up, or was it previously working and how doesn't due to an update?
(2015-12-13, 02:51)Matt Devo Wrote: [ -> ] (2015-12-12, 23:46)giant25 Wrote: [ -> ]I'm having a problem with "No signal" on the HDMI port connected to my dual-boot Chromebox after a reboot. I have a new Samsung UN65JU6500 4k TV and have read through this forum. I've tried creating an autostart.sh in /storage/.config, which looks like this:
Any idea on what could be going on? Please let me know if there's any other info I can provide that might help. I've also tried putting HDMI1 in PC and UHD color as suggested earlier in this thread. I'm on the latest Firmware on my Samsung TV. Thanks.
is this a box you just set up, or was it previously working and how doesn't due to an update?
Previously working, not working with new TV, no other changes. I have since updated to OE 6, but same behavior before that update.
Does my autostart.sh look right?
Any other way to force 1080p?
Is it possible I need a FW or BIOS update on Chromebox (ran script in February)?
Thanks.
(2015-12-13, 02:51)Matt Devo Wrote: [ -> ] (2015-12-12, 21:07)Diodato Wrote: [ -> ]But that's not all.... now after each reboot of my chromebox the TV ends up in the overscan mode (16:9) and not "Just Scan" (1:1 pixel size name for Samsung TVs). Need to manually change it each time to fullscreen no overscan mode. Am angry at myself to have updated the BIOS...
So a question to @Matt: how can I flash back a previous version of BIOS? A version prior the changes made in the video part?
I'm not sure how those issues would be video BIOS related, because it's not doing anything other than setting a single video mode on startup. Whether your TV overscans or not, or how it sets the video mode, should not be related to what the video BIOS is doing when initialized at boot. I can create a test firmware for you though which reverts only the video BIOS, so we can determine if it fact it is the issue. PM me for the script link.
My 7 year old Samsung TV (LE46N87BD) when receiving a Full HD (1920x1080) signal and set to no overscan (Just Scan) on a particular HDMI input will keep the no overscan mode until a non Full HD signal arrives. This is obvious since it is receiving a signal that does not map 1:1 to the physical "pixel" resolution of the screen. Now depending on the aspect ratio of the lower resolution new signal the TV switches to 4:3 or 16:9 mode. If once again the signal becomes Full HD (1920x1080) the TV will switch to the 16:9 (or continue in the 16:9) mode, doing overscan, and not the Just Scan (1:1 mapping with no overscan). So it never reverts back to no overscaning of a FullHD signal after a resolution change. Refresh frequency changes don't affect the mode.
Checked in the manual just now and on the HDMI inputs my TV supports these VESA modes: 800x600,1024x768,1280x1024@60
[email protected].
Initial installation of OpenELEC - first firmware flashing - I remember I had small letters on the screen. And all the time the brief text flashes during boots. But now they are quite big. So I assume that the previous BIOS was using the 1920x1080 resolution and the current BIOS some other lower resolution. And that's why the HDMI input looses the Just Scan mode.
Can't send you a PM or email. Get error about insufficient permissions... and I can't even access my own emails, same error message:
"You do not have permission to access this page." Email sent.
Will try to contact the moderators.
I will buy an Asus Chromebox on Black Friday at an unbelievable price on Amazon
(2015-12-13, 16:11)Concestly Wrote: [ -> ]I will buy an Asus Chromebox on Black Friday at an unbelievable price on Amazon
Thanks for letting us know your buying plans for November 25th, 2016.
Hello I followed instructions installing a standalone set up it worked,then I tried a dual boot set up after reinstalling firmware. It continues to say chrome os missing or damaged after reinstalling image. Any help would be greatly appreciated.
Thanks