[Elphel-support] Support-list Digest, Vol 34, Issue 3
Andrey Filippov
support-list at support.elphel.com
Wed Jun 6 17:18:18 PDT 2012
Carlos,
Yes, sure, try that. And it is really strange - how that could be changed
if you did not do it yourself. And as I wrote before - if you tried and can
modify that file from serial console - it is safe to modify this file.
Andrey
On Wed, Jun 6, 2012 at 6:05 PM, Carlos Padial <palidoestudio2 at gmail.com>wrote:
> these are from the camera before to do anything
>
>
> # mii-diag
> Using the default interface 'eth0'.
> Basic registers of MII PHY #0: 0180 7849 000e 7237 01e1 0000 0000 0000.
> Basic mode control register 0x0180: Auto-negotiation disabled, with
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
> Link partner information is not exchanged when in fixed speed mode.
>
> End of basic transceiver information.
>
> # cat /var/log/mii-diag.log
> mii-diag.c:v2.11 3/21/2005 Donald Becker (becker at scyld.com)
> http://www.scyld.com/diag/index.html
> Using the new SIOCGMIIPHY value on PHY 0 (BMCR 0x0000).
> Basic mode control register 0x0180: Auto-negotiation disabled, with
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
>
> This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
> 10baseT.
> Able to perform Auto-negotiation, negotiation not complete.
> Link partner information is not exchanged when in fixed speed mode.
>
> End of basic transceiver information.
>
> libmii.c:v2.11 2/28/2005 Donald Becker (becker at scyld.com)
> http://www.scyld.com/diag/index.html
> MII PHY #0 transceiver registers:
> 0180 7849 000e 7237 01e1 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0140 0015 0800 47dd 2882 0000 0000 0010
> 0000 0000 0000 0000 0000 0000 0000 0000.
> Basic mode control register 0x0180: Auto-negotiation disabled!
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
>
> Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
> Able to perform Auto-negotiation, negotiation not complete.
>
> Vendor ID is 00:03:9c:--:--:--, model 35 rev. 7.
> No specific information is known about this transceiver type.
> I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
> Advertising no additional info pages.
> IEEE 802.3 CSMA/CD protocol.
> Link partner capability is 0000:.
> Negotiation did not complete.
>
> Monitoring the MII transceiver status.
> 00:00:21.874 Baseline value of MII BMSR (basic mode status register) is
> 7849.
> Value of MII BMSR (basic mode status register) is 7849.
>
> then i edit the
>
> and find it a little diferent from yours:
>
>
> # (C) Copyright 2005-2007, Axis Communications AB, LUND, SWEDEN
> # Modified by Elphel, Inc., USA
>
> # This file is released under the GPL v2.
>
> # Uncomment the following line to override the generic hardware address
> # (usually the serial number) for this interface only.
> # MAC=00:0E:64:00:00:00
>
> # Valid boot protocols are "dhcp" and "none" (anything other than "dhcp"
> works).
> BOOTPROTO=none
> DHCP_CLIENT="/sbin/udhcpc -i eth0 -H $(hostname)"
>
> # Valid media types are "auto", "10baseT-HD", "10baseT-FD", "100baseTX-HD",
> # "100baseTX-FD" and "" (nothing).
> MEDIA=auto
> AUTONEG=never
> MDI_MODE=mdi
>
>
> # If you are using DHCP the following variables will not be used.
> IP=192.168.1.9
> NETMASK=255.255.255.0
> BROADCAST=192.168.1.255
> GATEWAY=192.168.1.15
> ---------------------------------------------
>
> i changed the mode to mdix and reboot,
>
> this is mii-diag and mii-diag.log
>
>
> # mii-diag
> Using the default interface 'eth0'.
> Basic registers of MII PHY #0: 0180 7849 000e 7237 01e1 0000 0000 0000.
> Basic mode control register 0x0180: Auto-negotiation disabled, with
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
> Link partner information is not exchanged when in fixed speed mode.
>
> End of basic transceiver information.
>
> # cat /var/log/mii-diag.log
> mii-diag.c:v2.11 3/21/2005 Donald Becker (becker at scyld.com)
> http://www.scyld.com/diag/index.html
> Using the new SIOCGMIIPHY value on PHY 0 (BMCR 0x0000).
> Basic mode control register 0x0180: Auto-negotiation disabled, with
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
>
> This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
> 10baseT.
> Able to perform Auto-negotiation, negotiation not complete.
> Link partner information is not exchanged when in fixed speed mode.
>
> End of basic transceiver information.
>
> libmii.c:v2.11 2/28/2005 Donald Becker (becker at scyld.com)
> http://www.scyld.com/diag/index.html
> MII PHY #0 transceiver registers:
> 0180 7849 000e 7237 01e1 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0140 0005 0800 47dd 2882 0000 0000 0010
> 0000 0000 0000 0000 0000 0000 0000 0000.
> Basic mode control register 0x0180: Auto-negotiation disabled!
>
> Speed fixed at 10 mbps, full-duplex.
> Internal Collision-Test enabled!
> Basic mode status register 0x7849 ... 7849.
> Link status: not established.
>
> Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
> Able to perform Auto-negotiation, negotiation not complete.
>
> Vendor ID is 00:03:9c:--:--:--, model 35 rev. 7.
> No specific information is known about this transceiver type.
> I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
> Advertising no additional info pages.
> IEEE 802.3 CSMA/CD protocol.
> Link partner capability is 0000:.
> Negotiation did not complete.
>
> Monitoring the MII transceiver status.
> 00:00:21.893 Baseline value of MII BMSR (basic mode status register) is
> 7849.
> Value of MII BMSR (basic mode status register) is 7849.
>
>
> do you think i can change this? it seems related to the problem...
> AUTONEG=never
>
> for this (like your file)
> AUTONEG=normal
>
>
>
> 2012/6/6 Andrey Filippov <support-list at support.elphel.com>
>
>> Carlos,
>>
>> the 10mbps would explain everything and I've never seen that speed in the
>> camera. And before trying to fix problem with reflashing (making sure to
>> overwrite the network configuration) I would like to try to find out - what
>> is wrong now. The mii-diag output in the camera I have shows:
>>
>> [root at Lens_Adjust /var/log]797# mii-diag
>> Using the default interface 'eth0'.
>> Basic registers of MII PHY #0: 3100 786d 000e 7237 01e1 cde1 0009 0000.
>> The autonegotiated capability is 01e0.
>> The autonegotiated media type is 100baseTx-FD.
>> Basic mode control register 0x3100: Auto-negotiation enabled.
>> You have link beat, and everything is working OK.
>> Your link partner advertised cde1: Flow-control 100baseTx-FD 100baseTx
>> 10baseT-FD 10baseT, w/ 802.3X flow control.
>> End of basic transceiver information.
>>
>> There is also a file /var/log/mii-diag.log , here is what it has on my
>> camera:
>> [root at Lens_Adjust /var/log]797# cat /var/log/mii-diag.log
>> mii-diag.c:v2.11 3/21/2005 Donald Becker (becker at scyld.com)
>> http://www.scyld.com/diag/index.html
>> Using the new SIOCGMIIPHY value on PHY 0 (BMCR 0x0000).
>> The autonegotiated capability is 01e0.
>> The autonegotiated media type is 100baseTx-FD.
>> Basic mode control register 0x3100: Auto-negotiation enabled.
>> You have link beat, and everything is working OK.
>> This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
>> 10baseT.
>> Able to perform Auto-negotiation, negotiation complete.
>> Your link partner advertised cde1: Flow-control 100baseTx-FD 100baseTx
>> 10baseT-FD 10baseT, w/ 802.3X flow control.
>> End of basic transceiver information.
>> libmii.c:v2.11 2/28/2005 Donald Becker (becker at scyld.com)
>> http://www.scyld.com/diag/index.html
>> MII PHY #0 transceiver registers:
>> 3100 786d 000e 7237 01e1 cde1 0009 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0140 002d 0f00 47bc 3082 0000 0000 0010
>> 00d0 0000 0000 0000 0000 0000 0000 0000.
>> Basic mode control register 0x3100: Auto-negotiation enabled.
>> Basic mode status register 0x786d ... 786d.
>> Link status: established.
>> Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
>> Able to perform Auto-negotiation, negotiation complete.
>> Vendor ID is 00:03:9c:--:--:--, model 35 rev. 7.
>> No specific information is known about this transceiver type.
>> I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
>> Advertising no additional info pages.
>> IEEE 802.3 CSMA/CD protocol.
>> Link partner capability is cde1: Flow-control 100baseTx-FD 100baseTx
>> 10baseT-FD 10baseT.
>> Negotiation completed.
>> Monitoring the MII transceiver status.
>> 00:00:16.139 Baseline value of MII BMSR (basic mode status register) is
>> 786d.
>> Value of MII BMSR (basic mode status register) is 786d.
>>
>>
>> I would also try to change MDI/MDIX settings (provided your
>> computer/switch is "auto mdi/mdix"). Edit the /etc/conf.d/net.eth0 :
>>
>> # (C) Copyright 2005-2007, Axis Communications AB, LUND, SWEDEN
>> # This file is released under the GPL v2.
>>
>> # Uncomment the following line to override the generic hardware address
>> # (usually the serial number) for this interface only.
>> # MAC=00:0E:64:00:00:00
>>
>> # Valid boot protocols are "dhcp" and "none" (anything other than "dhcp"
>> works).
>> BOOTPROTO=none
>> DHCP_CLIENT="/sbin/udhcpc -i eth0 -H $(hostname)"
>>
>> # Valid media types are "auto", "10baseT-HD", "10baseT-FD",
>> "100baseTX-HD",
>> # "100baseTX-FD" and "" (nothing).
>> MEDIA=auto
>> AUTONEG=normal
>>
>> # If you are using DHCP the following variables will not be used.
>> IP=192.168.0.236
>> NETMASK=255.255.255.0
>> BROADCAST=192.168.0.255
>> GATEWAY=192.168.0.15
>>
>> # MDI/MDIX configuration; nothing or any - auto by default; "mdix" - for
>> MDIX (cross); "mdi" - for MDI (normal)
>> MDI_MODE=
>>
>>
>> -------------------------------
>>
>> You may try to change the last line to
>> MDI_MODE=mdi
>> or
>> MDI_MODE=mdix
>>
>> and reboot the camera :
>> reboot -f
>> And copy /var/log/mii-diag.log
>>
>>
>> Just make sure you can edit the file with vi:
>>
>> vi /etc/conf.d/net.eth0
>>
>> because if you set some wrong with the network, you'll only be able to
>> communicate with it over the serial console (or have to use low-level
>> reflash).
>>
>> Andrey
>>
>>
>>
>>
>>
>> On Wed, Jun 6, 2012 at 10:30 AM, Carlos Padial <palidoestudio2 at gmail.com>wrote:
>>
>>> hi Andrey
>>>
>>> i have managed to send commands with minicom (it seems with ttylog it is
>>> not possible)
>>>
>>> we have been studying Flavio's article and we are aware about the:
>>>
>>> Recording + streaming statistics
>>> 2064×896 @ 23.994 JP46
>>> 96% 467k 51-52% 53-56%
>>>
>>> i supose our 1280x720 57K config should be low enougth for the camera
>>> cpu...
>>>
>>> anyway, the problem appears only when using the camera to get the
>>> streaming, i have no dopne any test with both record and streaming. just
>>> streaming
>>>
>>> i attach you a file with the test i made (in sheet 1 is the initial
>>> configuration, in sheet 2 the tests...)
>>>
>>> i observed that mii-diag says: Speed fixed at 10 mbps, full-duplex.
>>>
>>> and in my pc ethtool eth0 also says speed 10mbps for the ethernet...
>>>
>>> i'm using this to config eth in the pc, but then i cannot connect with
>>> the camera...
>>>
>>> ethtool --change eth0 speed 100 autoneg off duplex full
>>>
>>> i assume i must change the camera to 100mbps...
>>>
>>> it makes sense with the framesize limit of flavio (467K) but divided by
>>> 10.
>>>
>>> anyway, here is the collected data,
>>>
>>> thanks :)
>>>
>>> 2012/6/5 <support-list-request at support.elphel.com>
>>>
>>>> Send Support-list mailing list submissions to
>>>> support-list at support.elphel.com
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>>
>>>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>>>>
>>>> or, via email, send a message with subject or body 'help' to
>>>> support-list-request at support.elphel.com
>>>>
>>>> You can reach the person managing the list at
>>>> support-list-owner at support.elphel.com
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of Support-list digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. Re: hi from kinoraw (Andrey Filippov)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Tue, 5 Jun 2012 12:08:36 -0600
>>>> From: Andrey Filippov <andrey at elphel.com>
>>>> To: Carlos Padial <info at kinoraw.net>
>>>> Cc: Elphel Support List <support-list at support.elphel.com>
>>>> Subject: Re: [Elphel-support] hi from kinoraw
>>>> Message-ID:
>>>> <
>>>> CAF1q_iiKvbp8KbfXEyJHkWWTS0RqPnSH9O7hXfBS3_K4RvqjGg at mail.gmail.com>
>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>>
>>>> Hello Carlos,
>>>>
>>>> Shipping camera back and fourth can be expensive, so I'm trying to make
>>>> sure it can be a hardware problem related to fixing the 10369 board with
>>>> the connector that fell off. I can not think of any type of failure that
>>>> can manifest itself in that way. So I would try to make a table - what
>>>> works (always) and what does not. Can you make such table, using the
>>>> previous results and add some more?
>>>> I would test streaming and really low data rate (low fps and/or image
>>>> quality) with the serial port of the camera connected to the camera and
>>>> monitored, and streamer (str) killed and restarted from console (so
>>>> output,
>>>> if any will go to console). If the streamer will fail - what happens to
>>>> the
>>>> camera:
>>>> 1 - the serial console connection will be dead,
>>>> 2 - serial console will continue to be operational, but no network
>>>> connection (can not ping camera from outside)
>>>> 3 - console alive, network alive
>>>> In the case of the network down - what will the "ifconfig" and
>>>> "mii-diag"
>>>> output?
>>>>
>>>> Another test - if the camera is not streaming, just connected - will it
>>>> continue to be accessible after a long time?
>>>> What about recording to the external SATA HDD - does it work? Or also
>>>> fails?
>>>>
>>>> Andrey
>>>>
>>>>
>>>>
>>>> On Tue, Jun 5, 2012 at 11:14 AM, Carlos Padial <info at kinoraw.net>
>>>> wrote:
>>>>
>>>> > Dear Andrey,
>>>> >
>>>> > we hope everything's fine around there. We get in touch with you
>>>> because
>>>> > we've tried to sort out the problems we've had. As you suggested we
>>>> would
>>>> > like to send it to Utah so you could check and fix it.
>>>> >
>>>> > We hope you can help us with this. Could you please specify the
>>>> shipment
>>>> > details (customs procedures and others)? Should we send just the
>>>> camera
>>>> > body in its case?
>>>> >
>>>> > Thank you very much for all your support
>>>> >
>>>> > Best wishes
>>>> >
>>>> >
>>>> >
>>>> >
>>>> -------------- next part --------------
>>>> An HTML attachment was scrubbed...
>>>> URL: <
>>>> http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20120605/69e4954f/attachment-0001.html
>>>> >
>>>>
>>>> ------------------------------
>>>>
>>>> _______________________________________________
>>>> Support-list mailing list
>>>> Support-list at support.elphel.com
>>>>
>>>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>>>>
>>>>
>>>> End of Support-list Digest, Vol 34, Issue 3
>>>> *******************************************
>>>>
>>>
>>>
>>>
>>> --
>>> Carlos Padial
>>> surreal.asturnazari.es
>>>
>>> _______________________________________________
>>> Support-list mailing list
>>> Support-list at support.elphel.com
>>>
>>> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>>>
>>>
>>
>
>
> --
> Carlos Padial
> surreal.asturnazari.es
>
> _______________________________________________
> Support-list mailing list
> Support-list at support.elphel.com
> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20120606/e75d7e27/attachment-0002.html>
More information about the Support-list
mailing list