+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Testing & Experimental (/forum-21.html)
+--- Thread: beta2 (/thread-1312.html)
RE: beta2 - Killerbee - 20th Nov, 2013 11:53 PM
(20th Nov, 2013 11:41 PM)CurlyMo Wrote: Beta 1 image a long while ago
Code:
aptitude search xbian -F "%c %p %d %v"
Any chance you could prep an image for us?
I am still facing "segmentation faults" dpkg--configure -a, file system readonly errors...... when using apt-get upgrade or apt-get install <package name>.
I tried Beta1.1 => Beta2; New Beta2 image all the same.
With different kind of SD cards and different kind of PI (I have three).
I blame BTRFS. But I am not able to prove it
BUT I have to be honest. When not using apt-get update or apt-get install the system is running fine and fast!
But I'd like to install tvheadend.......
KB
RE: beta2 - CurlyMo - 20th Nov, 2013 11:55 PM
No, because i've got various custom tweaks throughout XBian.
RE: beta2 - Darkguy - 21st Nov, 2013 03:12 PM
Just upgraded to all the latest packages and things look good, XBMC started fine after a reboot.
Only thing I noticed was that all my CIFS-mounts were deleted from /etc/fstab for some reason. A (disabled) mount-point to an external HDD is still in there.
RE: beta2 - CurlyMo - 22nd Nov, 2013 03:54 AM
All packages in the devel repo are working for fine (for what i've tested).
RE: beta2 - f1vefour - 23rd Nov, 2013 09:58 AM
@mk01
I'm getting this and while it happens XBMC CPU usage spikes, it is certainly a kernel compatibility issue with lirc_rpi and the Ethernet driver.
http://pastebin.com/GwdzyLU5
*edit*
So far disabling turbo on Ethernet and changing vfs_cache_pressure to 300 has resolved the issue, doesn't really seem to affect LAN speeds either.
RE: beta2 - CurlyMo - 27th Nov, 2013 07:14 PM
Due to one of the threads here i noticed my SD card wasn't resized to full either:
Code:
Disk /dev/mmcblk0: 4012 MB, 4012900352 bytes
4 heads, 16 sectors/track, 122464 cylinders, total 7837696 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f06a6
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2048 71679 34816 c W95 FAT32 (LBA)
/dev/mmcblk0p2 71680 7335935 3632128 83 Linux
/dev/mmcblk0p3 7335936 7837695 250880 82 Linux swap / Solaris
root@pi:~# btrfs fi df /
Data, single: total=2.83GiB, used=1.90GiB
System, DUP: total=8.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, DUP: total=312.12MiB, used=115.08MiB
Metadata, single: total=8.00MiB, used=0.00RE: beta2 - mk01 - 1st Dec, 2013 10:55 AM
@CurlyMo
but this looks like the partitions are resized correctly.
and "btrfs fi df /" output is not saying about btrfs fs total size. the totals there are just saying 2.83GiB totally allocated (until now), currently 1.90GiB used.
if you want to check whether btrfs filesystem was resized to max, use "btrfs fi show". look here:
Code:
root@xbian05:~# fdisk -l
Disk /dev/mmcblk0: 7861 MB, 7861174272 bytes
4 heads, 16 sectors/track, 239904 cylinders, total 15353856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009be7b
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 71679 34816 b W95 FAT32
/dev/mmcblk0p2 71680 14852095 7390208 83 Linux
/dev/mmcblk0p3 14852096 15353855 250880 82 Linux swap / Solaris
root@xbian05:~# btrfs fi show
Label: 'xbian-beta2' uuid: 67901a92-640f-4087-96b2-7719a8367476
Total devices 1 FS bytes used 1.04GB
devid 1 size 7.05GB used 3.64GB path /dev/mmcblk0p2
Btrfs v0.20-rc1-358-g194aa4a
root@xbian05:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.1G 1.1G 5.7G 16% /
root@xbian05:~# btrfs fi res max /
Resize '/' of 'max'
root@xbian05:~# btrfs fi show
Label: 'xbian-beta2' uuid: 67901a92-640f-4087-96b2-7719a8367476
Total devices 1 FS bytes used 1.04GB
devid 1 size 7.05GB used 3.64GB path /dev/mmcblk0p2
Btrfs v0.20-rc1-358-g194aa4a
root@xbian05:~# btrfs fi df /
Data: total=3.26GB, used=1016.54MB
System: total=4.00MB, used=16.00KB
Metadata: total=392.00MB, used=49.17MB(22nd Nov, 2013 03:54 AM)CurlyMo Wrote: All packages in the devel repo are working for fine (for what i've tested).
even the XBMC ?
for both version there (-14 and -15) I have problem with seeking. simply doesn't work.
(20th Nov, 2013 11:53 PM)Killerbee Wrote: Any chance you could prep an image for us?
I am still facing "segmentation faults" dpkg--configure -a, file system readonly errors...... when using apt-get upgrade or apt-get install <package name>.
can you please follow this post ?
https://github.com/xbianonpi/xbian/issues/482
RE: beta2 - Killerbee - 1st Dec, 2013 08:17 PM
(1st Dec, 2013 10:55 AM)mk01 Wrote:(20th Nov, 2013 11:53 PM)Killerbee Wrote: Any chance you could prep an image for us?
I am still facing "segmentation faults" dpkg--configure -a, file system readonly errors...... when using apt-get upgrade or apt-get install <package name>.
can you please follow this post ?
https://github.com/xbianonpi/xbian/issues/482
@mk01
Sure I will test it today and comeback to you.
You changed/updated the xbian.conf file. But could you please also check the settings in the /etc/default/zram-sawp.conf file? SIZE=128. is this correct for a 256Mb pi with 128Mb GPU mem set in config.txt?
KB
RE: beta2 - CurlyMo - 1st Dec, 2013 08:26 PM
@mk01, resize, will check the again. package, didn't test this precisely.
RE: beta2 - mk01 - 1st Dec, 2013 08:51 PM
(1st Dec, 2013 08:17 PM)Killerbee Wrote: @mk01
Sure I will test it today and comeback to you.
You changed/updated the xbian.conf file. But could you please also check the settings in the /etc/default/zram-sawp.conf file? SIZE=128. is this correct for a 256Mb pi with 128Mb GPU mem set in config.txt?
yes. zram-swap in /etc/default is defining the roof (max amount). but the service never allocates more than 1/4 of system memory (total-gpu).
for 256mb model with 1/1 allocation this means ~ 30mb. you can also anytime set it to 0 in the config file.
mk
RE: beta2 - Killerbee - 1st Dec, 2013 08:53 PM
@mk01
What I did sofar:
opened two ssh sessions:
one with with root running htop
second one with root shell.
In the second shell I ran this:
Terminal
stop xbmc
wget download http://xbian.brantje.com/pool/devel/main/x/xbian-update/xbian-update_1.0.2-11_armhf.deb
install it using dpkg -i xbian-update_1.0.2-11_armhf.deb
wget download http://xbian.brantje.com/pool/devel/main/x/xbian-update/xbian-update_1.0.2-11_armhf.deb
install it using dpkg -i xbian-update_1.0.2-11_armhf.deb
CPU in htop goes max BUT I am not able to see what process! It's not the dpkg update process. So I assume it's the kernel/zram (I am not an expert here).
htop keeps running but as soon as I stop htop terminal (first ssh shell) is not responding. So I am unable to run dmesg.
So installation failed.
Second test.
Same as above but before updating i manually copied the content of the new xbian.conf from the new xbian-update_1.0.2-11 package to /etc/sysctrl.conf and /etc/default/xbian.conf files.
Reboot and ran the update procedure.
Result was the same. So update failed (stalled)
Do you have some sugestions?
edit:
after a while I get this in the terminal
Terminal
dpkg: error while cleaning up:
unable to remove newly-installed version of `/var/tmp/xbian_update/files_to_overwrite/etc/init/cron.conf': Read-only file system
dpkg: error while cleaning up:
unable to remove newly-installed version of `/var/tmp/xbian_update/files_to_overwrite/etc/init/networking.conf': Read-only file system
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 remove newly-installed version of `/var/tmp/xbian_update/files_to_overwrite/etc/init/cron.conf': Read-only file system
dpkg: error while cleaning up:
unable to remove newly-installed version of `/var/tmp/xbian_update/files_to_overwrite/etc/init/networking.conf': Read-only file system
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:
RE: beta2 - mk01 - 1st Dec, 2013 09:01 PM
(23rd Nov, 2013 09:58 AM)f1vefour Wrote: @mk01
I'm getting this and while it happens XBMC CPU usage spikes, it is certainly a kernel compatibility issue with lirc_rpi and the Ethernet driver.
http://pastebin.com/GwdzyLU5
*edit*
So far disabling turbo on Ethernet and changing vfs_cache_pressure to 300 has resolved the issue, doesn't really seem to affect LAN speeds either.
@f1vefour
retest with xbian-update 1.0.2-11c. but actually it is only netturbo=N and cache pressure default kept. but shorter interval between dirty write backs - should have similar effect as cache pressure.
@CurlyMo
where is the original xbian_lirc_kernel patch from?
(1st Dec, 2013 08:53 PM)Killerbee Wrote: CPU in htop goes max BUT I am not able to see what process! It's not the dpkg update process. So I assume it's the kernel/zram (I am not an expert here).
htop keeps running but as soon as I stop htop terminal (first ssh shell) is not responding. So I am unable to run dmesg.
So installation failed.
Second test.
Same as above but before updating i manually copied the content of the new xbian.conf from the new xbian-update_1.0.2-11 package to /etc/sysctrl.conf and /etc/default/xbian.conf files.
Reboot and ran the update procedure.
Result was the same. So update failed (stalled)
@Killerbee
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).
RE: beta2 - CurlyMo - 1st Dec, 2013 09:25 PM
@mk01, link?
After installing the latest staging debs of 1 dec. xbmc doesn't start anymore.
Probably because my /home pool is broken.
Code:
root@pi:/# btrfs-auto-snapshot list
WARNING: Less than 30% of free space. Keeping only one single snapshot...
data/@
home/@btrfs-auto-snap_daily-2013-11-18-0756_rollback
home/@btrfs-auto-snap_daily-2013-12-01-0757
home/@btrfs-auto-snap_weekly-2013-11-14-0830_rollback
home/@btrfs-auto-snap_weekly-2013-11-28-0830
home/@tmp.LuuF5ESptf
modules/@
modules/@btrfs-auto-snap_daily-2013-11-18-0756_rollback
modules/@btrfs-auto-snap_daily-2013-12-01-0757_rollback
modules/@btrfs-auto-snap_weekly-2013-11-14-0830_rollback
modules/@btrfs-auto-snap_weekly-2013-11-28-0830
root/@
root/@btrfs-auto-snap_apt-run-2013-11-17-2259_rollback
root/@btrfs-auto-snap_apt-run-2013-12-01-1136_rollback
root/@btrfs-auto-snap_daily-2013-11-18-0756_rollback
root/@btrfs-auto-snap_daily-2013-12-01-0757_rollback
root/@btrfs-auto-snap_weekly-2013-11-14-0830_rollback
root/@btrfs-auto-snap_weekly-2013-11-28-0830
root@pi:/# btrfs-auto-snapshot rollback home/@btrfs-auto-snap_weekly-2013-12-01-0757
WARNING: Less than 30% of free space. Keeping only one single snapshot...
Error: Source name does not exists!
root@pi:/#Code:
root@pi:/# ls -AlR /home/xbian/.xbmc/
/home/xbian/.xbmc/:
totaal 0
drwxrwxr-x 1 root root 0 aug 18 19:37 userdata
/home/xbian/.xbmc/userdata:
totaal 0
root@pi:/# ls -AlR /home/xbian/
/home/xbian/:
totaal 0
drwxr-xr-x 1 root root 0 dec 1 12:22 run_on_reboot
drwxrwxr-x 1 root root 16 dec 1 12:22 .xbmc
/home/xbian/run_on_reboot:
totaal 0
/home/xbian/.xbmc:
totaal 0
drwxrwxr-x 1 root root 0 aug 18 19:37 userdata
/home/xbian/.xbmc/userdata:
totaal 0
root@pi:/# ls -AlR /home/
/home/:
totaal 0
drwxrwxr-x 1 root root 36 dec 1 12:22 xbian
/home/xbian:
totaal 0
drwxr-xr-x 1 root root 0 dec 1 12:22 run_on_reboot
drwxrwxr-x 1 root root 16 dec 1 12:22 .xbmc
/home/xbian/run_on_reboot:
totaal 0
/home/xbian/.xbmc:
totaal 0
drwxrwxr-x 1 root root 0 aug 18 19:37 userdata
/home/xbian/.xbmc/userdata:
totaal 0RE: beta2 - mk01 - 1st Dec, 2013 09:36 PM
doesn't start like you even don't see splash with "starting xbmc…" or it starts loading, but never loads?
can you post:
1)
dmesg | grep init:
/run/upstart-ev.log
it is possible to also check this
2) /var/log/upstart/xbmc.log,xbmc-preload.log
RE: beta2 - CurlyMo - 1st Dec, 2013 09:52 PM
I see the splash but nothing happens afterwards.
Can't boot that install anymore after i tried to fix it myself.