When 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 RepliesI'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.
The desktop stops working, the panel stops working.. but compositing, desktop cube etc all work fine.I can still launch a program with Alt-F2.When I try and kill it (to restart) using 'killall plasma' / 'kill -9 <pid> / 'kill -15 pid' from a terminal, nothing happens, the process keeps running. If I leave it for about 30 mins it suddenly dies, allowing me to run 'plasma' from a terminal - then everything is back to normal.
If I log out and try to log back in again, I get a black screen. Only way to fix it is either to kill it and wait for 30 mins or so, or totally reboot the computer.Tail of the xsessions error file:
Code:
[/usr/bin/nepomukservicestub] Removing connection
[/usr/bin/nepomukservicestub] Removing connection
[/usr/bin/nepomukservicestub] CLuceneIndex::close in thread 3086616432[code]....
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 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?
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
Sometimes I get this weird thing where typing a name into the kickoff menu hangs after a few letters. It hangs the entire computer! Once it happens, I try to close it but have to wait about 20 seconds before I can do anything on the computer. Then everything else works fine (after it's closed). But if I go back to kickoff and try again, it does the same thing! I can't seem to find anything in "top" to indicate what's happening.
openSUSE 11.2
KDE 4.3.4
Linux 2.6.31.8-0.1-default i686
AMD Sempron(tm) Processor 3100+ 1.8 GHZ
nVIDIA G98 GForce 8400 GS with nvidia driver
Total memory (RAM): 1.4 GiB
Free memory: 541.6 MiB (+ 506.1 MiB Caches)
Free swap: 2.0 GiB
Here's "top" during a recent issue where konqueror wasn't opening to show sysinfo and there was some hanging (although this was after it came back from kickoff hanging) code...
My system hangs at boot time when loading hardware drivers for about a minute. It hangs here:
Code: dmesg
[ 8.196035] udevd version 124 started
[ 8.533233] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[code]....
My system hangs at boot time when loading hardware drivers for about a minute. dmesg
Code:
[ 11.865604] iTCO_vendor_support: vendor-support=0
[ 11.888580] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[code]....
My ISP offers the service of native IPv6. So my ADSL router provides me with a local and global IPv6 address. However after a reboot it takes minutes to finally see the global address when using "ifconfog eth0". During that time I can't do a ping6 to an external server, which seems logical. So I waited several minutes, but no global address. After that I started a KDE session, went back to the console(<Ctrl>+<Alt>+F1) and now the global address was there. Is this normal behavior or should I file bug report?
View 6 Replies View RelatedIt takes me a while to log in the splash screen just sits there for ages before i get to the desktop. Never used to be this slow and I'm not sure why. Firstly, I'm running Ubuntu 11.04, standard DE. I do have conky starting up in a script but it has the & at the end of the line so I didn't think this would cause it (or is there some special case for log in time on how & is treated?). However as a test I will comment out the line in the script and see if it is the cause.
However just for general knowledge and in case that isn't the problem, how does one go seeing what is happening during the time from when one log's in and the desktop is displayed? Is there some kind of log that shows the date/time that can be enabled or is there a debug mode that can be enabled somehow via special keys or maybe from grub?
Ever since the kernel update to 2.6.34.6-47.fc13.x86_64, my boot process hangs at about startx time. I boot cleanly at runlevel 3 in either this or the previous 2.6.33.8 kernel. If I execute startx from here (in either kernel), the system hangs at the same place. During the early troubleshooting, I read in another thread (250929) about installing xorg-x11-drv-catalyst, which I did using yum. This led to the failure of the 2.6.33 kernel; yum remove did not fix this. I have carefully followed the instructions in the fglrx HOWTO (updated a week ago by Hlingler) as they relate to a PAE kernel (including reinstalling mesa-libGL), and that fixed earlier difficulties. Hence, I felt I needed a new thread.
dmesg tells me
Code:
microcode: CPU0: patch_level=0x2000032
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
Linux video capture interface: v2.00
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
microcode: CPU1: patch_level=0x2000032
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: Microcode Update Driver: v2.00 .....
But the program itself reports
Code:
# microcode_ctl -h
This program is for updating the microcode on Intel processors belonging to the IA32 family - PentiumPro upwards (x86-64 included). It depends on the Linux kernel driver. The website urbanmyth.org/microcode (mentioned by yum info microcode_ctl) clearly indicates that Intel has taken over this microcodecode distribution, and suggests that it is no longer valid for AMD processors.
I found a reference to a kernel configuration flag CONFIG_MICROCODE_AMD (as a plausible subsititute for CONFIG_MICROCODE_INTEL) that possibly belongs in a script in /etc/init.d - but the above context leads me to suspect this is not true any more. In any event, those flags are not mentioned anywhere in my init.d scripts - in fact nowhere in the entire /etc tree. My microcode file exists, and is dated March 23. How do I get it installed? Or is this completely unrelated to my hanging boot problem, as suggested by the "platform microcode" line in the dmesg output? If so, where should I be looking?
Just making one last tweak with my fresh install of F12KDE. I need to . How do I do this
View 2 Replies View RelatedI made a fresh installation of Debian.
Code: Select all[VOSTRO200@root]#uname --all
Linux VOSTRO200 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
I changed to the kde desktop environment. I logged in as a normal user, and left the computer running for a few hours. when I came back the screen was turned off and the system does not respond to mouse movement, pressing the keyboard, or any combination thereof. I tried
Code: Select allCtr+Alt+F1,
CapsLock
First time i touched keyboard the led of numlock turned off, and never back. Blanking the screen itself does not cause a system crash, this occurs after several hours of inactivity.
.xsession-errors
Code: Select all/etc/gdm3/Xsession: Beginning session setup...
localuser:bartek being added to access control list
openConnection: connect: Nie ma takiego pliku ani katalogu
cannot connect to brltty at :0
Failed to connect to the VirtualBox kernel service
[Code] ....
After I installed a new hard drive, when I booted up into Ubuntu, it would give me this error: "failed command: WRITE DMA". So I tried the workarounds and I guess it just covered the log with the Boot Splash, now it's taking a long time just to boot up.
View 9 Replies View RelatedMy hard drive all of a sudden starts to read and write all on its own for around 15 seconds at a time while at idle or while I am just browsing the net. At first I thought it was from cron running but I have that disabled.
View 3 Replies View RelatedI have an Acer Aspire 1810TZ laptop with Windows 7 on it. I decided to dual boot w/ Ubuntu 10.04 32-bit Lucid Lynx. I was initially getting this issue
Code:
gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
[code]....
I started out with Kubuntu RC, then installed ubuntu-desktop and updated all the way to the current state of packages.Anyway, from the moment I installed the RC, from time to time the boot splash appears, the dots light up/turn off and then the booting hags. No key seems to work.I the do a hard reset and everything works just fine.As not to open another thread:- how can I see the Ubuntu splash screen? (currently I can see the Kubuntu one)- how can I turn the splash off and have it boot in text mode?
View 3 Replies View RelatedSince recently statd at the boot time takes, more then 30s or even more.
It is laptop configuration, no NFS server(?) lenny with few installs from backports (open office and .30 kernel - for Intel 5300) vmwware (7), as well firestarter firewall
Can I disable it or change the boot order (via sysv-rc-conf ), so I can speed up my boot time?
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
View 1 Replies View RelatedI recently broke down in the face of morbid curiosity and clicked that little version update button. it seems to run flawlessly (after i uninstalled the pesky touchpad) but it takes a long time to boot up now. at least a full minute. is this normal?
I will add also that it said my version of grub had been modified (which i dont remember doing, but may have) so i told it to leave the current one in place.
I am using Ubuntu 9.10. Every time I try to reboot my system it hangs. Shutdowns work properly. I've done multiple re-installations. Nothing I've tried fixes the problem. Does anyone have any suggestions?
View 4 Replies View RelatedI am trying to install rhythmbox-0.13.1.tar.gz in my fedora 10 for a long time but i am in vain I downloaded it and i put it in my desktop.Then i did this:
# cd ~/Desktop
# tar -zxvf rhythmbox-0.13.1.tar.gz
Doing this a new folder named tar -zxvf rhythmbox-0.13.1 is created in my desktop.
then i did this:
# cd rhythmbox-0.13.1
[Code]...
I am using Fedora 15 KDE 32-bit. I am facing a problem while shutdown. It takes unusually long to shut down. It reaches the blue screen with the fedora logo within a few seconds, but it stays on the blue logo screen for 2-3 minutes before shutting down. However, I am facing no problems during startup.
About suspending F15 KDE. It goes into suspend successfully but after switching on after suspend, it just shows an unresponsive black screen.
Is anyone else facing the same problem and has it been solved before? Because I haven't come across many posts regarding F15 KDE.
I want to try the new 11.1. When I start the installation (x86_64 DVD), the startup is hanging. The last message is "Starting udev...". Keyboard is completely frozen, only reset button is working. Mobo is an Intel DG965WH with 4GB RAM and ATI Graphic card (ASUS1950pro). My opensuse 11.0 runs without any problems.
View 9 Replies View RelatedI 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 wanted to know how can I make my programs or script automatically start at boot time ,for example if I restart my server at any time they start at boot time automatically with no need to any body to start them.
View 2 Replies View RelatedHow to stop starting daemons at boot time? For example:rc.bluetooth
View 3 Replies View RelatedI have a SSH box which is command line only and no X, this will be used remote and i'm trying to get the wireless network configured to start at boot. I'm using wpa_supplicant as the access point is secure with WPA2 At present if I send the following commands the machine will connect to the wifi and be reachable via ssh
ifup wlan0
/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -dd -i wlan0 -B
dhclient wlan0
This does not start at boot but requires manual input of the above commands. I've just come to a complete blank on geting this to start at boot time. Also I would like to set a fixed IP for this box.
I've got the last Debian stable release, the amd64-DVD-1 file , and copy it to my USB stick, using win32diskimager, as recommended in the installation guide.
It seems to go all fine, but when I rebooted, after entering the passphase it started a fsck "from util-linux 2.25.2", then it says:
"/dev/mapper/Debian-root: clean" and stuck there. i gave it quite a bit of time, tried to reinstall it and also got into the rescue mode of the installer,