search for: eeprom

On Thu, Mar 23, 2017 at 11:26 AM, Gene Heskett <gheskett at shentel.net> wrote: > Have you the file to be used to update the EEPROM with? Eaton shows a firmware file: https://powerquality.eaton.com/Support/Software-Drivers/Downloads/5P-UPS-firmware.asp However I'm not sure if it is for the questionable EEPROM and if so maybe it is downlevel from the current reported firmware. upsc shows: ups.firmware: 04 and the file is...

...NG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach: bge0 attach returned 6 bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3 miibus0: <MII bus> on bge1 brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0 brgphy0: 10baseT, 1...

> There is a posting public about Intel ethernet adapters and their > packets of death: > > http://blog.krisk.org/2013/02/packets-of-death.html > > Now, how can we test the EEPROM from FreeBSD, similar to the > ethtool of Linux ? There is no such tool. If you want to dump EEPROM contents, you can do so via one of the following ways for em(4) NICs or igb(4) NICs, as root: sysctl dev.XXX.Y.nvm=1 (for recent/newer FreeBSD) sysctl dev.XXX.Y.debug=2 (for older FreeBSD)...

Hi Chris 2017-03-23 16:58 GMT+01:00 Sonic <sonicsmith at gmail.com>: > On Thu, Mar 23, 2017 at 11:26 AM, Gene Heskett <gheskett at shentel.net> > wrote: > > Have you the file to be used to update the EEPROM with? > > Eaton shows a firmware file: > https://powerquality.eaton.com/Support/Software-Drivers/ > Downloads/5P-UPS-firmware.asp > > However I'm not sure if it is for the questionable EEPROM and if so > maybe it is downlevel from the current reported firmware. > upsc sh...

Hello, Sorry if any of this is obvious - I'm new to NUT. NUT via upsc is displaying (edited for length): device.model: Eaton 5P 2200 device.type: ups driver.name: usbhid-ups ups.alarm: Fatal EEPROM fault! ups.status: ALARM OL CHRG ups.test.interval: 604800 ups.test.result: Done and passed driver.version: 2.7.2 driver.version.data: MGE HID 1.33 driver.version.internal: 0.38 Is this possibly a firmware or configuration issue? Does NUT report the firmware version (it's not jumping out at m...

...:00 Sonic <sonicsmith at gmail.com>: > Hello > Hi Chris > Sorry if any of this is obvious - I'm new to NUT. > > NUT via upsc is displaying (edited for length): > > device.model: Eaton 5P 2200 > device.type: ups > driver.name: usbhid-ups > ups.alarm: Fatal EEPROM fault! > ups.status: ALARM OL CHRG > ups.test.interval: 604800 > ups.test.result: Done and passed > driver.version: 2.7.2 > driver.version.data: MGE HID 1.33 > driver.version.internal: 0.38 > > Is this possibly a firmware or configuration issue? > not sure, first time th...

On Thursday 23 March 2017 09:29:55 Sonic wrote: > Hello, > > Sorry if any of this is obvious - I'm new to NUT. > > NUT via upsc is displaying (edited for length): > > device.model: Eaton 5P 2200 > device.type: ups > driver.name: usbhid-ups > ups.alarm: Fatal EEPROM fault! > ups.status: ALARM OL CHRG > ups.test.interval: 604800 > ups.test.result: Done and passed > driver.version: 2.7.2 > driver.version.data: MGE HID 1.33 > driver.version.internal: 0.38 > > Is this possibly a firmware or configuration issue? > > Does NUT report the...

...FW is "02.12.0025". Hi Arno, According to that link, unless I'm missing something, as the 5P2200RT is a 2U sized unit (2 rack spaces) the proper firmware should be "03.00.0000". Firmware "02.12.0025" is listed for 1U sized units. > This FW upgrade may fix the EEPROM fault too, but it's not yet confirmed. > Please update me if you go through this upgrade. I certainly will - but it's quite problematic as there are no Windows systems in the server room. It's a bit unfathomable that in 2017 a manufacturer doesn't fully support such critical fu...

...01 adapter at 08c0 Do you want to scan it? (YES/no/selectively): Client found at address 0x08 Client found at address 0x2e (..) (..) Probing for `National Semiconductor LM85 or LM96000'... Success! (confidence 7, driver `lm85') (..) (..) Client found at address 0x50 Probing for `SPD EEPROM'... Success! (confidence 8, driver `eeprom') Probing for `DDC monitor'... Failed! Probing for `Maxim MAX6900'... Failed! Client found at address 0x52 Probing for `SPD EEPROM'... Success! (confidence 8, driver `eeprom') Client found at address 0x60 Client found at add...

...e any thing in the the 8kB of RAM that is always the same (lookup table etc.) or did you already think of that? I'm curios since the ATmega168 got 16kB of Flash that is as fast as the RAM (I think the chip is made so it limits its maximum speed to the slowest memory, flash. it also has some EEPROM besides the SRAM). //P?r Ps. ATmega spec: FLASH: 16kB EEPROM: 512B SRAM: 1kB SPEED: 0-20MHz Architecture: 8-bit RISC, no FPU. Site: http://www.atmel.com/dyn/products/product_card.asp?part_id=3303

...ist for further discussions... 2007/5/28, Alex Brodsky <abrodsky at acs.uwinnipeg.ca>: > Hi, > > My name is Alex Brodsky, I am a faculty member at University of > Winnipeg. > > I have been using NUT for a while now (on OpenBSD), but noticed that > I could not program the EEPROM values (using upsrw) of my Smart UPS > SC1000, even though, it worked fine with a Smart UPS 1500. The > manual for the SC1000 claims that the eeprom values could be programmed. > > I investigated further and discovered that the result of the 'a' > command to the SC1000 UPS,...

...wn reason both my monitors ended up with a corrupted EDID. They both provide VGA and DVI input. The VGA input works fine, while DVI is broken because of the EDID issue. Using these [1] instructions I have been able to read the EDID and fix it. Unfortunately I'm not able to write it back to the eeprom. I always get this message: i2c i2c-1: sendbytes: NAK bailout. This is what I usually see in /var/log/message [dump of the EDID] nouveau 0000:01:00.0: DVI-D-1: EDID block 0 invalid. [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-D-1 Do you know why writing to the monitor does no...

Hi, We have an old Win98 box at work that is used for programming GALs and EEPROMs, however we find that if the file is modified on the Unix side the Win98 box doesn't notice. This is rather annoying when you are iterating a design as you can imagine! One work around is to open a DOS box and 'type' the file - this seems to force it to re-get the file. Does anyon...

...tfile sensors-detect-output.txt As soon as I execute the recommended 'modprobe smbus-arp' I receive the following message: FATAL: Module smbus_arp not found. When I execute sensors, I receive the following: ====================================================== [root at matrix ~]# sensors eeprom-i2c-0-57 Adapter: SMBus I801 adapter at 1100 Unknown EEPROM type (8) eeprom-i2c-0-53 Adapter: SMBus I801 adapter at 1100 Unknown EEPROM type (8) ====================================================== I also attached sensors.conf from /etc for reference. I'm using xen-3.0.2 with kernel 2.6.16...

...Todd wrote.... > For those of you wanting to salvage your Cisco ATA-186 after > inadvertent locking, or after recovering your devices from a vendor > who has locked them, here is a rainy-day project for you: > somedoc.pdf..... Immediately strides to ATA, rips off cover... woohoo, EEPROM is socketed.... well maybe I'll just copy the contents of a working ATA into the programmer, and reflash the locked one, taking care to change the MAC address and serial number...... > Please aim your negative karma at Cisco for creating a piece of > hardware that can be rendered usele...

...MMU - 100 MHz System Bus - MaverickKey? IDs - 32-bit unique ID can be used for DRM compliance 128-bit random ID - Integrated Peripheral Interfaces - 16-bit SDRAM Interface up to 4 banks - 16-bit SRAM/FLASH/ROM - Serial EEPROM Interface - 1/10/100 Ethernet MAC - Two UARTs - Two-port USB2.0 Full Speed Host (OHCI) (12 Mbits per second) - IrDa Interface - Analog to Digital Converter - Serial Peripheral Interface (SPI) Port - 2-channel...

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

...s > > I have loads of relatively old smart upses that I currently control using a > bit patched version of apcupsd - the reason for those patches is the age of > the upses - roughly 10 years old+, which are can be a bit tricky to control. > From issues related to them: > > - no eeprom programming or calibration. So - no grace periods or minimal > battery level to power up > - @000 command is no-op - the only effect of it is happy led flashing > - @nnn will power up the ups right after 6*nnn minutes unconditionally > (regardless if the power returned or not - modern u...

...fos to NUT. Can you tell me what the prefered method is for NUT? The MCU is gattering the infos like: 1) own identification (Maxim DS28CZ04) 0000 -> "12345678" # serial number \ 0001 -> "24V DC modular ATX # real name of the modue | I?C EEPROM 0002 -> "electronica at tdnet" # Vendor Real Name | Maxim DS28CZ04 0003 -> "1.0.0" # Version | 0004 -> "2010-07-08" # Manufacturing Date / 0010 -> "24,0"...