XBian Beta 1.1 has no input on NOOBS

[engowen]

NOOBS 1.3.2, can be downloaded from raspberrypi.org support multiple OS to be installed on the same SD and upon booting raspberrypi NOOBS present a dialog to select which OS to boot.

After reading about Xbian I decided it is my preferred XBMC than RaspBMC hence I decided to make it as 1 of my multiboot OS. Creating the tarball is straightforward but time consuming, I'd created a tarball for XBian 1.0 Beta 1.1 using the guide from NOOBS github However using the boot.tar.xz I'd created NOOBS failed to build XBian. This is the error I got



To workaround it I used boot.tar.xz from Raspbian and Xbian installed without problem. Anyone interested can extract the OS file to NOOBS os folder.

The problem is once Xbian is loaded I'm not able to control it as both keyboard and mouse are not responding. I'd installed xbian-update1.0-1.2.deb but that doesn't help. I'd also updated all the packages by ssh using xbian and raspberry as password. For anyone who is interested I'd enabled root for ssh, password is raspberry.

I'd captured my problem here.



Anyone know what could be the problem?

[engowen]

Result from lsusb as below:

root@xbian:~# lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 001 Device 005: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard

root@xbian:~# lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 3: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M


I don't see keymap.xml, could this be the problem?

root@xbian:/home/xbian/.xbmc/userdata# ls -l
total 80
drwxr-xr-x 3 xbian xbian 4096 Jan 1 1970 addon_data
-rw-r--r-- 1 xbian xbian 719 Jun 8 23:28 advancedsettings.xml
-rw-r--r-- 1 xbian xbian 110 Jul 2 09:47 autoexec.py
drwxr-xr-x 3 xbian xbian 4096 Nov 9 09:56 Database
-rw-r--r-- 1 xbian xbian 27185 Jan 1 1970 guisettings.xml
drwxr-xr-x 2 xbian xbian 4096 Jan 1 1970 keymaps
-rw-r--r-- 1 xbian xbian 2059 Jan 1 1970 LCD.xml
drwxr-xr-x 2 xbian xbian 4096 Jan 1 1970 library
drwxr-xr-x 2 xbian xbian 4096 Jan 1 1970 peripheral_data
drwxr-xr-x 5 xbian xbian 4096 Jan 1 1970 playlists
-rw-r--r-- 1 xbian xbian 897 Jan 1 1970 profiles.xml
-rw-r--r-- 1 xbian xbian 385 Jan 1 1970 RssFeeds.xml
-rw-r--r-- 1 xbian xbian 270 Jun 8 22:41 sources.xml
drwxr-xr-x 19 xbian xbian 4096 Jan 1 1970 Thumbnails
root@xbian:/home/xbian/.xbmc/userdata# cd keymaps
root@xbian:/home/xbian/.xbmc/userdata/keymaps# ls -l
total 0

[mk01]

@engowen

for user editable xml files XBMC works like this: if missing, default is merged / used as conf upon start. so this should not be a problem.

if the problem related to only XBMC running, or after stop xbmc even console doesn't work for keyboard?

[engowen]

(13th Nov, 2013 09:52 AM)mk01 Wrote:  @engowen

for user editable xml files XBMC works like this: if missing, default is merged / used as conf upon start. so this should not be a problem.

if the problem related to only XBMC running, or after stop xbmc even console doesn't work for keyboard?

On console the keyboard work, when I run lsmod I noticed nothing is return. When I run sudo modprobe -r it was looking for a bin file in 3.6.11+ rather than 3.9.8+.

[mk01]

@engowen

good work, probably this (3.6.11+) vs 3.9.8 will be the problem.

I don't know NOOBS (so can't help), but looks like when you used the raspbian image to help with the install process, you created the problem.


Try to replace /boot files (or even /lib/modules) in the image for those from XBian standard image. This should be the solution. Although I don't know how this affects noobs installation as it.

btw: with XBian you don't need to run NOOBS to have more systems freely bootable. you can just copy the system to snapshot and boot any snapshot you like. And if you keep an eye on /boot, you will never get into troubles with any updates issued to them over time.

with beta1 and beta2 it is as core functionality there, no GUI - was planned for Beta2 but Beta2 will not include it. So this part lacks, but otherwise the functionality is simpler, booting natural, no hacks, images etc.

we will try to put into Beta3 then.