Hello, I am having trouble with Sax2 on an SiS6326 card: when I start it up, it says that the current setup is for XFree86-3, would I like to setup XFree86-4? (note: I have installed the latest sax2-4.2-23 and xf86-4.0.2-5 from ftp.suse.com/put/suse-updates/) and it asks if I want 3D support set up (it doesn't matter if I tell it yes or no, I get the same problem) after that it starts up like normal but I cannot see any text or any buttons. I know it's working because if I hit enter I get another "faceless" dialog box, but I can't set it up that way, and have to stop SaX2 with [CTRL]+[ALT]+[BACKSPACE]. I tried sax (original) and it works fine. Isn't this I bug? I also tried the sax2 -f option, no different. What do you think? Anyone else got a card like this? ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
Jonathan Wilson wrote:
Hello,
I am having trouble with Sax2 on an SiS6326 card: when I start it up, it says that the current setup is for XFree86-3, would I like to setup XFree86-4? (note: I have installed the latest sax2-4.2-23 and xf86-4.0.2-5 from ftp.suse.com/put/suse-updates/) and it asks if I want 3D support set up (it doesn't matter if I tell it yes or no, I get the same problem) after that it starts up like normal but I cannot see any text or any buttons. I know it's working because if I hit enter I get another "faceless" dialog box, but I can't set it up that way, and have to stop SaX2 with [CTRL]+[ALT]+[BACKSPACE]. I tried sax (original) and it works fine.
Isn't this I bug? I also tried the sax2 -f option, no different.
What do you think? Anyone else got a card like this?
---------------------------------------------------- Jonathan Wilson System Administrator
Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
I can't believe this still hasn't been fixed in Xfree86 4x. I used to use this card on a MB I had a couple of years ago and to avoid the anomalies you name, you had to turn off acceleration in the config file. Try doing that (I think the key word is no_accel) and see if that helps. Don -- ======================================== Donald E. Stidwell Network Engineer Information Systems Bon Secours Hampton Roads Home Care Bon Secours Hampton Roads Health System ========================================
Since upgrading from 7.0 to 7.1 my system never seems to be able to set the time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try. I sent in a report request a few weeks ago, but that seemed to go into a black hole too. I would appreciate any ideas anyone may have. -Garen
Since upgrading from 7.0 to 7.1 my system never seems to be able to set
Ok, as silly as this may sound, have you checked these:
What is the time set to in the BIOS? (IS it set to GMT?)
In the configuration section of YAST, is GMT set to -u ?
What time zone are you in?
Is your CMOS battery old, maybe?
This last one REALLY kicked my butt for a couple of weeks a while back.
HTH,
Geordon
----- Original Message -----
From: "Garen Parham"
time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try.
I sent in a report request a few weeks ago, but that seemed to go into a black hole too.
I would appreciate any ideas anyone may have.
-Garen
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Wednesday 04 April 2001 03:46, you wrote:
Since upgrading from 7.0 to 7.1 my system never seems to be able to set the time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try.
Me too! (Only two hours but still) This subject was dealt with some time ago on the list. Unfortunately I didn't pay much attention to it at the time (I was stil using 6.4 then). But I seem to remember some solution being presented (?) Does anyone still have it laying around in their mail? It read like a genuine fix, not a workaround... hwclock or something? Or maybe someone remembers *when* this topic was up, so we may find it in the archives? Jon
Jon Clausen wrote:
On Wednesday 04 April 2001 03:46, you wrote:
Since upgrading from 7.0 to 7.1 my system never seems to be able to set the time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try.
Me too! (Only two hours but still)
This subject was dealt with some time ago on the list. Unfortunately I didn't pay much attention to it at the time (I was stil using 6.4 then). But I seem to remember some solution being presented (?)
Does anyone still have it laying around in their mail?
It read like a genuine fix, not a workaround...
hwclock or something?
You may be referring to the fact that if you change the system time (i.e. do a 'date 040409052001.00') then this isn't reflected in a change in the system's hardware clock. Hence, when you reboot, you are back to using the old time. To set the hardware clock to the current system time, use the command: hwclock --utc --systohc if your hardware clock stores time in UTC (recommended) or this command: hwclock --systohc if your hardware clock stores time in local time. So, try setting your time to the correct time and then running one of the above commands. I'm not sure if this is the solution to the original problem though... Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
Chris Reeves wrote:
Jon Clausen wrote:
On Wednesday 04 April 2001 03:46, you wrote:
Since upgrading from 7.0 to 7.1 my system never seems to be able to set the time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try.
Me too! (Only two hours but still)
Me Too! Im in New York area, I use yast to set the timezone to new york local time the clock ends up being 3 hours off I go into the bios, verify the time, (there isnt a Greenwich mean time in my bios) Linux clock is still 3 hours + off use the hwclock setting suggested by Chris, reboot no difference verify the bios, reboot, no difference use yast to get the timezone to new york, use GMT, reboot, no difference Use yast to set the tz to Universial ;-) now my clock is only 20 min off.... I plan to adjust this in the bios -20 min fwiw... the Linux clock worked fine in 6.4 & 5.3 I suspect the data table that yast uses is corrupt of the logic it uses is flawed in other words .... its broke suggestions?? thanks rob
Rob, checkout my previous message about this - I fixed it by getting rid of /etc/adjtime that was hanging around for whatever reason. Maybe you could try that too. -Garen
-----Original Message----- From: rob [mailto:rob@cps92.com] Sent: Wednesday, April 04, 2001 6:02 AM Cc: SuSE Mailing List Subject: Re: [SLE] Can't get SuSE/Linux to set the time correctly.
...
Me Too!
Im in New York area, I use yast to set the timezone to new york local time
the clock ends up being 3 hours off
I go into the bios, verify the time, (there isnt a Greenwich mean time in my bios) Linux clock is still 3 hours + off use the hwclock setting suggested by Chris, reboot no difference verify the bios, reboot, no difference use yast to get the timezone to new york, use GMT, reboot, no difference
Use yast to set the tz to Universial ;-) now my clock is only 20 min off....
I plan to adjust this in the bios -20 min
fwiw... the Linux clock worked fine in 6.4 & 5.3
I suspect the data table that yast uses is corrupt of the logic it uses is flawed in other words .... its broke
suggestions??
thanks rob
Garen Parham wrote:
Rob, checkout my previous message about this - I fixed it by getting rid of /etc/adjtime that was hanging around for whatever reason. Maybe you could try that too.
-Garen
-----Original Message----- From: rob [mailto:rob@cps92.com] Sent: Wednesday, April 04, 2001 6:02 AM Cc: SuSE Mailing List Subject: Re: [SLE] Can't get SuSE/Linux to set the time correctly.
...
Me Too!
Im in New York area, I use yast to set the timezone to new york local time
the clock ends up being 3 hours off
I go into the bios, verify the time, (there isnt a Greenwich mean time in my bios) Linux clock is still 3 hours + off use the hwclock setting suggested by Chris, reboot no difference verify the bios, reboot, no difference use yast to get the timezone to new york, use GMT, reboot, no difference
Use yast to set the tz to Universial ;-) now my clock is only 20 min off....
I plan to adjust this in the bios -20 min
fwiw... the Linux clock worked fine in 6.4 & 5.3
I suspect the data table that yast uses is corrupt of the logic it uses is flawed in other words .... its broke
suggestions??
thanks rob
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
I also have the same problem hwclock show me the right hour instead of kde clock that is showing two hours more . I change K -> Preferences -> System -> Date & Hour and the kde clock shows the right hour , the same if I go to Yast1 - > System Adminitration _ > Set time zone to local when reboot the same problem again . -- ___ _ _ ___ | _ \__ _| |__| |___ / __| __ _ _ _ | _/ _` | '_ \ / _ \ \__ \/ _` | || | |_| \__,_|_.__/_\___/ |___/\__,_|\_,_|
Hi I just gave up and set my bios lock to match what the OS was displaying, told yast to use universial, then told hwclock to -hctosys I got it to display the correct time. There is a definete bug in my ver of 7.1 with the time and timezone I refuse to mess around with setting anymore ;-) rob ~~~~~~~~~~~~~~~~~~~~~~~~ Pablo Sau wrote:
Garen Parham wrote:
Rob, checkout my previous message about this - I fixed it by getting rid of /etc/adjtime that was hanging around for whatever reason. Maybe you could try that too.
* dizzy73 (dizzy73@connix.com) [010407 10:21]: => =>I refuse to mess around with setting anymore ;-) => How about installing xntpd and just letting that run so it queries a time server and keeps everything correct? This does work and it takes almost no effort to setup. Just install it..make sure it's set to yes in rc.config and that you have a couple of servers listed in rc.config for it to check. I did this a long time ago and forgot about it. It just works. -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
Ben Rosenberg
How about installing xntpd and just letting that run so it queries a time server and keeps everything correct?
You just have to make sure you install the update released in the last few days due to the discovery of a buffer overflow and associated remote root compromise. Brian.
Yes - it was me. There is no access to the hardware clock via the bios on my
Toshiba Satellite Pro. Several people sent answers, but the bottom line was as
follows:
Preferred: Set the hardware clock in the bios if you can
Otherwise use 'hwclock --set' option
In both cases you will then need to execute 'hwclock --hctosys' to sync the
system clock to the hardware clock. (I suppose you could reboot if you
wanted...)
Note that in both cases the it is a double dash for the option.
You can get full details (well terse details) from the man page - 'man
hwclock'
Alan
----- Original Message -----
From: "Jon Clausen"
participants (12)
-
Alan Lenton -
Ben Rosenberg -
Brian Edmonds -
Chris Reeves -
dizzy73 -
Donald Stidwell -
Garen Parham -
Geordon VanTassle -
Jon Clausen -
Pablo Sau -
rob -
wilson＠claborn.net