Re: [Xenomai] Xenomai-3 booting problems (2)

[Leopold Palomo-Avellaneda <leo@alaxarxa.net>]

El Divendres, 23 de gener de 2015, a les 11:18:59, Gilles Chanteperdrix va 
escriure:
> On Fri, Jan 23, 2015 at 10:44:24AM +0100, Leopold Palomo-Avellaneda wrote:
> > El Divendres, 23 de gener de 2015, a les 08:44:03, Gilles Chanteperdrix va
> > 
> > escriure:
> > > On Fri, Jan 23, 2015 at 08:36:14AM +0100, Leopold Palomo-Avellaneda 
wrote:
> > > > El Dijous, 22 de gener de 2015, a les 16:09:19, Leopold
> > > > Palomo-Avellaneda
> > > > va>
> > > > 
> > > > escriure:
> > > > > Hi again,
> > > > > 
> > > > > after made the modifications proposed by Jan Kiszka, now it doesn't
> > > > > built
> > > > > and the message is:
> > > > > 
> > > > > nvidiafb: unable to setup MTRR
> > > > 
> > > > Hi,
> > > > 
> > > > removed nvidiafb.ko module (and all the nvidia graphics stuff) and the
> > > > box
> > > > booted. It seems that nvidiafb (the non-free nvidia driver) doesn't
> > > > like
> > > > xenomai-3 or vice-versa.
> > > > 
> > > > Are you aware of this?
> > > 
> > > Were you trying to use the nvidia module compiled for the vanilla
> > > kernel, or did you recompile the nvidia module for the Xenomai
> > > kernel? The former will not work.
> > 
> > the second one. Using debian packages, when you install a new one, it
> > recompiles the modules needed (if they are packaged dkms) So, when I
> > installed the debian package, all the modules (that had sources) were
> > recompiled.> 
> > > Other than that, the nvidia module has been reported to work with
> > > Xenomai, if the I-pipe patch you use contains this patch:
> > > https://git.xenomai.org/ipipe.git/commit/?h=ipipe-3.16&id=bc5bea6f134de2
> > > e55b b6014566c62fa083ed9c7b
> > 
> > The module that failed was the nvidiafb. Not the others. For instance, now
> > I'm running 3.16 with xenomai 3.0.0 in my graphical desktop with nvidia
> > driver. It's the nvidia framebuffer that fails.
> 
> AFAIK, nvidiafb is part of the Linux kernel, not of the nvidia
> driver. According to this page:
> http://wiki.gentoo.org/wiki/NVidia/nvidia-drivers

Not exactly. The nvidia driver has two parts: one for the kernel and another 
for the X server. The kernel part has public source (no open source?), and 
it's recompiled as module. The other is closed, binary. 

AFAIK, the frame buffer is to have console in booting time, or console in 
general. It's used when you switch from graphic mode to console mode. But

> - the MTRR error is due to the fact that you disabled MTRR in the
> kernel configuration, probably because you disabled IOMMU

No, I have it activated.

$ grep CONFIG_MTRR /boot/config-3.16.0-xenomai-3.0.0 
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1


> - using the nvidiafb module with the nvidia proprietary module is
> not recommended, as they are known to conflict at times.

It could have conflicts, it's true. Because the two modules try to claim the 
same device. I should have the test installing only one and see what happens.

> > In debian systems, adding
> > blacklist nvidiafb
> > 
> > to/etc/modprobe.d/nvidia-blacklists-nouveau.conf
> > 
> > solve the issue.
> > 
> > xenomai has some kind of issue tracker?
> 
> You are using it.

I love this kind of issue tracker :-)


Leopold

-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150123/b2503f38/attachment.sig>