I just ran the auto-upgrade for F27 and I'm running into a problem with the display on the initial restart. The system boots fine until it tries to start up the x display. Then it seems to switch between several different screen resolutions (I get an auto-adjusting message on my monitor) but the screen stays black. I had been running a PVR-350 as my tv out but that just displays a green screen after the hardware initialization during startup. I attempted to disconnect the monitor through startup as that was mentioned elsewhere, but that didn't work. I've also tried copying my xorg.conf from my backup files into the /etc/X11 but I still cannot get a display to work either on my monitor or the TV. Any help would be appreciated.

Details? Such as the video card (make and model), your display(s), do you have both the monitor and TV attached at the same time?

Are you currently trying to use the 350's TV out (it was not clear from your post)? If so, perhaps mjl's post here http://mysettopbox.tv/phpBB2/viewtopic. ... 5&start=45 will help

I'm not sure of the video card, it's just the onboard video for my motherboard.

http://www.msicomputer.com/product/p_sp ... v&class=mb

The monitor is a Dell 15" LCD.

I'm not currently trying to run the PVR-350 as the tv out, this was just the initial restart after install. Based on previous installs I'd guessed I would do the initial configuration through the monitor before switching it over to the TV. Either way, the monitor just shows black, the TV shows green, and the behavior of the TV stays the same when the monitor is disconnected during startup.

I don't know anything about that video chipset, but I believe you need the S3 driver. See http://mysettopbox.tv/phpBB2/viewtopic.php?t=16385

And if/when you want to go to the 350's TV out, see mjl's post I referred to above...

Alright, I changed the driver section to read Driver "savage" but that didn't work either. Although now, instead of getting just a blank screen I'm getting the "respawning too fast" error. It appears to have originally put in Driver "via". I've tried "savage" and "s3" to no avail.

Just to recap:

In xorg.conf the relevant section reads:

Section "Device"
Identifier "Card0"
Driver "via"
Vendorname "all"
Boardname "all"
Endsection

This leads to the black screen and several mode switches, evidenced by the monitor trying to readjust.

If I change the driver to "s3" or "savage" I get the monitor flashing and then it gives the "respawning too fast" error.

It seems that the "via" driver is actually working, just that the modes are not correct for my monitor or video card, but I'm not sure about this. With the other two options X doesn't even seem to start.

Alright, I wussed out and reinstalled R5F1. It worked fine after the usual initial setup. Anybody know what might have changed in the newer version that could cause this sort of error? Thanks for all your help slow, hopefully I can get it working in the future. At the moment I can't take advantage of Schedules direct, but I guess I'll just have to work it out in the next 8 days.

Hi,

I had a similar error when I selected no to tv out. May want to retry and do the tv out yes and see if you are good to go. my manual install left a blank xorg.conf.pre350 so to bring xserver back, I copied the xorg.conf.1st into the .pre350

Mike

The problem was that I couldn't even get into the post-install setup. This happened immediately finishing the file copy from the cd. On the next reboot the display would not come up. I'm beginning to think that the problem lies in the modes for my card/monitor. It seemed to load X correctly, but the resolution/refresh rate it was running at was not visible on my screen. I tried taking out all but the native resolution for my monitor from xorg.conf but to no avail.

Any thoughts?

Can you flip to another virtual console using Ctrl-Alt-F1 and login in text mode?

Hi,

I had the same problem with an epia M12000 Motherboard (Autoinstall) - this would have also put "via" as the default driver in the xorg.conf although I didn't verify this.

CTRL-ALT-F1 doesn't work to switch to another console - I can see the screen flickering - seems to be cycling through different modes.

I haven't had time to troubleshoot further.

Ctrl alt f1 did not work to flip it to a console. The only way to gain access to the system was a ctrl alt del restart and then bring it up in single user mode.

There is one other thing I tried that I haven't mentioned. I went and grabbed the xorg.conf.pre350 file from my backup. I'm assuming this was the xorg that was used during the initial setup for R5F1, before I said yes to "Would you like to use the 350 etc...". Using this as xorg.conf ran into the same error as before, black screen, and a few mode switches. This would lead me to believe whatever is going on is something external to the xorg.conf file. What changes were made between F1 and F27 that could have effected things like this?

I don't know if this is related - I can't test right now I'm at work

http://mysettopbox.tv/CHANGELOG.txt says "Updated OpenChrome (SVN 340)"

This thread discusses lockups using latest Openchrome SVN and a possible solution http://forums.viaarena.com/messageview. ... erthread=y

Try commenting out EnableAGPDMA option in xorg.conf
I'm guessing here as I haven't tried it yet - I'm still waiting for our Telco to install our "narrowband" at home in deep dark Africa so I can't even post back tonight

I'm having the same problem on a A7V400-MX mb (vt8378). I just get a black screen. If I change the driver in xorg.conf to vesa then X works.

I think I found a clue from dmesg I get the following when using the via driver:

agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode

I'm having a similar (or identical) problem with an EPIA M10000 I upgraded from R5D? to R5F27. The symptoms seem identical, with the monitor occasionally flashing like it's trying to auto adjust, but other than that the box seemed locked up (Ctrl-Alt-F1, Ctrl-Alt-Backspace, etc. wouldn't do anything), and I was seeing a similar message when I booted into single user mode and checked the logs. Unfortunately I was very rushed to get a working system, so I just fell back to R5F1. I'm going to retry R5F27 over the weekend (once I take the time to image the R5F1 hda1 partition) and I'll try some of the options mentioned in the links above. In the mean time, has anyone successfully installed R5F27 on an Epia M10000?