Commit e88e014f authored by Karol Herbst's avatar Karol Herbst 🐧
Browse files

replace more references to freenode with OFTC

parent 9be79e11
Pipeline #327949 passed with stages
in 1 minute and 6 seconds
......@@ -17,14 +17,14 @@ list`_ is for general nouveau discussions. For developers, there is also
nouveau-related discussions on the `dri-devel mailing list`_ and the `mesa-dev
mailing list`_.
The ``#nouveau`` IRC channel on `FreeNode`_ is also available for nouveau
The ``#nouveau`` IRC channel on `OFTC`_ is also available for nouveau
discussion and `logs`_ are available.
The `issue tracker`_ and `this documentation`_ is available on the
`freedesktop.org GitLab`_.
.. _FreeNode: https://freenode.net/
.. _OFTC: https://www.oftc.net/
.. _logs: https://people.freedesktop.org/~cbrill/dri-log/index.php?channel=nouveau
.. _nouveau mailing list: https://lists.freedesktop.org/mailman/listinfo/nouveau
.. _dri-devel mailing list: https://lists.freedesktop.org/mailman/listinfo/dri-devel
......
......@@ -162,7 +162,7 @@ See [[MultiMonitorDesktop|MultiMonitorDesktop]].
### The fan is really LOUD all the time. How do I make it more quiet?
On many cards, the fan is temperature controlled already, but obviously in your case it is stuck at the maximum speed. We need some help from you to fix it, but we do not know yet what you could do for us, exactly. Please, check this FAQ item every once in a while, we will tell you here what to do, when we figure it out. In the mean time, if you are interested, you can read [[PowerManagement|PowerManagement]] and/or contact mupuf on the #nouveau freenode IRC channel.
On many cards, the fan is temperature controlled already, but obviously in your case it is stuck at the maximum speed. We need some help from you to fix it, but we do not know yet what you could do for us, exactly. Please, check this FAQ item every once in a while, we will tell you here what to do, when we figure it out. In the mean time, if you are interested, you can read [[PowerManagement|PowerManagement]] and/or contact mupuf on the #nouveau OFTC IRC channel.
Your help is needed to fix this issue.
......
## #nouveau on irc.freenode.net
## #nouveau on www.oftc.net
All are welcome to join our ongoing development conversation in the [[IRC channel|irc://irc.freenode.net/nouveau]].
All are welcome to join our ongoing development conversation in the [[IRC channel|irc://irc.oftc.net/nouveau]].
<a name="log2"></a>
### IRC logs
......
......@@ -38,7 +38,7 @@ cbaoth says he gets nothing to serial console, but kbd leds caps&scroll blinking
**status:** On hold, until mmio-trace is in mainline kernel and the "unknown opcode" issue is fixed.
* See if kernel boot option `mem=nopentium` makes a difference. In theory it should not...
* May be debugged using remote DMA over Firewire (The DMA busmastering hardware of FireWire can work even when the CPU is stuck with interrupts disabled, but the PCI bus and the DRAM controller must be alive). Quick Howto: Connect two boxes with Firewire, load ochi1394 on both, copy System.map from lockup machine to debug machine, install firescope (grep -r /firescope Documentation in 2.6.25rcX) run it and get dmesg buffer readout working, run the mmiostrace. If firescope is working in that lockup, you can also use a version of fireproxy (I think 0.33) to parse the RAM of the locked-up machine using gdb with debug symbols of the kernel. If you need help, ask benkai in freenode IRC.
* May be debugged using remote DMA over Firewire (The DMA busmastering hardware of FireWire can work even when the CPU is stuck with interrupts disabled, but the PCI bus and the DRAM controller must be alive). Quick Howto: Connect two boxes with Firewire, load ochi1394 on both, copy System.map from lockup machine to debug machine, install firescope (grep -r /firescope Documentation in 2.6.25rcX) run it and get dmesg buffer readout working, run the mmiostrace. If firescope is working in that lockup, you can also use a version of fireproxy (I think 0.33) to parse the RAM of the locked-up machine using gdb with debug symbols of the kernel.
## Null pointer dereferences in single step handler
......
......@@ -53,7 +53,7 @@ VP6+ | N/A | [[!color background=red text=TODO]] | [[!color background=red text=
VPE1/2 do not require any firmware to run. However, VP1/2/3/4/5 all require firmware to operate that is presently extracted from the NVIDIA binary driver. We cannot redistribute the firmware directly in linux-firmware because NVIDIA's license forbids redistribution of parts of their driver.
An effort is underway to fully reverse the underlying engines and create open-source firmware to provide out-of-the-box video decoding, please join us in #nouveau on irc.freenode.net if you're interested in helping.
An effort is underway to fully reverse the underlying engines and create open-source firmware to provide out-of-the-box video decoding, please join us in #nouveau on www.oftc.net if you're interested in helping.
If you are lucky, your distribution may already have a package for installing the firmwares. Here is a list of the supported distribution:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment