The 'message' gets an unending stream of errors code...
The offending kernel: Fedora (2.6.32.9-67.fc12.i686.PAE)
I am running the previous kernel with no problems.
When I run the new kernel after a short while networking quits and/or the xserver locks up...
My GMA500 (poulsbo) driver is not working any more because of the latest update I made using Software Update.
The update was a new kernel:
[omass@omass ~]$ uname -a
Linux omass 2.6.30.10-105.fc11.i586 #1 SMP Thu Dec 24 16:26:26 UTC 2009 i686 i686 i386 GNU/Linux
Now, after this update, when I reboot I get the following error code...
A yum update got interrupted - I cleaned it up, reran yum update - everything appeared okay but now system won't boot
kenel panic - not syncing VFS :unable to mount root fs on unknown-block(0,0)
any hope to repair this or must I reinstall linux ?
I just updated my kernel to 2.6.34.7-56.fc13.x86_64 last night and now I have no system sounds. Audacious plays my mp3's just fine, just as all my multimedia works in my web browser, vlc, etc... The only thing being affected is system sounds. I tried playing a sample with aplay and I got loud, crackling nonsense and this output code...
View 4 Replies View RelatedI installed Natty on a second partition yesterday to try it out, but i can't get wireless to work. Hardwire connection works fine, so does connecting wirelessly to my router. However, i cannot browse the internet or update. After rebooting a couple of times i was surprised to see internet working, but only for about half an hour. Then it stopped working again. My card is a Intel PRO/Wireless 4965AGN and i'm using the 64 bit version of 11.04.
So my question is if anyone has had the same kind of problem or maybe knows a fix?
I'm really disappointed cause Ubuntu worked out of the box for me since Hardy.
My fedora 12 laptop will no longer boot properly. i get my bios screen, then the fedora intro screen (with the f / infinity symbol on a blue background) after a brief blank screen, then i get a blank screen with a blinking cursor. i can type things but nothing happens when i do, and the computer never exits out of that screen.
is there anything i can do to correct this problem short of a reinstall? i really hate to lose some of the drivers i went to a lot of trouble to find and install as well as some software and some user files.
p.s.: the last thing i did before the problem was to use yum to install quite a few fonts (xorg-...) but it ran after that and i think even went through one reboot with no problems.
At some point in the last week, my webcam on 10.10 64bit mysteriously stopped working. The OS no longer recognises it as being there. It's an internal cam on a Clevo laptop and before this it's always worked perfectly.
Is there a way I can force the OS to recognise it? Or find out what broke it and fix it?
Just a heads up to others. There is a kernel regression in the 2.6.35 kernel with regard to, some but not all Intel Gigabit ethernet adapters using the e1000e driver. After an otherwise successful upgrade from fedora 13 to 14, no ethernet connection could be made while using the upgraded 2.6.35 kernel that comes with fedora 14. The 2.6.34 fedora 13 kernels work fine and were fortunately still available after the upgrade.
I have personally seen the identical malfunction on all 2.6.35 kernels I've tried with both Arch and Aptosid and have seen similar reported problems on the Gentoo forum. In each case, going back to a 2.6.34 or upgrading to a 2.6.36 kernel solved the problem so this is almost certainly a kernel issue. My onboard Intel Gigabit ethernet adapter is:
$ lspci -vv | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
I believe the intel ICH8 chipset motherboards are the ones primarily effected.
I beleive I had version 9.x installed. I upgraded once and everything was fine. I went the upgrade manager again and it found some more upgrades. The upgrade messed with grub. It then told me there were no new upgrades. Then I rebooted and it says
Try (hd0,0): NTFS5
Then the screen clears and there is some text I can't read and then it says command not found. Then it reboots.
Is there a way to fix this?
If not is there a way to recover the files from the disk image file.
I just installed it on my ancient IBM T-42 thinkpad, and am completely satisfied.
However, I want to help fedora get better.
I keep getting notices that there is some sort of kernel crash.
See cut and paste below.
When I try to use the automatic bug reporting, it fails to do it.
I have attached a screenshot of what happens when it doesn't report it.
I am trying to install a piece of software that uses an install.pl script which looks to /usr/src/linux/include/ for my kernel headers...but it never finds them or that directory/link.
I've run "yum install kernel-devel kernel-headers" so I am pretty sure they are installed.
My "rpm -qa | grep kernel" returns code...
What am I missing?
Hello, i recently update the kernel in fedora through the GUI update manager and after restarting the new kernel wouldn't boot and i had to reboot into the old one. it freezes right after Plymouth finishes and the login screen should show up it just completely freezes, i do have proprietary nvidia drivers could it be that?
View 9 Replies View RelatedLast night at 1:47 AM yum installed the current version of kernel-headers on my RHEL5 server:
Mar 17 01:47:47 linux1 yum: Updated: kernel-headers-2.6.18-164.15.1.el5.i386
Mar 17 13:47:22 linux1 syslogd 1.4.1: restart.
This locked the server up until I could physically get to it this afternoon and reboot the server. I then finished downloading and installing the new kernel, rebooted again, and the server appears to be running fine.
This is the second time this has happened on this server.
Has anyone else seen this problem when you setup yum to automatically update your servers? Other than manually updating servers, does anyone have any suggestions on how to keep this problem from happening again?
After updating to kernel-2.6.33.6-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again.
This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
Is it time to get my hammer?
Using hd3200 on a lenovo edge 13.
followed this guide to install catalyst 10.12 and everything went fine and drivers got loaded.
Just updated the kernel to the latest version(2.6.35.10-74.fc14.x86_64) and after the reboot, the screen is just blank.
I wireless network card is Broadcom Corporation BCM431, but is doesn't work after I update kernel from
2.6.29.6-217.2.7 to 2.6.29.6-217.2.8.
Linux localhost.localdomain 2.6.29.6-217.2.7.fc11.x86_64 #1 SMP Fri Aug 14 20:53:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
i upgraded my kernel to the latest version that being linux-image-2.6.31-19 and now when i start my linux box i get the grub shell. this problem happend once before but i only had to run the command: sudo update-grub2 and everything turned back normal. now even though i run the command everytime i restart my linux i get the grub shell.
Firstly my gdesklets have gone, and if I try to run gdesklets then I get a blank window in the top left corner, followed by another blank window in the centre which disappears, then the first one fades to gray.
Secondly, clicking the 'running man' to exit just closes both gnome panels.
Ubuntu 8.04 (2.6.24-25)I know 8.04 is pretty old now, and I should probably start over, but it was all fine until this latest update.
Posting from my Windows 7 system. Once again an Ubuntu kernel update has broken X. Once again I cannot get into Grub2, despite putting in the hacks to lengthen the time it listens. I don't need instructions on how to fix it from Live CD. I'm going to try Gentoo or something, anything, different. I need a Linux distro that can survive regular updates and boot to desktop reliably.
View 1 Replies View RelatedI am running Ubuntu 10.04 and ran the normal weekly updates last night. There were kernal updates listed but they have run alright before so I went ahead and let everything update.
On restart my Nvidia drivers would not load, so I restarted in low graphics mode. I uninstalled the Nvidia driver (with the intent of reinstalling them) but decided to restart before I reinstalled the driver (windows habit). upon restart I was told (in a very small box) that Ubuntu was running in low graphics mode.
I clicked ok and it proceeded to load, but it loaded it in regular mode and only the right half of the desktop is visible! It is like it is cut totally in half! And I can't get to the important side with Admin and Preferences. I tried boot options but that just gets me a very small colored box. There are no options when it boots just 3/4 of a box that says it is running in low graphics mode because "unable to load module "fglrx" module does not exist". I can not try and reinstall the Nvidia drivers because I can't see the part of the desktop that has Admin on it. I have used Ubuntu for several years now but have not used the terminal very often.
I'm running Ultimate Edition 2.4 on an Acer Aspire 3500 lappy, yesterday I allowed my system to upgrade the kernel (from 9.10 kernel 2.6.31-17 to 2.6.31-18 generic) as per usual but when it rebooted I had no WiFi. The network manager didn't even have a wireless section, only wired, and I couldn't setup a wireless network either. If I reboot into the earlier 2.6.31-17 kernel everything is OK.
Another problem is that even tho I have no screensaver enabled and no power saving options enabled, (ie screen never disabled) after a short time of no use the screen goes blank. If within a few minutes I touch the pad or hit a key the screen returns but if it's been an hour or so nothing I do will wake it up,even tho there is still disk activity etc, and the only way to recover is with a hard reset, hold power key to reboot.
Yesterday, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.
Ever since then, my suspend to ram (STR) function is broken.
The machine will suspend normally, but will not resume. When I try to awaken the machine, I can hear the fan in the tower start up (the subject machine is a desktop computer, please see below for specifics), but the machine seems to be otherwise dead (e.g. the monitor stays blank, pressing the "caps lock" key on my keyboard does not activate said keyboard's "caps lock" led, Ctrl-Alt-F[x] has no effect, etc). My only recourse at that point is a hardware reset (ouch!).
I tried running Code: Select allpm-suspend from a terminal, with no joy. Same result running Code: Select allecho -n "mem" > /sys/power/state from a terminal.
I checked the /var/log/pm-suspend.log file and noticed that each Code: Select all...performing suspend line used to (before said kernel upgrade) be directly followed by a Code: Select all...Awake. line, but, now, all said Code: Select all...performing suspend lines are followed by an Code: Select allInitial commandline parameters... line.
Before this, STR has worked well ever since I first loaded Squeeze on this machine back in 2012.
Code: Select allSqueeze 6.0.10; 2.6.32-5-amd64
Intel i7-980 Gulftown CPU
Asus P6X58D Premium Motherboard
EVGA GeForce GTS-450 Graphics Card
G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total)
Crucial RealSSD C300 128GB SSD
Western Digital Caviar Black 1TB HDD
Corsair HX850 PSU
[CODE]
Where's the recovery console in 10.04? Apparently there's no Grub so holding escape to get to a boot menu to boot into a shell isn't an option for me it seems.
I just want a shell so I can remove lm-sensors or whatever package I installed that's made my system unboobatble.
I installed the latest security update for squeeze. It entailed an update of the kernel. Now when it boots, it give continuous kernel error messages about "can't enumerate usb .... " I have a custom kernel compiled from source (not sure about the patch level) from the same kernel 2.6.32. It seems to work OK. Should I worry about the security of this custom kernel or should I try to recompile it? I don't really know how to do any patching of the kernel source.
View 5 Replies View RelatedLatest kernel update on 10.04 desktop broke my bluetooth. The icon in the tray has now faded and pushing 'turn bluetooth on' does absolutely nothing. I'm on a Lenovo S10-2 laptop, everything was working perfectly before today's update.
View 6 Replies View RelatedI just updated my kernel from 2.6.32-21 to 2.6.32-22 today. Now I am getting no sound. I have checked my mixer levels with both kmix and alsamixer. Nothing appears to be amiss. I tried rebooting with the old kernel and still no sound.
View 2 Replies View RelatedIn Lucid, Logitech Pro 9000 webcam worked fine until the kernel was upgraded to 2.6.32-24 recently. The usb sound was not listed in /proc/asound/cards. I had to boot from 2.6.32-23 to make it work.
UPDATE: the recent upgrade to 2.6.32-25 fixed this problem.
I managed to get my Linksys AE1000 USB wireless adapter to work on Unbuntu 10.04 LTS.but recently I updated the kernel to 2.6.32-26 and when i rebooted I logged on to see my wireless connection was not working.even worse, I can't fn the links i had that showed me how to install it in the first place, its about the fact that the new kernel uses a different usb setup(probably incorrect, let me know it its incorrect). its an issue that the hacked driver isnt compatible with the new kernel release, how can i revert to the older version that it did work on? i'm using a RALinkTech driver [URL]
View 3 Replies View RelatedLooking for a joystick recommendation for a laptop installed with FC8 (kernel 2.6.25-?)
View 1 Replies View RelatedI recently updated the kernel to the newest version(2.6.32-23-generic) using the update manager and now I am unable to boot in to my Lucid installation.
My setup is LVM on top of a RAID 0 array. My computer had been running in this configuration since Lucid was released.
The Error Code I get on Boot is to the effect of: /dev/mapper/ubuntu-os is not available.. and then I get kicked in to Busy Box.
Once in Busy Box if I try to use mdadm to mount the RAID array I get this error:
If I boot in to the live CD I can mount all of the partitions and LVM volumes, so it does not appear to be a failed drive or volume.
I have looked in the mdadm.conf, lvm config and grub config files and searched the "Google" for an answer with no-avail...
Ultimately I would like to find a solution which doesn't involve a re-installation.