headers
Eduardo Horvath | 1 Jun 2010 01:13
Picon

Re: Netbooting a sparc64

On Mon, 31 May 2010, DL wrote:

> Thanks for the clue Michael... when I omit the leading / from both efforts to
> pass the filename to ofwboot.net I get exactly the same results that I got when
> I included the leading /  *slapping my forehead in exasperation*

Unfortunately some veresions of tftpd have problems with files over a 
certain size.  It maybe your kernel is too big for your tftpd.

Eduardo
Permalink | Reply | 0 comments |
headers
Eduardo Horvath | 1 Jun 2010 01:26
Picon

Re: dma at ebus

On Mon, 31 May 2010, Chris Ross wrote:

>  So, in working on my X1 some more, I notice that the GENERIC kernel has a
> "dma* at sbus?", presumedly solely for the "esp* at dma?".  And, my Sun Netra
> X1 has a dma at ebus that is "not configured".
> 
>  Is the dma reported by the OBP not nearly the same as the "dma* at sbus?"?
> Or, it is just that there's no need for it, so no one adapted the driver to
> attach it?

Could be.

On some machines the "ebus" is actually the same Happy Meal chip that's 
attached to SBUS to provide SCSI and 10MB ethernet.  In some cases some of 
the functions are not used.

On other machines it's a standard PC "soutbridge" chip.  In this case the 
DMA is probably the ISA DMA.

Unless there's something directly wired to it, the DMA feature is probably 
unused.

Eduardo
Permalink | Reply | 2 comments |
headers
Erik Fair | 1 Jun 2010 07:45
Picon

Re: dma at ebus

More to the point, as the Netra X1 has no Sbus, you may remove or comment out anything and everything to do with
it for NetBSD kernels you intend to boot solely on that machine.

For two examples, please find these NetBSD/sparc64 5.x system-specific kernel configs:

http://www.clock.org/~fair/netbsd/FLAPJACK-LITE
http://www.clock.org/~fair/netbsd/FLAPJACK2

FLAPJACK2 is the motherboard code name (on the silkscreen) for the Netra T1 model 200 (500 MHz) and the Sun
Fire V120 (550 & 650 MHz).

FLAPJACK-LITE is the motherboard code name for the Netra X1, and I believe, the Sun Fire V100 (though I don't
have one of those to look at myself).

They were both edited down from GENERIC to fit the hardware (and in the case of the FLAPJACK2 which has a
single 32-bit PCI slot, hardware I might likely put in it).

	Erik <fair <at> netbsd.org>
Permalink | Reply | 1 comment |
headers
Chris Ross | 1 Jun 2010 15:51

Re: dma at ebus


  Oh yeah, I know that the X1 has no sbus at all, and that the pci bus isn't one things can be added to.  I've done the
same basic modification for the kernel I just built for this machine, which is where the question came
from.  "dma* at ebus?" doesn't configure, and I was wondering if there was any reason it should.

  Thanks for the examples, there, too.  Good references.

                          - Chris

On Jun 1, 2010, at 1:45 AM, Erik Fair wrote:

> More to the point, as the Netra X1 has no Sbus, you may remove or comment out anything and everything to do
with it for NetBSD kernels you intend to boot solely on that machine.
> 
> For two examples, please find these NetBSD/sparc64 5.x system-specific kernel configs:
> 
> http://www.clock.org/~fair/netbsd/FLAPJACK-LITE
> http://www.clock.org/~fair/netbsd/FLAPJACK2
> 
> FLAPJACK2 is the motherboard code name (on the silkscreen) for the Netra T1 model 200 (500 MHz) and the Sun
Fire V120 (550 & 650 MHz).
> 
> FLAPJACK-LITE is the motherboard code name for the Netra X1, and I believe, the Sun Fire V100 (though I
don't have one of those to look at myself).
> 
> They were both edited down from GENERIC to fit the hardware (and in the case of the FLAPJACK2 which has a
single 32-bit PCI slot, hardware I might likely put in it).
> 
> 	Erik <fair <at> netbsd.org>
(Continue reading)

Permalink | Reply | 0 comments |
headers
DL | 1 Jun 2010 20:07
Picon
Favicon

Re: Netbooting a sparc64

Hello all -

I finally have managed to netboot this Ultra 5 with a combination of all of the
clues that Martin, Eduardo and Mike provided.  As it turns out the last missing
piece that I needed was to edit the udhcpd.conf file on the router and insert
"siaddr {address of the machine which was running the TFTP server}" so that when
the udhcpd server received the BOOTP request from ofwboot it would respond with
that address.

 <at>  Martin, Eduardo and Mike : Thanks for the prompt and helpful replies!
Permalink | Reply | 0 comments |
headers
Thomas Klausner | 2 Jun 2010 22:00
Picon

Re: devel/boehm-gc doesn't work on sparc64

On Wed, Jun 02, 2010 at 01:01:46PM -0400, Chris Ross wrote:
>   Could this please be included?  Thank you.

Thanks, committed and sent upstream.
 Thomas
Permalink | Reply | 0 comments |
headers
DL | 2 Jun 2010 23:36
Picon
Favicon

Re: Readying a disk for booting NetBSD-5

Martin:
Thank you for the tips re: the filesystem choice
(http://article.gmane.org/gmane.os.netbsd.general/28715).  From that I decided
to go ahead and try to have sysinst put the 5.1 RC2 /, base and etc sets onto a
FFSv2 filesystem.  Did I understand you correctly that the 5.1 RC2 sysinst
should be able to make that work?

I thought I ran the sysinst okay by using the entire disk for /.  Thinking that
sysinst would need to put something in the first one or two disk sectors I first
tried to offset the start of the / partition by 2 sectors. sysinst did not like
that though and I ended up just setting / up in the disklabel starting from the
default sector 0.  The rest of the sysinst appeared to go as expected.

Yet upon rebooting from OpenBoot I am seeing the same "Invalid superblock magic"
result that Chris saw
(http://article.gmane.org/gmane.os.netbsd.ports.sparc64/6662). Should I question
my choice of the FFSv2 filesystem?  Or should I be looking for something else
about the way that I had sysinst put the NetBSD installation onto the disk?
Permalink | Reply | 6 comments |
headers
Eduardo Horvath | 2 Jun 2010 23:48
Picon

Re: Readying a disk for booting NetBSD-5

On Wed, 2 Jun 2010, DL wrote:

> Martin:
> Thank you for the tips re: the filesystem choice
> (http://article.gmane.org/gmane.os.netbsd.general/28715).  From that I decided
> to go ahead and try to have sysinst put the 5.1 RC2 /, base and etc sets onto a
> FFSv2 filesystem.  Did I understand you correctly that the 5.1 RC2 sysinst
> should be able to make that work?
> 
> I thought I ran the sysinst okay by using the entire disk for /.  Thinking that
> sysinst would need to put something in the first one or two disk sectors I first
> tried to offset the start of the / partition by 2 sectors. sysinst did not like
> that though and I ended up just setting / up in the disklabel starting from the
> default sector 0.  The rest of the sysinst appeared to go as expected.

Don't worry about any of that.

The disklabel takes up 1 sector.  The bootblock takes up 15 sectors.  And 
BSD filesystems skip the first 16 sectors.

> 
> Yet upon rebooting from OpenBoot I am seeing the same "Invalid superblock magic"
> result that Chris saw
> (http://article.gmane.org/gmane.os.netbsd.ports.sparc64/6662). Should I question
> my choice of the FFSv2 filesystem?  Or should I be looking for something else
> about the way that I had sysinst put the NetBSD installation onto the disk?

I think the 5.9 bootloaders only support FFSv1.  If you want v2 or LFS 
support you need to use -current.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Martin Husemann | 3 Jun 2010 00:14
Picon

Re: Readying a disk for booting NetBSD-5

On Wed, Jun 02, 2010 at 09:48:22PM +0000, Eduardo Horvath wrote:
> I think the 5.9 bootloaders only support FFSv1.  If you want v2 or LFS 
> support you need to use -current.

I just checked and you are right.
I thought I had asked for a pullup of the bootblock changes, but
apparently I didn't.

Martin
Permalink | Reply | 0 comments |
headers
Stephen Eastman | 3 Jun 2010 12:44
Picon
Favicon

Hi .. a gift!8

Hey friend!<BR>Share happiness!<BR>Are you in the need of buying electronic products? Here(<A
href="http://www.snnsnn.com/">www.snnsnn.com</A>) 5they have very fashionable electronic
products,and also there are unexpected preferential prices. If there is anything that you need,just
come with me!<BR>Wish you happy everyday!
Permalink | Reply | 0 comments |

Gmane