[SOLVED] How resolve "/pre-trigger/10plymouth-pretrigger.sh: 22: /lib/udev/console_init: not "

915086731 · 12-20-2010, 07:15 AM

Hello everyone!
These days, I get "/pre-trigger/10plymouth-pretrigger.sh: 22: /lib/udev/console_init: not found" message when boot fedora 14. Then the resolution is low and I can not get it higher to recommended level.
What confuse me is I can find /lib/udev/console_init , but can not find /pre-trigger/10plymouth-pretrigger.sh . Where is /pre-trigger/10plymouth-pretrigger.sh?
The content of boot.log is:

Code:

[saturn@localhost ~]$ cat /var/log/boot.log
/pre-trigger/10plymouth-pretrigger.sh: 22: /lib/udev/console_init: not found
		Welcome to Fedora 
Starting udev:                                             [  OK  ]
Setting hostname localhost.localdomain:                    [  OK  ]
Setting up Logical Volume Management:   No volume groups found
                                                           [  OK  ]
Checking filesystems
/dev/sda1: clean, 48238/642112 files, 856327/2564367 blocks
/dev/sda2: clean, 252490/2088960 files, 2581757/8351791 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
ip6tables: Applying firewall rules:                        [  OK  ]
iptables: Applying firewall rules:                         [  OK  ]
Starting portreserve:                                      [  OK  ]
Starting system logger:                                    [  OK  ]
Enabling ondemand cpu frequency scaling:                   [  OK  ]
Starting irqbalance:                                       [  OK  ]
Starting rpcbind:                                          [  OK  ]
Starting mdmonitor:                                        [  OK  ]
Starting system message bus:                               [  OK  ]
Setting network parameters...                              [  OK  ]
Starting NetworkManager daemon:                            [  OK  ]
Starting Avahi daemon...                                   [  OK  ]
Starting NFS statd:                                        [  OK  ]
Starting RPC idmapd:                                       [  OK  ]
Starting cups:                                             [  OK  ]
Starting acpi daemon:                                      [  OK  ]
Starting HAL daemon:                                       [  OK  ]
Retrigger failed udev events                               [  OK  ]
Starting PC/SC smart card daemon (pcscd):                  [  OK  ]
Starting VirtualBox kernel modules                         [  OK  ]
Starting sshd:                                             [  OK  ]
Starting ntpd:                                             [  OK  ]
Starting abrt daemon:                                      [  OK  ]
Starting ksm:                                              [  OK  ]
Starting ksmtuned:                                         [  OK  ]
Starting crond:                                            [  OK  ]
Enabling monthly Smolt checkin:                            [  OK  ]
Starting atd:                                              [  OK  ]
Starting jexec servicesRegistering binary handler for Windo[  OK  ]cations: 
[saturn@localhost ~]$ co

Can anyone help me?

PTrenholme · 01-09-2011, 08:54 PM

That executable is used to initialize your terminal, setting your keyboard and character set as specified by your language settings. Without it you terminal will (probably) default to USA keyboard and character settings.

The program is part of the initscripts package, so a simple sudo yum reinstall initscripts should resolve the problem.

A more fundamental question is: "Why was that package not properly installed or, if it was, what happened to it?" Since it is one of the initialization scripts, its absence would cause me to wonder what else might be wrong with my system, and to look for stuff like "rootkits" and other hijacking packages that might have gotten past my firewall. (But, hey, I spent a lot of time with Windows systems, so maybe I'm a little paranoid. It might just be a non-standard installation or something simple like a failing disk drive. [Oops! Sorry, see prior sentence re paranoia.])

915086731 · 03-23-2011, 06:39 AM

Thanks you very much