OK - my new Acer Aspire One is up and running Fedora 10 and KDE.
My temptation has been to create an xorg.conf and adjusting the 1024x600 into a virtual 1024x768 but OK, for the time being, I'm playing and learning.
KDE 4's systemsettings has a really interesting 'Display' option that allows me independent controls for the 19" LCD on my KVM (set to 1280x1024) and the built-in screen and for the present, I am using the 'clone' option.
It is apparent that if I reboot, the 19" display actually comes up in some grotesque resolution like maybe 640x480 and if I run systemsettings and just click the 'Display' control icon, it immediately restores the 1280x1024 setting...no need to click apply or anything else.
That seems to be a bug but it also seems that KDE is really close to getting this tool right. In my mind, installing and running system-config-display on this system would pretty much defeat what KDE is trying to accomplish here.
Is there anything here worthy of a bug report?
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
Craig
On Fri, 2009-01-16 at 21:56 -0700, Craig White wrote:
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
---- kcmshell ksynaptics says...
Shared Memory is not accessible.
Please add the option 'SHMConfig "on"' into the touchpad section of /etc/X11/xorg.conf
and of course, there isn't any xorg.conf file - ignoring that, it says 'Using Driver' "none" - which of course is why my touchpad isn't happening.
do I have to insmod/modprobe something?
Craig
Craig White wrote:
kcmshell ksynaptics says...
Shared Memory is not accessible.
Please add the option 'SHMConfig "on"' into the touchpad section of /etc/X11/xorg.conf
and of course, there isn't any xorg.conf file - ignoring that, it says 'Using Driver' "none" - which of course is why my touchpad isn't happening.
do I have to insmod/modprobe something?
Create an /etc/hal/fdi/policy/11-synaptics.fdi with the following contents: <?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <merge key="input.x11_options.SHMConfig" type="string">true</merge> </match> </device> </deviceinfo>
Using xorg.conf for input configuration is obsolete and should no longer be done.
Be warned that SHMConfig is insecure (that's why it's disabled by default).
Kevin Kofler
On Sat, 2009-01-17 at 15:58 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 20:16:25 +0100 Kevin Kofler wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
That's why xml gibberish like the above is so well documented :-).
---- do you just look for opportunities to cheap shot?
Craig
On Sat, 17 Jan 2009 15:42:27 -0700 Craig White wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
That's why xml gibberish like the above is so well documented :-).
do you just look for opportunities to cheap shot?
For ones that are deserved, yes. You'd think that at a minimum there would at least be a line in input section of the xorg.conf man page saying the information there is obsolete and good luck finding what replaced it, but there isn't even that much of a hint anywhere in the most likely place to look for one.
Enough perfectly justified cheap shots and I might someday perform the miracle of getting a linux developer to think "Hmmm... If we improve this so much no one can understand how to use it, that isn't really an improvement is it?". (But I don't hold out any real hope of that happening).
On Sat, 2009-01-17 at 17:59 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 15:42:27 -0700 Craig White wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
That's why xml gibberish like the above is so well documented :-).
do you just look for opportunities to cheap shot?
For ones that are deserved, yes. You'd think that at a minimum there would at least be a line in input section of the xorg.conf man page saying the information there is obsolete and good luck finding what replaced it, but there isn't even that much of a hint anywhere in the most likely place to look for one.
Enough perfectly justified cheap shots and I might someday perform the miracle of getting a linux developer to think "Hmmm... If we improve this so much no one can understand how to use it, that isn't really an improvement is it?". (But I don't hold out any real hope of that happening).
---- I suppose you missed the fact that in this very thread, I am praising the logic behind not having an xorg.conf file which locks me into settings because kdesettings 'Display' can do so much more.
The thing that eludes me is that with all of your superior knowledge, why do you remain sitting on the sidelines and taking cheap shots instead of joining the development team where your opinions have a chance of becoming part of the solution?
I'm gathering that you have bugzilla'd your corrections for the xorg.conf man page so that your input doesn't only live and die on the list.
I hate to say this because I, over time, have come to realize that you do have some knowledge of these things and also to realize that your attitude sucks. Perhaps you should be using a distribution or software that is more aligned towards your views...perhaps slackware or lfs. One thing for sure, if I were a Fedora developer, I'd tune you out.
Craig
I have had to use xorg.conf, simply because Fedora10 drivers do not adequately support ATI video cards. With the livna ati drivers, I am still unable to run compiz. And also, the settings for dynamic xorg.conf were woefully inadequate, leaving out important sweep frequencies. Somehow though, the xorg.conf that is created with UBUNTU excels with the use of my monitor and with that distribution Compiz works for me. It is almost 3 months into the Fedora10 distribution and still, hardly any progress for the ATI driver set.
Do we ask ATI to develop the drivers, or do we pray for help to the user community?
(I can and do live without compiz, but it is nice to have to show to those XP/Vista biggots
--- On Sat, 1/17/09, Craig White craigwhite@azapple.com wrote: From: Craig White craigwhite@azapple.com Subject: Re: life without system-config-display To: "Community assistance, encouragement, and advice for using Fedora." fedora-list@redhat.com Date: Saturday, January 17, 2009, 6:15 PM
On Sat, 2009-01-17 at 17:59 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 15:42:27 -0700 Craig White wrote:
Using xorg.conf for input configuration is obsolete and
should no longer be
done.
That's why xml gibberish like the above is so well
documented :-).
do you just look for opportunities to cheap shot?
For ones that are deserved, yes. You'd think that at a minimum there would at least be a line in input section of the xorg.conf man page saying the information there is obsolete and good luck finding what replaced it, but there isn't even that much of a hint anywhere in the most likely place to look for one.
Enough perfectly justified cheap shots and I might someday perform the miracle of getting a linux developer to think "Hmmm... If we improve this so much no one can understand how to use it, that isn't really an improvement is it?". (But I don't hold out
any
real hope of that happening).
---- I suppose you missed the fact that in this very thread, I am praising the logic behind not having an xorg.conf file which locks me into settings because kdesettings 'Display' can do so much more.
The thing that eludes me is that with all of your superior knowledge, why do you remain sitting on the sidelines and taking cheap shots instead of joining the development team where your opinions have a chance of becoming part of the solution?
I'm gathering that you have bugzilla'd your corrections for the xorg.conf man page so that your input doesn't only live and die on the list.
I hate to say this because I, over time, have come to realize that you do have some knowledge of these things and also to realize that your attitude sucks. Perhaps you should be using a distribution or software that is more aligned towards your views...perhaps slackware or lfs. One thing for sure, if I were a Fedora developer, I'd tune you out.
Craig
On Sun, 2009-01-18 at 17:11 -0800, Leslie Satenstein wrote:
I have had to use xorg.conf, simply because Fedora10 drivers do not adequately support ATI video cards. With the livna ati drivers, I am still unable to run compiz. And also, the settings for dynamic xorg.conf were woefully inadequate, leaving out important sweep frequencies. Somehow though, the xorg.conf that is created with UBUNTU excels with the use of my monitor and with that distribution Compiz works for me. It is almost 3 months into the Fedora10 distribution and still, hardly any progress for the ATI driver set.
Do we ask ATI to develop the drivers, or do we pray for help to the user community?
(I can and do live without compiz, but it is nice to have to show to those XP/Vista biggots
---- boy that yahoo sends out some lousy e-mail...
You don't mention which version of Ubuntu but I gather that it uses the 'old' version of xorg which would account for the disparity between Fedora and Ubuntu - at least in my mind.
ATI proprietary drivers are not the province of open source developers and Fedora does not package or recommend their use. Perhaps you are getting them directly from ATI or from livna/rpm-fusion but not Fedora.
As for wanting compiz to show off to Windows users...feh
Craig
On Sat, 2009-01-17 at 20:16 +0100, Kevin Kofler wrote:
Craig White wrote:
kcmshell ksynaptics says...
Shared Memory is not accessible.
Please add the option 'SHMConfig "on"' into the touchpad section of /etc/X11/xorg.conf
and of course, there isn't any xorg.conf file - ignoring that, it says 'Using Driver' "none" - which of course is why my touchpad isn't happening.
do I have to insmod/modprobe something?
Create an /etc/hal/fdi/policy/11-synaptics.fdi with the following contents:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <merge key="input.x11_options.SHMConfig" type="string">true</merge> </match> </device> </deviceinfo>
Using xorg.conf for input configuration is obsolete and should no longer be done.
Be warned that SHMConfig is insecure (that's why it's disabled by default).
---- thanks
any commentary about why I have to launch systemsettings and click on the 'Display' control panel which clearly remembers the settings and applies them rather than just applying them when I log into my account with KDE Desktop?
Craig
Craig White wrote:
any commentary about why I have to launch systemsettings and click on the 'Display' control panel which clearly remembers the settings and applies them rather than just applying them when I log into my account with KDE Desktop?
Because KDE does not automatically restore those settings on startup. It's an upstream KDE 4 issue.
You can try krandrtray which will restore your settings on startup, but it's yet another systray icon.
Kevin Kofler
On Sun, 2009-01-18 at 04:56 +0100, Kevin Kofler wrote:
Craig White wrote:
any commentary about why I have to launch systemsettings and click on the 'Display' control panel which clearly remembers the settings and applies them rather than just applying them when I log into my account with KDE Desktop?
Because KDE does not automatically restore those settings on startup. It's an upstream KDE 4 issue.
You can try krandrtray which will restore your settings on startup, but it's yet another systray icon.
---- thanks - will try tomorrow - am presently untethered (no KVM)
Craig
Bugzilla from kevin.kofler@chello.at wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
snip
Kevin Kofler
OK I need some advice please. I have a machine with no xorg.conf and I need to have it running vncserver loaded when X itself starts. In the past you could simply add a Load "vnc" line to the appropriate section of xorg.conf
Please can you advise me how this is achieved on a system without any xorg.conf?
Secondly, if running with an xorg.conf is now obsolete - please also tell me how to get a system that has Intel Graphics (a different computer) running X without any xorg.conf if the only way I know is to deliberately run with the vesa driver since the intel driver fails to work with that hardware? In fact even adding "xdriver=vesa" to the kernel boot line will likely create an xorg.conf file?
I do believe that there are still particular needs and particular combinations of hardware where running without an xorg.conf file will not work particularly since the needs are not satisfied by properly working drivers in some cases, and because alternative ways of loading particular modules is not provided in other cases.
The aim may well be to have no need for an xorg.conf file in the future but I do believe that we are not there yet!
Mike Cloaked wrote:
OK I need some advice please. I have a machine with no xorg.conf and I need to have it running vncserver loaded when X itself starts. In the past you could simply add a Load "vnc" line to the appropriate section of xorg.conf
Please can you advise me how this is achieved on a system without any xorg.conf?
I don't know. Maybe xorg.conf is still the right place for that.
Secondly, if running with an xorg.conf is now obsolete - please also tell me how to get a system that has Intel Graphics (a different computer) running X without any xorg.conf if the only way I know is to deliberately run with the vesa driver since the intel driver fails to work with that hardware? In fact even adding "xdriver=vesa" to the kernel boot line will likely create an xorg.conf file?
Yes, you need an xorg.conf to use a different graphics driver.
I only said that xorg.conf should no longer be used to set options for input devices, because those are now handled by HAL, and options can be set in HAL FDI files. It is also not needed to get graphics up with the default settings. But to set custom options for graphics, it is still the place to set them up (unless you can/want to set them per user using XRandR, but you can't switch the driver that way).
Kevin Kofler
On Sun, 2009-01-18 at 02:52 -0800, Mike Cloaked wrote:
Bugzilla from kevin.kofler@chello.at wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
snip
Kevin KoflerOK I need some advice please. I have a machine with no xorg.conf and I need to have it running vncserver loaded when X itself starts. In the past you could simply add a Load "vnc" line to the appropriate section of xorg.conf
Please can you advise me how this is achieved on a system without any xorg.conf?
---- yum install vnc-server # after editing /etc/sysconfig/vncserver appropriately, # setting user password and Xsettings... service vncserver start
Craig
On Sun, 2009-01-18 at 02:52 -0800, Mike Cloaked wrote:
Bugzilla from kevin.kofler@chello.at wrote:
Using xorg.conf for input configuration is obsolete and should no longer be done.
snip
Kevin KoflerOK I need some advice please. I have a machine with no xorg.conf and I need to have it running vncserver loaded when X itself starts. In the past you could simply add a Load "vnc" line to the appropriate section of xorg.conf.
vncserver is started by a /etc/inid.d script. It an be made to run on boot using chkconfig. Or am I missing something about what you want to do.
Please can you advise me how this is achieved on a system without any xorg.conf?
-- ======================================================================= The British are coming! The British are coming! ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Aaron Konstam wrote:
OK I need some advice please. I have a machine with no xorg.conf and I need to have it running vncserver loaded when X itself starts. In the past you could simply add a Load "vnc" line to the appropriate section of xorg.conf.
vncserver is started by a /etc/inid.d script. It an be made to run on boot using chkconfig. Or am I missing something about what you want to do.
Yes I believe that quite a few people are missing the point here - the point is that if you are managing a machine remotely and need to have the console X session visible at all stages of the operation of the machine then the vnc module needs to be started when X starts - here we are not talking about connecting to a remote X session visible on the client only but a desktop sharing mode where I for example can see the primary console session of a machine elsewhere even if the other computer is not yet logged in to a user. Hence by loading the vnc module in the xorg.conf file (as i have been doing for many years) then as soon as X starts it is possible to view that session from afar and log in on as if you were at the screen on the machine itself.
The ONLY way I know to do this is to load the vnc module in xorg.conf....
starting the vncserver would presumably allow you to make a remote X session visible from another machine but this would not be the primary console session on the server machine where vncserver is running?
I asked this same question some time ago concerning freenx where it seems that the same confusion arises. I never did get any direct advice on how to achieve desktop sharing between the primary desktop (including the login greeter before and after the user login) and a remote machine seeing the same desktop as a window on its own desktop session.
Please do enlighten me?
On Sat, 2009-01-17 at 20:16 +0100, Kevin Kofler wrote:
Craig White wrote:
kcmshell ksynaptics says...
Shared Memory is not accessible.
Please add the option 'SHMConfig "on"' into the touchpad section of /etc/X11/xorg.conf
and of course, there isn't any xorg.conf file - ignoring that, it says 'Using Driver' "none" - which of course is why my touchpad isn't happening.
do I have to insmod/modprobe something?
Create an /etc/hal/fdi/policy/11-synaptics.fdi with the following contents:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <merge key="input.x11_options.SHMConfig" type="string">true</merge> </match> </device> </deviceinfo>
Using xorg.conf for input configuration is obsolete and should no longer be done.
Be warned that SHMConfig is insecure (that's why it's disabled by default).
---- probably something for bugzilla but running kcmshell ksynaptics now reports to terminal... $ kcmshell ksynaptics DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... getInstance(pad.cpp:16) --- waiting for lock... Pad(pad.cpp:45) --- created singleton registerParameters(pad.cpp:489) --- registration done! init(pad.cpp:494) --- this version of libsynaptics supports the following driver versions: init(pad.cpp:499) --- --- 0.14.4 init(pad.cpp:499) --- --- 0.14.5 init(pad.cpp:499) --- --- 0.14.6 init(pad.cpp:501) --- initializing fitting driver segment... detectDriverVersion(pad.cpp:150) --- detecting driver version... driverStr(pad.cpp:193) --- driverStr intVerToStrVer(pad.cpp:96) --- intVerToStrVer detectDriverVersion(pad.cpp:180) --- detected driver version 0.15.2 driverVersion(pad.cpp:115) --- driverVersion driverVersion(pad.cpp:115) --- driverVersion init(pad.cpp:545) --- driver is too recent, please downgrade driver or update libsynaptics! getInstance(pad.cpp:20) --- ...unlocking done! libraryStr(pad.cpp:199) --- libraryStr driverKind(pad.cpp:132) --- driverKind driverStr(pad.cpp:193) --- driverStr intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasShm(pad.cpp:144) --- hasShm hasShm(pad.cpp:144) --- hasShm hasDriver(pad.cpp:138) --- hasDriver hasDriver(pad.cpp:138) --- hasDriver Launched ok, pid = 3180 hasParam(pad.cpp:256) --- hasParam intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasParam(pad.cpp:256) --- hasParam intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasDriver(pad.cpp:138) --- hasDriver ~Pad(pad.cpp:36) --- detach driver ~Pad(pad.cpp:39) --- deleted singleton [craig@aspire-one ~]$ ICE default IO error handler doing an exit(), pid = 3177, errno = 11
and in a dialog - it just says that no driver was found and is pretty much worthless to me at this point.
Craig
On Sun, 2009-01-18 at 22:01 +0100, Kevin Kofler wrote:
Craig White wrote:
init(pad.cpp:545) --- driver is too recent, please downgrade driver or update libsynaptics!
libsynaptics needs to be updated. Talk to the libsynaptics maintainer (probably through Bugzilla).
---- done...
https://bugzilla.redhat.com/show_bug.cgi?id=480573
thanks for all of your help
Craig
Craig
How do I report that Fedora's Xorg does not support intermediate sweep rates for 1200x960 resolution (only have 85 and 60, whereas 70 is the best to use for sizing and centering the screen in the CRT)
Somewhere Xorg must get hardware information.
--- On Sun, 1/18/09, Craig White craigwhite@azapple.com wrote: From: Craig White craigwhite@azapple.com Subject: Re: life without system-config-display To: "Community assistance, encouragement, and advice for using Fedora." fedora-list@redhat.com Date: Sunday, January 18, 2009, 1:02 PM
On Sat, 2009-01-17 at 20:16 +0100, Kevin Kofler wrote:
Craig White wrote:
kcmshell ksynaptics says...
Shared Memory is not accessible.
Please add the option 'SHMConfig "on"' into the
touchpad section
of /etc/X11/xorg.conf
and of course, there isn't any xorg.conf file - ignoring that, it
says
'Using Driver' "none" - which of course is why my
touchpad isn't
happening.
do I have to insmod/modprobe something?
Create an /etc/hal/fdi/policy/11-synaptics.fdi with the following
contents:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2"> <device> <match key="info.capabilities"
contains="input.touchpad">
<merge key="input.x11_options.SHMConfig"type="string">true</merge> </match>
</device> </deviceinfo>
Using xorg.conf for input configuration is obsolete and should no longer
be
done.
Be warned that SHMConfig is insecure (that's why it's disabled by
default). ---- probably something for bugzilla but running kcmshell ksynaptics now reports to terminal... $ kcmshell ksynaptics DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... getInstance(pad.cpp:16) --- waiting for lock... Pad(pad.cpp:45) --- created singleton registerParameters(pad.cpp:489) --- registration done! init(pad.cpp:494) --- this version of libsynaptics supports the following driver versions:
init(pad.cpp:499) --- --- 0.14.4 init(pad.cpp:499) --- --- 0.14.5 init(pad.cpp:499) --- --- 0.14.6 init(pad.cpp:501) --- initializing fitting driver segment... detectDriverVersion(pad.cpp:150) --- detecting driver version... driverStr(pad.cpp:193) --- driverStr intVerToStrVer(pad.cpp:96) --- intVerToStrVer detectDriverVersion(pad.cpp:180) --- detected driver version 0.15.2 driverVersion(pad.cpp:115) --- driverVersion driverVersion(pad.cpp:115) --- driverVersion init(pad.cpp:545) --- driver is too recent, please downgrade driver or update libsynaptics!
getInstance(pad.cpp:20) --- ...unlocking done! libraryStr(pad.cpp:199) --- libraryStr driverKind(pad.cpp:132) --- driverKind driverStr(pad.cpp:193) --- driverStr intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasShm(pad.cpp:144) --- hasShm hasShm(pad.cpp:144) --- hasShm hasDriver(pad.cpp:138) --- hasDriver hasDriver(pad.cpp:138) --- hasDriver Launched ok, pid = 3180 hasParam(pad.cpp:256) --- hasParam intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasParam(pad.cpp:256) --- hasParam intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer hasDriver(pad.cpp:138) --- hasDriver ~Pad(pad.cpp:36) --- detach driver ~Pad(pad.cpp:39) --- deleted singleton [craig@aspire-one ~]$ ICE default IO error handler doing an exit(), pid = 3177, errno = 11
and in a dialog - it just says that no driver was found and is pretty much worthless to me at this point.
Craig
On Sun, 2009-01-18 at 18:25 -0800, Leslie Satenstein wrote:
Craig
How do I report that Fedora's Xorg does not support intermediate sweep rates for 1200x960 resolution (only have 85 and 60, whereas 70 is the best to use for sizing and centering the screen in the CRT)
Somewhere Xorg must get hardware information.
---- http://bugzilla.redhat.com
You probably want to provide things like...
- model of your monitor/display (your video card hardware should be obvious from the next item)
- output of command, lspci -v
- contents of /var/log/Xorg.0.log (probably best this as an attachment)
Also - for the record, you might consider not jumping in with your issues on other people's threads but I do concede that yours is somewhat related and I am finished with the thread anyway so it's not a problem but it's often considered rude.
Craig
On Fri, 16 Jan 2009 21:56:40 -0700 Craig White wrote:
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
The trackpad works fine on my Acer Aspire One with F10. In fact, I've never had a "real" mouse on that machine yet.
On Fri, 2009-01-16 at 23:09 -0600, Frank Cox wrote:
On Fri, 16 Jan 2009 21:56:40 -0700 Craig White wrote:
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
The trackpad works fine on my Acer Aspire One with F10. In fact, I've never had a "real" mouse on that machine yet.
---- that's not very helpful. I suspect that because my setup has always had a USB mouse connected until now, that's why I don't have it.
At least look in /etc/modprobe.conf or do an lsmod and give me a hint where the solution is
Craig
On Fri, 2009-01-16 at 22:22 -0700, Craig White wrote:
On Fri, 2009-01-16 at 23:09 -0600, Frank Cox wrote:
On Fri, 16 Jan 2009 21:56:40 -0700 Craig White wrote:
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
The trackpad works fine on my Acer Aspire One with F10. In fact, I've never had a "real" mouse on that machine yet.
that's not very helpful. I suspect that because my setup has always had a USB mouse connected until now, that's why I don't have it.
At least look in /etc/modprobe.conf or do an lsmod and give me a hint where the solution is
---- never mind...PEBKAC
apparently <Function><F7> is a toggle for on/off on the touchpad and I must have fat fingered it when I was going for <Function><F6> for the KVM display.
Nice that I can shut it off when I'm seriously typing. Bad that my eyesight requires me to take off my glasses to try to figure out what the little symbols are on the little keyboard.
Thanks
Craig
On Fri, 16 Jan 2009 22:22:51 -0700 Craig White wrote:
that's not very helpful. I suspect that because my setup has always had a USB mouse connected until now, that's why I don't have it.
At least look in /etc/modprobe.conf or do an lsmod and give me a hint where the solution is
[frankcox@acer ~]$ ll /etc/modprobe.conf -rw-r--r-- 1 root root 0 2008-11-04 05:51 /etc/modprobe.conf [frankcox@acer ~]$ /sbin/lsmod Module Size Used by aes_i586 11648 1 aes_generic 31144 1 aes_i586 fuse 49436 2 i915 53508 2 drm 158260 3 i915 sunrpc 155924 3 ip6t_REJECT 7296 2 nf_conntrack_ipv6 15864 2 ip6table_filter 6400 1 ip6_tables 14736 1 ip6table_filter ipv6 230132 32 ip6t_REJECT,nf_conntrack_ipv6 cpufreq_ondemand 9996 1 acpi_cpufreq 12172 1 dm_multipath 17164 0 snd_hda_intel 395544 3 snd_seq_dummy 6660 0 snd_seq_oss 30364 0 snd_seq_midi_event 9600 1 snd_seq_oss snd_seq 48320 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 9996 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 41600 0 snd_mixer_oss 16896 1 snd_pcm_oss snd_pcm 64772 2 snd_hda_intel,snd_pcm_oss arc4 5760 2 ecb 6528 2 crypto_blkcipher 18052 1 ecb snd_timer 21896 2 snd_seq,snd_pcm snd_page_alloc 11144 2 snd_hda_intel,snd_pcm snd_hwdep 10372 1 snd_hda_intel snd 51768 16 snd_hda_intel,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep soundcore 9416 1 snd i2c_i801 12048 0 i2c_core 21396 2 drm,i2c_i801 uvcvideo 51720 0 iTCO_wdt 13732 0 iTCO_vendor_support 6916 1 iTCO_wdt ath5k 112520 0 mac80211 173668 1 ath5k cfg80211 23816 2 ath5k,mac80211 r8169 32132 0 acer_wmi 17472 0 mii 8192 1 r8169 compat_ioctl32 5120 1 uvcvideo serio_raw 8836 0 pcspkr 6272 0 video 20244 0 videodev 32000 1 uvcvideo v4l1_compat 15876 2 uvcvideo,videodev joydev 12736 0 output 6528 1 video wmi 9768 1 acer_wmi ata_generic 8452 0 pata_acpi 7680 0
On Fri, 2009-01-16 at 22:22 -0700, Craig White wrote:
On Fri, 2009-01-16 at 23:09 -0600, Frank Cox wrote:
On Fri, 16 Jan 2009 21:56:40 -0700 Craig White wrote:
One more thing...I set it up with my KVM and finally just booted it without any of that attached and realized that the built-in track pad doesn't work at all. I installed ksynaptics, disconnected the USB mouse and rebooted but it still seems dead to the world in Fedora, not in Windows. Anyone have a suggestion?
The trackpad works fine on my Acer Aspire One with F10. In fact, I've never had a "real" mouse on that machine yet.
that's not very helpful. I suspect that because my setup has always had a USB mouse connected until now, that's why I don't have it.
At least look in /etc/modprobe.conf or do an lsmod and give me a hint where the solution is
Sorry, I'm late to this thread. If the question is how to let ksynaptics/gsynaptics control touchpad features in F10, the answer is to create /etc/hal/fdi/policy/10-synaptics.fdi containing:
<?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <match key="info.product" contains="Synaptics TouchPad"> <merge key="input.x11_driver" type="string">synaptics</merge> <merge key="input.x11_options.SHMConfig" type="string">On</merge> </match> <match key="info.product" contains="AlpsPS/2 ALPS"> <merge key="input.x11_driver" type="string">synaptics</merge> </match> <match key="info.product" contains="appletouch"> <merge key="input.x11_driver" type="string">synaptics</merge> </match> <match key="info.product" contains="bcm5974"> <merge key="input.x11_driver" type="string">synaptics</merge> </match> </match> </device> </deviceinfo>
For where this comes from, see /usr/share/hal/fdi/policy/20thirdparty/10-synaptics.fdi. Note the line above containing "SHMConfig"
HTH.
Craig
-
Aaron Konstam -
Craig White -
Frank Cox -
Kevin Kofler -
Leslie S Satenstein -
Matthew Saltzman -
mike cloaked -
Tom Horsley