ath_hal problems on sparc64

2006-03-15 Thread Sascha Luck
Hi,

I'm having some issues with the newly imported ath_hal module on the
sparc64 architecture:

(/usr/src/sys/modules/ath_hal)

[EMAIL PROTECTED] make
Warning: Object directory not changed from original
/usr/src/sys/modules/ath_hal
make: don't know how to make
/usr/src/sys/modules/ath_hal/../../contrib/dev/ath/public/sparc64-elf.hal.o.uu.
Stop

This file is actually called sparc64-be-elf.hal.o.uu. After copying to
'sparc64-elf.hal.o.uu', the module builds cleanly but doesn't load. The
only error message when trying to load it is:

serval# link_elf: symbol  undefined

Does this mean the uuencoded binary HAL is corrupt?

cheers,
s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ath_hal problems on sparc64

2006-03-15 Thread Sascha Luck
Sam,

On Wednesday 15 March 2006 16:55, Sam Leffler wrote:
> It means the files.sparc64 rules are botched.  I just committed the
> changes to head yesterday but you posted to stable@; what version of
> the os are you running?  I will mfc the changes to releng6 as soon as
> I get the ok.

Sorry, noticed only after posting, it's RELENG6 as of 1/2 hour ago. 

> FWIW the sparc64 hal has not been tested on freebsd so far as I know.
> It is known to work on netbsd and linux and is os-independent but
> beware...

I've got a few U10s and an Atheros PCI card here if you want me to do 
some testing. Would it make more sense to pull one of them up to 
CURRENT to test this?

>   Sam

cheers,
s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ath_hal problems on sparc64

2006-03-15 Thread Sascha Luck
On Wednesday 15 March 2006 17:01, Sam Leffler wrote:
> Oops, you were building a module, not adding ath_hal to a kernel
> config file.  I will fix the module build but I have no way to test
> if the code works.

I initially tried to build it into the kernel too, but it failed (AFAIR 
with missing includes, but it was a while ago). As for testing, I can 
test the code on one of my Ultra10s.

>   Sam
cheers,
s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ath_hal problems on sparc64

2006-03-16 Thread Sascha Luck
On Thursday 16 March 2006 22:32, Sam Leffler wrote:

> There's something bogus in the hal.o; I will need to figure out what
> happened and respin it.  It's not going to happen immediately; sorry.

So it appears. I just got hit by this on -CURRENT as well, with ath_hal 
compiled into the kernel. It dumps into kdb when trying to attach the 
driver. I'll see if I can manage to get a serial console set up, so I 
can post a trace... 

>   Sam

cheers,
s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: CFT: new ath hal

2006-04-29 Thread Sascha Luck
Sam Leffler wrote:
>  Otherwise I believe I fixed the sparc builds.

I've built it as a module on 6.1PR/sparc64 (as of 09.03.2006) and it
still
shows the same behaviour as the previous build (PR sparc64/94483)

cheers,
s.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Dell PowerEdge 1400.

2000-11-06 Thread Sascha Luck

Thus spoke Noor Dawod:
> Does the new FreeBSD 4.x branch support the Adaptec 7899 dual channel
> Ultra3 card? This is the card installed on the Dell PowerEdge 1400. See:

Yup.

> Also, does FreeBSD support the optional hardware RAID controller
> available for the same PowerEdge machine mentioned above?

Generally speaking, yes. It's an AMI Megaraid (device amr). We've had some 
dodginess with it, though (randomly failed drive 0). YMMV, though.

> Noor

s.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message