LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 09-07-2005, 09:19 PM   #1
elliotfuller
Member
 
Registered: Apr 2005
Location: San Francisco, CA
Distribution: Ubuntu, Debian
Posts: 83

Rep: Reputation: 15
Configuring LiLO Error 'Initial RAM disk.... and is too big to fit between 4M-15M..'


I booted Knoppix onto a machine with two blank hardrives. Did a RAID setup, etc. I am using the 2.4.27 Linux kernel and I did a debootstrap sarge to install Debian. I have my RAID drivers finally built into the kernel (a big step for me).


When I look at: /etc/lilo.conf

Code:
boot=/dev/md0
root=/dev/md0
lba32
read-only
image=/boot/vmlinuz-2.4.27
label=linux
When I run: knoppix#lilo

Code:
Warning: '/proc/partitions' does not exist, disk scan bypassed
Added linux *
The boot record of  /dev/md0  has been updated.
Knoppix:/usr/src/linux#
When I run: knoppix#lilo -q -v

Code:
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 12:32:32 on May 25 2005
Debian GNU/Linux

Warning: '/proc/partitions' does not exist, disk scan bypassed
Warning: mapfile created with no linear/lba32 option
Reading boot sector from /dev/md0
Installed:  Thu Sep  8 07:53:49 2005

Global settings:
  Delay before booting: 1510.0 seconds
  Command-line timeout: 1425.9 seconds
  Unattended booting
  Enter boot prompt only on demand
  Boot-time BIOS data saved
  Boot-time BIOS data auto-suppress write NOT bypassed
  Large memory (>15M) is NOT used to load initial ramdisk
  RAID installation
  Boot device WILL be used for the Map file
  Boot prompt can be accessed from COM95
  Boot prompt message is 25354 bytes
  No default boot command line
Images:
  51e0 T prepare_namespace
c0105310 T disable_hlt
c0105320 T enable_hlt
c0105330 T default_idle
c0105380 t poll_idle
c01053a0 T cpu_idle
c0105410 T machine_real_restart
c01054d0 T machine_restart
c01055e0 T machine_halt
c01055f0 T machine_power_off
c0105610 T show_regs
c0105760 T arch_kernel_thread
c01057a0 T exit_thread
c01057b0 T flush_thread
c01057f0 T release_thread
c0105850 T copy_thread
c01058f0 T dump_thread
c0105a10 T __switch_to
c0105ad0 T sys_fork
c0105b00 T sys_clone
c0105b30 T sys_vfork
c0105b60 T sys_execve
c0105be0 T get_wchan
c0105c6d t .text.lock.process
c0105c80 T __up
c0105ca0 T __down
c0105d60 T __down_interruptible
c0105e50 T __down_trylock
c0105ea4 T __down_failed
c0105eb0 T __down_failed_interruptible
c0105ebc T __down_failed_trylock
c0105ec8 T __up_wakeup
c0105ed4 T __write_lock_failed
c0105ef4 T __read_lock_failed
c0105f08 t .text.lock.semaphore
c0105f60 T copy_siginfo_to_user
c0106000 T sys_sigsuspend
c01060b0 T sys_rt_sigsuspend
c01061d0 T sys_sigaction
c01062e0 T sys_sigaltstack
c0106310 t restore_sigcontext
c0106450 T sys_sigreturn
c0106570 T sys_rt_sigreturn
c01066b0 t setup_sigcontext
c01067e0 t setup_frame
c0106a00 t setup_rt_frame
c0106cd0 t handle_signal
c0106e20 T do_signal
c01070e7 t .text.lock.signal
c0107148 T lcall7
c0107198 T lcall27
c01071e8 T ret_from_fork
c0107208 T system_call
c0107240 T ret_from_sys_call
c0107251 t restore_all
c0107260 t signal_return
c0107278 t v86_signal_return
c0107288 t tracesys
c01072ab t tracesys_exit
c01072b5 t badsys
c01072c4 T ret_from_intr
¸ *
    No password
    Boot command-line won't be locked
    Single-key activation
    VGA mode: 13109 (0x3335)
    Kernel is loaded "low"
    Initial RAM disk is 1634953572 bytes
       and is too big to fit between 4M-15M
Fatal: geo_comp_addr: Cylinder number is too big (12483 > 1023)
What am I to do?

Last edited by elliotfuller; 09-07-2005 at 09:26 PM.
 
Old 09-07-2005, 11:22 PM   #2
Matir
Moderator
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 117Reputation: 117
And it won't boot? I think lilo may be looking at a non-existant initrd and getting some arbitrary size with -q.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Lilo: kernel doesn't support initial ram disks. ecion Mandriva 22 07-22-2004 10:36 AM
Kernel too big to fit on floppy boot disk tacobill Red Hat 11 03-07-2004 12:21 AM
lilo ram disk error creznedmick Linux - Newbie 2 12-05-2003 06:13 AM
lilo error:linuxebda too big? saturn_vk Linux - General 3 02-23-2003 12:14 PM
64 RAM, LILO, and a boot disk.. help :( Volatile Linux - Newbie 2 02-23-2001 02:23 PM


All times are GMT -5. The time now is 03:11 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration