|
From: Rok M. <rok...@gm...> - 2019-01-09 23:58:00
|
No, both the daemon and the clients (gcdemu or cdemu-client) should be run as regular user, not as root. Because by default, both are trying to connect via per-session D-Bus, which will probably be missing for root. On 9. 01. 19 21:47, lie...@gr... wrote: > I will do so. > FYI > 0# modinfo vhba > filename: /lib/modules/4.9.0-6-amd64/extra/vhba.ko > license: GPL > description: Virtual SCSI HBA > version: 20170610 > author: Chia-I Wu > srcversion: 33907B3A0F9660F04111AD7 > depends: scsi_mod > retpoline: Y > vermagic: 4.9.0-6-amd64 SMP mod_unload modversions > > So it now loaded when I did modprobe > > > I already posted the error message for running it as root user (as it > should as it is a device program) > Running it through sudo, from user account I get > > ~$ sudo gcdemu > [sudo] password for bozo: > AppIndicator tray icon mode > > after which nothing happens. > > > > > On 2019-01-09 14:48, Rok Mandeljc wrote: >> On debian, I would advise you to use the provided build scripts >> (debian subfolder in each component's folder) to build .deb packages >> and install those: >> >> git clone git://git.code.sf.net/p/cdemu/code cdemu-code >> cd cdemu-code >> >> # VHBA >> cd vhba >> apt-get build-dep . # Run as root; should install all build dependencies >> dpkg-buildpackage -b -tc -uc # Builds the package >> cd .. >> apt install ./vhba-dkms_20170610-1_all.deb # Run as root to install >> the package >> >> modinfo vhba # Check if module was automatically built for the >> current kernel >> >> # libmirage >> cd libmirage >> apt-get build-dep . # Run as root; should install all build dependencies >> dpkg-buildpackage -b -tc -uc # Builds the package >> cd .. >> apt install ./libmirage11_3.2.0-1_amd64.deb >> ./libmirage11-dev_3.2.0-1_amd64.deb >> ./gir1.2-mirage-3.2_3.2.0-1_amd64.deb # Install libMirage before >> trying to build cdemu-daemon package >> >> # Same steps for cdemu-daemon, cdemu-client, gcdemu: same >> >> The .deb packages provide additional configuration for setting >> permissions and module auto-load, which you will be missing if you do >> a manual build from source. And incorrectly set permssions on VHBA >> control device will be one of the reasons for cdemu-daemon to refuse >> to start. >> >> Best regards, >> Rok > > > _______________________________________________ > Cdemu-devel mailing list > Cde...@li... > https://lists.sourceforge.net/lists/listinfo/cdemu-devel |