Slackware :: Can't Boot Up With Kernel
May 2, 2011
I installed Slackware 13.37 today, fresh install. I added the generic 2.6.37.6 kernel to lilo, rebooted, and ran with it. I transferred some stuff to my hard drive and installed a few things, reboot again and now I can't boot up with my kernel of choice (but I can with the huge kernel). It stops during the boot process and says
Code:
[1.785238] No filesystem could mount root, tried: romfs
[1.785342] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
[1.785417] Pid: 1, comm: swapper Not tainted 2.6.37.6 #2
After that is a line that says Call Trace and several lines after that with stuff that makes no sense to me and that I don't feel like typing out, but will if it is relevant.
View 5 Replies
ADVERTISEMENT
Jun 20, 2010
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
View 10 Replies
View Related
Jan 5, 2010
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
View 14 Replies
View Related
Mar 15, 2010
I've just seen a strange set of error code during my boot sequence:
WARNING: at mm/page_alloc.c:1813 __alloc_pages_nodemask+0x5ce/0x6c0()
Hardware name: MS-7250
Modules linked in: lp fuse nvidia(P) joydev snd_cmipci gameport rtc_cmos rtc_core thermal processor snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore thermal_sys i2c_nforce2 rtc_lib button agpgart k8temp hwmon psmouse sg i2c_core ppdev parport_pc parport forcedeth serio_raw evdev
Pid: 1543, comm: mount Tainted: P 2.6.33 #2
Call Trace: .....
The machine appears to run normally otherwise.
View 4 Replies
View Related
Feb 16, 2011
My Slackware boots using the huge kernel. I am not using LILO; I am using GRUB from the extras directory on the DVD. I followed the tutorial @ [URL] up to the point where it discusses modifying LILO. My /boot/grub/menu.lst reads, in part:
# Linux bootable partition config begins
title Slackware Linux on (/dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 ro vga=normal
# Linux bootable partition config ends
This boots the huge kernel. What changes must I make to the above menu.lst entry to boot using the generic kernel?
View 3 Replies
View Related
Mar 7, 2010
I tried to compile a 2.6.33 kernel following Alien's guide.
I pretty much used the default values for every (NEW) option avaiable. I used "make localmodconfig" on my current config (zcat /proc/config.gz) and then tried to use "make menuconfig" to check if I could change anything. I didn't understand most of the options, so I skipped it. Then I used "make bzImage modules" and "make modules_install", copied the files mentioned on the wiki and run lilo.
But when I try to boot using my custom kernel, it gives an error like "Cannot remount read-only filesystem as read-write! This can cause serious problems."
If I try to continue the boot, it hangs when trying to launch the syslog script...
The new kernel entry on lilo.conf is:
Code:
image = /boot/vmlinuz-custom-2.6.33
root = /dev/sda4
label = newkernel
read-only
just like the default kernel entry.
By the way, one thing I changed is the kernel compression format, which I set LZMA. But it didn't seem to be the problem, since it at least started...
View 10 Replies
View Related
May 14, 2010
After using slackpkg to update to -current on a new slack(32) install I was greeted with kernel panic "can't mount root fs" on reboot.
It was looking in the wrong place. I thought I answered yes and slackpkg would run lilo for me when it was done with the upgrade but perhaps I misunderstood.
I had my handy dandy USB boot stick so I set the bios and booted from USB. OK fine, I pointed to the correct location (hda1) and voila.
a 64bit kernel... The machine in question is a 2004 vintage celeron notebook
To my question: Is there a way I can point the loader to another kernel?
One last piece of the puzzle, the dvd drive is bad and I don't (yet) have a PXE server or even another linux box.
View 2 Replies
View Related
Jan 5, 2010
's/ARCHTYPE=i386/ARCHTYPE=x86/'If your looking for a kernel image in /usr/src/linux/arch/i386/boot, your not likely to find one.
View 3 Replies
View Related
Mar 12, 2010
I recently did a fresh install of current and once I had it up and running I compiled a fresh 2.6.33 kernel using my old config file, but now I get this warning durning boot, specifically during module loading WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release. This doesn't seem to be causing any problems but I am curious to know what the message meams? I checked /etc/modprobe but everything looks normal.
View 1 Replies
View Related
Oct 14, 2010
The new 2.6.35.7 kernel fails to boot on my Lenovo laptop. I had previously compiled a 2.6.35 kernel with a couple of different .config files and never had it boot properly. The failure occurs very quickly and I am including the final screenshot in case that helps.
View 7 Replies
View Related
Mar 2, 2010
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?
View 18 Replies
View Related
Dec 24, 2010
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
View 3 Replies
View Related
Jan 20, 2010
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]....
View 4 Replies
View Related
Jan 13, 2011
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 2.6.33.4-smp with 2.6.33.4 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??
View 1 Replies
View Related
Jun 23, 2011
I'm trying to bring my Slackware system back to life as my XP HDD is dying... I've got everything working except for my audio. I got a new motherboard (ASRock P43DE3) and it has a VIA VT1708S as the onboard audio. Is there any way I can get this working without rebuilding the kernel?
View 5 Replies
View Related
Aug 21, 2010
I'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
My codecs are :
Code:
root@unraid:~# cat /proc/asound/Intel/code* | grep Codec
Codec: Realtek ALC888
Codec: Intel G45 DEVIBX
Code:
lspci -v:
[Code]...
View 4 Replies
View Related
Jun 22, 2011
Fresh and Full install: Slackware 13.37 64-bit x86_64. What is the correct procedure to switch from huge kernel to 2.6.38.4 kernel?
View 6 Replies
View Related
May 13, 2011
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies
View Related
Dec 31, 2008
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:
View 3 Replies
View Related
Feb 11, 2010
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
[root@noname boot]# uname -r
2.6.18-164.11.1.el5
My /boot/grub/menu.lst looks like:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I can't see anything wrong and I did not change/try anything.
View 11 Replies
View Related
Nov 6, 2009
I compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
View 1 Replies
View Related
Mar 24, 2011
I would like to recompile my kernel to add few modules to it but I would like to keep my current configuration so as not to have troubles with missing drivers for my hardware and stuff.
How do I do that?
View 7 Replies
View Related
Jul 17, 2010
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 Related
Jan 21, 2010
So I got slackware 13 from the website and created 4 partitions (primary) and left some (100GB) space as I planned to install windows 7 in that. After installing slack, when I booted from windows DVD (rtm) in partition section it said I already have 4 primary partition so windows cannot used the rest of space despite the fact that it was free (windows even grayed all options like new partition and format etc. for that space). So I thought I'd create 2-3 primary partition for linux (slackware) so that windows can use the free space and make it a primary partition.
So, Next I formatted with slack (3 partition, 2 Primary, 1 extended, total space for slack 50GB) and after its installation I worked my way with windows, but it just created one partition of 100Gb, won't let me create any saying all primary partitions are created. Anyway, I created that partition and installed windows 7. But it messed up my lilo (slack won't show in boot menu) neither can I create any new partition.
After all I reformatted again created 2 partitions for windows (that actually became 3 as windows 7 create 100Mb separate partition for system). Installed windows correctly. Then I booted with slack , which allowed only creating 1 partition as 3 were already there. So I created 1 extended partition, in which I created 4 partition 1 to mount for /boot (100M), 1 for /swap (3G), 1 for home (10G), 1 for / (35G) everything worked fine till I reached last point to install lilo. At that point it said cannot install Lilo (I tried all options simple, expert, install to MBR etc.) but it just won't install. Anyway, after that it said you can install it manually so I clicked OK. Then it said setup complete, remove disk and press alt+ctrl+del to reboot, which I did. But there is just windows 7, no slack ?
View 9 Replies
View Related
Jan 23, 2010
I try to install Slackware to my IDE hard drive and boot first from Slackware DVD. After I loaded huge.s kernel, and tried to partition the hard drive using fdisk by entering "fdisk /dev/hda", I found out that the partition size is max to 3 Gigs instead of 80 Gigs.
I think the kernel is looking at my boot disk, which is around 3 Gigs. How can I make so that it looks at my IDE drive instead at my boot drive? Is there any manual that shows me how to install Linux from scratch this means I want to wipe out all my hard disk and install Slackware Linux there?
View 2 Replies
View Related
Jul 18, 2011
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
View 17 Replies
View Related
Oct 27, 2010
I installed Slackware 13.1 and Windows server 2008, I also installed LILO in MBR, I Found I can boot into slackware, but can't boot into Server 2008. then I　use command bootsect/fixmbr. now I can boot into server 2008, but the problem is I can't boot into slackware. I try to install lilo to supper sector. it's not works. I only can boot my slackware by a USB stick.who can help me to solve this problem? I really need these two systems.
View 5 Replies
View Related
Jul 22, 2010
I am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
[Code]....
View 5 Replies
View Related
May 29, 2010
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?)
I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
[Code]...
View 13 Replies
View Related
Nov 1, 2010
I've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per [URL].. it returns GrUB error 15. Here is my menu list entry for Slackware -
Code:
###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
savedefault
[Code]...
View 15 Replies
View Related
