Timeline for Cannot create "Hello World" module (and NVIDIA, and VirtualBox)
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2012 at 23:23 | comment | added | cas | thank you. i'd run out of ideas and the --color thing would never have occurred to me. | |
| Jul 28, 2012 at 14:07 | history | bounty awarded | dimitarvp | ||
| Jul 28, 2012 at 14:07 | comment | added | dimitarvp | Even though I solved the problem myself, I am giving the bounty to you. Thanks for your efforts, they are appreciated. :) | |
| Jul 27, 2012 at 13:45 | comment | added | dimitarvp | (1) dkms status gives this: nvidia, 302.17: added. (2) Yes, I have both packages since the start of my tries. (3) The command I pastes was already tried, gives the same every time (see Update #3, same happens with NVIDIA as with VirtualBox). Simply MODPOST 0 modules and that's all. :-( See my previous comment for some would-be pinpointing I did. | |
| Jul 27, 2012 at 13:07 | comment | added | dimitarvp | GNU ld (GNU Binutils for Debian) 2.22 -- this is what I get. BTW, after some inspection of Makefile.modpost, I established that the phase where .mod.c file(s) must be generated, well, they don't. So it's no wonder .ko file is not built. Reference: /usr/src/linux-headers-3.2.0-3-amd64/scripts/Makefile.modpost. Namely, step #3 is at fault. Something's wrong and and nobody tells me what it is, even when I issue make V=1. | |
| Jul 27, 2012 at 9:22 | comment | added | cas | also, what does ld -v say? if it says 'GNU gold' rather than 'GNU ld' that could be the problem. there's a comment in the nvidia src Makefile that says # avoid ld.gold, see #626279 LD=ld.bfd | |
| Jul 27, 2012 at 9:12 | comment | added | cas | what does dkms status say? have you got both linux-headers-3.2.0-3-common and linux-headers-3.2.0-3-amd64 installed? have you tried dkms build -m nvidia -v 302.17 -k 3.2.0-3-amd64 && dkms install -m nvidia -v 302.17 -k 3.2.0-3-amd64 | |
| Jul 27, 2012 at 0:00 | comment | added | dimitarvp | No luck. I am browsing modpost.c and Makefile.modpost in the hopes I can get some sort of reason... will appreciate every clue you can give me in the meantime. | |
| Jul 26, 2012 at 22:59 | comment | added | dimitarvp | My make is 3.81-8.2 at the moment (that version is both in wheezy and sid). I am gonna try the patches found in the linked bug (and a link found in there as well) and report back. | |
| Jul 26, 2012 at 22:16 | comment | added | cas | sorry, ignore that. i read it wrong. the make from experimental causes the problem. reverting fixes it. | |
| Jul 26, 2012 at 22:11 | comment | added | cas | have you seen bugs.debian.org/cgi-bin/bugreport.cgi?bug=635317 ? different error message, but the problem was solved by upgrading to the make package from experimental. what version of make is installed? I have 3.81-8.2 from sid. experimental has 3.82-1. | |
| Jul 26, 2012 at 11:52 | comment | added | dimitarvp | Sadly, no joy. Removed RVM from my .bashrc files (both the root and the regular user), restarted the console, then purged dkms (which naturally purged nvidia-kernel-dkms and virtualbox-dkms). Then I did apt-get clean (even though debsubs didn't report problems), then I did reinstall them. Nothing changed. Can we try to solve the issue in Update #4 btw? (I believe it's the root of the problem.) I got a tiny "hello world" module, and even it doesn't get a .ko file built. You got any idea on this? | |
| Jul 26, 2012 at 2:38 | comment | added | dimitarvp | You could be right. I got RVM, and it's infamous for overriding important things in one's environment. Just finished my 18-hour freelancing "working day", gonna crash now, but both your suggestions will be tried, first thing when I get up. Thanks. | |
| Jul 25, 2012 at 23:24 | comment | added | cas | sorry, kind of skipped over it in a tl;dr fashion :). I did notice just now in UPDATE #1 that you have several non-standard directories in your PATH...is there any chance there's a conflicting binary/script in one of those dirs? have you tried setting a "standard" PATH (just the usual system dirs) before building the dkms module? | |
| Jul 25, 2012 at 23:14 | comment | added | dimitarvp | Thank you. Didn't try to purge dkms itself yet -- I am gonna do it after I am done working for the day. I got another question for you though -- did you read my edits on trying to create a "hello world" module? The part where no .ko file ever gets created? Do you got any idea on how should I remedy this? (modpost is inside the linux-kbuild-3.2 package btw.) | |
| Jul 25, 2012 at 11:34 | history | answered | cas | CC BY-SA 3.0 |