I am going to change my hardware soon, just a new motherboard and cpu, same sound card,gfx card and other stuff. Will it boot and run ok ( like a live cd/dvd) until I have time to do a reinstall or does it have specific ports the hardware is installed on now?
View 6 Replies
I am trying to figure out how to load the generic kernel in Grub2.
I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output:
Code:
Why this will not load.
One thing I always do is switch to the vmlinuz-generic(-smp) kernel in /etc/lilo.conf and build an initrd (see /boot/README.initrd for details). The "huge" kernel used by default is only meant for installing and not recommended for everyday use. It has a lot of drivers you don't need built-in and uses more RAM than the "generic" kernels.
still trying to find my feet and get to know Slackware. In one of my previous threads, 'things to do after installing' i was told the above message. When i installed, it used the huge kernel, but i'm unsure if that was the one that got installed. when i start slackware up, above the login screen it say, �wecome to Linux 2.6.37.6-smp (tty1)� I was wondering how to swich to the generic smp kernel, do I just change the vmlinuz to the desired, in lilo?
I've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors:
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted)
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh
mkinitrd -c -k 2.6.33.1 -f ext4 -r /dev/sda2 -m usbhid:ehci-hcd:ext4 -o /boot/initrd.gz
2. my root fs is ext4 on /dev/sda2
3. I've changed all necessary links in /boot
4. I've changed my /etc/lilo to:
image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sda2
label = Linux-Generic
read-only
I was interested in the idea of the btrfs subvolumes, so I made a virtual machine and installed Slackware as per the instructions here: [URL] It all went very well, but when I tried to switch from the huge kernel to the generic kernel and use the initrd.gz generated from step 29 (except that I used 2.6.37.4-smp instead of whatever's there) in lilo.conf, it failed to boot. I also noticed that in the instructions themselves, the poster doesn't actually add the initrd.gz to lilo.conf, so I'm guess the huge kernel has everything it needs to boot properly.
View 13 Replies View RelatedI've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
View 14 Replies View RelatedMy 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?
i'm attempting to configure the vmware server on the above mentioned system,without luck.i can't get the vmmon to compile. I have tried this out-dated guide [URL] but no luck. I have setup made the necessary links as explained in this guide [URL] I haven't managed to try out the any-any patch since no link to the patch is alive anymore.Since slack 13.37 is using 2.6.37.3 kernel I wonder if anyone has found a way to compile the vmware modules on these recent kernels.
View 12 Replies View RelatedI 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'm currently trying to setup Slackware 13.7 on a server, using software RAID 1. I'm using the README_RAID.TXT document at the root of the Slackware disc as a reference. Anyway, here's what I have so far.
/dev/md1 -> /boot partition
/dev/md2 -> swap partition
/dev/md3 -> / partition
Code:
[root@raymonde:~] # fdisk -l /dev/sd{a,b}
Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
[code]....
I created an initrd image using mkinitrd -F, added an according stanza to /etc/lilo.conf and ran 'lilo' after that. Now I can boot on the vanilla huge kernel all right. But I can't seem to boot on the generic kernel. Whenever I try to do this, the boot process stops short on the following error message:
Code:
mount: mounting /dev/md3 on /mnt failed: Device or resource busy
ERROR: no /sbin/init found on rootdev
I want to compile a custom kernel, because I need a path for a device. Here is what I've done:
Code:
$ cd /media/work/temp/
$ apt-get build-dep --no-install-recommends linux-image-$(uname -r)
$ apt-get source linux-image-$(uname -r)
$ cd linux-2.6.31
[Code].....
What is the difference between those kernels that you can install from this PPA:
[URL]
ppa:kernel-ppa/ppa
...which currently has 2.6.35-19.25-generic
AND
[URL]
...which currently has 2.6.35.3-maverick (even has later version 2.6.36-rc2-maverick)
AND
[URL]
...which currently has 2.6.35.3 (even has later versions 2.6.36-rc2 and 2.6.36-rc2-git4)
Are they the same? Which is newer? Is 2.6.35-19-generic = 2.6.35.3?
Just installed the patches/upgrades for the 2.6.35.30 kernel. Ubuntu will not boot without me typing "y" and hitting enter and later hitting the enter key again. Just have a blank screen unless I do this. Discovered what to do by booting into recovery mode. Had to make a display selection. Just guess at the enter key the second time the boot process stopped. I new to Ubuntu so don't know where to look in the logs to provide additional information to help trouble shoot the problem. If some one can guide me as to where to look I'll post log info. Hope this is the right place to post this. If I need to make a bug report let me know.
Forgot to add: HP Pavalion dv5000 (dv5020us to be specific). AMD Turion64 processor. ATI Radeon Mobility 200M video.
I was previously using kernel-huge until a slackware update caused some problems for me, so I switched over to kernel-generic but now I'm wondering if it uses both of my cpus on my dual core processor.
View 1 Replies View RelatedWhich cataloging app would you recommend? I have ebooks in pdf, chm, epub etc. Currently testing tellico. Tags fetching and auto opening the book would be a bonus.
View 2 Replies View RelatedI'd like to compile a generic kernel for my netbook on my desktop. They are both F12 64bit. On my desktop can I do:
make xconfig
make
make modules_install
Then copy the folder to my netbook then:
make install? Is there a better way? I don't really want to make .rpms.
I reported a bug at [URL].., then I had been asked to test the latest generic kernel in order to test whether the bug exist in latest kernel or not. I had read the information at [URL]... I installed the most current version of generic kernel. After that, I restart my computer and try to use the latest installed kernel. Then, the laptop freeze. Then, I restart my computer by turning off and on again, select the older kernel, successfully boot into Ubuntu to post this thread. What can I do since I am required to test the latest generic kernel?
View 2 Replies View RelatedI installed Mint 9 and directly after installation there were updates to download and install, which I did. One of the updates is a newer kernel, 2.6.32-24-generic.
When I manually install the nVidia driver 256.44 and restart gdm it works. When I reboot I land in low resolution, have to remove and re-install the older (195.36) driver through "Hardware Drivers". Somehow the new kernel and the latest nVidia don't match together. Am I the only one suffering from this or are there more people with this problem,and what to do about it?
I just noticed I'm not running with the latest kernel.
This box was originally installed as Ubuntu 10.04, then upgraded to 10.10.
I just recently noticed that, even though kernel 2.6.35-24-generic is installed, this box seems to insist on booting up with 2.6.32-24-generic.
Looking at /boot/menu.lst, it looks ok. (default is 0, and first kernel in list is 2.6.35-24. 2.5.32-24 is the *last* one in the list!)
Trying to compile Kernel 2.6.35 on Ubuntu 9.10 (2.6.31-14-generic).
got: The UTS Release version in include/linux/version.h""
does not match current version:
"2.6.35-xxx"
Please correct this
make[1]:***[debian/stamp/install/linux-image-2.6.35-xxx] Error 2
make[1]:***leaving directory `/usr/src/linux-2.6.35'
make:*** [kernel_image] Error 2
Can any one tell me what should I do? Is this Ok for using the compiled vmlinux image?where can I find the correstponding initrd file if this kernal compile is Ok?
I've recently upgraded from Ubuntu 9.04 Server edition to Karmic Koala 9.10 server.Earlier when I ran uname -r it showed: KernelVersion-serverNow the current version I've upgraded to shows 2.6.31-20-generic-pae.Should the Ubuntu server edition be using a generic-pae kernel?
View 9 Replies View RelatedMy sound was working in the past, but since I upgraded to kernel 2.6.31-20, it's no longer working. I am using Ubuntu on a Macbook and followed instructions from the Macbook 6,1 wiki on [URL]... I just installed the lastest alsa-driver using the following commands:
[code]...
I installed Ubutnu 9.10 Server on my Dell Server for LAMP & OpenSSH server. After the install was complete, I noticed the the kernel installed on the server was 2.26.31-14-generic instead of 2.26.31-14-server.I am wondering why would generic kernel be installed from ubuntu-server 9.10 cd? And how do go about chaning to server kernel? Or do I even need to do that? Would generic kernel work as server kernel ?
View 2 Replies View RelatedI have problem with my laptop, the last week I update my kenel to 2.6.32-24-generic-pae and in this moment the wireless drive dosen't work.
View 1 Replies View RelatedI did the kernel update via Update Manager today. Unfortunately , after this , disaster happened whereby sh.grub> prompt appeared on screen.
I got no idea how to rescue or repair the grub. I installed Ubuntu 9.10 in my E: under Windows 7 partition and labeled as "ubuntu". It has dual boot capability.
This week my ubuntu 10.10 was updated via update center. I obtained the new kernel headers 2.6.35-23-generic but now I can't boot using this kernel version and I have to select manually 2.6.35-22-generic in grub. I can see the ubuntu plymouth splash screen but it never rise gnome. where are the boot logs and how to activate them, In /var/log/ I have "boot" file but is empty and in "boot.log" I cant see any usefull information (I have BOOTLOGD_ENABLE=yes in /etc/defaul/bootlogd).
View 4 Replies View RelatedI'm on Ubuntu 10.10 - fresh install 2 days ago, I marked all packages for upgrade in Synaptic, everything upgraded except 'linux-image-2.6.35-22-generic' kernel image. Now everytime I use apt-get or synaptic it takes ages as it tries to update the kernel image every time. The error I am receiving is as follows:
[Code]....
Where can I get a copy of the 2.6.33.4 config that comes with Slackware? Also, can I get a binary of the kernel, the one that comes with Slackware 13.1?
View 14 Replies View RelatedI have installed Slack 13.37 for test on VMware. I installed just all - also all avalible distro. kernel imiges:
Code:
vmlinuz-generic-2.6.37.6
vmlinuz-generic-smp-2.6.37.6-smp
vmlinuz-huge-2.6.37.6
vmlinuz-huge-smp-2.6.37.6-smp
and the default is vmlinuz-huge-smp-2.6.37.6-smp.
Im trying to switch to vmlinuz-generic-2.6.37.6 So, what I did:
fs = ext4
root fs = /dev/sda1
Code:
/boot# mkinitrd -c -k 2.6.37.6 -m ext4 -f ext4 -r /dev/sda1
Edited lilo: pointing new image, lilo command executed. Every time I start new kernel i got this error: [URL]
Upgraded to latest kernel 2.6.32-23. Ubuntu 10.04 I run a twinview video configuration of 2 screens @ 1920x1200. On booting, X wanted to go to low res for the session, which reverted to one screen (that is, I lost the twin view), but actually kept the 1920x1200 res on the one. I restarted X on got both screen working with the second as a replica of the first. Something has changed in this version of the kernel. Reverted to the previous Kernel version (22) and all is sweet (twin view is back working). But this can only be a temporary workaround.
View 9 Replies View Related
