slack 12, switch to generic kernel from huge kernel, using grub?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
slack 12, switch to generic kernel from huge kernel, using grub?
I am trying to switch from using the default installed huge kernel to the generic kernel.
I have read the recent posts on here that reference the dropline gnome kernel guide, and i have searched for grub related posts on this topic. i just need some help interpreting if possible.
here is what i have done so far...
i performed a full install of slackware 12 which means, i think, that i have all of the required kernel packages installed for a simple switch of the kernel.
now i read that the symlinks in /boot for vmlinuz, system-map and config are just to simplify scripting of the boot process (or some such) and it is ok to directly reference the files which are to be used at boot by the boot loader.
so therefore as i am using grub, i thought i could just write a new stanza in grub to call the generic kernel files like so...
Code:
# The backup copy of the MBR for drive '/dev/hda' is
# here '/boot/grub/mbr.hda.4267'. You can restore it like this.
# dd if=mbr.hda.4267 of=/dev/hda bs=512 count=1
#
# Start GRUB global section
timeout 10
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Linux huge 2.6.21.5 smp
root (hd0,1)
kernel /boot/vmlinuz root=/dev/hda2 ro vga=773
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux generic 2.6.21.5 smp
root (hd0,1)
kernel /boot/vmlinuz-generic-smp-2.6.21.5-smp root=/dev/hda2 ro vga=773
initrd /boot/initrd.gz
# Linux bootable partition config ends
# title --- For help press 'c', type: 'help'
# root (hd0)
# title --- For usage examples, type: 'cat /boot/grub/grub.txt'
# root (hd0)
as you can see, i think i created an initrd using the following command..
and it appears to be in the boot directory. I am also calling the initrd in the grub entry.
now when i boot up i seem to have a choice of the 2 kernels in my grub menu and both actually do boot the os, but i am sure i am still booting the huge kernel as the dmesg files from each of the different boot options are identical, and uname-r in both boot options gives the same result of...
Code:
2.6.21.5-smp
can someone tell me where i am misunderstanding all the guides and manuals i am reading please?
It's pretty self explanatory! The "boot/vmlinuz" defines what kernel is going to be booted. vmlinuz by popular convention is usually a symbolic link to the actual kernel file. this practice allows you to change your kernel configuration by changing your symbolic link (inside das boot) and not have to re-edit your lilo/grub files. In your setup both your boot entries point to the same generic kernel.
are you sure your huge kernel is booting up, perhaps if you posted your dmesg that might help!
[Disclaimer]
I really don't know much about grub, /var/log/*, or kernels. So I may be completely off base here.
[/Disclaimer]
The uname -r output would be correct for both kernels I believe (because they are both 2.6.21.5-smp kernels) the same goes for your dmesg output (I think dmesg reads from /var/log/messages) you probably will have different messages in some spots of /var/log/syslog however, because with the "huge" kernels there would have been some ugly error messages regarding kernel modules that aren't there, or aren't necessary... I'm not at my Slackware box, otherwise I could be more specific.
I think the easies way to tell if your switch was sucessful would be to look at lsmod. if you're running the generic kernel you will have a lot of modules listed, if running the huge kernel, not so many
In short, it looks like from your post that you have properly changed over to the generic slackware kernel. If your lsmod for both boot options is not different, I appologise!
Again, the only difference as far as I know between the two kernels is that in one, almost everything is built in, and in the other, almost everything is a module. therefore, the only difference you will see when booting is in the section relevant to loading modules.
another way you could double check is to only have one entry in your menu.lst , that way you can be certain that the only possible kernel you could be using is the one you specify. (if it fails you can fairly easily use the edit command ('e' I believe) to remove references to the initrd and point grub at the huge kernel and boot from there. It's really easy as I recall.)
Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #1 SMP Tue Jun 19 14:52:25 CDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000e0000 size: 0000000000020000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000000fec0000 end: 000000000ffc0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000ffc0000 size: 0000000000038000 end: 000000000fff8000 type: 3
copy_e820_map() start: 000000000fff8000 size: 0000000000008000 end: 0000000010000000 type: 4
copy_e820_map() start: 00000000ffb80000 size: 0000000000080000 end: 00000000ffc00000 type: 2
copy_e820_map() start: 00000000fff00000 size: 0000000000100000 end: 0000000100000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000ffc0000 (usable)
BIOS-e820: 000000000ffc0000 - 000000000fff8000 (ACPI data)
BIOS-e820: 000000000fff8000 - 0000000010000000 (ACPI NVS)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
255MB LOWMEM available.
Entering add_active_range(0, 0, 65472) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 65472
HighMem 65472 -> 65472
early_node_map[1] active PFN ranges
0: 0 -> 65472
On node 0 totalpages: 65472
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 479 pages used for memmap
Normal zone: 60897 pages, LIFO batch:15
HighMem zone: 0 pages used for memmap
DMI 2.3 present.
ACPI: RSDP 000FF980, 0014 (r0 AMI )
ACPI: RSDT 0FFF0000, 002C (r1 DELL ZUUL 20010703 MSFT 1011)
ACPI: FACP 0FFF1000, 0074 (r1 DELL ZUUL 20010703 MSFT 1011)
ACPI: DSDT 0FFE0000, 2DEB (r1 D815EA EA81510A 12 MSFT 100000B)
ACPI: FACS 0FFF8000, 0040
ACPI: BOOT 0FFF4000, 002B (r1 DELL ZUUL 20010703 MSFT 1011)
ACPI: PM-Timer IO Port: 0x408
Allocating PCI resources starting at 20000000 (gap: 10000000:efb80000)
Built 1 zonelists. Total pages: 64961
Kernel command line: root=/dev/hda2 ro vga=773
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (0120a000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Detected 997.050 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 254260k/261888k available (2658k kernel code, 7056k reserved, 1046k data, 268k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffe17000 - 0xfffff000 (1952 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xd0800000 - 0xff7fe000 ( 751 MB)
lowmem : 0xc0000000 - 0xcffc0000 ( 255 MB)
.init : 0xc04a6000 - 0xc04e9000 ( 268 kB)
.data : 0xc039892d - 0xc049e374 (1046 kB)
.text : 0xc0100000 - 0xc039892d (2658 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1995.50 BogoMIPS (lpj=3991004)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 14k freed
ACPI: Core revision 20070126
ACPI: setting ELCR to 0200 (from 0e08)
CPU0: Intel Celeron (Coppermine) stepping 0a
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfda95, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0500-053f claimed by ICH4 GPIO
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
libata version 2.20 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:0b: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0b: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0b: iomem range 0x100000-0xfffffff could not be reserved
pnp: 00:0b: iomem range 0x0-0x0 could not be reserved
Time: tsc clocksource has been installed.
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: fc900000-fe9fffff
PREFETCH window: e4600000-f46fffff
PCI: Bridge: 0000:00:1e.0
IO window: d000-dfff
MEM window: fea00000-feafffff
PREFETCH window: f4700000-f47fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 98304 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 457k freed
Simple Boot Flag at 0x7a set to 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
vesafb: framebuffer at 0xe8000000, mapped to 0xd0880000, using 1536k, total 32768k
vesafb: mode is 1024x768x8, linelength=1024, pages=4
vesafb: protected mode interface info at c000:c2c0
vesafb: pmi: set display start = c00cc305, set palette = c00cc38a
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003 d103 d203 d303 d403 d503 da03 ff03
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Switched to high resolution mode on CPU 0
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
input: Macintosh mouse button emulation as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 2
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:DMA
Probing IDE interface ide0...
hda: Maxtor 2B020H1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdd: SAMSUNG SC-140B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39062500 sectors (20000 MB) w/2048KiB Cache, CHS=38752/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 hda3
hdd: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
Loading iSCSI transport class v2.0-724.
usbmon: debugfs is not available
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 312 MB/s
raid6: int32x2 353 MB/s
raid6: int32x4 285 MB/s
raid6: int32x8 274 MB/s
raid6: mmxx1 931 MB/s
raid6: mmxx2 1136 MB/s
raid6: sse1x1 387 MB/s
raid6: sse1x2 1094 MB/s
raid6: using algorithm sse1x2 (1094 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 2074.000 MB/sec
raid5: using function: pIII_sse (2074.000 MB/sec)
md: multipath personality registered for level -4
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 268k freed
input: AT Translated Set 2 keyboard as /class/input/input1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
iTCO_wdt: Found a ICH2 TCO device (Version=1, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Linux agpgart interface v0.102 (c) Dave Jones
intel_rng: Firmware space is locked read-only. If you can't or
intel_rng: don't want to disable this in firmware setup, and if
intel_rng: you are certain that your system has a functional
intel_rng: RNG, try using the 'no_fwh_detect' option.
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 10, io base 0x0000ef80
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
agpgart: Detected an Intel i815 Chipset.
agpgart: AGP aperture is 64M @ 0xf8000000
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usb 1-2.1: new full speed USB device using uhci_hcd and address 3
usb 1-2.1: configuration #1 chosen from 1 choice
Linux Tulip driver version 1.1.14 (May 11, 2002)
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKF] -> GSI 3 (level, low) -> IRQ 3
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
tulip0: MII transceiver #1 config 3100 status 7809 advertising 01e1.
eth0: Davicom DM9102/DM9102A rev 49 at MMIO 0xfeaffc00, 00:80:AD:78:BB:D2, IRQ 3.
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.3.2)
ath_pci: 0.9.4.5 (0.9.3.2)
ACPI: PCI Interrupt 0000:02:0d.0[A] -> Link [LNKF] -> GSI 3 (level, low) -> IRQ 3
ath_rate_sample: 1.2 (0.9.3.2)
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.8 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0xfeae0000, irq=3
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 11 (level, low) -> IRQ 11
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
Adding 499928k swap on /dev/hda1. Priority:-1 extents:1 across:499928k
EXT3 FS on hda2, internal journal
input: PC Speaker as /class/input/input2
input: ImPS/2 Generic Wheel Mouse as /class/input/input3
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
Capability LSM initialized
scsi 0:0:0:0: Direct-Access Maxtor 6 L200P0 BAH4 PQ: 0 ANSI: 0
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
sda: sda1 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: Attached scsi disk sda
usb-storage: device scan complete
sd 0:0:0:0: Attached scsi generic sg0 type 0
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
truthfatal... i was wondering that about the uname -r command, as both kernels are built from the same source i wondered if their would be a distinction with this command?
and thanks for the tip about lsmod, i will do a comparison now, just to be sure.
It's pretty self explanatory! The "boot/vmlinuz" defines what kernel is going to be booted. vmlinuz by popular convention is usually a symbolic link to the actual kernel file. this practice allows you to change your kernel configuration by changing your symbolic link (inside das boot) and not have to re-edit your lilo/grub files. In your setup both your boot entries point to the same generic kernel.
are you sure your huge kernel is booting up, perhaps if you posted your dmesg that might help!
- perry
Hi,
Quote:
Originally Posted by perry
In your setup both your boot entries point to the same generic kernel.
Perry, I don't use Grub but if you look at the 'OP's' output for '/boot' the user is using different kernels for his menu.
having slept on it, and then reviewing the two dmesg files this morning, i am convinced i am booting the generic kernel.
the generic dmesg is 75 lines shorter than the huge dmesg, there are no -EEXIST errors in the generic and most of the differences appear to be focussed on unrequired hardware support being loaded.
as a test i also deleted the initrd.gz file and tried to boot the generic option. the boot failed, but after i recreated the initrd it worked.
finally i think i understand how to switch around between existing kernels on my machine.
as a side note, i am sure many people are using different versions of the same kernel source at any given time (ie 2.6.22.5-huge or 2.6.22.5-generic or 2.6.22.5-custom compiled). Is this comparison between modules loaded, or dmesg files the best way to know which 2.6.22.5 kernel one is using at any given time. is there not a command similar to uname -r or an option for that command to highlight which of the kernels stored in /boot is being used?
finally i think i understand how to switch around between existing kernels on my machine.
That's good! Be sure too keep a known working kernel in a stanza within your 'lilo.conf' or 'grub menu' to allow recovery in case of some error(s). I set up some systems with recovery methods;
Code:
excerpt from 'lilo.conf';
loki:~# cat /etc/lilo.conf |less
# << Stanza examples>>
# Windows bootable partition config begins
other = /dev/hda1
label = Windows98
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.31
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
#
#
#03-06-6 18:15 gws
#
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.15.3a
root = /dev/hda3
label = Lnx26153a
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
#boot 2.6.15.3a as single
#to allow maintenace
image = /boot/vmlinuz-2.6.15.3a
append = "single"
root = /dev/hda3
label = L26_single
read-only
# Linux bootable partition config ends
The above is from a small laptop control system that is using Slackware 11. Notice the different stanza for the boot(s).
Quote:
Originally Posted by jaguarrh
i am sure many people are using different versions of the same kernel source at any given time (ie 2.6.22.5-huge or 2.6.22.5-generic or 2.6.22.5-custom compiled). Is this comparison between modules loaded, or dmesg files the best way to know which 2.6.22.5 kernel one is using at any given time. is there not a command similar to uname -r or an option for that command to highlight which of the kernels stored in /boot is being used?
That is what the 'uname [OPTION]' is for! I'm sure the '2.6.22.5-huge' you are referring to is a typo since your 'dmesg' output shows 'Linux version 2.6.21.5-smp'.
Quote:
excerpt 'man uname'
UNAME(1) User Commands
NAME
uname - print system information
SYNOPSIS
uname [OPTION]...
DESCRIPTION
Print certain system information. With no OPTION, same as -s.
-a, --all
print all information, in the following order, except omit -p
and -i if unknown:
-s, --kernel-name
print the kernel name
-n, --nodename
print the network node hostname
-r, --kernel-release
print the kernel release
I suggest you use the 'man' to get some useful information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
