On Wed, Apr 23, 2014 at 03:16:52PM +0200, Alessandro DE LAURENZIS wrote:
> Your patch is still applicable to 5.4 stable (with only minor refinements),
> but unfortunately it doesn't change anything for this BGE chip...
Thanks, this motivated me to poke a bit further at it.
Just to make sure: Did
On Wed, Apr 23, 2014 at 10:52:10PM +0200, Alessandro DE LAURENZIS wrote:
> In order to adapt your code to 5.4-Rel, I did the following
> modification:
>
> From:
>
> + /* Configure 10Mbps, the chip draws too much power in D3cold. */
> + if (!(sc->bge_flags & BGE_FIBER_TBI) &&
> +
On Thu, Apr 24, 2014 at 10:31:47AM +0200, Alessandro DE LAURENZIS wrote:
> After further checks, I noticed that there still was a part of the patch
> not correctly applied. I modified a bit the code and renamed the two
> constants. Now there is no error after "ifconfig bge0 wol".
Ok, so far so goo
On Wed, Apr 23, 2014 at 11:21:33PM +0200, Alessandro DE LAURENZIS wrote:
> How can I check? For sure, there is no mention in the BIOS setup...
To find out if ASF is enabled, change this:
/* Allow WoL if ASF is unsupported or disabled. */
if (!(sc->bge_flags & BGE_ASF_MODE)) {
On Thu, Apr 24, 2014 at 10:20:34PM +0200, Alessandro DE LAURENZIS wrote:
> but:
>
> # dmesg | egrep DEBUG
>
>
> #
> (no response)
>
> # egrep DEBUG /var/log/*
On Fri, Apr 25, 2014 at 08:53:42AM +0200, Alessandro DE LAURENZIS wrote:
> Some other debug here, and this time with (I hope) more useful info.
Thanks!
> First of all, I confirm that the debug messages triggered by the added
> printf instructions are *NOT* logged by dmesg (and /var/log/*), but ar
On Fri 25/04, Fred wrote:
> On 04/25/14 11:24, Alessandro DE LAURENZIS wrote:
>
> >
> >I'm attaching a tarball with all the modified files, 'cause we proceeded
> >iteratively and it's very easy to miss something; it would be great if
> >you could revisit the code and prepare a patch usable with 5.
On Fri, Apr 25, 2014 at 3:24 AM, Alessandro DE LAURENZIS <
just22@gmail.com> wrote:
> On Fri 25/04, Stefan Sperling wrote:
> > On Fri, Apr 25, 2014 at 08:53:42AM +0200, Alessandro DE LAURENZIS wrote:
> > > Some other debug here, and this time with (I hope) more useful info.
> >
> > Thanks!
> >
On Fri 25/04, Stefan Sperling wrote:
> On Fri, Apr 25, 2014 at 08:53:42AM +0200, Alessandro DE LAURENZIS wrote:
> > Some other debug here, and this time with (I hope) more useful info.
>
> Thanks!
>
> > First of all, I confirm that the debug messages triggered by the added
> > printf instructions
On Wed 23/04, Stefan Sperling wrote:
> On Wed, Apr 23, 2014 at 03:16:52PM +0200, Alessandro DE LAURENZIS wrote:
> > Your patch is still applicable to 5.4 stable (with only minor refinements),
> > but unfortunately it doesn't change anything for this BGE chip...
>
> Thanks, this motivated me to pok
On Thu 24/04, Stefan Sperling wrote:
> On Thu, Apr 24, 2014 at 10:20:34PM +0200, Alessandro DE LAURENZIS wrote:
> > but:
> >
> > # dmesg | egrep DEBUG
> >
> >
How can I check? For sure, there is no mention in the BIOS setup...
On 23 April 2014 23:16:23 CEST, Stefan Sperling wrote:
>On Wed, Apr 23, 2014 at 10:52:10PM +0200, Alessandro DE LAURENZIS
>wrote:
>> In order to adapt your code to 5.4-Rel, I did the following
>> modification:
>>
>> From:
>>
>>
On Thu 24/04, Stefan Sperling wrote:
> On Thu, Apr 24, 2014 at 10:31:47AM +0200, Alessandro DE LAURENZIS wrote:
>
> Can you please check for me if bge_activate() is called when you
> shut down the machine, and with what value? Just add a printf like this:
>
> int
> bge_activate(struct device *sel
On Thu 24/04, Stefan Sperling wrote:
> On Wed, Apr 23, 2014 at 11:21:33PM +0200, Alessandro DE LAURENZIS wrote:
> > How can I check? For sure, there is no mention in the BIOS setup...
>
> To find out if ASF is enabled, change this:
>
> /* Allow WoL if ASF is unsupported or disabled. */
>
On Tue 22/04, Stefan Sperling wrote:
> On Tue, Apr 22, 2014 at 04:43:51PM +0200, Alessandro DE LAURENZIS wrote:
>
> What you'd need is wol support for bge, like was done for some
> other drivers. I believe your 'halt' workaround prevents bge_stop()
> from being run which deliberately shuts down th
I assume it might be set from bios. I look into user guide
for a mobo I have and here it is, under apm. "Power on by...".
To shutdown my openbsd node i use "shutdown -ph now" and
turn it on with power button physically.
Best regards
Zoran
On Tue, Apr 22, 2014 at 04:43:51PM +0200, Alessandro DE LAURENZIS wrote:
> Folks,
>
> OpenBSD 5.4-Rel, GENERIC kernel. I'm trying to set up a file server that
> should be remotely controlled (broken LCD).
>
> I need to switch it on by means of WOL functionality (supported by and
> activated into
Folks,
OpenBSD 5.4-Rel, GENERIC kernel. I'm trying to set up a file server that
should be remotely controlled (broken LCD).
I need to switch it on by means of WOL functionality (supported by and
activated into the BIOS).
The interface is:
$ dmesg | egrep bge
bge0 at pci2 dev 0 function 0 "Broad
18 matches
Mail list logo
