search for: nvidiafb

...errmann at gmail.com> wrote: > >> >> And your PCI-BAR adjustment doesn't change >> >> anything either, sorry. >> > >> > I simply tried another approach to pacify the resource checker. >> > >> > However, there is some difference. nvidiafb cannot access the >> > resources if IORESOURCE_BUSY is used. >> >> Are you sure this is related to IORESOURCE_BUSY? Or is it related to >> CONFIG_X86_SYSFB? > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > compile without it. create_simplef...

...rything works fine. It's the > default and is what pre-3.12 kernels always did. Of course, you are right, I missed sysfb.h. > > I tried four combinations: with and without IORESOURCE_BUSY and with > > and without the PCI resource adjustment. The only combination when > > nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and > > the BOOTFP resource is adjusted to match the PCI BAR. > > A dmesg log would be nice, but I assume nvidiafb fails because it > cannot map its BAR regions? The logs are adjusted and so it the kernel config file. $ grep...

...mapping of such a resource; we don't want > * to warn for those; some drivers legitimately map only > * partial hardware resources. (example: vesafb) > */ > > So I added IORESOURCE_BUSY to sysfb_simplefb.c and the problem is fixed > now. Actually, it prevents nvidiafb from claiming the device: > > nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff > 64bit pref] > > But maybe that's the point of sysfb_simplefb? Anyway, here's the > patch/hack, signed off in case it's correct :) > > FWIW another nvc0...

...t; effects even if the effects are positive :) Indeed. And I appreciate your help a lot. >> And your PCI-BAR adjustment doesn't change >> anything either, sorry. > > I simply tried another approach to pacify the resource checker. > > However, there is some difference. nvidiafb cannot access the > resources if IORESOURCE_BUSY is used. Are you sure this is related to IORESOURCE_BUSY? Or is it related to CONFIG_X86_SYSFB? Thanks David > It's not that it matters for me. nvidiafb fails on my hardware anyway > and I don't need it when I already have simple...

...ug.cgi?id=69488 Good to hear that my patch actually makes more than cosmetic difference for somebody. My system doesn't hang even with the stack trace. I posted another patch on the bug page. It widens the BOOTFB resource to match the PCI BAR instead of making it busy. With the new patch, nvidiafb doesn't report that the resource is busy, it reports unsupported hardware, which is true. Old patch: nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] nvidiafb: cannot request PCI regions New patch: nvidiafb: Device ID: 10de0ffc nvidiafb: unknown NV_ARCH...

...tic issue. We need to mark the sysfb FB as busy to avoid the nasty warnings. Other than that, this shouldn't cause any issues. Thanks David > I posted another patch on the bug page. It widens the BOOTFB resource > to match the PCI BAR instead of making it busy. With the new patch, > nvidiafb doesn't report that the resource is busy, it reports > unsupported hardware, which is true. > > Old patch: > nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff > 64bit pref] > nvidiafb: cannot request PCI regions > > New patch: > nvidiafb: Devi...

http://bugs.freedesktop.org/show_bug.cgi?id=16450 Summary: Powerbook G4 12" (NV34M [GeForce FX Go5200]) freezes on X restart - Fedora 9 Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...er driver, and/or back, and/or restarting does nothing. Code: dusf at banshee:~$ lspci -k ... 01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1) Subsystem: Dell Device 0405 Kernel driver in use: nvidia Kernel modules: nvidia-current, nvidia-173, nouveau, nvidiafb Although now Kernel modules also includes 'nvidia' after my attempts to fix the problem which I shall get on to. I was advised on the WINE HQ forums: > You are using both the proprietary and FOSS drivers. Remove the FOSS > drivers (nouveau) and use only the nVidia supplied drivers...

Hi Pavel On Fri, Sep 27, 2013 at 9:40 PM, Pavel Roskin <proski at gnu.org> wrote: > Quoting David Herrmann <dh.herrmann at gmail.com>: > >> I am aware of this and there is already a fix pending from 2 weeks >> ago. Unfortunately, I have been in the US for the last 2 weeks and >> haven't really been able to push on that. Anyhow, it should really be >>

...lags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Kernel modules: nvidiafb -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

...(64-bit, prefetchable) [size=256M] Region 3: Memory at f8000000 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at 6c00 [size=128] [virtual] Expansion ROM at fb000000 [disabled] [size=512K] Capabilities: <access denied> Kernel modules: nvidia, nvidiafb -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

...0200 David Herrmann <dh.herrmann at gmail.com> wrote: > >> And your PCI-BAR adjustment doesn't change > >> anything either, sorry. > > > > I simply tried another approach to pacify the resource checker. > > > > However, there is some difference. nvidiafb cannot access the > > resources if IORESOURCE_BUSY is used. > > Are you sure this is related to IORESOURCE_BUSY? Or is it related to > CONFIG_X86_SYSFB? CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would compile without it. create_simplefb() is used in arch/x86/kerne...

Hello, I have installed git-kernel (3.2-rc3) with git-drm libs on debian. nvidiafb on terminals works fine, but loading of nouveau for Xorg fails. Maybe someone can help me or give me hints (what do I have to change?). The kernel produces the attached output. Best regards, Lars Callenbach ----- [ 6.971517] [drm] Initialized drm 1.1.0 20060810 [ 7.036085] [drm:drm_pci_...

...8] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information <?> Capabilities: [100] Virtual Channel <?> Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information <?> Kernel modules: nouveau, nvidiafb

Hello! I'm getting this backtrace every time I boot: resource map sanity check conflict: 0xf0000000 0xf1ffffff 0xf1000000 0xf112bfff BOOTFB ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at /home/proskin/src/linux/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x372/0x380() Info: mapping multiple BARs. Your kernel is fine. Modules linked in: CPU: 6 PID: 1 Comm: swapper/0 Not tainted

...a screen, mostly at its bottom. Switching to console causes crash and lock of a kernel with some responsibility to magic sysrq. I used yesterday git versions of drm, xf86-video-nouveau and mesa on slamd64-current linux (64 bit) distribution, linux 2.6.22.7 with SMP support on Athlon dual core CPU, nvidiafb module was loaded. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=15481 Summary: Nouveau on nVidia Corporation G71 [GeForce 7950 GT]: works but lockup for 6 min at shutdown Product: xorg Version: 7.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: high Component:

...e resource * but a driver mapping of such a resource; we don't want * to warn for those; some drivers legitimately map only * partial hardware resources. (example: vesafb) */ So I added IORESOURCE_BUSY to sysfb_simplefb.c and the problem is fixed now. Actually, it prevents nvidiafb from claiming the device: nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] But maybe that's the point of sysfb_simplefb? Anyway, here's the patch/hack, signed off in case it's correct :) sysfb_simplefb: mark BOOTFB resource as busy From: Pave...

...it didn't. It's better when patches don't have unexpected effects even if the effects are positive :) > And your PCI-BAR adjustment doesn't change > anything either, sorry. I simply tried another approach to pacify the resource checker. However, there is some difference. nvidiafb cannot access the resources if IORESOURCE_BUSY is used. It's not that it matters for me. nvidiafb fails on my hardware anyway and I don't need it when I already have simplefb and nouveau. But I think we should have a closer look why it fails and what other drivers may fail. -- Regards,...

...I am having big trouble getting the nouveau driver to work with either > Geforce GT 710 or Geforce 9800 GT on an ARM armv7l Cortex-A9 with PCIe > x1/x4 with linux kernel 4.15-rc. > > The Geforce GT 710 hangs the kernel boot process for a while and then > a kernel oops occurs, due to nvidiafb, when initializing CRTC. It also > generates messages "division by zero in kernel". You definitely want to disable nvidiafb somehow, it's ancient, unmaintained, and has zero chance of working on this hardware. I'm not even entirely sure how/why it thinks it can work on this ha...