headers
Manuel Bouyer | 1 Jul 2007 12:36

Re: [ANNOUNCEMENT] The pkgsrc-2007Q2 Branch

On Sun, Jul 01, 2007 at 11:25:50AM +0100, Alistair Crooks wrote:
> 
> The pkgsrc-2007Q2 Branch
> ========================
> 
> The pkgsrc developers are very proud to announce the new pkgsrc-2007Q2
> branch, [...]

As I did for the previous branches, I'll do regular bulk builds from
pkgsrc-2007Q2 and provide the resulting binaries for NetBSD 2.1, 3.1 and
4.0 on i386, sparc and (new with this branch) amd64. Expect binaries to
show up in about 10 days for i386 and amd64, and 3 to 4 weeks for sparc.

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 0 comments |
headers
Garrett D'Amore | 2 Jul 2007 08:33
Picon

grub and amd64.. issues?

In short: is it possible to get grub to directly boot an amd64 kernel
without going through the chainloader?

Here's why I need to do that.

I'm trying to test a kernel to which I've added LSI SAS support to the
mpt driver.  This is on hardware to which I have remote console and
power, but no direct access.  The hardware has 8GB RAM, and therefore
cannot boot an i386 kernel.  It already has the grub that comes with
Solaris installed.  (Its a Sun x4200.)

I don't have access to the DHCP server, nor to the server where the grub
menu.lst file is loaded.  I do however have root access to other
machines on the same subnet, so I can set up an alternate TFTP or NFS
server (not DHCP!)

As far as I know, there are no physical removable storage, and in fact
the only mass storage on the system is the mpt-connected SAS drives
(which I need my newly modified driver to access!)

I do have access to the local ufs filesystem, which has Solaris
installed on it.

What I'd love to be able to do is something like:

grub> root (hd0,0,a)
grub> kernel /netbsd
(or kernel --type=netbsd /netbsd)

grub> boot
(Continue reading)

Permalink | Reply | 9 comments |
headers
Brandon Lee | 2 Jul 2007 09:39

Re: grub and amd64.. issues?

On 7/2/07, Garrett D'Amore <Garrett.Damore <at> sun.com> wrote:
> In short: is it possible to get grub to directly boot an amd64 kernel
> without going through the chainloader?
>
>
>
> Here's why I need to do that.
>
> I'm trying to test a kernel to which I've added LSI SAS support to the
> mpt driver.  This is on hardware to which I have remote console and
> power, but no direct access.  The hardware has 8GB RAM, and therefore
> cannot boot an i386 kernel.  It already has the grub that comes with
> Solaris installed.  (Its a Sun x4200.)
>
> I don't have access to the DHCP server, nor to the server where the grub
> menu.lst file is loaded.  I do however have root access to other
> machines on the same subnet, so I can set up an alternate TFTP or NFS
> server (not DHCP!)
>
> As far as I know, there are no physical removable storage, and in fact
> the only mass storage on the system is the mpt-connected SAS drives
> (which I need my newly modified driver to access!)
>
> I do have access to the local ufs filesystem, which has Solaris
> installed on it.
>
> What I'd love to be able to do is something like:
>
> grub> root (hd0,0,a)
> grub> kernel /netbsd
(Continue reading)

Permalink | Reply | 0 comments |
headers
Francisco Valladolid Hdez. | 2 Jul 2007 17:33
Picon
Favicon

Re: [ANNOUNCEMENT] The pkgsrc-2007Q2 Branch


Excellent Manuel, 

Regards.

--- Manuel Bouyer <bouyer <at> antioche.eu.org> wrote:

> On Sun, Jul 01, 2007 at 11:25:50AM +0100, Alistair
> Crooks wrote:
> > 
> > The pkgsrc-2007Q2 Branch
> > ========================
> > 
> > The pkgsrc developers are very proud to announce
> the new pkgsrc-2007Q2
> > branch, [...]
> 
> As I did for the previous branches, I'll do regular
> bulk builds from
> pkgsrc-2007Q2 and provide the resulting binaries for
> NetBSD 2.1, 3.1 and
> 4.0 on i386, sparc and (new with this branch) amd64.
> Expect binaries to
> show up in about 10 days for i386 and amd64, and 3
> to 4 weeks for sparc.
> 
> -- 
> Manuel Bouyer <bouyer <at> antioche.eu.org>
>      NetBSD: 26 ans d'experience feront toujours la
> difference
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 2 Jul 2007 21:43

Re: grub and amd64.. issues?

On Sun, Jul 01, 2007 at 11:33:46PM -0700, Garrett D'Amore wrote:
> In short: is it possible to get grub to directly boot an amd64 kernel
> without going through the chainloader?
> 
> 
> 
> Here's why I need to do that.
> 
> I'm trying to test a kernel to which I've added LSI SAS support to the
> mpt driver.  This is on hardware to which I have remote console and
> power, but no direct access.  The hardware has 8GB RAM, and therefore
> cannot boot an i386 kernel.  It already has the grub that comes with
> Solaris installed.  (Its a Sun x4200.)
> 
> I don't have access to the DHCP server, nor to the server where the grub
> menu.lst file is loaded.  I do however have root access to other
> machines on the same subnet, so I can set up an alternate TFTP or NFS
> server (not DHCP!)
> 
> As far as I know, there are no physical removable storage, and in fact
> the only mass storage on the system is the mpt-connected SAS drives
> (which I need my newly modified driver to access!)
> 
> I do have access to the local ufs filesystem, which has Solaris
> installed on it.
> 
> What I'd love to be able to do is something like:
> 
> grub> root (hd0,0,a)
> grub> kernel /netbsd
(Continue reading)

Permalink | Reply | 7 comments |
headers
Martin Husemann | 2 Jul 2007 21:48
Picon

Re: grub and amd64.. issues?

On Mon, Jul 02, 2007 at 09:43:01PM +0200, Manuel Bouyer wrote:
> An i386 kernel should work on a box with 8G, it just will see only
> about 3Gb. It may not be what you expect, but it should be a solution
> to start working on the patches :)

Doesn't work for me on a 4GB box (kernel crashes during pmap bootstrap)

Martin
Permalink | Reply | 4 comments |
headers
Manuel Bouyer | 2 Jul 2007 21:57

Re: grub and amd64.. issues?

On Mon, Jul 02, 2007 at 09:48:12PM +0200, Martin Husemann wrote:
> On Mon, Jul 02, 2007 at 09:43:01PM +0200, Manuel Bouyer wrote:
> > An i386 kernel should work on a box with 8G, it just will see only
> > about 3Gb. It may not be what you expect, but it should be a solution
> > to start working on the patches :)
> 
> Doesn't work for me on a 4GB box (kernel crashes during pmap bootstrap)

I guess grub isn't providing the expected infos about memory.
Did you try setting REALEXTMEM to about 3GB (or maybe 2GB to be safe) ?

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 3 comments |
headers
Garrett D'Amore | 2 Jul 2007 22:08
Picon

Re: grub and amd64.. issues?

Manuel Bouyer wrote:
> On Sun, Jul 01, 2007 at 11:33:46PM -0700, Garrett D'Amore wrote:
>   
>> In short: is it possible to get grub to directly boot an amd64 kernel
>> without going through the chainloader?
>>
>>
>>
>> Here's why I need to do that.
>>
>> I'm trying to test a kernel to which I've added LSI SAS support to the
>> mpt driver.  This is on hardware to which I have remote console and
>> power, but no direct access.  The hardware has 8GB RAM, and therefore
>> cannot boot an i386 kernel.  It already has the grub that comes with
>> Solaris installed.  (Its a Sun x4200.)
>>
>> I don't have access to the DHCP server, nor to the server where the grub
>> menu.lst file is loaded.  I do however have root access to other
>> machines on the same subnet, so I can set up an alternate TFTP or NFS
>> server (not DHCP!)
>>
>> As far as I know, there are no physical removable storage, and in fact
>> the only mass storage on the system is the mpt-connected SAS drives
>> (which I need my newly modified driver to access!)
>>
>> I do have access to the local ufs filesystem, which has Solaris
>> installed on it.
>>
>> What I'd love to be able to do is something like:
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Garrett D'Amore | 2 Jul 2007 22:14
Picon

Re: grub and amd64.. issues?

Manuel Bouyer wrote:
> On Mon, Jul 02, 2007 at 09:48:12PM +0200, Martin Husemann wrote:
>   
>> On Mon, Jul 02, 2007 at 09:43:01PM +0200, Manuel Bouyer wrote:
>>     
>>> An i386 kernel should work on a box with 8G, it just will see only
>>> about 3Gb. It may not be what you expect, but it should be a solution
>>> to start working on the patches :)
>>>       
>> Doesn't work for me on a 4GB box (kernel crashes during pmap bootstrap)
>>     
>
> I guess grub isn't providing the expected infos about memory.
> Did you try setting REALEXTMEM to about 3GB (or maybe 2GB to be safe) ?
>
>   

No, but I didn't know about that.  (Hence my message to this list.)  
I'll try that tonight.

    -- Garrett
Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 2 Jul 2007 22:16

Re: grub and amd64.. issues?

On Mon, Jul 02, 2007 at 10:08:37PM +0200, Martin Husemann wrote:
> On Mon, Jul 02, 2007 at 09:57:54PM +0200, Manuel Bouyer wrote:
> > I guess grub isn't providing the expected infos about memory.
> > Did you try setting REALEXTMEM to about 3GB (or maybe 2GB to be safe) ?
> 
> In my case it's the native bootloader. I never cared enough to fix it
> (though I think I talked to frank about it), because this machine runs
> the amd64 port usually.

Interesting. I've booted i386 on several systems with 4GB or more, and didn't
run into this. I used the native bootloader each time, though.

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 0 comments |

Gmane