Jordan Gordeev wrote:
> At present the amd64 kernel is loaded just above the first megabyte
> of physical memory.
Yes, I know, and the standard i386 kernel is loaded at 4 MB,
and the PAE kernel is loaded at 2 MB. It doesn't matter
much, though.
> I have no idea if the loader uses malloc()/fr
Oliver Fromme wrote:
Hello,
I've got a small question regarding $subject. I'm looking
at this code snippet from src/sys/boot/i386/loader/main.c:
#if defined(LOADER_BZIP2_SUPPORT) || defined(LOADER_FIREWIRE_SUPPORT)
heap_top = PTOV(memtop_copyin);
memtop_copyin -= 0x30;
heap_bot
Marcel Moolenaar wrote:
> On Feb 22, 2008, at 12:39 PM, Oliver Fromme wrote:
> > Yes, that'll work well for putting characters on the
> > screen. But I don't think it is suitable for generic
> > graphics operations, even (and especially) for drawing
> > single pixels.
>
> True. What do you
On Feb 22, 2008, at 12:39 PM, Oliver Fromme wrote:
At the same time the VGA driver is abstracted from any
high-level details, like fonts or character sets. This
means that it's easy to write an accelerated driver for
some graphics hardware. You simply implement mode
setting and bitblt and you're
Marcel Moolenaar wrote:
> [Oliver explains bitblit, then Marcel explains bitblt.]
OK, so we mean the same thing, bascially.
> The higher lever TTY code simply calls bitblt with a
> bit mask of the glyph to be printed and doesn't need to
> know about the details of the display. As such, simple
On Feb 21, 2008, at 2:09 AM, Oliver Fromme wrote:
Actually I don't plan to use a bitblit function at all,
because it's not really feasible in standard VGA modes.
What do you mean by that?
Maybe we have different understandings what bitblit means.
My understanding is that bitblit is a raster
Marcel Moolenaar wrote:
> On Feb 20, 2008, at 12:08 PM, Oliver Fromme wrote:
> > By the way: Will the standard i386 /boot/loader work
> > on an EFI machine, or does it require a different loader
> > binary?
>
> It needs a different loader. If you want to support EFI
> the right way, it als
On Wed, Feb 20, 2008 at 01:44:42PM -0800, Marcel Moolenaar wrote:
>control over everything. On top of that, we can't use any
>code in the loader from the kernel, so whatever support we
>add, we need to add to the kernel too.
We can't re-use the same executable bytes but, with care, we
should be ab
On Feb 20, 2008, at 3:44 PM, Marcel Moolenaar wrote:
That would be possible. But then there will be other
problems. For example, lets say that the i386 loader
decides to use 640x480 @4bit, and the sparc64 loader
decides that 1152x900 @8bit is "best".
The Forth code clearly needs a way to que
On Feb 20, 2008, at 12:08 PM, Oliver Fromme wrote:
By the way: Will the standard i386 /boot/loader work
on an EFI machine, or does it require a different loader
binary?
It needs a different loader. If you want to support EFI
the right way, it also needs a different kernel -- one
that respect
Marcel Moolenaar wrote:
> Oliver Fromme wrote:
> > I understand the "yes" part, but I do not understand the
> > "see (a)/(b)" part. :-) What does the recursive reference
> > mean?
>
> It means that they can be treated the same:
Ah, OK. It's clear to me now.
> > Just out of curiosity, w
On Feb 20, 2008, at 4:57 AM, Oliver Fromme wrote:
Marcel Moolenaar wrote:
Oliver Fromme wrote:
It will not replace the current text menu ("beastie.4th"),
so you can still use it on your Hercules monochrome or CGA
machine or with serial console, of course.
We can probably forget about those
Marcel Moolenaar wrote:
> Oliver Fromme wrote:
>
> > It will not replace the current text menu ("beastie.4th"),
> > so you can still use it on your Hercules monochrome or CGA
> > machine or with serial console, of course.
>
> We can probably forget about those configurations.
OK, maybe no
On Tuesday 19 February 2008 22:27, Marcel Moolenaar wrote:
> On Feb 19, 2008, at 11:43 AM, Oliver Fromme wrote:
> > It will not replace the current text menu ("beastie.4th"),
> > so you can still use it on your Hercules monochrome or CGA
> > machine or with serial console, of course.
On Feb 19, 2008, at 11:43 AM, Oliver Fromme wrote:
It will not replace the current text menu ("beastie.4th"),
so you can still use it on your Hercules monochrome or CGA
machine or with serial console, of course.
We can probably forget about those configurations.
This is a list of things tha
> You also can't dual boot without console access.
You can, I have a system triple booting without using
the console.
Method 1: boot through grub. Create shell scripts that
edit grub's menu.lst file.
Method 2: use fdisk(8) to change active partition.
With or without dual booting, if the least
Subject: Re: boot loader
On Fri, Oct 26, 2007 at 01:47:04PM -0700 I heard the voice of
Doug Barton, and lo! it spake thus:
>
> You could theoretically install onto a local system, tar it up, then
> unpack it in the unused partition on your remote machine, yes.
> However in order to set t
On Fri, Oct 26, 2007 at 01:47:04PM -0700 I heard the voice of
Doug Barton, and lo! it spake thus:
>
> You could theoretically install onto a local system, tar it up, then
> unpack it in the unused partition on your remote machine, yes.
> However in order to set the new slice bootable you'd have to
network.
Again appreciate your help.
Thomas
-Original Message-
From: Doug Barton [mailto:[EMAIL PROTECTED]
Sent: Friday, October 26, 2007 1:47 PM
To: Thomas Ching
Cc: freebsd-hackers@freebsd.org
Subject: Re: boot loader
FYI, for future reference this question is really more appropriate for
FYI, for future reference this question is really more appropriate for
[EMAIL PROTECTED]
On Fri, 26 Oct 2007, Thomas Ching wrote:
Hi, I am trying to do the following with existing systems running 4.5.
I'd really appreciate if anyone has any hints, pointers, opinions, or
even just "you should t
On Monday 27 June 2005 06:49 pm, Mike Meyer wrote:
> As reported here (I hope - the moderator got the message) and in
> -questions, I have a motherboard that installs just fine, but gets a
> "Can't work out which disk we are booting fromm" message when the
> installed os boots.
>
> Hacking boot/i38
yeah but there was no loader.old
so this is fix if you don't have the loader.old
regards,
Nexohrion
The user " John Baldwin" wrote this strange object...:
> On Wednesday 09 March 2005 09:59 am, Webmaster Shizukana.net wrote:
>> It's resloved, she edit the /boot/loader instead of /boot/loader.co
On Wednesday 09 March 2005 09:59 am, Webmaster Shizukana.net wrote:
> It's resloved, she edit the /boot/loader instead of /boot/loader.conf
>
> fix:
You can also just use /boot/loader.old to boot up and then cp loader.old to
loader.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.o
It's resloved, she edit the /boot/loader instead of /boot/loader.conf
fix:
if someone has freebsd release as you, let him upload it to a site, with
the name loader.x
then boot your computer with the fixit cd of freebsd (Disk 2)
Configure your Network
go to shell, then
cd /mnt
mkdir fixbsd
mount
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 Mar 2005, Webmaster Shizukana.net wrote:
Can somebody help me?
I've got a problem with my bootloader and i dont know how to fix it.
If I boot my pc, it stops loading, it says:
Invalid Format.
FreeBSD/i386-Release 5.3
default: 0:ad(0,a)/kernel
From: "Doug White" <[EMAIL PROTECTED]>
To: "Gemini Domino" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 15, 2000 17:59
Subject: Re: Boot loader problem workaround
>
> It would be nice if a command like
>
> fdisk -a -1 ad0
>
On Sat, 15 Jul 2000, Gemini Domino wrote:
> There's been a problem reported by several people on multi-HD multiboot
> systems about the bootloader clearing active flags and making it impossible
> to reboot without using a boot disk to use FDISK to reset the active flag.
> This was solved by turni
27 matches
Mail list logo
