| Uploader: | Taulkis |
| Date Added: | 12 April 2009 |
| File Size: | 70.27 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 25712 |
| Price: | Free* [*Free Regsitration Required] |
Have been googleing for a couple of days now, Some posts in these forums but not much useful yet. I don't think I need it, but it doesn't work just like yours.
Pete Graner pgraner wrote on Comment 7 Chuck Ebbert Not built in, not a module. Video Device [GFX0] multi-head: When I manually inktialize the grub commands to bootthe problem seems to be fixed.
Would this be related to this bug, or should I file a new one? Hosting by Gossamer Threads Inc.
AGP aperture is M 0xd So it still loads drm first, then i, then agpgart. At the first reboot I hope, but after few reboot the problem appear sometimes.
[AGPGART] Allow multiple backends to be initialized
Running on Battery power: The initializs has been corrected. That message is just a warning, it says. Note You need to log in before you can comment on or make changes to this bug. Graphics address remapping table. Comment 20 Chuck Ebbert The updates fix this bug on my system.
– agpgart-intel hangs during initialization
Wed Mar 30, I can reproduce this pretty reliably on my Latitude D when booting with the internal screen and undocked. Thu Mar 31, 5: AGP aperture is M 0xe Vostro NonfreeKernelMo dules: However, when I log in now, compiz is not running.
All seems ok in xorg. Vlad Nicolae bfg-se7en on If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version.
With the new kernel 2.
Changed in linux Ubuntu: With the other kernels this does not happen. Show Obsolete 3 Add an attachment proposed patch, testcase, etc. Aperture conflicts with PCI mapping. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Intel HD Graphics Chipset [ 0.
You are not directly subscribed to this bug's notifications. Tim Gardner timg-tpi wrote on Without having read the relevant kernel source, I'd still venture that one of the following causes might be our ljnux.
Comments
Post a Comment