• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by seba

  1. Sorry I don't have one anymore. My cable provider switched to encrypted channels two years ago which made T230 is useless.
  2. Did you try that in some linux distro on same hardware? Quick googling led me to this 1. Please reboot the system and then press [Delete] to enter the BIOS setup. 2. BIOS > Advanced > CPU Configuration > SVM Mode -> set enabled 3. BIOS > Advanced > North Bridge Configuration > IOMMU -> set enabled. If it is working on same hardware under linux distro it should work here to.
  3. What is possible in GUI depends on good folks maintaining phpVirtualBox but you can always use shell and VBoxManage. For nested options as doc states here you would run following as root /opt/VirtualBox/VBoxManage modifyvm "My VM Name" --nested-hw-virt on
  4. There was a package that was downloading few files from internet, but they are not created by me. If you refer about not being able to select anything outside volume1 in file browser then yes. You need to edit file config.php in webstations folder there look for line var $browserRestrictFolders = array('/volume1'); you can modify it to suite your needs. Also Virtualbox 6.0.8 is out you can find it on github where I'm posting new versions.
  5. In web stations shared folder you will find phpvirtualbox4dsm and in there config.php. Keep in mind that if you disable auth then anybody who has access to your server can use virtualbox, even if he doesn't have syno account on your box.
  6. When I find time. I plan to fix issues and build version Virtualbox 6.0. Btw what model do you have for arch x86_64?
  7. PhpVirtualBox is not integrated into DSM. Default user and pass is admin/admin. Also you can disable auth by uncommenting line in config.php
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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. .....
  14. 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.
  15. I've successfully used Geniatech T230 (aka MyGica T230) in tvheadend it supports T. T2 and C.
  16. 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.
  17. 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
  18. 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.
  19. @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 *
  20. Kernel modules are copied during installation from package to /lib/moduels/3.2.40/. That is done by script from scripts folder during install.
  21. 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
  22. @Adrirand You have corrupted configuration file. You need to delete /root/.config/VirtualBox/VirtualBox.xml so new one will get recreated. After that you will have to import VMs.
  23. I will support 5.1 once I repair my xpenology box. Mb is gone for rma and when I get it back, 5.1 will be more stable for me to work with it. Sent from my Nexus 7 using Tapatalk HD
  24. Real synology boxes are not supported because I don't have one so i can't test vbox properly, that is the reason I didn't upload spk to any public repo. Also since there is no xpenology 5.1 I cant support vbox on 5.1. That being said error message you have seam to be happening because of vbox crashing. Clue to reason why you could find in vbox log at /var/log/vbox.log (i think that is the location). Sent from my Nexus 7 using Tapatalk HD