i810 & i915 blank screen Intel Corporation 82845G onboard video

davimint · 06-25-2007, 11:48 PM

It's no fun since the monitor crashed for that used computer that I'm trying to get going. It's a pain switching the cables back and forth.

Quote:

you might try '$echo startfluxbox > ~/.xinitrc'

I got " Error: Couldn't connect to XServer "
I also looked at the output of running process while the screen was blank and couldnt find where gdm or x was running.

also I noticed that if I deleted the xorg.conf.new and re-ran the command "X -configure" I got this...

dlopen: /usr/X11R6/lib/modules/drivers/apm_drv.so: undefined symbol: XvRTPort
(EE) Failed to load /usr/X11R6/lib/modules/drivers/apm_driver.so
(EE) Failed to load module "apm" (loader Failed, 7)

Maybe this will help..

Also, I noticed that when I'm using the Live-cd that the i915 is used by two and drm is used by three. I tried to figure out what is not being loaded but I was unable to find the command to show me that. If I remember correctly it's one for i915 and two for drm on the problem system.

"output from Zenwalk-LiveCD"

Code:

Module                  Size  Used by
i915                   15232  2 
drm                    48028  3 i915

Anyway.. Hope this helps..

Also, If anyone would like to look at the bios settings that are available to have me check anything in there that could be causing problems, here's a link...

http://support.dell.com/support/edoc...n/syssetup.htm

bioe007 · 06-26-2007, 11:34 AM

one thing I noticed is your zenwalk xorg.conf has a much more reasonable vert refresh (did I miss a monitor change?)

Quote:

Originally Posted by zenwalk xorg.conf

### Comment all HorizSync and VertSync values to use DDC:
HorizSync 30.0 - 80.0
VertRefresh 60.0 - 75.0

Quote:

Originally Posted by posted xorg.conf

Section "Monitor"
Identifier "Monitor0"
HorizSync 30-85
VertRefresh 48-120
VendorName "Monitor Vendor"
ModelName "Monitor Model"

this could be the trouble.

davimint · 06-26-2007, 02:14 PM

bioe007,
The p780 monitor crashed for some reason as I explained in post #14 and I surely hope it not something in this computer that caused that since I'm changing my cables back and forth on my main pc with it's lcd monitor. The specs on the p780 were as you just stated and i'll edit that when I get home and try again but I think I played with those already and still have not gotten it to work. The errors on the apm that are stated in post #16 have got me worried at this point because I cant find out what XvRTPort is.

thanks....

davimint · 06-26-2007, 10:03 PM

Ok, I'm typing this from the used PC that is the cause of this very long post. The sad part is that I am typing it from a partition with a install of Zenwalk. NOT by any means knocking Zenwalk I just prefer Slackware and Linux is all about choice. So, since I know don't have to swap cables back and forth between two systems just to check something and since I've got a system working on this PC I just need to spend some time looking around to see what's going on in Slackware on this PC. Now, I'm not saying that I don't have a question or two about things so here they are.

First, why in the world is my IDE drive being called sda ????
From what I read this may be a standard that is on the way but why has Pat not gone to it.

Second, why is my boot process hanging at the following part. I read a post or two and tried the following as stated in one but it did not do any good.

Code:

append="resume=/dev/sda1 splash=silent legacy_ide earlymodules=sis"

So here is where the computer hangs during the boot process that I can not get figured out so far.

Code:

ata1.00: configured for UDMA/100
scsi1 : ata_piix
ata2.00: ATAPI, max UDMA/33
ata2.00: qc timeout (cmd 0xef)
ata2.00: failed to set xfermode (err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: qc timeout (cmd 0xef)
ata2.00: failed to set xfermode (err_mask=0x4)
ata2.00: limiting speed to UDMA/33:PIO3
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: qc timeout (cmd 0xef)
ata2.00: failed to set xfermode (err_mask=0x4)
ata2.00: disabled
scsi 0:0:0:0: Direct-Access     ATA      WDC WD400BB-75DE 05.0 PQ: 0 ANSI: 5
SCSI device sda: 71505528 512-byte hdwr sectors (36611 MB)
sda: Write Protect is off

So, I'm off to install Slackware again and maybe since I have at least one linux distribution working maybe I can get my beloved Slackware going.

thanks to everyone so far....

Nikosis · 06-27-2007, 01:40 AM

Did you try to run xorgconfig and build everything from there. Personally I don't like xorgsetup (never done any good in my case).If you know your horizsync and vertrefresh there is no way to crush your lcd and try use vesa driver (worked for me many times)

cwwilson721 · 06-27-2007, 02:35 AM

In my dri post (link in sig), the xorg file I have works fine with that chipset. (I'm using the same one right now). The xorg.conf file is commented so you can change what is needed (like mouse and stuff. Leave the video part as is)

Give it a shot.

nx5000 · 06-27-2007, 06:13 AM

Quote:

First, why in the world is my IDE drive being called sda ????

On Fedora7, all disks are now called sdxx.
A bit misleading I agree. I guess its udev that does this. I don't have this on my debian with same kernel as FC7.

Quote:

Also, I noticed that when I'm using the Live-cd that the i915 is used by two and drm is used by three. I tried to figure out what is not being loaded but I was unable to find the command to show me that. If I remember correctly it's one for i915 and two for drm on the problem system.

Probably the dri.

For your tests, I would disable dri first.
When you get your screen running, try back the dri.

Quote:

I got " Error: Couldn't connect to XServer "
I also looked at the output of running process while the screen was blank and couldnt find where gdm or x was running.

killall -9 X
You don't even need .xinitrc, try this:

Code:

xinit /usr/bin/xterm -- -ac :0

That's the minimal way of starting X, no WM, no security.
Be sure to not have anything running on display :0.
Otherwise change the above to:

Code:

xinit /usr/bin/xterm -- -ac :1

Then you can't use dri on both displays anyway.

davimint · 06-27-2007, 07:42 AM

Progress at last!

late last night I ran into the command xorgcfg -testmode which gave me that funny Window-Manager look, I can't remember the name of it but I used it the time I was setting up gentoo.

Anyway I did as you asked "nx5000" and got the xterm shell.

One, I made sure that "dri" was not in my xorg.conf

Two, I killed all the process.
Note: No process running, I also checked this with "ps -aux | grep x" and
only got some /sbin/agetty process...

Three, copied my /etc/X11/xorg.conf to /etc/X11/xorg.conf.old. copied my /root/xorg.conf.new to /etc/X11/xorg.conf.. The one slackware generated has got the vesa driver in it for some reason.

Four, ran "xinit /usr/bin/xterm -- -ac:0" and got a error about xterm is not in path but did show me the light "usr/X11R6/bin/xterm"
note: I'm not 100 percent positive that it told me where it was.

five, ran the new command "xinit /usr/X11R6/bin/xterm -- -ac:0" and I got Xterm in a little window ( top left hand of screen ) and my mouse...

Well that's a big improvement, but what does all this mean ?

So, now what 'DO I NEED TO CHECK" with my newbie self. I feel like it's my first day using linux.

Thanks again.

trashbird1240 · 06-27-2007, 08:14 AM

Sorry if I missed this: are you using a 2.4 kernel? I totally failed to get X going with a 2.4 kernel on an i810 chipset.

Use 2.6.17.13 and INSTALL THE MODULES! For the love of kernel, the modules, man!

Joel

davimint · 06-27-2007, 12:48 PM

This system has been tried with 2.4 and 2.6 stock kernels from Slackware with the correct module packages installed. Slackware for somereason has failed to see/configure the 845g/gl video adapter. On this same machine Zenwalk picked it up and works fine. This is a used machine that I picked up from a co-worker that is suppose to be a good PC but it's been setting up for a long time. It's not my main PC in my house because I have two others and both have Slackware installed on them one with a nvidia gpu and the other with a santa-curz video card. I could have purchased a video card for this box but since I don't know anything about it I didn't want to spend the money. This is the only time I have ever had any problems like this with Slackware on the install other than tweaks in the xorg.

Now, back to post #23...

Since I know that the Xserver will work, what do that tell me about the install on this machine. Where should I being to look or which is the best way to see what's going wrong. I've already checked the xinit in this post or would it be something in the gdm that may be the problem. Maybe it's in a path how would I check that. I just do not know where to start..

Remeber that post #23 is where I finally got something to work.

thanks again.

onebuck · 06-27-2007, 01:33 PM

Hi,

I've read the thread. No where did you say that you chose a environment or window manager. If you 'man xwmconfig' you will get the reasoning.

excerpt;

Quote:

xwmconfig provides a menu of the window managers available on the
machine so that you may choose one of them to use when X is started
with "startx".

When run by root, it sets the symbolic link /etc/X11/xinit/xinitrc,
which selected the default system-wide window manager to use for X, and
also creates a /root/.xinitrc file with the same window manager
selected (perhaps suitable to move into /etc/skel/).

When run by a non-root user, xwmconfig writes out a $HOME/.xinitrc
file, allowing the user to choose their own default window manager
(possibly overriding the one chosen as a system default).

Your test shows that the X system is working, so select a WM or environment. If you want something lite then select XFCE.

You should also check some of the links in my sig, especially link #1 in the Code: section to get some good information that will assist you.

davimint · 06-27-2007, 05:30 PM

onebuck and all who have posted
Sorry that I didn't state that anywhere but it's been done about 100 times on the first, second, and third install. The first install I used the 2.6 smp kernel from slackware on this p4 machine and from what I've read about the 2.6 kernel from pat's notes that actually on current it may run better. On the second install I used the 2.6 generic (non-smp) kernel and also tried the ide stock kernel. On this third install it was done with the generic non-smp kernel (2.6) but I didn't waste time on kde I just installed the normal window-managers. Now, strangley enough after using the command "xinit /usr/bin/xterm -- -ac:0" everything is working. I really think this machine is possessed. I did nothing this afternoon other than get home and move the monitor cables from one machine to the other due to the fact that the dell p780 monitor went bad the other night. Now.. I don't want to jump up and down yet because sadly enough I'm going to dump everything and reinstall without Zenwalk on this PC and with slackware including kde. I will post back for everyone to know...

Now, I printed off all the slackbook info and other info today. I'm fixing to save the xorg.conf files to my usb-stick so I will have a good one for sure.

All that being said.. I would just like to thank everyone at LQ who has helped and posted on this thread and I wish I could say that I found the stupid thing I did so someone else would not make whatever mistake if any I made but at this point I just can not say that. I don't know what went wrong so I'm going to start over again on a fresh install and see how it goes. Maybe all will be well on this install.

Again, thanks ALL

davimint · 06-27-2007, 07:32 PM

WORKING & SOLVED ( I Guess )

I just wiped hard-drive and installed slackware again. I must say there was still a slight problem but thanks to all the folks here on LQ who have helped me it's working now.

If anyone would be interested in what I had do here's what I did and maybe a few could post ideas as to what's getting mixed up on the install...

After the install I checked my xorg.conf and found that it was configured with the vesa driver so I discard this configuration.

Used the command "X -configure" and checked it to make sure it picked up the i810 card driver which it did and set the correct DefaultDepth and Modes for my monitor.

Moved the newly created xorg.conf to it's proper place and used the command "xwmconfig" & selected fluxbox. At this point I wondered if it would work so I typed startx after a second or two of heavy thoughts and it failed.

I though well last time it worked with twm (window manager)so maybe that's the trick for some reason. So I selected it from the xwmanger and guess what it worked like a charm. I exited and select fluxbox and now it's working like a charm.

Can not explain why but at least I've learned some new things to check..

Once again, thanks

onebuck · 06-27-2007, 07:43 PM

Hi,

I would suggest you use Slackware 12 RC2 with the default kernel. This should work for you.

Or you could use Eric's script; mirror-slackware-current.sh to download current and create install cdroms/dvd.

davimint · 06-27-2007, 10:18 PM

Yes, I keep current on my main linux-box and I like alienbob's scrip but I've been working on one just to learn a little for myself. I though I would wait on this old box till I get the official from slackware when they start shipping them. I wanted to support Pat and the guys for their effort. Beside's since the monitor I was using for that box died I am kinda stuck till I make a decision on monitors. I've been thinking about a new "nvidia" card and a nice wide screen 22" monitor for my main PC. It's my 25th wedding anniversary in April so I guess I can start giving a hint since I have been given my hint or two.

Anyway thanks for the help.

david