Forum

Software
XBian version: Not shown on 2015.04.04 (System | Summary)
XBMC/Kodi version: 14.2 (April 30 2015)
Overclock settings: default

Hardware
Device type and model Raspberry Pi Model B 512 MB
Power supply rating: 2.4A
SD card size and make/type: Various
Network (Ethernet or wireless): Both/Either
Connected devices TV

Log files
Link to logfile(s): None

Problem description:
Using the XBian Installer (V.1.21, the only generation that will boot is 2015.04.04? All others (2015.03.07, x.04.11, x.04.18 & x.04.25) will not boot

How to reproduce:
Use installer to create SD card with image 2015.04.04 and test. It boots and to all intent and purpose is working.
Using the exact same resources (Pi, installer, SD card) repeat with later images. Pi will not boot. No green SD activity LED seen at all!





Regards, Martin

What about when you install without the installer? If you've tried that is.

(7th May, 2015 09:32 AM)f1vefour Wrote: [ -> ]What about when you install without the installer? If you've tried that is.

Hi,

Yes, I have. I am running SuSE 13.2 on a desktop and I had been using the Suse ImageWriter v1.10.
This had been fine for a very long time. However, and I don't know when, but it then stopped working (ie creating a bootable SD card).
At first, thinking that it was just a problem with the latest image, I made the SD card with the last known working image (2015.04.04) and upgraded.
However, after multiple image releases resulted in the same non-booting card, I thought it was time to try and figure out why.

I only listed the XBian Installer in the opening post, because I guessed that it would be dismissed if I only reported failure using the SuSE ImageWriter. "Keep it Simple" and "In House"!

Looking forward to any additional thoughts you may have....

Regards, Martin

For some reason when you use version 2015.04.25 theres no boot files installed in the xbianboot/ partition.
I think they must've messed up when they were making it.

(9th May, 2015 10:39 AM)liamc12 Wrote: [ -> ]For some reason when you use version 2015.04.25 theres no boot files installed in the xbianboot/ partition.
I think they must've messed up when they were making it.

Do you think that is also the only reason with versions x.y.07, x.y.11 & x.y.18?
Seems awfully careless to make the same mistake 4 times!!
Or maybe it is just that no one is pointing out the problem to the package makers?

Regards, Martin

(11th May, 2015 09:20 PM)mprowe Wrote: [ -> ]

(9th May, 2015 10:39 AM)liamc12 Wrote: [ -> ]For some reason when you use version 2015.04.25 theres no boot files installed in the xbianboot/ partition.
I think they must've messed up when they were making it.

Do you think that is also the only reason with versions x.y.07, x.y.11 & x.y.18?
Seems awfully careless to make the same mistake 4 times!!
Or maybe it is just that no one is pointing out the problem to the package makers?

Regards, Martin

I honestly don't know if they made a mistake four times or not but if anyone has installed the latest version correctly (2015.04.25) then by all means please let me know, if not, they they must have messed up 4 times but nobody has reported it or they're in the process of fixing it atm, I'm not sure to be honest.

WoooHoooo..... Its working again!

So, what's changed?
If I download the image file from SourceForge its called "XBian_2015.05.16_imx6.img.gz"
But if I use the Xbian Installer (still v.1.21) its called "XBian_Stable_rpi.img.gz"
Are they they the same? Why the change from a (reasonably) understandable naming convention?
How has the Xbian Installer stopped listing all the images from its working directory and now only lists: Stable,
2015.04.04 & 2015.03.31?

And lastly, how can I see what Xbian version is in use from the Confluence GUI, now that this information is missing from System | Settings?

Regards, Martin

There is nothing wrong with the symlinks:

Sorry CurlyMo, but that is too cryptic for me!
If someone would translate for me, that would be wonderful. Otherwise CurlyMo has waisted his time (I'm just guessing that "he" is a He?).

Also returning to naming conventions: What's with dropping the date in the image name and using non-temporal "stable" & "latest".
Which to my mind, do not mean anything once the week is out!

Best regards, Martin

You told me that the file XBian_2015.05.16_imx6.img.gz is actually XBian_Stable_rpi.img.gz. If you look at the list, you'll see that XBian_Stable_rpi.img.gz is the same as XBian_2015.04.04_rpi.img.gz. So your comments is incorrect in this sense.

Secondly, the reason we use this naming convention can be read here:
http://www.xbian.org/xbian-stable-release/

Thirdly, the installer just lists the versions available for a specifc platform.

(20th May, 2015 06:31 AM)CurlyMo Wrote: [ -> ]You told me that the file XBian_2015.05.16_imx6.img.gz is actually XBian_Stable_rpi.img.gz. If you look at the list, you'll see that XBian_Stable_rpi.img.gz is the same as XBian_2015.04.04_rpi.img.gz. So your comments is incorrect in this sense.

Sorry, if that is how it read. I did not intend to say anything, I was just asking...

Quote:Secondly, the reason we use this naming convention can be read here:
http://www.xbian.org/xbian-stable-release/

Thank you. I have now read that paper and can you confirm my understanding?
1. That although the above paper says that you are going to use a date-format file name, that is now no longer going to happen?
2. The file name for the same image will be different on SourceForge (XBian_Latest_rpi.img.gz) and the Xbian download page (quote from above paper: These versions should soon be accompanied by a XBian_2014.12.31-2_rpi.img.gz and so on for direct download from our download page.)?

To test my understanding (and confirm my actions), how do I see what generation of Xbian I have actually installed on my PI?
Is the missing information from the "System" > "System Info" > "Summary" page, just a glitch in recent versions or is it hidden somewhere else?

Quote:Thirdly, the installer just lists the versions available for a specifc platform.

Based on what?
1. The content of MY local working directory? Or
2. Reference to YOUR repository?

Thank you very much for all your attention, Martin

(20th May, 2015 05:48 PM)mprowe Wrote: [ -> ]Sorry, if that is how it read. I did not intend to say anything, I was just asking...

No problem.

Quote:Thank you. I have now read that paper and can you confirm my understanding?
1. That although the above paper says that you are going to use a date-format file name, that is now no longer going to happen?

As you can see in the list it still is. The latest image is from 19th of may.

Quote:2. The file name for the same image will be different on SourceForge (XBian_Latest_rpi.img.gz) and the Xbian download page (quote from above paper: These versions should soon be accompanied by a XBian_2014.12.31-2_rpi.img.gz and so on for direct download from our download page.)?

Depend on when an image was created. The latest image always links to the last date. The stable image links to that image people told us to be working well ootb.

Quote:To test my understanding (and confirm my actions), how do I see what generation of Xbian I have actually installed on my PI?
Is the missing information from the "System" > "System Info" > "Summary" page, just a glitch in recent versions or is it hidden somewhere else?

Not sure about Kodi, but you can look in the top left op de xbian-config from the terminal.

Quote:Based on what?
1. The content of MY local working directory? Or
2. Reference to YOUR repository?

Thank you very much for all your attention, Martin

Based on this page: http://sourceforge.net/projects/xbian/rss?path=/release

Having another look at the "img" from windows installer... 2 new additions. Test running 5.19.15 now. Thank you to who ever got this bug removed, so far soooooooooooooooo good. 15 minutes in, all set up n looking very nice. TY again for the people behind the screen. XBian is awesome as usual.

A new crew member @Nachteule was assigned to the image building and fixed it for us

(21st May, 2015 05:21 PM)CurlyMo Wrote: [ -> ]A new crew member @Nachteule was assigned to the image building and fixed it for us

... and a big thanks from me too.
And of course to CurlyMo for tolerance in explaining all my questions.

Thank you, Martin