| Summary: | Mouse/Keyboard cannot work with poky-image-sato-live on netbook | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | meta-yocto | Assignee: | Jeff Dike <jeffrey.g.dike> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | High | CC: | kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, susie.li, yongkang.you |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M2 | ||
| Hardware: | Netbook | ||
| OS: | x86 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
| Attachments: | |||
|
Description
Jiajun Xu
2010-07-26 01:32:23 UTC
The commit is fbf2022c9a082edfa86d6acd7078dd6ad6968f71 from poky master tree. commit fbf2022c9a082edfa86d6acd7078dd6ad6968f71 Author: Richard Purdie <rpurdie@linux.intel.com> Date: Thu Jul 22 23:56:36 2010 +0100 sanity.conf: Update layer version after the last commit Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> (In reply to comment #1) > The commit is fbf2022c9a082edfa86d6acd7078dd6ad6968f71 from poky master tree. > commit fbf2022c9a082edfa86d6acd7078dd6ad6968f71 > Author: Richard Purdie <rpurdie@linux.intel.com> > Date: Thu Jul 22 23:56:36 2010 +0100 > sanity.conf: Update layer version after the last commit > Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> Could you post the entire X.log? The lines that you showed aren't necessarily errors - they are marked as informational. Jeff Created attachment 23 [details]
Xorg log
(In reply to comment #3) > Created attachment 23 [details] > Xorg log Can you add the following to your /etc/X11/xorg.conf? Section "ServerFlags" Option "AutoAddDevices" "False" EndSection Also make sure your /etc/formfactor/config says: HAVE_TOUCHSCREEN=0 (In reply to comment #4) > (In reply to comment #3) > > Created attachment 23 [details] [details] > > Xorg log > Can you add the following to your /etc/X11/xorg.conf? > Section "ServerFlags" > Option "AutoAddDevices" "False" > EndSection > Also make sure your /etc/formfactor/config says: > HAVE_TOUCHSCREEN=0 It can work now after I modified as you mentioned. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Created attachment 23 [details] [details] [details] > > > Xorg log > > Can you add the following to your /etc/X11/xorg.conf? > > Section "ServerFlags" > > Option "AutoAddDevices" "False" > > EndSection > > Also make sure your /etc/formfactor/config says: > > HAVE_TOUCHSCREEN=0 > It can work now after I modified as you mentioned. Just to be clear... The mouse and keyboard are working and this bug can be closed? (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #3) > > > > Created attachment 23 [details] [details] [details] [details] > > > > Xorg log > > > Can you add the following to your /etc/X11/xorg.conf? > > > Section "ServerFlags" > > > Option "AutoAddDevices" "False" > > > EndSection > > > Also make sure your /etc/formfactor/config says: > > > HAVE_TOUCHSCREEN=0 > > It can work now after I modified as you mentioned. > Just to be clear... > The mouse and keyboard are working and this bug can be closed? instead of closing it immediately, it's better to change default xorg.conf and /etc/formfactor/config for netbook in poky, instead of requiring manual modification every time. So patch is welcomed. :-) (In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > (In reply to comment #4) > > > > (In reply to comment #3) > > > > > Created attachment 23 [details] [details] [details] [details] [details] > > > > > Xorg log > > > > Can you add the following to your /etc/X11/xorg.conf? > > > > Section "ServerFlags" > > > > Option "AutoAddDevices" "False" > > > > EndSection > > > > Also make sure your /etc/formfactor/config says: > > > > HAVE_TOUCHSCREEN=0 > > > It can work now after I modified as you mentioned. > > Just to be clear... > > The mouse and keyboard are working and this bug can be closed? > instead of closing it immediately, it's better to change default xorg.conf and > /etc/formfactor/config for netbook in poky, instead of requiring manual > modification every time. So patch is welcomed. :-) Yes, good point. I'll close this when a fix has been merged.
> > > Just to be clear...
> > > The mouse and keyboard are working and this bug can be closed?
> > instead of closing it immediately, it's better to change default xorg.conf and
> > /etc/formfactor/config for netbook in poky, instead of requiring manual
> > modification every time. So patch is welcomed. :-)
> Yes, good point.
> I'll close this when a fix has been merged.
Thanks for Kevin's clear comments. :)
Jeff, You can change the bug status "RESOLVED" after your fixing is built in milestone build. I will verify it and mark it as "VERIFIED".
(In reply to comment #9) > > > > Just to be clear... > > > > The mouse and keyboard are working and this bug can be closed? > > > instead of closing it immediately, it's better to change default xorg.conf and > > > /etc/formfactor/config for netbook in poky, instead of requiring manual > > > modification every time. So patch is welcomed. :-) > > Yes, good point. > > I'll close this when a fix has been merged. > Thanks for Kevin's clear comments. :) > Jeff, You can change the bug status "RESOLVED" after your fixing is built in > milestone build. I will verify it and mark it as "VERIFIED". One concern I have whether this is applicable to all netbooks. You had a problem with one particular netbook, but how do we know that applying this to all netbooks is correct for them? (In reply to comment #10) > (In reply to comment #9) > > > > > Just to be clear... > > > > > The mouse and keyboard are working and this bug can be closed? > > > > instead of closing it immediately, it's better to change default xorg.conf and > > > > /etc/formfactor/config for netbook in poky, instead of requiring manual > > > > modification every time. So patch is welcomed. :-) > > > Yes, good point. > > > I'll close this when a fix has been merged. > > Thanks for Kevin's clear comments. :) > > Jeff, You can change the bug status "RESOLVED" after your fixing is built in > > milestone build. I will verify it and mark it as "VERIFIED". > One concern I have whether this is applicable to all netbooks. You had a > problem with one particular netbook, but how do we know that applying this to > all netbooks is correct for them? It seems that there's no elegant solution to address all netbooks. We have to handle them one-by-one, e.g. by defining them as separate MACHINE with its own set of config files. But in general we could provide a generate feature set which perhaps work for most models, or at least the Intel modles we currently mean to support. For example, HAVE_TOUCHSCREEN perhaps is a good default off. I'm not familar with AutoAddDevices though. Even MeeGo I don't think the default released image can seamlessly run on all netbooks. Our QA just tests several models in house. (In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #9) > > > > > > Just to be clear... > > > > > > The mouse and keyboard are working and this bug can be closed? > > > > > instead of closing it immediately, it's better to change default xorg.conf and > > > > > /etc/formfactor/config for netbook in poky, instead of requiring manual > > > > > modification every time. So patch is welcomed. :-) > > > > Yes, good point. > > > > I'll close this when a fix has been merged. > > > Thanks for Kevin's clear comments. :) > > > Jeff, You can change the bug status "RESOLVED" after your fixing is built in > > > milestone build. I will verify it and mark it as "VERIFIED". > > One concern I have whether this is applicable to all netbooks. You had a > > problem with one particular netbook, but how do we know that applying this to > > all netbooks is correct for them? > It seems that there's no elegant solution to address all netbooks. We have to > handle them one-by-one, e.g. by defining them as separate MACHINE with its own > set of config files. But in general we could provide a generate feature set > which perhaps work for most models, or at least the Intel modles we currently > mean to support. For example, HAVE_TOUCHSCREEN perhaps is a good default off. > I'm not familar with AutoAddDevices though. Even MeeGo I don't think the > default released image can seamlessly run on all netbooks. Our QA just tests > several models in house. So, you would suggest making a new MACHINE for this which says that it's a netbook, but it needs AutoAddDevices off? That seems reasonable to me, but emenlow requires it as well, and I bet others do too, so we might end up with a collection of different machines needing the same settings. netbook already has HAVE_TOUCHSCREEN off (and I assume that Jiajun didn't need to change it), so that's fine. (In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > > (In reply to comment #9) > > > > > > > Just to be clear... > > > > > > > The mouse and keyboard are working and this bug can be closed? > > > > > > instead of closing it immediately, it's better to change default xorg.conf and > > > > > > /etc/formfactor/config for netbook in poky, instead of requiring manual > > > > > > modification every time. So patch is welcomed. :-) > > > > > Yes, good point. > > > > > I'll close this when a fix has been merged. > > > > Thanks for Kevin's clear comments. :) > > > > Jeff, You can change the bug status "RESOLVED" after your fixing is built in > > > > milestone build. I will verify it and mark it as "VERIFIED". > > > One concern I have whether this is applicable to all netbooks. You had a > > > problem with one particular netbook, but how do we know that applying this to > > > all netbooks is correct for them? > > It seems that there's no elegant solution to address all netbooks. We have to > > handle them one-by-one, e.g. by defining them as separate MACHINE with its own > > set of config files. But in general we could provide a generate feature set > > which perhaps work for most models, or at least the Intel modles we currently > > mean to support. For example, HAVE_TOUCHSCREEN perhaps is a good default off. > > I'm not familar with AutoAddDevices though. Even MeeGo I don't think the > > default released image can seamlessly run on all netbooks. Our QA just tests > > several models in house. > So, you would suggest making a new MACHINE for this which says that it's a > netbook, but it needs AutoAddDevices off? That seems reasonable to me, but > emenlow requires it as well, and I bet others do too, so we might end up with a > collection of different machines needing the same settings. > netbook already has HAVE_TOUCHSCREEN off (and I assume that Jiajun didn't need > to change it), so that's fine. Does emenlow use same xorg.conf as netbook now? I'm not sure about this part. Since emenlow is a seperate layer, I guess it has its own config there? But my gut-feeling seems that it's reasonable to have different xorg.conf for different machine. One example is to look at meta/packages/xorg-xserver/xserver-xf86-config. OpenEmbedded even has dozens of machine specific xorg.conf. Also has a quick learn about AutoAddDevices just now. From its meaning, no new device from HAL will be added if it's disabled. Does it exclude USB devices too? presumably disable this option looks a workaround, and there may be other things we need dig out? :-) > So, you would suggest making a new MACHINE for this which says that it's a
> netbook, but it needs AutoAddDevices off? That seems reasonable to me, but
> emenlow requires it as well, and I bet others do too, so we might end up with a
> collection of different machines needing the same settings.
> netbook already has HAVE_TOUCHSCREEN off (and I assume that Jiajun didn't need
> to change it), so that's fine.
Jeff,
HAVE_TOUCHSCREEN is set to "1" in my /etc/formfactor/config.
Do you mean you have disabled it but the patch is not in M2 build?
(In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > (In reply to comment #10) > > > > (In reply to comment #9) > > > > > > > > Just to be clear... > > > > > > > > The mouse and keyboard are working and this bug can be closed? > > > > > > > instead of closing it immediately, it's better to change default xorg.conf and > > > > > > > /etc/formfactor/config for netbook in poky, instead of requiring manual > > > > > > > modification every time. So patch is welcomed. :-) > > > > > > Yes, good point. > > > > > > I'll close this when a fix has been merged. > > > > > Thanks for Kevin's clear comments. :) > > > > > Jeff, You can change the bug status "RESOLVED" after your fixing is built in > > > > > milestone build. I will verify it and mark it as "VERIFIED". > > > > One concern I have whether this is applicable to all netbooks. You had a > > > > problem with one particular netbook, but how do we know that applying this to > > > > all netbooks is correct for them? > > > It seems that there's no elegant solution to address all netbooks. We have to > > > handle them one-by-one, e.g. by defining them as separate MACHINE with its own > > > set of config files. But in general we could provide a generate feature set > > > which perhaps work for most models, or at least the Intel modles we currently > > > mean to support. For example, HAVE_TOUCHSCREEN perhaps is a good default off. > > > I'm not familar with AutoAddDevices though. Even MeeGo I don't think the > > > default released image can seamlessly run on all netbooks. Our QA just tests > > > several models in house. > > So, you would suggest making a new MACHINE for this which says that it's a > > netbook, but it needs AutoAddDevices off? That seems reasonable to me, but > > emenlow requires it as well, and I bet others do too, so we might end up with a > > collection of different machines needing the same settings. > > netbook already has HAVE_TOUCHSCREEN off (and I assume that Jiajun didn't need > > to change it), so that's fine. > Does emenlow use same xorg.conf as netbook now? I'm not sure about this part. > Since emenlow is a seperate layer, I guess it has its own config there? > But my gut-feeling seems that it's reasonable to have different xorg.conf for > different machine. One example is to look at > meta/packages/xorg-xserver/xserver-xf86-config. OpenEmbedded even has dozens of > machine specific xorg.conf. > Also has a quick learn about AutoAddDevices just now. From its meaning, no new > device from HAL will be added if it's disabled. Does it exclude USB devices > too? presumably disable this option looks a workaround, and there may be other > things we need dig out? :-) emenlow does have its own xorg.conf, but that's a small addition considering all of the other special stuff it has (its own layer rather than just an extra machine file). Also, the mouse was the only problem - the keyboard was fine. There's only two machine-specific xorg.conf files now (igep0020 and qemux86), so that doesn't seem like the best argument in favor of another one. Ideally, I'd like to be able to say that this thing is a netbook, except it needs a special flag passed to xserver-xf86-config to have AutoAddDevices=False in xorg.conf. A whole new machine file seems very heavy-handed in comparison to what's really needed. As for its actual meaning, I don't really understand it either. It just seems like a workaround for systems where X doesn't see hot-plugged devices for some reason. (In reply to comment #14) > > So, you would suggest making a new MACHINE for this which says that it's a > > netbook, but it needs AutoAddDevices off? That seems reasonable to me, but > > emenlow requires it as well, and I bet others do too, so we might end up with a > > collection of different machines needing the same settings. > > netbook already has HAVE_TOUCHSCREEN off (and I assume that Jiajun didn't need > > to change it), so that's fine. > Jeff, > HAVE_TOUCHSCREEN is set to "1" in my /etc/formfactor/config. > Do you mean you have disabled it but the patch is not in M2 build? Oh, I didn't expect that :-) You did say this was a netbook, and meta/packages/formfactor/netbook/machconfig has HAVE_TOUCHSCREEN=0 Do you have MACHINE="netbook" or something else? (In reply to comment #15) > emenlow does have its own xorg.conf, but that's a small addition considering > all of the other special stuff it has (its own layer rather than just an extra > machine file). Also, the mouse was the only problem - the keyboard was fine. > There's only two machine-specific xorg.conf files now (igep0020 and qemux86), > so that doesn't seem like the best argument in favor of another one. If you look at OpenEmbedded side, there're tons of them. But surely I may be wrong here as it's also my first time to think about this issue, and there may be other ways cleaner :/ > Ideally, I'd like to be able to say that this thing is a netbook, except it > needs a special flag passed to xserver-xf86-config to have AutoAddDevices=False > in xorg.conf. > A whole new machine file seems very heavy-handed in comparison to what's really > needed. So do you know any tricks to add those tweak lines for netbook, patching xorg.conf? Or does xserver support cmd parameter for similar effect? If not providing machine specific xorg.conf, then the only way I can come up now is to dynamically change some thing... > As for its actual meaning, I don't really understand it either. It just seems > like a workaround for systems where X doesn't see hot-plugged devices for some > reason. Well, then Jiajun can further test whether something is broken. If everything works fine, perhaps it's fine as a workaround for M2 (In reply to comment #16) > > Jeff, > > HAVE_TOUCHSCREEN is set to "1" in my /etc/formfactor/config. > > Do you mean you have disabled it but the patch is not in M2 build? > Oh, I didn't expect that :-) > You did say this was a netbook, and meta/packages/formfactor/netbook/machconfig > has HAVE_TOUCHSCREEN=0 > Do you have MACHINE="netbook" or something else? OK. So no problem now. You mean HAVE_TOUCHSCREEN should be set to 0 in /etc/formfactor/machconfig. Yes, it's true on my netbook. In /etc/formfactor/config, it is set to 1. (In reply to comment #18) > (In reply to comment #16) > > > Jeff, > > > HAVE_TOUCHSCREEN is set to "1" in my /etc/formfactor/config. > > > Do you mean you have disabled it but the patch is not in M2 build? > > Oh, I didn't expect that :-) > > You did say this was a netbook, and meta/packages/formfactor/netbook/machconfig > > has HAVE_TOUCHSCREEN=0 > > Do you have MACHINE="netbook" or something else? > OK. So no problem now. You mean HAVE_TOUCHSCREEN should be set to 0 in > /etc/formfactor/machconfig. Yes, it's true on my netbook. > In /etc/formfactor/config, it is set to 1. This problem should be fixed with commit http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jdike/netbook-xorg-conf&id=74160b3721cc3b233911c9d6c887b52435a6d9ae With M2-20100728 build, the bug still exists although /etc/X11/xorg.conf has been modified in image. Created attachment 24 [details]
Xorg log with M2 20100728 image
(In reply to comment #21) > Created attachment 24 [details] > Xorg log with M2 20100728 image It looks exactly the same as the original X log. Can you post your xorg.conf? (In reply to comment #22) > (In reply to comment #21) > > Created attachment 24 [details] [details] > > Xorg log with M2 20100728 image > It looks exactly the same as the original X log. > Can you post your xorg.conf? Yes. I have posted it. See comment 21. (In reply to comment #23) > (In reply to comment #22) > > (In reply to comment #21) > > > Created attachment 24 [details] [details] [details] > > > Xorg log with M2 20100728 image > > It looks exactly the same as the original X log. > > Can you post your xorg.conf? > Yes. I have posted it. See comment 21. That's the log, not the conf file. (In reply to comment #24) > (In reply to comment #23) > > (In reply to comment #22) > > > (In reply to comment #21) > > > > Created attachment 24 [details] [details] [details] [details] > > > > Xorg log with M2 20100728 image > > > It looks exactly the same as the original X log. > > > Can you post your xorg.conf? > > Yes. I have posted it. See comment 21. > That's the log, not the conf file. The xorg.conf like following: ######## Section "ServerFlags" Option "AutoAddDevices" "False" EndSection Section "Device" Identifier "Intel Graphics Driver" Driver "intel" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Intel Graphics Driver" Monitor "Generic Monitor" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" EndSection Section "ServerFlags" Option "DontZap" "0" EndSection ######## (In reply to comment #25) > (In reply to comment #24) > > (In reply to comment #23) > > > (In reply to comment #22) > > > > (In reply to comment #21) > > > > > Created attachment 24 [details] [details] [details] [details] [details] > > > > > Xorg log with M2 20100728 image > > > > It looks exactly the same as the original X log. > > > > Can you post your xorg.conf? > > > Yes. I have posted it. See comment 21. > > That's the log, not the conf file. > The xorg.conf like following: > ######## > Section "ServerFlags" > Option "AutoAddDevices" "False" > EndSection > Section "Device" > Identifier "Intel Graphics Driver" > Driver "intel" > EndSection > Section "Monitor" > Identifier "Generic Monitor" > Option "DPMS" > EndSection > Section "Screen" > Identifier "Default Screen" > Device "Intel Graphics Driver" > Monitor "Generic Monitor" > DefaultDepth 24 > EndSection > Section "ServerLayout" > Identifier "Default Layout" > Screen "Default Screen" > EndSection > Section "ServerFlags" > Option "DontZap" "0" > EndSection > ######## As a test, could you merge the two ServerFlag sections, like this: Section "ServerFlags" Option "DontZap" "0" Option "AutoAddDevices" "False" EndSection I'm suspicious that the second one is completely overriding the first, where I would have liked them to accumulate. (In reply to comment #26) > > The xorg.conf like following: > > ######## > > Section "ServerFlags" > > Option "AutoAddDevices" "False" > > EndSection > > Section "Device" > > Identifier "Intel Graphics Driver" > > Driver "intel" > > EndSection > > Section "Monitor" > > Identifier "Generic Monitor" > > Option "DPMS" > > EndSection > > Section "Screen" > > Identifier "Default Screen" > > Device "Intel Graphics Driver" > > Monitor "Generic Monitor" > > DefaultDepth 24 > > EndSection > > Section "ServerLayout" > > Identifier "Default Layout" > > Screen "Default Screen" > > EndSection > > Section "ServerFlags" > > Option "DontZap" "0" > > EndSection > > ######## > As a test, could you merge the two ServerFlag sections, like this: > Section "ServerFlags" > Option "DontZap" "0" > Option "AutoAddDevices" "False" > EndSection > I'm suspicious that the second one is completely overriding the first, where I > would have liked them to accumulate. I am in home now... So need to check it after I go to office tomorrow. Actually I already tried adding following section to the end today but it cannot help. > > Section "ServerFlags" > > Option "AutoAddDevices" "False" > > EndSection (In reply to comment #27) > (In reply to comment #26) > > > The xorg.conf like following: > > > ######## > > > Section "ServerFlags" > > > Option "AutoAddDevices" "False" > > > EndSection > > > Section "Device" > > > Identifier "Intel Graphics Driver" > > > Driver "intel" > > > EndSection > > > Section "Monitor" > > > Identifier "Generic Monitor" > > > Option "DPMS" > > > EndSection > > > Section "Screen" > > > Identifier "Default Screen" > > > Device "Intel Graphics Driver" > > > Monitor "Generic Monitor" > > > DefaultDepth 24 > > > EndSection > > > Section "ServerLayout" > > > Identifier "Default Layout" > > > Screen "Default Screen" > > > EndSection > > > Section "ServerFlags" > > > Option "DontZap" "0" > > > EndSection > > > ######## > > As a test, could you merge the two ServerFlag sections, like this: > > Section "ServerFlags" > > Option "DontZap" "0" > > Option "AutoAddDevices" "False" > > EndSection > > I'm suspicious that the second one is completely overriding the first, where I > > would have liked them to accumulate. > I am in home now... So need to check it after I go to office tomorrow. > Actually I already tried adding following section to the end today but it > cannot help. > > > Section "ServerFlags" > > > Option "AutoAddDevices" "False" > > > EndSection How did that work on Monday, but doesn't work now? Can you reproduce what you did on Monday (or Tuesday I guess) and show me the resulting xorg.conf when you get back to the office? (In reply to comment #28) > How did that work on Monday, but doesn't work now? > Can you reproduce what you did on Monday (or Tuesday I guess) and show me the > resulting xorg.conf when you get back to the office? OK. I will check it tomorrow. (In reply to comment #29) > (In reply to comment #28) > > How did that work on Monday, but doesn't work now? > > Can you reproduce what you did on Monday (or Tuesday I guess) and show me the > > resulting xorg.conf when you get back to the office? > OK. I will check it tomorrow. I have checked the old(20100725) and the new(20100728) build image. The result is same as before. 20100725 image comes from http://yoctobuild01.jf.intel.com/milestone/20100725-1/netbook/x86_32/ 20100728 image comes from http://yoctobuild01.jf.intel.com/milestone/20100728-1/netbook/x86_32/ The result is as below: A A+ B B+ Mouse/Keyboard N/W W N/W W A: 20100725 image A+: Image A with xorg.conf modified B: 20100728 image B+: Image B with xorg.conf modified N/W: Not Work W: Work Created attachment 25 [details]
Xorg conf and log for 20100725 image, Xorg.conf is original conf file, while Xorg.conf.mod is the file modified
Created attachment 26 [details]
Xorg conf and log for 20100728 image, Xorg.conf is original conf file, while Xorg.conf.mod is the file modified
(In reply to comment #30) > I have checked the old(20100725) and the new(20100728) build image. The result > is same as before. > 20100725 image comes from > http://yoctobuild01.jf.intel.com/milestone/20100725-1/netbook/x86_32/ > 20100728 image comes from > http://yoctobuild01.jf.intel.com/milestone/20100728-1/netbook/x86_32/ > The result is as below: > A A+ B B+ > Mouse/Keyboard N/W W N/W W > A: 20100725 image > A+: Image A with xorg.conf modified > B: 20100728 image > B+: Image B with xorg.conf modified > N/W: Not Work > W: Work The xorg.conf and xorg.log for the two builds are attached as attachment. (In reply to comment #33) > (In reply to comment #30) > > I have checked the old(20100725) and the new(20100728) build image. The result > > is same as before. > > 20100725 image comes from > > http://yoctobuild01.jf.intel.com/milestone/20100725-1/netbook/x86_32/ > > 20100728 image comes from > > http://yoctobuild01.jf.intel.com/milestone/20100728-1/netbook/x86_32/ > > The result is as below: > > A A+ B B+ > > Mouse/Keyboard N/W W N/W W > > A: 20100725 image > > A+: Image A with xorg.conf modified > > B: 20100728 image > > B+: Image B with xorg.conf modified > > N/W: Not Work > > W: Work > The xorg.conf and xorg.log for the two builds are attached as attachment. Can you just post a working xorg.conf? I'm having winzip problems at the moment. (In reply to comment #33) > (In reply to comment #30) > > I have checked the old(20100725) and the new(20100728) build image. The result > > is same as before. > > 20100725 image comes from > > http://yoctobuild01.jf.intel.com/milestone/20100725-1/netbook/x86_32/ > > 20100728 image comes from > > http://yoctobuild01.jf.intel.com/milestone/20100728-1/netbook/x86_32/ > > The result is as below: > > A A+ B B+ > > Mouse/Keyboard N/W W N/W W > > A: 20100725 image > > A+: Image A with xorg.conf modified > > B: 20100728 image > > B+: Image B with xorg.conf modified > > N/W: Not Work > > W: Work > The xorg.conf and xorg.log for the two builds are attached as attachment. Sorry, a typo here, only the modifed xorg.conf with 0725 image can work. The table should be: A A+ B B+ Mouse/Keyboard N/W W N/W N/W A: 20100725 image A+: Image A with xorg.conf modified B: 20100728 image B+: Image B with xorg.conf modified N/W: Not Work W: Work (In reply to comment #35) > (In reply to comment #33) > > (In reply to comment #30) > > > I have checked the old(20100725) and the new(20100728) build image. The result > > > is same as before. > > > 20100725 image comes from > > > http://yoctobuild01.jf.intel.com/milestone/20100725-1/netbook/x86_32/ > > > 20100728 image comes from > > > http://yoctobuild01.jf.intel.com/milestone/20100728-1/netbook/x86_32/ > > > The result is as below: > > > A A+ B B+ > > > Mouse/Keyboard N/W W N/W W > > > A: 20100725 image > > > A+: Image A with xorg.conf modified > > > B: 20100728 image > > > B+: Image B with xorg.conf modified > > > N/W: Not Work > > > W: Work > > The xorg.conf and xorg.log for the two builds are attached as attachment. > Sorry, a typo here, only the modifed xorg.conf with 0725 image can work. > The table should be: > A A+ B B+ > Mouse/Keyboard N/W W N/W N/W > A: 20100725 image > A+: Image A with xorg.conf modified > B: 20100728 image > B+: Image B with xorg.conf modified > N/W: Not Work > W: Work The xorg.conf problem should be fixed by http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jdike/netbook-xorg-conf&id=ba9e8773d0757af59f40b96d40e7bafd54273ccd This file would have made the 0725 image work out of the box. There's a separate problem with the 0728 image. Jiajun will file a separate bug for it, but the short story is that there is a version mismatch between the X server and its modules, and it looks like the X server upgrade wasn't completely done. (In reply to comment #36) > The xorg.conf problem should be fixed by > http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jdike/netbook-xorg-conf&id=ba9e8773d0757af59f40b96d40e7bafd54273ccd > This file would have made the 0725 image work out of the box. > There's a separate problem with the 0728 image. Jiajun will file a separate > bug for it, but the short story is that there is a version mismatch between the > X server and its modules, and it looks like the X server upgrade wasn't > completely done. Jeff, I think you mean even your fixing patch is included, mouse/kdb still cannot work in X either becasue of version mismatch, right? I will open a new bug for it. M2 Commit: http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?id=2550ff720011746fa7d9ab62cb3ec1ac0de5766a Verfied with 20100731 build, the bug is fixed. |