On 28.07.2012 01:26, Jan Beerden wrote:
>> Ah, the full package name is kernel-devel-3.2.7-9.pvops.qubes.x86_64. You
>> specify it also as "kernel-devel-3.2.7-9*".
> That did the trick, unfortunately I can't insmod my module due to "Unknown
> symbol in module"
> I also tried the 3.4.4 kernel without any luck.
You can load required modules manually (try modprobe symbol:SYMBOL_NAME). Or
make /lib/modules writable (which also means that kernel for this VM will not
be affected by upgrades). I've described the procedure here:
But read below, perhaps you will no need to compile modules at all.
>> BTW There is also 3.4.4 kernel in our development repo (kernel for VM is
>> installed in dom0 as kernel-qubes-vm package). If you want, you can test
>> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
>> Some history and issues connected with this version can be found here:
. Perhaps your 3G modem will work
>> of the box there. You can choose kernel version on per-VM basis and
>> system-wide default via qubes-manager or qvm-prefs/qubes-prefs tools.
>> The actual problem is that I need to enable my 3G modem using toshset and
> Toshiba ACPI.
Hmm... VM have no access to host ACPI. Perhaps you need to use toshiba_acpi
module (which already is in our kernel) in dom0? Also toshset is used only to
turn 3G modem on - if need access to toshiba_acpi - also can be used only from
I guess that your modem appear as USB device, so you must attach it to netvm
with full USB controller
). There was somewhere
more detailed instruction (especially how track which USB controller handle
which device), but don't remember where...
> Also on my Fedora 16 and 17 installation with the most recent kernel, this
> module was actually working.