I am trying to install slackware 13 on a dell poweredge. However I am getting a kernel panic on the "Fusion MPT 3.04.07" driver. This is preventing the installer from detecting the SCSI hard drives. I have been able to install sucessfully with 12.0. Can anyone suggest how to fix this?
View 7 RepliesI have an IBM server with a: "SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)", meaning kernel module CONFIG_FUSION. This is the real hardware, not emulated by vmware. With recent kernels (2.6.30-35) the boot results in one of three situations:
1.) Most common: kernel panic, way too long stack dump to see anything useful but did have a terminal briefly to debug this and its just not being able to communicate with the scsi subsystems, google for errors found nothing of use.
2.) Sometimes: A hang waiting for the scsi disks after the controller fails to initialize properly, does not pass in a couple of hours.
3.) Very rarely: A long wait for the scsi controller to initialize but a succesful boot afterwards. ACPI subsystems are taking all CPU power. This is the state the machine is at now, working somewhat.
I can boot the machine with a Gentoo live install disk (kernel 2.6.29 I think) and under that version the controller initializes instantly and there are no problems whatsover using the disks so the hardware seems to be solid!
There were some MPT changes in 2.6.25rc5 so thats the latest kernel I've tried. The errors during boot change to a bit more verbose but thats about it. Unfortunately I don't have a serial terminal with me anymore so cannot capture these errors but it was something about an "unexpected doorbell" with 2.6.24 and nothing memorable with .25. Long story short tho, googling the errors provides no solutions and the little I find points to the controller being too slow to initialize somehow.
I'm running out of ideas here and the server is burning fans like theres no tomorrow (ACPI taking everything it can) so is my only option to downgrade to 2.6.29 (and downgrade udev, lvm2, so on and on and on)? I can't believe I'm the only one for whom this has been broken for several minor versions.
Kernels tried:
- 2.6.29-gentoo (live disk) - works, blazing fast initialization
- 2.6.32-gentoo-r7 - random boot failures and successes
- 2.6.34-gentoo-r1 - same
- 2.6.35-rc5 vanilla - same, better errors, zero useful google results.
I'm not very keen on longshot attempts since it can take a couple of hours of panic-loops to get the machine booted up again and the server functions cannot be transferred to another machine. Also, I'm a bit hesitant to mention this, but the boot has only ever succeeded when a serial cable with something at the other end is connected. At first it was the testing serial terminal and now its just a connection to a UPS.
Attached: bootlog of succesfull-ish boot with 2.6.34 (had to cut some out to make the sizelimit):
Code:
Linux version 2.6.34-gentoo-r1 (root@livecd) (gcc version 4.3.4 (Gentoo Hardened 4.3.4 p1.1, pie-10.1.5) ) #1 SMP Sun Jul 18 18:54:48 EEST 2010
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000099c00 (usable)
BIOS-e820: 0000000000099c00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[code]....
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....
I would like to upgrade from my slackware version 12.2.0 based system. I have 200GB IDE hard drive. Tried installing with kernel version 2.6.32.7. The installation would not boot. The kernel is looking for root on sda1 when it should be hda1. Is there a way other than reconfiguring, compiling and building the kernel?
View 13 Replies View RelatedI 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?
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 have gone through all the kernel config options repeatedly, but everytime I get the same error after running my configured kernel.
To begin with, after unpacking the kernel I get Undefined video mode numer: 305 and then a selection of video modes appears.
Why are the standard settings in my lilo 1024x768x256 (vga 773) not accepted?
VFS: Cannot open root device "808" or unknown block(8,8) Please append a correct "root"=" boot option; here are the available partitions: Kernel panic- not syncing :VFS: Unable to mount root fs on unknown block(8,8)
My partitions are ext2, and this format (as well as other formats) are compiled in the kernel.
I have been dual booting "Windoz" (hda1) and slackware 11 (RTAI - hda 5) old system. The problem happen after I installed slackware 13(sda8) on the same hard drive. I was able to mount my old slack11 (now (sda5)) to slack13 to read. So I wanted to boot to slack11.
MY Lilo on slack 13:
Now when I boot to Slackware11 I get:
VFS:
How can I boot a old "hda" image on "sda" system. With a floppy I can go back to Slackware11.
today I updated my Slackware 13.0 to 13.1. Unfortunately it didn't boot any longer. I probably forgot to run "lilo" before restarting. However, I reinstalled Slackware and I installed grub instead of lilo I'm more familiar with it..
This was my first menu.lst config:
Quote:
title Linux (uuid)
root(hd0,0)
kernel /vmlinuz root=UUID=6a8096a3-3915-4ef2-8984-976e42d04cfc ro vga=0x031b
While booting it stopped and printed this message:
Quote:
Kernel panic - not syncing: VFS; Unable to mount root fs on unknown-block
Then I compared it to other Linux system on different computers and I noticed that every of them, who are using uuids, using an initrd as well. So I created one and now it boots properly.
I just wonder, why? Why does it need an initrd to boot by using uuids?
im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,4) i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3. but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. edit this is my lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda3
[Code]...
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel.
Red Hat nash version 4.2.1.13 starting
sda: assuming drive cache: write through
sda: assuming drive cache: write through
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd-dev failed: 2
Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info:
Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
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:
I 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?
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 RelatedAfter 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:
A package dependency could not be found. More information is available in the detailed report.
Details:
Quote:
package could not be removed, as other packages depend on it.
maybe simple task, but still those errors are killing me.
From time to time, I check out the latest compiz-fusion just to play around with it. Everything compiles and installs just fine under my Slackware64 13.1 install, and I follow the build order that's been posted here and on SlackBuilds.org. When I switch over to compiz and emerald from Xfwm4 using fusion-icon, everything looks just fine. However, all of the text that *I* input into aterm is corrupted. Using the xfce terminal doesn't seem to be a problem. When I move the cursor using the arrow keys, a similar type of display corruption occurs. When I close aterm, an outline of the window remains until I tell fusion-icon to reload the window manager.
View 2 Replies View Relatedi found this http://crunchbanglinux.org/forums/to...indow-manager/ it has screenshots of exactly what i'm looking for, but i cant actually get it to work when following their instructions. i create the fusion.desktop file and the start-fusion.sh file, but they do not show up in xwmconfig or KDM. is there something in particular for slackware that i have to do to add the .desktop entry to my list of sessions?
View 4 Replies View RelatedI'm hoping that this is a stupid question with a very simple answer that I just can't find.I've been playing around with compiz-fusion on -current64. When I have two windows open, if I close the top, active window, I would expect that the next window in the stack would receive the focus. However, it does not. I have to alt-tab to it or click it with the mouse.
View 3 Replies View RelatedIm am building a Linux distro. It will be very tiny and fast.
I only have a minimal linuxkernel (bzImage) who is 1,2 mb big. And then I have Busybox who is 174,6 kb big.
The commands in busybox is: cd, ls, mkdir, rmdir, wget, httpd, clear, rm, poweroff, halt, reboot, fdisk, mount, umount, free, and cp.
When I compiled the kernel i use initramfs/initrd function and point it to a folder where initrd/initramfs source is.
The kernel works OK with others initramfs/initrd files. But not with my own.
Quote:
Here is how the end of the kernelcomplie look like.
Quote:
Here is my init file who is the initrd/initramfs source.
Quote:
The initramfs folder contains "bin" (folder) and "init" a file. No more.
The problem is that the kernel cannot find/read init file.
Recently i've been playing with few variations of linux distros since my Windows XP got infected with something that makes anything flash-player related crash or restart computer even(im saying this because it might be related), reinstall didn't help fix it so i decided to better switch back to Linux world and tried some newest distros. Everything was nice untill..recently some distros after installation gave me kernel-panic or caps lock+scroll lock lights blinking..trouble is Fedora 14 just gave me same stuff after i went maybe 5mins away from keyboard with web browser open then came back to notice..if at first i thought it was wrongly made distribution now i'm bit scared that my PC is dying..i did basic search in google and people say it may be related to hardware beeing too old or drivers but when i use it then i don't encounter this - just when afk. I have almost none experience in Fedora so was just wondering if someone could point me to right direction
View 6 Replies View RelatedI have a CR-48 running Ubuntu 11.04. I've had some continual issues with it, along with other Linux distros I tried. There are times my laptop freezes completely during mid use. If I power off and back on, 70% of the time it doesn't detect the hard drive upon next boot. If I go into BIOS, no SSD detected. If I pull the battery, hit the power button, put battery back in, it'll run fine for a while.
I'm up in the air if it's a hard drive issue or motherboard issue. Once I got this kernel panic I sat here for a half hour on another system typing it up. I hope somebody can look at it and make sense of it and tell me what essentially is happening.
running Kernel 2.6.9.89 just updated from RHN using up2date...
This server runs for a random 5-30 mins then throws the kernel panic.
The Fedora 11 Live CD was tested on a Dell and it is good. On the HP Pavilion a705w, with an Intel Celeron 2.93HHz w 760MB RAM, the install fails with kernel panic. The cd was burned on the HP.
A colleague suggested that the HP may not be compatible with the kernel. Are there startup settings that I might try to diagnose the panic issue? Perhaps there is a verbose boot up process that pauses so one can take notes?
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 RelatedEdit: The PC is broken and I'll buy a new one. Don' bother reading this thread.
I have Kubuntu 9.10 installed on my Acer 7520g laptop. It used to work fine.
But recently my laptop has often went into kernel panic, sometimes at boot, sometimes after hours of normal usage. Today it has not been able to boot properly from HD a single time.
When I boot it up in recovery mode, it kernel panics and displays this (normal mode displays just the graphical progress bar, no text):
Code:
00010c0f
[ 9.620019] TSC f0ed3f8e6
[ 9.620019] PROCESSOR 2:60f82 TIME 1270650316 SOCKET 0 APIC 0
[ 9.620019] This is not a software problem!
[Code]....
I'm sure this is a pure software problem, because Ubuntu 7.10 LiveCD boots up normally and I got X, Gnome and everything working. So CPU must be working perfectly.
I read the logs in /var/log but there were no error messages.
I decided to try Kubuntu (10.4 64bit) again today, it's been a few years since I last tried it. The installation went well, but now I don't seem to be getting past Grub. I get a message that says: Kernel panic - not syncing:VFS:Unable to mount root fs on unknown block(0,0) I tried to use the recovery mode option in grub but that gave me the same message.
View 9 Replies View RelatedI am getting Kernel panic. I was getting is very frequently before, then I re-installed and it starts off fine then after a while it starts happening again.The problem is I have no idea what is causing it. The screen is completely frozen and won't respond to anything. The Alt sysreq combinations don't work, and I have to power off with the button.
View 2 Replies View RelatedI have a Toshiba Satellite laptop, dual-boot with Win7 and Ubuntu 10.10. Everything works as it should in Ubuntu, except when I resume from standby the computer goes into a "kernel panic," the screen freezes and caps lock light blinks.
I travel with my laptop and use standby all the time being a student, so I've been forced to use Windows 7 because it's far more reliable (isn't that funny >_<) when I resume from standby..
After literally searching for DAYS, no solutions have worked for me, and apparently this is a pretty big issue. I would love to get Ubuntu running full-time on my laptop. Also, my display drivers aren't officially supported by Ubuntu, but I'm not sure if that has anything to do with it.