search for: igps

My HP 4010 and the IGP 350M video card. I can only get it to go into 800x600 mode. At one time, Resolution Display (gnome desktop) was giving me an option of 1024x768 and if I selected it the monitor went crazy. Now I don''t even get that higher resolution as an option. I have searched far and wide for information on this card and the Radeon linux driver. No help at all. My

https://bugs.freedesktop.org/show_bug.cgi?id=86641 Bug ID: 86641 Summary: nouveau crashes kernel with nvidia 9400 igp Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau Assignee:

My NC4010 has the ATI Radeon IGP 350M controller http://h18000.www1.hp.com/products/quickspecs/11832_na/11832_na.HTML It works fine in 800x600 but when I change it to 1024x768 the LCD goes bad. Hard to discribe, it looks like the 800x600 is just smaller in the upper left with parts clipped and the rest of the screen repeats part of the reduced sized image. I am running at 60Mz. I have

http://www.tomshardware.com/consumer/20040428/index.html The iRiver iGP-100 was just reviewed at Toms Hardware. They specifically mention that it supports Vorbis. Just thought I'd pass this along. Paul --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

https://bugs.freedesktop.org/show_bug.cgi?id=50374 Bug #: 50374 Summary: nouveau fails to obtain EDID from NV11 (nforce IGP) Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug ID: 87361 Summary: [NV4C] Kernel lock-up after booting to desktop in Fedora 20 & 21 (Nvidia Geforce 6100 IGP) Product: Mesa Version: 10.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker

Hi This does not look right: diff --git a/drivers/gpu/drm/nouveau/nouveau_mem.c b/drivers/gpu/drm/nouveau/nouveau_mem.c index 775a701..c1fd42b 100644 --- a/drivers/gpu/drm/nouveau/nouveau_mem.c +++ b/drivers/gpu/drm/nouveau/nouveau_mem.c @@ -540,7 +540,8 @@ nouveau_mem_detect(struct drm_device *dev) dev_priv->vram_size = nv_rd32(dev, NV04_FIFO_DATA); dev_priv->vram_size &=

Dear All, I just upgraded my firewall/smarthost to a 2.6 GHz P4 on a Gigabyte board with the ATI RS350 chipset. Unfortunately the chipset isn't support on the kernel and I get slow disk performance lspci gives this: lspci 00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge 00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP PCI/AGP Bridge 00:13.0 USB Controller: ATI

See https://bugs.freedesktop.org/show_bug.cgi?id=74492 Reported-by: Ronald <ronald645 at gmail.com> Suggested-by: Marcin Ko?cielnicki <koriakin at 0x04.net> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/Makefile | 1 + drivers/gpu/drm/nouveau/core/engine/device/nv40.c | 10 ++---

Anyone ever used the iGPS-500 under CentOS 5? Any recommendations on a USB-based GPS that "just works"? Ray

Hello! I have trouble with multipath routing. Those options are enabled in kernel: [*] IP: policy routing [*] IP: equal cost multipath [*] IP: equal cost multipath with caching support (EXPERIMENTAL) <*> MULTIPATH: round robin algorithm But issuing: ip r a 1.2.3.0/23 scope global equalize nexthop via 80.245.176.11 \ dev eth0 weight 1 nexthop via 80.245.176.13 dev eth0

...similar issue. You're getting a > bunch of other failed reads, looks like we're somehow not bringing the > card up properly. The most immediate "fix" is to just disable nouveau > entirely -- boot with nouveau.modeset=0. > > Cheers, > > -ilia > As the IGPs "tend" to "steal" system memory: [ 21.733864] nouveau [ PFB][0000:01:00.0] RAM type: stolen system memory [ 21.733883] nouveau [ PFB][0000:01:00.0] RAM size: 256 MiB [ 21.787222] nouveau [ DRM] VRAM: 256 MiB can we reverse the process in this case, and &qu...

On 16-04-2024 16:21, Konrad Jacobi via samba wrote: > hi, > on a samba domain member file server i'm using dfs root shares with > multiple msdfs symlinks pointing to other shares (on the same server), > which works fine. These linked shares have different access rights, > therefore a user might have access to one linked share but not to > another. > Another option is

I just merged drm (Direct Rendering) from HEAD. - Support for latest Intel chips - Support and fixes for many AMD/ATI chips r500 and below - Support AMD/ATI IGP based chips (rs690/rs485) - Lots of code cleanups - Lots of other fixes and changes since the existing drm is 2+ years old If you are experiencing a "garbled" screen with

hi, on a samba domain member file server i'm using dfs root shares with multiple msdfs symlinks pointing to other shares (on the same server), which works fine. These linked shares have different access rights, therefore a user might have access to one linked share but not to another. Is there any option to hide msdfs-symlinks to shares that a user cannot read? (the same as 'hide

...ch chip to set its domain explicitly. > > > This question may have been asked a ton of times, but what is the difference > with the nvac (Ion)? > > Would the nvac have some reserved memory for its usage by the bios which > would then be used as "VRAM"? PFB on the dGPU IGPs has facilities to fake VRAM from an area of "stolen" system memory reserved by the SBIOS. GK20A/GM20B do not do this, and require direct (or, via a mmu, whatever) access to system memory. Ben. > > In any case, the patchseries sounds simple-enough to be maintainable. > > ___...

On Fri, Oct 9, 2020 at 5:54 PM Karol Herbst <kherbst at redhat.com> wrote: > > On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary <linux at zary.sk> wrote: > > > > Hello, > > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working: > > [ 0.000000] Linux version 5.9.0-rc8+ (zary at gsql) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian)

...ere, not actually flip it to the nv4c msi rearm method.] In case of tl;dr, my recommendation is to backport into 3.13: fa8c9ac72fe0bcdf5bc7cc84e85cc2a1af53f9fd 4761703bd04bbdf56396d264903cc5a1fdcb3c01 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 In that order. This should avoid buggy MSI on the nv4x IGPs as well as NV46 (G72). Starting with v3.14, you should only need 0a363e85cdafbceeee6a49b91c604d0d4d070dc7, since presumably 4761703bd04bbdf56396d264903cc5a1fdcb3c01 will have already been backported. Cheers, -ilia

Commit 'drm/nv50-nvc0/vm: support unsnooped system memory' caused a regression on certain nv50 IGP due to not passing the correct target type to nv50_vm_addr() Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=45746 Reported-by: Johannes Obermayr <johannesobermayr at gmx.de> Tested-by: Johannes Obermayr <johannesobermayr at gmx.de> Signed-off-by: Emil Velikov

Dear All, After recently taking a little dive into the NVAC clock tree, I was wondering what that net would look like on cards I expect to be similar. In this case I'm looking for MMIOtraces of NVAA and NVAF, which is marketed as the 8x00 mGPU, 9x00 mGPU, 320M, ION and/or some nForce IGP. If there is anyone who could provide me with an MMIO trace for any of these cards that would be