(1st Dec, 2013 09:01 PM)mk01 Wrote: [ -> ]actually yes, I have one suggestion - to follow the steps I posted precisely.
what you did is not going to help help. this because
1) the file which needs to be updated is /etc/sysctl.d/xbian.conf
2) parameters from the file are put into effect very very early during boot process - if you only change file, nothing happens.
3) you updated /etc/sysctl.conf with correct values but kept /etc/sysctl.d/xbian.conf as it was before. during reboot then this happens:
- values are read/set from sysctl.conf file.
- values are then read/set (overwritted) with again old values from xbian.conf (located at /etc/sysctl.d).
- we are exactly where we were.
if you have extracted /etc/sysctl.d/xbian.conf you can just copy it over (but to correct location) and reboot.
and to see the process, you simple "top", when started press "i", then "c", "s", "1" and [enter]. but I suppose it is "mmcqd" (kernel thread writing physical data to mmc media card).
@
mk01
indead it's the mmcqd kernel thread. Take's 50% of my CPU.
Unfortunately I am not able to install the xbian-update_1.0.2-11_armhf.deb package.
I have deleted both the /etc/sysctrl.d/xbian.conf and /etc/sysctrl.conf file.
Rebooted
But the installation takes forever.... mmcqd thread takes 50% of CPU.
After 8 minutes
Terminal
dpkg: error while cleaning up:
unable to remove newly-installed version of `/var/tmp/xbian_update/pchanges/sysctl.conf': Read-only file system
dpkg: error while cleaning up:
unable to securely remove '/var/lib/dpkg/tmp.ci': Read-only file system
dpkg: error while cleaning up:
unable to securely remove '/var/lib/dpkg/reassemble.deb': Read-only file system
Processing triggers for xbian-package-initramfs-tools ...
dpkg: unrecoverable fatal error, aborting:
unable to flush updated status of `xbian-package-initramfs-tools': Read-only file system
I have deleted both the /etc/sysctrl.d/xbian.conf and /etc/sysctrl.conf file.
copied the xbian.conf file from the package to /etc/sysctrl.d/xbian.conf and /etc/sysctrl.conf file.
Rebooted
But the installation takes forever.... mmcqd thread takes 50% of CPU.
Result is the same as above. "Read only file system"
Do you have some more suggestions or should I start from a fresh Beta2 (or other)
[edit]
I have checked my config.txt file and noticed that content was the same as cmdline.txt!!!
Who (me) or "what" did this?!? I don't know.
KB
can you post dmesg to pastebin?
also remouting to read-only mode means we have different problem. filesystem corruption - which can be caused by many factors.
let's look at the dmesg output.
(2nd Dec, 2013 01:55 AM)mk01 Wrote: [ -> ]can you post dmesg to pastebin?
also remouting to read-only mode means we have different problem. filesystem corruption - which can be caused by many factors.
let's look at the dmesg output.
I think I found the problem. My config.txt file was corrupt.
I removed all content and rebooted.
I installed the xbian-update deb and now I could see actually the update process.
Due to (extra)available memory? Because gpu_mem_256=128 was missing?
I ran the config utility to set the proper (overclock)values in the config.txt.
I manually added the gpu_mem_256=128 to it.
Rebooted
stop xbmc
Apt-get update apt-get upgrade was successfully.
All went well
I could find this in the dmeg
Terminal
[ 2.194638] Indeed it is in host mode hprt0 = 00021501
[ 2.280878] Btrfs detected SSD devices, enabling SSD mode
[ 2.282615] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
[ 2.296376] VFS: Mounted root (btrfs filesystem) on device 0:12.
KB
(1st Dec, 2013 09:25 PM)CurlyMo Wrote: [ -> ]/home/xbian/.xbmc:
totaal 0
drwxrwxr-x 1 root root 0 aug 18 19:37 userdata
/home/xbian/.xbmc/userdata:
totaal 0
if you still have the filesystem can you mount the btrfs root with
Code:
mount -o subvol=/ /dev/root /mnt
and check with mc the …home/@ probably others ? or even root/@/home which should be empty just used as mount point . maybe you find them there ?
when you see /home/xbian so empty, is it actually mountpoint and active ? "mountpoint /home" will tell.
yesterday I found that mountall from wheezy 7.2 is working a bit different than before. in my case 1 from 10-20 cases happened (and only if booted directly to rootfs without initramfs) /proc wasn't mounted soon enough to provide cmdline infos causing /home and /lib/modules not being mounted. very very strange.
this would correspond with your xbmc not being started and the right package reinstall could recreate missing xbian xbmc and userdata dir.
so that's why I'm just asking if the /home you are looking at is really mounted home/@.
it was corrected in xbian-update yesterday - version -11d and /etc/xbian_revision should read 000063 .
(19th Nov, 2013 06:45 AM)peibol16 Wrote: [ -> ]Hi,
I get the following error when I try to execute xbian-config:
/usr/local/sbin/xbian-config: l?nea 200: /run/lock/xbian-config.gui: No existe el fichero o el directorio
I have a clean installation of beta2 and I read in previous pages that the issue is solved but I have not clear how to fix.
I run into this one as well. Hopefully also fixed.
Just a short question:
I am using your 1.0 Beta 2 like described in the
first post here for a while now and I just wanted
to know, if we have to change something back
(meaning the deb mirror for example), when this
leaves beta status or when there is a newer
version.
Also, I was always doing update with
"apt-get clean; apt-get update; apt-get upgrade"
Was that wrong, because I just read something
about doing updates per XBIAN-Config? Where
do I find/start that? Not per Putty/SSH, I guess.
Thank you, guys
@
syco - If something is working - don't touch it :-)
Beta2 has been designed to be as user friendly as possible. Which is why updates can be handled via ssh xbian config and via XBMC.
(From a ssh shell just type xbian-config)
However, manual apt-get's are just as good - it ust gives more information. There is no difference.
After a fresh beta2 install and an apt-get-update; apt-get upgrade I am stuck with the splash screen: Configuring network.....
Any suggestions what to do?
I checked the /etc/network/interfaces file and looks good to me.
Code:
auto eth0
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
wireless-power off
iface default inet dhcp
[edit]
I removed spash from the cmdline.txt file and the screen shows:
Terminal
..
Moving root
Switching root
mountall
started hwclock
xbian-nowait
started wait-for-state xbian-done
KB
(7th Dec, 2013 09:45 PM)Killerbee Wrote: [ -> ]After a fresh beta2 install and an apt-get-update; apt-get upgrade I am stuck with the splash screen: Configuring network.....
Any suggestions what to do?
I checked the /etc/network/interfaces file and looks good to me.
can you please also provide /etc/fstab ?
(7th Dec, 2013 02:48 AM)syco Wrote: [ -> ]Just a short question:
I am using your 1.0 Beta 2 like described in the
first post here for a while now and I just wanted
to know, if we have to change something back
(meaning the deb mirror for example), when this
leaves beta status or when there is a newer
version.
@
syco
for upgrading you got correct answer already
as for the right sources.list file it depends when you started with beta2. it started on old devel repo which was later changed by update package to stable automatically so should be fine.
still you can check your /etc/apt/sources.list . correct record for XBian should read
Code:
deb http://xbian.brantje.com wheezy main
OR
deb http://xbian.brantje.com stable main
both are correct
How can i install XBMC Gotham?
I tried it with sudo apt-get install xbian-package-xbmc-gotham-nightly
but i got the following message:
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-gotham-nightly : Depends: xbian-package-shairplay but it is not installable
E: Unable to correct problems, you have held broken packages.
Even if i tried to install underr XBMC Packages under Video i got the info that the file is corrupted
Any help would be apreciated.
Yami
(21st Dec, 2013 02:56 AM)yami Wrote: [ -> ]How can i install XBMC Gotham?
I tried it with sudo apt-get install xbian-package-xbmc-gotham-nightly
but i got the following message:
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-gotham-nightly : Depends: xbian-package-shairplay but it is not installable
E: Unable to correct problems, you have held broken packages.
Even if i tried to install underr XBMC Packages under Video i got the info that the file is corrupted
Any help would be apreciated.
Yami
Perhaps you must be on the devel branch, I always am and had your issue until I added the staging branch as well.
See here:
http://forum.xbian.org/showthread.php?pid=18772#pid18772
Hi guys,
For an unkown reason, my updates have stopped working with this error message:
Code:
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_i18n_Translation-en
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_i18n_Translation-en
E: The package lists or status file could not be parsed or opened.
Actually, I have not changed anything about it, so I do not know what is wrong here.
Maybe someone can help me out?
Cheers, mates.
It's a Raspbian issue, not XBian. Wait for them to fix it.
Thank you.
Btw, can someone show/copy me the content of his/her /etc/apt/sources.list file?
I believe, mine got corrupt.