-
Notifications
You must be signed in to change notification settings - Fork 33
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
Issue with XL IQ routes #31
Comments
The calibration results are stored in |
I had the same problem, and no it keeps coming up with the blue screen. Once I find my screwdrivers I'll have a look inside. |
Ok, the device doesn't present as a drive anymore it looks like a USB ethernet device. I had to load the driver manually and manually set the IP address and ping works. Telnet and FTP respond as follows: telnet: Unable to connect to remote host: Connection refused ftp: connect: Connection refused not sure how to connect as I'd love to delete the touchscreen config file... still looking for my screwdrivers with the torx bits. |
Oops, Ping isn't working. The device is detected but doesn't seem to respond. |
15 second reset bring me back to where I can use it in disk mode with my computer... but when I disconnect I get the Blue screen again. I'll try deleting the file as you suggested above. |
Ok, after removing that file I get a black screen. I'm pretty sure I saw an answer about framebuffer settings, I'll go look for that now. |
Precompiled version doesn't work, but compiling chokes on this step... Can't find libjpeg-6b.tar.gz --2018-09-14 20:57:58-- ftp://ftp.pl.freebsd.org/vol/rzm4/GraphicsMagick/delegates/libjpeg-6b.tar.gz |
My old XL IQ routes is no longer supported for officials updates, so i tried to install opentom on it, it worked, i made the touchscreen calibration but since then, it just display a blue screen with a tiny rocket on the up left of the screen and i can't do anything else, impossible to restart or access to the internal memory (no SD card on this model), maybe i missed something ?
The text was updated successfully, but these errors were encountered: