Re: bfe0: couldn't map memory

2007-02-03 Thread Nuno Antunes

On 1/13/07, Nuno Antunes [EMAIL PROTECTED] wrote:

On 1/13/07, Sepherosa Ziehau [EMAIL PROTECTED] wrote:
 On 1/13/07, Nuno Antunes [EMAIL PROTECTED] wrote:
  Hi,
 
  I'm having trouble getting my bfe network interface card to work on
  dragonfly. The following appears on dmesg (hand transcribed):
 
  bfe0: Broadcom BCM4401-B0 Fast Ethernet irq 17 at device 1.0 on pci6
  bfe0: couldn't map memory
  device_probe_and_attach: bfe0 attach returned 6
 
  The interface does not appear on ifconfig -a
 
  Any help would be very appretiated.

 http://leaf.dragonflybsd.org/mailarchive/users/2006-01/msg00097.html

 Hope this will be helpful.

 Best Regards,
 sephe

 --
 Live Free or Die


Hi Sephe,

Thanks for the tip. A BIOS upgrade solved it.



Hmm. I recently started getting this error again, it knocked my head
out trying to find the reason (but it's working now).

I tried no-optimizations (even removed /etc/make.conf), trying
GENERIC, no SMP, always the same error. There was a difference when I
tried NATA though, it gave me:

bfe0: MII without any PHY!

Maybe options PCI_MAP_FIXUP for NATA had something to do with this?

Anyway, it turned out to be that I had disabled PXE booting at the
BIOS. Having it enabled allows bfe to work correctly on DFly on this
laptop (note that it was working of FreeBSD and Windows on the same
laptop without PXE enabled). The BIOS upgrade I had done before must
have restored the default enable PXE booting, that's why it worked
after the upgrade (until I disabled it later and started to get the
error again scratching my head why...).

Could it be there's some issue with pci memory/port mapping that
enabling PXE cirumvents? I'm way off my knowledge here..

Anyways, I just though I could tell the tale..

Thanks,
Nuno


Debugging vkernels with gdb

2007-02-03 Thread Steve Mynott

Is it possible to use kgdb to debug a vkernel as if it were remote
over a serial line?

Cheers Steve


Re: Debugging vkernels with gdb

2007-02-03 Thread Simon 'corecode' Schubert

Steve Mynott wrote:

Is it possible to use kgdb to debug a vkernel as if it were remote
over a serial line?


no.  just use gdb on the vkernel process.  modulo some stack rewinding it works.

cheers
 simon

--
Serve - BSD +++  RENT this banner advert  +++ASCII Ribbon   /\
Work - Mac  +++  space for low €€€ NOW!1  +++  Campaign \ /
Party Enjoy Relax   |   http://dragonflybsd.org  Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz   Mail + News   / \



signature.asc
Description: OpenPGP digital signature


Re: Debugging vkernels with gdb

2007-02-03 Thread Matthew Dillon

:Is it possible to use kgdb to debug a vkernel as if it were remote
:over a serial line?
:
:Cheers Steve

Yes.  Not even as if it were remote over a serial line... all you have
to do is gdb the vkernel's process id.

There is one issue, though... page faults that occur within the VKERNEL
itself will be caught by GDB, so you will get a lot of breaks in the
debugger that you have to 'cont' through.

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


Re: ath(4) major update

2007-02-03 Thread Sepherosa Ziehau

On 2/3/07, Ja'far Railton [EMAIL PROTECTED] wrote:

On Thu, Feb 01, 2007 at 07:55:24PM +0800, Sepherosa Ziehau wrote:
CIS reading done
ath0: Atheros 5212 mem 0x8801-0x8801 irq 11 at device 0.0 on
cardbus0
ath0: unable to attach hardware; HAL status 3
device_probe_and_attach: ath0 attach returned 6


Does the old HAL work for you?  If not, do any wired cardbus NICs work
on you laptop?
BTW, please give me the exact product name of the problematic ath(4)
cardbus NIC, thanks.

Best Regards,
sephe

--
Live Free or Die


We are officially better than FreeBSD (accoridng to distrowatch)

2007-02-03 Thread Petr Janda

According the stats on their site:

7 Day Average:

19. DragonFly 475 and going up
20. FreeBSD 455 and going up

I am aware that most of the hits were because of 1.8, its still 
nevertheless amusing :)


Petr