site  contact  subhomenews

Neo-64 hits another bump

September 27, 2015 — BarryK
I reported about a problem with my "neo-64" build, x86_64 kernel with all-32bit packages:
http://bkhome.org/news/201510/neo-64-hits-a-bump.html

Another problem I had was the Xorg 'modesetting' driver didn't work, or rather, mostly didn't.

I solved this by installing the 64-bit Xorg. Now everything seems to work.

While doing this, my frustration with the "/usr/X11R7" path boiled up.

I once suggested to Rene that T2 should have the option of building Xorg in /usr, like all other distros, but got no response.

Perhaps one day I should modify T2, however, for now I am thinking of doing away with /usr/X11R7 in woofQ, simply by moving everything into /usr.

This would simplify a lot of things, especially all the weird symlinks I have had to put in.

I might have a look at doing that tonight.

Comments

I built my neo-64 Quirky with 64-bit Xorg, thinking that it would fix the malfunctioning 'modesetting' driver.

However, today I discovered that the 32-bit modesetting driver works fine.

What was causing it to go wonky is the hybrid video in my laptop. My Acer 5742G laptop has Intel video, plus NVIDIA GeForce GT 420M video.
In theory, I could use either, however I have only ever used the default, the Intel video.

The kernel loads both the 'i915' and 'nouveau' driver modules, with default of KMS enabled. It is the latter that was upsetting the Xorg 'modesetting' driver (which requires the kernel i915 module only, as I am using that video interface).

Curiously, I don't recall having this problem before. I am wondering if it is something new with the 4.1.7 kernel.

Anyway, I did not blacklist the 'nouveau' module, just set its parameter to "modeset=0" -- this is done in the 'xorgwizard' script.
Now, 32-bit Xorg is working great.

I also fixed a couple of other things in 'xorgwizard'.

So, currently the only 64-bit application in my neo-64 Quirky is the 'ddcprobe' utility.

Tags: linux