On Thu, Apr 02, 2009 at 03:15:30AM +, John wrote:
> Quoting Chagin Dmitry :
>
> >>>
> >>> dchagin# ifconfig malo0 scan
> >>> ifconfig: unable to get scan results
> >>>
> >>> In the evening I will more in detail look... anyway, many thanks :)
> >>
> >>FWIW the following commands would be useful
Quoting Chagin Dmitry :
>
> dchagin# ifconfig malo0 scan
> ifconfig: unable to get scan results
>
> In the evening I will more in detail look... anyway, many thanks :)
FWIW the following commands would be useful for CURRENT:
# ifconfig wlan0 create wlandev malo0
# ifconfig wlan
On Tue, Mar 31, 2009 at 04:36:08PM +0900, Weongyo Jeong wrote:
> On Tue, Mar 31, 2009 at 11:03:25AM +0400, Chagin Dmitry wrote:
> > On Tue, Mar 31, 2009 at 12:42:29PM +0900, Weongyo Jeong wrote:
> > > On Mon, Mar 30, 2009 at 08:53:34PM +0400, Chagin Dmitry wrote:
> > > > On Mon, Mar 30, 2009 at 05:
On Tue, Mar 31, 2009 at 11:03:25AM +0400, Chagin Dmitry wrote:
> On Tue, Mar 31, 2009 at 12:42:29PM +0900, Weongyo Jeong wrote:
> > On Mon, Mar 30, 2009 at 08:53:34PM +0400, Chagin Dmitry wrote:
> > > On Mon, Mar 30, 2009 at 05:05:32PM +0900, Weongyo Jeong wrote:
> > > > On Sat, Mar 28, 2009 at 10:
On Tue, Mar 31, 2009 at 12:42:29PM +0900, Weongyo Jeong wrote:
> On Mon, Mar 30, 2009 at 08:53:34PM +0400, Chagin Dmitry wrote:
> > On Mon, Mar 30, 2009 at 05:05:32PM +0900, Weongyo Jeong wrote:
> > > On Sat, Mar 28, 2009 at 10:11:43PM +0300, Chagin Dmitry wrote:
> > > > On Wed, Mar 25, 2009 at 09:
On Mon, Mar 30, 2009 at 08:53:34PM +0400, Chagin Dmitry wrote:
> On Mon, Mar 30, 2009 at 05:05:32PM +0900, Weongyo Jeong wrote:
> > On Sat, Mar 28, 2009 at 10:11:43PM +0300, Chagin Dmitry wrote:
> > > On Wed, Mar 25, 2009 at 09:52:43PM +, John wrote:
> > > > Hi list
> > > >
> [skiped]
>
> > >
On Mon, Mar 30, 2009 at 05:05:32PM +0900, Weongyo Jeong wrote:
> On Sat, Mar 28, 2009 at 10:11:43PM +0300, Chagin Dmitry wrote:
> > On Wed, Mar 25, 2009 at 09:52:43PM +, John wrote:
> > > Hi list
> > >
[skiped]
> >
> > Weongyo, please, look at line #166 - 169.
>
> Oops. I got it. :-) I'll
On Sat, Mar 28, 2009 at 10:11:43PM +0300, Chagin Dmitry wrote:
> On Wed, Mar 25, 2009 at 09:52:43PM +, John wrote:
> > Hi list
> >
> > I configured the malo device as per the manpage. Now I'm getting panic
> > after the device is probed as per
> > http://www.growveg.org/desktop/DSC_6973-3008.j
On Sat, Mar 28, 2009 at 06:45:10PM +, John wrote:
> Paul B. Mahol wrote:
>
> >You should use this version of firmware:
> > http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz
> >
>
> That's what I'm using, as per the manpage:
>
> [snip]
>
> This driver requires firmware to be
On Wed, Mar 25, 2009 at 09:52:43PM +, John wrote:
> Hi list
>
> I configured the malo device as per the manpage. Now I'm getting panic
> after the device is probed as per
> http://www.growveg.org/desktop/DSC_6973-3008.jpg
>
> Is there a parameter I can pass to boot that will ignore this
> dri
Paul B. Mahol wrote:
You should use this version of firmware:
http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz
That's what I'm using, as per the manpage:
[snip]
This driver requires firmware to be loaded before it will work. These
firmware files are from the OpenBSD mal
On 3/28/09, John wrote:
> Paul B. Mahol wrote:
>> On 3/28/09, John wrote:
>>> Weongyo Jeong wrote:
>>>
It looks something goes wrong so could you please patch if_malo_pci.c
manually it's a very simple patch and test? Sorry for inconvenience.
>>> Hello,
>>>
>>> Now I get:
>>>
>>> sudo k
Paul B. Mahol wrote:
On 3/28/09, John wrote:
Weongyo Jeong wrote:
It looks something goes wrong so could you please patch if_malo_pci.c
manually it's a very simple patch and test? Sorry for inconvenience.
Hello,
Now I get:
sudo kldload /boot/kernel/if_malo.ko
kldload: can't load /boot/ker
On 3/28/09, John wrote:
> Weongyo Jeong wrote:
>
>> It looks something goes wrong so could you please patch if_malo_pci.c
>> manually it's a very simple patch and test? Sorry for inconvenience.
>
> Hello,
>
> Now I get:
>
> sudo kldload /boot/kernel/if_malo.ko
> kldload: can't load /boot/kernel/i
Weongyo Jeong wrote:
> It looks something goes wrong so could you please patch if_malo_pci.c
> manually it's a very simple patch and test? Sorry for inconvenience.
Hello,
Now I get:
sudo kldload /boot/kernel/if_malo.ko
kldload: can't load /boot/kernel/if_malo.ko: Exec format error
[j...@potat
On 3/27/09, John wrote:
> Weongyo Jeong wrote:
>>
>> It looks something goes wrong so could you please patch if_malo_pci.c
>> manually it's a very simple patch and test? Sorry for inconvenience.
>
> After editing, is it sufficient to just build and install a new kernel?
Yes, (or only if_malo mod
Weongyo Jeong wrote:
>
> It looks something goes wrong so could you please patch if_malo_pci.c
> manually it's a very simple patch and test? Sorry for inconvenience.
After editing, is it sufficient to just build and install a new kernel?
thanks
--
John
_
Weongyo Jeong wrote:
> It looks something goes wrong so could you please patch if_malo_pci.c
> manually it's a very simple patch and test? Sorry for inconvenience.
No worries. I've edited if_malo_pci.c now and will build a new kernel
when I get back home. I'll let you know how I get on
thanks
On Thu, Mar 26, 2009 at 11:23:09AM +, John wrote:
> Weongyo Jeong wrote:
>
> > Could you please test it with attached patch to fix a page fault? I
> > don't know why bus_dma_tag_create() returns ENOMEM that it looks
> > temporary.
>
> Hi,
>
> Seems the patch failed to apply:
>
> [r...@pota
Paul B. Mahol wrote:
> On 3/26/09, John wrote:
>> Paul B. Mahol wrote:
>>
>>> This is a contradiction, I think that in csup case "last rule wins"
>> How come this builds a 7-STABLE system rather than -CURRENT ?
>>
>> In any case, I appreciate your comment and will take out the offending
>> line. (
On 3/26/09, John wrote:
> Paul B. Mahol wrote:
>
>> This is a contradiction, I think that in csup case "last rule wins"
>
> How come this builds a 7-STABLE system rather than -CURRENT ?
>
> In any case, I appreciate your comment and will take out the offending
> line. (it's in there because I thou
Paul B. Mahol wrote:
> This is a contradiction, I think that in csup case "last rule wins"
How come this builds a 7-STABLE system rather than -CURRENT ?
In any case, I appreciate your comment and will take out the offending
line. (it's in there because I thought ports was always HEAD)
cheers
--
On 3/26/09, John wrote:
> Paul B. Mahol wrote:
>
>>
>> Patch is so trivial and short that it can be applied manually.
>>
>> Are you sure that you use 7 STABLE sources and not CURRENT one?
>
> I'm absolutely certain. Sources from the 25th March, make world and
> kernel the day after:
>
> [r...@pota
Paul B. Mahol wrote:
>
> Patch is so trivial and short that it can be applied manually.
>
> Are you sure that you use 7 STABLE sources and not CURRENT one?
I'm absolutely certain. Sources from the 25th March, make world and
kernel the day after:
[r...@potato ~]# uname -a
FreeBSD potato.growveg
On 3/26/09, John wrote:
> Weongyo Jeong wrote:
>
>> Could you please test it with attached patch to fix a page fault? I
>> don't know why bus_dma_tag_create() returns ENOMEM that it looks
>> temporary.
>
> Hi,
>
> Seems the patch failed to apply:
Patch is so trivial and short that it can be appl
Pyun YongHyeon wrote:
> #cd /usr/src/sys/dev/malo
> #patch -p0 < /path/to/patch_malo_20090326_panic.diff
>
> And rebuild malo(4)/kernel.
No luck I'm afraid:
[r...@potato /usr/src/sys/dev/malo]# patch -p0 <
patch_malo_20090326_panic.diff
Hmm... Looks like a unified diff to me...
The text leadi
Pyun YongHyeon wrote:
> #cd /usr/src/sys/dev/malo
> #patch -p0 < /path/to/patch_malo_20090326_panic.diff
>
> And rebuild malo(4)/kernel.
Ok thanks for that, I'll try again
--
John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/ma
Weongyo Jeong wrote:
> Could you please test it with attached patch to fix a page fault? I
> don't know why bus_dma_tag_create() returns ENOMEM that it looks
> temporary.
Hi,
Seems the patch failed to apply:
[r...@potato /usr/src/sys/dev/malo]# ls -la
total 140
drwxr-xr-x2 root wheel5
On Thu, Mar 26, 2009 at 10:59:25AM +, John wrote:
> Weongyo Jeong wrote:
>
> > Could you please test it with attached patch to fix a page fault? I
> > don't know why bus_dma_tag_create() returns ENOMEM that it looks
> > temporary.
>
> Hi, thanks for this, I'll try it when I get home tonight.
Weongyo Jeong wrote:
> Could you please test it with attached patch to fix a page fault? I
> don't know why bus_dma_tag_create() returns ENOMEM that it looks
> temporary.
Hi, thanks for this, I'll try it when I get home tonight. Not all that
familiar with patching though. I guess I go to where m
On Wed, Mar 25, 2009 at 09:52:43PM +, John wrote:
> Hi list
>
> I configured the malo device as per the manpage. Now I'm getting panic
> after the device is probed as per
> http://www.growveg.org/desktop/DSC_6973-3008.jpg
Could you please test it with attached patch to fix a page fault? I
do
Paul B. Mahol wrote:
> On 3/25/09, John wrote:
>> Hi list
>>
>> I configured the malo device as per the manpage. Now I'm getting panic
>> after the device is probed as per
>> http://www.growveg.org/desktop/DSC_6973-3008.jpg
>>
>> Is there a parameter I can pass to boot that will ignore this
>> dri
On 3/25/09, John wrote:
> Hi list
>
> I configured the malo device as per the manpage. Now I'm getting panic
> after the device is probed as per
> http://www.growveg.org/desktop/DSC_6973-3008.jpg
>
> Is there a parameter I can pass to boot that will ignore this
> driver/module? I have tried disabl
Hi list
I configured the malo device as per the manpage. Now I'm getting panic
after the device is probed as per
http://www.growveg.org/desktop/DSC_6973-3008.jpg
Is there a parameter I can pass to boot that will ignore this
driver/module? I have tried disable-module to no avail. Is the only
optio
34 matches
Mail list logo
