On 2008/12/21, at 21:24, Ryo Murakawa wrote:

> Masafumi-san
>
> Thank you for your reply.
>
> And I want to make sure if my step is wrong or not.
> When I use this atge driver, do I have to stop nwam service?
>

Well that depends....
sometimes we need to stop nwam automatic service(we have to use manual  
setting in nwam) and check
whether atge works or not in the network setting.


> Today I installed Jaris on my hp mini 1000.  And I installed myk  
> driver to work the wired NIC and
> the ndis driver to work the wireless driver.
>
> When nwam service run, I never use this myk driver. But when I stop  
> nwam, I can use the wired NIC.
>

Well,I sometimes meet this problem because of something wrong in nwam.
so in this case we should stop nwam and use network manual setting.
have you tried to stop on your Eee and then your atge works out?

And Could I ask you a favor,could you send your /var/adm/messages for  
checking your atge driver working well?
Perhaps it is big file so you might better send only to me,not to this  
mailing list.

I now talking with Murayama-san about this problem..
sorry for your inconvenience.

Regards,

-masafumi

> Best Regards.
>
> Ryo Murakawa
>
>
> On 2008/12/21, at 17:54, Masafumi Ohta wrote:
>
>> Murakawa-san
>>
>> sorry too late to respond I have had a cold for a long time:-(
>> let me check with Murayama-san.
>>
>> sorry for your impatience.
>>
>> -masafumi
>>
>> On 2008/12/14, at 0:49, Ryo Murakawa wrote:
>>
>>> Hi,
>>>
>>> I have been using Solaris Express nb95 on external USB disk on
>>> myEeePC 4G.
>>> Today I downloaded the atge driver and installed it on my EeePC
>>> followed by README.txt.
>>>
>>> But my L2 NIC doesn't work correctly. The command "ifconfig atge0
>>> plumb" is OK. But
>>> The command "ifconfig atge0 dhcp start" is NG.
>>>
>>> The messages is below
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 392281 kern.info] atge0:
>>> atge_init_chip_2: called at time:27063
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 453531 kern.info] atge0:
>>> atge_init_chip_2: GAPC:0x60405060
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 648229 kern.info] atge0:
>>> atge_init_chip_2: HDCTL:0x7a1f037
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 346521 kern.info] atge0:
>>> atge_init_chip_2: INTRDELAY_INIT:0x1
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 477463 kern.info] atge0:
>>> atge_init_chip_2: INTRCLR_TIMER:0xc350
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 500093 kern.info] atge0:
>>> atge_init_chip_2: MTU: 0x5f2
>>> Dec 14 00:20:11 eeepcb95 atge: [ID 765148 kern.info] atge0:
>>> atge_set_rx_filter:
>>> called at time:27063, active:0, rxmode:8<ENABLE>, MACCTL:
>>> 28005c20<DEBUG,RXVTAG,FD>
>>> Dec 14 00:23:10 eeepcb95 atge: [ID 765148 kern.info] atge0:
>>> atge_set_rx_filter:
>>> called at time:45040, active:0, rxmode:9<ENABLE,PROMISC>, MACCTL:
>>> 04101cec<AB,AUTOPAD,CRCEN,FD,RXFC,TXFC>
>>> Dec 14 00:28:00 eeepcb95 atge: [ID 765148 kern.info] atge0:
>>> atge_set_rx_filter:
>>> called at time:74022, active:0, rxmode:8<ENABLE>, MACCTL:
>>> 04109cec<AB,PROMISC,AUTOPAD,CRCEN,FD,RXFC,TXFC>
>>>
>>> I think this driver work correctly for all EeePC with Atheros L2  
>>> NIC.
>>> So could you tell me
>>> how to resolve this problem.
>>>
>>> Best Regards.
>>>
>>> Ryo Murakawa
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> eeepc-discuss mailing list
>>> eeepc-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/eeepc-discuss
>>
>


Reply via email to