(29th Sep, 2013 02:05 PM)darrylb Wrote: [ -> ]Hmm, I have yet another failed install. At this point, I am tempted to give up on a beta 2 upgrade at this time, until its fully built for download. The biggest reason I was wanting to try this one, is RaLink 5370 wireless dongle to work, as I have had a heck of a time getting it to work with previous versions...
@
darrylb, before you give up, can you just tell me whether is it this one?
http://forum.xbian.org/thread-1346-post-15719.html#pid15719
as I after a week realized the issue, I turned the apt and web completely down, that's why it was non-accessible. after some changes turned on again ~ 1h ago. you got the fresh packages (specially xbian-update in the version 1.0.2-0) and got crash again?
if yes, can you please tell me how you restored and reapplied / reinstalled? Finally I found a typo in calling one of the triggers which caused xbian-update to call itself instead of initramfs update and this still before the same script (own) finished - what created endless loop - with a freeze / reboot in few seconds.
if that's it, then just new boot and update will not help - it will crash again / need to crash again until solved - as the broken script from xbian-update has been stored into system and will be called again - until not overwritten by the corrected one (which takes its place).
so as general info even if you don't give it a try anymore - what I fully accept - but for others:
Code:
1) when the system collapses - unplug AC - remove SD card
2) on another PC go into /boot and:
a) if possible, check if /boot/initramfs.gz is intact (gunzip -tv initramfs.gz). if on windows and check is not possible, remove "initramfs initramfs.gz 0x00a00000" line from config.txt
b) check for non empty / existent cmdline.txt. if not present, look for cmdline.new or .default. if you don't have usbinstall, just rename the file to cmdline.txt
3) system should boot
4) do "apt-get clean; apt-get update; apt-get install —reinstall xbian-package-initramfs-tools xbian-update" (dpkg —configure -a will be maybe needed before - apt-get will complain if so)
5) ugly part is, that it will happen again - the wrong/bad scripts is still in the system and marked as active and still accepting trigger requests
6) again step 2)
7) new correct script should already replaced the wrong, but still we need ...
8) to do "dpkg —configure -a"
10) just for test we can do again "apt-get clean; apt-get update; apt-get install —reinstall xbian-package-initramfs-tools xbian-update"
for experienced:
Code:
1) recover as point (2) above
2) just extract "triggers" file and "postinst" from xbian-update 1.0.2-0 and replace the saved versions in /var/lib/dpkg/info
3) anything should run fine
for lazy:
Code:
1) recover as point (2) above
2) if you did not disable regular snapshots (daily/weekly) or before APT-get operation, just:
3) btrfs-auto-snapshot list root
4) find a snapshot dated before Sep-21(or20), I'm not sure and do:
5) btrfs-auto-snapshot rollback [name_of_snapshot] (e.g. root/@btrfs-auto-snap_daily-2013-09-20-0623)
6) reboot and update as usual
(rollback with affect system only, home, xbmc settings / libraries are preserved)
I'm really sorry for troubles to anyone it affected - just hoping this one is the issue. If not I will take the repository down until I find the bug.
mk
(29th Sep, 2013 02:05 PM)darrylb Wrote: [ -> ]The biggest reason I was wanting to try this one, is RaLink 5370 wireless dongle to work, as I have had a heck of a time getting it to work with previous versions...
and the dongle is at least working ? is it new driver to 3.10.y kernel line?
mk
(26th Sep, 2013 01:28 AM)Smultie Wrote: [ -> ]Just installed beta2 and I'm pleasantly surprised.
One thing that doesn't seem to be working anymore though are the "play, pause, stop, forward" buttons on my remote when using CEC.
http://imm.io/1gMPZ
can you please retry with xbian-package-xbmc-scripts v1.0.1-2 with the "tv screen off" set to OFF and report back?
mk
(22nd Sep, 2013 07:32 PM)webjib Wrote: [ -> ]Should /etc/usbmount/mount.d/ contains a script to share usb drive ?
According to this page :http://www.davidc.net/automatically-exporting-usb-drives-over-samba
it is just one command messing nice style inside usbmount because the original scripts is calling helper folders/scripts only in case of ext. disk not found in /etc/fstab.
so if someone if yet from Alpha5 using /etc/fstab for static names, or other reasons, such disks would be excluded from the workflow.
but for this whole structure of if<>then needs to be changed and there are at least 6-7 levels of it. so for now will stay like this and one day with clear eye and bright head will change the structure.
one reason what just crossed my mind is that on boot up, the registry shares table is cleared (on start of smbd). it is more than likely, that the disk is mounted before.
can you (with booted system) try:
Code:
DEVNAME=/dev/XXX usbmount remove
usbmount /dev/XXX
mount point should appear as share. you can check with
I will think about the early mount, later network and late smbd.
(23rd Sep, 2013 05:18 PM)CurlyMo Wrote: [ -> ]Quote:Also, as of now, lirc is not starting itself. "Service lirc start" returns "start: Job failed to start".
Got the same error here. When using the old init script it does work.
so that means that /etc/lirc includes are ok ?
if you update xbian-package-lirc to 1.4-8.3, I turned on debug logging. just do a "start lirc" and post /var/log/upstart/lirc.log
(23rd Sep, 2013 09:44 AM)thenork Wrote: [ -> ]Also, as of now, lirc is not starting itself. "Service lirc start" returns "start: Job failed to start". I can start it manually by running lircd (as root). If I then run service lirc stop, it says "lirc stop/waiting", but it does not actually stop lircd.
thenork,
1) smb
with encrypted password (samba passwords) turned on, those have to be maintained with "smbpasswd" command.
it is possible to update linux system password via smbpassword update (even remote), but I don't know of a solution to do it other direction.
either use "smbpasswd xbian" or just use guest. in actual package version guest should have the same privileges as with 1.x package.
2) lirc
if you update xbian-package-lirc to 1.4-8.3, I turned on debug logging. just do a "start lirc" and post /var/log/upstart/lirc.log
