i810 not working in 12.0 ("detecting sil164")
I have an integrated Intel 855GM and had been using the i810 driver with DRI and everything in 11.0. I try this in 12.0 and get some screen flickering, then a blank screen which I then ctrl+alt+backspace out of. My xorg.conf:
Code:
Section "Module" Code:
(WW) intel(0): Bad V_BIOS checksum Any suggestions would be appreciated. |
Why do you have two device sections? One for vesa, and one for i810. You could try getting rid of the vesa device section.
|
Because VESA is what works. I keep it there so I can get X working at all, by changing the Device in my Screen section. Simply having an unused Device section shouldn't make the used one throw errors.
Just to be sure, I removed it and still get the same thing. In case it helps, it does this both with the huge-smp-2.6.21.5 kernel as well as my custom 2.6.21.5 kernel. |
Quote:
Code:
upgradepkg --reinstall xf86-video-i810-1.7.4-i486-1.tgz |
Well, thank you for that, it worked. This leads me to some questions:
1 - How was I supposed to know that a package interferes with another package? I'm suddenly paranoid about the order in which I install things. 2 - Why does the intel driver want to replace the i810 driver? Is it supposed to be the new version of it or something? And if so, why are both included then? And who do I notify that it breaks things? |
I've got two of four machines with the i810 in them and until tonight I never found this problem. I always get them working but its a pain. I checked both & reinstalled the i810 but still had to work my magic to get them going again.
I sure wish someone could get this figured out and get "Pat and the Crew" to update it in the changelogs. There's got to be something going on with this and not just buggy i810 cards. |
Quote:
X will just read those sections but not use them as long as they aren't defined in section screen to be used :) |
I've got Intel 845G integrated graphisc and after fresh installation of 12.0 got the same problem (sil164). Solution was to uninstall xf86-video-intel and then reinstall xf86-video-i810, just like you said above. I found that, when uninstalling xf86-video-intel, the man page for i810 is lost (and that directed me to reinstall xf86-video-i810 ;-)). So there truly seems to be interference between i810 and intel.
|
I have been remiss...
...in my duty of thanking you for the post below:
Quote:
Thanks for this post! Blessed be! Pappy |
does anyone know exactly why this change was done? Earlier it was all fine ...
|
Quote:
Slackware-12 cannot make that same claim. In order to get X-windows working, I had to run xorgconfig to set up the basics in the xorg.conf file. Then I have to manually edit xorg.conf and make sure that VertRefresh=60. Xorgsetup is right out since it doesn't set up a VertRefresh line in the xorg.conf file. According to Pat Volkerding in the official release announcement for Slackware-12: Quote:
Fortunately, this problem was known. I can just imagine how frustrating setting up Slack-12 would have been without this thread. It took a little time for me to finally figure out exactly what was happening when I tried to start KDE while the VertRefresh problem was a problem. Now that I know, it takes me a lot less time to setup this machine properly...having done so four different times now just with Slack-12. Blessed be! Pappy |
Xorg 7 is certainly not new ... it is pretty old. Infact, slack11 has a hack to fix ATI cards on XorgR6 (in the extras section) and there is a note there saying "hopefully we will move to modular X soon where such hacks won't be needed)
|
Quote:
Quote:
The good thing is once you get passed the cure listed in this thread, and a few others listed in other places, Slackware 12 is just as stable as Slackware 11. The even bigger plus is once you get hal sorted out and functional, Slackware 12 detects all media, from CD's to USB zip sticks. Blessed be! Pappy |
Quote:
Another user reporting the same problem. The intel driver would not work with my system, all I could get was a slow fade to white. Reinstalling the i810 driver as above fixed mine as well. |
I added this post to my DRI post, with the attendant solution.
Since I'm not currently using an Intel Video Chip in any of my Slackware boxes, this has slipped by me. A question: Was the issue caused by a "clean install" of SW12, or was it an "upgrade" from a previous version (11,10, -current, or whatever)? |
It was a clean install of 12. I haven't yet installed 12.1 on the laptop with the Intel chipset, so I don't know if the issue is still there, however.
|
Mine was a clean install also, I swapped hdd's removing my older slackware install and starting with a blank drive.
|
Seems like a boo-boo in the install scripts somewhere.
As I like to say: Poop happens. One of the quirks of our most beloved distro. (No sarcasm. I really do love it) |
Hi,
If you look inside packages "xf86-video-i810" and "xf86-video-intel" you'll notice that some files got the same name in both packages. As "xf86-video-intel" is installed later in the installation process, files from "xf86-video-i810" are repleaced, and I think here comes the problem that xorg can't use i810, and e.g. my video card doesn't work with intel, but only with i810. Best regards, atelszewski |
Quote:
Personally, I'm happy as a clam to just reinstall i810 after everything else is done... |
Hi,
I don't know what you exactly mean by: Quote:
It is possible to create slackware cd (dvd) without, let's say intel driver by removing it from packages and editing tagfile for the x series, but in my opinion it's worthless when you know the solution and don't plan to install slackware on thousand computers from cd:) Now, I almost don't use cd's, but PXE and network installation which works just fine. Here comes the easy way to include only the packages you want to install, etc. Best regards, atelszewski |
From the thread I linked to it sounds like the overwrite was intentional.
I'd like to do a custom slack cd (dvd) as well. throw in openoffice and the latest firefox, etc. |
Quote:
And to have it in the actual distro, not changed by individual users, so this relatively minor issue won't affect future users of SW and Intel video chipsets, and cause uneeded irritation. It seems to be a very small oversight by the devel team for SW. Maybe fix that in future releases? |
Hi,
Quote:
Quote:
Best regards, atelszewski |
i810 notes
i810 from intel is an Xorg integrated chipset. It can support 3D with the help of Direct Redndering Infrastructure. Use the option CacheLines (input an integer) this allows you to change your 2D properties, acceleration of video. If the values set to lower 3D textures are visible. If set higher 2D is enhanced at the expense of 3D
|
i810 notes
i810 from intel is an Xorg integrated chipset. It can support 3D with the help of Direct Redndering Infrastructure. Use the option CacheLines (input an integer) this allows you to change your 2D properties, acceleration of video. If the values set to lower 3D textures are visible. If set higher 2D is enhanced at the expense of 3D
|
This thread is almost 5 years old. Please don't resurrect such old threads.
In the mean time the Intel drivers have seen a complete rewrite, so I doubt that these problems apply anymore. |
All times are GMT -5. The time now is 11:59 AM. |