2013-01-11, 18:12
I installed network Manager yesterday to be able to configure my wireless via xbmc to find out that it disables my usb-cec on build. Has anyone experience this, and if so is there a solution?
2013-01-11, 19:06
One thing that did not work for me after completing the install and initial setup was "Exit". If I chose "exit" from the power menu, I would be kicked out to a text screen, but no command line. Just a few lines of some messages (one was something about checking battery??). I tried a few keystrokes and nothing happened. Then I tried ctrl+alt+del, and the system rebooted into XBMC.
Is there a way to exit XBMC to the Linux command line? Or do I always have to telnet in from another machine? I'm at work now so can't post a debug log, but if necessary I can do that tonight.
Thanks...
Is there a way to exit XBMC to the Linux command line? Or do I always have to telnet in from another machine? I'm at work now so can't post a debug log, but if necessary I can do that tonight.
Thanks...
2013-01-11, 19:41
ctrl+alt+F1 or F2 and F7 to get back
No, exit doesn't work as intended, idk why and honestly doesn't matter since the above works and most ppl use putty to do stuff.
uNi
No, exit doesn't work as intended, idk why and honestly doesn't matter since the above works and most ppl use putty to do stuff.
uNi
2013-01-11, 20:13
Can anyone help with a update/upgrade problem?
I run sudo apt-get update which, after all the "gets" says:
So I run
Which hangs on:
only hitting Ctrl + C fixes the hang but than I get this:
Trying to perform an upgrade hangs eventually:
Nothing fixes this hang. Ctrl+C does not work. A hard reset is then the only way to reboot the system but I did get upgraded to RC3 of XBMC.
I run sudo apt-get update which, after all the "gets" says:
Code:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.Code:
sudo dpkg --configure -aWhich hangs on:
Code:
Setting up linux-image-3.5.0-19-generic (3.5.0-19.30) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.5.0-19-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-19-generic /boot/vmlinuz-3.5.0-19-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.5.0-19-generic /boot/vmlinuz-3.5.0-19-generic
update-initramfs: Generating /boot/initrd.img-3.5.0-19-genericonly hitting Ctrl + C fixes the hang but than I get this:
Code:
^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.5.0-19-generic.postinst line 1010.
dpkg: error processing linux-image-3.5.0-19-generic (--configure):
subprocess installed post-installation script returned error exit status 2
Setting up linux-libc-dev:amd64 (3.5.0-21.32) ...
Setting up libshairport1:amd64 (1:1.2.1~git20121216.16395d8-0~ppa1~quantal) ...
dpkg: dependency problems prevent configuration of linux-image-extra-3.5.0-19-generic:
linux-image-extra-3.5.0-19-generic depends on linux-image-3.5.0-19-generic; however:
Package linux-image-3.5.0-19-generic is not configured yet.
dpkg: error processing linux-image-extra-3.5.0-19-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
linux-image-generic depends on linux-image-3.5.0-19-generic; however:
Package linux-image-3.5.0-19-generic is not configured yet.
linux-image-generic depends on linux-image-extra-3.5.0-19-generic; however:
Package linux-image-extra-3.5.0-19-generic is not configured yet.
dpkg: error processing linux-image-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic; however:
Package linux-image-generic is not configured yet.
dpkg: error processing linux-generic (--configure):
dependency problems - leaving unconfigured
Setting up xbmc-bin (2:12.0~git20121223.0918-rc2-2quantal) ...
Setting up libglib2.0-0:amd64 (2.34.1-1ubuntu1) ...
Setting up xbmc (2:12.0~git20121223.0918-rc2-2quantal) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for python-support ...
Errors were encountered while processing:
linux-image-3.5.0-19-generic
linux-image-extra-3.5.0-19-generic
linux-image-generic
linux-genericTrying to perform an upgrade hangs eventually:
Code:
xbmc@xbmc:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
linux-headers-generic linux-image-generic
The following packages will be upgraded:
gnupg gpgv memtest86+ mountall python3-dbus python3-distupgrade
ubuntu-release-upgrader-core ufw xbmc xbmc-bin
10 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
4 not fully installed or removed.
Need to get 37.5 MB of archives.
After this operation, 1,112 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main mountall amd64 2.42ubuntu0.3 [68.8 kB]
Get:2 http://ppa.launchpad.net/wsnipex/xbmc-xvba/ubuntu/ quantal/main xbmc all 2:12.0~git20130104.1024-rc3-0quantal [22.2 MB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main gpgv amd64 1.4.11-3ubuntu4.1 [185 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main gnupg amd64 1.4.11-3ubuntu4.1 [807 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main memtest86+ amd64 4.20-1.1ubuntu2.1 [285 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main python3-dbus amd64 1.1.1-1ubuntu0.1 [101 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main ubuntu-release-upgrader-core all 1:0.190.5 [27.9 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main python3-distupgrade all 1:0.190.5 [142 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main ufw all 0.33-0ubuntu2.1 [161 kB]
Get:10 http://ppa.launchpad.net/wsnipex/xbmc-xvba/ubuntu/ quantal/main xbmc-bin amd64 2:12.0~git20130104.1024-rc3-0quantal [13.5 MB]
Fetched 37.5 MB in 36s (1,025 kB/s)
Preconfiguring packages ...
(Reading database ... 90260 files and directories currently installed.)
Preparing to replace mountall 2.42ubuntu0.2 (using .../mountall_2.42ubuntu0.3_amd64.deb) ...
Unpacking replacement mountall ...
Preparing to replace gpgv 1.4.11-3ubuntu4 (using .../gpgv_1.4.11-3ubuntu4.1_amd64.deb) ...
Unpacking replacement gpgv ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up gpgv (1.4.11-3ubuntu4.1) ...
(Reading database ... 90260 files and directories currently installed.)
Preparing to replace gnupg 1.4.11-3ubuntu4 (using .../gnupg_1.4.11-3ubuntu4.1_amd64.deb) ...
Unpacking replacement gnupg ...
Processing triggers for install-info ...
Processing triggers for man-db ...
Setting up gnupg (1.4.11-3ubuntu4.1) ...
(Reading database ... 90260 files and directories currently installed.)
Preparing to replace memtest86+ 4.20-1.1ubuntu2 (using .../memtest86+_4.20-1.1ubuntu2.1_amd64.deb) ...
Unpacking replacement memtest86+ ...
Preparing to replace python3-dbus 1.1.1-1 (using .../python3-dbus_1.1.1-1ubuntu0.1_amd64.deb) ...
Unpacking replacement python3-dbus ...
Preparing to replace ubuntu-release-upgrader-core 1:0.190.4 (using .../ubuntu-release-upgrader-core_1%3a0.190.5_all.deb) ...
Unpacking replacement ubuntu-release-upgrader-core ...
Preparing to replace python3-distupgrade 1:0.190.4 (using .../python3-distupgrade_1%3a0.190.5_all.deb) ...
Unpacking replacement python3-distupgrade ...
Preparing to replace ufw 0.33-0ubuntu2 (using .../ufw_0.33-0ubuntu2.1_all.deb) ...
Unpacking replacement ufw ...
Preparing to replace xbmc 2:12.0~git20121223.0918-rc2-2quantal (using .../xbmc_2%3a12.0~git20130104.1024-rc3-0quantal_all.deb) ...
Unpacking replacement xbmc ...
Preparing to replace xbmc-bin 2:12.0~git20121223.0918-rc2-2quantal (using .../xbmc-bin_2%3a12.0~git20130104.1024-rc3-0quantal_amd64.deb) ...
Unpacking replacement xbmc-bin ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Processing triggers for python-support ...
Processing triggers for hicolor-icon-theme ...
Setting up linux-image-3.5.0-19-generic (3.5.0-19.30) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.5.0-19-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-19-generic /boot/vmlinuz-3.5.0-19-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.5.0-19-generic /boot/vmlinuz-3.5.0-19-generic
update-initramfs: Generating /boot/initrd.img-3.5.0-19-generic
Setting up linux-image-3.5.0-19-generic (3.5.0-19.30) ...Nothing fixes this hang. Ctrl+C does not work. A hard reset is then the only way to reboot the system but I did get upgraded to RC3 of XBMC.
2013-01-11, 20:24
Whats this got to do with script?
Your upgrading Linux as well why?
uNi
Your upgrading Linux as well why?
uNi
2013-01-11, 20:30
(2013-01-11, 20:13)ozzyman778 Wrote: <snipped>
i had that issue on my system when i used this script a month or so ago on a new build. did several clean installs and was unable to get around it. since seemingly no one else had the issue and the script didn't seem to be actively developed anymore i ended up with a fresh mini install and configuring things myself. in the interest of trying to find a commonality here's my system:
i3 3225 on an asrock z77 pro4 mobo
8gb ram
nvidia 610
intel 520 180gb ssd
this is basically the extent of my install:
Code:
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo add-apt-repository ppa:wsnipex/xbmc-xvba
sudo apt-get update
sudo apt-get install nvidia-current
sudo apt-get install xbmc
sudo usermod --group adm,sudo,cdrom,audio,video,plugdev,fuse,vboxusers xbmc
sudo adduser xbmc usersthe one strange thing is that i don't seem to have my tty consoles when i ctrl+alt+f1-f12 but i do most everything over ssh anyway so that's not a big deal. although if anyone knows why that might be i'm open to fixing it
2013-01-11, 20:32
2013-01-11, 20:34
er no you guys are definitely doing something wrong!
uNi
uNi
2013-01-11, 23:58
BTW, Bram77's method and script need to be put on the official wiki. So. Awesome.
2013-01-12, 00:32
(2013-01-11, 20:34)uNiversal Wrote: er no you guys are definitely doing something wrong!
uNi
respectfully disagree. i've done minimal ubuntu xbmc installs on several machines for years (and have done my share of helping on these forums) so i like to think i know what i'm doing for the most part. i generally prefer to do things the long way but i was in a hurry so that's why i gave this script a shot. that time savings went out the window when i did three clean installs and finally a fourth by hand. had the same issue with each install utilizing this script and not at all since i did it by hand. like i said i didn't care enough to see what exact combination of packages, tweaks, etc. the script installed that i didn't caused the issue. when installing on appropriate hardware with the proper ubuntu base the excuse "you did something wrong" goes out the window. the question is is there a problem with the script, hardware, packages, etc?
edit: i also disagree that people should have to hold back on kernel upgrades regardless of their desires. and if that is a stipulation of using the script it should be implemented in the script itself or at the very least stipulated in the OP.
2013-01-12, 00:41
I hope I understand correctly what the problem is here....
During the installation using the script you'll be asked if you want to enable automatic updates. This can be risky because you might turn off the machine while an update process is active in the background. In most cases this doesn't really matter. It will solve itself. But in some cases it might corrupt your apt cache or even you kernel installation. Maybe that's what has happened in these cases?
During the installation using the script you'll be asked if you want to enable automatic updates. This can be risky because you might turn off the machine while an update process is active in the background. In most cases this doesn't really matter. It will solve itself. But in some cases it might corrupt your apt cache or even you kernel installation. Maybe that's what has happened in these cases?
Please add to my reputation if you find my posts usefull (+/- button below posts)
Ubuntu 12.10 minimal XBMC auto-install script :: XBMControl :: Xbmc XBOX Skins :: XBMControl for Android :: Owner of Sudo Systems
2013-01-12, 07:49
(2013-01-11, 19:41)uNiversal Wrote: ctrl+alt+F1 or F2 and F7 to get back
No, exit doesn't work as intended, idk why and honestly doesn't matter since the above works and most ppl use putty to do stuff.
uNi
Do most people use ssh/telnet to solve network connectivity issues? How do you adjust anything on a machine that's not connected to the network?
2013-01-12, 09:15
(2013-01-11, 19:41)uNiversal Wrote: ctrl+alt+F1 or F2 and F7 to get back
No, exit doesn't work as intended, idk why and honestly doesn't matter since the above works and most ppl use putty to do stuff.
uNi
So ctrl+alt+f2 exits to a CLI login... but ctrl+alt+f7 does not put me back in xbmc. Instead it gives the same result as if I tried to "exit" from xbmc using the power menu exit choice. Any ideas?
2013-01-12, 11:44
Then when you were on terminal you killed xbmc, run:
And then ctr+alt+F7 or F6 or whatever try a few combos, mine is F7 maybe yours is some other key for some bizarre reason.
Its not brain surgery this eh?
uNi
Code:
sudo restart xbmc
or
sudo start xbmcAnd then ctr+alt+F7 or F6 or whatever try a few combos, mine is F7 maybe yours is some other key for some bizarre reason.
Its not brain surgery this eh?
uNi
2013-01-13, 06:57
(2013-01-12, 00:41)Bram77 Wrote: I hope I understand correctly what the problem is here....
During the installation using the script you'll be asked if you want to enable automatic updates. This can be risky because you might turn off the machine while an update process is active in the background. In most cases this doesn't really matter. It will solve itself. But in some cases it might corrupt your apt cache or even you kernel installation. Maybe that's what has happened in these cases?
this wasn't the case for me, i didn't have automatic updates enabled for specifically this scenario. it was a self-initiated update where it would hang updating the initramfs which no amount of futzing would fix.
