I'm not sure if any of you guys have encountered this (weird) situation.
First of all, my laptop spec is Compaq Presario 2166ae (AMD Athlon XP-M 2400+, ATI Radeon Mobile U1). I installed FreeBSD 7.2-RELEASE from DVD; that is, I'm not upgrading and everything is supposed to be updated.
After installing all distributions and packages on the DVD, I copied /root/xorg.conf.new to /etc/X11/xorg.conf, and enabled hal and dbus by adding the following two lines in /etc/rc.conf:
And the following lines in /etc/X11/xorg.conf:
I then added following lines in ~/.xinitrc:
Then launched X by typing startx. Everything was fine, including the resolution, E17, keyboard, and mouse were all working smoothly. I then launched windowmaker, and still everything were working good. Then I switched kde4, and noticed that somthing got strange - nothing in KDE4 was working unless I move my mouse. For example, when I clicked a button nothing happend until I pinch my mouse. I then switched back to E17, but this phenomenom was still there; on E17's default theme when the cursor is hovering above a list there should be "shining" animation moving across the list as well as fading in and out, but now these animations are all freezed - only when I pinch the mouse does everying work a bit. Another example is that, when I wanted to type something in xterm, those characters didn't show up until I move the mouse. In short: when the mouse doesn't move, so doesn't everything (regardless of being a user or root)!
At first I thought the gigantic kde4 was the cause, but then I tried to re-install FBSD7.2 from DVD but only with windowmaker as the window manager but again, everything was fine at first and then the phenomenom came back (before this happened again, I installed thunderbird and pidgin using pkg_add -r). I haven't got time to have a look at /var/log/Xorg.0.log or dmesg at the moment (will check these logs this weekend) but IMHM I don't think I came across with any error message... The system is still usable, but this is extremely annoying...x(
Anyone had this problem before? Any solution or advice would be appreciated.
First of all, my laptop spec is Compaq Presario 2166ae (AMD Athlon XP-M 2400+, ATI Radeon Mobile U1). I installed FreeBSD 7.2-RELEASE from DVD; that is, I'm not upgrading and everything is supposed to be updated.
After installing all distributions and packages on the DVD, I copied /root/xorg.conf.new to /etc/X11/xorg.conf, and enabled hal and dbus by adding the following two lines in /etc/rc.conf:
Code:
hald_enable="YES"
dbus_enable="YES"
And the following lines in /etc/X11/xorg.conf:
Code:
Section "ServerFlags"
Option "AllowEmptyInput" "false"
EndSection
I then added following lines in ~/.xinitrc:
Code:
exec enlightenment_start
#exec wmaker
#exec /usr/local/kde4/bin/startkde
Then launched X by typing startx. Everything was fine, including the resolution, E17, keyboard, and mouse were all working smoothly. I then launched windowmaker, and still everything were working good. Then I switched kde4, and noticed that somthing got strange - nothing in KDE4 was working unless I move my mouse. For example, when I clicked a button nothing happend until I pinch my mouse. I then switched back to E17, but this phenomenom was still there; on E17's default theme when the cursor is hovering above a list there should be "shining" animation moving across the list as well as fading in and out, but now these animations are all freezed - only when I pinch the mouse does everying work a bit. Another example is that, when I wanted to type something in xterm, those characters didn't show up until I move the mouse. In short: when the mouse doesn't move, so doesn't everything (regardless of being a user or root)!
At first I thought the gigantic kde4 was the cause, but then I tried to re-install FBSD7.2 from DVD but only with windowmaker as the window manager but again, everything was fine at first and then the phenomenom came back (before this happened again, I installed thunderbird and pidgin using pkg_add -r). I haven't got time to have a look at /var/log/Xorg.0.log or dmesg at the moment (will check these logs this weekend) but IMHM I don't think I came across with any error message... The system is still usable, but this is extremely annoying...x(
Anyone had this problem before? Any solution or advice would be appreciated.