Hi Paul,
On Wed, Nov 09, 2016 at 11:02:34AM +0800, Paul Wise wrote:
> On Wed, Nov 9, 2016 at 1:53 AM, Andreas Tille wrote:
>
> > I guess I need some help in the build failure of r-bioc-shortread[1].
> ...
> > Error: segfault from C stack overflow
>
> You'll need to get the GDB bactrace for this.
On Wed, Nov 9, 2016 at 1:53 AM, Andreas Tille wrote:
> I guess I need some help in the build failure of r-bioc-shortread[1].
...
> Error: segfault from C stack overflow
You'll need to get the GDB bactrace for this.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sat, Nov 5, 2016 at 7:38 AM, Rogério Brito wrote:
> This is just a quick feedback from an armel tester.
FYI, armel is to be dropped after stretch so you will probably want to
plan your transition to new hardware.
https://lists.debian.org/msgid-search/20160722013605.ga...@einval.com
--
bye,
I noticed that the 'versatile' kernel flavour for armel doesn't work
any more. Starting with Linux 4.5, CONFIG_ARCH_VERSATILE depends on
CONFIG_ARCH_MULTI_V5, but we didn't enable the latter. The 'versatile'
kernel flavour is being built for ARMv7 but without support for any
particular platform,
On 11/8/2016 4:25 PM, Mark Morgan Lloyd wrote:
> On 08/11/16 21:00, Jerry Stuckle wrote:
>
>> Thanks for the input. There are no error messages from QEMU, and the
>> console status looks good. I started out with this on the QEMU mailing
>> list, but after lots of looking, people basically threw
On 08/11/16 21:00, Jerry Stuckle wrote:
Thanks for the input. There are no error messages from QEMU, and the
console status looks good. I started out with this on the QEMU mailing
list, but after lots of looking, people basically threw up their hands.
At this point it doesn't *look* like a QEM
On Tue, Nov 8, 2016 at 3:20 AM, Ian Campbell wrote:
> On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
>> The only odd thing I see in the syslog at startup are lines indicating
>> eth0 is not found.
>
> Wild stab in the dark: Perhaps things have remembered the mac address
> of the original
Re,
On Tue, Nov 08, 2016 at 02:27:30PM -0500, Lennart Sorensen wrote:
[...]
> > Could you try with another macadress ?
> >
> > Here (on amd64, though), sometimes qemu doesn't like some macadress,
> > dunno why...
> >
> > The tool 'macchanger' can create a valid one.
>
> I tried with that mac
On Tue, Nov 08, 2016 at 06:29:38PM +0100, JF Straeten wrote:
> Hi,
>
> On Tue, Nov 08, 2016 at 09:51:37AM -0500, Lennart Sorensen wrote:
>
> [...]
> > > If I don't specify any nic, QEMU supplies a default which is
> > > accepted by Debian. However, when I specify a virtio-net-device
> > > (so I c
Hi arm porters,
I guess I need some help in the build failure of r-bioc-shortread[1].
Any idea why it fails with
...
** inst
** preparing package for lazy loading
Warning: multiple methods tables found for 'arbind'
Warning: multiple methods tables found for 'acbind'
Warning: replacing previous i
Ah. I'd get a Dell laptop a few years old, put in a fresh hard drive,
and run OpenBSD instead of Linux. Much simpler and more reliable.
I've been using it since about 2002, including on the only firewall
machines I've built. I prefer the default FVWM to KDE for speed
reasons but I've had no prob
Hi,
On Tue, Nov 08, 2016 at 09:51:37AM -0500, Lennart Sorensen wrote:
[...]
> > If I don't specify any nic, QEMU supplies a default which is
> > accepted by Debian. However, when I specify a virtio-net-device
> > (so I can bridge to the host nic), I get no nic.
[...]
> > -netdev
> > -bridge,br=
> Has anybody done this, are there comparable instructions for an RPi3,
> and- above all- is there a straightforward kernel release suitable for
> host and guest?
I posted a similar question on the Raspberry Pi forums here:
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=154497&p=1010500#p
On Tue, Nov 08, 2016 at 03:01:09PM +, Mark Morgan Lloyd wrote:
> I prefer to run pukka Debian rather than Raspbian, approximately as
> described at http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/
>
> http://blog.flexvdi.com/2015/03/17/enabling-kvm-virtualization-on-the-raspberry-pi
I prefer to run pukka Debian rather than Raspbian, approximately as
described at http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/
http://blog.flexvdi.com/2015/03/17/enabling-kvm-virtualization-on-the-raspberry-pi-2/
and related pages describes getting Qemu+KVM running on an RPi2.
H
On 08/11/16 14:30, Ian Campbell wrote:
On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote:
Any other ideas?
I'm at a bit of a loss, maybe someone else has some bright ideas.
A few bits of info whic might jolt someones memory:
I can't usefully help, since while I use Qemu for various tar
On Mon, Nov 07, 2016 at 10:57:29PM -0500, Jerry Stuckle wrote:
> Hi, all,
>
> I'm trying to get Debian armhf (jessie) running under qemu-system-arm.
> It's working OK except for one point.
>
> If I don't specify any nic, QEMU supplies a default which is accepted by
> Debian. However, when I spec
On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote:
> Any other ideas?
I'm at a bit of a loss, maybe someone else has some bright ideas.
A few bits of info whic might jolt someones memory:
What is your full qemu command line for the working case (with the
default nic) and non-working cases?
Hi.
This is just a quick feedback from an armel tester.
I'm using a KuroBox Pro that Martin gave me a few years ago with Debian
testing and everything works perfectly with kernel
linux-image-4.7.0-1-marvell.
I had some 100% reproducible issues with kernels around 4.4 that I never
managed to repo
On 11/8/2016 3:20 AM, Ian Campbell wrote:
> On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
>> The only odd thing I see in the syslog at startup are lines indicating
>> eth0 is not found.
>
> Wild stab in the dark: Perhaps things have remembered the mac address
> of the original (automatic
On 08/11/16 09:30, Ian Campbell wrote:
On Tue, 2016-11-08 at 08:42 +, Mark Morgan Lloyd wrote:
Does "ifconfig -a" (as root) show the virtio device with some name
other than eth0? If so then you might need to edit
/etc/udev/rules.d/70-persistent-net.rules to cause it to forget the
old
device.
On Tue, 2016-11-08 at 08:42 +, Mark Morgan Lloyd wrote:
> > Does "ifconfig -a" (as root) show the virtio device with some name
> > other than eth0? If so then you might need to edit
> > /etc/udev/rules.d/70-persistent-net.rules to cause it to forget the
> > old
> > device.
>
> Is that file sti
On 08/11/16 08:30, Ian Campbell wrote:
On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
The only odd thing I see in the syslog at startup are lines indicating
eth0 is not found.
Wild stab in the dark: Perhaps things have remembered the mac address
of the original (automatically added) d
On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
> The only odd thing I see in the syslog at startup are lines indicating
> eth0 is not found.
Wild stab in the dark: Perhaps things have remembered the mac address
of the original (automatically added) device as eth0 and so the virtio
device
24 matches
Mail list logo
