keyboard
by Patrick Dupre
Hello,
I am using a french alternative keyboard, but the right CRTL key is not
working. I would like that it does the same thing than the left CRTL.
in the layout this key apears as Level5 S
How can I configure this keyboard?
Thank.
--
======================================================================
Patrick DUPRÉ || email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale ||
Tel. (33)-(0)3 28 23 76 12 || Fax: 03 28 65 82 44
189A, avenue Maurice Schumann || 59140 Dunkerque, France
======================================================================
11 years
RE:Disability relief
by Alan Gagne
> I do always set that, yes, as soon as I find it, and it does
> help; but I have yet to find it in Gnome 3 or xfce4. Anybody know where
> it lurks?
I have not read this entire thread so maybe I am too late to the game.
If you are still looking at how to turn on the bulls-eye around the
mouse pointer
in gnome 3 it comes with gnome tweak tool.
Alan
11 years
What is Fedora 18 acpi_osi default? Or, seeking consistent power management.
by Noah Cutler
Have been working out some kinks with recently acquired Dell M4700
Precision workstation.
Out of the box everything just works (impressive compared to Fedora 14),
except for Nvidia K1000M chip which insists on max power mode (heat) in
multi-head setup (Linus gave them the finger; I'd prefer that they shut
up...my laptop fans).
So I took a risk and flashed the vBios, underclocking the chip
significantly. Fantastic success, machine is absolutely quiet now, can run
all day under light load and fans never go on, awesome stuff...with one
caveat: for some reason after a suspend/resume power management goes awry
and the Nvidia chip heats up, triggering dreaded fan-on-off cycle over &
over & over (not as bad as before the vBIOS mod, but highly annoying
regardless).
The only way to get out of the heat loop is to restart X or restart the
machine, and then light load quiet until next suspend/resume.
Looking through /var/log I see that my kernel boot flag pcie_aspm=force is
picked up, but later is rejected:
PCIe ASPM is forcibly enabled
> [0.609409] pci_root PNP0A08:00: ACPI _OSC support notification failed,
> disabling PCIe ASPM
> [1.613536] pci 0000:00:01.0: ASPM: Could not configure common clock (this
> is the Nvidia chip, BTW)
> [1.619912] ACPI _OSC control for PCIe not granted, disabling ASPM
>
Thought maybe there's a buggy DSDT at play, so decompiled existing dsdt and
fixed the lone error and handful of warnings. Reran grub with modified
dsdt.aml and restarted. Same deal, ASPM seems to be somewhat broken no
matter what I do.
So, how does Fedora identify itself to underlying firmware? Assume acpi_osi
is Linux. I added that and "Windows 2012" as test kernel params, but
neither appeared to do anything particularly useful.
Can't underclock the Nvidia chip much more, so am hoping to find a way to
get reliable power management post-resume from suspend as something is
going off the rails at this time and not on system start/login.
Thanks for ideas.
11 years
RE:getting back from a black screen
by Alan Gagne
> On 04/08/2013 12:31 PM, Reindl Harald wrote:
> >/
> />/ [harry at srv-rhsoft <https://admin.fedoraproject.org/mailman/listinfo/users>:~]$ lspci | grep -i graphic
> /
> AHA! Two ways to do it. How Unix!
And let's add a twist to find out your drivers.
[dw-agagne ~]# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
then using the bus:slot.func returned from previous command.
dw-agagne ~]# lspci -s 01:00.0 -k
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 204a
Kernel driver in use: nouveau
Alan
11 years
presto
by Henk Breimer
starting fc18 presto-plugin has disappeared
I would like to get yum out of this mode.
Can't find a conf switch or trick to do that in man or google.
Is this another choice removed from "Linux,the world of choice"?
Or can I get a hint from here?
Thanks,
Henk
11 years
Online backup providers
by Joseph L. Casale
Anyone have any experience with jungledisk?
They offer a Linux client and have pretty cheap rates for large volumes of data. We are
retiring a private colocated backup and hoping to migrate to a commercial online solution.
Of the few that support Linux, this one looks pretty decent at first glance.
Thanks,
jlc
11 years
Unable to install F18 into an existing linux partitions.
by Dan Thurman
I was not able to install F18 via LiveCD/Anaconda
as it appears to insist on (unformatted) free space.
I was able to install F17 with anaconda, which
allowed me to specify the /boot and / software
destination having two partitions wiped out by
newly reformatting them while installing.
In F18, one has a choice to choose LVM, BRFS(?), or
Partition schemes, so I choose the Partition
scheme, checked that I wanted no help, to
manually modify and/or define the software
destination and hovering the cursor over 2nd
button, the highlight says: "Please wait... software
metadata is being loaded" and nothing happens for
over 30 minutes of waiting.
I do not want to use the 'reclaim' button because
this might mess up the partition table and screw
the entire disk.
I also noted that while waiting, I was able to set
the locale, but not allowed to change the date,
time nor 12/24 hour selections, they are greyed out,
even though I was able to do this on the time/date
menubar but this has nothing to do with anaconda.
So, what can I do at this point?
11 years
/var/log/messages ful of rpc.statd select: Bad file descriptor lines
by Steve Searle
On three or four occasions now on one of my Fedora 18 machines warns
that I am running out of space on /var (it has its own partition). This
is due to /var/log/messages being full of rpc.statd[1282]: my_svc_run()
- select: Bad file descriptor messages - these are repeated many times a
second.
Deleting /var/log/messages gets round this as a work around, but can
anyone suggest what I can do to investigate/fix this?
Thanks
Steve
--
Website: www.stevesearle.com
17:41:12 up 22 days, 15:59, 1 user, load average: 0.00, 0.00, 0.00
11 years
Sad computer with gnome: what to do ?
by Theodore Papadopoulo
Since several weeks, I get regularly thei Sad Computer icon which
tells me in disconnect and re-connect. But that does not work (and
that is true with every variants of gnome installed on my computer).
In the same situation KDE seems to work well even though that's not my
favorite setup.
All this seems to be related to switching between a configuration
where the laptop is docked and has two screens and a stadalone
configuration where the internal panel is the only screen. When I
first had the problem, I was unable to login, rebooted and then had
the trouble. With time, I learning that I could take a console, kill
the screensaver and then call the gnome-control-center to switch the
display, but this does not solve the problem completely as it still
happens sometimes after a while.
I have tried to remove my .gnome[-2] stuff and various other config
stuff such as monitors.xml. I have looked at the various log
(messages, Xorg, ... without any clue at the issue).
So I'm asking advice in how to analyse and cure definitely this problem.
Any idea ?
Thank's
Theo.
PS: Another stange behavior on my computer is that I often get a no
more processes situation in cases I have a relatively low number of
processes (~320). I strongly suspect chrome, but it is difficult to be
sure as the system information given by ps seems reasonnable.
I do not think this is related (except maybe on the fact that it may
create the situation in the beginning, but since the sad computer
remain after reboots, what is corrupted remains even after the process
problem is solved,
PS2: hum and I also must say that I use the nvidia drivers. I know
this is not the best setup to ask for help here, but this is mandated
by my company, and I believe that the problem is more to be found
somewhere in the gnome configuration files than in some drivers settings.
PS3: Generally speaking, gnome works great (even though some interface
choices might or might not please people), but when it fails it is
sometimes very difficult to understand where the problem is....
This is true for some small problems (failure in applets at start
which seems realted to timings problems and are easily solved by
re-logging), but in the case of this sad computer, I believe that more
information should be provided on what fails (or at least where to
look for that information).
11 years
