i'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
View 6 RepliesWhen booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
View 7 Replies View RelatedI've done an upgrade from lenny to squeeze.Now, I'm getting a lot of udev warning messages at the boot time.Knows someone howto remove them?
View 6 Replies View RelatedI'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I recently did a fresh install of current and once I had it up and running I compiled a fresh 2.6.33 kernel using my old config file, but now I get this warning durning boot, specifically during module loading WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release. This doesn't seem to be causing any problems but I am curious to know what the message meams? I checked /etc/modprobe but everything looks normal.
View 1 Replies View RelatedMy fedora 11 (2.6.30-102) spends a long time while initializing services on
"Starting system message bus:"
---------- Post added at 08:47 PM CST ---------- Previous post was at 06:33 PM CST ----------
Auth is LDAP.
There's a 3.5 years old bug in redhat bugs database, that's still not resolved,regarding dbus trying to use ldap auth, before ldap service is started.Workaround is to change ldap config to soft binding.
3.5 years for a bug that affect enterprise users - are you there redhat?
Sometimes when I try to open some chat application i get a strange warning message asking for password. The message is that /usr/libexec/mission-control is trying to gain access of the system, please provide the password. On top of the message box it shows "Unlock Keyring".
This very weird, as I am also unable to do a print-screen when this message box is up.
what this message is all about and what does the executable /usr/libexec/mission-control do?
I am using Empathy as my chat application
I am getting the following message
WARNING: probably, rcvbuf is not enough to hold preload.
When i try to adjust the mtu to the router (1400) config
What is wrong about message? if i change to a low value, like 500, the message it doesn't showed..
Just installed F15, was everything fine, but then gnome got away, from terminal I have<gnome-session:1951): Warning can't start display message.Before that I put in config file one extra line to start tint2 like <sleep 3 && tint2.Not sure was it the reason?
View 4 Replies View RelatedCode:
Probing EDD (edd=off to disable) .... then the boot hang up for a few minutes with a flashing cursor immediately after the message and finally it booted the default OpenSuse 11.1 in the usual way. I tried to search LQ, Wikipedia, Google... but even if the message has been reported by many people, nobody gave the answer to the question running in my mind:
Code:
What is EDD? Should I start to think about the funeral for my beloved notebook? Should I consider to do an additional backup copy of the backup of my disk, just for sure?
I'm getting strange error after the splash screen in lucid
(process:290):GLib-Warning**:getpwid_r():failed due to unknown user id(0)
(process:315):GLib-Warning**:getpwid_r():failed due to unknown user id(0)
after this error the screen just hangs.
I have done a fresh text-only installation of Fedora 10 on a Dell Dimension E521 for the purpose of setting up a server. After installation I ran yum update to bring the system up to date. After the update, I rebooted the computer, but the boot process froze. I recycled power and pressed "I" after the Dell BIOS screen and the GRUB bootloader appeared. I selected the most current version, edited the kernel line by deleting "rhgb quiet" and replacing it with "3." After making this change, I continued with the boot and the computer stopped at "Starting udev:" I have two fedora 10 revisions showing in the GRUB bootloader, the original installation and the update after running yum.
I repeatedly tried rebooting both versions and, after about 30 attempts, the computer finished booting and got me to the command prompt. Reading through the forums indicated there might be some issue with my nVidia GeForce 6150 onboard video and fedora 10. So, when I got to the command prompt, I followed the instructions in the forums [URL] to load the rpmfusion drivers. This appeared to be successful and when I looked at /etc/X11/xorg.conf it appeared to be correct for the new nVidia drivers. After loading these new drivers I tried rebooting. Unfortunately, I have been trying now over and over to get back to the command prompt, but simply can't get past "Starting udev."
Fedora 12 randomly crashes after a fresh install.Everything is left at its default during the installation except I install KDE and not Gnome.When I try to boot I hit esc at the splash screen to see where it hangs, but it never hangs at the same spot twice. Sometimes it hangs and sometimes it restarts. Its crashed everywhere from starting udev to the login screen.
I've been using kubuntu for the past year because I have the same problem with F10 and F11.
I dual boot with Windows 7 for games.
System specs:
Motherboard: MSI P45 Platinum
Processor: Intel Core 2 Duo E8500
Video Card: Radeon HD4850
Memory: 4GB (2x2GB) Patriot
HDD: Main: 250GB SATA Western Digital
code....
Is there any way to set up my system so that, just before I run out of RAM, and SWAP is utilized, I can get a warning message so that I can kill the memory hog before my computer slows to a crawl?I'm a programmer, and it's happened a few times that my programs have memory leaks and run over into SWAP and effectively freeze my system.
View 2 Replies View RelatedI'm pretty new to Ubutnu and Linux in general so take it easy on me. I'm a Senior at the University of Houston and part of our final project involves running an application in Ubuntu that was developed by another university. It installs fine, but when I run the command the launch the configure gui I get a strange warning message.
View 2 Replies View Relatedim writing a simple socket program and im getting below mentioned warning msg. what does it mean and what i have to do to avoid this warning ??
/usr/include/sys/socket.h:214: note: expected 'socklen_t * __restrict__' but argument is of type 'int *'
Why is it when I run gedit, there are always tonnes of error or warning messages? (Even though my gedit ran successfully)
To name a few:
1. GConf error: failed to contact configuration server; some possible causes are that you ned to enable TCP/IP networking for 0 RBit, or you have stale NFS lockes due to a system crash.
2. Failed to get connection to session: Did not receive a reply among others.
Just to mention again my gedit is running fine though. Is there any configuration that I missed out? or I can disable to avoid these nuisance?
I had occasion to add a few lines to rc.sysinit. Turns out the lines syntax was wrong. Instead of the booting ignoring those lines and proceeding on, then giving me an error warning or perhaps dumping into the interactive mode it just hung up! After several tries at moving on I discovered ESC dropped me into some sort of unannounced shell I got the installation disk out and with the repair system option using VI I got the lines deleted and all went back to normal. Now my suggestion is that if something does not make sense in terms of syntax while booting then cover it by doing the above and ignoring it with a warning later.
View 14 Replies View RelatedI'm not concerned about this since this traffic is generated from the loopback address, but would like to find out what it is.
[code]...
rencently, i move develop env from one linux machine to another, two linux have same gcc and make version, but at new linux machine make warning/error messages dont show color font.so, when make, there are all white messages, i cant focus on warning and error.
View 2 Replies View RelatedI just wrote a simple perl script to compare the following two files
[Code]...
I see these boot.log warning and understand that the directory where these config files are kept has (or is) changing. Okay, but is the correct procedure to just move them over from the /etc/modprobe.conf dir to the /etc/modprobe.d file? I am wondering if some changes to those config files or those that they are related to must be also made? A portion of the boot.log is below.
[Code]....
I speeded up boot time significantly. This was accomplished by using chkconfig off to stop unneeded services from starting at boot time and by reinstalling without LVMs
There are now just two remaining things that are slowing down boot time:
1- At boot time, I see the message "Setting up LVM" and after a while "LVM not found" Is there a way to keep Centos from trying to set up LVM? (I am not using LVM, that is why it is not found)
2- I am using a Lenovo Thinkpad and there is a delay at boot time as Centos setting up the built in mouse: "TPPS/2 IBM TRACKPOINT as class /input/input6"
I do not need the trackpoint (I use an USB mouse), Is there a way to disable the built in trackpoint (mouse) so that Centos doesn't spend unnecessary time install it at boot time?
I get an expired key warning every time I add a repo from the OBS. Creation/expiration dates are the same each time. This alway happens in the OBS, not Packman or elsewhere. I've tried cleaning the metadata and cache, and doing a rebuild with rpm. I've removed all of the existing keys associated w/OBS. Somebody know what this is about? I can't think of anything else to try.
Code:
New repository or package signing key received:
Key ID: 9584A164BD6D129A
[code]...
I'm running CentOS 5.3 on a laptop and there are numerous warnings in the dmesg output that look like:
Warning Timer ISR/0: Time went backwards: delta=-252671169 delta_cpu=-248671169 shadow=6729603658291 off=235680520 processed=6730092000000 cpu_processed=6730088000000 0: 6730088000000
Jim wrote: FC12-x86_64/KDE
trying to connect to a NXserver across internet, it won't connect.I'm getting to this point at "time out"
203 NXSSH running with pid:2163
285 Enabling skip of SSH config files
285 Enabling check 0n switch command
285 Setting the preferred NX options
If I do a "ssh tom@76.254.20.238" I can connect to Server and tom /home. In ~/.nx the only two directories there is Config and Temp and in Temp there is three files , numbered 3112 6900 6903.
6900, 6903 can be read by user
3112 can only be read by 'ROOT'
Each Runlog is listed below[code].....
How to remove this ever occuring Warning, which appears every time I open a terminal?
* Warning: removing empty lock file
* Error: failed to remove empty lock file
* Error: failed to get the lock: /usr/bin/keychain: 1492: cannot create /home/prashant/.keychain/http://prashant-laptop.promptcloud.com/-lockf: Directory nonexistent
I am having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
[URL]
I upgraded from f13 to f14 and now i get this message after booting up. I am at a loss as to what to do to clear it.
Code:
cat: /proc/self/attr/current: Invalid argument
Welcome to Fedora
Starting udev: udevd[478]: SYSFS{}= will be removed in a future udev version,
[Code].....
After asking on both this forum and the Fedora forum, I felt it was safe enough to install a copy of Fedora on my working-well openSUSE drive. I have a 1 TB drive, partitioned as follows:
I did an install of Fedora 13, was VERY careful to set up the installer to put it's files in the partitions I wanted, although I did let it mark the partition as active, feeling it may have to boot during the installation process.
I had grub installed in the root of the partition rather than the MBR for both systems.
When Fedora finished installing, I rebooted the system only to find that it wouldn't. I got the dreaded "No Boot Device" message.
So, I started the 5 hour process of booting with the parted magic disk, booting with a Gentoo live disk (only one around), monkeying with the install parts of the openSUSE and Fedora disks, swapping drives to Windows to download openSUSE Live CDs (yes, both) and searching the forums and various other web sites for some poor bloke who did the same stupid whatever it was I did, and finally, as I was using fdisk on the Gnome Live CD, I noticed the warning message stating that fdisk would not work on a drive that was partitioned with the GPD format.
Notice that I have 5 partitions? That is not a typo on my part, I used the GPD format when I set it up so I could do what I did without using "imitation" partitions.
When I used parted (the command line editor on the Gnome Live CD) to change the active partition, everything started working again! Well, at least I can boot the openSUSE system, the most important thing.
It is my suspicion that the Fedora install uses fdisk to do it's work, and fdisk just mucks up a GPD formatted disk. Not the information, just the part of the drive that holds the partition table. Perhaps just the flags section. I don't know enough to say with any certainty.
I didn't change the drives parameters during the installation of Fedora, so I don't know of it even offers the GPD partitioning option. If not, I can understand how this sort of thing could happen.
Still....So now all I have to do is make the grub menu, the one installed with openSUSE, boot the Fedora installation on the next partition. Seems simple enough.