Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

wilberfan · 2011-11-10 01:22:44

I didn't know about Linux-ck. Might be something to look into!

swanson · 2011-11-10 03:36:28

Just tried linux-ck-kx and nvidia-ck and exactly the same problem;

[ 366.922990] vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size.
[ 366.924426] NVRM: RmInitAdapter failed! (0x26:0xffffffff:1175)
[ 366.924432] NVRM: rm_init_adapter(0) failed

And also, nvidia-beta (290.x) couldn't find kernel sources though headers were installed. So no go yet!

Last edited by swanson (2011-11-10 03:56:53)

graysky · 2011-11-10 10:32:23

...sure you have that piece of hardware?

swanson · 2011-11-10 10:57:54

I've run your ck-k10 kernel before on my Athlon II 260 CPU. And my Nvidia 220GT has functioned very well on all nvidia drivers and kernels up until kernel 3.1.x and nvidia 285.05.09-3. 285.05.09-1 and 3.0.7 was fine. But now ...

EDIT; trials so far;
Standard arch kernel 3.1.-4 / nvidia 285.05.09-3 - no go (logs above)
Kernel linux-ck-kx (3.1-4) / nvidia-ck-kx (285.05.09-6) - no go (same logs as above)
Zen-kernel linux-zen (3.1.0-1) / nvidia-zen 280.13 from AUR - no go - logs;

[ 82.905037] NVRM: API mismatch: the client has the version 285.05.09, but
[ 82.905038] NVRM: this kernel module has the version 280.13. Please ...
(I guess I could fix this ... )

Nvidia-beta from AUR won't compile complaining not to find kernel sources though headers ARE installed.

My thoughts; kernel 3.1.x seems to mess up a lot of things; nvidia, alsa, some nic's as seen in several threads here.. I can't really make heads ot tails of it. Where do I start?

One more thing to test; manually grab kernel and nvidia packages from testing repo and install them too. Can't go any worse.
EDIT no 2; found no linux 3.1.x packages in testing. So hanging back and wait seems to be the order of the day. I'm out of options.

Last edited by swanson (2011-11-10 11:27:13)

graysky · 2011-11-10 11:53:24

No idea dude.. At least your problem is constant across kernel families.... Also, edit the nvidia-ck-beta pkgbuild to require the headers and Linux packages you have... Or just delete those lines from the pkgbuild. Also 3.1-4 has been moved out of [testing] and into [core].

swanson · 2011-11-10 12:01:31

graysky wrote:

Also, edit the nvidia-ck-beta pkgbuild to require the headers and Linux packages you have... Or just delete those lines from the pkgbuild.

I'll try this later today. Thanks for the concern Graysky!

brain0 · 2011-11-10 14:47:37

swanson wrote:

X won't start and this pops up; "id 'x' respawning too fast"
After console login this snippet from dmesg is interresting;
[ 366.922990] vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size.
[ 366.924426] NVRM: RmInitAdapter failed! (0x26:0xffffffff:1175)
[ 366.924432] NVRM: rm_init_adapter(0) failed

I this an i686 installation? If so, read the "Kernel virtual address space exhaustion on the X86 platform" on ftp://download.nvidia.com/XFree86/Linux … ssues.html (which I found after 10 seconds of googling the above error message). This whole problem could be caused by some VM changes in 3.1.

Also, all this "install this", "rebuild that" crap in this thread is entirely useless and a waste of time. The nvidia module itself and linux package from the repositories work great, rebuilding random packages won't "fix" them. It really tires me to keep seeing BAD ADVICE that is completely UNRELATED TO THE PROBLEM everywhere in this thread - most of you seem to neither have read the thread nor understood the problem. Nobody requested additional information, nobody referred to the information given. Instead, everyone told the poor users to randomly install and rebuild things, likely screwing up their systems and causing tons of new problems without fixing the original one. Shame on you, Arch users, shame on you!

swanson · 2011-11-10 15:30:12

Yes I'm on i686. Yes I found that info as well but deemed it old and dubious since it suggested 2-3 kernel parameters which slow everything down. Furthermore my gt220 card should work with this setup. But, having said that, arch is a rolling release and surprises are to expect. So, hug the console and do some trial and error research!

brain0 · 2011-11-10 15:40:11

swanson wrote:

Yes I'm on i686. Yes I found that info as well but deemed it old and dubious since it suggested 2-3 kernel parameters which slow everything down.

Yes, vmalloc= is not the best idea, but if you try experimenting with values like the nvidia readme suggests, you will likely get it to work again.

swanson wrote:

Furthermore my gt220 card should work with this setup. But, having said that, arch is a rolling release and surprises are to expect. So, hug the console and do some trial and error research!

It should. But ... the limited address space of 32 bit systems is a problem. Changes in the way Linux handles vmalloc could always cause this problem. Can you compare the output of

$ grep Vmalloc /proc/meminfo

for 3.0 and 3.1?

I don't know if there is a real solution to this issue, other than installing a 64 bit system.

swanson · 2011-11-10 16:44:44

Looked into vmalloc further and it might be the thing. Seems that some dvb cards (Hauppauge which I have) can compete with Nvidia drivers on 32-bit systems and increasing vmalloc might do the trick without slowing things down too much. My first google round gave something about CUDA and kernel 2.6.9 which I discarded, a bit too hastily it seems.

I will try to put vmalloc=256M at the kernel line later tonight. More info;
http://www.mythtv.org/wiki/Common_Probl … _too_small

I will also contemplate a 64-bit system. But that's another kettle of fish altogether.

@wilberfan; do you have some dvb card as well? Or maybe a bit too small RAM on a 32-bit Arch?

Last edited by swanson (2011-11-10 16:47:34)

brain0 · 2011-11-10 16:52:53

The problem is not too small RAM, but too much RAM - I I remember correctly, if you have more RAM, this problem shows more often.

Can you still show me the output of grep Vmalloc /proc/meminfo? I am really interested in the actual values.

swanson · 2011-11-10 17:02:21

I'm not present at the moment (on the machine concerned). But will be later. By the way, I have 2 GB RAM which is modest by todays standards I think.

Thanks for the help and insights! Very welcome!

wilberfan · 2011-11-10 18:13:36

swanson wrote:

Looked into vmalloc further and it might be the thing. Seems that some dvb cards (Hauppauge which I have) can compete with Nvidia drivers on 32-bit systems and increasing vmalloc might do the trick without slowing things down too much. My first google round gave something about CUDA and kernel 2.6.9 which I discarded, a bit too hastily it seems.
@wilberfan; do you have some dvb card as well? Or maybe a bit too small RAM on a 32-bit Arch?

Actually, I do. A Hauppauge PVR-350. (This is box doubles as my mythTV install). 32-bit, 2GB of RAM. :-O

wilberfan · 2011-11-10 18:46:03

brain0 wrote:

Also, all this "install this", "rebuild that" crap in this thread is entirely useless and a waste of time. The nvidia module itself and linux package from the repositories work great, rebuilding random packages won't "fix" them. It really tires me to keep seeing BAD ADVICE that is completely UNRELATED TO THE PROBLEM everywhere in this thread - most of you seem to neither have read the thread nor understood the problem. Nobody requested additional information, nobody referred to the information given. Instead, everyone told the poor users to randomly install and rebuild things, likely screwing up their systems and causing tons of new problems without fixing the original one. Shame on you, Arch users, shame on you!

Not to step on any well-intentioned toes, but I thought this was a very valid point... Thanks for saying it out loud...

dhave · 2011-11-10 19:07:14

brain0 wrote:

Also, all this "install this", "rebuild that" crap in this thread is entirely useless and a waste of time. The nvidia module itself and linux package from the repositories work great, rebuilding random packages won't "fix" them. It really tires me to keep seeing BAD ADVICE that is completely UNRELATED TO THE PROBLEM everywhere in this thread - most of you seem to neither have read the thread nor understood the problem. Nobody requested additional information, nobody referred to the information given. Instead, everyone told the poor users to randomly install and rebuild things, likely screwing up their systems and causing tons of new problems without fixing the original one. Shame on you, Arch users, shame on you!

... just changed my "From" location accordingly. I hope there's no irreversible harm caused.

swanson · 2011-11-10 19:12:07

Kernel 3.0.7x :

grep Vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 71044 kB
VmallocChunk: 18940 kB

Kernel 3.1.x _

VmallocTotal: 122880 kB
VmallocUsed: 84952 kB
VmallocChunk: 11816 kB

BUT this is with all dvb cx88 modules blacklisted!! AND now the whole new upgraded linux (3.0.7-1 -> 3.1-4) and upgraded nvidia (285.05.09-1 -> 285.05.09-3).

So in my case this is solved partly at least. Yey!

@wilberfan: you have some tests to do; Either take out the dvb card, or blacklist all its modules or add vmalloc=256MB at the end of the kernel line.

In my case I was lazy and just blacklisted the modules. I had them all listed already in modprobe.conf. And I migth throw it out because with recent changes here, almost all channels are HD and my card , HVR1300, can't use them. So I had only 2 channels in left anyway.

I will thank ALL that helped with tips and good spirits. There are sometimes several solutions to a linux problem and positive thinking goes a long way. But without brain0's insights I would have stumped. Thx m8!

PS I'll place myself at the back of the woodshed for not googling deep enough! See you there Dhave!

Last edited by swanson (2011-11-10 19:37:12)

dr.dynamics · 2011-11-10 20:44:16

An upgrade to linux-3.1-4 is also unkind to my Intel GMA 4500MHD video card (in an HP 2730p). Screen flicker / wierdness. Tried an experiment, booted with a liveCD/USB of shiny new Fedora 16, also using kernel 3.1 -> same issue.

brain0 · 2011-11-11 09:14:49

swanson wrote:

Kernel 3.0.7x :
grep Vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 71044 kB
VmallocChunk: 18940 kB
Kernel 3.1.x _
VmallocTotal: 122880 kB
VmallocUsed: 84952 kB
VmallocChunk: 11816 kB
BUT this is with all dvb cx88 modules blacklisted!! AND now the whole new upgraded linux (3.0.7-1 -> 3.1-4) and upgraded nvidia (285.05.09-1 -> 285.05.09-3).

Yeah, there is some difference in VmallocUsed as you can see (slightly more with the new kernel). This difference is probably the reason why your DVB and nvidia won't work in parallel. vmalloc=192M should suffice in any case!

I hate to repeat myself, but you will never have these limitations with a 64 bit system.

brain0 · 2011-11-11 09:16:22

wilberfan wrote:

swanson wrote:
@wilberfan; do you have some dvb card as well? Or maybe a bit too small RAM on a 32-bit Arch?
Actually, I do. A Hauppauge PVR-350. (This is box doubles as my mythTV install). 32-bit, 2GB of RAM. :-O

Okay, this sounds like exactly the same issue.

brain0 · 2011-11-11 09:17:36

dr.dynamics wrote:

An upgrade to linux-3.1-4 is also unkind to my Intel GMA 4500MHD video card (in an HP 2730p). Screen flicker / wierdness. Tried an experiment, booted with a liveCD/USB of shiny new Fedora 16, also using kernel 3.1 -> same issue.

There's some discussion about intel graphics issues on the mailing list, and there are a few patches queued for 3.1.1. The only thing I am certain of is this: This is not related to the nvidia problem.

swanson · 2011-11-11 09:46:59

Well, my card is too old now but I'll look into a 64-bit system anyway.

bangkok_manouel · 2011-11-11 09:52:43

install a 64bit kernel on your existing machine/install, keep nvidia-utils 32bit and install only the 64bit nvidia kernel module. that is, if you have a 64bit capable cpu of course. if you compile anything that is using uname to check your arch, use the linux32 tool provided by the util-linux package.

/edit: typo

Last edited by bangkok_manouel (2011-11-11 09:53:20)

swanson · 2011-11-11 10:14:50

This Wiki article about full migration without reinstalling, to 64-bit seems to be ok :

https://wiki.archlinux.org/index.php/Mi … installing

bangkok_manouel · 2011-11-11 10:22:38

or you can use a 64bit kernel with 32bit userland as stated above for a super fast fix.

4javier · 2011-11-11 11:35:14

Ignorance time:
shouldn't be this problem avoided, using an i686 kernel compiled enabling PAE?

Arch Linux

#26 2011-11-10 01:22:44

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#27 2011-11-10 03:36:28

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#28 2011-11-10 10:32:23

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#29 2011-11-10 10:57:54

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#30 2011-11-10 11:53:24

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#31 2011-11-10 12:01:31

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#32 2011-11-10 14:47:37

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#33 2011-11-10 15:30:12

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#34 2011-11-10 15:40:11

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#35 2011-11-10 16:44:44

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#36 2011-11-10 16:52:53

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#37 2011-11-10 17:02:21

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#38 2011-11-10 18:13:36

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#39 2011-11-10 18:46:03

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#40 2011-11-10 19:07:14

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#41 2011-11-10 19:12:07

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#42 2011-11-10 20:44:16

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#43 2011-11-11 09:14:49

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#44 2011-11-11 09:16:22

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#45 2011-11-11 09:17:36

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#46 2011-11-11 09:46:59

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#47 2011-11-11 09:52:43

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#48 2011-11-11 10:14:50

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#49 2011-11-11 10:22:38

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

#50 2011-11-11 11:35:14

Re: Upgrade to linux-3.1-4 and nvidia 285.05.09-3 broke my X

Board footer