2 pane, swiss army knife file manager?
blchupin at iinet.net.au
Tue Nov 27 11:17:22 UTC 2012
On 21/11/12 03:59, Gene Heskett wrote:
> On Tuesday 20 November 2012 11:42:11 Basil Chupin did opine:
>> On 20/11/12 17:41, Ric Moore wrote:
>>> On 11/20/2012 12:00 AM, Basil Chupin wrote:
>>>> On 20/11/12 11:49, Gene Heskett wrote:
>>>>> On Monday 19 November 2012 19:47:16 Basil Chupin did opine:
>>>>>> On 20/11/12 05:54, Gene Heskett wrote:
>>>>> Not a thing Basil. But if I click on a graphics file, it will show
>>>>> it to
>>>>> me, but its own screen will be destroyed in the process,
>>>>> unrecovereble ANAICT.
>>>>> Cheers, Gene
>>>> As I said, something wrong at your end :-) . I can view any graphic I
>>>> want without losing mc when I close the graphic.
>>> Gene is using the noveau <sp?> driver which has a ways to go. I think
>>> he wouldn't get that tearing if he managed to install the nvidia
>>> driver with hockey. But, his custom kernel seems to mung that up. Ric
>> That would explain it - the use of nouveau driver.
>> But if he compiled his own kernel correctly then he should be able to
>> compile the nVidia driver for it. I compile my own nVidia driver every
>> time, each time a new version is released (or even a beta, as in the
>> latest one 310.14).
> Possibly Basil, but the OEM nvidia drivers absolutely demolish the latency
> figures of the real time kernel, making it impossible and unsafe to run
> machinery with that driver. I have tried, and I have a container I toss
> broken $20 carbide tools into that has about a two hundred bucks worth of
> tools the nvidia driver broke by stalling a motor with its 200 millisecond
> long IRQ lockouts.
To begin, I hadn't responded earlier because I was looking for some
doco, which I still failed to find, and also doing some magical things
with Cinelerra and well as installing an upgrade on my wife's computer.
Re the above, you mention 3 things which I found interesting and for
which it would be nice to have some information.
The first is your mention of "the OEM nvidia drivers". Do you mean the
basic, nouveau driver which is used when you install the the distro you
Secondly, you mention "the real time kernel". Do you actually mean a
'real time kernel' or do you mean something else? I am not aware that
there may be a real time kernel as I understand that such a beast is
difficult to put together and hard to keep updated because of all the
patches. But I have to say that I know nothing about this subject.
Thirdly, your very specific reference that your motor is being stalled
by "200 millisecond long IRQ lockouts". I couldn't help smiling when I
read that and thought to myself, "Why not 201 or 202.3 milliseconds?"
:-) . How do you manage to measure this value?
> That is reason #1.
> Reason #2, is that I have yet to build a custom kernel that the nvidia
> driver would allow itself to be installed to. The failure message, 100% of
> the time is that it is already installed.
If you read the instructions given on the nVidia site you will find that
there is cli which you can use to uninstall an existing nvidia driver.
But when I compile mine I am 'told' that there a driver already
installed and do I want it removed - to which, of course, I answer with
The other thing I wanted to mention, and it was re this that I was
searching for some dox I have/?had, about rolling your own kernel.
Some years ago I used to roll my own kernel because the kernel came in 3
flavours: a pae one, a standard one, and some other. (This by the way
has nothing to do with Ubuntu as it wasn't a gleam in dadda's eyes at
that time :-) .) The point of me mentioning this is that as far as I can
remember both the pae and the standard kernels were meant to be used on
_servers_ and therefore had a high latency (don't ask where, I said I
know nuffin' I just followed instructions :-) ); they were not really
designed for use on fast desktops - which is the reason why I used to
roll my own and fiddled with some parameters which gave better results
on a desktop. I wish I could find the dox I was using which spelt out
the parameters which needed to be altered :-( , but one of then was to
increase something's latency from the default of 1000 Hz to ?????.
> So I startx, and either fail
> outright, or wind up with an /etc/X11/xorg.conf that has been destroyed
> because it got overwritten by a vesa config. So you spend 3 hours screwing
> around trying to recover a working X server, and in the end wind up doing a
> full re-install after saving as much of your work as you can to someplace
> it won't get nuked by the install.
> When the nvidia driver decides to play nice with the IRQ's,
While I have never had the need to fiddle with this, I am pretty sure
that the nvidia configuration gives you the ability to do all sorts of
tweaking with its performance. But I guess that this would also depend
on whether the nvidia card you are using is of the modern era or of the
Edwardian era :-) .
Here are a couple of screenshots to show what I mean:
> AND is capable
> up updating the install despite finding traces of an old install by
> deleting and overwriting the old files with whatever its trying to install
> this time, aka a --force option, then I might consider its use again BUT
> NOT on a machine that is actually running what can be dangerous, higher
> powered machinery.
> That of course is up to nvidia. If they want the whole market, they will
> fix that, if not, sorry not on my machines.
> Cheers, Gene
Using openSUSE 12.2 x86_64 KDE 4.9.3 & kernel 3.6.7-1 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU
More information about the ubuntu-users