Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1075 - modprobe: Failed to open config file /etc/modprobe.devfs

Attached to Project: Arch Linux
Opened by Rafal Szczepaniak (lanrat) - Tuesday, 06 July 2004, 19:23 GMT
Last edited by Judd Vinet (judd) - Wednesday, 07 July 2004, 02:47 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

After last upgrade of module-init-tools to version 3.0-1 I can see a few errors in /var/log/messages and on the console during startup/shutdown:

modprobe: FATAL: Failed to open config file /etc/modprobe.devfs: No such file or directory

I think everything works ok - there are only errors showing up. It seems that modprobe.devfs is now hardcoded in /sbin/modprobe.
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 12 July 2004, 01:35 GMT
Reason for closing:  Fixed
Comment by Marco Borrini (Lupetto) - Tuesday, 06 July 2004, 20:54 GMT
I also have this issue.
Comment by John Gallias (TheRaginAsian) - Wednesday, 07 July 2004, 02:19 GMT
I am experiencing this as well, not that's its all that big of a deal cause my system seems to work fine but always scares me when I halt or reboot.
Comment by Judd Vinet (judd) - Wednesday, 07 July 2004, 02:46 GMT
Does an empty /etc/modprobe.devfs fix the error?
Comment by nackd (Prieto) - Wednesday, 07 July 2004, 15:48 GMT
/etc/modprobe.devfs is missing in module-init-tools. To fix it, go to http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/module-init-tools-3.0.tar.bz2 and extract modprobe.devfs into /etc
Comment by Rafal Szczepaniak (lanrat) - Wednesday, 07 July 2004, 18:55 GMT
Thanks for the info. I'm going to test it now. But what about modules.devfs? Should it be left as it is now? (modules.devfs calls modules.conf at the end, modprobe.devfs calls modprobe.conf). Can they coexist together without any problems?

BTW putting an empty modprobe.devfs gets rid of the message too but I suppose it's not "right".
Comment by Moritz Esser (Moritz) - Wednesday, 07 July 2004, 19:20 GMT
I got the same errormessage while connecting the sshd. That message has gone after creating an empty /etc/modprobe.devfs but I still can't connect ("error: openpty no such device")
Comment by John Gallias (TheRaginAsian) - Thursday, 08 July 2004, 04:45 GMT
Thank you Prieto, that did the trick, Here's what I did exactly.

downloaded module-init-tools-3.0 using the link provided, opened at console, SU'd, ran file-roller, unpacked modprobe.devfs into /etc, closed file-roller and the console, logged out of gnome, halt, and Viola no Errors.
Comment by nackd (Prieto) - Thursday, 08 July 2004, 15:31 GMT
Rafal: I'm not an expert, but I guess modules.devfs is right as it is (the file even says "THIS IS AN AUTOMATICALLY GENERATED FILE. DO NOT EDIT!!!") and it can coexist with modprobe.devfs just as modules.conf and modprobe.conf do (one for 2.4 and one for 2.6 kernel).
An empty modprobe.devfs is the same as no one. The file is used by devfsd for module autoloading, so I think you don't need it if you load all the modules you need at boot-up (via MODULES in /etc/rc.conf).

Moritz: Maybe you don't have devpts in fstab?

John: Not at all.
Comment by Moritz Esser (Moritz) - Friday, 09 July 2004, 08:51 GMT
@Prieto: Sure it is ;-)

@all: why not update the module-init-tools with the file from kernel.org?
Comment by nackd (Prieto) - Friday, 09 July 2004, 12:03 GMT
I vote for that

Loading...