Arch Linux

lamarozzo

Member

Registered: 2008-06-29

Posts: 25

modprobe.d files

Today I read the followin Arch news

Files in /etc/modprobe.d without a .conf suffix will be ignored in the future.

What do I have to do with my /etc/modprove.d/sound file? Do I have to rename it?

Thanks.

mcmillan

Member

Registered: 2006-04-06

Posts: 737

Re: modprobe.d files

Looks that way, I had a file belonging to udev in there that got changed to a pacsave file and a new file ending in .conf was made. That seems the logical way to deal with this.

arkham

Member

From: Stockholm

Registered: 2008-10-26

Posts: 516

Website

Re: modprobe.d files

I just mv'd all the files to .conf

---

"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

VoodooSteve

Member

From: Vancouver, BC

Registered: 2009-03-31

Posts: 43

Re: modprobe.d files

I'm confused about this too. I have a few non-.conf files in there but I haven't made any modifications myself, they were placed there by arch install. Are they safe to remove or should .conf be added or what?

Last edited by VoodooSteve (2009-06-19 21:57:21)

golfadas

Member

Registered: 2008-12-05

Posts: 22

Re: modprobe.d files

im realy confused.. in /etc iv got a modprob.d and a modprobe.conf.pacsave, in mdoprob.d iv got: alsa;  framebuffer_blacklist.conf;     framebuffer_blacklist.pacsave;  modprobe.conf usb-load-ehci-first.conf. In modprobe.conf.pacsave i ve got the same ones. Where will i put alsa??

bellbottom

Member

Registered: 2008-05-20

Posts: 17

Re: modprobe.d files

Certainly, after upgrade i think nowbody knows how to save or deltele or modify the .conf files in /etc/modprobe.d
On system boot i receive a lot of meesages about files unused.

Cheers.

Last edited by bellbottom (2009-06-20 13:14:49)

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: modprobe.d files

The home page clearly states about this.For eg rename /etc/modproe.d/sound to /etc/modprobe/sound.conf

The new module-init-tools 3.8 package changes the location of the configuration file: /etc/modprobe.conf is no longer read, instead /etc/modprobe.d/modprobe.conf is used. Files in /etc/modprobe.d without a .conf suffix will be ignored in the future.

Please adjust your local configuration files after the update.

If these changes not made, will issue warnings during booting.

ammon

Member

Registered: 2008-12-11

Posts: 413

Re: modprobe.d files

Deleted my /etc/modrobe.d/sound.
Did not noticed anything diffirent after reboot.

P.S.
Cleaned my /etc/modprobe.d/ and reinstalled module-init-tools
sound file did not showed up.

moljac024

Member

From: Serbia

Registered: 2008-01-29

Posts: 2,676

Re: modprobe.d files

Read the news guys:

http://www.archlinux.org/news/450/

---

The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

azul

Member

From: New York

Registered: 2009-06-20

Posts: 5

Re: modprobe.d files

For eg rename /etc/modproe.d/sound to /etc/modprobe/sound.conf

These are the only changes that need to be made? I wasn't 100% sure at first, so I held off on the update.

moljac024

Member

From: Serbia

Registered: 2008-01-29

Posts: 2,676

Re: modprobe.d files

For eg rename /etc/modproe.d/sound to /etc/modprobe/sound.conf

These are the only changes that need to be made? I wasn't 100% sure at first, so I held off on the update.

And move modprobe.conf to the /etc/modprobe.d directory. That's it.

---

The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

ozar

Member

From: USA

Registered: 2005-02-18

Posts: 1,686

Re: modprobe.d files

Yep, the info in the news article (see post #9 above) and the warning messages provided by the upgrade itself made it pretty clear what needed to be done.

Thanks to those that provided the fixes even before the upgrade was released!

---

oz

rsambuca

Member

From: Calgary, Canada

Registered: 2008-07-21

Posts: 143

Re: modprobe.d files

Sorry to be so daft guys, but what exactly do I have to move or rename to the /etc/modprobe.d/ directory?  I have read the release, but al it says is "Please adjust your local configuration files after the update.".  This really doesn't help me as I have no idea to which configuration files it is referring, as I don't know what is and what isn't a module.  Do I have to move every *.conf file in /etc into /etc/modprobe.d/ directory?  Or do I have to move other files and add the .conf extension later? 

I am afraid the instructions for this update assume knowledge which I obviously do not have.  Any help would  be appreciated.

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: modprobe.d files

I am afraid the instructions for this update assume knowledge which I obviously do not have.  Any help would  be appreciated.

I wonder which knowledge that would be?

Just read the frontpage news, interpret what it says (there's not really a lot of room for (mis)interpretation), and act accordingly. What's so difficult? The message is pretty clear to me, and I am not a native English speaker.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

EVRAMP

Member

From: Czech Republic

Registered: 2008-10-03

Posts: 173

Website

Re: modprobe.d files

Many of you are mentioning /etc/modprove.d/sound. This was created by ALSA when configuring. Its purpose is to mark your default audio card, so pc speaker will not be used as default.
Since in arch kernel 2.6.30 was pc speaker removed, you dont need this file anymore. You need to set your default card only if you have two or more sound cards, if so change it to sound.conf and it will be fine.

rsambuca

Member

From: Calgary, Canada

Registered: 2008-07-21

Posts: 143

Re: modprobe.d files

I am afraid the instructions for this update assume knowledge which I obviously do not have.  Any help would  be appreciated.

I wonder which knowledge that would be?

Just read the frontpage news, interpret what it says (there's not really a lot of room for (mis)interpretation), and act accordingly. What's so difficult? The message is pretty clear to me, and I am not a native English speaker.

Perhaps you could read the first paragraph of my prior post where I state my exact questions.

stryder

Member

Registered: 2009-02-28

Posts: 500

Re: modprobe.d files

Basically every file currently inside /etc/modprobe.d has to end with a .conf. Otherwise they will be ignored and a warning issued when you boot. So rename every file there to end with .conf. If you have files there that end with .pacsave most probably there is already a corresponding file with .conf. If you check the creation dates the .conf file will probably be the latest. You can then delete the .pacsave file so the boot messages won't flash. If you are fearful of deleting, then just move those files somewhere else. Finally make sure that /etc/modprobe.conf is now /etc/modprobe.d/modprobe.conf.