[Koenkk]

(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.

AFAIK the problem with the fresh install can be easily fixed with a hotfix

[Smultie]

If upgrading causes that many problems, then just don't offer the option to upgrade imho.

[raspberry_pd]

(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

No that is not acceptable. The alphas were so much better than this beta that everyone had a reasonable expectation that the beta would be even better. Instead this beta is much worse than the alphas. Really Rikardo, no point dodging the issue. These things happens but don't tell people their expectations for excellence were unfounded. To some people, 'bleeding edge' means the latest tested and mostly reliable software. A good example is Firefox Aurora. It's alphaware but I've been using it since Mozilla switched to rapid releases and rarely have I experience any issues. I realise that XBian doesn't have the resources of Mozilla but not utilising the users who are willing to help before a "release" is silly.

---

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

+1

Full respect to the XBian people. I've been absent for quite a while so I can't really expect to whine too much without putting in the effort to help. However all humanity is imperfect. This was a bad release and rightfully has been pulled. Let's not deny it and move on.

I'm willing to do clean installs of 1A5 and then upgrade to beta if that is the testing scenario that needs more work.

[rikardo1979]

@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-

[kraleksandr]

So, what I have to do with my GPIO IR receiver?
It works with alpha5 upgraded to beta1, but with clean install of beta1 I cant make it works.
Also, mode2 says that it cant find the /dev/lirc0.

[Fred]

(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

Can you try this:

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

Terminal

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

[kraleksandr]

@Fred
I've did this several hours ago. Otherwise it says that mode2 notfound.

---

Terminal

sudo modprobe lirc_rpi

Now mode2 can see IR receiver

---

Sometimes ago I have this problem too and someone said that it'll be fixed in the beta1.
So, looks like lirc_rpi loads when something not ready for this and we (I) need to place "sleep 2" somewhere. But where?

[raspberry_pd]

(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-

If I can't say anything nice, better to say nothing at all.

[Epedemic]

Hmm it seems after i left it over night, speed is back to normal... I will install my crap (SB, nzbget, samba & trakt) and see if it still works, and if it survives a reboot

[nsviper]

(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?

Just to confirm, this worked.

Didn't need to do anything with /etc/fstab, just the line change in config.txt

I know beta has been pulled for now, but will definitely be testing it once its available again - have reverted to Alpha5 on my test Pi but can see a significant performance difference between Alpha5 and Beta1

Look forward to its re-release!

[Scott4uf21]

So many posts on issues posted after mine, not a word on my my wifi dongles that worked for alpha don't work on beta?

Went back to Alpha this morning, full strength on the same wifi, guess i have to stick with alpha for my customers (mine runs directly connected, still like the beta, hope the issues get fixed soon). Thanks for all the work you guy put in on here and Xbian!

[f1vefour]

I think having a select group of testers which have shown they are both knowledgeable of the system being tested and good at debugging/resolving issues is a great idea before future releases.

Most of the major issues could be avoided and the rest of the Xbian users can then help iron out the smaller issues once a general beta release has been produced.

Once again just my opinion.

[Uncle_Tubbie]

I did a fresh install and used sudo update. Everything here is fine, with the execption on an ADD_ON not working correctly, but I believe that to be the add-on and on Xbian.

Thanks guyz

[hawkpd]

May be slightly off topic for this forum but then again maybe not as the Beta release has been pulled. Question is how do I get a new build or upgrade of Xbian running XBMC 12.2? I'm still learning Linux so go easy!

I have a nicely working setup of Xbian 1.0A5 (XBMC 12.1) on a Pi and XBMC on a couple of PC's using a shared DB on my Synology NAS so I have been planning an upgrade gradually!

I did a fresh install of Xbian 1.0A5 on a test SD card on Sunday night followed by the upgrade commands I had found "sudo apt-get update" and "sudo apt-get install xbian-package-xbmc -y" followed by the nightly install mentioned in the notes to fix the mouse jumping issue. All worked fine and it upgraded XBMC to version 12.2. So I was planning at some point to upgrade my live system!

But then the new Beta version was released on Tuesday (which I have tried!) and since then the upgrade commands above apart from the first get update command, fail to work! I assumed it would still work as its a different download package I guess!?

On Thursday the command "sudo apt-get install xbian-package-xbmc -y" generated a lot of errors ending with the error "E: There are problems and -y was used without --force-yes"
As a test I ran the command again as "sudo apt-get install xbian-package-xbmc -y --force-yes" and it did a lot more but still did not upgrade XBMC.

Today its changed again and results in the error below.

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
xbian-package-xbmc : Depends: upstart but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


What am I doing wrong? Is there a working XBMC 12.2 version? Is there a simply fix or should I hold on XBMC 12.1 for now? And apologies if this post is too long!

[hans30]

I've updated from alpha 5 to beta 1, the boot time is very fast now!!

i moved the installation to usb drive (philips 10gb), loaded de gpio drivers and i can play games with retropie.

The mce remote works out of the box with al the buttons.
For people who cant' get the GPIO IR receiver working, (logitech harmony and mce remotes) this me be a possible solution:

Try this with putty:

nano /etc/modules then add lirc_rpi to /etc/modules


# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

lirc_rpi



next to do is;

nano /etc/lirc/lircd.conf then add the content below;

#
# brand: HP
# model no. of remote control: TSGH-IR01
# devices being controlled by this remote: HP Slimline S3100y
#
# RC-6 config file
#
# source: http://home.hccnet.nl/m.majoor/projects_remote_control.htm
# http://home.hccnet.nl/m.majoor/pronto.pdf
#
# used by: Philips
#
#########
#
# Philips Media Center Edition remote control
# For use with the USB MCE ir receiver
#
# Dan Conti dconti|acm.wwu.edu
#
# Updated with codes for MCE 2005 Remote additional buttons
# *, #, Teletext, Red, Green, Yellow & Blue Buttons
# Note: TV power button transmits no code until programmed.
# Updated 12th September 2005
# Graham Auld - mce|graham.auld.me.uk
#
# Radio, Print, RecTV are only available on the HP Media Center remote control
#
#
# Updated with codes for MCE 2007 Remote additional buttons
# Visualization, Aspect, SlideShow, Eject
# Note:
# Renamed some buttons: DVD->DVDMenu, More->MoreInfo, Star->Asterisk, Hash->Pound
# Note:
# Blue, Yellow, Green, Red, and Teletext buttons do not exist on the HP remote

begin remote

name mceusb
bits 16
flags RC6|CONST_LENGTH
eps 30
aeps 100

header 2667 889
one 444 444
zero 444 444
pre_data_bits 21
pre_data 0x37FF0
gap 105000
toggle_bit 22
rc6_mask 0x100000000


begin codes

#seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009
Media 0x00007b7f
PlayPause 0x00007b91


#unused by HP remote
Blue 0x00007ba1
Yellow 0x00007ba2
Green 0x00007ba3
Red 0x00007ba4
Teletext 0x00007ba5

#ba6 - bae unused
BA6 0x00007ba6
BA7 0x00007ba7
BA8 0x00007ba8
BA9 0x00007ba9
BAA 0x00007baa
BAB 0x00007bab
BAC 0x00007bac
BAD 0x00007bad
BAE 0x00007bae

Radio 0x00007baf
Print 0x00007bb1

#bb2 - bb4 unused
BB2 0x00007bb2
BB3 0x00007bb3
BB4 0x00007bb4

Videos 0x00007bb5
Pictures 0x00007bb6
RecTV 0x00007bb7
Music 0x00007bb8
TV 0x00007bb9

#bba - bbf unused
BBA 0x00007bba
BBB 0x00007bbb
BBC 0x00007bbc
BBD 0x00007bbd
BBE 0x00007bbe
BBF 0x00007bbf
#bc1 - bca unused
BC1 0x00007bc1
BC2 0x00007bc2
BC3 0x00007bc3
BC4 0x00007bc4
BC5 0x00007bc5
BC6 0x00007bc6
BC7 0x00007bc7
BC8 0x00007bc8
BC9 0x00007bc9
BCA 0x00007bca

Eject 0x00007bcb
SlideShow 0x00007bcc
Visualization 0x00007bcd

#bce - bcf unused
BCE 0x00007bce
BCF 0x00007bcf
#bd1 - bd7 unused
BD1 0x00007bd1
BD2 0x00007bd2
BD3 0x00007bd3
BD4 0x00007bd4
BD5 0x00007bd5
BD6 0x00007bd6
BD7 0x00007bd7

Aspect 0x00007bd8
Guide 0x00007bd9
LiveTV 0x00007bda
DVD 0x00007bdb
#NoGap
Back 0x00007bdc
OK 0x00007bdd
Right 0x00007bde
Left 0x00007bdf
Down 0x00007be0
Up 0x00007be1
#NoGap
Star 0x00007be2
Hash 0x00007be3
#NoGap
Replay 0x00007be4
Skip 0x00007be5
Stop 0x00007be6
Pause 0x00007be7
Record 0x00007be8
Play 0x00007be9
Rewind 0x00007bea
Forward 0x00007beb
#NoGap
ChanDown 0x00007bec
ChanUp 0x00007bed
VolDown 0x00007bee
VolUp 0x00007bef
#NoGap
More 0x00007bf0
Mute 0x00007bf1
Home 0x00007bf2
Power 0x00007bf3
#NoGap
Enter 0x00007bf4
Clear 0x00007bf5
#NoGap
Nine 0x00007bf6
Eight 0x00007bf7
Seven 0x00007bf8
Six 0x00007bf9
Five 0x00007bfa
Four 0x00007bfb
Three 0x00007bfc
Two 0x00007bfd
One 0x00007bfe
Zero 0x00007bff
end codes

end remote
#
# this config file was automatically generated
# using lirc-0.8.4a(default) on Mon Feb 23 23:55:04 2009
#
# contributed by
#
# brand: Hauppauge
# model no. of remote control:
# devices being controlled by this remote: PVR-150 Remote (MCE kit)
# SMK dongle 0609:031d
#

begin remote

name mceusb_hauppauge
bits 13
flags RC6|CONST_LENGTH
eps 30
aeps 100

header 2674 870
one 455 427
zero 455 427
pre_data_bits 24
pre_data 0x1BFF82
gap 106288
min_repeat 1
toggle_bit_mask 0x8000
rc6_mask 0x100000000

begin codes
TV 0x1BB9
Music 0x1BB8
Pictures 0x1BB6
Videos 0x1BB5
Power 0x1BF3
Stop 0x1BE6
Record 0x1BE8
Pause 0x1BE7
Play 0x1BE9
Rewind 0x1BEA
Foward 0x1BEB
Replay 0x1BE4
Skip 0x1BE5
Back 0x1BDC
More 0x1BF0
Up 0x1BE1
Left 0x1BDF
Right 0x1BDE
OK 0x1BDD
Down 0x1BE0
VolUp 0x1BEF
VolDown 0x1BEE
Home 0x1BF2
ChanDown 0x1BED
ChanUp 0x1BEC
Mute 0x1BF1
RecTV 0x1BB7
Guide 0x1BD9
LiveTV 0x1BDA
DVD 0x1BDB
One 0x1BFE
Two 0x1BFD
Three 0x1BFC
Four 0x1BFB
Five 0x1BFA
Six 0x1BF9
Seven 0x1BF8
Eight 0x1BF7
Nine 0x1BF6
Star 0x1BE2
Zero 0x1BFF
Hash 0x1BE3
Clear 0x1BF5
Enter 0x1BF4
end codes

end remote


#
# this config file was automatically generated
# using lirc-0.8.4a(default) on Tue Mar 10 19:27:09 2009
#
# contributed by
#
# brand: SIIG Vista MCE remote
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

name vista_mce
bits 16
flags RC6
eps 30
aeps 100

header 2654 889
one 427 427
zero 427 427
pre_data_bits 21
pre_data 0x37FF0
gap 69850
toggle_bit_mask 0x8000
rc6_mask 0x100000000

begin codes
Power 0xEBF3
Pictures 0x6BB6
Radio 0xEBAF
Videos 0x6BB5
Music 0xEBB8
Rec 0x6BE8
Pause 0xEBE7
Stop 0x6BE6
Skipback 0xEBE4
Play 0x6BE9
Skipfwd 0xEBE5
Rwd 0x6BEA
Fwd 0xEBEB
Start 0x6BF2
Back 0xEBDC
More 0x6BF0
Volup 0xEBEF
Voldown 0x6BEE
Chup 0xEBED
Chdown 0x6BEC
Up 0xEBE1
Down 0x6BE0
Left 0xEBDF
Right 0x6BDE
Mute 0xEBF1
Rectv 0x6BB7
Guide 0xEBD9
Livetv 0x6BDA
Dvdmenu 0xEBDB
1 0x6BFE
2 0xEBFD
3 0x6BFC
4 0xEBFB
5 0x6BFA
6 0xEBF9
7 0x6BF8
8 0xEBF7
9 0x6BF6
* 0xEBE2
0 0x6BFF
# 0xEBE3
Clear 0x6BF5
Enter 0xEBF4
end codes

end remote


The last step is to reboot the system (sudo reboot) and you are done