I recently updated my fc12. before the update all was well but now it takes very long to boot. when i checked the text output by pressing F3 it stops at "Applying Intel CPU microcode update".
View 1 RepliesI have a few XenServer VMs all running CentOS 5.5. Some are 32-bit and others are 64-bit.
Every time they boot, the following message appears:
Applying Intel CPU microcode update: [FAILED]
Does anyone know why this is happening and how I can fix it?
I installed fedora 14 on my Dell studio xps 1645 with CPU intel i7 core inside.
I downloaded the microcode.dat file from the intel website to update the revision of the CPU.
I tried to put it in /etc/ but no update was done. also in /etc/firmware (after creating the latter directory), and no update was done. also in /lib/firmware (after renaming the current microcode.dat file) and no update was done.
Because the version of the microcode installed by the package intel-microcode in Testing (2009-03-30) is way older than the one currently offered by Intel (2010-02-09), I only installed the package microcode.ctl and let it fetch the microcode. However, after reading the Read Me files, manual pages and system logs, and checking the directory where the microcode is stored, I have not been able to find an option to check the version of the microcode in use.
This is the output of update-intel-microcode:
Local version:
Remote version:
could not extract the actual data of remote microcode
I just installed Fedora on my desktop (previously Ubuntu)
The root and boot partitions are on a OCZ RevoDrive, which is seen as 2 separate drives and used software raid0 for speed.
Here is a link to my bootchart, which shows a 17sec delay before anything starts.
[url]
md0 and md1 are on the RevoDrive, the boot is a raid1 partition (as i was unable to boot from a raid0 partition) and the root partition is a raid 0 partition
Code:
Any one know away to get rid of the delay at the start of the boot chart?
Last Saturday, I ran an update on my laptop using F12 and received a new kernel. As of this morning, the new kernel hasn't shown up on my desktop, using f 11. (Yes, I check every day.) Currently, my uptime is 34 days, so you can see how long it's been since the last kernel update for F11. Does anybody know why there'd be an update for one version and not for another? In case anybody's wondering:
[joe@khorlia ~]$ uname -r
2.6.30.10-105.2.23.fc11.i586
After applying an update about two or three days ago, I restarted my system and now I'm getting a black screen at login. I can hear the brief drum sound clip that plays when the login dialog box pops up, but the screen is completely black and I can't see anything. I'm still able to access low graphics mode via the fail-safe option in the recovery mode menu. So far I've tried the following commands in the terminal:
Code:
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
sudo apt-get install xserver-xorg-video-ati
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-
core[code]....
get the delay from booting into gnome to actually getting up your desktop? Mine seems to boot, come to a purple background with a pointer, then after a while of waiting the panels and my actual background loads. Just wandering if anyone else gets the same. Edit > Happens regardless of what drivers i use for graphics so it's not an issue of open/closed drivers.
View 5 Replies View RelatedOn startup I get the following message:
Code:
Applying Intel CPU microcode update: FATAL: Module microcode not found. OK
ERROR: Module microcode does not exist in /proc/modules
Selfmade Kernel:
Code:
[toby@sarah ~]$ cd /usr/src/kernels/linux
[toby@sarah linux]$ cat .config | grep -i microcode
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
Code:
[toby@sarah linux]$ rpm -qa | grep -i microcode
microcode_ctl-1.17-1.53.fc12.1.x86_64
I found few links, saying that this is a Xen problem but I have no Xen.
Both F15 KDE Live CD and DVD new installs fail on HP 2133 mini notebook. The device has previously accepted F12 installation without a problem. The HP 2133 has a VIA C7 processor. Is this CPU is no longer compatible with Fedora? The syslog repeats endlessly 'microcode: no support for this CPU vendor'. The Live CD will not even begin the install to diskl. The DVD will install but will fail on reboot with the microcode error. How to overcome this installation problem?. Is there a kernel upgrade or microcode update that has already resolved this and how can it be installed?
View 1 Replies View RelatedYesterday I applied the su security patch to my openSuSE 11.2 x86_64 system.After applying the patch, any attempt at su failed, and after rebooting the system earlier this morning any login (root, user, otherwise) fails with a "Permission Denied".Is it possible that the su update somehow messed up my (standard) pam settings?
View 10 Replies View RelatedMy self-built PC had a BT wireless adaptor in it which worked, albeit after a bit of a faff, with Ubuntu 10.10 in connecting to my BT HomeHub2.
When I came to use it last week it would not connect. I'd not changed any hardware but I had been applying regular updates via Update Manager.
Bearing in mind the "faff" factor, I decided to try a different (Edimax) wireless card but got the same result. Upgrading to 11.04 has made no difference either.
It does *try* to connect but fails, so I think the card is installed correctly. I've also tried a full reset on the HomeHub and the setup works fine with W7.
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?
I have Fedora 11. After my most recent update, I can't log in. Every time I authenticate, the logon window disappears, the screen goes black briefly, and then I am back at the log in window I entirely reinstalled, and then it worked, until I updated to the newest kernel then it didn't work anymore. Update: I now generated a xorg.conf with system-config-display --noui I manually removed and reinstalled xorg-x11-drv-intel with yum. It didn't work. By the way: now the start hangs on "Starting atd: OK" If I specify "vesa" in xorg.conf, then it gets past the point, but display doesn't load properly.
View 14 Replies View RelatedHappening right now on a Fedora XII 64 Bit:The latest Fedora kernel update (from today, 2009/12/01 - coming from fedora updates [not update-testing]) destroys my Intel GM45 (= i915 kernel driver) so much that I
1. Have no plymouth dooring booting (just this blue textmode lines on the bottom)
2. Have a completley black KDE screen (only my colorshaded windows shadows appear, if I rightclick into the darkness - with no contents) - that's however a composite effect which strangely enough works (Alt f2 reveals for the 10th of a second the "start application"-window and vanishes)
3. If I change to a tty console (eg.via CTRL ALT F5), in 3 of 5 tries the screen does not manage to change to the new video mode and flickers insanely (switching back betwwen CTRL ALT F1 [x-server] and CTRL ALT F5 [tty] a couple of times helps) which tells me that...
- at least KMS is gone.
- 3D-Compositing is completly messed up resulting in a unusable complete black GUI
However, beside this
4. the KDM login screen appears in its full beauty and so does the "KDE loading" thing. Going back to kernel 2.6.31.5 makes any of this disappear and working nicely (I defaulted this in grub now). The computer is a lenovo thinkpad SL500 (cheap intel dualcore 64Bit CPU) with intel GMA4500 chipgraphics (if its not something with my linux configuration it should affect other similar notebook types too).
I really use fedora on my notebook (right now with kernel 2.6.31.5). My desktop uses a radeon HD 4870 - big bad luck with fedora 12: The radeon driver is not able to show KDE windows the right way (looks really really bad - even with those "experimental" Mesa settings-trick) and the unfree AMD driver does not work under fedoras high X Server version (which may be better this way! ) . So I end up using windows on it, waiting for a decent radeon driver to kickstart a decent 64bit linux (fedora still being first choice as the right compromise between cutting edge and usability)...
I don't know if it's just my system, but after applying the latest Wine update, the mouse cursor in Wine windows is now purple/magenta/pink, whatever. Not a big problem, just annoying. I've looked through the various config files in ~home and /usr/share/wine, and can't find any parameter that might even remotely address this.
View 4 Replies View Relatedi just installed fedora 13(fresh install) everything worked fine so i wanted to install the nvidia drivers (using akmod) everything went fine so i rebooted it. It started fine showing everything as[ OK ]But after showingEnabling monthly Smolt checkin: [ OK ]Starting atd: [ OK ]It stops rigth there...I dont know why, i just can reboot and cant go any furtherThe next one must be service local, but cant get it started
View 3 Replies View RelatedAfter GRUB 2 comes up (I'm running Ubuntu 10.10) and I choose the OS to boot, there is about a 5 second delay where nothing appears to happen after I make the selection -- no disk activity. It happens consistently every time I boot. Again, this is after I choose the OS to boot, so it shouldn't have anything to do with the standard delay to allow me to choose the appropriate OS.Is there a good way to troubleshoot this and determine what is causing the delay?
View 4 Replies View RelatedThis morning I did an update on a current F13 system with NVIDIA Graphics card. System gets to a complete white bar across the screen followed by "FEDORA 13" . This all starts blinking and goes no further.
View 7 Replies View RelatedAfter applying some updates to F11, I was unable to login. After putting the username and password in, the dialog would go away and it would appear that the window manager was trying to load. Somewhere in the process the mouse and keyboard stops responding. The HD activity lights flashes for quite a while but later goes out.
Hoping that F12 would help, I upgraded. The upgrade went well but the problem still exists.
I am wondering, what is the status of Intel GMA X4500 driver on Fedora 10.
View 2 Replies View RelatedVLC was behaving weirdly recently and when I've tried to run it with primusrun command (since I have optimus card) it gave me a segmentation fault
Code: Select allVLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42)
Segmentation fault
I've read on google that issue has been solved by a few people from updating the microcode, but I don't even understand what microcode is, I'm also not sure whether I should install amd64 or intel package for it?
Here is my lscpu
Code: Select all$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
[Code] ....
if an admin decides this is security feel free to move, at the moment I can't decide where so posted here...On my laptop (msi-u100) my bluetooth stack creates rfcomm0 but is not applying the correct context label to it so selinux is bitching.
View 2 Replies View RelatedTechnically it is a Realtek chipset I believe. Worked fine under 11.2. In the old days would just run alsaconf but I'm sure that is passe' by now.
View 9 Replies View RelatedNot sure if this is hardware or software so I am raising the question here. I have an Ithaca 280 printer that worked great on fedora 8 with cups 1.3.3. When I upgraded my server and installed Fedora 12 with cups 1.4.2 i noticed a 5 second delay between sending a print job to the printer and it actually printing. This issue doesnt happen with laser printers, just the ithaca thermal printer. I have tested this with 10 other ithaca 280 printers and all of them have the same result. I am using a raw driver, and it is an IP based printer setup for Jetdirect in cups. The setup is identical on a Fedora 8 server as it is on this Fedora 12 server. I have even taken the steps to upgrade to cups 1.4.4 just to see if it was corrected in a newer version, but the issue is still there. I have a utility that writes the raw text directly to the printer which i used to test that it wasnt an issue with the printer or its internal print server. That utility allows the document to print immediately.
what is causing this delay and how to correct it? If not, does anyone know how to print directly to the printer using cups instead of letting it go to the queue first like cups normally does for print jobs?
I have been connecting to ssh but now it takes longer time to prompt for username and also password.Can any one tell what is the reason why it takes time
View 3 Replies View RelatedI should install a new openSuse 11.2 or if I should make an Update-Installation from DVD (see openSUSE 11.2 Installation Quick Start Installation Mode: Select Mode - New Installation / Update / [...]) or an Update Installation via Yast.Now I am using openSuse 11.1 and Gnome 2.24.1 (mostly, 1 account is using KDE) and Kernel Linux 2.6.27.45-01.1-pae. "/home" is on an separated partition (as part of an extended partition).
Contra new installation?:
- I have an Laptop (Samsung x20) with integrated intel 915 graphic and an very hight resolution (1400x1050). The monitor's resolution is not listed in the bios of the graphic cart/solution. Because of that I had many problems with my fist installation of suse/openSuse linux.
- Will I have problems to keep my old accounts?
Pro new installation?:
- Sometimes funny system reports (mostly about ICE).
- I have been logged in as root in Gnome (as I had some problems with (no) audio, the digital optical audio out is still not running).
- I think the fist installation was a few years ago maybe I had been to often "bold".
IPtables creates an error during startup as well as when I try to restart it: Here's the output of:
[Code]....
I am in a situation to boot fedora 15 live cd in to command line mode, not graphical mode, for some testing purpose. how to change argument during booting mode
View 4 Replies View Relatedi'm using Fedora 11 which i installed a couple of days back... i added my user name to the sudoer list but everytime i run the sudo command it takes at least 20 + seconds before anything happens... this happens everytime i run sudo... in comparison to running su things happen immediately... anyone else experiencing this? now everytime i install or run a command requiring root access i just use su...
View 7 Replies View Related