Il 25/11/2015 23:07, Catalin Soare ha scritto:
On Nov 25, 2015 11:54 PM, "Mauro Condarelli" <[email protected] <mailto:[email protected]>> wrote: > > > Il 25/11/2015 22:23, Catalin Soare ha scritto: >> >> Hello there, >> >> Maybe it is as you said earlier, an option in the kernel. Namely, the no multicard support you mentioned earlier, is it possible that was comming from the kernel itself or was it noveau? >> > Thanks Catalin. > > Context of said error is: > ... > [ 7.708] (II) Loading sub module "fbdevhw" > [ 7.708] (II) LoadModule: "fbdevhw" > [ 7.708] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 7.709] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 7.709] compiled for 1.17.2, module version = 0.0.2 > [ 7.709] ABI class: X.Org Video Driver, version 19.0 > [ 7.709] (WW) Falling back to old probe method for vesa > [ 7.709] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support > [ 7.709] (II) Loading sub module "dri2" > [ 7.709] (II) LoadModule: "dri2" > [ 7.709] (II) Module "dri2" already built-in > [ 7.709] (--) NOUVEAU(0): Chipset: "NVIDIA NVE4" > [ 7.709] (II) NOUVEAU(0): Creating default Display subsection in Screen section > "Default Screen Section" for depth/fbbpp 24/32 > [ 7.709] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32 > [ 7.709] (==) NOUVEAU(0): RGB weight 888 > ... > > I do not know where it comes from (if You want I can post or pastebin the whole log again). > I tried googling, but never found an explanation, only cited in threads "solved" by other means. > VGAarbiter is a kernel module but AFAIK it deals with "legacy VGA devices" which do not "allow relocation of such (I/O or memory space) ranges"; it is unclear to me if this applies to my case. > > I am willing to experiment, but I need help because I have no experience with video drivers. > > Regards > Mauro No need to upload again, I admit I didn't bother to check since apparently others have already and I don't have experience with Linux drivers. Personally, what I would do in this case is save the dmesg for debian somewhere; go back to Mint and check dmesg over there too. Also check if Mint has blacklisted any modules, such as, for example fbdevhw? Either way, there should be something that you will find by matching the 2 OSs.
Thanks. willdo. Mauro
