Linux Framebuffer drivers for small TFT LCD display modules. Development has moved to https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/fbtft?h=staging-testing
1.85k
stars
494
forks
source link
USB crash when using original fbtft without adafruit's modifications #304
I'm using the PiTFT 2,8" capacitive version and the original fbtft (i compiled the FT6x06 module at my own). I'm using Arch Linux, all up to date.
When i play audio with my audio usb card and force screen updates (for example moving the mouse or what ever), sound crackles. When i do not stop moving the curser, than some moments later, the hole USB system crashes: No USB device is working, and no ethernet. I tried powered usb hub (not working) and tried USB 1.1 (kernel argument) (this works, but than all other devices are not working).
When i use the the whole /boot and /lib/modules/, /lib/modules/3.18.14-v7+/ (with alredy compiled ft6x06) and /lib/firmware folder from an existing adafruit installation and use this in my arch linux installation, my arch linux boots up fine and sound is absolutly ok.
I would try to debug, but there is absolutly no dmesg or journalctl entry related to this issue.
I'm using the PiTFT 2,8" capacitive version and the original fbtft (i compiled the FT6x06 module at my own). I'm using Arch Linux, all up to date.
When i play audio with my audio usb card and force screen updates (for example moving the mouse or what ever), sound crackles. When i do not stop moving the curser, than some moments later, the hole USB system crashes: No USB device is working, and no ethernet. I tried powered usb hub (not working) and tried USB 1.1 (kernel argument) (this works, but than all other devices are not working).
When i use the the whole /boot and /lib/modules/, /lib/modules/3.18.14-v7+/ (with alredy compiled ft6x06) and /lib/firmware folder from an existing adafruit installation and use this in my arch linux installation, my arch linux boots up fine and sound is absolutly ok.
I would try to debug, but there is absolutly no dmesg or journalctl entry related to this issue.