Forum

Hi guys,

I've just installed Xbian 1.0B2 and wanted it to be up to date. So I used the "Update All" Option in XBMC.
When it was finished I did a reboot but Xbian didn't start again. It's hanging on the splash screen "configuring network".

Tried it again and again, but everytime the same. (with the tool over ssh and even manually)

I stay for now without updating, but am interested why it doesn't work for me. Somebody knows?

greetings
josch

-- edit --

SOLUTION HERE

-- edit --

Software
XBian version: 1.0B2
XBMC version: default
Overclock settings: default

Hardware
Power supply rating: enough (DLink Hub)
RPi model (model A/B 256mb/512mb): 512mb
SD card size and make/type: 4GB Transcend
Network (wireless or LAN): wireless
Connected devices (TV, USB, network storage, etc.): TV, USB Hub, Wifi Dongle

You installed from an image or via an installer?

I assume when you say manually you did;

sudo apt-get update
sudo apt-get upgrade.

Can you run sudo apt-get update, sudo apt-get -s upgrade and post the output. (The -s is for a simulation)

@joschh

do you use nfs mounts in /etc/fstab ?

does the splash exits after 100s as XBMC does not start so it should be considered failed and console should show up

Sure I can, thanks for that fast support!

I installed it via the official installer and yes, used just apt-get when talking about updating manually.



@mk01:
I don't use nfs and didn't modified anything before updating. (//edit: only setup wifi and changed localisation/language to german)

Thought I was waiting more than 100s - the loading bar is getting full very slowly and then just keeps showing the full bar. Nothing happens.
But maybe I just waited only 99s? - Hmm, actually i leave it running for a very long time. But if this info would help, I could do the update again
to be absolutely sure I waited over 100 seconds.

I wonder if this has something to do with you being on wireless.

Do you have an Ethernet connection available?

I've seen reports of hangs before where Xbian is trying to connect to ETH0 and not WLAN0.

I have a feeling that if you connect an Ethernet cable your problems will go away.

There is an option for Ethernet but it's kind of complicated and my girlfriend would be killing me if would start rearranging the living room right now.

I will test it later or tomorrow and post the result.... But if it would work with ETH0, what I have to change to set it back to WLAN0?

It wasn't a case of killing anyone - but trying to solve the issue. Just drag the RPi to a Ethernet connection and see if my theory is correct.

There was a recent post similar to this - where ETH0 was removed from auto and all worked fine.

(10th Jan, 2014 03:49 AM)IriDium Wrote: [ -> ]ETH0 was removed from auto and all worked fine.

Could you please declare "auto" for me? Is it a specific file I have to edit?

Managed to get a long ethernet cable, so rearranging the living room isn't needed anymore and I can do it without losing my life.

Just finished testing:

1. The splash screen "configuring network" stays all the time. No console even after plenty minutes.
2. It does boot normal with ethernet connected!
3. Wifi works well too after booting, but still no boot if I unplug the ethernet cable.



greetings
josch

if you removes eth0 from list of "auto" adapters?

(editing /etc/network/interfaces)

Yep, now it's booting without ethernet connected!

Thats how /etc/network/interfaces now looks like:


That fix is working, but I'm interested in why this is necessary?
No problem if no one knows, I'm just asking for learning.


Thank you both!
josch

if eth0 is flagged as auto, system will not consider networking up until eth0 will be configured. without cable attached this won't happen. making related services and jobs not start.

So maybe this should be skipped if eth0 won't come up. I can imagine that many users only use wlan0 and could be frustrated if the Pi won't boot after updating Xbian.
I mean, before the update there was no need edit something - it worked independently from eth0.

Have a nice day.

@josch

this is not something XBian developed. this is how system was designed for years. maybe this wasn't so visible before with linear sysvinit boot scripts, but is crucial for parallel processing with upstart.

also we were thinking of this possibility and that's why XBian will remove "auto" from eth0 if you configures wlan0 (in xbian-config CLI or XBMC). (eth0 will still be configured if cable is plugged in and there is link even without "auto" - but if it fails, it won't affect the process in any negative way).

another issue there is that due to BUG in debian scripts in previous release, eth0 was always being configured regardless of being or not "auto" what was masking / hiding this standard process with "auto" being important and made users not considering this as misconfiguration.

then with migration to upstart we had to consider somehow if auto should or shouldn't be added (if was missing) by update script as this correction of Debian BUG and not having "auto" on eth0 would hit significantly larger group of installations a leave them without networking.

maybe this happened to you. you configured wlan0, auto was taken from eth0 and all was fine. then auto came back. I will review xbian-update package for this part.

maybe you can in-between just confirm that xbian-update was installed during the update run when you realized after.

Thanks for information. That makes it more clear to me.