On Sunday 23 July 2006 08:32, Anthony DeRobertis wrote:
> Andreas Kleen wrote:
>
> >
> > You need to use iommu=soft swiotlb=force
> >
> > The standard IOMMU is also broken on VIA, but forced swiotlb should
> > work.
>
> Didn't work :-(
swiotlb=force is unfortunately broken right now.
But whi
Anthony DeRobertis wrote:
Andreas Kleen wrote:
You need to use iommu=soft swiotlb=force
The standard IOMMU is also broken on VIA, but forced swiotlb should
work.
Didn't work :-(
Excepts from the log:
Bootdata ok (command line is BOOT_IMAGE=2.6.17-1-smp ro root=902
iommu=soft swiotl
Andreas Kleen wrote:
>
> You need to use iommu=soft swiotlb=force
>
> The standard IOMMU is also broken on VIA, but forced swiotlb should
> work.
Didn't work :-(
Excepts from the log:
Bootdata ok (command line is BOOT_IMAGE=2.6.17-1-smp ro root=902
iommu=soft swiotlb=force single)
...
skge et
On Wednesday 12 July 2006 06:09, Kevin Brown wrote:
> Andreas Kleen wrote:
> > If it helps I can do a proper patch that only bounces IO > 4GB through
> > the copy.
>
> For the A8V series of boards, that will almost certainly be just fine,
> because as far as I know you can't populate them with more
Andreas Kleen wrote:
If it helps I can do a proper patch that only bounces IO > 4GB through
the copy.
For the A8V series of boards, that will almost certainly be just fine,
because as far as I know you can't populate them with more than 4G of
memory anyway.
If someone has more than 4G of me
Spamming bug robot dropped from cc list.
Am Mi 12.07.2006 04:46 schrieb Anthony DeRobertis <[EMAIL PROTECTED]>:
> OK, here are the results with iommu=force. All of these are copied
> down
> by hand, so please forgive any transcription errors:
You need to use iommu=soft swiotlb=force
The standa
OK, here are the results with iommu=force. All of these are copied down
by hand, so please forgive any transcription errors:
2.6.12[1]: Last line displayed on screen is "ata1: dev 0 ATA max
UDMA/133 390721968 sectors, lba48". Then it sits there. Scrolling with
shift-pgup/pgdown works. Control-Alt-
Andi Kleen wrote:
> Is that a board with VIA chipset?
Yep.
>
> VIA doesn't seem to support PCI accesses with addresses >4GB and they also
> don't have a working GART IOMMU.
>
> It will likely work with iommu=force
I'll give this a try I do get a line in dmesg which reads:
PCI-DMA: Disabl
* Andi Kleen <[EMAIL PROTECTED]> [2006-07-07 23:28]:
> Is that a board with VIA chipset?
Yes, according to lspci, there's a VIA K8T800Pro and VT8237.
:00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
:00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
On Friday 07 July 2006 23:18, Stephen Hemminger wrote:
> On Mon, 3 Jul 2006 22:52:38 +0200
> Martin Michlmayr <[EMAIL PROTECTED]> wrote:
>
> > We received the following bug report at http://bugs.debian.org/341801
> >
> > | I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory
> >
On Mon, 3 Jul 2006 22:52:38 +0200
Martin Michlmayr <[EMAIL PROTECTED]> wrote:
> We received the following bug report at http://bugs.debian.org/341801
>
> | I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory
> | hole in the BIOS, the skge driver prints out this message:
> |
We received the following bug report at http://bugs.debian.org/341801
| I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory
| hole in the BIOS, the skge driver prints out this message:
| skge hardware error detected (status 0xc00)
| and then does not work. Setting debug=16
12 matches
Mail list logo
