Hello.
I have a Silicon Motion SM720 Lynx3DM card which X in Ubuntu 8.10 (and
Fedora 9) will not start on. The log seems fine but ends with:
AddScreen/ScreenInit failed for driver 0
The issue it experience seems to have been introduced by changes to X
to use libpciaccess.
Using GDB, and
Le Lun 1 décembre 2008 08:19, David Miller a écrit :
But what I spend most of my time doing is figuring out what new
default breaks Xorg on my system. This was one of them.
The other one was the internal fonts stuff with the X server, which
caused me to lose my Emacs international fonts.
Twas brillig at 11:38:21 01.12.2008 UTC+05 when [EMAIL PROTECTED] did gyre and
gimble:
AEP Then it may be a good idea to write such client (even without the pop-up,
AEP a static default stored in the configuration file will also work) and add
AEP it to xorg-apps as an example implementation
On Mon, Dec 01, 2008 at 09:49:29AM +0100, Nicolas Mailhot wrote:
IIRC even SUN was told in no incertain terms
it could forget its own next-gen font system because everyone that
mattered had adopted fontconfig
I may be completely wrong on this one, but ISTR one of the problems with
STSF (aside
Twas brillig at 20:22:30 01.12.2008 UTC+11 when [EMAIL PROTECTED] did gyre and
gimble:
DS [0]: Emacs in 'utter luddites' shock.
Not anymore.
--
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Sergey == Sergey Udaltsov [EMAIL PROTECTED] writes:
If keyboards which use I32 with the kbd driver generate I158 in
evdev I'd make I32 be WWW and if they generate I180 when using evdev
then HomePage.
Sergey Ghm. How could I find this out without having that particular keyboard
Sergey in
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 09:49:29 +0100 (CET)
Ironically fontconfig was adopted in large part because the core fonts
system had major problems with internationalization.
Ironically you didn't read my posting.
I'm not against any of this stuff, I'm against
Chris == Chris Ball [EMAIL PROTECTED] writes:
Chris The following program (requires XInput2) warps my pointer to (0,0)
Chris instead of the requested (600,400). I'd be interested to know whether
Chris this happens for other people,
It warped my pointer to 600,400.
My server and client libs
On Sun, 2008-11-30 at 14:11 +, Beso wrote:
just look at the
evdev driver. i think that after its development
the usability of keyboards and mouses has increased quite a lot. now i
cannot see a reason to switch back to kbd +
mouse instead of evdev.
I see one: keyboard layout isn't
Le Lun 1 décembre 2008 10:39, David Miller a écrit :
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 09:49:29 +0100 (CET)
Ironically fontconfig was adopted in large part because the core
fonts
system had major problems with internationalization.
Ironically you didn't read
I suspect WWW is more likely than HomePage.
Yes, I suspect the same thing. That's why I asked.
But I see that some of the keyboards have both, often with I32 as
HomePage and something else as WWW.
Yes, for those cases we have to distinguish...
Maybe the bsd src for converting from usb to
On Mon, Dec 01, 2008 at 01:39:32AM -0800, David Miller wrote:
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 09:49:29 +0100 (CET)
Ironically fontconfig was adopted in large part because the core fonts
system had major problems with internationalization.
Ironically you
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 10:58:17 +0100 (CET)
If there is somethign obvious here, is that emacs maintainers didn't
made due diligence by any reasonable definition. Even the kernel made
major changes (devfs, sysfs, etc) in the time it took for emacs folks
From: Daniel Stone [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 21:05:46 +1100
On Mon, Dec 01, 2008 at 01:39:32AM -0800, David Miller wrote:
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 09:49:29 +0100 (CET)
Ironically fontconfig was adopted in large part because the core
Le Lun 1 décembre 2008 11:19, David Miller a écrit :
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 10:58:17 +0100 (CET)
If there is somethign obvious here, is that emacs maintainers didn't
made due diligence by any reasonable definition. Even the kernel
made
major changes
Richard Schwarting [EMAIL PROTECTED] writes:
Hello.
I have a Silicon Motion SM720 Lynx3DM card which X in Ubuntu 8.10 (and
Fedora 9) will not start on. The log seems fine but ends with:
AddScreen/ScreenInit failed for driver 0
The issue it experience seems to have been introduced by
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 11:26:51 +0100 (CET)
Le Lun 1 décembre 2008 11:19, David Miller a écrit :
From: Nicolas Mailhot [EMAIL PROTECTED]
Date: Mon, 1 Dec 2008 10:58:17 +0100 (CET)
If there is somethign obvious here, is that emacs maintainers
Xavier Bestel wrote:
On Sun, 2008-11-30 at 14:11 +, Beso wrote:
just look at the
evdev driver. i think that after its development
the usability of keyboards and mouses has increased quite a lot. now i
cannot see a reason to switch back to kbd +
mouse instead of evdev.
I see one:
Le Lun 1 décembre 2008 12:22, Colin Guthrie a écrit :
I think the real question here is who is responsible for this.
IMHO the core problem is that the Linux kernel console has been left
to rot quietly. The main reason evdev/hal does not export a system
layout information xorg could use
Hi Peter,
this is regression caused by correction for 14373 (fixed with commit
ae986d1c73d).
I rebuild server removing the coding that copy more than 2 shift level
and more than 2 groups like this:
/* AB..CDE... - ABABCDE... */
if (groupWidth 0 maxSymsPerKey =
Here I published the keycodes used for WWW and HomePage (and
VendorHome, just in case):
http://spreadsheets.google.com/ccc?key=pCdLapzoHyYYFYQ5pKV3-QA
Another suspect keycode: I02. May be, we just should state that I32
would be for HomePage, I02 would be for WWW?...
Of course, this is only for
David == David Miller [EMAIL PROTECTED] writes:
David Yet my emacs fonts are fux0red, my input device specifications in
David my xorg.conf file are completely ignored, and MetaSendsEscape no
David longer works with my xterms, with the current X server.
Using --disable-config-dbus
On Mon, Dec 01, 2008 at 01:40:57PM +0100, Nicolas Mailhot wrote:
As usual, people who care about something are free to maintain it in
good shape, since this is how free software works.
What is there to maintain, exactly?
OG.
___
xorg mailing list
On Mon, Dec 01, 2008 at 01:15:05PM +0100, Nicolas Mailhot wrote:
BTW now that almost all the X userspace has been converted to use
fontconfig and modern TrueType/OpenType fonts, I expect the level of
attention fonts in legacy bitmap format receive to drop sharply, which
will ultimately lead to
Le Lun 1 décembre 2008 13:33, Olivier Galibert a écrit :
On Mon, Dec 01, 2008 at 01:15:05PM +0100, Nicolas Mailhot wrote:
BTW now that almost all the X userspace has been converted to use
fontconfig and modern TrueType/OpenType fonts, I expect the level of
attention fonts in legacy bitmap
Le Lun 1 décembre 2008 13:44, Olivier Galibert a écrit :
On Mon, Dec 01, 2008 at 01:40:57PM +0100, Nicolas Mailhot wrote:
As usual, people who care about something are free to maintain it in
good shape, since this is how free software works.
What is there to maintain, exactly?
Fonts are
What is there to maintain, exactly?
Fonts are not generated out of thin hair and they need to be updated
to keep up with the environment.
Only if you keep breaking the environment carelessly.
Environment changes can be changes in encoding standards (unicode is
still evolving and even
Le Lun 1 décembre 2008 13:59, Alan Cox a écrit :
The result is that since there is no single shared layout X and the
kernel use, no layout info is exposed by the kernel infrastructure.
(and from a functional point of view there is no reason a key should
have a different behaviour in X and
On Mon, 1 Dec 2008, James Cloos wrote:
David == David Miller [EMAIL PROTECTED] writes:
David Yet my emacs fonts are fux0red, my input device specifications in
David my xorg.conf file are completely ignored, and MetaSendsEscape no
David longer works with my xterms, with the current X server.
Le Lun 1 décembre 2008 14:10, Alan Cox a écrit :
All non issues.
In case you've not noticed every time you use a vectorised font you
turn
it into a bitmap to suit a changing variety of hardware and encodings.
In case you've not noticed the so-called kernel console userspace is
totally
In case you've not noticed the so-called kernel console userspace is
totally unable right now to turn standard vectorised fonts into
bitmaps suiting a changing variety of hardware and encodings, and
relies on manually pre-processed bitmap fonts precious few people
maintain and adapt to
Just check the console on any random selection of non-us or uk systems
and you'll see the current garbage is the console output. Sure it is
not a blocker because all the different encodings agree on the ASCII
part, but anything outside the 127 first codepoints has a high
probability of being
On Mon, Dec 01, 2008 at 02:05:24PM +0100, Nicolas Mailhot wrote:
Le Lun 1 décembre 2008 13:44, Olivier Galibert a écrit :
On Mon, Dec 01, 2008 at 01:40:57PM +0100, Nicolas Mailhot wrote:
As usual, people who care about something are free to maintain it in
good shape, since this is how
Le Lun 1 décembre 2008 14:31, Alan Cox a écrit :
Just check the console on any random selection of non-us or uk
systems
and you'll see the current garbage is the console output. Sure it is
not a blocker because all the different encodings agree on the ASCII
part, but anything outside the
On Sun, Nov 30, 2008 at 10:38 PM, Alexander E. Patrakov
[EMAIL PROTECTED] wrote:
It is traditionally the default only in Xorg. If you get a Russian
version of Windows 2000 or XP, Russian will be the default, with the
possibility to switch to English with Alt+Shift. Also, even in the US
Daniel Stone wrote:
On Mon, Dec 01, 2008 at 10:47:06AM +0500, Alexander E. Patrakov wrote:
Also, currently, for unconfigured Xorg, such newly-added keyboard gets
the us layout. This is also a hard-coded policy, should we remove it?
Ignoring both the rhetoric and the fact that neither of
On Mon, 2008-12-01 at 12:59 +, Alan Cox wrote:
The result is that since there is no single shared layout X and the
kernel use, no layout info is exposed by the kernel infrastructure.
(and from a functional point of view there is no reason a key should
have a different behaviour in X
On Mon, Dec 1, 2008 at 12:15 AM, Peter Hutterer
[EMAIL PROTECTED] wrote:
...
┌───
RRScreenChangeNotify
type: BYTE; always GenericEvent
extension: CARD8; extension offset
sequenceNumber: CARD16 low 16 bits of request seq.
On Mon, Dec 01, 2008 at 06:36:32AM -0800, Dan Nicholson wrote:
I was reading the xkb-atkins log a couple weeks ago. It looks like a
nice diet. :)
FWIW, this is progressing nicely, except I've currently regressed the
case where people can't compile XKB keymaps. Normally I wouldn't
really care
Hi,
On Mon, Dec 01, 2008 at 01:33:02PM +, Colin Guthrie wrote:
James Cloos wrote:
Using --disable-config-dbus --disable-config-hal when configuring will
drop the input mess and use the spec from xorg.conf.
Having just experienced this exact issue, I don't think this is correct.
The
On Mon, Dec 01, 2008 at 01:15:05PM +0100, Nicolas Mailhot wrote:
1. they do not use the layout database where maintenance happens
(xkb-config)
2. therefore the optimal layout is often missing console-side, and
good-enough for debugging qwerty is used
3. even when there is a good layout, there
I mean this is broken every Fedora release or so just by applying
system updates without any user-level intervention. I don't think that
So file a Fedora bug.
The font data is out there already thank you. As you keep conveniently
forgetting X can already render those fonts to bitmaps
I just observe few people are working on them anymore, because most
applications use something else.
I see few people working on them because they are not broken and don't
need work. Same with the consoles. We get almost no console patches
because the kernel consoles do what people need
On Mon, Dec 01, 2008 at 08:47:02PM +0500, Alexander E. Patrakov wrote:
2008/12/1 Corbin Simpson [EMAIL PROTECTED]:
Now, the big difference between HAL and udev is that udev sets its defaults
based on LSB. I don't know whether or not LSB has anything to say about
keyboard layouts, or what
Le Lun 1 décembre 2008 16:47, Alexander E. Patrakov a écrit :
Apriori, there is no sensible default keyboard layout.
There could be if the hardware started advertising what actually
painted on its keys (and even then many people would want to override
it). Since it does not, you're right.
--
On Mon, Dec 01, 2008 at 03:50:25PM +, Alan Cox wrote:
If you're saying X is now needed to render the console I think people
will object.
Of course not - the majority of Linux systems don't even run X.
I can think of two possible responses:
a) good, so it's off-topic for xorg@;
b)
Twas brillig at 16:58:42 01.12.2008 UTC+01 when [EMAIL PROTECTED] did gyre and
gimble:
Apriori, there is no sensible default keyboard layout.
NM There could be if the hardware started advertising what actually
NM painted on its keys
/me wonders what Happy Hacking Blank Top keyboards would
Apriori, there is no sensible default keyboard layout.
Yes, there is, and it's called US. This isn't being Anglo-centric or
Which US layout - there are several and then you get all the variants
with extra funny buttons for internet etc ?
anything, and I'm not going to argue the point.
On Mon, 2008-12-01 at 16:58 +0100, Nicolas Mailhot wrote:
Le Lun 1 décembre 2008 16:47, Alexander E. Patrakov a écrit :
Apriori, there is no sensible default keyboard layout.
There could be if the hardware started advertising what actually
painted on its keys (and even then many people
b) given that we're talking about font rendering, how we talk about
Linux systems that actually render fonts?
The subset that do: Framebuffer drivers, nanogui, and X (particularly non
embedded devices).
Kernel side font handling is bitmaps or font tables with the work done by
the video
On Mon, Dec 01, 2008 at 04:11:46PM +, Alan Cox wrote:
Apriori, there is no sensible default keyboard layout.
Yes, there is, and it's called US. This isn't being Anglo-centric or
Which US layout - there are several and then you get all the variants
with extra funny buttons for
Hi James,
It warped my pointer to 600,400.
My server and client libs are all from git (master branches), x86
(32bit).
Thanks, that's very helpful to hear. I'm also running from GIT master
(via jhbuild), but on 64-bit x86 and Fedora 10.
Cheers,
- Chris.
--
Chris Ball [EMAIL
On Tue, 2008-11-25 at 10:18 +0800, Leandro Galvez wrote:
Hi Adam,
Does damage extension have the api to notify if the framebuffer
has already been updated with the data? Need something to notify me if
buffer has already been updated and ready for display so I can send
the data to the
On Tue, 2008-11-25 at 12:55 +0100, Matthieu Herrb wrote:
Thanks for the answer. That seems to work indeed.
Applied to master. Thanks for testing!
- ajax
signature.asc
Description: This is a digitally signed message part
___
xorg mailing list
Chueh Steel wrote:
Hi, all,
1. Is it possible to compiler one X input module so that it could be
binary compatible across xorg 1.3, 1.4 or 1.5?
I believe Nvidia does this, but I don't know if they've published how.
Due to the API/ABI changes, you would have to have header files available
You probably remember the system, it's my fujitsu P7120 lifebook with
the funny backlight wiring.
Previously, suspend/resume was made to work by saving the PCI state
including the legacy backlight register setting (and worked just fine
when invoked with a hal quirk).
On FC9, with the 2.6.26
On Sunday 30 November 2008 19:50:28 Tino Keitel wrote:
On Sat, Nov 29, 2008 at 14:53:54 +, Tobias Kaminsky wrote:
I don't know any details about Xephyr, but the current stable release
of the Xserver doesn't allow multihead accross multiple graphic
adapters. This is a planned feature
Daniel Stone wrote:
__ ___ _ _ _ _ _ _ ___
\ \ / / / ___| | __ )| | | |_ _| |_ _| | | |_ _/ ___|
\ V /| _| \___ \ | _ \| | | | | | | | | |_| || |\___ \
| | | |___ ___) | | |_) | |_| | | | | | | _ || | ___) |
|_|
Daniel Stone wrote:
Hi,
On Mon, Dec 01, 2008 at 01:33:02PM +, Colin Guthrie wrote:
James Cloos wrote:
Using --disable-config-dbus --disable-config-hal when configuring will
drop the input mess and use the spec from xorg.conf.
Having just experienced this exact issue, I don't think this
Sergey Udaltsov wrote:
Of course, this is only for kbd driver (which is nearly deprecated
these days, isn't it?;)
Except on non-Linux systems, where kbd is still used since evdev can't be.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window
On Wed, 2008-11-26 at 23:27 -0200, Paulo César Pereira de Andrade wrote:
Remove the x11-driver-video-sun... packages listed above. They
were being build and installed by default, but they won't work
on a normal ix86 computer.
Making one wonder why you build them for architectures that do not,
On Mon, 2008-12-01 at 00:39 -0800, Richard Schwarting wrote:
So, I'm going to try and find out what the correct behaviour should be
to fix it, but any hints would be gratefully appreciated.
Other drivers handle this by unmapping memory at the end of PreInit.
- ajax
signature.asc
This is the first beta for libXrandr 1.3. It adds projective transforms
and GetScreenResourcesCurrent, panning support is not there yet.
Cheers,
Julien
Adam Jackson (2):
Remove RCS tags.
Add GetScreenResourcesCurrent
Julien Cristau (3):
Set attr-pendingNparams in
On Mon, Dec 01, 2008 at 08:57:16AM -0600, Pat Kane wrote:
On Mon, Dec 1, 2008 at 12:15 AM, Peter Hutterer
[EMAIL PROTECTED] wrote:
...
┌───
RRScreenChangeNotify
type: BYTE; always GenericEvent
extension: CARD8; extension offset
On Tue, Dec 02, 2008 at 02:31:48AM +1100, Daniel Stone wrote:
On Mon, Dec 01, 2008 at 06:36:32AM -0800, Dan Nicholson wrote:
I was reading the xkb-atkins log a couple weeks ago. It looks like a
nice diet. :)
FWIW, this is progressing nicely, except I've currently regressed the
case where
Adam Jackson wrote:
On Wed, 2008-11-26 at 23:27 -0200, Paulo César Pereira de Andrade wrote:
Remove the x11-driver-video-sun... packages listed above. They
were being build and installed by default, but they won't work
on a normal ix86 computer.
Making one wonder why you build them for
Peter Hutterer wrote:
Pretty much the same behaviour when you remove mouse/kbd, btw.
Yeah I guess I can't argue with that logic ;)
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux
Julien Cristau wrote:
This is the first beta for libXrandr 1.3. It adds projective transforms
and GetScreenResourcesCurrent, panning support is not there yet.
I presume this needs an updated xrandrproto?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Hi all. I'm upgrading from Fedora 6 to Fedora 10. I did a clean
install of Fedora 10 and then, as the default X config didn't work, I copied
across my old xorg.conf file. Naturally I had to comment out a few lines in
that file.
Now a word on my setup. I have two screens, one hanging off an
Vesa driver seems to ignore dpms settings and even 'xset dpms force off'
won't power off display.
Thinkpad T42 with an ATI Radeon M 7500
Slackware 12.0
xorg 7.1
--
Psychiatrists say that one out of four people are mentally ill. Check
three friends. If they're OK, you're it.
On Mon, 2008-12-01 at 01:39 -0800, David Miller wrote:
I'm not against any of this stuff, I'm against it being
done by default which breaks things on existing systems
that try to build GIT xorg and help you guys test things.
In the particular case of --disable-builtin-fonts, I think 'only
On Tue, Dec 02, 2008 at 04:18:36AM -0200, Paulo César Pereira de Andrade wrote:
One possible solution, that I proposed some time ago (but got no
response) would be to add something like an UDI option to input
devices. So, one could have something like this in his xorg.conf:
Section
Timothy S. Nelson wrote:
Hi all. I'm upgrading from Fedora 6 to Fedora 10. I did a clean
install of Fedora 10 and then, as the default X config didn't work, I
copied across my old xorg.conf file. Naturally I had to comment out a
few lines in that file.
Now a word on my setup. I have
Thomas, here's the set of patches that appears to fix the problem. It's a
combination of some bugs and insanity in the XKB protocol.
Basically, we're required to convert from XKB to core (including the weird
replication in ae986d1c73d), but when converting back we're missing vital
information
From: Peter Hutterer [EMAIL PROTECTED]
---
xkb/xkbUtils.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/xkb/xkbUtils.c b/xkb/xkbUtils.c
index 313d418..014ddef 100644
--- a/xkb/xkbUtils.c
+++ b/xkb/xkbUtils.c
@@ -524,7 +524,7 @@ int
From: Peter Hutterer [EMAIL PROTECTED]
---
xkb/xkbUtils.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/xkb/xkbUtils.c b/xkb/xkbUtils.c
index 313d418..014ddef 100644
--- a/xkb/xkbUtils.c
+++ b/xkb/xkbUtils.c
@@ -524,7 +524,7 @@ int
From: Peter Hutterer [EMAIL PROTECTED]
Single-group keys may get replicated amongst all groups. Check explicitly for
this case and squash it down to one group.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
xkb/XKBMisc.c | 82 +++-
1
From: Peter Hutterer [EMAIL PROTECTED]
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
xkb/XKBMisc.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/xkb/XKBMisc.c b/xkb/XKBMisc.c
index c0b1878..dcde470 100644
--- a/xkb/XKBMisc.c
+++ b/xkb/XKBMisc.c
@@ -242,6 +242,8
From: Peter Hutterer [EMAIL PROTECTED]
Single-group keys may get replicated amongst all groups. Check explicitly for
this case and squash it down to one group.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
xkb/XKBMisc.c | 82 +++-
1
79 matches
Mail list logo