Re: Fwd: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
On Sun, Mar 22, 2009 at 08:07:31PM +0100, Francesco Pietra wrote: > Please disregard all issues below. Running > > # dpkg-reconfigure -phigh xserver-xorg > > X started correctly and should be 3D. I must say the the HOWTO has > made simple what is apparently a complex installation. I am curious > where the nvidia driver is indicated: after the reconfigure with > options, /ect/X11/xorg.conf is the same as before, when X failed to > start. Well actually as of lenny it became a bit tricker to get the nvidia driver going. I should update the howto to fix that. In /etc/X11/xorg.conf you have to add 'Driver "nvidia"' to the section for the video card. Another way to do that is to install the package 'nvidia-xconfig' and running that tool, and it should automatically add the Driver line to the xorg.conf for you. I am still experimenting a bit with that to decide how to add that to the howto. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Fwd: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
Please disregard all issues below. Running # dpkg-reconfigure -phigh xserver-xorg X started correctly and should be 3D. I must say the the HOWTO has made simple what is apparently a complex installation. I am curious where the nvidia driver is indicated: after the reconfigure with options, /ect/X11/xorg.conf is the same as before, when X failed to start. thanks francesco -- Forwarded message -- From: Francesco Pietra Date: Sun, Mar 22, 2009 at 7:54 PM Subject: Re: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx To: Lennart Sorensen With a Tyan S2895 dual-opteron, using the current nvidia driver, it ended in X not starting. It was disabled by the system with message: restart GDM when it is configured correctly. I got the impression that "dexconf" failed to reconfigure xorg.conf. I run # dpkg-reconfigure xserver-xorg but I must have done it wrong as I was given the chance to configure keyboard and mouse only. I did not find where to select the nvidia driver. File xorg.conf is below. I must say that I first run # apt-get update # apt-get upgrade which installed the linux-image-2.6-26-amd64 Actually that image was already in use because I installed amd64 lenny a few days ago on a new raid1 with fresh disks. But there was something wrong with the kernel: at any new boot, gnome warned about a kernel failure. After the above upgrade gnome did no more complain. If anything, there is a message on boot: All RAM (4GB), though Your BIOS does not leave a aperture memory hole, this costs 64.. Failed to allocate mem resources #6 (this should have no bearing on failure to start X) Although the chipset is not recent VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) I had no indication as to use a legacy driver. Therefore, I provide the information to hopefully unravel where the configuration is incorrect. I followed the steps # apt-get install nvidia-kernel-common module-assistant # m-a -i -t prepare # depmod -a # apt-get install nvidia-glx nvidia-glx-dev xserver-xorg the latter was already installed; the system asked whether to clean from unused libraries, I accepted but did not take notice of the removed libraries. # dpkg-reconfigure xserver-xorg # dexconf (as I had notedited before) # adduser ... video I had no warning or error message thus far NOT YET INSTALLED nvidia-glx-ia32 package # reboot == Here is xorg.conf # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection == Here is lspci: 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host b
Re: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
On Fri, Mar 20, 2009 at 11:14:36AM +0100, Francesco Pietra wrote: > I forgot to mention that the graphic card is Pixelview 6600 256M DDR > DVI GeForce 6800. I expected that it is compatible with fglrx No. fglrx is for firegl and radeon cards. A geForce is an nvidia chip and would work with either the nv open source drivers, or the nvidia closed source drivers. For how to install the nvidia closed source drivers (which do openGL unlike the open source nv drivers), see the howto here: http://www.tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
On Fri, Mar 20, 2009 at 6:14 AM, Francesco Pietra wrote: > 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 You may have more success with the nvidia driver with that particular GPU, GeForce GPU's are nvidia products. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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 Date: Thu, Mar 19, 2009 at 4:05 PM Subject: Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx To: amd64 Debian 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: p...@: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: p...@: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: p...@: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 Date: Wed, Mar 18, 2009 at 8:18 AM Subject: Resource conflict amd64 lenny To: amd64 Debian 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 D
Fwd: Resource conflict amd64 lenny & MMIO issues & failure of modprobe fglrx
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: p...@: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: p...@: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: p...@: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 Date: Wed, Mar 18, 2009 at 8:18 AM Subject: Resource conflict amd64 lenny To: amd64 Debian 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=10 kernel.shmall=40 At boot: ERROR Resource conflict P
