You are not logged in.
Hello!
I've just updated today, with the linux 3.1 kernel.
Pacman gave me an output for module-init-tools :
warning: /etc/modprobe.d/modprobe.conf installed as /etc/modprobe.d/modprobe.conf.pacnew
Ok, I guess.
But then,during the kernel install, it gives me a:
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.pacnew, it will be ignored in a future release
And, same thing as I've updated VirtualBox, I have to modprobe the new module, but it gives me:
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.pacnew, it will be ignored in a future release.
And, maybe my English sucks, but I really don't understand that sentence :-)
-beside, a uname -r gives me
3.0-ARCH
Shouldn't I be with the 3.1 kernel?
Hasta la Singularidad Siempre
Offline
I've just updated today, with the linux 3.1 kernel.
Congrats
Pacman gave me an output for module-init-tools :
warning: /etc/modprobe.d/modprobe.conf installed as /etc/modprobe.d/modprobe.conf.pacnew
Ok, I guess.
You guessed right.
But then,during the kernel install, it gives me a:
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.pacnew, it will be ignored in a future release
You have to merge the new contents of the pacnew file into your older conf file manually.
-beside, a uname -r gives me
3.0-ARCH
Shouldn't I be with the 3.1 kernel?
Did you reboot?
Last edited by SanskritFritz (2011-11-11 12:49:03)
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
My ..conf.pacnew was empty so I erased it. I think modprobe just reacts to the suffix .pacnew, but it's a good reminder.
Offline
Exactly.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Thanks guys, all is well.
the .conf.pacnew was empty so I erased it too, and it worked.
Out of curiosity, was there an announcement that I missed about it?
Last time I had to manually edit a file after an update was with the initscripts update, as in with this announcement:
http://www.archlinux.org/news/initscrip … -required/
Oh, and yeah: I didn't reboot, hence the old kernel - shame on me to even ask ;-)
(well, I specifically didn't reboot before I was sure about the modprobe.conf issue, but then got carried away when writing the post...)
Thanks again, have a nice week-end!
Hasta la Singularidad Siempre
Offline
Guys, you need to deal with all the pacnew files, there won't be any special announcements apart from the pacman output.
The /etc/modprobe.d/modprobe.conf.pacnew may be empty but other .pacnew files may bring important changes.
Offline
I recommend using pacmatic, nice tool.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
I recommend using pacmatic, nice tool.
Some more info and tools: https://wiki.archlinux.org/index.php/En … orig_Files
Offline