could not generate /etc/modprobe.conf [solved]

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

Dear all:

I found other users also having a similar prob here after upgrading to the newest stable version of baselayout:

ecatmur · Posted: Sun Jan 22, 2006 3:30 pm Post subject:

Try modules-update --verbose.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

ecatmur · Posted: Sun Jan 22, 2006 5:26 pm Post subject:

Right, that flag is in unstable baselayout (1.12.0_pre14).

Try /sbin/generate-modprobe.conf.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

i see.....if I still can't get it in a few days, I'll try emerge that version of baselayout, thank you!

tried generate-modprobe.conf, but the problem persists.

Fester · Posted: Mon Jan 23, 2006 8:02 am Post subject:

I recently had this problem and the issue ended up being that I had compiled and installed a new kernel but forgotten to run "make modules_install", and so /lib/modules/<current_kernel_version> did not exist. Of course that's a rather silly thing to forget to do so perhaps your problem is completely different, but I thought I'd throw it out there.

ecatmur · Posted: Mon Jan 23, 2006 9:56 am Post subject:

Which version of module-init-tools are you running?
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

nunogt · Posted: Mon Jan 23, 2006 11:31 am Post subject:

/sbin/generate-modprobe.conf didn't work for me either.

Btw, I'm running sys-apps/module-init-tools-3.2.1

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

Hi all, I just emerged the baselayout-1.12.0_pre13-r1, and
#modules-update --verbose
and it tells me that I have invalid items +++ in modprobe.conf, then I removed it and re-run
#modules-update
and problem solved now, even during booting.

thanks to ecatmur and all for being patient and giving helps and advices.
_________________
Appreciate Gentoo: Best Devs, Best Forums. YOU could help too: Help Answer

polle · Veteran Joined: 28 Feb 2003 Posts: 1498 Location: Belgium

I also got:
* Warning: could not generate /etc/modprobe.conf!

So I did:

/sbin/generate-modprobe.conf

result:

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

I think the key is about baselayout-1.12.0_pre13-r1, did u have that?
_________________
Appreciate Gentoo: Best Devs, Best Forums. YOU could help too: Help Answer

polle · Veteran Joined: 28 Feb 2003 Posts: 1498 Location: Belgium

No , I have baselayout 1.11.14-r2

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

I remember I have that prob as u described b4, so I only solved it after upgrading to baselayout-1.12.0_pre13-r1, hope it helps
_________________
Appreciate Gentoo: Best Devs, Best Forums. YOU could help too: Help Answer

polle · Veteran Joined: 28 Feb 2003 Posts: 1498 Location: Belgium

thanks for the feedback, I saw today that 1.11.14-r3 is now an upgrade in portage, will try that first if not , I will try your version

Sophisto · n00b Joined: 16 Jan 2006 Posts: 41 Location: Leicester, UK

Hi!

I've got a similar problem with modules-update. However, I only get an error message when i do modules-update force. If I simply do modules-update then everything is fine!

polle · Veteran Joined: 28 Feb 2003 Posts: 1498 Location: Belgium

Todya I upgraded to ~x86 baselayout1.12.0_pre15-r1
problem is solved now ( after editing /etc/modules.conf, see above)

smg · Posted: Sun Feb 12, 2006 2:57 pm Post subject:

polle · Veteran Joined: 28 Feb 2003 Posts: 1498 Location: Belgium

correct, that was the solution for me

smg · Posted: Sun Feb 12, 2006 9:09 pm Post subject:

dpetka2001 · l33t Joined: 04 Mar 2005 Posts: 804

hi there...i also get a warning about not being able to generate modprobe.conf during boot messages...i have read through this thread...as far as i understand upgrading to ~x86 baselayout is the only solution until now is that right?? is it in general recommended using ~x86 baselayout in general?? and what is the problem of not being able to generate modprobe.conf?? is it really bad??

hurricane · Tux's lil' helper Joined: 15 Jul 2004 Posts: 100

Allright. This is the same shit as every time one has to update:
"Stable" packages throw errors in portage, hae errors in their configs or simply buggy ebuilds! And not a single word in GWN or anywhere!

This time i ran my self-written installer-script (exact listing of the commands i would type when following the manual. i even went trough the whole manual before running it.),
but nooo: on modules-update this crap can't even write to /etc/modprobe.conf!
Even when i do a:
chmod a+rwX /etc /etc/modprobe.conf

This really FUCKING SUCKS!!!

If i want to have a system that dies on every update i take WindowsME!
Even WinXP works better than this shit!

Why can't the portage maintainers TEST their shit before putting it in "stable"???
here's how i compare gentoo to debian:
testing = ~arch
unstable = arch
stable = n/a

And of course the portage maintainers rather like to remenber me of the netiquette than thinking they coul *pussibliy* ever do something wrong!
Nooo... not them... the're GODS who are PERFECT!

I really CANT'S STAND IT ANYMORE!!!

If you do it on a free basis but are incompetent, then STOP IT! PELASE!

To me, the actual state of portage is worse than not having portage at all!

I don't want to hear any elusions anymore! FIX IT! For your own sake!

golding · Posted: Wed Mar 01, 2006 5:05 am Post subject:

Sorry for coming in late, however, I think you'll find the correct command is

#> update-modules -vd (verbose & debug)

which I have used on many occasions without any drama.

Until I checked a moment ago, I didn't even know that the command "modules-update" existed. I learned about the other command from the comments in the file

/etc/modules.d/alsa

when I was learning how the Gentoo module system worked just so I could get my sound. The file I read has this to say

## IMPORTANT
## You need to customize this section for your specific sound card(s)
## and then run 'update-modules' command
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##

Before Gentoo I had only used "generate-modprobe.conf " and found it wanting for this distro.

BTW hurricane, as a results driven strategy, tantrums do not work very well, except at the age of about 2, and even then only on your own parents. I would expect not on a list where we would hope we are all just a little more mature, indeed, professional than that :roll:

_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.

step · Apprentice Joined: 16 May 2002 Posts: 173

Sophisto, please look at your /etc/modules.d/alsa

there must be some garbage in your file at line 62
you have a empty "option" there.

I had same problem and then I discovered, that in my /etc/modules.d/alsa had a line that started with '-a'.
After i fixed this line '-a' , my modules-update works OK.
No need to upgrade to ~x86.

Decibels · Veteran Joined: 16 Aug 2002 Posts: 1542 Location: U.S.A.

I just had this problem because of lines added from /etc/modules.d/sensors.
It was just the modprobe lines for each one. Not sure why. So for right now
commented them out cause don't use lm_sensors much anyway.
They modprobed fine, so wasn't like I recompiled the kernel and did something
different with the modules.
That got rid of the error.

Going to have to look into it more later.
_________________
http://webpages.charter.net/decibelshelp/
Don't assume malice for what stupidity can explain.
Always remember you're unique. Just like everyone else.
Everybody lies........but it doesn't matter since nobody listens.

tecknojunky · Posted: Thu Jul 20, 2006 2:10 pm Post subject: