Bug 149373 - [realtek/atheros]: None of my network card working
Summary: [realtek/atheros]: None of my network card working
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
Depends on:
Reported: 2010-08-07 00:40 UTC by Putu Nano
Modified: 2018-05-28 19:44 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Putu Nano 2010-08-07 00:40:01 UTC
I installed PC-BSD in Laptop Toshiba Satellite T135D-S1320, but none of my network card are working.

[nano@pcbsd-5277] /home/nano# pciconf -lv | grep -B3 network
alc0@pci0:8:0:0:        class=0x020000 card=0xffe01179 chip=0x10621969 rev=0xc0 hdr=0x00
    vendor     = 'Attansic (Now owned by Atheros)'
    device     = 'Atheros AR8132 PCI-E Fast Ethernet Controller (AR8132)'
    class      = network
none1@pci0:9:0:0:       class=0x028000 card=0x818110ec chip=0x817210ec rev=0x10 hdr=0x00
    vendor     = 'Realtek Semiconductor'
    device     = 'Realtek RTL8191SE wireless LAN 802.11N PCI-E NIC (RTL8191SE ?)'
    class      = network

[nano@pcbsd-5277] /dev# dmesg | grep alc0
alc0: <Atheros AR8132 PCIe Fast Ethernet> port 0xc000-0xc07f irq 17 at device 0.0 on pci8
alc0: 0x40000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
alc0: cannot allocate memory resources.
device_attach: alc0 attach returned 6
Comment 1 Remko Lodder freebsd_committer 2010-09-05 11:50:10 UTC
Responsible Changed
From-To: freebsd-i386->freebsd-net

This is more networkish then i386-ish
Comment 2 Adrian Chadd freebsd_committer 2011-04-11 12:39:58 UTC
Responsible Changed
From-To: freebsd-net->freebsd-wireless

punt to wireless list
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:53 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
- Untouched since 2018-01-01.
- Affects Base System OR Documentation


Reset to open status.

I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.