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...
I'm using Ubuntu 10.04 64bit (Kernel 2.6.32-22-generic) and sometimes my /home partition is remounting in read-only and i have no idea why. Normally I only use programms like Firefox, Rhythmbox, Evolution and Netbeans 6.8. Should I switch to the EXT3 filesystem?
dmesg shows me the following information: Code: [ 8758.010352] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 8758.010356] ata7.00: failed command: FLUSH CACHE [ 8758.010360] ata7.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 8758.010361] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8758.010363] ata7.00: status: { DRDY } [ 8758.010366] ata7: hard resetting link .....
Code: badblocks -v /dev/sdb Checking blocks 0 to 78150743 Checking for bad blocks (read-only test): done Pass completed, 0 bad blocks found.
I have downloaded voyage linux 6.5 based on lenny. One of the last things it says is mounting filesystem as read only. then asks me to do login. how to stop this action and eave the file system as Read/Write.
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?
I compiled a kernel using a previous kernel config after I switched to the ext4 file system. Previously it was using ext3 and the kernel compiled and ran fine. I added support for ext4 to the config but when I went to boot I had a kernel panic. The error was "kernel can't mount vfs on (8,5)". Root is on sda5, I don't know what the 8 is. I started over, using mrproper and made a new config, but got the same error. I created an initrd with the ext4 file system but then the kernel said it couldn't mount root on ext3 because of unique options. (something along those lines) I booted back into the default kernel and saw that it had a similar error right after the bios check, but it loaded fine. I'm wondering why the kernel is saying that the ext4 file system is ext3.
My linux distro is CentOS 5.3. Today I edited /etc/sysconfig/readonly-root and set "READONLY" to yes, now my /etc/sysconfig/readonly-root file is like this:
# Set to 'yes' to mount the system filesystems read-only. READONLY=yes # Set to 'yes' to mount various temporary state as either tmpfs
I download "VirtualBox-3.1.2-56127-Linux_amd64.run" and installed it, and got a messages like this " virtualbox have been installed successfully in my system", but when I run virtualbox, I've been told "/etc/init.d/vboxdrv setup" something like that. And I run virtualbox in terminal, got this:
Warning: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.29.6) or it failed to load. Please recompile the kernel module and install it by sudo /etc/init.d/vboxdrv setup You will not be able to start VMs until this problem is fixed.
I run "/etc/rc.d/rc.vboxdrv start" as a root, got messages like this : Starting VirtualBox kernel module ...failed! (modprobe vboxdrv failed.)
I'm getting BSOD when I'm booting my main system (debian 8 fully updated). I get a BSOD with a _ sign. URL...because I can't access to failed boots files. Besides having the files
Code: Select allfelipe@debian ~ % ls /var/log/journal 362d07f9e18b45f8aec4575c347f181d 92e8a448f7a348719da129184a7e6821
Code: Select allfelipe@debian ~ % journalctl --list-boots 0 0c51ae5b67f144059c5470dbe345d621 vie 2016-03-25 09:05:29 ART—vie 2016-03-25 09:11:58 ART
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.
I just did a full install of Slackware64 on my netbook. Everything was sweet until I tried switching to the generic kernel. Even before this, I noticed when I ran the mount command it listed not sda3, which really is the root partition, but /dev/root as the root partition. This also appears in mtab, but not fstab. So yeah, here are the errors when I try booting into the generic kernel:
Code: mounting /dev/sda3 on /mnt failed: No such device No /sbin/init found on rootdev (or not mounted) bin/sh: cant access tty: job control turned off
I've tried rebuilding the mkinitrd_command_generator.sh script several times, as well as lilo.conf. But no success I've looked at some similar old threadss here but most of them are related to slackware 12 and older, so I don't know if these issues are related or not.
I want to change my sda2 partition to ntfs type. i have installed GParted but it is returning a strange type of error. Here is the error dump file...
[Code]...
WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot.
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??
I have a netbook with a 150GB hard drive in it. A while ago I dropped my netbook and it wouldn't boot. Had a "failed command: READ FPDMA QUEUED" error at startup. So naturally I went and reinstalled. Reinstalling worked fine and I had my computer back. What I didn't account for was the fact that anytime it lost power and didn't shut down properly, I'd get the same error. I can't seem to recover my data either. Can't get any live disks to mount the hard drive after this error but for some reason I can still reinstall Crunchbang (essentially debian). Now I know there are bad sectors or something because when I try to use the disk that came with the netbook with an image of Windows XP that writes to the entire hard drive it throws an error but linux will avoid this I suppose when installing.
Now all of this is to say, being a laptop, several times I have left it on overnight when I fall asleep working or have to run into to town and it'll die and then I lose all my data, rather irritating. What's causing this error? What can I do to prevent it besides getting a new hard drive? If I can't prevent it from happening in the future is there a way to recover the data off the hard drive? Here's the section of the boot log that contains the error: [url]
Recently updated to kernel 2.5.32.11-99 and upon restart, failed to boot. Get stuck at a recovery prompt asking for root password or Ctrl-D to continue (which reboots system). I worked around this problem by reverting to the previous kernel 2.6.32.9-70. From what I can tell, with the newer kernel there is a problem with device enumeration of software raid volumes.
I got home today to find that my KDE login screen would not let me log in. It said the authentication process failed or something and I needed to terminate the screen lock process manually. So I go over to another virtual terminal and try to log in. As soon as I enter my user name, a bunch of errors come up and I am unable to log in. "This can't be good" I think to myself, and reboot.
I am greeted by this error upon booting: The error says that it says it cannot find /sbin/init. I loaded up a Ubuntu live CD and verified that /sbin/init is indeed present and all my other files still seem to be there. I tried booting into arch fallback on grub but that didn't work either. Midway through the day I SSHed my desktop from my phone and started it doing an upgrade. I was able to login.
I am trying to install linux kernel manually, for this I had compiled linux-2.6.36 with minimum drivers and features. Note that ext2, ext3, jffs file system support and sd ata_piix drivers are set as inbuilt kernel modules.
I had two hard disk for my Intel x86 box sda and sdb. I have running linux on sdb from which I can access sda. sda has one partition sda1 as ext3 fs.
I had created following directories at sda1 root, bin, boot, etc, sbin
After compiling kernel, I had copied bzImage, system map files to boot folder. then using 'grub-install' I had installed grub on sda. after installation I edited grub.conf to setup kernel image.
grub.conf
Code:
After this I booted sda by changing HDD boot priorities,And wow I got grub prompt -- linux kernel booted but as soon as it tries to mount file system it dies with error,
Code:
I accept that I dont have binaries for init and no initialization stuff in /etc, but I think problem is I am not able to give correct rootfs to kernel.
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.
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?
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.
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.
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.
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 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?
I installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
I have a recent install of ubuntu 10.10 on a brand new rig, and everything appears to be working properly but I get these 2 errors during bootup that seem to make the book process take a bit longer than expected but haven't actually noticed a problem in performance.
I have been unable to find a site with information on what err -22 means. From what little I have found on the issue it seems to be something with the usb 3.0 hubs on the back of my motherboard?
