DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082014-05-28T22:54:41ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #2675 (New): Ultimate N WiFi Link 5300 get iwn_intr: fatal firmware error on 5GHzhttps://bugs.dragonflybsd.org/issues/26752014-05-28T22:54:41Zrevuwa
<p>I'm using a Lenovo Thinkad X200s with Intel Ultimate N WiFi Link 5300.</p>
<p>On Dragonfly BSD 3.6.2 it worked perfectly without any errors (and exactly the same configuration). Since 3.7.X and the actual testes 3.8.0RC my WiFi decive throws the following error on every try to load it (also over manual /etc/rc.d/netif restart):</p>
<ol>
<li>dmesg.boot (with rc_debug enabled) ###<br />iwn0: iwn_intr: fatal firmware error<br />firmware error log:<br /> error type = "SYSASSERT" (0x00000005)<br /> program counter = 0x00003130<br /> source line = 0x00000585<br /> error data = 0x0000000100000000<br /> branch link = 0x0000312A0000312A<br /> interrupt link = 0x0000091600000000<br /> time = 1270108785<br />driver status:<br /> tx ring 0: qid=0 cur=0 queued=0 <br /> tx ring 1: qid=1 cur=0 queued=0 <br /> tx ring 2: qid=2 cur=0 queued=0 <br /> tx ring 3: qid=3 cur=3 queued=0 <br /> tx ring 4: qid=4 cur=0 queued=0 <br /> tx ring 5: qid=5 cur=0 queued=0 <br /> tx ring 6: qid=6 cur=0 queued=0 <br /> tx ring 7: qid=7 cur=0 queued=0 <br /> tx ring 8: qid=8 cur=0 queued=0 <br /> tx ring 9: qid=9 cur=58 queued=0 <br /> tx ring 10: qid=10 cur=0 queued=0 <br /> tx ring 11: qid=11 cur=0 queued=0 <br /> tx ring 12: qid=12 cur=0 queued=0 <br /> tx ring 13: qid=13 cur=0 queued=0 <br /> tx ring 14: qid=14 cur=0 queued=0 <br /> tx ring 15: qid=15 cur=0 queued=0 <br /> tx ring 16: qid=16 cur=0 queued=0 <br /> tx ring 17: qid=17 cur=0 queued=0 <br /> tx ring 18: qid=18 cur=0 queued=0 <br /> tx ring 19: qid=19 cur=0 queued=0 <br /> rx ring: cur=11</li>
</ol>
<p>I just load 'iwn5000fw_load="YES"' over loader.conf, because the other modules (if_iwn.ko, wlan_ccmp.ko, wlan_tkip.ko) are loaded by the generic kernel. This is what I've loaded, too:</p>
<ol>
<li>kldstat ###<br />Id Refs Address Size Name<br /> 1 28 0xffffffff80200000 15a8710 kernel<br /> 2 1 0xffffffff817a9000 13020 snd_hda.ko<br /> 3 2 0xffffffff817bd000 31bf8 sound.ko<br /> 4 3 0xffffffff817ef000 bf758 acpi.ko<br /> 5 1 0xffffffff818af000 c7a0 ehci.ko<br /> 6 2 0xffffffff818bc000 f4c0 dm.ko<br /> 7 1 0xffffffff818cc000 1c4f8 dm_target_crypt.ko<br /> 8 4 0xffffffff827e9000 58d0 libiconv.ko<br /> 9 1 0xffffffff827ef000 20c8 libmchain.ko<br />10 1 0xffffffff827f2000 f98 msdos_iconv.ko<br />11 1 0xffffffff827f3000 f88 ntfs_iconv.ko<br />12 2 0xffffffff827f4000 10a38 ntfs.ko<br />13 1 0xffffffff82805000 fd0 cd9660_iconv.ko<br />14 1 0xffffffff82806000 5928 acpi_video.ko<br />15 1 0xffffffff8280c000 70c48 drm.ko<br />16 2 0xffffffff8287d000 2ec8 iicbus.ko<br />17 1 0xffffffff82880000 53fc8 iwn5000fw.ko<br />18 1 0xffffffff828d4000 1da8 coretemp.ko<br />19 1 0xffffffff828d6000 68d0 acpi_thinkpad.ko<br />20 1 0xffffffff828dd000 3dd0 est.ko<br />21 1 0xffffffff83042000 35000 pf.ko</li>
</ol>
<ol>
<li>rc.conf (relevant entries) ###<br />wlans_iwn0="wlan0" <br />ipv6_enable="YES" <br />ipv6_network_interfaces="wlan0" <br />ifconfig_wlan0="up DHCP WPA mode 11a"</li>
</ol>
<ol>
<li>wpa_supplicant.conf ###<br />ctrl_interface=/var/run/wpa_supplicant<br />eapol_version=2<br />network={<br /> ssid="my SSID name" <br /> priority=145<br />#scan_ssid=1<br /> proto=RSN<br /> key_mgmt=WPA-PSK <br /> pairwise=CCMP<br /> group=CCMP<br /> psk="my secure passphrase" <br />}</li>
</ol>
<ol>
<li>sysctl.conf (relevant entries) ###<br />net.inet6.ip6.use_tempaddr=1<br />net.inet6.icmp6.nodeinfo=0<br />net.inet6.icmp6.rediraccept=0</li>
</ol>
<p>In IRC at #dragonflybsd on EFNet <a class="user active user-mention" href="https://bugs.dragonflybsd.org/users/556">@profmakx</a> wrote: "I have iwn4965 and iwn6000, both work".</p>
<p>I've just tested (just for fun) to replace all that modules (if_iwn.ko, wlan_ccmp.ko, wlan_tkip.ko, iwn5000fw.ko) one by one and all together with the older one from v3.6.2. The result was exactly the same error.</p>
<p>I've found a FreeBSD issue with parallels:<br /><a class="external" href="http://www.marshut.com/sinuy/iwn-firmware-sysassert.html">http://www.marshut.com/sinuy/iwn-firmware-sysassert.html</a></p>
<p>Thanks in advance for any help!</p> DragonFlyBSD - Bug #2636 (Feedback): Add -x flag to iostat (a la solaris)https://bugs.dragonflybsd.org/issues/26362014-02-13T21:50:00Ztuxillo
<p>Add -x flag to iostat (a la solaris)</p> DragonFlyBSD - Bug #2631 (In Progress): Verify library versioning current with full package build...https://bugs.dragonflybsd.org/issues/26312014-02-13T21:46:57Ztuxillo
<p>Verify library versioning current with full package build and switch it on (after publishing packages)</p>
<p>most libraries complete and working now. libc/pthreads could be an issue.</p> DragonFlyBSD - Bug #2552 (New): hammer recovery should indicate progresshttps://bugs.dragonflybsd.org/issues/25522013-05-01T02:44:36Zphma
<p>I'm running hammer recover on a 55 GB partition of an IDE drive and it's been running for about a day. I have no idea how long it'll take. It would be a good idea if, every few minutes, hammer recover would output how many blocks it's read and how many are left, or just a percentage.</p> DragonFlyBSD - Bug #2529 (New): Sundance network adapter is not detected and attachedhttps://bugs.dragonflybsd.org/issues/25292013-03-21T14:13:29Zkworrc.kworr@gmail.com
<p>I have one of those ASUS NX1001 cards with Sundance controller. Current version doesn't correctly detects it.</p>
<p>pciconf -lv (snip):<br />none6@pci0:2:6:0: class=0x020000 card=0x82131043 chip=0x020013f0 rev=0x31 hdr=0x00<br /> vendor = 'Sundance Technology Inc / IC Plus Corp'<br /> device = 'IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY'<br /> class = network<br /> subclass = ethernet</p>
<p>In current FreeBSD (RELENG_9) it is detected as:</p>
<p>ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2<br />ste0: Ethernet address: 00:26:18:eb:37:85<br />miibus1: <MII bus> on ste0<br />ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1<br />ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto</p> DragonFlyBSD - Bug #2403 (New): newfs -E doesn't handle /dev/serno device names properlyhttps://bugs.dragonflybsd.org/issues/24032012-08-17T12:07:45Zftigeot
<p>Trying to run this command fails:</p>
<pre><code>newfs_hammer -E -L USR_OBJ /dev/serno/00000000112233445566</code></pre>
<pre><code>Device:/dev/serno/00000000112233445566 (kern.cam.da.rno/00000000112233445566.trim_enabled) does not support the TRIM command<br /> usage: newfs_hammer -L label [-Ef] [-b bootsize] [-m savesize] [-u undosize]<br /> [-V version] special ...</code></pre>
<p>The only trim_enabled sysctls id are of the form<br /> kern.cam.da.0.trim_enabled<br /> kern.cam.da.1.trim_enabled<br /> kern.cam.da.2.trim_enabled<br /> etc...</p>
<p>It seems newfs -E only expects drive names to be of the form /dev/daX<br />TRIM options in other utilities such as fdisk or disklabel may have the same issue</p> DragonFlyBSD - Bug #2095 (New): Running installer post-install: Unsupported DFUI transport ''https://bugs.dragonflybsd.org/issues/20952011-06-26T16:20:49Zgreenrd
<p>If you try to run installer on an installed system to reconfigure it, you get:</p>
<p>Starting installer. /etc/pfi.conf not found, starting interactive install.<br />Unsupported DFUI transport ''.</p> DragonFlyBSD - Bug #2020 (New): Port brcm80211 driver from Linux to DragonFly BSDhttps://bugs.dragonflybsd.org/issues/20202011-03-06T06:54:10Zstuder
<p>In September 2010, Broadcom released a full opensource version under BSD licence <br />of their driver for part of their WLAN hardware (BCM43224, BCM43225, BCM4313 <br />(PCIe NIC)).</p>
<p>That would be so nice if this could be added to DragonFly BSD.</p>
<p>For more information, see :<br />- <a class="external" href="http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418">http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418</a><br />- <a class="external" href="http://wireless.kernel.org/en/users/Drivers/brcm80211">http://wireless.kernel.org/en/users/Drivers/brcm80211</a></p> DragonFlyBSD - Bug #1982 (New): There is no linuxulator on x86-64https://bugs.dragonflybsd.org/issues/19822011-02-04T21:53:04Zherrgard
<p>The linuxulator would have to be ported from x86.</p> DragonFlyBSD - Bug #1947 (New): GA-880GM-UD2H (rev. 1.3) AHCI fails to detect disks at the end of...https://bugs.dragonflybsd.org/issues/19472010-12-31T22:46:34Zeocallaghan
<p>Attached is the verbose boot of the machine when two 1TB disks are in a RAID 1<br />behind the controller. If the AMD RAID controller is set to AHCI mode the disks<br />show fine.</p>
<ul>
<li>Background:</li>
</ul>
<p>Board:<br /><a class="external" href="http://www.gigabyte.com/products/product-page.aspx?pid=3475#sp">http://www.gigabyte.com/products/product-page.aspx?pid=3475#sp</a></p>
<p>Southbridge chipset data sheet:<br /><a class="external" href="http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBIQFjAA&url=http%3A%2F%2Fdeveloper.amd.com%2Fassets%2F45215_sb710_ds_pub_1.25.pdf&rct=j&q=AMD%20SB710%20raid%20controller&ei=6-EdTb3dDZHwvwPp9-XwDQ&usg=AFQjCNH7gThMfcsRKvLicnmwBIJR1lSbRQ&cad=rja">http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBIQFjAA&url=http%3A%2F%2Fdeveloper.amd.com%2Fassets%2F45215_sb710_ds_pub_1.25.pdf&rct=j&q=AMD%20SB710%20raid%20controller&ei=6-EdTb3dDZHwvwPp9-XwDQ&usg=AFQjCNH7gThMfcsRKvLicnmwBIJR1lSbRQ&cad=rja</a></p> DragonFlyBSD - Bug #1882 (New): Idea for handling new USB vendor/device codeshttps://bugs.dragonflybsd.org/issues/18822010-10-20T17:22:04Zbmk
<p>This is just an idea / wish.</p>
<p>Have a config file called /etc/usb_hotwire.conf</p>
e.g.:
<ol>
<li>This file allows you to map a new unsupported usb vendor/device code</li>
<li>to an existing usb vendor/device code supported by a driver.</li>
<li>File Format:</li>
<li><unsupported vendor code>:<unsupported device code> <supported vendor<br />code>:<supported device code></li>
</ol>
<ol>
<li>The following makes my unsupported USB wireless adapter use the same driver<br />(rum) as a D-Link DWL-G122</li>
</ol>
<p>0x1044:0x2573 0x07d1:0x3c03</p> DragonFlyBSD - Bug #1313 (New): Signal code in kernel needs major overhaul (signal queues, si_cod...https://bugs.dragonflybsd.org/issues/13132009-03-13T15:04:10Zhasso
<p>Although our siginfo structure has a si_code member, we don't use it and <br />don't even have a defines related to it.</p>
<p><a class="external" href="http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html">http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html</a></p> DragonFlyBSD - Bug #1148 (In Progress): BCM4311 wireless network adapter detected but not functionalhttps://bugs.dragonflybsd.org/issues/11482008-10-09T12:27:01Zarchimedes.gaviola
<p>Hi,</p>
<p>I have a mini-PCI wireless network adapter on my laptop that wasn't<br />detected on DragonFly 2.0.0 during installation. Since it wasn't<br />detected, what I did is performing the steps in the<br />bwi(4) manual <a class="external" href="http://leaf.dragonflybsd.org/cgi/web-man?command=bwi&section=ANY">http://leaf.dragonflybsd.org/cgi/web-man?command=bwi&section=ANY</a><br />and download the firmware at<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/bwi/v3.tbz">http://leaf.dragonflybsd.org/~sephe/bwi/v3.tbz</a>. Now, the driver were<br />detected (Broadcom BCM4311) but seems not functional. It doesn't show<br />up after invoking ifconfig. Below is the dmesg output:</p>
<p>device_probe_and_attach: bwi0 attach returned 6<br />Preloaded elf module "/modules/if_bwi.ko" at 0xc07b93c8.<br />bwi0: <Broadcom BCM4311 802.11 Wireless Lan> mem 0x31300000-0x31303fff<br />irq 11 at device 0.0 on pci1<br />bwi0: BBP: id 0x4311, rev 0x2, pkg 0<br />bwi0: MAC rev 13 is not supported<br />bwi0: no MAC was found</p>
<p>And as I try looking at the /usr/src/sys/dev/netif/bwi/if_bwi.c code,<br />BCM4311 is part of the supported device</p>
<pre><code>{ PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM4311,<br /> "Broadcom BCM4311 802.11 Wireless Lan" },</code></pre>
<p>Thanks,<br />Archimedes</p> DragonFlyBSD - Bug #725 (In Progress): 'make distribution' fails w/'ro' /usr/objhttps://bugs.dragonflybsd.org/issues/7252007-07-10T09:42:05Zc.turner
<p>This seems to choke on sendmail from a ~1wk build<br />(no code changes on this part of the tree it seems)</p>
<p>not sure if it is 'supposed to work' or<br />for how long it has been broken, so I didn't investigate further..</p>
<p>basically, trying to use a -HEAD machine to build out jail<br />images from a release machine over ro nfs..</p>
<p>Thanks,</p>
<p>- Chris</p> DragonFlyBSD - Bug #285 (Feedback): interrupt latency with re without ip address configuredhttps://bugs.dragonflybsd.org/issues/2852006-08-07T06:00:07Zthomas.nikolajsen
<p>Playing sound using pcm(4)/snd(4) gives bad quality: hiss and hops, like sound isn't playing for very short time periods.</p>
<p>This is experienced:<br /> - not having SMP in kernel config (eg GENERIC)<br /> - from dfly-1.5 26th December '05 (24th is ok using kernels from chlamydia);<br />including HEAD.</p>
<p>dfly-1.4 is ok, including 1.4.4.</p>
<p>Using audio/mpg123 for MP3, 'cp test.raw /dev/dspW' or pcmplay for decoded sound.<br />Buffering audio data with mpg123 -b doesn't sound like making any difference.</p>
<p>CPU load doesn't sound like making any difference.<br />Problem experienced on several systems, using snd_via8233 and snd_ich.</p>
<p>No X11 used.</p>
<pre><code>-thomas</code></pre>