you just recompile your usb driver with the changes needed and use that as your current driver.Can you explain how to apply / install the patch?
you just recompile your usb driver with the changes needed and use that as your current driver.Can you explain how to apply / install the patch?
Would it be possible to get a Teensy++ to 2.0 work?
Aren't those sodimm though? I wouldn't know how to use one.
because it doesn't.
yeah, you just need the right drivers. usb 2 is enough to run f-g, it just won't work with stock drivers.
But out of the box only with so-dimm contacts...There is a PI3 in the same form factor as PI0, its called CM3 or Raspberry PI Computing Module 3
Hi,
i have successfully used a Raspberry Pi 3 with Ubuntu Mate for Fusee Gelee!!!
Setup like Ubuntu
Tadaaa!!!
(Now i will setup a button (for example Pimoroni button-shim) to run fusee gelee on raspberry.)
Then, its no pc / Mac / vm or monitor neccessary to run the exploit :-))))
what the hell?! a pi 3 clearly has xhci. And a pi zero works just fine, too, just gotta use a ehci kernel with having certain restrictions removed.(look at f0f's example ehci patch to see what needs to be removed)
uuuh, not that i know of. I don't know why you would need that, though, just use a distro you like, look up the usb2/ehci driver source and recompile the ehci driver with f0f's changes.Is there a bootimage uploaded anywhere to try?
Hi,
i have successfully used a Raspberry Pi 3 with Ubuntu Mate for Fusee Gelee!!!
Setup like Ubuntu
Tadaaa!!!
(Now i will setup a button (for example Pimoroni button-shim) to run fusee gelee on raspberry.)
Then, its no pc / Mac / vm or monitor neccessary to run the exploit :-))))
UPDATE:
Here is my first try to run the exploit when the switch in RCM is connected to the Pi 3:
https://github.com/Darkmelman/udev_rule_fusee_gelee_pi3
Note:
to get idVendor and idProduct, run lsusb after connect the switch in RCM mode
UPDATE 2:
Errors corrected on GitHub and idVendor and idProduct added!
Its working fine! ;-))
Enter RCM mode and 3 seconds later fusee runs!
UPDATE 3:
Patched the kernel and now everything is ru running on a pi zero w, and thanks udev, automated ;-))
uuuh, not that i know of. I don't know why you would need that, though, just use a distro you like, look up the usb2/ehci driver source and recompile the ehci driver with f0f's changes.
Hi,how did you patch the kernel got issues with ehci
The patch works on a OSMC kernel. I just successfully launched a payload from a Raspberry Pi 3 model B+ running OSMC.
All it took was
git clone https://github.com/osmc/osmc.git
cd osmc/packages/kernel-osmc
wget https://raw.githubusercontent.com/f...aster/linux-ehci-enable-large-ctl-xfers.patch -O patches/rbp-040-linux-ehci-enable-large-ctl-xfers.patch
make rbp2
sudo dpkg -i *.deb
reboot
I actually tried on Ubuntu first (I only single boot Linux on all my systems) but failed and gave up when it failed to find a header file.I dont have an raspberry does any one know the right commands on ubuntu
Please could you share the patched OSMC kernel? Cheers!The patch works on a OSMC kernel. I just successfully launched a payload from a Raspberry Pi 3 model B+ running OSMC.
All it took was
git clone https://github.com/osmc/osmc.git
cd osmc/packages/kernel-osmc
wget https://raw.githubusercontent.com/f...aster/linux-ehci-enable-large-ctl-xfers.patch -O patches/rbp-040-linux-ehci-enable-large-ctl-xfers.patch
make rbp2
sudo dpkg -i *.deb
reboot
https://nofile.io/f/7dqzDPJkFd9/rbp2-image-4.14.34-1-osmc.debPlease could you share the patched OSMC kernel? Cheers!
The patch works on a OSMC kernel. I just successfully launched a payload from a Raspberry Pi 3 model B+ running OSMC.
URLs removed.