Patched and re-ran. I can see the difference in the debug output, but the
behavior does not appear to be affected. I've attached both a debug and
dmesg log. This time, I've included the dmesg messages printed as a result
of running OpenOCD.
Cheers!
Benjamin Rodgers
On Wed, Aug 10, 2016
On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson <
andreas.fritiof...@gmail.com> wrote:
>
> On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <benjamin.rodgers@
> verizondigitalmedia.com> wrote:
>
>> I compiled OpenOCD 0.9.0 from source first without
>
d
> Warn : use 'feroceon.cpu' as target identifier, not '0'
> sheevaplug_load_uboot
> Info : clock speed 2000 kHz
> Info : TAP feroceon.cpu does not have IDCODE
> Info : TAP auto0.tap does not have IDCODE
> Info : TAP auto1.tap does not have IDCODE
> Info : TAP auto2.tap does not have IDCODE
> Info : TAP auto3.tap does not have IDCODE
Cheers!
Benjamin Rodgers
Confirmed that downgrading from 'libpulsecore5_0.9.10-3+lenny2_amd64' to
'libpulsecore5_0.9.10-3+lenny1_amd64' resolves the issue. Also
confirmed that adding a distclean + bootstrap to debian/patches resolves
the issue. However, am I wrong to assume that the output of bootstrap
(or any of the
Package: abiword
Version: 2.2.9-1
Severity: important
Tags: experimental
I am currently using abiword 2.2.9-1 and I was using libfribidi0
0.10.4-6. When using this combination, typing anything into AbiWord
would crash and produce the following error:
abiword: symbol lookup error: abiword:
Package: pciutils
Version: 1:2.1.11-15
Severity: normal
The subvendor ID provided by lspci -mn is erroneous. Apparently lspci
is duplicating the device ID instead of printing the subvendor ID.
Example follows:
__ BEGIN EXAMPLE __
lspci -mn
00:00.0 0600 10de 01e0 c1 00 01e0 80ac
[...]
6 matches
Mail list logo
