After reading this article openSUSE News - Forum Users Benefit from openSUSE KDE Repository I added that KDE repo to yast and switched all packages.
After rebooting it says (failsafe kernel configuration says the same):
Kernel panic - not syncing: VFS:
Unable to mount root fs on unknown block (0,0)
And stops at this string: "[<c0203826>] kernel_thread_helper+0x6/0x10" and capslock light is blinking.
I have a new acer machine which runs fine on 10.10 mythbuntu desktop livecd. Install seemed fine.
Then I ran an update and on reboot I get a kernel panic error. Research on this reveals it as a very deep subject which can consume many hours, so I opted to reinstall.
This time with ubuntu 10.10. I've tried different CDs, liveusb. Same errors.
So, the question is this - where do I concentrate my efforts - somewhere ubuntu doesn't like this machine, or grub. Does a reinstall overwrite the grub install too? Or do I have a bogus grub install I need to purge before I will get anywhere.
Here's what to do right after applying the latest kernel security patch (2.6.34.7-0.4) to get the ATI driver back to work. Do not reboot yet make sure the update installed the headers and sources for kernel 2.6.34.7-0.4: rpm -qa | grep 2.6.34.7-0.4 should print the files in red on a 64bit system:
[Code]....
I attempted to upgrade a Slackware 13.0 fresh install to current. First I updated 13.0 by running:
Code:
slackpkg update
slackpkg upgrade-all
I then amended the mirror to current and ran the following commands
Code:
slackpkg update
slackpkg upgrade-all
[Code]...
I am trying to install openSUSE 11.3 on a Dell Dimension XPS D233. When the system loads the install after the second of six pieces it always locks up and the Caps Lock and Scroll Lock start flashing. This in my experience as a IT Specialist means a kernel panic has occurred. Does anyone know of the way to correct and/or bypass this issue?
View 4 Replies View RelatedI have had a serious problem with my laptop recently. I have been having unexpected reboots and kernel panics and I don't know why. I can't tell if it is hardware or software, and what is causing it.
It has happened on multiple power bricks from different outlets and locations, my slice battery and my main 9-cell battery.
I am running Debian Testing/Stretch with Kernel 4.1 with XFCE4 on a Lenovo T420 with 16 gb of ram, a i5-2540m, USB3 Express Card, OCZ SSD, an intel 7260 ac wifi card and Ericcson F5521GW 3g card. I also have a modded bios for the wireless cards, and I have had that for over half a year without any problems.
I have no clue what the cause is from the logs.
I also booted into Windows for a bit, then it blue screened, but I don't know if it was because of a driver I had tried to put on earlier for the 3g card, because Linux was out of commission and I needed 3g. The driver didn't work, gave a code 10 or something and gave me a blue screen that said something along the lines of device driver attempting to corrupt the system has been caught. Windows also won't boot anymore.
I'm not worried about Windows though, and what I really need is Linux to work, being that this was the first time I booted up into windows in several months.
Memtest runs fine, and passes all tests.
Right when I turned on my computer after one incident, I wrote a script to check the CPU temp and write it to a file every second. Once the computer turned off, I read the file and it said the CPU was at 39 degrees. Not something to turn off over.
I cannot find any indication of a problem in /var/log/kern.log. kern.log was extracted from the computer right after it rebooted randomly. Find it here: [URL] ...
After having my usb wifi adapters working fine for some time, they stopped working and I can not get network connectivity.
Some one else was using my box and they reported seeing a kernel panic and then rebooted the box. Now there is no connectivity through the wifi interfaces.
I have seen the kernel panics related to this driver before, but usually a reboot has no ill effect.
Code:
root@Algalon:~# iwconfig wlan0
wlan0 RTxx70 Wireless ESSID:"a800" Nickname:"RT3070STA"
Mode:Managed Frequency=2.412 GHz Access Point: 00:0B:86:9A:08:80
Bit Rate=54 Mb/s
[Code].....
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Code:
It is my first try getting Linux on my pc which is an Acer Aspire Z5610. This is not the first time for me when I am getting an Kernel Panic error on this computer.
I looked up google hoping to find an answer and I found out that it may be my BIOS's fault. I currently have Windows 7 on this PC. I have a Phoenix BIOS and there is an update for it called "Bios Linux" on the official Acer support website.
OK, after this short introduction, that's the error:
I really hope to get support for this problem as I can not literally install any other OS to this PC than Windows 7 because they fail with Kernel Panic.
Tried other Linux Editions and even Mac OS Intel Edition and IAtkos V1 and V7 and they all give kernel panic.
I got this weird kernel panic in a brand new computer that my friend bought a few days ago.
The hardware specs are:
- AMD Athlon II X3
- 4 GB RAM
- SATA HDD and DVD
- Motherboard: MSI K9N6PGM2
Whats happening? I have installed openSUSE in a lot of machines and this is the first time that i got this.
Tried with a lot of media that i have here, LiveCD's, various DVD's and nothing.
just updated to the kernel 2.6.36.2 contained in this repository: Index of /repositories/Kernel:/stable/openSUSE_11.3 The x86_64 type. And im getting a kernel panic after about 15 minutes of machine usage. Is it an error in packaging or what?
View 9 Replies View RelatedI've currently have opensuse 11.3 installed on my system and I would like to do a new fresh install of opensuse 11.4. I therefore downloaded the DVD 11.4 x64 install. However, when booting the kernel from the DVD (that leads to the installation procedure) I obtain the following error message "unable to handle kernel paging request". The system then stops and I need to perform a hard reset to restart again. The same happens if I try do boot from the live gnome CD. Thus, I'm unable to install opensuse 11.4 at all due to this problem. A possible solution would be to perform a hot update (i.e. changing repositories in my 11.3 and perform a zypper refresh and zypper dup). But I'm a bit scared of doing this since this will install the problematic kernel. how to circumvent this problem ? Is there any updated version of the live CD? I've been able to install opensuse 11.4 x64 without problems at home. Now I'm trying to install it at work. The current kernel (at work) is:
[code]....
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
View 5 Replies View RelatedMy computer
AMD phemom II 955 X4 Black Edition 3,2 Ghz
Asus M4A785TD-M EVO micro atx
Kingston 4Gb Ram DDR3 1333 mhz (KVR1333D3N9K2/4G)
Disco Duro Western Digital 1 terabyte
LG GH24 Super Multi DvD rewriter
menu.lst
fstab
fdisk /dev/sda
Orden (m para obtener ayuda):
Bios
I have Sata=AHCI
Sometimes it starts and sometimes not. the RAM is memtest OK. The test detects a firmware in the micro hole 15 to 16 mb of memory. The rest is OK.
I updated my slackware 13 to current with the commands as writes in man slackpkg:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
but now it's print kernel panic and I can't restore it.I tryed to boot with root=/dev/sda3 parametre, but not effect. Do you have ideas?
Yesterday i was prompted by my update manager to update some packages. I really don't remember which but i updated.
After reboot the box now kernel panics. I don't believe i get a ubuntu splash screen, and at this point i can't figure out how to get to my grub, in case a kernel was upgraded and it's possible to boot to different kernel.
i noticed some words like 'mantis', 'oops' and 'dvb_core' was a part of the text i get on the screen.
Can this be because of a dvb* upgrade that breaks something important ?
If needed, i should be able to boot via liveCD, or i could take a picture of the errors.
Update manager downloaded and installed latest kernel (Ubuntu, Linux 2.6.31 -16 -generic). When I tried to restart I get the message { 1.661235}Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block(8,38). Everything works fine on previous update.
View 1 Replies View RelatedI would like to remotely reboot a computer (via ssh) to a non default kernel. If I just type reboot, it reboots to the default kernel. Man reboot(8) does not give any hint so I am not sure that is possible at all. I have found nothing googling around either.
View 6 Replies View RelatedThe server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
# cat /etc/grub.conf
default=0
timeout=20
[code]....
It appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.
View 3 Replies View RelatedAfter update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
View 4 Replies View RelatedI just reinstalled my OpenSuse 11.3 with the GNOME desktop. As soon as I was done installing and I was on a fresh desktop, I installed the Yast updates that were available, rebooted, and now I can't login to any of my User accounts. Whenever I try to login, it tells me that it is "Unable to Open Session".o any of you know how I can fix this without having to reinstall all over again
View 1 Replies View RelatedI am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)"
I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
I've upgraded kernel 2.6.27.48-0.2-default to 2.6.27.54-0.1.1 on openSUSE 11.1. Before I tried to upgrade to 2.6.27.48-0.3-default where I encountered the same issue. After reboot it can not find the modules for 2.6.27.48-0.2-default which puzzled me to no end. Now I have found that the /boot which is on separate partition of ext2 type is not mounted. The mount command does not recognize ext2 and xfs anymore.
Clearly the initrd does not have the right modules. Since this is standard zypper up process I would expect this to work without issues since it has worked until the 2.6.27.48-0.2-default kernel without issues. Has something changed with the last 2 kernel versions that requires some extra actions from me and if so what do I have to do.
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
View 9 Replies View Relatedlatest update to 11.3 a complete failure afterwards on reboot I'm instructed that I must first install kernel and to strike any key to exit which return me to grub menu. thats it for me and Osuse. 11.3 has been one bug after another and to much for me overcome. I will return once a day to see if anyone can fix this/
View 9 Replies View RelatedI recently decided to try out OpenSuSE after a few years of using kubuntu. However, upon lanuching the install disk I get the following kernel panic: "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(3,1)". I am using the 64-bit DVD install and I have verified the md5 of both the download and the disk itself. The specs for my computer are:
Core 2 Q6600
4gb ddr2 RAM
MSI P6N-SLI motherboard
Nvidia GTX 480
I tried to install OpenSuse via LiveCD this morning I got following Error Message: Kernel panic - not syncing:
[code]....
I am using the 32bit-Version of OpenSuse while running this on a 64bit Dualcore. Could that cause the issue?
I'm using openSUSE 11. I'hv tried to upgrade it to 11.1 with a x86_64 installation DVD (as I did earlier), but it failed. It showed the following message:
[Code]...
eventually same type of problem happend when I was trying with fedora 10... fedora 9 and openSUSE 11 install smoothly in my 64 bit machine (compaq SR1730IL, Intel pentium 4, 524 and 1GB DDR2 RAM)
Today i upgraded my system and started getting error when i update, install or remove a package. The error isn't restricted only to one repository so i thing something is wrong with my system.
[Code]....