Slackware :: Custom Kernel, Now System Is Unbootable?
Jun 26, 2011
I compiled my own custom kernel for the first time. I tinkered with different options, nothing to difficult. I actually didn't expect it to work the first time.
I had kept the original lilo boot config just in case something was to go wrong. Now when I try to boot the system, I always get a "VFS: cannot mount root system on (8,3)". I googled this and found that my kernel did not support my root filesystem (btrfs). So I made an initrd with btrfs kernel module, but it didn't help. I then got a string of errors about how /dev could not be mounted.
My question is two-fold. First, how come when I configure the system back to when it was first installed, it still won't boot? Im using the same kernel (22.214.171.124-smp). Second, how can I get myself out of this rut without reinstalling?
vga = normal
# Linux - Slackware
image = /boot/vmlinuz-huge-smp-126.96.36.199-smp
root = /dev/sda3
label = Linux
BTW, I have been maintenancing the system by chrooting into the device off of my slackware boot disk. Im on slack 13.37
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
I have a custom built 2.6.37 kernel where I have most of my devices compiled into the kernel. The only modules are related to nouveau (in case I want to go back to proprietary nvidia) and sound drivers. Everything seems to be running fine. However, in /proc/acpi, I'm missing a number of entries, such as thermal_zone/, dsdt, etc. I do have ac_adapter/, battery/, button/, event, processor/ and wakeup. I've gone through what I think is a very detailed review of my kernel config, and I can't find where I've missed something ACPI related. Here is my kernel config with the ACPI section.
Code: # Power management and ACPI options CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND_NVS=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION=y .....
this isn't so much slackware specific as it is general linux related, but using the default huge slackware kernel included with 13.1, acpi reports cpu temps of about 55 celsius i always like to run my own kernels though, and using the latest stable kernel, i have compiled one using what i believe is necessary for my hardware, and everything works as expected except that acpi reports my cpu temp as 80 celsius at idle, causing my fan to be running constantly
so without simply using the generic config included with slack in the newer kernel, what do you think might be causing the thermal issues? i used diff on the two configs and the output is over 5,000 lines, so thats not a huge help, and im really not even sure what to be looking for the cpu is an intel i7 720qm, so if anyone might know any specific settings for that processor type needed for acpi to interface with it properly that would be much obliged here is my config for potential review: [URL] also, if i disable acpi entirely, the fan operates as normal but i cannot get readings obviously
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is: /sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current. What i missing in kernel?
I have a Macbook Pro 5,5. I had Fedora 14 installed on it, updated to the latest version. I updated the kernel, and performed an update. Now, every time my system starts, it loads up the startup fedora bar, and it gets stuck at the bar being loaded 100%.I press ESC to see what is going on behind the scenes, and I notice that the problem is that atd cannot start up.
I did a routine update of my ubuntu 10.4 (in wubi vista) to the latest kernel (something -26) and installed a java plugin for firefox. After a reboot, i open up the "Ubuntu" entry and i see a message flash accross the screen (something about hda,0,0 or sda im not sure) then it just reboots the PC. No command line or anything. No need to say im pretty screwed
My question is, is there any way to get my files off of wubi? Or even better can i restore Ubuntu to working again? P.S for some reason the two times i have tried to run a live CD on this laptop, it has corrupted vista.
I built my slackware system from source code. Bootstrapped, toolchained etc.. The only thing I didn't change was the chost thinking that life would be easier if left alone @ i486. Would I have gained anything if I had used i786 or even pentium4 (pentium4-slackware-linux-gnu)?
I already got all the benefits of optimization when I used (still using) my own CFLAGS CXXFLAGS right? So changing the chost won't do anything speed wise will it? If I used march=prescott when compiling everything am I ok to just forget about the chost value? It's not gonna change anything will it?
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 188.8.131.52-smp with 184.108.40.206 headers? I just compiled and installed the 2.6.37-autogroup kernel from AUR on my ARCH setup and I like it especially when using firefox with lots of tabs open and other background apps also running. I did notice a speed and smothness difference in my ARCH testing setup with this kernel patch and I can get same results in 13.1??
My mom's computer is no longer bootable. I was thinking of attempting to fix it later on this week and am thinking of doing a chroot and updating via a live CD hoping that an even newer update solves the problem but I have some doubts of success. Does anyone have any information about this issue so that I can be better prepared to fix it? Also, I thought I should mention that I tried the second newest kernel to see if that would make it work. It didn't. The error is something along the lines of having the /dev/diskuuid change. If I'm correct, Ubuntu changed the disk's name and is trying to boot the old name. It's dropping to an initramfs shell (not the regular terminal where you can work miracles ).
I've just reported a launchpad bug report about my desktop system being unbootable after upgrade to lucid lynx. [URL]... I opened this thread to ask if someone else experienced a similar problem and for collecting information and workarounds (none yet) about this quite serius problem. The system has an nvidia graphic card and proprietary drivers were installed before the upgrade. However I'm not sure the problem is related to this. FYI, the system booted regularly from a usb stick with ubuntu lucid lynx. SO the problem is in the upgrade path.
I tried running an upgrade from 8.04 LTS to 10.4 last night, and things seemed to be going smoothly. The upgrade progress was nearly complete, and I wandered off for a while to let it run. When I came back, I had nothing but an orange screen and and unresponsive system. I left it alone all night with the hopes that something would happen, but this morning nothing had changed so I hard restarted the system.
Ubuntu 10.4 appears in GRUB, but the system cannot boot and exits with a kernel panic and the message "vfs unable to mount root fs on unknown-block" I was able to boot to a 10.4 LiveCD, and I can browse all of my files from there. What can I do to get this system back up an running? I have dozens of user account and a lot of customization (it acts as a webserver with a wiki for a gaming website running on it, among other things), so I really really don't want to do a fresh install and lose all my data and customizations.
I updated 9.10 and system crashed during update and is now unbootable. It seems to freeze (or is just taking a really long time) at fsck. Is there any way to make my computer usable again without reinstalling the whole OS?
I have installed Ubuntu Lucid Lynx Alpha on my computer.was running fine until I installed usplash. Now when I boot up I get a message saying "Ubuntu is running in low-graphics mode" and a list of options. When I select any of them and press Enter I get a blank screen. I can't even load a command line. I want to remove usplash to see if that fixes the problem, but I would have to do it from another OS. How could I do that? My other operating systems are Ubuntu Karmic and OpenSUSE.
yesterday I performed an automatic security update suggested by the update manager on my virtualized (with VirtualBox on a Windows 7 host) Ubuntu 10.10 installation.
The update somehow failed and left me with an unbootable system. When I try to boot, I am told that various folders, files, and what not are missing. Then the system drops into a busybox and leaves me with an (initramfs) prompt.
This happens with all kernels I get offered by GRUB, although the error messages are quite different from kernel to kernel.
Well, the short of it is this: I don't have the slightest idea on how to get back to a working system and this site is the final straw I'm willing to grab. A complete disaster like this following an update initiated and executed by the system is unheard of in Windows-land; at least I haven't heard of it, yet, and therefore I am going to abandon Ubuntu and Linux altogeteher, if there is no remedy.
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
a stock fedora 11 install on my embedded board results in the primary CompactFlash card being driven by the SCSI driver and is called SDA..running my custom kernel which i have slimmed down and yanked out the SCSI stuff because I dont need it, results in my CompactFlash card being called HDA of course driven by the ATA driver.which should I be using? both work just fine.. the CompactFlash card is on board and according to Soekris is actually run from an IDE controller, as there is no SCSI on board..
so im assuming the less amount of system overhead is to run it as IDE?I have no issues running it either way I just want to do whats right.. and what is going to be supported in kernels down the line, as im considering a bump from my current 2.6.30 kernel upwards for my project.
I been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (220.127.116.11 )Following this help thread viewtopic.php?t=4468.When i invoke make xconfig i'm just kinda lost at that point. Not really sure what to do, so i just save it as is and then compile/install.when i try to boot the kernel, a kernel panic happens saying it can't not mount the root partition.So i am sure i am missing a step with the xconfig part but not sure what.
I wasn't using my laptop for at least a few hours, but when I looked at it, it had seemed to crash. I am hoping to figure out what caused this, and to prevent it from happening again. I believe it has something to do with drm or b43 as that is what I could decipher from the screen. I have checked some logs and found nothing irregular. I do not want this to happen again. I am running kernel 18.104.22.168 with no patches and a custom config tailored to my processor. The reason I am running 22.214.171.124 is because of support for my Wifi.
I would like to try and optimize my kernel a bit. Since I am doing this on a fresh install, I don't really care if the os gets bricked in the process, and I am sure I can bring it back if I can boot into a recovery console from the old kernel. So, I followed thispost. I patched it and copied and edited a config file from /boot/, saved it as .config, I tried it several times with both removing and not removing /debian and /debian.master directories from the source, yet I always get the same error when I run "make oldconfig".
Code: $ make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig *** Error during writing of the kernel configuration. make: *** [oldconfig] Error 1
Had a custom kernel (126.96.36.199) running under Slackware 12.1 and also the same kernel on an Ubuntu 10.04 machine just fine, however after a clean install of Slackware 13.1 this kernel no longer works (This kernel was re-compiled with the same .config file under Slack 13.1) as I keep getting the the following: -Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3) The strange thing is it keeps looking for the root file system in hda1, however the stock 13.1 kernel finds it in /dev/sda1 so the root partition is /dev/sda1 in lilo and the harddisk is known as /dev/sda.
I am trying to update my fedora 8 kernel, is there a way to do that? I build the one of kernel.org but when i want to boot it a get a lot of messages like: mount: cant find /dev/root I tried to follow the guide at building a custom kernel for fedora, but thats just for the last supported version of the kernel of fedora 8.
however,, there are no kmod-wl packages for that kernel, so i have no wireless at the moment. how do i build / obtain kmod-wl package for my kernel? rebuilding the kmow-wl src packages does occure in build for an older kernel:
When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
I've about 5.5GB of free space....whenever I try to compile the kernel my system runs out of space...says zero bytes remaining maybe I din't configure it that well I cant exactly figure out which drivers/modules I need in order to obtain a working kernel.
All I want is a lxde based desktop to play with and tweak. The problem is that I am using rather esoteric hardware. An xcore86 device on chip to be precise. I have a custom kernel in deb format, and I managed to install UNR 9.10 and then install the custom kernel. Strip out as much obvious gnome stuff and install an lxde desktop. Now this is a quite good solution but still leaves me with a lot of junk that I am not sure I need. 2 ideas occurred to me. Install lubuntu and then install the custom kernel(this failed to work because lubuntu's kernel refused to play nicely with the xcore) or do a minimal install and work my way up adding the things that I wanted. (Again this ground to a halt when the screen went blank)
I looked at unetbootin to try and put in a custom kernel but to a novice like myself it did not work very well.Can anyone help, either a list of everything that can be removed safely from a UNR install to leave me with a minimal install, or a way to insert a custom kernel into a lubuntu iso?
I'd like to create a custom squeeze kernel. Is it a really bad idea to edit to edit the kernel config file directly instead of using "make config", "make menuconfig" or "make gconfig"? My problem is I missing a search function, for example in "make menuconfig" and cannot find some entries.