Out of necessity to have a working system ASAP, I installed Ubuntu
which has the same problem, but does all the installation from the
blue screen which I can see. Now when I boot up, the screen goes
blank when GRUB should appear, and stays blank until the graphical
part of the boot-up. I will try
Levi Waldron wrote:
[...] I ran the "stable" install disc again,
specifying "linux vga=ask" at the boot prompt. It offered me the
choice to scan all available vesa modes, and *nothing* showed up on my
screen during the scan.
This seems to be equivalent to a bug that has been reported and
resolv
On Fri, 24 Mar 2006 23:00:20 +
"Levi Waldron" <[EMAIL PROTECTED]> wrote:
> 2006/3/24, Andrew Sackville-West <[EMAIL PROTECTED]>:
> > it probably is booting. you've got the wrong video mode for your setup. you
> > should probably specify vga=ask in the kernel line of your boot also, this
> >
2006/3/24, Andrew Sackville-West <[EMAIL PROTECTED]>:
> it probably is booting. you've got the wrong video mode for your setup. you
> should probably specify vga=ask in the kernel line of your boot also, this
> seemed appropriate:
>
> http://72.14.203.104/search?q=cache:iz_Ho_51kzoJ:www.linux-mag
On Fri, 24 Mar 2006 18:26:39 +
"Levi Waldron" <[EMAIL PROTECTED]> wrote:
> At least, I think that's what the problem is after installing lilo on
> on the the HD partitions, by booting a live CD then using chroot.
> liloconfig gave me the following warning:
>
> Warning: Unable to determine vi
Hi Ulysses,
On 22-Sep-98 Ulisses Alonso Camaro wrote:
>
> I would like to know if there is a boot loader wich allows to "modify"
> command line arguments at the prompt, this is what I want:
>
> nfsaddrs=147.156.10.20:147.156.17.31:147.156.1.11:255.255.128.0:eth0:none
> ^
>
6 matches
Mail list logo
