The only error message I am able to retrieve is in the GDM 0.log as follows:
AUDIT: Sat Mar 7 17:58:27 2009: 5034 X: client 9 rejected from local host ( uid=500 gid=500 pid=5066 )
I just recently notice that my Fedora 13 is randomly stop at boot. This is a fresh install less than a week and with all the updated kernel and software as of today. I could not get much information from /var/log/messages (only about 3 lines at the time it froze).
It froze straight after it finishes the boot sequence. I can see a mouse cursor but that's about it. The last init sequence I could see before going to X was "atd" (if that helps at all)
This install is on a single Seagate 1.5TB drive without any other drives attached to the system (I rule out if that's problem with the other hard drives)
on Gigabyte P35DS3 mobo on ICH9 port
the mobo has AHCI mode for the hard drive
I got some bad sector on the hard drive (40 sectors)
For some reason, it kept stopping when I cold boot. Once it stop and I press the reset button it normally works.
I found another forum mentioning it can be issue with the video driver. So I here's further information of my system code...
My F-14 x64 bootup stalls with this message: "K10 temp ... unreliable CPU thermal sensor: monitoring disabled". I'm unable to find an explanation/basis for this message. I can boot from CD#1 and chroot onto the disk - near as I can tell, all the data is there. Might this be the result of a corrupt boot up sequence file and, if so, which one(s)?
View 3 Replies View RelatedI am seeing this in my dmesg ouput:
Code:
compiz[3329]: segfault at 3d9786e288 ip 0000003d93c3a4b2 sp 00007fff332d0f10 error 4 in libglib-2.0.so.0.1800.4[3d93c00000+e0000]
I have an nVidia Quadro FX 570M card and I am using nVidia's 177.82 drivers:
Code:
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 177.82 Tue Nov 4 16:50:05 PST 2008 I believe error 4 is "Interrupted system call".
I just installed 2.6.35.12-88.fc14.x86_64 via Software Update and rebooted. When selecting new kernel to boot from, the boot sequence doesn't finish. I am not sure how t o troubleshoot; I am prompted for the PassWord for encrypted /home, but after that, it freezes.
View 8 Replies View RelatedI have a fresh installation from the demo ISO image of F14 running on an Acer TravelMate 4200. The system is a Dual Boot with win Vista. Windows Vista runs without any problems but when using F14 a kernal crash constantly occurs and it then hard freezes or hangs and the machine needs to be cold booted. There is nothing in particular that I am doing either, the problem happens when the machine is idol or when I am working in various apps.
The F14 system is completely up to date running kernel version 2.6.35.13-91.fc14.i686. The following error below is from the automatic bug reporting tool and I have reported this using the tool:
Package: kernel
Latest Crash:Sat 04 Jun 2011 14:55:00
Command: not_applicable
Reason: BUG: unable to handle kernel NULL pointer dereference at 000000f8
Comment: None
Bug Reports:
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
it happened first after upgrading about a week (|| more) ago. i thought that it's just em.. kinda normal (i'm running debian unstable, so such things are happening often).
but now it became a problem: i've tried reinstalling nvidia's drivers and compiz itself. no effect. also, i can't catch any errors in logs.
Is there an easy way to upgrade kernel to 2.6.38?
Or do i have to compile a custom kernel?
After kernel branch update some times ago i found compiz very slowly, but with older branch compiz was not such slow as today.
Here is my uname:
Quote:
I downloaded 64-bit version of Fedora 11 and burned the iso on my dvd. When I rebooted the machine it booted up from the dvd but it showed an error message that kernel "image not found". And it stops there itself. Can someone show me some way except downloading the iso again?
View 1 Replies View RelatedI am running fedora 12, x64. How can I upgrade fed12 as such? (apart from compiling the kernel myself)
View 3 Replies View RelatedGoogle answers attempted:
# grep lm /proc/cpuinfo
# uname -m
# file /sbin/init
# file /usr/bin/file
I don't think none of the above gives deterministic answer. Since I have 32-bit & 64-bit different system all of above spit out the same info.
I upgraded my F13 kernel from 2.6.33 to 2.6.34. But, the newer kernel isn't booting. It starts the booting process and then goes idle. how shall I troubleshoot?
View 2 Replies View RelatedI've managed to get some sound through the system with kernel 2.6.40.1. I use multiple sound cards, I have problems with keeping the same order. I added in etc/modprobe.conf The list of sound devices, putting my D66 card as device 3, Rebooted and cat /proc/asound/cards showed all fore devices in the correct order. I got audio through one of the apps , and started to try and get another ,wsjt, to function.
[Code]....
I have been running F14 as a 32-bit system (original m/b was 32-bit). Now the system is on a 64-bit dual-core processor board and I'd like to change from the 32-bit kernel to 64-bit. I downloaded a 64-bit kernel (kernel-2.6.35.6-45.fc14.86_64.rpm) and attempted to install it. It won't install and Package Installer returns a message of the sort that says this file "has incompatible architecture.
Valid architectures are ['athlon', 'i686', 'i586', 'i486'....]". My processor is an Athlon 64 x2. Is it possible to do what I want to do (I only want the kernel at the moment)? Is there some Fedora file I need to modify to allow the system to install the 64-bit kernel for this m/b? Do I need another file (or files) installed before I install the kernel?
I had fedora 12 installed on a Macbook pro Intel first generation with ATI Radeon graphics card (see the attachment). Compiz crash when trying to watch *.wmv movie codified with wmvvc1dmo on kernel-PAE-2.6.32.9-67.fc12.i686. I want to convert the film to *.mpg, then I download the mplayer codecs in order to see the film, I can do it without problems with the on kernel-PAE-2.6.31.12-174.2.22.fc12.i686. But I updated my system last Saturday and when I was trying to see the movie again the computer began to respond really slow, then I began to close applications and when I tried to restart I got the message: "compiz is not responding".
I tried again but the same problem. Other thing that I noticed is that when the computer go to sleep, when I wake up it, the display show horizontal black spikes, it is like it doesn't have the appropriate refreshing rate. I think that the problem is related with the acceleration on graphic card. Yesterday, I booted on kernel-PAE-2.6.31.12-174.2.22.fc12.i686, and I watched the film, and the wake up was without problems. That is the reason I call it a regression.
[Code]...
I have a new work laptop (Dell M6400) that I currently have F10 i386 on. I would like to take advantage to the 64bit processor, but don't know if I need to completely re-install my F10, or if I just have to add the proper 64 bit kernel and applications.
View 4 Replies View RelatedIve loaded 64studio (hda6) grub in MBR, and fed10 grub on its partition (hda8), but from Studio it seems i cant Mount fed10 files to look at the Kernel path from MBR. (studio did not auto pick it up, like it did for Mandriva on hda7)
Does anyone know what it is ? something like kernel /boot/vmlinuz.....and Initrd(hd0,7)/boot.initrd.img .....then i can Edit menu.Lst in MBR grub.
I am running a vmware on a 64 bit fedora 9. I have already installed kernel header, but the vmware could not find the kernel header, and ask to input the kernel header path. I added /usr/include to the vmware, it complained not a right kernel header.
View 1 Replies View RelatedThe -162 kernel upgrade just released failed to boot in my x86-64 system. Additionally, both previous kernels failed in (probably) the same way. The progress icon proceeded all the way to its 'f' image, and then hung. I touched escape key, and found several disturbing messages among a dozen or so lines --
mdadm: No arrays found in config file or automatically. A dynamic linking error occurred: /lib64/multipath/libcheckdirectio.so: no such file or directory awk: cmd. line:1: fatal: cannot open file `/etc/inittab` for reading (Invalid Argument). Init: rcS post-stop process (807) terminated with status 2s. I got into rescue mode with my install disk, then looked for libcheckdirectio.so in /mnt/sysimage/lib64 but it was not there. Also, locate -d /mnt/sysimage/mlocate/mlocate.db/libcheckdirectio.so found nothing.
Ran chroot and executed the fakd diagnostic (which I had not seen before) and rebooted. Same problem - although now the screen is telling me SELinux is requiring a targeted policy relabel. My dual-boot-to-vista system has been erratic (requiring fsck several times, and confounding the Vista partition to require file checks), primarily since a large install of Eclipse and multiple plug-ins AFAICR.
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code:
make gconfig
make -j4 all (or make all)
make modules_all
make install
The last command edits my grub.conf file and writes this:
[Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
there is no sound in Fedora14 after kernel update (kernel-2.6.35.11-83.fc14). when use kernel-2.6.35.10-74.fc14 , I can listen to music.
View 14 Replies View RelatedMy main systems runs Fedora 14 x64 with the latest updates (I can't check anymore, but I believe it has the .13.91 x64 kernel). Since this afternoon it became unsuable. First, Opera Browser crashed and the crash report app of the browser showed up. Clicking one of the options there resulted to X crash, if I understood what really went on. No input, mouse or kb, I couldn't go to tty etc. I had to do a hard reset. Next boot proceeded normally up to the point that GNOME desktop is fully loaded. ABRT began reporting numerous kernel oops.
Rebooted again (noticed that init.d fails, so hard reset again) and tried past two kernel versions, same results.
Yum crashes and so does everything. I tried to revert all recent updates with yum history, but yum crashed.
Last update was May 22, and it updated kmod-nvidia.
Quote:
uname -a
Linux innovator 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
initial crash
Package: kernel
[code]...
before the reboot Opera 11.11 had crashed and it's own bug report tool came up. Clicking the "do not report this error now" option probably crashed X, because the screen went black and no input was possible (no mouse or keybord, so I couldn't go to tty either. Had to do a hard reset) Bug Reports:Kernel oops report was uploaded
One of the numerous crashes
Package: kernel
Latest Crash:Τρι 24 Μάι 2011 09:19:56 μμ
[code]...
In an attempt to ameliorate some other problems (lm_sensors, and loopback), and based on several forum entries, I decided to update the default f15 kernel (2.6.38.35) using kernel-2.6.39-1.fc16.x86_64.rpm from rawhide. It seemed to install without problems and when I rebooted it seemed to hang just before completing the boot process. The on screen boot messages ended with:
Started Display Manager
Started LSB: daemon for libvirt ........
Starting LSB: suspend/resume libvirt guests on shutdown/boot
[ 12 ......
about a dozen similar lines ending with
[25.030991 hci_cmd_timer: hci0 command tx timeout
then it apparently hangs
However, at that point I can log into to a console using Cntl-Alt-f2, so most, if not all, the crucial boot processes seem to have completed. There is an issue with the nVidia driver that I will deal with by modifying /boot/grub/grub.conf to re-enable nouveau, but I am stumped by what is causing the hang up. There is a certain amount of traffic regarding a similar problem with Ubuntu 11.04, but no solution other than it seems to be related to a BIOS bug (NFI)
what sub-system uses the "hci_cmd_timer" and why it might interfere with the boot process? Has anyone else run into a similar problem with f15?
Is there a better way to get an updated kernel in f15? I do want to keep all the Red Hat patches and back ports, so reluctant to build a kernel from scratch from upstream sources at kernel.org (and maybe just a bit apprehensive ;-})
Keep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
I'm currently using FC 9 - 2.6.27 x86_64. (In my Hp - nx6320 laptop with- Intel centrino Duo processor). I have downloaded linux-2.6.30.2. How do I install this with i386/i686 configuration set. All that I want is a 32 bit - linux-2.6.30, because NCTUns 5.0 works only with the 32-bit kernel. I have tried following:
Code:
make ARCH=i386 menuconfig
After this, I see the architecture set to "X86_32 = Y" in the .config file. But later, after I run
Code:
make bzImage
The configuration restarts asking to select Y/N for various packages and modules. I have no much idea on what to select and what not to, in order to retain X86_32 set. I end up with the new .config file with contents as below after the make bzImage command.
Code:
#X86_32 is not set
X86_64 = y
Again it is going to be built as a X86_64 bit kernel.
How to install the kernel as 32-bit along with the existing FC-9 64 bit kernel.