There has been some mention of booting UEFI systems in
this thread. This appears to be a comprehensive resource:
http://www.rodsbooks.com/efi-bootloaders/index.html
Many bootloaders are covered, and the author also
mentions his own project, rEFInd
http://www.rodsbooks.com/refind/
cheers
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
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 video adapter in use in the present system.
(nb. I wasn't actually able to follow through
Why do you like a
>> > seperate boot partition?
>>
>> yes, many bootloaders (aboot, silo, lilo) can only read ext2.
>
> Regards LILO, incorrect.
>
> LILO doesn't read ext2. Or any other filesystem.
>
> It directly addresses the kernel by raw disk hardware
on Mon, Dec 01, 2003 at 09:41:21PM -0500, Tom Vier ([EMAIL PROTECTED]) wrote:
> On Mon, Dec 01, 2003 at 03:39:16PM -0800, Mark Ferlatte wrote:
> > Is there any need for a /boot partition on modern hardware? Why do you like a
> > seperate boot partition?
>
> yes, many boo
I'm about to start installing Debian 2.2r2. How does debian deal with
bootloaders? Will it allow me to install lilo or other on a floppy so that I
don't have to deal with bootloaders on my harddrive or entries in my mbr. I run
windows as my primary and linux as the secondary. Mandrake
Greetings yet again Dusers,
I have been asked by our Physics Dept. to carve up a win box and install
the one true OS on it. I recall reading a while ago that there was an up
and comming nice replacement (functionally) to fips. Unfotunately I
don't recall the name off hand. Any body know what I am t
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
> ^
>
-BEGIN PGP SIGNED MESSAGE-
Hi all again
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:
This is one of the parameters I want to modify:
nfsaddrs=147.156.10.20:147.156.17.31:147.156.1.11:255.255.128.0:eth0
13 matches
Mail list logo
