Sorry for the late reply. I have now tested with the current kernel (3.0.6).
At least it does not mess up as much as the manual patches, but still it
does not work.
I have attached the dmesg output if you want to check.
If you would like me to test patches, please do not hesitate.
As I am a bit s
On Mon, Oct 10, 2011 at 9:53 PM, Chris Wilson wrote:
> On Mon, 10 Oct 2011 22:32:38 +0200, Tempura San wrote:
> Non-text part: multipart/mixed
>> This would be great, but...
>>
>> I have just tested the patches and it really messes up the system.
>>
>> On the first boot I got a shell and was able
On Mon, 10 Oct 2011 22:32:38 +0200, Tempura San wrote:
Non-text part: multipart/mixed
> This would be great, but...
>
> I have just tested the patches and it really messes up the system.
>
> On the first boot I got a shell and was able to to a dmesg:
> ...
> [ 46.775935] [drm] Initialized drm
This would be great, but...
I have just tested the patches and it really messes up the system.
On the first boot I got a shell and was able to to a dmesg:
...
[ 46.775935] [drm] Initialized drm 1.1.0 20060810
[ 46.926398] i915 :00:02.0: enabling device ( -> 0003)
[ 46.926412] i915 0
On Sun, Oct 9, 2011 at 19:36:27 +0100, Chris Wilson wrote:
> On Sun, 9 Oct 2011 14:44:30 +0200, Daniel Vetter wrote:
> > On Sun, Oct 09, 2011 at 01:07:25PM +0200, Tempura San wrote:
> > > Here is the output of lspci -nn:
> > >
> > > 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
On Sun, Oct 09, 2011 at 10:19:34PM +0200, Tempura San wrote:
> I have built the module with the lines removed. Now in dmesg I get these
> lines, which look better to me:
>
> [...] pci :00:02.0: enabling device ( -> 0003)
> [...] pci :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
I've integrated your patches into the i915 driver I am using.
If I just rebuild the module the result is the same as with Daniel's
suggestion.
As there is also a change in vgaarb.c - which is not a module - I need
to do a full build and check again.
If this is not fixing the behaviour either, is
I have built the module with the lines removed. Now in dmesg I get these
lines, which look better to me:
[...] pci :00:02.0: enabling device ( -> 0003)
[...] pci :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[...] pci :00:02.0: setting latency timer to 64
[...] [drm] Initial
On Sun, 9 Oct 2011 14:44:30 +0200, Daniel Vetter wrote:
> On Sun, Oct 09, 2011 at 01:07:25PM +0200, Tempura San wrote:
> > Here is the output of lspci -nn:
> >
> > 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
> > Controller/Host-Hub Interface [8086:2570] (rev 02)
> > 00:02.0 Dis
On Sun, Oct 09, 2011 at 01:07:25PM +0200, Tempura San wrote:
> Here is the output of lspci -nn:
>
> 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
> Controller/Host-Hub Interface [8086:2570] (rev 02)
> 00:02.0 Display controller [0380]: Intel Corporation 82865G Integrated
> Graphic
Here is the output of lspci -nn:
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface [8086:2570] (rev 02)
00:02.0 Display controller [0380]: Intel Corporation 82865G Integrated
Graphics Controller [8086:2572] (rev 02)
00:06.0 System peripheral [0880]: Intel
On Sun, Oct 09, 2011 at 11:34:57AM +0200, Tempura San wrote:
> According to sysfs, agpgart-intel is only bound to the device:
> 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
> Controller/Host-Hub Interface (rev 02)
That's actually how it should be.
> In case the BIOS did not do the setu
I can assign the internal card as primary device, but I would like to
have the PCI (not PCIe) to be the primary one.
Background: The PCI card is an old one, where I take the RAMDAC signal
to feed an old LCD panel - so the console output is visible on the LCD.
The internal card is connected via VGA
According to sysfs, agpgart-intel is only bound to the device:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
In case the BIOS did not do the setup right, is there any way to
(re-)initialise it in a running system?
Tempura.
>> Secondary display:
>>
> Secondary display:
> 03:0a.0 VGA compatible controller: Avance Logic Inc. ALG-2302
>
> The 82865G is onboard, but via BIOS the other (PCI) card is activated.
> In the end I would like to run Xorg on the 82865G card and keep the
> console output on the PCI card.
The problem is I don't think the s
On 2011/10/08 17:25 (GMT+0200) Tempura San composed:
The 82865G is onboard, but via BIOS the other (PCI) card is activated.
In the end I would like to run Xorg on the 82865G card and keep the
console output on the PCI card.
Does your PC's BIOS setup not permit to assign priority to the onboard
Hi everybody,
I want to set up the following configuration:
Primary display:
00:02.0 Display controller: Intel Corporation 82865G Integrated Graphics
Controller (rev 02)
Secondary display:
03:0a.0 VGA compatible controller: Avance Logic Inc. ALG-2302
The 82865G is onboard, but via BIOS the othe
17 matches
Mail list logo
