All of lore.kernel.org
 help / color / mirror / Atom feed
* Think 2.4.10 broke my PCI subsystem.
@ 2002-09-15  5:29 Kevin Carpenter
  2002-09-15 17:13 ` Jeff Garzik
       [not found] ` <3D8451DD.4050106@googgun.com>
  0 siblings, 2 replies; 3+ messages in thread
From: Kevin Carpenter @ 2002-09-15  5:29 UTC (permalink / raw)
  To: linux-kernel

I've recently been okaying around with low cost motherboards and have been
problems on two of them:  the BIOSTAT micro-ATX mobo M7VKQ, and the ESC L7SOM
mobos.

BOth work fine so long as I hold the kernel to 2.4.9 or earlier.  Once the
2.4.10 patch is applied, the kernel no longer recognises the PCI Buss.

Under 2.4.9 /proc/pci shows:

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: PCI device 1039:0740 (Silicon Integrated Systems [SiS]) (rev 1).
      Master Capable.  Latency=32.  
      Non-prefetchable 32 bit memory at 0xe8000000 [0xe8ffffff].
  Bus  0, device   1, function  0:
    PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP (rev 0).
      Master Capable.  Latency=99.  Min Gnt=12.
  Bus  0, device   2, function  0:
    ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 0).
  Bus  0, device   2, function  5:
    IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 208).
      Master Capable.  Latency=16.  
      I/O at 0x4000 [0x400f].
  Bus  0, device   2, function  7:
    Multimedia audio controller: PCI device 1039:7012 (Silicon Integrated Systems [SiS]) (rev 160).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=52.Max Lat=11.
      I/O at 0xe000 [0xe0ff].
      I/O at 0xe400 [0xe47f].
  Bus  0, device  15, function  0:
    Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
      IRQ 11.
      Master Capable.  Latency=32.  Min Gnt=32.Max Lat=64.
      I/O at 0xe800 [0xe8ff].
      Non-prefetchable 32 bit memory at 0xe9102000 [0xe91020ff].
  Bus  1, device   0, function  0:
    VGA compatible controller: PCI device 1039:6325 (Silicon Integrated Systems [SiS]) (rev 0).
      Prefetchable 32 bit memory at 0xe0000000 [0xe7ffffff].
      Non-prefetchable 32 bit memory at 0xe9000000 [0xe901ffff].
      I/O at 0xd000 [0xd07f].

Using lspci:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 740 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 PCI Audio Accelerator (rev a0)
00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]: Unknown device 6325

>From DMESG:

POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb5f0, last bus=1
PCI: Probing PCI hardware
PCI: Using IRQ router SIS [1039/0008] at 00:02.0
Linux NET4.0 for Linux 2.4

After rebuilding with any kernel greater than patch level 9, I get the following
messages as part of the boot sequence:

mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb5f0, last bus=1
PCI: System does not support PCI
isapnp: Scanning for PnP cards...

HELP PLEASE!  I don't want to be stuck on 2.4.9 forever!

I have one development box that I can do just about anything you wish to. 
Please let me know how to help.

Thanks,

Kevin C.
-- 
Kevin Carpenter:  KevinC@SeaPlace.org
Kevin's Home Page: http://www.seaplace.org/kevinc
(Expressing his comments from home in St. Louis, where this message originated)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Think 2.4.10 broke my PCI subsystem.
  2002-09-15  5:29 Think 2.4.10 broke my PCI subsystem Kevin Carpenter
@ 2002-09-15 17:13 ` Jeff Garzik
       [not found] ` <3D8451DD.4050106@googgun.com>
  1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2002-09-15 17:13 UTC (permalink / raw)
  To: Kevin Carpenter; +Cc: linux-kernel

Kevin Carpenter wrote:
> I've recently been okaying around with low cost motherboards and have been
> problems on two of them:  the BIOSTAT micro-ATX mobo M7VKQ, and the ESC L7SOM
> mobos.
> 
> BOth work fine so long as I hold the kernel to 2.4.9 or earlier.  Once the
> 2.4.10 patch is applied, the kernel no longer recognises the PCI Buss.


What happens on a modern kernel, 2.4.19 or 2.4.20-pre7?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Think 2.4.10 broke my PCI subsystem - resolved.
       [not found]     ` <3D850523.70608@googgun.com>
@ 2002-09-16  3:43       ` Kevin N. Carpenter
  0 siblings, 0 replies; 3+ messages in thread
From: Kevin N. Carpenter @ 2002-09-16  3:43 UTC (permalink / raw)
  To: Ahmed Masud; +Cc: linux-kernel

2.4.20-pre7 fixes whatever the problem was.  Kernels between 2.4.10 and 
2.4.19 were broke for these mobo.

Did notice a new message:  Using IRQ router SIS [1039/0008]

Thanks to whomever fixed it!

Kevin C.

Ahmed Masud wrote:

> Kevin N. Carpenter wrote:
>
>> Thats the whole point.  Nothing past 2.4.9 will run on these mobos.
>>
>> Do appreciate the consideration.
>>
>> Kevin C.
>>
>> Ahmed Masud wrote:
>>
>>> Kevin Carpenter wrote:
>>>
>>>> I've recently been okaying around with low cost motherboards and 
>>>> have been
>>>> problems on two of them:  the BIOSTAT micro-ATX mobo M7VKQ, and the 
>>>> ESC L7SOM
>>>> mobos.
>>>>
> Wait ... you say that already :) sorry....
>
>



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-09-16  3:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-15  5:29 Think 2.4.10 broke my PCI subsystem Kevin Carpenter
2002-09-15 17:13 ` Jeff Garzik
     [not found] ` <3D8451DD.4050106@googgun.com>
     [not found]   ` <3D847E95.9040602@seaplace.org>
     [not found]     ` <3D850523.70608@googgun.com>
2002-09-16  3:43       ` Think 2.4.10 broke my PCI subsystem - resolved Kevin N. Carpenter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.