Seen these errors?

***glennzo*** · #1 10th March 2009, 10:50 AM

Hi guys. Anyone seeing these errors when booting F11 Alpha?

Quote:

[root@alpha ~]# cat /var/log/boot.log | more
Welcome to Fedora
Press 'I' to enter interactive startup.
Starting udev: Loading /lib/kbd/keymaps/i386/qwerty/us.map.gz
[ OK ]
Setting hostname alpha: [ OK ]
Setting up Logical Volume Management: [ OK ]
Checking filesystems
Fedora11: clean, 122153/1313280 files, 1001655/5242880 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
Entering non-interactive startup
Applying Intel CPU microcode update: WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future
release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.

WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future rel
ease.

Enabling p4-clockmod driver (passive cooling only): [ OK ]
ip6tables: Applying firewall rules: WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future
release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.

WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future rel
ease.
[ OK ]
iptables: Applying firewall rules: [ OK ]
Starting auditd: [ OK ]
Starting portreserve: [ OK ]
Starting system logger: [ OK ]
Starting irqbalance: [ OK ]
Starting rpcbind: [ OK ]
Starting NFS statd: [ OK ]
Starting RPC idmapd: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /et
c/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future
release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.

WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future rel
ease.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future
release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.

WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future rel
ease.
[ OK ]
Starting system message bus: [ OK ]
Starting Avahi daemon... [ OK ]
Starting cups: [ OK ]
Starting acpi daemon: [ OK ]
Starting HAL daemon: [ OK ]
Starting PC/SC smart card daemon (pcscd): [ OK ]
Setting network parameters... [ OK ]
Starting NetworkManager daemon: [ OK ]

Starting crond: [ OK ]
Starting atd: [ OK ]

Not a big deal since any alpha machine should be considered a toy at this point but I'm just curious to see if anyone else has seen these errors.

leigh123linux · #2 10th March 2009, 10:53 AM

You can stop the error by renaming the listed files.

i.e

Code:

/etc/modprobe.d/blacklist

becomes

Code:

/etc/modprobe.d/blacklist.conf

***glennzo*** · #3 10th March 2009, 11:07 AM

Good morning Leigh. (still AM in England I believe?) Thanks for the reply. That's pretty much what I figured. Seemed fairly obvious although I wasn't entirely sure if it was the right thing to do. I'll give it a go.

***glennzo*** · #4 10th March 2009, 11:16 AM

Leigh, you are right on the money, as usual. All errors gone now that I made those changes. Thanks a bunch.

leigh123linux · #5 10th March 2009, 11:22 AM

It's still AM here ( 10:21 GMT ), renaming the files fixed it for me.

Time to reboot

Code:

  Cleanup        : kernel                                                                     8/8 

madwifi-trunk (r3940-20090129.01): Installing module.
.....................
......
nvidia (180.37-1.fc10): Installing module.
.............
......
vboxdrv (2.1.4): Installing module.
.............
......
vboxnetflt (2.1.4): Installing module.
............
......

Removed:
  kernel.x86_64 0:2.6.29-0.33.rc5.fc10                                          
  kernel-devel.x86_64 0:2.6.29-0.33.rc5.fc10                                    

Installed:
  kernel.x86_64 0:2.6.29-0.54.rc7.git3.fc10                                     
  kernel-devel.x86_64 0:2.6.29-0.54.rc7.git3.fc10                               

Updated:
  kernel-firmware.noarch 0:2.6.29-0.54.rc7.git3.fc10                            
  kernel-headers.x86_64 0:2.6.29-0.54.rc7.git3.fc10                             

Complete!

Edit it's good

Code:

[leigh@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.29-0.54.rc7.git3.fc10.x86_64 #1 SMP Tue Mar 10 03:03:50 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[leigh@localhost ~]$

**AdamW** · #6 10th March 2009, 09:11 PM

They're only deprecation warnings, anyway. Nothing's actually broken.

I tend not to work around problems like this, so that I can keep an eye on them and if there's still a file or two which hasn't been changed a few months down the road, I can poke the maintainer to take care of it.

scottro · #7 19th April 2009, 02:54 PM

posterartist---
If I may make a suggestion, you're FAR more likely to get valuable answers by deleting this post, which is in a completely unrelated thread, and reposting it with a descriptive subject line. As it is, people might glance at the subject, recognize that it's an old thread, and not even bother going to the end to see your question.

By descriptive subject line, I mean something like No acpi found Live KDE CD.

Putting your post here, at the end of a relatively dated, completely unrelated thread is not a good way to get the attention of someone who might know the answer.

I say "delete this post" because double posting is a no-no.
I would also suggest you mention which Live CD.