video hang up


#1

When I hook my monitor up to DC-125 it sets proper resolultion accodring to xrandr 1366x768. However, all I see on the screen is diagonal lines.

Screen 0: minimum 320 x 200, current 1366 x 768, maximum 2048 x 2048
DVI-3 connected 1366x768+0+0 698mm x 392mm
1366x768 59.8*+
1024x768 75.1 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 66.7 60.0
720x400 70.1
640x400 70.0 60.0

if I plug in the DC-125 without the monitor connected it sets it to 1024x768 which actually displays right. But it starts having artifacts show up (mouse leaving trail etc…) after about 5 minutes of light use the display will completely lockup and I will get the following in dmesg repeating over and over. The only way I can get out of it is to unplug the DC-125.
[9838.328043] [drm] wait for urb interrupted: ffffffc2 available: 0
[9839.328042] [drm] wait for urb interrupted: ffffffc2 available: 0
[9840.328051] [drm] wait for urb interrupted: ffffffc2 available: 0
[9841.328049] [drm] wait for urb interrupted: ffffffc2 available: 0
[9842.328050] [drm] wait for urb interrupted: ffffffc2 available: 0
[9843.328040] [drm] wait for urb interrupted: ffffffc2 available: 0

I’m running fedora18 with all the latest updates. any help you could give would be wonderful.


#2

I forgot to mention one item. I started with a “minimal” install. so it is entirely possible that I’m missing some rpm.


#3

just an update
I got past the resolution problem by adding the following
cat /etc/X11/xorg.conf.d/01-monitor.conf
Section “Monitor”
Identifier “On-Lap”
Modeline “1280x720R” 63.75 1280 1328 1360 1440 720 723 728 741 +hsync -vsync
VendorName “MTC”
EndSection
Section “Screen”
Identifier “Screen1”
Device “pluggable”
Monitor “On-Lap”
DefaultDepth 24
SubSection “Display”
Modes “1280x720R”
EndSubSection
EndSection

I still get the hangup but only on one machine. I think it just doesn’t supply enough power to the unit. Still testing.


#4

digging through the Xlogs I found the following difference in the working vs non working machine.
====WORKING===
[619011.528] (EE) modesetting(0): Unknown EDID version 0
[619011.528] (II) modesetting(0): EDID for output DVI-9
[619011.528] (II) modesetting(0): Printing probed modes for output DVI-9
[619011.528] (II) modesetting(0): Modeline "1280x720R"x59.7 63.75 1280 1328 1360 1440 720 723 728 741 +hsync -vsync (44.3 kHz UP)
[619011.528] (II) modesetting(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[619011.528] (II) modesetting(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[619011.528] (II) modesetting(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[619011.528] (II) modesetting(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[619011.528] (II) modesetting(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[619011.528] (II) modesetting(0): Output DVI-9 connected
[619011.528] (II) modesetting(0): Using user preference for initial modes
[619011.528] (II) modesetting(0): Output DVI-9 using initial mode 1280x720R +0+0
[619011.528] (II) modesetting(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[619011.528] (==) modesetting(0): DPI set to (96, 96)

====Not WORKING===
[284.242] (II) modesetting(0): EDID for output DVI-3
[284.242] (II) modesetting(0): Manufacturer: MTC Model: 31 Serial#: 1
[284.242] (II) modesetting(0): Year: 2012 Week: 15
[284.242] (II) modesetting(0): EDID Version: 1.3
[284.242] (II) modesetting(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[284.242] (II) modesetting(0): Sync: Separate Composite
[284.242] (II) modesetting(0): Max Image Size [cm]: horiz.: 70 vert.: 39
[284.242] (II) modesetting(0): Gamma: 2.20
[284.242] (II) modesetting(0): DPMS capabilities: Off; RGB/Color Display
[284.242] (II) modesetting(0): First detailed timing is preferred mode
[284.242] (II) modesetting(0): redX: 0.639 redY: 0.342 greenX: 0.297 greenY: 0.615
[284.242] (II) modesetting(0): blueX: 0.146 blueY: 0.068 whiteX: 0.313 whiteY: 0.329
[284.242] (II) modesetting(0): Supported established timings:
[284.242] (II) modesetting(0): 720x400@70Hz
[284.242] (II) modesetting(0): 640x480@60Hz
[284.242] (II) modesetting(0): 640x480@67Hz
[284.242] (II) modesetting(0): 640x480@72Hz
[284.242] (II) modesetting(0): 640x480@75Hz
[284.242] (II) modesetting(0): 800x600@56Hz
[284.242] (II) modesetting(0): 800x600@60Hz
[284.242] (II) modesetting(0): 800x600@72Hz
[284.242] (II) modesetting(0): 800x600@75Hz
[284.242] (II) modesetting(0): 832x624@75Hz
[284.242] (II) modesetting(0): 1024x768@60Hz
[284.242] (II) modesetting(0): 1024x768@70Hz
[284.242] (II) modesetting(0): 1024x768@75Hz
[284.242] (II) modesetting(0): Manufacturer’s mask: 0
[284.242] (II) modesetting(0): Supported standard timings:
[284.242] (II) modesetting(0): #0: hsize: 640 vsize 400 refresh: 60 vid: 49
[284.242] (II) modesetting(0): #1: hsize: 640 vsize 400 refresh: 70 vid: 2609
[284.242] (II) modesetting(0): #2: hsize: 800 vsize 600 refresh: 60 vid: 16453
[284.242] (II) modesetting(0): #3: hsize: 800 vsize 600 refresh: 75 vid: 20293
[284.242] (II) modesetting(0): #4: hsize: 1024 vsize 768 refresh: 60 vid: 16481
[284.242] (II) modesetting(0): #5: hsize: 1024 vsize 768 refresh: 75 vid: 20321
[284.242] (II) modesetting(0): Supported detailed timing:
[284.242] (II) modesetting(0): clock: 85.5 MHz Image Size: 698 x 392 mm
[284.242] (II) modesetting(0): h_active: 1366 h_sync: 1436 h_sync_end 1579 h_blank_end 1792 h_border: 0
[284.242] (II) modesetting(0): v_active: 768 v_sync: 771 v_sync_end 774 v_blanking: 798 v_border: 0
[284.243] (II) modesetting(0): Monitor name: Monitor
[284.243] (II) modesetting(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 82 kHz, PixClock max 135 MHz
[284.243] (II) modesetting(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 82 kHz, PixClock max 135 MHz
[284.243] (II) modesetting(0): Serial No: 000001
[284.243] (II) modesetting(0): EDID (in hex):
[284.243] (II) modesetting(0): 00ffffffffffff003683310001000000
[284.243] (II) modesetting(0): 0f1601036c4627782aa2a5a3574c9d25
[284.243] (II) modesetting(0): 115054bfee003100310a4540454f6140
[284.243] (II) modesetting(0): 614f01010101662156aa51001e30468f
[284.243] (II) modesetting(0): 3300ba882100001e000000fc004d6f6e
[284.243] (II) modesetting(0): 69746f720a0a0a0a0a0a000000fd0038
[284.243] (II) modesetting(0): 4b1f520d000a202020202020000000ff
[284.243] (II) modesetting(0): 003030303030310a202020202020006b
[284.243] (II) modesetting(0): Printing probed modes for output DVI-3
[284.243] (II) modesetting(0): Modeline "1280x720R"x59.7 63.75 1280 1328 1360 1440 720 723 728 741 +hsync -vsync (44.3 kHz UP)
[284.243] (II) modesetting(0): Modeline "1366x768"x59.8 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync (47.7 kHz eP)
[284.243] (II) modesetting(0): Modeline "1280x720_60.00"x59.9 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync (44.8 kHz)
[284.243] (II) modesetting(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[284.243] (II) modesetting(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[284.243] (II) modesetting(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[284.243] (II) modesetting(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[284.243] (II) modesetting(0): Modeline "1024x576R"x59.8 42.00 1024 1072 1104 1184 576 579 584 593 +hsync -vsync (35.5 kHz)
[284.243] (II) modesetting(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[284.243] (II) modesetting(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[284.243] (II) modesetting(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[284.243] (II) modesetting(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[284.243] (II) modesetting(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[284.244] (II) modesetting(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[284.244] (II) modesetting(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[284.244] (II) modesetting(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[284.244] (II) modesetting(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[284.244] (II) modesetting(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[284.244] (II) modesetting(0): Modeline "640x400"x70.0 23.35 640 656 720 800 400 401 404 417 -hsync +vsync (29.2 kHz)
[284.244] (II) modesetting(0): Modeline "640x400"x60.0 19.51 640 648 712 784 400 401 404 415 -hsync +vsync (24.9 kHz)
[284.244] (II) modesetting(0): Output DVI-3 connected
[284.244] (II) modesetting(0): Using user preference for initial modes
[284.244] (II) modesetting(0): Output DVI-3 using initial mode 1280x720R +0+0
[284.244] (II) modesetting(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[284.244] (==) modesetting(0): DPI set to (96, 96)

Anybody have any ideas?


#5

I’m about ready to return this unit. The machine I need to have this working with doesn’t work with it. I have two machines I hook this up to. My desktop running FC18 and my mini server running FC18. Both see and load the desktops properly BUT my laptop works flawlessly and the mini server has sever video corruption during usage (mouse trails etc…) I’ve been working on this for a week. I have posted here numerous times trying to get some support from plugable (I’m willing to pay for support but there isn’t a phone number just this community form)

I’m running out of time to make this work reliably. I’m guessing I will just have to return what promised to be a good device. and look for something else.

one last note it isn’t a power issue. I went and bought a powered usb hub just to see if it was under powered but that wasn’t the problem.


#6

Hi Nate,

Sorry, we’re also at a loss as to what’s happening on Fedora 18. We’ve seen one or two other cases (including one in our office), where a certain pattern of Fedora package updates leaves the system in a state like what you’re describing.

Our experience is it doesn’t happen on every system – just like your experience where things are fine on one system, but not the other.

In the limited cases we’ve hit so far, people have resolved those problems either by re-installing F18 or by backing off the most recent Fedora update set and then re-upgrading. That’s what was done to our in-office machine, and now it’s working and we can’t get it *back* into the problem state to recreate what you’re seeing and learn more about it.

I have no idea what’s happening, but suspect some particular version of xorg, kernel drm, systemd, or udev is leaving behind a config file that then screws things up after it. Going back or re-installing removes that file and then re-upgrade at this point seems to take you straight past the problem.

But without the ability to recreate, we’re just not certain.

So I’m not sure what to recommend other than a re-install of Fedora 18. Based on a limited set of datapoints, it may “magically” resolve the issue.

I’m sorry, that’s a very unsatisfying answer. We don’t like to give the “reinstall” answer. I wish we knew more.

Given all this, the return and full refund is definitely no problem. Just visit http://amazon.com/returns – we try to make the process as quick and hassle-free as possible.

And it’s clear you’re very knowledgeable and committed, so if you do figure out the root cause behind why some F18 systems hit this problem and others don’t, please post back here – the answer would be a huge help to others.

Again, my apologies and please let us know if there’s a particular way we can help!

Bernie


#7

Thanks for the response. I now have a direction. I’m making a several different forms of the “broken” state (cp to USB drive, clonezilla) I will then try your suggested way of fixing it. Then if that does work I would be more than happy to send you a copy of the “broken” state for further diagnoses. I will also do a diff on the two images to see if I can find what changed.


#8

Thanks Nate!


#9

Fresh install of FC18 still has the same problem. Any other ideas?


#10

interesting. just for the fun of it I updated my fc18 this morning and now the corupption still happens but anywhere for 2-60seconds later it corrects itself. PROGRESS.
Here are the rpms that got installed with the updates.
tzdata-2013b-2.fc18.noarch
libisofs-1.2.8-1.fc18.x86_64
farstream02-0.2.2-2.fc18.x86_64
xorg-x11-drv-openchrome-0.3.2-1.fc18.x86_64
libmusicbrainz5-5.0.1-5.fc18.x86_64
libburn-1.2.8-1.fc18.x86_64
tzdata-java-2013b-2.fc18.noarch
audit-libs-python-2.2.3-2.fc18.x86_64
audit-2.2.3-2.fc18.x86_64
audit-libs-2.2.3-2.fc18.x86_64
gpg-pubkey-de7f38bd-501f4964


#11

more progress. I was just “cleaning up” the install and removed some rpms. the full problem returned. I tracked it down to gnome-shell. If it is installed the video corruption is cleaned up within 2-60 seconds. if it is uninstalled then the corruption remains indefinitely.


#12

more progress. I installed kde-workspace (my preferred desktop) and in the login screen the corruption is cleared up in 2-6 seconds. but once in KDE the corruption is indefinite.


#13

Focusing in on how the machine + monitor without edid works, but the one with doesn’t …

EDID is a data block that the graphics adapter queries from the monitor. Linux DRM has a different edid parser than the frame buffer subsystem.

Not getting edid is usually only with VGA (analog) connection to monitor, and often long (2m+) cable.

Can you swap stuff between the machines to get no edid on the currently failing system?

If it works, we can hone in on that. Not too confident, though.


#14

went and retested. I must have been looking at an old Xorg log. It does see it.

Here are the specs of the two machines
WORKING
lenovo T400 laptop
~]cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel® Core™2 Duo CPU P8600 @ 2.40GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
bogomips : 4787.89
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel® Core™2 Duo CPU P8600 @ 2.40GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
bogomips : 4787.89
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
~]$ free -m
total used free shared buffers cached
Mem: 3849 3697 151 0 71 1497
-/+ buffers/cache: 2128 1721
Swap: 5965 482 5483

NOT WORKING
xi3 X5 module
~]# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon™ 64 X2 Dual Core Processor 3400+
stepping : 2
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
bogomips : 2000.13
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon™ 64 X2 Dual Core Processor 3400+
stepping : 2
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
bogomips : 2000.13
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps
~]# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (int gfx)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 3c)
00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780E [Radeon HD 3200]
01:05.1 Audio device: Advanced Micro Devices [AMD] nee ATI RS780 HDMI Audio [Radeon HD 3000-3300 Series]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller (rev 10)
~]# free -m
total used free shared buffers cached
Mem: 1749 1670 78 0 39 909
-/+ buffers/cache: 720 1028
Swap: 7039 1 7038


#15

I did the following tests.
I used another laptop with a live fedora 18 disk and a different monitor. no problems.
I used live disk with problem machine and it had less problems. It was almost usable.

I’m now just wondering. Is my problem machine under spec for used of the dc-125? Is the data corruption I’m experiencing consistent with an underpowered machine?


#16

Hi Nate,

Thanks for the additional data points. You ruled out power (in terms of USB bus power) when you tried that powered USB hub.

In terms of CPU or GPU processing power, no, that couldn’t cause what you’re seeing.

What could cause it is a *different* GPU driver. In Fedora 17, displaylink devices were handled with the udlfb framebuffer driver (which I maintained). The nice thing about that was it had no dependencies on any other graphics drivers, and the framebuffer architecture is relatively super-simple.

In Linux kernels 3.4+ (and in Fedora 18), the udlfb driver was replaced by the udl driver, which is written to a different model – the Direct Rendering Manager (DRM) model – which is has more capabilities, but is much more complex. David Airlie (the DRM lead developer) did this tough work. The DRM architecture has a lot of potential capabilities, like using the main GPU to render all the pixels on the system, and then handing those pixels off to virtual, network or USB devices like DisplayLink ones for final rendering – that’s great. But the downside of all that is a lot of interdependencies and complexity – more that can go wrong in ways that are tough to diagnose and harder to maintain.

Xorg, systemd, and other components have been more tied in recent versions to the DRM model, so it’s not a matter of choosing the older model – you can’t easily configure the system back to using a simple framebuffer driver.

So, long story short,based on what you’re describing, I’m wondering if the problem might be in the different main GPU controllers (and likely different DRM driver for them).

From your logs, the working system has a:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

And the non-working system has a:
ATI RS780E [Radeon HD 3200]

Does the pattern of success/failure you’re seeing match this? Can you tell which DRM driver and version are loading for each GPU?

Again, thanks for all your work getting to the bottom of this, and seeing if there’s any way though it.

Thanks!
Bernie


#17

here is working system
]$ uname -a ; lsmod | grep drm
Linux yoda 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
drm_usb 12990 1 udl
drm_kms_helper 46708 2 udl,i915
drm 264680 6 udl,i915,drm_usb,drm_kms_helper
i2c_core 38353 5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit

and the NOT working system
]$ ssh root@192.168.1.1 “uname -a ; lsmod | grep drm”
Linux r2d2 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
drm_usb 12990 1 udl
drm_kms_helper 46708 2 udl,radeon
drm 264680 5 udl,ttm,drm_usb,drm_kms_helper,radeon
i2c_core 38353 5 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,radeon
]$ ssh root@192.168.1.1 modinfo radeon -F vermagic
3.8.5-201.fc18.x86_64 SMP mod_unload

I hope that is what you are looking for.


#18

I also had thought about this and removed radeon.ko module from being loaded when gdm started. It didn’t change anything.


#19

Hi Nate - I think to get any insight, we need to try to get a Fedora 18 setup going under ATI Radeon graphics, to see if we can recreate the problem specific to that machine.

Given that we have no clue at this point, please know that the refund is no problem at all – just visit http://amazon.com/returns and it’ll get processed quickly (if within 30 days). We don’t want you going past 30 days with a setup that isn’t working on the machine you’re wanting it to.

Thanks,
Bernie


#20

I have an idea to solve this. Is there a way you can contact me privately?