Joerg Wunsch wrote: > 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. >
Done, posted here: http://jupiter.billgatliff.com/~bgat/avrdude-logs There is a capture of the console output with -vvvv, and output from strace. b.g. -- Bill Gatliff [EMAIL PROTECTED] _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
