Newb: generic Kernel install. Here's where I'm at.....

joutlancpa · 04-15-2009, 05:27 PM

Here is my lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda3
  label = Windows
  table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-2.6.27.7-smp
  initrd = /boot/initrd.gz
  root = /dev/sda5
  label = Slackware_Linux
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda5
  label = Slack_Failsafe
  read-only
# Linux bootable partition config ends

brianL · 04-15-2009, 05:41 PM

I can't see anything seriously wrong with that. That warning about LBA32 can be stopped by putting lba32 in lilo.conf, I usually put it just before all the VESA settings. But that being missing wouldn't cause the problem you're having. It's a mystery to me.

joutlancpa · 04-15-2009, 05:48 PM

Quote:

Originally Posted by brianL

I can't see anything seriously wrong with that. That warning about LBA32 can be stopped by putting lba32 in lilo.conf, I usually put it just before all the VESA settings. But that being missing wouldn't cause the problem you're having. It's a mystery to me.

when trying to boot the initrd.gz at boot up, it keeps saying it cannot execute it, and cannot 'sync' ? however the installer kernel boots up just fine. I've got quarky hardware with this m4400 (in sig), and most distros I can't even get into X except Slack and any 'buntu derivative. Shouldn't it be a problem my command generated script? special settings I need? I'm lost.

brianL · 04-15-2009, 05:56 PM

I don't know much about the hardware side and BIOS, so I can't be any help with that. Somebody one this forum must know the answer.

bgeddy · 04-15-2009, 08:08 PM

Hi theziod. As brianL says your lilo.conf looks OK.

Just to be specific - when booting your generic kernel - does it say

Code:

Loading generic .....................................................
Bios Data Check succesful

then lines of kernel reporting or doesn't it get this far ? The thing is these first bits are from the initial ram disk and bits are loaded to support loading the rest of the kernal from the disk. What I'm trying to do is establish how far in the boot process it's getting.

At first sight it seems that it has a problem reading from the disk after the initrd which often can be fixed by messing with the ram disk. It's not an easy diagnostic process though !

Another angle is to boot to a known good kernel (huge) and check what hardware is being reported at boot up and in dmesg. The tricky part is, with the huge kernels loading the world at boot up, it's hard to see what's essential.

In any case all these fixes would mean messing with the initrd (adding modules) and/or recompiling the generic kernel to include something as built in. There are other avenues you may persue but it's all a bit involved !You may be best just sticking with the huge kernel. There's no big disadvantages to this.

joutlancpa · 04-15-2009, 08:46 PM

Quote:

Originally Posted by bgeddy

Hi theziod. As brianL says your lilo.conf looks OK.

Just to be specific - when booting your generic kernel - does it say

Code:

Loading generic .....................................................
Bios Data Check succesful

then lines of kernel reporting or doesn't it get this far ? The thing is these first bits are from the initial ram disk and bits are loaded to support loading the rest of the kernal from the disk. What I'm trying to do is establish how far in the boot process it's getting.

At first sight it seems that it has a problem reading from the disk after the initrd which often can be fixed by messing with the ram disk. It's not an easy diagnostic process though !

Another angle is to boot to a known good kernel (huge) and check what hardware is being reported at boot up and in dmesg. The tricky part is, with the huge kernels loading the world at boot up, it's hard to see what's essential.

In any case all these fixes would mean messing with the initrd (adding modules) and/or recompiling the generic kernel to include something as built in. There are other avenues you may persue but it's all a bit involved !You may be best just sticking with the huge kernel. There's no big disadvantages to this.

Yes, it gets that far as you say above, then about a page of entries before it panics....when it goes to load the initrd it panics....says it can't 'sync' or connect

amiga32 · 04-15-2009, 08:56 PM

I had the same problem with initrd. I just compiled ext3 into the kernel instead. Sorry its not really a solution, but if you find how to make it work I would like to hear it.

joutlancpa · 04-15-2009, 10:20 PM

how could I go about starting with the Huge kernel, and building DOWN?

EDIT: A Slacker on this forum said he eliminated the need for a ramdisk but sounded complicated for me...can anyone suggest some ram disk settings? Is anyone else using a DELL Laptop?

amiga32 · 04-15-2009, 10:59 PM

Quote:

A Slacker on this forum said he eliminated the need for a ramdisk but sounded complicated for me

when you edit your kernel configuration, all you have to check the ext3 filesystem to be built into the kernel instead of as a module. Its actually really simple

joutlancpa · 04-15-2009, 11:15 PM

Quote:

Originally Posted by amiga32

when you edit your kernel configuration, all you have to check the ext3 filesystem to be built into the kernel instead of as a module. Its actually really simple

Could you draw a picture for me? I'm still in a steep learning phase....I would very much appreciate that!

Also, these guys are installing Slack 12.2 on my machine...wonder what kernel they are using? http://www.emperorlinux.com/systems/...details&id=524

amiga32 · 04-16-2009, 12:31 AM

Quote:

Originally Posted by thezoid

Could you draw a picture for me? I'm still in a steep learning phase....I would very much appreciate that!

Also, these guys are installing Slack 12.2 on my machine...wonder what kernel they are using? http://www.emperorlinux.com/systems/...details&id=524

Follow Alien BOB's guide for building a new kernel for anything you are unsure of.

You will find ext3 options under Filesystem options when configuring your kernel. That guide even has a section about it.

brianL · 04-16-2009, 05:48 AM

If everything's working OK with the huge kernel, do as bgeddy suggests and stick with that.

joutlancpa · 04-16-2009, 12:45 PM

Quote:

Originally Posted by brianL

If everything's working OK with the huge kernel, do as bgeddy suggests and stick with that.

Well, I was getting some funky behaviour in VirtualBox, with some usb devices working, like my scanner, and some not, like my usb keypad!! I thought something might be going on there with all those daemons and services running....?

joutlancpa · 04-18-2009, 12:55 PM

I'm going to resurrect this thread and thank everyone like bgeddy and BrianL for their help. I've stuck with Stable after some thought, and built my own kernel per Alien Bob's guide. I pretty much followed his suggestions like building in ext3 etc plus I built in Dell Laptop support (don't know if that helped or what) and was very careful about leaving things alone. This is the stock generic kernel I customized. I rebuilt my Nvida driver, and voila I'm "Back In Slack".

Question: why did I need that initial ram disk in the first place, because it was easier? Because now I'm booting without one....I'm trying to understand all this rather than be a 'cut and paste 'parrot'

thanks !! john