Bug#548128: Similar Problem
* Frans Pop elen...@planet.nl [2009-12-14 21:53]: Martin has just tested a modified version of this program (which first reads the system date and only sets it to the epoch if the current value is earlier). I've committed this and will upload clock-setup. Does not necessarily need to be included in the upcoming release. I've tested d-i on my Thecus N2100 with a bogus date and it now works correctly: Jan 1 00:00:00 clock-setup: System date is before 1-1-1970; correcting... Jan 1 00:00:00 clock-setup: System date has been set to 1-1-1970. Dec 16 19:50:40 clock-setup: Wed Dec 16 19:50:40 UTC 2009 Dec 16 19:50:40 clock-setup: rdate: adjust local clock by 1260993039.995376 seconds Frans, can you put this fix into lenny too? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Saturday 12 December 2009, Frans Pop wrote: So, if the problem is simply that rdate fails when the current system time is before the epoch (1-1-1970), how about we include a trivial command to set the date to the epoch before calling rdate as a workaround until rdate gets fixed. Martin has just tested a modified version of this program (which first reads the system date and only sets it to the epoch if the current value is earlier). I've committed this and will upload clock-setup. Does not necessarily need to be included in the upcoming release. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Friday 11 December 2009, Frans Pop wrote:
On Friday 11 December 2009, Frans Pop wrote:
And that looks to be the issue described in this bug report:
http://bugs.debian.org/502336
I've just done some debugging in rdate of this problem, and it looks to
be a calculation bug in rdate (either due to incorrect handling of
overflow or maybe endianness). See the BR linked above for details.
So, if the problem is simply that rdate fails when the current system time
is before the epoch (1-1-1970), how about we include a trivial command to
set the date to the epoch before calling rdate as a workaround until rdate
gets fixed.
The attached code does the job.
/*
* Copyright (c) 2009 Frans Pop f...@debian.org
* Licence: GPL version 2 or later
*/
/*
* set-date-epoch.c: Set the system date to the epoch
*/
#include sys/time.h
#include err.h
#include time.h
int
main(int argc, char **argv)
{
struct timeval new;
new.tv_sec = 0;
new.tv_usec = 0;
if (settimeofday(new, NULL) == -1)
err(1, Could not set time of day);
return 0;
}
Bug#548128: Similar Problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On My Apple G4 Tower using the net install disk the install hangs at 1% and the console read out displays a similar thing. There seems to be problems with untrusted packages in the console. I have tried to install many times but face the same problem. I currently have no system on the G4 and can't seem to boot other install dvd's or cd's. I left it running over night before i found about the alt-f4 thing and saw that it was hanging on this yes no question I am decidedly stuck as to what to do. A lot of the packages seem to have expired keys is this a problem with the mirror? I'm using the standard uk debian mirror but have had the same problem no matter what options I choose. In expert mode (I am no expert) or standard install or install video=ofonly (I had problems with the video on previous etch install I can get the installer running but it always hangs. I can skip the installing of other software on expert install but it has left me with a bare system with virtualy noting on it and I am unfamiliar with the commands to build a system from scratch on the command line. Mikko -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLIlRpAAoJEJc4nKbiWDRBlQQH/26lcwOd6HZu2xNwiQzQWtMw iOw9l82ulokQm99N7ODsV7c67cIWgFGkuoDk4XY8h+8Es1zgpvF+vqVllwBfi5LU APia/jno8Ewe0n9k2m+wKB/3thxsymkTfsl76zUvg8Y8SNFPFiXXU4r5AmatiNke lZ0z6F3SFDEz7O6kuySrfalMzRvFq6Z0/nrCaqCezyumHDGPVlYL6yaiaC058g4J 9Y2JcILoY9EcAtG4RnUnRiPmAhHoHa/1NYMuBCiTfMTcS/ME7I9Byb4AteuBfPPr OG5dd8XU6qY9vKWwzv0RwxlbrrGkpgvJ1JBEK+t4PQO5oBwv0AgnLnFm08O6hME= =MzHH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Friday 11 December 2009, Mikko Eley wrote: On My Apple G4 Tower using the net install disk the install hangs at 1% and the console read out displays a similar thing. There seems to be problems with untrusted packages in the console. I have tried to install many times but face the same problem. I currently have no system on the G4 and can't seem to boot other install dvd's or cd's. Can you send us the syslog for the installation (gzipped)? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/12/2009 15:00, Frans Pop wrote: On Friday 11 December 2009, Mikko Eley wrote: On My Apple G4 Tower using the net install disk the install hangs at 1% and the console read out displays a similar thing. There seems to be problems with untrusted packages in the console. I have tried to install many times but face the same problem. I currently have no system on the G4 and can't seem to boot other install dvd's or cd's. Can you send us the syslog for the installation (gzipped)? If I knew how to find it and most importantly send it to you. The system is bare at the moment and installing gnome and xfce have failed. Not sure what commands/programs to use for sending the file. I don't have any thumb drives to get the file off the machine and onto my laptop, any ideas welcome. -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLImMOAAoJEJc4nKbiWDRB19oH/039FpN+l8SbXOsR3NzfPacR MQKOL+TbSygtR13xm2pU1QN7ZzSP4xYYhxmtHugRusQQJ3gB1OpSkGL62JR5p2S5 5P15k5o6Xt3wBZ8fTsrabaC7ftaxH0LmJn3tuf9kXH2XRqudQn/HKH1b6vRz36q3 fLmyZhRfs3Q7JEiuPrJr6dfE7me1Djcx83sBWWK6qmcYdAbWZrbwvkDFvbAXYl3V Tw7dly+UfTPqBerpn0IXQ+XFTBIxDeHOjOCOXhapm4xvNjjzLvHbLBiztLNW61yE KMvXCm7LYqOXQSENPfR35boT53t+lhuy6e5fay3OMaZVbjfFNZ8Sr3nOVUfCDW8= =I17q -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Friday 11 December 2009, Mikko Eley wrote: If I knew how to find it and most importantly send it to you. The system is bare at the moment and installing gnome and xfce have failed. Not sure what commands/programs to use for sending the file. I don't have any thumb drives to get the file off the machine and onto my laptop, any ideas welcome. So you do have a second system. If you have a network connection between them, the following will work. Start the installation. After you've set up networking (for example at the start of partitioning), use the go back option to go to the main menu of the installer. Select the option Save debug logs and choose the option to start a web server. Using the instructions in the next dialog, you should then be able to connect to the powerpc box from your laptop. After that continue the installation until it hangs. At that point, use the browser on your laptop to download the syslog file. Another option is to do the installation in expert mode and select as extra component the openssh-client-udeb. Then, when the installation hangs, switch to a debug console on VT2 and use 'scp' to copy the file to your laptop. If all that does not work, you can also manually copy the last 20 lines or so from the VT4 display. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Friday 11 December 2009, Mikko Eley wrote: web server trick worked a charm syslog is attatched. Thanks for the tip I didn't know debian could do that. No problem. Next time please gzip large files before sending them though (otherwise you run the risk we never see them because our mailing list rejects the mail). The log shows a bunch of probably related problems. The first is the huge number of messages 'implausibly old time stamp 1904-01-01' while installing packages. It is possible that the wrong system date/time is the cause of the untrusted packages error because GPG needs a reasonable system time. So, first question is: is the hardware clock of your system set correctly? But normally at least the system time should get updated [1] during the installation. However, that fails here: kernel: [ 197.895382] warning: process `rdate' used the deprecated sysctl system call with 1.40. clock-setup: rdate: Could not set time of day: Invalid argument And that looks to be the issue described in this bug report: http://bugs.debian.org/502336 So, to solve the installation failure you will need to set your hardware clock to a reasonable date, assuming your systems BIOS/firmware allows you to do that. You can then retry a full installation. If that does not work there is another workaround, and that is to boot the installer with the option 'debian-installer/allow_unauthenticated=true'. But it really would be better to have the clock set correctly (assuming that is the cause of the GPG failure). Cheers, FJP [1] The hardware clock should also get updated, but only at the very end of the installation and I've no idea whether that actually works on powerpc. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
Frans Pop wrote: It is possible that the wrong system date/time is the cause of the untrusted packages error because GPG needs a reasonable system time. Why isn't base-installer's setting of --ignore-time-conflict avoiding this problem? -- see shy jo signature.asc Description: Digital signature
Bug#548128: Similar Problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/12/2009 19:38, Frans Pop wrote: On Friday 11 December 2009, Mikko Eley wrote: web server trick worked a charm syslog is attatched. Thanks for the tip I didn't know debian could do that. No problem. Next time please gzip large files before sending them though (otherwise you run the risk we never see them because our mailing list rejects the mail). The log shows a bunch of probably related problems. The first is the huge number of messages 'implausibly old time stamp 1904-01-01' while installing packages. It is possible that the wrong system date/time is the cause of the untrusted packages error because GPG needs a reasonable system time. So, first question is: is the hardware clock of your system set correctly? But normally at least the system time should get updated [1] during the installation. However, that fails here: kernel: [ 197.895382] warning: process `rdate' used the deprecated sysctl system call with 1.40. clock-setup: rdate: Could not set time of day: Invalid argument And that looks to be the issue described in this bug report: http://bugs.debian.org/502336 So, to solve the installation failure you will need to set your hardware clock to a reasonable date, assuming your systems BIOS/firmware allows you to do that. You can then retry a full installation. If that does not work there is another workaround, and that is to boot the installer with the option 'debian-installer/allow_unauthenticated=true'. But it really would be better to have the clock set correctly (assuming that is the cause of the GPG failure). Cheers, FJP [1] The hardware clock should also get updated, but only at the very end of the installation and I've no idea whether that actually works on powerpc. Couldn't set the time in the BIOS after some searching on the net for instructions. Nor did the work around work BUT I booted the partially installed system and managed to use the date command in root. It is now past the hang and installing away. Thank you for your help! The machine was sitting in storage for some time and I think the battery on the motherboard died. If I have more time/date problems that will be the first thing to get replaced. Again Thank you, Mikko, Now I just have to get wireless working, my arch nemesis in Linux so I can stop tethering it to my laptop. I suspect the card isn't supported so another purchase may be a fully Gnu compatible wireless card... -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLIq6HAAoJEJc4nKbiWDRBj9gH/ivxwDha1SxLreEAv7i0U+2c aJxCuvvzvLDYqk/EHOSmvlwmtr6h2r3OjwtuqwlprxaozNLPQmpuGycnqsRdo0zj T0j9yYP2jd+nSw73DZIOoiTUyaGjvXNP6QeuRJRCCP3azGg+ZA6fG9jOOdn/3NSs sqe57L1pQ95hw4ritXYLvDven8/cSGhwuD6nFFm6kUZsM+9tzl0CcCkSyC1dgvdP MAyCoE3rF2ONG9cQ8LsXVrFaNG8/ZZZfhCGjF4oeYJLAirrAxt1z55bHt6/G/9dP sugnRGtc19VoiOwqfkwzadojFWHJDYWj5YsKCIwIySb3dwmWcms63uOs0+EvBAw= =Xdxn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
On Friday 11 December 2009, Frans Pop wrote: And that looks to be the issue described in this bug report: http://bugs.debian.org/502336 I've just done some debugging in rdate of this problem, and it looks to be a calculation bug in rdate (either due to incorrect handling of overflow or maybe endianness). See the BR linked above for details. On Friday 11 December 2009, Joey Hess wrote: Why isn't base-installer's setting of --ignore-time-conflict avoiding this problem? No idea. But I'll let someone else look into that aspect. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548128: Similar Problem
Quoting Frans Pop (elen...@planet.nl): No idea. But I'll let someone else look into that aspect. Well, that issue was really hairy..:-) Wouldn't it be worth documenting it in some way in either the documentation or the errata file? signature.asc Description: Digital signature
