All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 86935] New: unknown kepler chipset
Date: Tue, 02 Dec 2014 15:19:58 +0000	[thread overview]
Message-ID: <bug-86935-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2006 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=86935

            Bug ID: 86935
           Summary: unknown kepler chipset
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: sven.koehler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

With Linux 3.17.4, I get the following errors in dmesg:

nouveau ![  DEVICE][0000:01:00.0] unknown Kepler chipset
nouveau E[  DEVICE][0000:01:00.0] unknown chipset, 0xb06070b1
nouveau E[     DRM] failed to create 0x00000080, -22
nouveau: probe of 0000:01:00.0 failed with error -22

Obviously, I don't have a framebuffer console during boot and of course
nouveau-based X also doesn't work. I'm currently using uvesafb as a workaround.

lspci -v output:

01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730]
(rev a1) (prog-if 00 [VGA controller])
    Subsystem: CardExpert Technology Device 1287
    Flags: bus master, fast devsel, latency 0, IRQ 11
    Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
    Memory at e8000000 (64-bit, prefetchable) [size=128M]
    Memory at f0000000 (64-bit, prefetchable) [size=32M]
    I/O ports at e000 [size=128]
    Expansion ROM at f7000000 [disabled] [size=512K]
    Capabilities: [60] Power Management version 3
    Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [78] Express Legacy Endpoint, MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [128] Power Budgeting <?>
    Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
    Kernel modules: nouveau

I have no additional details on the card. It came with an HP office PC.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3206 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-12-02 15:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 15:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-86935-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-12-02 15:27   ` [Bug 86935] [NV106] unknown kepler chipset 0x106 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 15:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 11:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 11:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 12:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 12:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 13:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-18 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-27 18:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-27 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-14 20:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-20  4:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-86935-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.