ksosez Wrote:Just a heads up. I did a clean install of 10 using the minimal install method. using the script with nvidia drivers 195 and 260 both hung on reboot.

EDIT: this is with 1.023 for both.

EDIT2: 190 didnt work either..All hung after reboot

The install worked fine under 9.11 and a previous version of the script. I then switched to SVN PPA and it installed the SVN build for 10 release and booted just fine..

X3lectric Wrote:The install procedure is the same now as on all scripts b4, only the 260 drivers were added to the initial 10.0 install

• Installed Minimal Ubuntu
  
• Downloaded the script
  
• When prompted, updated the script
  
• Installed XBMC Dharma 10.0
  
• Rebooted.
  
• This then loads the XBMC splash screen... But then prompts for a Linux user log-in.
  
• Once logged in you see a Zombie process running.
  

• Is the XCI script still being supported?
  
• Will the XCI script be fixed?
  
• Is there any guides or work arounds?
  
• Is it worth trying to install XBMC Live?
  

johan_tre Wrote:Hi X3lectric,

for the wifi setup I have a small script that is a better version that supports wifi security.

Currently XCI offers the choice of a list of scanned networks.
My network however is hidden. Here one should be able to type in his network name, (this is the ssid) so an inputbox would be a better option here.
Also the password should have this possibility.

From the current script I've seen that the wpa-psk is DIRECTLY filled in, which I believe will never be working.

below how to get this encription working.
mySSID: the wpa-ssid
myNetworkPass: the network password that ones has to know to get onto the wifi network.
ra0: the name of my network device.

Note: grep " psk" contains 1 tab in front of the psk.
While editing, do this by Ctrl+v and typing the tab key.

Code:

[b][u]WPAKEY[/u][/b]=$(wpa_passphrase [b]mySSID[/b] [b]myNetworkPass[/b] | grep "    psk" | awk 'BEGIN {FS="="} {print $2}')

#echo "auto wlan0" >>/etc/network/interface

echo "auto [b]ra0[/b]" >> interfaces
echo "iface [b]ra0[/b] inet dhcp" >> interfaces
echo "wpa-driver wext" >> interfaces
echo "wpa-ssid [b]mySSID[/b]" >> interfaces
echo "wpa-ap-scan 2" >> interfaces
echo "wpa-proto RSN" >> interfaces
echo "wpa-pairwise CCMP" >> interfaces
echo "wpa-group CCMP" >> interfaces
echo "wpa-key-mgmt WPA-PSK" >> interfaces
echo "wpa-psk "[b][u]$WPAKEY[/u][/b] >> interfaces

freestyler3000 Wrote:F.A.0. X3lectric and all...

*snip

• Is the XCI script still being supported?
  

freestyler3000 Wrote:

• Will the XCI script be fixed?
  

freestyler3000 Wrote:

• Is there any guides or work arounds?
  

X3lectric Wrote:don't use 260 drivers on first install, bug with ppa from the nvidia vdpau guy, so get on his case.

https://sourceforge.net/apps/phpbb/xci/viewtopic.php?f=3&t=141&p=500#p500

that proves that 195 is still good I will do a last change.

also try with alsa normal/195 drivers and 1.0.23/195 drivers I would like to know if 1.023 also affects install....

I backported alsa but I am NO expert in packaging, hence why i asked for volunteers to help out and also cause Im seriously disabled.

other issue is https://sourceforge.net/apps/phpbb/xci/viewtopic.php?f=3&t=140&p=504#p504

I have that user looking into it... I left bed to go to toilet and checked mails on way back, thats how great my life is atm.

thx.

X3lectric Wrote:The install procedure is the same now as on all scripts b4, only the 260 drivers were added to the initial 10.0 install

I have a guy here saying itworks finewith 195 https://sourceforge.net/apps/phpbb/xci/viewtopic.php?f=3&t=141&p=500#p500

I just dont know if alsa 1.0.23 makes a difference on first install cause no one posts logs.

SO I suspect that alsa 1.0.23 + 260 on initial is to blame, but this is only a guess.

CAN anyone experiment and confirm that 195 and normal alsa is ok on xci 1.0995?

BTW the nvidia drivers come from https://launchpad.net/~nvidia-vdpau/+archive/ppa

so please report bugs to help me out cause just one complaint from me is not enough.

from 256.52 to 260 hes packaged the drivers in a non standard way, so please help me help you.

freestyler3000 Wrote:

• Is it worth trying to install XBMC Live?
  

freestyler3000 Wrote:Any help appreciated... This is a super great script I've used in the past and I hope it gets fixed,sometime soon...

Freestyler

Quote:OpenElec could intercept the need for having another installation download everytime.

Quote:A better option would be to split it up in his functionalities.

X3lectric Wrote:@ johan_tre
Its not hard to maintain when the problems are solved annd it is all modular so each area says what it does...

X3lectric Wrote:Nothing good comes of easy/lazy work.

X3lectric Wrote:Openelec and the script cant be used together simply because openelec is not Debian based, I know I spoke to the dev many times.

X3lectric Wrote:yet your suggestion could probably make it simpler but I see now, it unlikely.

X3lectric Wrote:Also the point of having a installer with menu parts all in one despite size is easier to maintain and easier for the end user to use.

X3lectric Wrote:I wouldn't want to be hours running scripts when I can do it all in one hour.

X3lectric Wrote:Thx anyway man, rather you tell me that you not going to do it then to say yes and disapear like the rest of all the others, including the other co-founder.

johan_tre Wrote:what do you mean by that?
I hope you're not offended when I found it a hard-to-maintain script.
And I've done the effort of reading it, in order to solve the problem I had at the time.
Conclusion for me: It's far to long to be kept clear, all the dialog clutter doesn't do good to it, the mix between installation ways doing the same thing, the incorrect Alsa installation, the ever recurring ppa problems (you're not the only having these prob's, xbmscript has the same issue), it's all just confusing. All in one script.

Quote:all the dialog clutter doesn't do good to it

Quote: the incorrect Alsa installation

Quote:the ever recurring ppa problems *snip You'll understand the irritation when installing Dharma and nvidia 256 (my previous setup) was also not installing properly anymore.
Then I'm out of options

Quote:Guess what... not so much was changed. So what could be the problem then?? It's at THAT moment you decide to look for other options. Forced a little, because of the lack of knowledge and support.
I wanted a solution for my problem.

See what I mean?
Understand how I came to the ideas?
They are not meant to be offending. Only to help.

Quote: it doesn't work. Period.

Quote:Shit, how come?
Has OpenElec's distro no similar "dialog" package then?

Quote:Can you imagine what a non-developer sees opening that script?
His conclusion will be simple: it doesn't work. Period.

Quote:The menu handler is not a good idea, is that what you're saying?
If it increases simplicity by splitting up in an flexible way, why not?
To me it seemed a good idea... (but maybe unfeasible?)

Quote:Please explain? "hours running scripts". For which conditions you mean that?
A split up can't make that difference, can it?
When I speak about splitting up, I mean this in an dynamic way. So that the user can't see the difference between the old and the new script. The only difference would be simplicity when a problem occurs, and a cause of problem could easier be pointed.
One script can call another, no?
Having one script representing the main stream of dialogs etc, calling scripts doing the work is not such a bad idea, no?
Maybe I'm to progressive in my perception about the possibilities here?