Re: Question : grub commands
Am Dienstag, 15. August 2006 21:57 schrieb Matteo Vescovi: Hi Hans, On 08/15/2006 02:38 PM, Hans wrote: It seems, that in last kernel 2.6.17 this problem is solved. I read the documentation of the kernel, and (as you wrote), these timers just misbehave if you have a chipset of ATI. This is the case on my notebook: ATI chipset ! Hey, since you're new to the solution of the double timing, probably you don't even know anything about the more problematic ACPI bug with the ATI Xpress 200M chipset. If you want to preserve your Turion64, pay a visit to: http://bugzilla.kernel.org/show_bug.cgi?id=5534 Well, without this kernel-command it is running fine with the newest kernel. So there are no problems any more. I additionally did hope, that this could be the reason, why my 3D-accelertion with the fglrx-river is still slow. All 3D-functions are o.k., I get the box with the rotating wheels when starting fgl_glxgears, but they are rather slow. About 50 FPS, that is speed as mesa-glx shows ! Should be 600 FPS, that would be o.k. fglrxinfo shows the correct driver-version, and glxinfo |grep direct shows direct rendering: Yes So verything seems t be o.k. with the software, and my idea was, something else, but not the driver is braking my system. You can believe me: I checked really everything, and do not know, where to look now. Additonally I tested every xorg.conf I found in the web and checked a whole bunch of settings. Sadly no success ! ATI really sux ! (This notebook I got as new of a guarantee as exchanged, I had Nvidia-card on the other noteook). And I have never heard of someone who got 3d-acceleration really fast running with a pure 64-bit-system with ATI.. Here fglrx 8.27.10 is working fine... about 480 fps, not 600 but that's not bad. Your situation sounds strange. I one time got 600FPS (ATI radeon X700), but after a restart of x-server, I got 50 FPS again. So I think, something does prevent the speed. Could you send me your /etx/X11/xorg.conf ? This way I would be able to look at the difference to mine. Thanks Hans Thats a little bit information about the background, maybe other people this could help, too Thanks for all your help ! best regards Hans Greetings. mfv -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/16/2006 03:24 AM, Robert Isaac wrote: That might change, though, now that AMD owns ATi. They _might_ release specs :-) http://news.com.com/2061-10791_3-6104655.html Mmhh, it seems like it won't change so soon. :-( Take care. mfv - -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4t2IwpmiLhhMAcoRAgFFAJ49gUfstGRTyMDxtF06DWhAnpOCZQCffsz5 xzIsLp4Ssl1UeuUtvgnwhPE= =zU0q -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Am Mittwoch, 16. August 2006 10:44 schrieb Matteo Vescovi: On 08/16/2006 06:56 AM, Hans wrote: I one time got 600FPS (ATI radeon X700), but after a restart of x-server, I got 50 FPS again. So I think, something does prevent the speed. Could you send me your /etx/X11/xorg.conf ? Here it is. I guess it's the most common xorg config file around. No big changes at all. ;-) Hope it could help. See you soon. mfv Hi Matteo, I checked, but got no success. Your xorg.conf looks like mine, and I could not find some great difference. Last I tested your configuration, and the only thing I had to change was PCI-address from 1:5:0 to 1:0:0. X started, but was the same before. So I think, that really some other is make my system slow. Anyway, I am now another step forward. I use Xorg7.0 maybe this is the reason, who knows Best regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Yes, but with the inevitable corporate shake up that will occur in ATi's management at the upper levels because of the buyout, things will have to change. It's not like their drivers or their attitude towards GNU/Linux could get any worse. http://airlied.livejournal.com/31180.html On 8/16/06, Matteo Vescovi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/16/2006 03:24 AM, Robert Isaac wrote: That might change, though, now that AMD owns ATi. They _might_ release specs :-) http://news.com.com/2061-10791_3-6104655.html Mmhh, it seems like it won't change so soon. :-( Take care. mfv - -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4t2IwpmiLhhMAcoRAgFFAJ49gUfstGRTyMDxtF06DWhAnpOCZQCffsz5 xzIsLp4Ssl1UeuUtvgnwhPE= =zU0q -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Hi Hans! On 08/15/2006 06:27 AM, Hans wrote: Sorry, I maybe did not ask correctly. It is not the problem, that the time is not shown correctly. The background is, that other timings are running in double speed, too (i.e. keyboard clock and some other). This is a known problem on AMD mobile processors and was discussed in earlier days. The solution of it, was to add disable_timer_pin_1 in the boot vcommand on grub or lilo. Now I read about adding noapictimer should solve this, too. My question aimed to an technical answer, if the commands disable_timer_pin_1 and noapictimer are doing the same, or if they both solve the mentioned problem in different ways. My hope was, someone knows, as I find there no answer in the web. Best regards Hans First of all, which kernel version are you using?? I had (as many others) the same problem with my HP laptop based on the ATI Xpress200M chipset. So, at the time of 2.6.15, I had to add disable_timer_pin_1 to the grub parameters not to have a double timing of almost everything (but you already knew that). Now, starting with ker 2.6.16, the bug about wrong timing has been corrected directly in the kernel, so using this kernel version or above you won't need the explicit definition of that param anymore. Hope it could help. Greetings. mfv -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Am Dienstag, 15. August 2006 10:51 schrieb Matteo Vescovi: Hi Hans! On 08/15/2006 06:27 AM, Hans wrote: Sorry, I maybe did not ask correctly. It is not the problem, that the time is not shown correctly. The background is, that other timings are running in double speed, too (i.e. keyboard clock and some other). This is a known problem on AMD mobile processors and was discussed in earlier days. The solution of it, was to add disable_timer_pin_1 in the boot vcommand on grub or lilo. Now I read about adding noapictimer should solve this, too. My question aimed to an technical answer, if the commands disable_timer_pin_1 and noapictimer are doing the same, or if they both solve the mentioned problem in different ways. My hope was, someone knows, as I find there no answer in the web. Best regards Hans First of all, which kernel version are you using?? I had (as many others) the same problem with my HP laptop based on the ATI Xpress200M chipset. So, at the time of 2.6.15, I had to add disable_timer_pin_1 to the grub parameters not to have a double timing of almost everything (but you already knew that). Now, starting with ker 2.6.16, the bug about wrong timing has been corrected directly in the kernel, so using this kernel version or above you won't need the explicit definition of that param anymore. Hey, this is a new information ! Cool ! My adding was of the tim eof 2.6.15 indeed. I did not know, that this is fixed now. I am running kernel 2.6.17 on my notebook Acer Aspire 5020 Hope it could help. Oh yes, it does ! Great ! Thanks ! Greetings. mfv -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Tue, Aug 15, 2006 at 06:27:32AM +0200, Hans wrote: Sorry, I maybe did not ask correctly. It is not the problem, that the time is not shown correctly. The background is, that other timings are running in double speed, too (i.e. keyboard clock and some other). This is a known problem on AMD mobile processors and was discussed in earlier days. The solution of it, was to add disable_timer_pin_1 in the boot vcommand on grub or lilo. Now I read about adding noapictimer should solve this, too. My question aimed to an technical answer, if the commands disable_timer_pin_1 and noapictimer are doing the same, or if they both solve the mentioned problem in different ways. I believe the problem occoured with ATI chipsets on laptops. As far as I have understood it, the problem is that the timer interrupts occour both on the 8259 interrupt controller, and through the apic. I believe 'disable_timer_pin_1' makes the kernel ignore the 8259 interrupt for the timer, and that 'noapictimer' ignores the apic interrupt for the timer. Since the problem seems to be getting two interrupts for every timer event, one for each interrupt method, it makes sense that disabling either one will solve the problem. It doesn't matter which one you disable as long as you disable one of the two. It really looks like a bug in the design of the chipset, although it may just be that the BIOS/ACPI tables are done wrong, which is rather common it seems. Too often the ACPI tables for windows work, but are incomplete or wrong for other operating systems. Apparently on such systems, telling linux to lie to acpi and pretend to be windows xp often solves such strange problems. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Tue, Aug 15, 2006 at 09:22:43AM +0200, Koen Vermeer wrote: /usr/src/linux-source-2.6.17/Documentation/kernel-parameters.txt says: disable_timer_pin_1 [i386,x86-64] Disable PIN 1 of APIC timer Can be useful to work around chipset bugs. Hmm, that isn't what I thought it meant. I must have misread something before. /usr/src/linux-source-2.6.17/Documentation/x86-64/boot-options.txt says: noapictimer Don't set up the APIC timer Based on that, I'd say that 'noapictimer' just doesn't use that timer, while disable_timer_pin_1 provides a workaround for the problem. I guess I'd use the latter if it works. Sounds reasonable to me. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Am Dienstag, 15. August 2006 15:14 schrieb Lennart Sorensen: On Tue, Aug 15, 2006 at 06:27:32AM +0200, Hans wrote: Sorry, I maybe did not ask correctly. It is not the problem, that the time is not shown correctly. The background is, that other timings are running in double speed, too (i.e. keyboard clock and some other). This is a known problem on AMD mobile processors and was discussed in earlier days. The solution of it, was to add disable_timer_pin_1 in the boot vcommand on grub or lilo. Now I read about adding noapictimer should solve this, too. My question aimed to an technical answer, if the commands disable_timer_pin_1 and noapictimer are doing the same, or if they both solve the mentioned problem in different ways. I believe the problem occoured with ATI chipsets on laptops. As far as I have understood it, the problem is that the timer interrupts occour both on the 8259 interrupt controller, and through the apic. I believe 'disable_timer_pin_1' makes the kernel ignore the 8259 interrupt for the timer, and that 'noapictimer' ignores the apic interrupt for the timer. Since the problem seems to be getting two interrupts for every timer event, one for each interrupt method, it makes sense that disabling either one will solve the problem. It doesn't matter which one you disable as long as you disable one of the two. It really looks like a bug in the design of the chipset, although it may just be that the BIOS/ACPI tables are done wrong, which is rather common it seems. Too often the ACPI tables for windows work, but are incomplete or wrong for other operating systems. Apparently on such systems, telling linux to lie to acpi and pretend to be windows xp often solves such strange problems. -- Len Sorensen Hi Len ! It seems, that in last kernel 2.6.17 this problem is solved. I read the documentation of the kernel, and (as you wrote), these timers just misbehave if you have a chipset of ATI. This is the case on my notebook: ATI chipset ! Well, without this kernel-command it is running fine with the newest kernel. So there are no problems any more. I additionally did hope, that this could be the reason, why my 3D-accelertion with the fglrx-river is still slow. All 3D-functions are o.k., I get the box with the rotating wheels when starting fgl_glxgears, but they are rather slow. About 50 FPS, that is speed as mesa-glx shows ! Should be 600 FPS, that would be o.k. fglrxinfo shows the correct driver-version, and glxinfo |grep direct shows direct rendering: Yes So verything seems t be o.k. with the software, and my idea was, something else, but not the driver is braking my system. You can believe me: I checked really everything, and do not know, where to look now. Additonally I tested every xorg.conf I found in the web and checked a whole bunch of settings. Sadly no success ! ATI really sux ! (This notebook I got as new of a guarantee as exchanged, I had Nvidia-card on the other noteook). And I have never heard of someone who got 3d-acceleration really fast running with a pure 64-bit-system with ATI.. Thats a little bit information about the background, maybe other people this could help, too Thanks for all your help ! best regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hans, On 08/15/2006 02:38 PM, Hans wrote: It seems, that in last kernel 2.6.17 this problem is solved. I read the documentation of the kernel, and (as you wrote), these timers just misbehave if you have a chipset of ATI. This is the case on my notebook: ATI chipset ! Hey, since you're new to the solution of the double timing, probably you don't even know anything about the more problematic ACPI bug with the ATI Xpress 200M chipset. If you want to preserve your Turion64, pay a visit to: http://bugzilla.kernel.org/show_bug.cgi?id=5534 Well, without this kernel-command it is running fine with the newest kernel. So there are no problems any more. I additionally did hope, that this could be the reason, why my 3D-accelertion with the fglrx-river is still slow. All 3D-functions are o.k., I get the box with the rotating wheels when starting fgl_glxgears, but they are rather slow. About 50 FPS, that is speed as mesa-glx shows ! Should be 600 FPS, that would be o.k. fglrxinfo shows the correct driver-version, and glxinfo |grep direct shows direct rendering: Yes So verything seems t be o.k. with the software, and my idea was, something else, but not the driver is braking my system. You can believe me: I checked really everything, and do not know, where to look now. Additonally I tested every xorg.conf I found in the web and checked a whole bunch of settings. Sadly no success ! ATI really sux ! (This notebook I got as new of a guarantee as exchanged, I had Nvidia-card on the other noteook). And I have never heard of someone who got 3d-acceleration really fast running with a pure 64-bit-system with ATI.. Here fglrx 8.27.10 is working fine... about 480 fps, not 600 but that's not bad. Your situation sounds strange. Thats a little bit information about the background, maybe other people this could help, too Thanks for all your help ! best regards Hans Greetings. mfv - -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4ic3wpmiLhhMAcoRAv2bAKDFV+VRDuuJta7VZ+/96HGtpwvHTwCgtHpX AeszKZ2a/dewc+84UwwMeRs= =mSwQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Tue, Aug 15, 2006 at 09:57:43PM +0200, Matteo Vescovi wrote: Here fglrx 8.27.10 is working fine... about 480 fps, not 600 but that's not bad. Your situation sounds strange. But my pathetic GF6200 is getting 1250fps... What gives? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/15/2006 11:23 PM, Lennart Sorensen wrote: But my pathetic GF6200 is getting 1250fps... What gives? It gives that ATI sucks! :-) That's all. Len Sorensen mfv - -- Matteo Vescovi System Administrator Studio Vescovi Progettazioni -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4kIvwpmiLhhMAcoRAmrSAJ90Saza0f5+av0xj01phi120dHsQgCgyj2L NZPIE0oL15n7V1fsfBmUtIs= =pLSk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
It gives that ATI sucks! :-) That's all. That might change, though, now that AMD owns ATi. They _might_ release specs :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote: Hello ! Just an easy question: Is there a difference between disable_timer_pin_1 and noapictimer at startup in grub ? If yes, what is the difference ? (This command is needed to get the clock running correct) regards Hans Why not use Chrony and your local pool.ntp.org servers for time? Also what happens if you don't reboot for a long time, then how do you keep your time correct? Not that it makes a difference, but those are kernel commands, I believe all grub does is pass those on to the kernel anyway. Your local search engine will be most useful here, might want to give it a go. Gnu_Raiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote: On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote: Hello ! Just an easy question: Is there a difference between disable_timer_pin_1 and noapictimer at startup in grub ? If yes, what is the difference ? (This command is needed to get the clock running correct) regards Hans Why not use Chrony and your local pool.ntp.org servers for time? Also what happens if you don't reboot for a long time, then how do you keep your time correct? Not that it makes a difference, but those are kernel commands, I believe all grub does is pass those on to the kernel anyway. Your local search engine will be most useful here, might want to give it a go. Gnu_Raiz ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. HTH cmr -- Debian 'Sarge': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote: ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. There have been kernel/chipset combinations where the system clock ran double speed. This is outside the scope of what ntp will tolerate. ntp won't run on such a system. The system has to be reasonably accurate before ntp will work with it. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Monday 14 August 2006 03:22 pm, Lennart Sorensen wrote: On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote: ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. There have been kernel/chipset combinations where the system clock ran double speed. This is outside the scope of what ntp will tolerate. ntp won't run on such a system. The system has to be reasonably accurate before ntp will work with it. -- Len Sorensen Acknowledged! cmr -- Debian 'Sarge': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Monday 14 August 2006 14:40, Mike Reinehr wrote: On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote: On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote: Hello ! Just an easy question: Is there a difference between disable_timer_pin_1 and noapictimer at startup in grub ? If yes, what is the difference ? (This command is needed to get the clock running correct) regards Hans Why not use Chrony and your local pool.ntp.org servers for time? Also what happens if you don't reboot for a long time, then how do you keep your time correct? Not that it makes a difference, but those are kernel commands, I believe all grub does is pass those on to the kernel anyway. Your local search engine will be most useful here, might want to give it a go. Gnu_Raiz ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. HTH cmr -- Debian 'Sarge': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC :) I have one machine that uses ntpd, if your curious that is what Freebsd ships with except it's not turned on by default. Regardless the hardest part was doing the .conf file, it was easy if you use the pool at ntp.org. If you really want to read up on the virtures of Chrony and why some suggest it for Debian you might want to search Debian user list, as it comes up once in a while. Let's just say that each has it ardent fans. Gnu_Raiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
On Monday 14 August 2006 03:13 pm, Gnu-Raiz wrote: On Monday 14 August 2006 14:40, Mike Reinehr wrote: On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote: On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote: Hello ! Just an easy question: Is there a difference between disable_timer_pin_1 and noapictimer at startup in grub ? If yes, what is the difference ? (This command is needed to get the clock running correct) regards Hans Why not use Chrony and your local pool.ntp.org servers for time? Also what happens if you don't reboot for a long time, then how do you keep your time correct? Not that it makes a difference, but those are kernel commands, I believe all grub does is pass those on to the kernel anyway. Your local search engine will be most useful here, might want to give it a go. Gnu_Raiz ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. HTH cmr -- Debian 'Sarge': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC :) I have one machine that uses ntpd, if your curious that is what Freebsd ships with except it's not turned on by default. Regardless the hardest part was doing the .conf file, it was easy if you use the pool at ntp.org. That was why I suggested ntp-simple as it requires no configuration. It just works! (tm) Like you, I've used regular ntp and found the configuration to be pain. :-) If you really want to read up on the virtures of Chrony and why some suggest it for Debian you might want to search Debian user list, as it comes up once in a while. Let's just say that each has it ardent fans. I'm not familiar with Chrony and will look it up. Thanks! Gnu_Raiz cmr -- Debian 'Sarge': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question : grub commands
Am Montag, 14. August 2006 22:22 schrieb Lennart Sorensen: On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote: ntp-simple couldn't be easier to install use and will keep your system time synchronized with the national time servers. I also would recommend ntpdate if you shut your system down frequently. Ntpdate will set the time on boot, while ntp-simple will keep it synchronized. There have been kernel/chipset combinations where the system clock ran double speed. This is outside the scope of what ntp will tolerate. ntp won't run on such a system. The system has to be reasonably accurate before ntp will work with it. -- Len Sorensen Hi Len ! Sorry, I maybe did not ask correctly. It is not the problem, that the time is not shown correctly. The background is, that other timings are running in double speed, too (i.e. keyboard clock and some other). This is a known problem on AMD mobile processors and was discussed in earlier days. The solution of it, was to add disable_timer_pin_1 in the boot vcommand on grub or lilo. Now I read about adding noapictimer should solve this, too. My question aimed to an technical answer, if the commands disable_timer_pin_1 and noapictimer are doing the same, or if they both solve the mentioned problem in different ways. My hope was, someone knows, as I find there no answer in the web. Best regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
