n Mon, Jul 11, 2016 at 04:36:44PM -0700, Mike Larkin wrote:
> > On Tue, Jul 12, 2016 at 01:28:21AM +0200, stolendata.net wrote:
> > > I just managed to get it to boot. The machine is running sort of
> headless
> > > with only the on-board IGP available, using 32MB of sha
AM, Mike Larkin wrote:
> On Tue, Jul 12, 2016 at 12:30:23AM +0200, stolendata.net wrote:
> > Alright, ddb prompt pops up on i386. Last output from kernel:
> >
> > real mem ...
> > avail mem ...
> > kernel: page fault trap, code=0
> > Stopped at memcpy+0x13:
https://i.imgur.com/EAqLSPJ.jpg
https://i.imgur.com/FBh4syj.jpg
On Tue, Jul 12, 2016 at 12:32 AM, Mike Larkin wrote:
> On Tue, Jul 12, 2016 at 12:30:23AM +0200, stolendata.net wrote:
> > Alright, ddb prompt pops up on i386. Last output from kernel:
> >
> > real
x27;m game.
On Tue, Jul 12, 2016 at 12:12 AM, Mike Larkin wrote:
> On Tue, Jul 12, 2016 at 12:09:03AM +0200, stolendata.net wrote:
> > GENERIC.MP AMD64/5.9-release booted from full install on USB disk
> behaves
> > the exact same way as the ramdisk kernel, stops booting at the s
200, stolendata.net wrote:
>
> >
> > If it's of any value to help narrow the problem down, this particular CPU
> > model is probably not the culprit. I've been running OpenBSD on one on
> > another board since 4.9.
> >
>
> Even though you don't
OpenBSD on one on
another board since 4.9.
On Mon, Jul 11, 2016 at 11:05 PM, Mike Larkin wrote:
> On Mon, Jul 11, 2016 at 10:37:23PM +0200, stolendata.net wrote:
>
> > With 5.9/AMD64-release the kernel manages to get just a few steps
> further,
> > crashing after a few lines
Apologies if this is not the preferred mailing list for this.
As I can't get the machine to boot, I'll just provide a picture of the
crash: http://i.imgur.com/KDcPwTg.jpg
With 5.9/AMD64-release the kernel manages to get just a few steps further,
crashing after a few lines of the "BIOS0" enumerati
I reported this about a month and a half ago. Same problem with my RT2860
device, and for the past years I've handled it the same way you did: by
having the clients rapidly pinging the AP to prevent them from entering
power saving mode.
I never got any response indicating that someone is looking i
My bad, thanks for the clarification. However, RAL(4) is still not capable
of properly managing power saving clients. I've been running this Edimax
EW-7728IN card (RT2860; see dmesg in initial report) as HostAP since 4.9,
so I'm well-acquainted with the problems seen by the clients as I've had to
d
s that the man page
claim should finally be supported.
On Tue, Jun 4, 2013 at 3:25 PM, Stuart Henderson wrote:
> On 2013/06/04 15:20, stolendata.net wrote:
> > The man page of ral(4) makes it understood that power saving in host ap
> > mode is now finally working, but only for cer
10 matches
Mail list logo
