On Tue, Jan 20, 2015 at 08:47:17PM -0800, Adrian Chadd wrote:
> No idea why it doesn't work on stable/8. That's odd. It should work just
> fine.

True, esp. since it lists the nets and apparently can talk to DHCP server;
getting "sendto: Host is down" is very strange.  I will try again at home
or some cafe.

> sysctl dev.ath.0.ledon=<1 | 0 - ie, the LED polarity>
> sysctl dev.ath.0.softled=1
> Toggle softled 0 -> 1 each time you change ledpin, just to make sure
> the programming takes.

OK, running the following loop toggles LED on and off for a second:

  sysctl dev.ath.0.ledpin=1
  while :; do
      sysctl dev.ath.0.ledon=1
      sysctl dev.ath.0.softled=0
      sysctl dev.ath.0.softled=1
      sleep 1
      sysctl dev.ath.0.ledon=0
      sysctl dev.ath.0.softled=0
      sysctl dev.ath.0.softled=1
      sleep 1

I got confused in the beginning, because it was not obvious that actually
both softled=0 and softled=1 commands are required after each ledon change.

When I changed the pin (0 -> 1) and set LED to off, the card started to
show some activity, looking sane.  So it looks like it generally DTRT, but
needs to be told which pin to use.  Any hint I can put in /boot/loader.conf
for that, or I have to patch the driver?

> What's broken with suspend/resume? That should be fixed.

I didn't imply "broken wireless stack and/or drivers".  It took quite a
long time (almost three minutes) and several presses of power button, all
accompanied with weird screen artifacts, to get laptop back to life.  Some
relevant messages:

  pcib0: failed to set ACPI power state D2 on \134_SB_.PCI0: AE_BAD_PARAMETER
  acpi0: cleared fixed power button status
  error: [drm:pid1651:intel_lvds_enable] *ERROR* timed out waiting for panel to 
power off
  uhci_interrupt: host system error
  uhci_interrupt: host controller process error
  wakeup from sleeping state (slept 00:02:52)

On stable/8 resume is nearly instant (around one second to get myself back
to X11 with keyboard and mouse working).

> I've no idea about what or why it broke on stable/8 but isn't on
> -HEAD. I've done some pretty significant surgery to ath and net80211
> since stable/8. You can try narrowing it down by trying stable/9 and
> stable/10 to see if it started working during one of those releases.

Yes, I will probably do something like that.  Thanks Adrian!

freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to