|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| ARCHIVES - 64bit Environments Running an AMD64 or Xeon system? Of course Linux is ready for it - but if you have any questions feel free to ask in here! |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I have SuSe 10.2 installed on a box with
Intel Duo Core E4500 @ 2.20 GHz Onboard ASUSTek Network card 82788 vender Marvell Technologies (sky2 driver) Intel ® Q33 / Q3 / G33 Graphics Controller The maichine was freezing up overnight and the keyboard and mouse were dead. The box wasn't responding to pings. When trying a remote login using SSH the attempt never timed out, but a login was never offered. I turned off all power management functions and the next morning it was frozen again. I tried turning off the screensaver but that didn't make a difference. I unplugged it from the net and it ran for three days straight. Then I plugged it into the network and worked all day long. The next morning the thing was locked up again. I am bluffed. If that is really hardware incompatibility could it be that sky2 driver? Often it boots like below and then it I ifdown and ifup the eth0 a few times the DHCP deamon catches the IP. Starting service kdmdone lo lo IP address: 127.0.0.1/8 done eth0 device: Marvell Technology Group Ltd. Unknown device 4364 (rev 12) eth0 configuration: eth-id-00:1d:60:b2:1d:7c eth0 (DHCP) . . . . . no IP address yet... backgrounding. waiting Waiting for mandatory devices: eth-id-00:1d:60:b2:1d:7c __NSC__ 14 12 11 10 9 <notice>checkproc: /opt/kde3/bin/kdm 3148 8 7 6 4 3 2 1 0 eth0 device: Marvell Technology Group Ltd. Unknown device 4364 (rev 12) eth0 configuration: eth-id-00:1d:60:b2:1d:7c eth0 dhcpcd is still waiting for data waiting eth0 interface could not be set up until now failedSetting up service network . . . . . . . . . . . . . . . .failed |
|
|||
|
I assume you triple-checked your installation media and drives? I don't really have a similar system (BioStar mobo with Athalon 64x2 +2GB memory, 2x300GB SATA drives and 2x250GB PATA drives) but I've come across this kind of behavior. I have run Linspire, WinXP, Suse 10.0, 10.1, 10.2, 10.3 (I ran each for about a year or two, and each reinstalled several times over those years) so you can imagine that I know how my system hardware behaves in general. Right now I have WinXP, 10.1, 10.2, and 10.3 installed. 10.2 suddenly did this freezing thing last summer, but has been perfectly stable since then after a reinstall.
There seem to be cases where either a proper install didn't get done or some strange corruption occur. 10.3 was flakey right from the first install. It would just freeze. I have two DVD's and one of them won't reliably install games, and it turned out that I had installed 10.3 from that drive. So I reinstalled it and it's been good since then. Geeze, I sound like a windows person... "reinstall, reinstall..." :lol: Patti |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|