https://bugzilla.novell.com/show_bug.cgi?id=440923
User herbert@graeber-clan.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=440923#c2
--- Comment #2 from Herbert Graeber
Please attach y2logs. See
http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske... http://en.opensuse.org/Bug_Reporting_FAQ#What_does_that_NEEDINFO_bug_status_...
In general, we need YaST logs for almost all YaST bug reports; it's very rare that we can do anything useful without them.
Yes, I know, that you need y2logs, but I was not able to provide them, because the system was unbootable and an eeepc is somewhat limited with its boot capabilities. Meanwhile I have installed successfully, so the log file is not available anymore.
Also, please elaborate what error message you got. What makes you so sure the package download was what failed? Did you get errors about bad RPM signatures?
Yes, exactly, the message said, the signature is wrong.
And of course the usual suspects: Did you try "memtest" to check if the hardware is 100% reliable? Anything else suspicious in /var/log/messages?
Memtest runs without errors for over an hour. Before trying openSUSE 11.1 Beta4 I had openSUSE 11.0 installed with an atl1e driver from the BuildService and had similar problems using the package manager, but i haven't written a bug report about this, because the driver wasn't an official one. That's the reaon, why I believe the network driver is the source of the problem. But it could be the SSD, too. My next step will be to do another installation on a SDHC card, to reproduce the problem and provide a log file, if it happens again. This may rule out the SSD as the source of the problem, too. If it happens again, I will try to copy the rpm using the console and look if the retry will work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.