As Bill Gatliff wrote: > Bummer. Neither that, nor adding information to udev/rules.d seems > to help. :(
Then use -vvvv (four "v"s). This will print out the entire communication log, so we can see the actual error code. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
