+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Bugs (/forum-23.html)
+--- Thread: XBian 1.0 Alpha 4 Bugthread (/thread-182.html)
RE: XBian 1.0 Alpha 4 Bugthread - CurlyMo - 4th Jan, 2013 05:52 AM
Kindle changers work perfectly here.
RE: Xbian constantly reboots - Flint - 4th Jan, 2013 05:54 AM
(4th Jan, 2013 05:39 AM)rikardo1979 Wrote: I've tried Kindle charger and I found it to week for RPi so I would say it is power related
Please try another PSU if you can
Thank you for super quick reply. I will try different power source.
RE: XBian 1.0 Alpha 4 Bugthread - ambro72 - 4th Jan, 2013 06:07 AM
(4th Jan, 2013 12:19 AM)djumaka Wrote:I confirm fix increasing GPU RAM to 128. In next days I will try others values for @namtih(3rd Jan, 2013 11:10 PM)Koenkk Wrote: For those having playback/ other XBMC issues please try this build: http://forum.xbian.org/thread-177.html
My problem was that XBMC was throwing insufficient resources error in the log, and the guys in the raspbmc channel gave me a hint on that... so I managed to fix it with increasing the GPU RAM from 100 -> 128 in /boot/config.txt, without going to the other build... Will still investigate, though, as this might be just one of the cases.
Hope this is useful to someone.
Regards,
Boyan.
RE: XBian 1.0 Alpha 4 Bugthread - namtih - 4th Jan, 2013 06:21 AM
As you have moved the topic to another category, you should also edit the link "XBian 1.0 Alpha 4 topic" on the startpage. It's broken now. Or you add an link to the bugfix topic too.
(4th Jan, 2013 06:07 AM)ambro72 Wrote: I confirm fix increasing GPU RAM to 128. In next days I will try others values for @namtih
Thank you. Would be great to perhaps finally find a value working in all situations. In my opinion you don't need to test all values between 100 to 128. Just give 114 a try. If it works, we should use it as default. If not...yeah...let's stay with 128.
RE: XBian 1.0 Alpha 4 Bugthread - CurlyMo - 4th Jan, 2013 06:28 AM
(4th Jan, 2013 06:21 AM)namtih Wrote: As you have moved the topic to another category, you should also edit the link "XBian 1.0 Alpha 4 topic" on the startpage. It's broken now. Or you add an link to the bugfix topic too.Done
RE: Xbian constantly reboots - IriDium - 5th Jan, 2013 01:39 AM
(4th Jan, 2013 05:54 AM)Flint Wrote:(4th Jan, 2013 05:39 AM)rikardo1979 Wrote: I've tried Kindle charger and I found it to week for RPi so I would say it is power related
Please try another PSU if you can
Thank you for super quick reply. I will try different power source.
I use a 700ma ZTE phone charger on my RPi and I haven't had any problems. I would also say it is a power issue, especially if you are using both of the Pi's USB outputs (Supposedly 100ma max on each one).
RE: XBian 1.0 Alpha 4 Bugthread - da_didi - 7th Jan, 2013 12:07 AM
I installed the Alpha4 on my sdhc, first boot was very fast, I played some videos and after a restart, the service xbmc doesn't start anyore:
Quote:root@xbian:/home/xbian# xbmc
sh: 1: glxinfo: not found
XBMC needs hardware accelerated OpenGL rendering.
Install an appropriate graphics driver.
Please consult XBMC Wiki for supported hardware
http://wiki.xbmc.org/?title=Supported_hardware
Any ideas?
RE: XBian 1.0 Alpha 4 Bugthread - CurlyMo - 7th Jan, 2013 12:09 AM
Wrong startup script
Code:
sudo /etc/init.d/xbmc startRE: XBian 1.0 Alpha 4 Bugthread - ambro72 - 7th Jan, 2013 01:23 AM
(4th Jan, 2013 06:21 AM)namtih Wrote: As you have moved the topic to another category, you should also edit the link "XBian 1.0 Alpha 4 topic" on the startpage. It's broken now. Or you add an link to the bugfix topic too.I tried with GPU RAM 114 set and everything works like 128.
(4th Jan, 2013 06:07 AM)ambro72 Wrote: I confirm fix increasing GPU RAM to 128. In next days I will try others values for @namtih
Thank you. Would be great to perhaps finally find a value working in all situations. In my opinion you don't need to test all values between 100 to 128. Just give 114 a try. If it works, we should use it as default. If not...yeah...let's stay with 128.
I have a couple of films not working with both settings. I'm invastigating.
RE: XBian 1.0 Alpha 4 Bugthread - numanoids - 7th Jan, 2013 07:52 PM
Anyone else discovered that CEC appears to be broken also?
Upgraded an alpha2 install and it didn't work so I thought part of the upgrade had borked but when i did a clean install I dont get any CEC functionality at all.
From debug log
Quote:9:00:31 T:3042570240 DEBUG: LoadMappings - loaded node "Raspberry Pi CEC Adapter"
19:00:31 T:3042570240 DEBUG: LoadMappings - loaded node "Pulse-Eight CEC Adapter"
19:00:31 T:3042570240 DEBUG: GetMappingForDevice - device (2708:1001) mapped to Raspberry Pi CEC Adapter (type = cec)
19:00:31 T:3042570240 DEBUG: SECTION:LoadDLL(libcec.so.2)
19:00:31 T:3042570240 DEBUG: Loading: libcec.so.2
19:00:31 T:3042570240 DEBUG: InitialiseFeature - using libCEC v2.0.5
19:00:31 T:3042570240 NOTICE: Register - new cec device registered on rpi->RPI: Raspberry Pi CEC Adapter (2708:1001)
19:00:31 T:3031802944 NOTICE: Thread CEC Adapter start, auto delete: false
19:00:31 T:3031802944 DEBUG: OpenConnection - opening a connection to the CEC adapter: RPI
19:00:31 T:3031802944 DEBUG: CecLogMessage - unregistering all CEC clients
19:00:31 T:3031802944 DEBUG: CecLogMessage - Broadcast (F): osd name set to 'Broadcast'
19:00:31 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchiq_initialise succeeded
19:00:31 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchi_initialise succeeded
19:00:31 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchi_connect succeeded
04:55:57 T:3031802944 ERROR: CecLogMessage - failed to release the previous LA
04:55:57 T:3031802944 ERROR: CecLogMessage - could not open a connection (try 1)
04:55:58 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchiq_initialise succeeded
04:55:58 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchi_initialise succeeded
04:55:58 T:3031802944 DEBUG: CecLogMessage - InitHostCEC - vchi_connect succeeded
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address changed to Broadcast (f)
04:55:58 T:3031802944 DEBUG: CecLogMessage - RegisterLogicalAddress - registering address e
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address changed to Playback 2 (8)
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address changed to Free use (e)
04:55:58 T:3031802944 DEBUG: CecLogMessage - Open - vc_cec initialised
04:55:58 T:3031802944 DEBUG: CecLogMessage - connection opened
04:55:58 T:3031802944 DEBUG: CecLogMessage - << Broadcast (F) -> TV (0): POLL
04:55:58 T:3031802944 DEBUG: CecLogMessage - initiator 'Broadcast' is not supported by the CEC adapter. using 'Free use' instead
04:55:58 T:3031802944 DEBUG: CecLogMessage - << e0
04:55:58 T:2966340672 DEBUG: CecLogMessage - processor thread started
04:55:58 T:3031802944 DEBUG: CecLogMessage - >> POLL sent
04:55:58 T:3031802944 DEBUG: CecLogMessage - TV (0): device status changed into 'present'
04:55:58 T:3031802944 DEBUG: CecLogMessage - << requesting vendor ID of 'TV' (0)
04:55:58 T:3031802944 DEBUG: CecLogMessage - << e0:8c
04:55:58 T:2966340672 DEBUG: CecLogMessage - >> 0f:87:00:00:f0
04:55:58 T:2966340672 DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): device vendor id (87)
04:55:58 T:2966340672 DEBUG: CecLogMessage - TV (0): vendor = Samsung (0000f0)
04:55:58 T:3031802944 DEBUG: CecLogMessage - expected response received (87: device vendor id)
04:55:58 T:2966340672 DEBUG: CecLogMessage - replacing the command handler for device 'TV' (0)
04:55:58 T:3031802944 DEBUG: CecLogMessage - registering new CEC client - v2.0.0
04:55:58 T:3031802944 DEBUG: CecLogMessage - detecting logical address for type 'recording device'
04:55:58 T:3031802944 DEBUG: CecLogMessage - trying logical address 'Recorder 1'
04:55:58 T:3031802944 DEBUG: CecLogMessage - << Recorder 1 (1) -> Recorder 1 (1): POLL
04:55:58 T:3031802944 DEBUG: CecLogMessage - << 11
04:55:58 T:3031802944 DEBUG: CecLogMessage - UnregisterLogicalAddress - releasing previous logical address
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address changed to Broadcast (f)
04:55:58 T:3031802944 DEBUG: CecLogMessage - RegisterLogicalAddress - registering address 1
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address e was taken by another device, allocating a new address
04:55:58 T:2996827200 DEBUG: CecLogMessage - logical address changed to Recorder 1 (1)
04:55:59 T:3031802944 DEBUG: CecLogMessage - << 11
Re: XBian 1.0 Alpha 4 Bugthread - rikardo1979 - 7th Jan, 2013 08:06 PM
all works here,so maybe something bugging in yours
RE: XBian 1.0 Alpha 4 Bugthread - numanoids - 7th Jan, 2013 08:16 PM
(7th Jan, 2013 08:06 PM)rikardo1979 Wrote: all works here,so maybe something bugging in yours
Curious particularly as it was working fine beforehand - guessing most probably the way its communicating or something. I'll try another distro and see if it works.
Update: Ok so RaspBMC suffers from the same issue - looks like something broken within the Frodo implementation with libcec for this TV. I guess I'll need to take up with pulse-eight.
Update2: Appears libcec doesn't like some other powered on devices being connected at the same time. If I yank out the cable STB and restart XBMC then it initialises fine - one to watch out for other folks out there.
Thanks anyway
RE: XBian 1.0 Alpha 4 Bugthread - raspberry_pd - 7th Jan, 2013 10:07 PM
Unfortunately I have some bugs to report with the latest Koennk build that he is building AFAIK to try and address the various little bugs that have arisen with a4.
On bootup:
Quote:[ ok ] Cleaning up temporary files... /tmp
then
Quote:[Info] Loading kernel module snd-bcm2835.
libkmod: ERROR ../libkmod/libkmod-index.c:818 index_mm_open: magic check fail: a000000 instead of b007f457
later ...
Quote:[....] Starting rpcbind daemon: cannot create socket for udp6
rpcbind: cannot create socket for udp6
then
Quote:[....] Starting NFS common utilities statdlibkmod: ERROR ../libkmod/libkmod-index.c:818 index_mm_open: magic check fail: a000000 instead of b007f457
libkmod: ERROR ../libkmod/libkmod-index.c:818 index_mm_open: magic check fail: a000000 instead of b007f457
libkmod: ERROR ../libkmod/libkmod-index.c:818 index_mm_open: magic check fail: a000000 instead of b007f457
later ...
Guys this is ludicrously hard to trap these errors. Can we please bundle bootlogd and have it running immediately in the default image? See here:
http://www.cyberciti.biz/faq/debian-ubuntu-record-boot-messages/
Seems like an ultra trivial solution to trapping boot errors (assuming it works) whereas dmesg at present is pretty much useless because it only seems to contain positive non-error information! It almost seems as if dmesg goes out of it's way to IGNORE errors!
I would have tried bootlogd myself on this troublesome image/install, but I can not get apt working either
Quote:xbian@xbian:~# sudo apt-get update
...
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/dpkg/status
E: The package lists or status file could not be parsed or opened
That is assuming that the package exists in our apt.
*sigh*
Not the most productive of evenings but I'm sure we've all been there and done that.
RE: XBian 1.0 Alpha 4 Bugthread - CurlyMo - 7th Jan, 2013 10:22 PM
You forgot to do:
Code:
depmod -aRE: XBian 1.0 Alpha 4 Bugthread - da_didi - 10th Jan, 2013 03:34 AM
(7th Jan, 2013 12:09 AM)CurlyMo Wrote: Wrong startup script
Code:
sudo /etc/init.d/xbmc start
Well, then there is no output on the console and I didn't find any error logs..