Hello,

 

I went to install OpenSUsE 10.1 beta6 on my latitude d500 (to test another
bug) when it hard crashed during setup. It just totally froze at the
graphical installer in the middle of installing packages (it was at 100% for
installing hplip), I couldn't move the mouse, I couldn't do ctrl + alt + F1,
there was no hard drive access, I didn't see a kernel panic message, etc. I
was doing a HTTP install, more details below.

 

I would like to know if there is anyway I can get more information about
what happened so as to help solve a potential bug. I could go ahead and try
to install again, but that would delete any install logs that might contain
information about what went wrong, and it might succeed and thus not
reproduce that log info. I looked through /var/log/YaST2/y2logRPM (it didn't
report hplip as being installed) and y2start.log, but they don't seem to
indicate any problem.

 

People at freenode suggested I run a memory test and the sisoft Sandra burn
in test (I have windows XP on another partition), but both of them completed
successfully. Furthermore, I can't ever remember a time my computer crashed
on me, unless I was using ndiswrapper or hot swapping stuff I shouldn't
have. I have done stress intensive stuff such as copying large amounts of
data, using the 10/100 NIC near 100%, using the wireless card (which
produces a lot of heat and is next to the CPU) while using the CPU a lot, or
playing games (full CPU and integrated graphics usage.) It would have to be
a very big coincidence if it just happened to crash for hardware reasons
this time. I find it very unlikely that it overheated, like was suggested on
IRC, since the wireless card couldn't even have been used, it's a totally
unsupported Broadcom.

 

This install was done by downloading the CD ISO's, using makeSUSEdvd to
combine them into one installation source (makeSUSEdvd -s -i), and then
using the mini iso to point to that source, shared over HTTP from another
machine on the same LAN. I was using my Intel pro 100 VE for this. I have
used makeSUSEdvd on 10.1 beta6 before successfully, on an x86_64 source that
was burnt to a DVD, and it worked fine.

 

It did have some trouble trying to access it over SMB, but then I put the
source on HTTP and it was fine.

 

I did a pretty custom package selection (again, it crashed while installing
hplip), and I did have it format the partition it was installing to with
reiserFS.

 

My system is a latitude d500, with a Pentium-m 1.3, 384 megs of ram, intel
855GM, a Hitachi IC25NO40ATCS05-0 hard drive, an LG CRN-8245B CD-ROM drive,
and an Intel pro 100 VE with a MS intellimouse optical plugged in.

 

Again, if anyone can give advice on identifying the problem through data on
the partition, I'd appreciate it. If that is impossible, I'd like to know
that too so I can try again. I'm just trying to do whatever I can to help
identify what is probably a bug.

 

-Mike

Reply via email to