Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make no error,but run fltest "device no connect" #31

Open
lvzusheng opened this issue May 28, 2019 · 7 comments
Open

make no error,but run fltest "device no connect" #31

lvzusheng opened this issue May 28, 2019 · 7 comments

Comments

@lvzusheng
Copy link

run "ls /dev" can find "fl2000-3"
but run"sudo ./fltest " " fl2000 device not connected?"
and No screen signal

@dan1lo
Copy link

dan1lo commented Jul 16, 2019

What is your linux? Mine is ubuntu 19.6 and don' works too

@sarlacpit
Copy link

I have also had the same issue in Ubuntu18.04 - I've not found a way around it. The USB device mounts ok and I can see the files. The VGA part just doesn't work - Struggling to figure out why so far... Here is some system info and a dmesg.

dmesg

[79972.768783] usb 4-6: new SuperSpeed USB device number 7 using xhci_hcd
[79972.793095] usb 4-6: New USB device found, idVendor=1d5c, idProduct=2000
[79972.793099] usb 4-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[79972.794192] usb-storage 4-6:1.3: USB Mass Storage device detected
[79972.794371] scsi host5: usb-storage 4-6:1.3
[79972.811830] audit: type=1400 audit(1569326739.671:145): apparmor="DENIED" operation="open" profile="snap.brave.brave" name="/sys/devices/pci0000:00/0000:00:14.0/usb4/4-6/busnum" pid=7023 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[79972.811846] audit: type=1400 audit(1569326739.671:146): apparmor="DENIED" operation="open" profile="snap.brave.brave" name="/sys/devices/pci0000:00/0000:00:14.0/usb4/4-6/devnum" pid=7023 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[79973.813722] scsi 5:0:0:0: Direct-Access                               A001 PQ: 0 ANSI: 4
[79973.814105] sd 5:0:0:0: Attached scsi generic sg2 type 0
[79973.814237] sd 5:0:0:0: [sdb] 2047 4096-byte logical blocks: (8.38 MB/8.00 MiB)
[79973.814373] sd 5:0:0:0: [sdb] Write Protect is off
[79973.814375] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[79973.814504] sd 5:0:0:0: [sdb] No Caching mode page found
[79973.814509] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[79973.817499]  sdb:

lspci

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M]
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
0e:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

lsusb

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:64d0 Microdia 
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 007: ID 1d5c:2000  
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 8087:07da Intel Corp. 
Bus 003 Device 021: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard
Bus 003 Device 020: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
Bus 003 Device 019: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 018: ID 0424:2524 Standard Microsystems Corp. USB MultiSwitch Hub
Bus 003 Device 017: ID 04b4:120d Cypress Semiconductor Corp. 
Bus 003 Device 016: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

@ConsciousCode
Copy link

ConsciousCode commented Oct 24, 2019

In main.c, it has the device path hard-coded to /dev/fl2000-0, but the driver created /dev/fl2000-1 for me. Easy fix is to just change it to the correct name, "nicer" fix would be to search for the glob /dev/fl2000-*. When I run fltest with this edit, it runs with no error, though it doesn't seem to be generating an HDMI signal.

@diegodlpereira
Copy link

@ConsciousCode thanks - your proposed fix worked like a charm, nice catch

@ConstantineAlexandre
Copy link

In main.c, it has the device path hard-coded to /dev/fl2000-0, but the driver created /dev/fl2000-1 for me. Easy fix is to just change it to the correct name, "nicer" fix would be to search for the glob /dev/fl2000-*. When I run fltest with this edit, it runs with no error, though it doesn't seem to be generating an HDMI signal.

not work for me

@ConstantineAlexandre
Copy link

@ConsciousCode thanks - your proposed fix worked like a charm, nice catch

any suggests?

@lvzusheng
Copy link
Author

lvzusheng commented May 25, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants