(28th Jun, 2013 06:45 PM)Smultie Wrote:  

(28th Jun, 2013 06:41 PM)rikardo1979 Wrote:  is all about the upgrade from Alpha5 not a fresh flash.

Fresh flash gives problems as well. I know, cause I used a new flash.

(28th Jun, 2013 06:43 PM)rikardo1979 Wrote:  also this was an open test as beta means that it is still in testing stage and all should expect that something may go wrong, thats why it is Beta 1.0

(28th Jun, 2013 07:04 PM)Smultie Wrote:  If upgrading causes that many problems, then just don't offer the option to upgrade imho.

Quote:
Pre-release versions

In conjunction with the various versioning schemes listed above, a system for denoting pre-release versions is generally used, as the program makes its way through the stages of the software release life cycle.

Programs that are in an early stage are often called "alpha" software, after the first letter in the Greek alphabet. After they mature but are not yet ready for release, they may be called "beta" software, after the second letter in the Greek alphabet. Generally alpha software is tested by developers only, while beta software is distributed for community testing.

(28th Jun, 2013 05:08 PM)kraleksandr Wrote:  After clean install I cant use my IR reciever like it didnt exist.

Terminal

xbian@xbian ~ $ mode2
mode2: could not get file information for /dev/lirc0
mode2: default_init(): No such file or directory

(28th Jun, 2013 12:25 AM)CurlyMo Wrote:  

Terminal

sudo chmod +x /usr/local/bin/*

(28th Jun, 2013 07:36 PM)rikardo1979 Wrote:  @raspberry_pd
nice reading for you, especially

Quote:
Pre-release versions

In conjunction with the various versioning schemes listed above, a system for denoting pre-release versions is generally used, as the program makes its way through the stages of the software release life cycle.

Programs that are in an early stage are often called "alpha" software, after the first letter in the Greek alphabet. After they mature but are not yet ready for release, they may be called "beta" software, after the second letter in the Greek alphabet. Generally alpha software is tested by developers only, while beta software is distributed for community testing.

full article
http://en.m.wikipedia.org/wiki/Software_versioning

And as you can see we do not saying that there are no problems an always advice to make a backup before upgrade procedure.
Also there were a major changes between alpha and beta so we have to tested this way as there is no way do it internally as we do not have that many pre-release testers in team
As usual we all do the best to help all and trying to solve the issues asap.
Still,keep in mind, none of us do this as full time job and none of us take any pay. All is done in a free time of each of us.
All need a time.
-thx-

(28th Jun, 2013 12:27 AM)Fred Wrote:  

(27th Jun, 2013 10:43 PM)nsviper Wrote:  

(27th Jun, 2013 10:34 PM)Fred Wrote:  @nsviper: Can you post your current cmdline.txt here, don't have access to it right now.

Here you go boss:

sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=xbian-root-btrfs rootfsopts=subvol=root/@,noatime,compress=lso,thread_pool=1,space_cache,autodefrag rootfstype=btrfs rootwait=10 smsc95xx.turbo_mode=N elevator=noop nohdparm splash logo.nologo quiet loglevel=0 noswap mod_scsi.scan=async

Thanks. Try changing 'root=LABEL=xbian-root-btrfs' to 'root=/dev/sda1'. Also make these changes in /etc/fstab

---

@CurlyMo: Thanks for your extensive testing. Too bad you experience these errors, I'm especially surprised by the XBMC errors since I'm not experiencing them at all. Did you upgrade or do a clean install?