Re: agp_backend_initialize() failed on ServerWorks CNB20LE

2005-09-02 Thread Dave Jones
On Fri, Sep 02, 2005 at 11:21:39PM +0200, Maciej Soltysiak wrote:
 > Hello,
 > 
 > On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled
 > I get these upon bootup:
 > Linux agpgart interface v0.101 (c) Dave Jones
 > agpgart: unable to determine aperture size.
 > agpgart: agp_backend_initialize() failed.
 > agpgart-serverworks: probe of :00:00.0 failed with error -22
 > agpgart: unable to determine aperture size.
 > agpgart: agp_backend_initialize() failed.
 > agpgart-serverworks: probe of :00:00.1 failed with error -22

Every time I've seen this reported so far, its turned out that the board
doesn't actually have an AGP slot. Is this case here too ?

Documentation on serverworks chipsets is as good as non-existant,
so there's not a great deal we can do here.

 > The only problems I have that *may* be related to these messages is the
 > fact that when I boot into X and try to switch to a text console, the
 > screen gets garbled and freezes, the server works fine besides the
 > screen throwing trash at me.

Likely completely unrelated. agpgart is used only for accelerated 3d.

Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


agp_backend_initialize() failed on ServerWorks CNB20LE

2005-09-02 Thread Maciej Soltysiak
Hello,

On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled
I get these upon bootup:
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of :00:00.0 failed with error -22
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of :00:00.1 failed with error -22

lspci -vvv shows (i skipped the IDE, ISA and NIC lines):
00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


agp_backend_initialize() failed on ServerWorks CNB20LE

2005-09-02 Thread Maciej Soltysiak
Hello,

On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled
I get these upon bootup:
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of :00:00.0 failed with error -22
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of :00:00.1 failed with error -22

lspci -vvv shows (i skipped the IDE, ISA and NIC lines):
00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR-
Latency: 64, cache line size 08

00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 64, cache line size 08

00:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC 
[Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA])
Subsystem: Intel Corporation: Unknown device 4756
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 66 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 19
Region 0: Memory at fc00 (32-bit, prefetchable) [size=16M]
Region 1: I/O ports at 5000 [size=256]
Region 2: Memory at fb10 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 5000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


The only problems I have that *may* be related to these messages is the
fact that when I boot into X and try to switch to a text console, the
screen gets garbled and freezes, the server works fine besides the
screen throwing trash at me.
It is not a big issue, but maybe anyone would like to know.
Or enlighten me if it

Regards,
Maciej


-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: agp_backend_initialize() failed on ServerWorks CNB20LE

2005-09-02 Thread Dave Jones
On Fri, Sep 02, 2005 at 11:21:39PM +0200, Maciej Soltysiak wrote:
  Hello,
  
  On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled
  I get these upon bootup:
  Linux agpgart interface v0.101 (c) Dave Jones
  agpgart: unable to determine aperture size.
  agpgart: agp_backend_initialize() failed.
  agpgart-serverworks: probe of :00:00.0 failed with error -22
  agpgart: unable to determine aperture size.
  agpgart: agp_backend_initialize() failed.
  agpgart-serverworks: probe of :00:00.1 failed with error -22

Every time I've seen this reported so far, its turned out that the board
doesn't actually have an AGP slot. Is this case here too ?

Documentation on serverworks chipsets is as good as non-existant,
so there's not a great deal we can do here.

  The only problems I have that *may* be related to these messages is the
  fact that when I boot into X and try to switch to a text console, the
  screen gets garbled and freezes, the server works fine besides the
  screen throwing trash at me.

Likely completely unrelated. agpgart is used only for accelerated 3d.

Dave

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/