Hi, I did try it with 8MB, 16MB and 32MB RAM with the same results;The computers are i486 DX4 (100MHz); The bios doesn't have the memory hole option; and I can boot Linux from HD on these machines.
Could the source of trouble be initrd? Below is the relevant part of the boot process. Thanks, Cicero mknbi-1.2-6/first32.c (GPL) 16384 k total memory Ramdisk at 0X00F8F000, size 0X00071000 Uncompressing Linux.... Ok, booting the kernel Linux.................. BIOS-provided physical RAM map; BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 0000000000009fc00 - 0000000000a0000 (reserved) BIOS-e820: 0000000000100000 - 0000000000d80000 (usable) BIOS-e820: 000000000fec00000 - 00000000fed00000 (reserved) BIOS-e820: 000000000fee00000 - 00000000fef00000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) On node 0 total pages: 3456 Zone (0): 3456 pages Zone (1): 0 pages Zone (2): 0 pages initrd extends beyond end of memory (0X01000000 > 0X00d80000) disabling initrd . . . On Thursday 24 January 2002 12:51, you wrote: > Cicero, > > It should work with as little as 8mb of ram. > > Does the boot screen show that 16mb of ram was detected? > > Also, many of the older 486 computers had the ability > to set a "memory hole" in the 15th or 16th megabyte of > ram. > > make sure that setting is turned OFF. I've seen that > cause problems for initrd as well. > > Hope that helps, > > Jim. > > Cicero Mota wrote: > > Thanks Jim, > > > > It realy looks like a memory problem since the kernel disables initrd > > during the boot process complaining about not enough memory. I have three > > of these i486, all of them with 16 MB RAM and they suffer from the same > > problem. Although my i586 machines work fine with the same amount of ram. > > > > Cheers. > > > > Cicero > > > > On Wednesday 23 January 2002 17:55, you wrote: > >>Cicero, > >> > >>My first thought is probably not enough ram in > >>the workstation, but that's just a guess, because > >>I have no clue how much ram there is. > >> > >>You can hit the Shift-PageUp keys and scroll backwards > >>through the boot messages. Go all the way back > >>to where Etherboot hands control over to the kernel. > >> > >>You should see some information about the initrd, and > >>whether the kernel had a problem with the initrd. > >> > >>Jim McQuillan > >>[EMAIL PROTECTED] > >> > >>Cicero Mota wrote: > >>>Hi, > >>> > >>>I'm running a ltsp v3.0 server. The provided ltsp kernel > >>>(vmlinuz-2.4.9-ltsp-5) boots without any problems for pentia (i586), and > >>>amd machines but fails for i486 when it 's trying to mount ram0. These > >>>are the last lines shown during boot proccess: > >>> > >>>NET4: Unix domain socktes 1.0/SMP for Linux NET4.0. > >>>VFS: Cannot open root device "ram0" or 01:00 > >>>Please append a correct "root=" boot option > >>>Kernel panic: VFS: unable to mount root fson 01:00 > >>> > >>>Does anyone know how to correct this? > >>> > >>>Thanks. > >>> > >>>Cicero > >>> > >>>_____________________________________________________________________ > >>>Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > >>> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > >>>For additional LTSP help, try #ltsp channel on irc.openprojects.net _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
