• Content Count

  • Joined

  • Last visited

  • Days Won


seba last won the day on November 11 2018

seba had the most liked content!

Community Reputation

7 Neutral

About seba

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I've made new release, VirtualBox is updated to 5.2.20. I've created packages for few more architectures, you can find them now in release page on github, I've tested only bromolow package. Also note that currently there is a bug with upgrade procedure so you will have to uninstall old version and then install new one. Regards, Seba
  2. If vbox doesn't work work you please give me output of 'uname -a', so I know what kind of arch you have. Also content of scripts.log file and dmesg messages. By the looks of it there should be a build custom for each arch, which I was hoping to avoid, as it takes time to prepare which I don't have. Just to add I made some changes to x64 package and re-upload it to github.
  3. There is a log file in /volume1/virtualbox/scripts.log you can check what went wrong there. You can ignore messages like /lib/ no version information available I've uploaded package for x86_64 on github but only for 3.10.105 kernel, it is untested.
  4. Hi, I created spk packages for virtualbox 5.2 on DSM 6.2 (currently for bromolow), more info here, since I've split phpvirtualbox and virtualbox you will need also this. Give it a spin if you are brave enough. Standard disclaimer apples.
  5. seba

    Tvheadend installation issues had a bug when wrong user was used to start service, don't remember right now but in start-stop-script wrong user was referenced, non existing/created user. Other then that it works ok. I've been using it for few years now.
  6. seba

    DVB-T2 Dongle

    Yes, it will be interesting to see what is their plan with that. Especially with this note in 6.2 beta Known Issues & Limitations ..... Starting from DSM 6.2, the USB device drivers, including printers, cloud printers, DAC/speakers, Wi-Fi dongles, DTV dongles, LTE dongles, and Bluetooth dongles, will no longer be updated. .....
  7. seba

    DVB-T2 Dongle

    I did have to. Was building it from media_tree since drivers where mainlined since 3.19. I created script that packaged everything in spk.
  8. seba

    DVB-T2 Dongle

    I've successfully used Geniatech T230 (aka MyGica T230) in tvheadend it supports T. T2 and C.
  9. Package had error in start script. I reuploaded!htNwgZLK!oKFESUWZQ9af ... p5Ws25Gxac, 5.1 version doesn't contain w_scan. You will have to restart server.
  10. If you are on xpenology 5.2 you can try this!tkVSGb5L!-8mwXbakXnlK ... U0xLyxJrJo but YMMV. I had the tuner working fine in 5.1 but in 5.2 I can't even scan channels properly, I get a lot of PAT timeout errors. Something changed between kernels that is giving me trouble, If I could I would downgrade to DSM 5.1 just for this. I don't need to say that I'm pretty interested in 6.0 in hope it would remedy issue with media driver. Btw. if you are on 5.1 try this!htNwgZLK!oKFESUWZQ9af ... p5Ws25Gxac, this one has dvbv5tools included to switch tuner to DVB-C mode so you might need to change (comment out) few lines in script to disable it. For 5.2 I've made separate package for dvb5tools!Es9DhJIC!qG8LWkcwL0xi ... CqJKrGo7XY and added w_scan too.
  11. Yes you need two hw adapters.
  12. You can select which interface VM will be bridged to in VM configuration "settings->network adapter" there is dropdown where you select on which interface bridge will be created. I didn't test this since I have only one NIC working. And yes you can have several VM's bridged to one NIC.
  13. @rthga81 check file permissions it should be root:root 755 @dodo-dk tar xf virtualbox-x64-4.3.12.spk mkdir package tar xf package.tgz -C package cd package tar zcf ../package.tgz * cd .. tar cf ../vbox.spk *
  14. Kernel modules are copied during installation from package to /lib/moduels/3.2.40/. That is done by script from scripts folder during install.
  15. Hi, To help troubleshoot problems here are few tips: Virtualbox should create log file at following location /var/log/vbox.log. From ssh try this do start drivers /var/packages/virtualbox/target/scripts/ start of this goes without error then /var/packages/virtualbox/target/scripts/ start and finally if vboxinit was without errors /var/packages/virtualbox/target/scripts/ start I've added this to first post as well for reference. Since I won't get my mb anytime soon from repair, you are welcome to try and fix package. Basically you need to setup crosscompile environment for info use Synology guide at their website. Source for vbox driver you can find in "All distributions" package at virtualbox download page (use AMD64).