hiho,
did you try to boot with knoppix (livecd)? it has a kernel, which boot on the
most hardware and maybe you will see some interresting kernel messages.
/*veit*/
Am Mittwoch 16 März 2005 23:34 schrieb Glenn Meyer:
> Thank you for your reply!
>
> I shut down everything in the BIOS that had an option to do so. Still
> wouldn't boot. Left all turned off. In the Grub GUI, I added vga=none
> 3 so the line reads....
>
> kernel /vmlinuz-2.4.21-27.EL ro root=LABEL=/ vga=none 3
>
> then hit enter to accept the modification and "b" to boot. It only gets
> a few lines and says...
> Booting command-list
> root (hd0,1)
> Filesystem type is ext2fs, partition type 0x83
> kernel /vmlinuz-2.4.21-27.EL ro root=LABEL=/ vga=none 3
> [Linux-bzImage, setup=0x1400, size=0x12f50a]
>
> Error 23: Error while parsing number
>
> Press any key to continue... (when I do it goes quickly back to Grub)
>
>
> For partitions, I had created
> swap (512MB)
> /boot (100MB ext3)
> / (8+MB ext3)
>
>
> Any other thoughts? I'm open to options (nothing to lose yet) and do
> appreciate your help! Thank you!
>
> Kwan Lowe wrote:
> > Glenn Meyer wrote:
> >> I have a Compaq Armada M700 (laptop) that I am installing Red Hat WS
> >> 3.0 on. The install goes very smoothly until the reboot. Very early
> >> in the boot process, the system hangs every time immediately
> >> following....
> >>
> >> "Total HugeTLB memory allocation, 0"
> >>
> >> Googling hasn't produced anything I can comprehend. I find nothing
> >> on Red Hat's site. Any thoughts or suggestions? Thank you!
> >
> > Have you checked this site:
> > http://www.linux-on-laptops.com/compaq.html
> >
> > The quirks seem mostly related to video. Try booting in runlevel 3. At
> > the boot prompt you'd add:
> > vga=none 3
> >
> > Do this at the end of whatever kernel is your default. It's probably
> > GRUB running, so at the GRUB screen select the kernel line, 'e' to
> > edit, add the above, press Enter, then 'b' to boot it.
> >
> > If this works try looking at video settings.
> >
> > If you still have a problem, drop into the BIOS and start turning off
> > stuff such as sound, USB, etc.. THen turn them back on one-by-one to
> > see if you can boot.
> > -----------------------------------------------------------------------
> > This list is provided as an unmoderated internet service by Networked
> > Knowledge Systems (NKS). Views and opinions expressed in messages
> > posted are those of the author and do not necessarily reflect the
> > official policy or position of NKS or any of its employees.
>
> -----------------------------------------------------------------------
> This list is provided as an unmoderated internet service by Networked
> Knowledge Systems (NKS). Views and opinions expressed in messages
> posted are those of the author and do not necessarily reflect the
> official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:13:31 EDT