A very drastic workaround that got you by your problem. I'm not sure it is
solved until someone understands WHAT happened and WHY so you can be
confident it won't happen again or know a less drastic resolution.
On Sat, Jul 14, 2012 at 9:50 PM, kitepi...@kitepilot.com
kitepi...@kitepilot.com
For what I have seen, I believe it to be a combination of problems from the
chipset/kernel/drivers interaction. Xubuntu and Mint came from the same
Ubuntu base and that's why they shared the problem.
Of course this is only my speculation and what you say is very well valid,
and the issue
Well, the Gnomes are at work (again) in my box and I could certainly use
some help to evict them...
This is what's happening:
I use:
'ssh -fCXY user@remotebox run-something'
a lot.
Works every time.
Or 'mostly' every time...
Now when I run (ONLY from *MY* box):
ssh -fCXY turboviking
Hi-
On Sat, Jul 14, 2012 at 8:20 AM, kitepi...@kitepilot.com
kitepi...@kitepilot.com wrote:
Well, the Gnomes are at work (again) in my box and I could certainly use
some help to evict them...
This is what's happening:
I use:
'ssh -fCXY user@remotebox run-something'
a lot.
Works every
Latest version...:(
No joy...
Now, Virtual box works OK from its box or any other of my boxes that I SSH
from. That being the case, I have to assume that the problem is with my
box's kernel/X/SSH combination.
Virtualbox is still running in the remote box, only the output is displayed
apt-get update
This is possibly a known malloc issue with glibc for your chipset.
Research requires full backtrace, versions, firmware and chipset versions.
# dmidecode
A post to the mint support might net more info although I would do
exhaustive reasearch on the error x-referenced with your
Sounds hardware-ish as Lisa mentioned - I'd do a memtest on there,
sounds like whenever something trys to grab a gob of ram, it hits a dead
chip, poops itself, and exits with a malloc error. I've used just about
every release of vbox for years now and never seen that.
Either that or you have
Well, I was able to determine that the 'malloc' error is happening in *MY*
box (I thought it was happening on the *other* box), so I booted my box with
a 'Rescatux' CD, installed SSH, did:
ssh -fCXY user@remote virtualbox
and it worked...
What that means to me is that both, the last Xubuntu
Well, I wiped out Mint and installed Debian squeeze.
All good now... :)
ET
kitepi...@kitepilot.com writes:
Well, the Gnomes are at work (again) in my box and I could certainly use
some help to evict them...
This is what's happening:
I use:
'ssh -fCXY user@remotebox run-something'
a
I have traditionally had better luck with Nvidia graphics with Linux.
however since the ATI/AMD merger they have REALLY stepped up their
Linux driver support. so much so that a HUGE contract went from Nvidia
to AMD fro graphics for the better Linux support. So before flipping
graphics hardware i
10 matches
Mail list logo
