On Thu, May 24, 2007 8:32 am, Eberhard Roloff wrote: >> When I type tail /var/log/messages I don't see anything strange. > > Well if it turns out to be non-X related, i.e. if your hardware > freezes > in runlevel three, as well, I would try to do it the old fashioned way with disabling certain kernel parameters like "noacpi" and similar. Ex. http://www.faqs.org/docs/Linux-HOWTO/BootPrompt-HOWTO.html
I don't know if I've run in runlevel3. I really wouldn't be able to do anything there, as my work is all GUI. > > Also you might google for other users experiences with Linux on your hardware. > > regards > Eberhard, who concludes (once again, just for me and myself!) that brand > new hardware is not the ideal place for Linux, especially not if the hardware in question is a notebook. I wouldn't have done it, except I have a buddy with the same notebook. He's had it for about six months and runs SLED. I figured it would be safe to run openSUSE. Dunno. I've been running Amarok now for over an hour with no issues. I did download the latest nVidia driver, but am a bit fearful of loading it in case I mess up. Also I believe I'd have to hand-edit my xorg.conf file. Not something I'm inclined to do. At this point, the machine locked up. I am still able to SSH into it from my XP box. Looking at the messages I see: login as: root Last login: Thu May 24 11:18:42 2007 from 10.3.15.90 Have a lot of fun... jabba:/home/kai # tail /var/log/messages May 24 11:48:12 jabba zmd: ServiceManager (ERROR): Service refresh failed for 'SUSE-Linux-10.2-Updates': Failed to parse XML metadata: Can't add repository at http://mirror.mcs.anl.gov/suse/update/10.2: Unknown source type for http://mirror.mcs.anl.gov/suse/update/10.2 May 24 12:00:26 jabba sshd[5419]: error: PAM: Authentication failure for root from 10.3.15.90 May 24 12:00:27 jabba sshd[5419]: error: PAM: Authentication failure for root from 10.3.15.90 May 24 12:00:30 jabba sshd[5419]: Accepted keyboard-interactive/pam for root from 10.3.15.90 port 3096 ssh2 jabba:/home/kai # Nothing there appears out of the ordinary. In fact, the machine is obviously running. Looking more like an x.org issue, eh? -- k -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
