Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.

Nachrichten - jpkrohling

Seiten: [1]
Sundtek MediaTV Pro / Re:Fedora with external USB disk vs. mediaclient with systemdcheck
« am: September 26, 2013, 08:27:23 Nachmittag »
With the change I mentioned (from /usr/sbin/systemctl to /usr/bin/systemctl) made it work, so, it's all fine now. I can safely reboot the machine and everything works. Thanks for your support!

Sundtek MediaTV Pro / Re:Fedora with external USB disk vs. mediaclient with systemdcheck
« am: September 25, 2013, 08:21:53 Nachmittag »
Unfortunately, it didn't seem to work. I removed the udevd files, installed the driver again based on the latest version (24. September 2013) and the exact same behavior remains. Even the udev files look the same. So, perhaps something on the Fedora check didn't work. By looking at the diff, I see this:

< _SIZE=49455
> _SIZE=49305
<            sed '1,1370d' ${app} > /tmp/.sundtek/installer.tar.gz
>            sed '1,1366d' ${app} > /tmp/.sundtek/installer.tar.gz
<           if [ -e /usr/sbin/systemctl ]; then
<               rm -rf /etc/udev/rules.d/80-mediasrv-eeti.rules
<               rm -rf /lib/udev/rules.d/80-mediasrv-eeti.rules
<           fi

It seems strange to me, because on Fedora 19 this doesn't exists. It does exist, however, on "bin" (not "sbin"):

$ which systemctl
$ uname -a
Linux acai 3.11.1-200.fc19.x86_64 #1 SMP Sat Sep 14 15:04:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
Fedora release 19 (Schrödinger’s Cat)

Removing the "s" (and changing the SIZE parameter) seems to make it work.

Sundtek MediaTV Pro / Fedora with external USB disk vs. mediaclient with systemdcheck
« am: September 23, 2013, 09:17:34 Vormittag »

I think I might have hit a case that wasn't perhaps expected by the driver. I have a Fedora 19 installed on a machine, and my data files are mounted at boot on /var/media. This is an external USB 3.0 disk. After installing the Sundtek driver, I'm unable to boot. After a timeout during boot, I'm in emergency mode, where I can choose to proceed (Ctrl+D) or enter in the maintenance mode. Neither means that the mount points will be available upon booting. But I'm able to mount them once boot is completed.

After some hours debugging (and of reinstalling fedora, piece by piece), I've found out that if I remove the "--systemdcheck" from /etc/udev/rules.d/80-mediasrv-eeti.rules , I'm able to boot just fine, but the Sundtek driver won't start. And it seems that starting the mediaclient doesn't just work. As I didn't have time to debug this particular problem, I've decided to just reinstall the driver, and it worked.

So, currently, I have two choices:
a) Leave the system in the state that the installer left, but as a price to pay, the boot will be extremelly long and the devices won't be mounted (but hey, mediaclient will be working)
b) Remote "systemdcheck" from the rules directory, and reinstall the driver after each reboot.

Is this a known bug? Is there a workaround for this? For debugging purposes, what concrete things can I do to help you? Send the boot.log? dmesg?

Software / Re:LIRC - Remote control
« am: August 22, 2013, 08:31:31 Nachmittag »

I think I have the new remote control (the order is from May 2012, and the remote control looks *different* than this one: ) , and I couldn't get it to work with Ubuntu. When using the configuration /opt/doc/sundtek.conf , I see some output on irw, but those are not a match for the keys (ie: when I press "back", it reports as "volume up", and so on). When using the configuration  /opt/doc/sundtek_vcr_remote.conf , I get no output at all. I'm not sure what to try, and I guess that trial/error with the hex codes wouldn't be good for my sanity :-)

Seiten: [1]