Re: 9.2DVD install for AMD64 fails...

From: David Wright (david_c_wright_at_hotmail.com)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 08:45:03 +0100

marko wrote:

> I've used SUSE in the past and I'd love to be among the SuSE users now
> that its come so far (and with all the good things you hear about 9.2).
> I downloaded that DVD that supposedly has both i386 & AMD64 (aka
> x86_64) arch's on it and proceeded with the install on my new Abit AV8
> Athlon 3400+ system. It gets all the way through installing packages
> and rebooting to do some final configuration and then when it says
> click Finish and you can login... the screen goes black and the
> monitor's LED just flashes meaning its not getting any signal. My
> keyboard's Num Lock LED can be turned on/off, so the machine is in some
> type of stasis (and not locked up). Would it mean anything that I have
> an LCD screen? I've seen some mention of that before...
>
> I gave up after a couple of minute's wait; maybe I should wait longer
> for it come back? I tried rebooting and after seeing all the bootup
> messages, the screen goes into the same type of state. Very
> frustrating. I've seen some entries in newsgroups regarding this same
> issue but no resolution. Maybe somebody has come across some
> resolution since then?

I agree with Bill, it sounds like when you set up the graphics, for some
reason it picked a scan rate that the monitor won't work with. I have 3
machines with LCD's and they only respond with refresh rates between 60 and
73Hz.

I know when I booted Knoppix on one machine, it defaulted to 90+Hz and the
monitor displayed the screen correctly, but had a huge OSD window in the
middle of the display telling me to adjust the scan rate down, the other
monitors wouldn't cope with that and just went to sleep.

Boot in failsafe or to a command line (try pressing ALT+CTRL+F1 to get to a
console), log in as root (or as user and su to root) and edit the x86conf
file and adjust the scan rates manually (or try Sax2 from the command line
to do it with a GUI).

Dave

Relevant Pages

  • Re: [SLE] how to start the gui?
    ... > I've only ever run SuSE linux and it always was starting the KDE gui. ... > I can login, and did so as root, then nothing else happens. ... I'm lost at the command line for the most part. ... It's probably choking on the new monitor. ...
    (SuSE)
  • Re: how to monitot that an aoolication as NOT started as scheduled.
    ... The calls to be made are in a database and their call time, number of calls made until response and succes or failuer of reacing the client is logged in the table, so one thing coming to mind is running a report at regular times a few minutes after the process is supposed to be started and counting if there have been more than a few calls started, this would indicate successfull start of process, if no calls were started 10 minutes after normal startup time, then send a report to a numberof responsible people in the organization warning of possible failure to start. ... Since your process requires no user interaction why do you not have it start as a service so you don't have to worry about someone rebooting the machine. ... You could set up a system to monitor it using remoting, but I'm not familar enough with it to give you a direction. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: List-based login screen?
    ... the password from the small yellow post-it on the monitor. ... authentication server) barf on the disk, and on rebooting, fsck discovered ... no place for the yellow sticky note. ... loader took me straight to a password prompt. ...
    (alt.os.linux)
  • Re: Please help with fc2 / screen problem!
    ... > I've spent the last two nights rebooting and reinstalling Fedora Core 2, ... > Installation is on a clean disk and will run fine. ... > my monitor is not recognized by the installer. ...
    (comp.os.linux.setup)
  • Pls help newb with hardware setup problem @fc2
    ... I've spent the last two nights rebooting and reinstalling Fedora Core 2, ... Installation is on a clean disk and will run fine. ... The first problem I encouter is that my monitor is ...
    (comp.os.linux.hardware)