Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
I forgot to mention that the graphic card is Pixelview 6600 256M DDR
DVI GeForce 6800. I expected that it is compatible with fglrx
francesco
---------- Forwarded message ----------
From: Francesco Pietra <chiendarret@gmail.com>
Date: Thu, Mar 19, 2009 at 4:05 PM
Subject: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of
modprobe fglrx
To: amd64 Debian <debian-amd64@lists.debian.org>
Besides the issues posted initially (please see at the end of this
message) other problems have arisen, while I did nothing about BIOS
yet, which is Phoenix version 2004Q3, 03/14/2006.
I installed:
smartmontools (OK)
sensors-detec (fine with smsc47b397 and k8 temp; actually, during ssh
installatio there was a message: "Aborting MAKEDEV invocation", but
udev worked fine)
ssh (and linked it to the computing machine through pub keys, OK)
At reboot, I noticed:
Waiting for /dev to be fully populated ... [ 11.733444]
Cannot reserve MMIO region
after a while it booted, while gnome warned that there was a kernel failure.
The I went on for fglrx;
m-a a-i -t fglrx
reported
setting up fglrx-glx-ia32 (1:8-12-4)
After reboot,
modprobe fglrx
reported
FATAL error inserting fglrx
(/lib/modules/2.6.26-1-amd64/misc/fglrx.ko): cannot allocate memory
$ free -m
reports
Mem 3970 (total) 295 (used) 3674 (free) 0 (shared)
corresponding to four slots DDR1 pc32oo ECC 1GB.
# lshw -class memory
*-firmware
description: BIOS
vendor: Phoenix Technologies Ltd.
physical id: 1
version: 2004Q3 (03/14/2006)
size: 101KiB
capacity: 960KiB
capabilities: pci pnp upgrade shadowing escd cdboot bootselect
edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880
int5printscreen int9keyboard int14serial int17printer int10video acpi
usb
*-cache:0
description: L1 cache
physical id: 6
slot: H0 L1 Cache
size: 64KiB
capacity: 64KiB
capabilities: asynchronous internal write-back
*-cache:1
description: L2 cache
physical id: 7
slot: H0 L2 Cache
size: 2MiB
capabilities: synchronous internal write-through unified
*-cache:0
description: L1 cache
physical id: 8
slot: H1 L1 Cache
size: 64KiB
capacity: 64KiB
capabilities: asynchronous internal write-back
*-cache:1
description: L2 cache
physical id: 9
slot: H1 L2 Cache
size: 2MiB
capabilities: synchronous internal write-through unified
*-memory:0
description: System Memory
physical id: d
slot: System board or motherboard
size: 16GiB
*-bank:0
description: DIMM DRAM Synchronous
physical id: 0
slot: C0_DIMM0
size: 8GiB
width: 64 bits
*-bank:1
description: DIMM DRAM Synchronous
physical id: 1
slot: C0_DIMM1
size: 8GiB
width: 64 bits
*-bank:2
description: DIMM DRAM Synchronous [empty]
physical id: 2
slot: C0_DIMM2
*-bank:3
description: DIMM DRAM Synchronous [empty]
physical id: 3
slot: C0_DIMM3
*-bank:4
description: DIMM DRAM Synchronous
physical id: 4
slot: C0_DIMM0
size: 128MiB
width: 64 bits
*-bank:5
description: DIMM DRAM Synchronous
physical id: 5
slot: C1_DIMM1
size: 128MiB
width: 64 bits
*-bank:6
description: DIMM DRAM Synchronous [empty]
physical id: 6
slot: C1_DIMM2
*-bank:7
description: DIMM DRAM Synchronous [empty]
physical id: 7
slot: C1_DIMM3
*-memory:1 UNCLAIMED
description: Memory controller
product: CK804 Memory Controller
vendor: nVidia Corporation
physical id: 4
bus info: pci@0000:00:00.0
version: a3
width: 32 bits
clock: 66MHz (15.2ns)
capabilities: ht bus_master cap_list
configuration: latency=0
*-memory:2 UNCLAIMED
description: Memory controller
product: CK804 Memory Controller
vendor: nVidia Corporation
physical id: 0
bus info: pci@0000:80:00.0
version: a3
width: 32 bits
clock: 66MHz (15.2ns)
capabilities: ht bus_master cap_list
configuration: latency=0
*-memory:3 UNCLAIMED
description: Memory controller
product: CK804 Memory Controller
vendor: nVidia Corporation
physical id: e
bus info: pci@0000:80:01.0
version: a3
width: 32 bits
clock: 66MHz (15.2ns)
capabilities: bus_master
configuration: latency=0
=====================
thaks for help
francesco
---------- Forwarded message ----------
From: Francesco Pietra <chiendarret@gmail.com>
Date: Wed, Mar 18, 2009 at 8:18 AM
Subject: Resource conflict amd64 lenny
To: amd64 Debian <debian-amd64@lists.debian.org>
I have resumed a dismissed (removed mem slots, HDD WD Raptor, floppy,
CD-ROM) computer that was running fine with amd64 etch raid1.
Mainboard Tyan S2895, two dual-opteron 265, graphic card Pixelview
6600256M DDR DVI PCI-Express. New two sata Maxtor HDD 250GB, 4 slots
Kingston DDR1 pc3200 400MHz, new CD-ROM and floppy. amd64 lenny raid1.
No fast video driver installed as yet.
kernel.shmmax=1000000000
kernel.shmall=4000000000
At boot:
ERROR Resource conflict PCI Mass Storage Controller in slot 01
Bus: 01, Device 04, Function: 00 was unable to run due to memory constraints
Press <F1> to resume, <F2> to stop.
On pressing F1 it boots fine and everything is working, as far as I
can understand. On booting again, same issues.
BIOS (never updated) problem with lenny?
Thanks for advice
francesco pietra
Reply to: