Debian Hardware :: Nouveau - Pointer To TMDS Table Invalid
Apr 13, 2015
I migrated from Ubuntu 14.10 some weeks ago and I've been playing with Debian Jessie RC2 these days. Everything is working right... however when debian is starting I get some error messages from nouveau, I've just run dmesg and here is the output [URL] ....
I'm getting some lines like this :
Code: Select all[  8.933681] nouveau [ DEVICE][0000:08:00.0] BOOT0 : 0x0e7240a2
[  8.933682] nouveau [ DEVICE][0000:08:00.0] Chipset: GK107 (NVE7)
[  8.933683] nouveau [ DEVICE][0000:08:00.0] Family : NVE0
[  8.948205] nouveau [  VBIOS][0000:08:00.0] using image from ACPI
[  8.948513] nouveau [  VBIOS][0000:08:00.0] BIT signature found
[Code] ....
There is any explanation for these "write of ___________ FAULT at ________" messages?
When I boot from my new Fedora15 LiveCD I get this on startup:
Code: Pointer to BIT loadval table invalid. Everything appears to be working pretty normally other than the fact that the error came up on the screen. Is this going to be a major problem? Is there some kind of fix or patch that I can apply?
I have just installed the newest Debian Stable 7.8 release on my new notebook. Before installation I had to free some disk space from the preinstalled Windows7 with ntfsresize and fdisk. In addition to the existing three primary partitions I created an extended one with three logical partitions for /(root) /home and swap, see the output of 'fdisk -lu'
For some reason I put a bootable flag on sda7, and the only small concern during installation was that some BIOS systems might not work with boot-flag no logical drives. Now, every time I boot I get this "Invalid partition table!' message which I must 'enter" away before I get to the GRUB menu.
i just upgraded to 10.10 thru update manager, had problems upgrading, had to disable Nvidia - nouveau to upgrade and everything went well for 5 days but then i disabled backports in software sources then i changed visual affect from normal to extra and turned computer off. NOW i cant use ubuntu it just freezes on the purple ubuntu screen prior to login.have tried using safe mode and repair broken packages, which did a 21mb update but still nothing but freeze. i get this message in safe mode
I installed openSUSE on a XP runnng computer and every thing is OK.When I tried to Install a new XP, I got this error:Code:Invalid Partition Table I fixed it by reinstalling GRUB using Rescue System.I tried fix mbr on XP Repair System and I got that error again.Now I want to keep XP and remove openSUSE. But computer only boots by GRUB and XP's boot loader is unable to boot and shows that error
I had a RAID controller in a system that would not load Virtuozzo. So I deleted the array created by the 3Ware 9550SX controller before removing it and one drive from the CentOS 4.8 server. Even though I deleted the array when the server boots it shows an error:
ERROR : asr : invalid RAID config table
How can I clear and remove the table without having to reload the OS? Can I? Di I need to run the Seagate Tools and reset the drive?
I keep getting the following errors on any terminal sessions I have open:
Code: Message from syslogd@zzzzz at Aug 24 14:55:55 ... kernel: Northbridge Error, node 0 Message from syslogd@zzzzz at Aug 24 14:55:55 ... kernel:Invalid GART PTE entry during table walk.
Nothing appears to actually be failing and my searches on the Internet imply that this may actually not be a problem at all but rather an OS issue. Can anyone provide a definitive answer?
I installed Debian 5.03 Lenny successfully on my machine. I got this error during boot: ACPI : invalid PBLK length [5]. After that the Operating System boots properly and starts normally. What does this error statement mean? Is it safe to work with this installation despite this error?
I was installing opensuse 11.2 in parallel with windows xp.but during installation suddenly power has gone and after that opensuse is giving me the error message corrupt partition.i am also not able to login in xp. so I decide to reinstall windows, I got the error saying "invalid partition table" after the first restart of windows xp installation.
I tried to use windows system recovery console and committing fixmbr and fixboot commands, but didn't work. i have 2 window partition(1 for windows and 1 for data).i do,nt want to format 2,nd partition.
How can I installed windows?My plan was first to install windows xp, then opensuse again.
I was reading another thread about someone with a bad partition table and I decided to join this forum. I'm not going to take any drastic actions with the partition (/dev/sda3) in question. I am going to wait for instructions on what to do first. I am not very good with Linux and need some hand holding. System: DELL 4550 Dual-Booted with XP and Ubuntu. Works OK, just no swap. Well, here's what I did: I deleted a partition for Windows XP Pro because it was a trial, and it ran out. I then decided to slide the swap partition for the Ubuntu Linux that I dual-boot into over. (If this was successful, I was going to try expanding the root partition to take up the unused space.) I used Gparted on a CD to do this, as I figured it was safe to do.
I now cannot mount the swap space at bootup (and have to go into a backup version of the OS), although I can use Gparted in Linux to execute the "swapon" command, and it appears that it worked because I now see "swapoff" as an option on the context menu. (I actually don't even need a swap partition, except to hibernate.) If I highlight the swap partition and click on "Drive" on Gparted's menu bar and select "Create Partition Table", it will erase all data on /dev/sda, so how do I fix the bad partition table non-destructively?
I'm trying to clone a Linux install to a different laptop. It's made a little complicated by two facts:
1) The 'new' laptop I'm trying to copy my Linux installation to is actually older and has a smaller hard drive then the computer I'm copying from
2) The computer I'm copying from has both a windows and Linux installation; I only care about the Linux partition.
I figured I would copy only the Linux partition from my primary computer to the laptop, sense the laptop doesn't have a large enough hard drive to copy everything. So I used the DD commands to copy SDA3 (main Linux partition) from my main computer to SDA2 of my laptop. When I came back a few hours later I was surprise to find my laptop trying to reboot itself (I never turned it off). It would keep starting to reboot, failing, and restarting itself. Not too surprising sense its boot partition wasn't changed so it's trying to boot into centos when I copied a redhat partition to it.
The problem is that when I used a redhat boot disk the rescue mode was unable to find a Linux partition to mount. /dev/sda2 exists, but trying to mount it gets the complaint "No such file or directory". "fdisk -l" lists sda1 (the boot sector) and sda2. Sda2 is the correct size and reports Linux LVM for its system. But "fdisk -l /dev/sda2" gives the error message "Disk /dev/sda2 doesn't contain a valid partition table" Did I not clone the drive correctly, or was an error caused due to the boot sector not being copied yet (the laptops boot sector is smaller then my old computers, so I can't copy from old computer to laptop)? Can I salvage the laptops partition table somehow, or do I have to repeat the cloning process? And if I do have to re-clone my computer can anyone tell me what I did wrong the first time so it works this time? I don't care if I copy just the Linux partition or both windows and Linux. Even though my main computer has a larger hard drive I'm only using about half of its available space so it should be possible to copy both partitions if I could ignore the unused sections of the harddrive.
Edit: I used DD to copy a tiny part of the Linux partition from my laptop so I could look at it. Most of it is illegible binary of course, but I scrolled through till I found some text right near the beginning:
Code:
VolGroup00 { id="F2MWxh-....-BidcLe" seqno = 1
[code]....
So it seems that the DD command did copy everything over to the laptop, which is good to know. I noticed that it says device="/dev/sda3" right in the middle of the code I just posted. The Linux section of my original computer was SDA3 but I copied it to partition SDA2 of my laptop. So is the problem because the boot partition is for the wrong device? I don't suppose if I modified that one line to say SDA2 it would be able to load correctly? (Not that I know how I would modify the line, short of using the DD command again).
I installed Ubuntu as shown in the wiki and when I went to restart it gave me a lovely blinking cursor and nothing else. So I held down option, loaded into osx, reinstalled rEFIt and got my menu on startup. Unfortunately, the partition sync tool doesn't seam to be working, it gives me an error: Status: MBR partition table is invalid, partitions overlap. Error: Not Found returned from gptsync.efi
Now that nVidia is up and running, I'm curious to do a comparison with Nouveau. I there an EASY way to do this? Like a simple on/off switch? Major system/kernel changes are not an acceptable option. If it can't be easily done, I'll just stick with nVidia.
I've started playing around with debian 6 stable, and was just wondering if its worth it to go to the trouble of removing nouveau, or if it will handle everything well enough. I use my laptop for a little bit of gaming (older games) under wine, all the basic email/web browsing/writing stuff, some photo editing under gimp, movies/music, and a very little bit of Blender work.Will Nouveau handle all this well enough, or should I use the proprietary nvidia driver?
I have installed debian jessie stable and would like to use hardware decoding with the nouveau driver. I have tested with the propietary nvidia 340.65 driver and MPV and successfully enabled hardware decoding. However, there seems to be a frame sync issue with mutter and nvidia that I want to avoid. I've followed the instructions for enabling hardware decoding with nouveau here, hURL..., but haven't had success. What I've done so far is install jessie stable, run updates, install mplayer2, mpv, mesa-vdpau-drivers, and follow the previously mentioned guide. Mplayer2 throws an error about not finding the proper codec. MPV at least attempts to play the video but promptly freezes the system so that I can't recover without rebooting. URL....
I'd like to run a real-time kernel with the latest linux-rt patch, for 2.6.33. Incidentally, the .33 kernel was the first to include the Nouveau driver, and seeing that I cannot get the proprietary NVidia driver to compile --the RT patch really messes things up and the patches for nv-linux.h out there all seem incomplete-- I thought it would be a good idea to switch to Nouveau and save me from additional headaches.
I'm running sid, and as you certainly know, the Nouveau driver has been backported to the stock Debian kernel, 2.6.32-5-686. It works very well, all I had to do was change my xorg.conf with this line : Driver "nouveau".
However, when I boot my new 2.6.33-rt kernel, Xorg stops here :
[skipping a lot of stuff that seems to work ok] (II) LoadModule: "nouveau" (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" compiled for 1.7.7, module version = 0.0.15
[Code]....
So what is so different about the backport to 2.6.32 ? How come the DRM lib, or whatever it is, doesn't work with 2.6.33 ?
I just thought of something, I'll try compiling my 2.6.33 kernel without the -rt patch and I'll let you know.
I need to use the proprietary NVIDIA driver instead, but it can't install while this is active. I'm working off a fairly fresh install anyway, so I can reinstall debian if the option to not install nouveau is present somewhere during the install process. Or, is there an easy way to get rid of Nouveau from my current install altogether?
I have been googling trying to fix this ... basicly I have a (int **) variable, and when I try to pass a (int) value to a specific position, I have seg.fault.Resuming what I have is:
I was using an extremely common debian based distro, but I have been rebooting my pc non stop for the last two days trying to get my nvidia fx5200 drivers to work. (it is just IMPOSSIBLE to disable the nouveau driver, i have tried blacklisting it, editing xorg etc, nothing works) I need to know if there are many issues with getting nvidia graphics cards to work in debian. it seems like the last 18 months worth of releases on all the other debian based distros have completely broken all support for any nvidia card made prior to 2011. i know for a fact that in windows xp all my hardware works perfectly, but i really dont want to have to use that, i have been a linux user for more than 5 years now, but all i am really looking for now is reliability. i want to be able to use the nvidia-173 driver, as i know that this allows me to watch the movies i take on my dv camera, and ......
Yesterday I installed some updates on my Jessie system (I don't remember if the kernel was also updated). After rebooting the system nothing happens after the "Loading intial ramdisk"-message. If I boot in recovery mode the boot stops at the message:
Code: Select allfb: switching to nouveaufb from simple
If I add "nouveau.modeset=0" temporary to the GRUB-entry for the recovery mode, it will boot up in the console-mode.
I was able to get an ethernet connection with "dhclient eth0" and removed the "xserver-xorg-video-nouveau" package. Then I installed it and the removed gnome-desktop again. Before removing it, aptitude said the following to the package:
Code: Select alli A xserver-xorg-video-nouveau
Now it only says:
Code: Select alli  xserver-xorg-video-nouveau
But this didn't change my problem. I found a similar case in the internet, but there were no solutions for it: [URL] ....
The next thing I would do, is to install the proprietary nvidia-drivers, but since I have a GTX 960 video card, I would have to use experimental drivers. So I'm afraid to make it more worse trying to install this drivers.
Also I'm not sure if it really is a driver-specific of kernel-specific problem. My kernel is version 3.16.0-4-amd64.
Motherboard: M2N-MX with Athlon X2 3600 from 2006 onwards 00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Kernel: Debian Sid with 2.6.32-5-amd64 and custom 2.6.36-rc7 Monitor: Samsung 712N, 17inch, with native 1280x1024 resolution
Everything was fine with both kernels with custom 1280x1024 resolution upto yesterday. But when I rebooted today, first I noticed that X stopped working. After updating xorg.conf to 1024x768, it started working . After going through the kernel log in /var/log/messages, I noticed the following differences
Yesterdays log:
nouveau 0000:00:0d.0: Detected 64MiB VRAM nouveau 0000:00:0d.0: 64 MiB GART (aperture) nouveau 0000:00:0d.0: Saving VGA fonts
[code]....
There is an extra "Load detected" line and the resolution got reduced from 1280x1024 to 1024x768.
Today I've installed Debian Squeeze Beta2. During the net-installation everything was fine. After the installation my login screen is too slow: booting up the the login graphics may take several minutes and when it is done, the keyboard is delayed or not responsive. When I switch to tty, before the activation of the cursor (that is, before I can type anything at the login prompt because the keyboard does not respond), appears this message.
[drm] nouveau 0000:05:00.0 GPU lockup - switching to software fbcon Then I can login into the terminal. LSPCI say that 05:00 is the graphics card, an INVIDIA GeForce 8800 gtx that worked on Debian Lenny.
I've just installed Squeeze and try to install Nvidia drivers, but installer wrote that I have to disable Nouveau first. So could you please tell me how to turn off nouveau driver totally and correctly.
