Closed
Bug 697421
Opened 13 years ago
Closed 13 years ago
Please investigate dongles on talos-r4-lion-002, 003
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Assigned: mlarrain)
References
Details
These machines are unable to set 1600x1200x32. The last time we experienced this, it was corrected by reinserting the dongles. This isn't currently blocking me, but we need to address it before we put these machines into production
Updated•13 years ago
|
Assignee: server-ops-releng → mlarrain
Updated•13 years ago
|
colo-trip: --- → scl1
Reporter | ||
Comment 1•13 years ago
|
||
Any updates here?
Comment 2•13 years ago
|
||
As I mentioned last week, we did not have anyone available to go to the datacenter to do work. This is on the list of things to look at this week.
Assignee | ||
Comment 3•13 years ago
|
||
reseated the dongles and had jhford test. Problem resolved.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Matthew Larrain[:digipengi] from comment #3) > reseated the dongles and had jhford test. Problem resolved. 002 is still showing problems when I log in talos-r4-snow-002:~ cltbld$ screenresolution get Display 0: 1280x1024x32 talos-r4-snow-002:~ cltbld$ screenresolution list Available Modes on Display 0 1x1x8 1x1x16 1x1x32 1x1x64 1x1x96 800x600x8 800x600x16 800x600x32 800x600x64 800x600x96 1024x768x8 1024x768x16 1024x768x32 1024x768x64 1024x768x96 1280x1024x8 1280x1024x16 1280x1024x32 1280x1024x64 1280x1024x96 1680x1050x8 1680x1050x16 1680x1050x32 1680x1050x64 1680x1050x96 1280x1024x32
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•13 years ago
|
||
Reseated the correct dongle and it's displaying correctly now.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•