[Hardware] Asus F5N, network devices

[Hardware] Asus F5N, network devices

[Yuriy Al. Shirokov]

Доброго времени суток!

Пытаюсь заставить работать ALD4.0 на Asus F5N. Главная проблема --- не
работают оба сетевых адаптера. Если верить выводу lspci, это
00:0a.0 Ethernet controller: nVidia corporation unknown device 054c (rev a2)
(Ethernet-карта) и
05:00.0 Ehternet controller: Ahteros Communications, Inc. Unknown
device 001c (rev 01)
(WiFi-модуль).

WiFi инсталятор, кажется, опознал --- в ядре после загрузки сидит
модуль ath_pci. Модуль forcedeth для ethernet-карты пришлось
прописывать самостоятельно.

Файл /etc/net/ifaces/eth0:
MODULE=forcedeth
BOOTPROTO=dhcp

Файл /etc/net/ifaces/eth1:
MODULE=ath_pci
BOOTPROTO=dhcp

При service network restart сообщает:
...
Starting group 1/realphys (2 interfaces)
     Starting eth0: .SIOCGIFFLAGS: No such device
..OK
     Starting eth1: .SIOCGIFFLAGS: No such device
..OK
...

С этим можно что-нибудь сделать?

-- 
С уважением,
Ю.А.Широков.

Re: [Hardware] Asus F5N, network devices

[Konstantin A. Lepikhov]

Hi Yuriy!

Sunday 10, at 08:37:05 PM you wrote:

> Доброго времени суток!
> 
> Пытаюсь заставить работать ALD4.0 на Asus F5N. Главная проблема --- не
> работают оба сетевых адаптера. Если верить выводу lspci, это
> 00:0a.0 Ethernet controller: nVidia corporation unknown device 054c (rev a2)
> (Ethernet-карта) и
> 05:00.0 Ehternet controller: Ahteros Communications, Inc. Unknown
> device 001c (rev 01)
> (WiFi-модуль).
> 
> WiFi инсталятор, кажется, опознал --- в ядре после загрузки сидит
> модуль ath_pci. Модуль forcedeth для ethernet-карты пришлось
> прописывать самостоятельно.
> 
> Файл /etc/net/ifaces/eth0:
> MODULE=forcedeth
> BOOTPROTO=dhcp
> 
> Файл /etc/net/ifaces/eth1:
> MODULE=ath_pci
> BOOTPROTO=dhcp
> 
> При service network restart сообщает:
> ...
> Starting group 1/realphys (2 interfaces)
>      Starting eth0: .SIOCGIFFLAGS: No such device
> ..OK
>      Starting eth1: .SIOCGIFFLAGS: No such device
> ..OK
> ...
> 
> С этим можно что-нибудь сделать?
А что в dmesg? Помогает ли обновление ядра до std-smp-alt11?

-- 
WBR et al.

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Konstantin A. Lepikhov пишет:
>> Пытаюсь заставить работать ALD4.0 на Asus F5N. Главная проблема --- не
>> работают оба сетевых адаптера.
...
>> С этим можно что-нибудь сделать?
> А что в dmesg? Помогает ли обновление ядра до std-smp-alt11?

В dmesg --- ничего. Совсем. Т.е. service network restart вообще не
оставляет следов в /var/log/messages.

Ядро std-smp-alt11 --- оно в branch лежит (конкретно сейчас пока нет под
рукой этого ноута, и вообще машины под ALD4)? Какие репозитарии надо
прописать в ALD4, установленный с диска, чтобы его поставить?

Кстати, есть в рассылке кто-то, у кого работают wifi-карточка Ahteros
и/или набортная сетевуха nForce?

- --
С уважением,
Ю.А.Широков.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR69v8+dMeS2DDLCcAQKtcgP/WQXwUTOSZpFK3Dub8DOg7mfjngXt6oML
Y17v1VQ+JikELf1u794lt26B/Ivbz+BAIO6o7Ngs5ho0I3sxNLoGGc9EuIs2a24Y
JtCK9vSHhzHeIKVy+s5SNftuogV6ykjxNm/1bQ4XOAxgW31dxOhDJIlsT1q40ATh
uCakLEdKbsc=
=YUQ/
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Konstantin A. Lepikhov пишет:
>> Пытаюсь заставить работать ALD4.0 на Asus F5N. Главная проблема --- не
>> работают оба сетевых адаптера.>> Файл /etc/net/ifaces/eth1:
...
>> MODULE=ath_pci
>> BOOTPROTO=dhcp
...
>> С этим можно что-нибудь сделать?
> А что в dmesg? Помогает ли обновление ядра до std-smp-alt11?

Я так и не нашёл std-smp-alt11, обновился до std-smp-alt12 из branch.

Обычная ethernet-карта заработала, спасибо! С wifi всё то же ---
SIOCGIFFLAGS: No such device

У кого-нибудь она работает с madwifi? А с ndiwrapper?

- --
С уважением,
Ю.А.Широков.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7hvmudMeS2DDLCcAQKudwP/UEjgO5enE7TMdog94Q6eKeMNIAVy96Yx
c7xTl6J57ELv+jMel3y4quMBzTmq/JL7U73i7AXGx6CGUCYR+QBdXaoTmB7feIWr
zCkGpFlEYyfsp1NPX4+aaVR6BGLj+7rpeByafn91mOGxWpBMroameDrfkJE/uUSb
0PuQVBtEo+A=
=rlgK
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Sergey Vlasov]

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Sun, Feb 17, 2008 at 08:32:10PM +0300, Yuriy Shirokov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Konstantin A. Lepikhov пишет:
> >> Пытаюсь заставить работать ALD4.0 на Asus F5N. Главная проблема --- не
> >> работают оба сетевых адаптера.>> Файл /etc/net/ifaces/eth1:
> ...
> >> MODULE=ath_pci
> >> BOOTPROTO=dhcp
> ...
> >> С этим можно что-нибудь сделать?
> > А что в dmesg? Помогает ли обновление ядра до std-smp-alt11?
> 
> Я так и не нашёл std-smp-alt11, обновился до std-smp-alt12 из branch.
> 
> Обычная ethernet-карта заработала, спасибо! С wifi всё то же ---
> SIOCGIFFLAGS: No such device
> 
> У кого-нибудь она работает с madwifi? А с ndiwrapper?

Всё-таки покажите вывод dmesg.

Скорее всего, wifi использует слишком новый чипсет, который не
поддерживается текущей версией драйверов madwifi (к сожалению, в
выпущенной только что версии http://madwifi.org/wiki/Releases/0.9.4
поддержка новых чипсетов не добавилась, зато исправлены проблемы
совместимости с ядром 2.6.24).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yuriy Shirokov пишет:
> Konstantin A. Lepikhov пишет:
>>> Пытаюсь заставить работать ALD4.0 на Asus F5N.
> Обычная ethernet-карта заработала, спасибо! С wifi всё то же ---
> SIOCGIFFLAGS: No such device

На странице madwifi есть вот такое:
http://madwifi.org/wiki/UserDocs/Troubleshooting#OnRedHatIgetSIOCGIFFLAGS:Nosuchdevice.

Рекомендуют для устранения этой ошибки отредактировать
/etc/modules.conf, переименовав eth1 в ath0, и соответствующим образом
поправить network-scripts. Почему это работает? В рамках etcnet можно
сделать что-то аналогичное?

- --
С уважением,
Ю.А.Широков.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7h2tOdMeS2DDLCcAQLMugP+IpLmXbO2MhVwoCJxV6PNAsHoXsLVQIFX
GiAIQH0MIS5znUQVjUQPqifpHtDxDhJS12DJCmPK6Kn9AXC9F9H89SYfvkQQV0At
uvc+TmOsflf1eDtFlrl3AMGbpCLF4Tv+WJnBBNvy+KRfjHnDbE2cKrLzvJHOfjOh
iAvekR2hVP8=
=BPuS
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Sergey Vlasov]

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

On Sun, Feb 17, 2008 at 10:01:51PM +0300, Yuriy Shirokov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Sergey Vlasov пишет:
> > Всё-таки покажите вывод dmesg.
> 
> Сейчас в результате service network restart там такое:
[skip]

Из этого фрагмента можно понять только то, что драйвер forcedeth из
нового ядра заработал (либо, как минимум, хорошо делает вид, что
работает).  Сообщения от драйверов madwifi (ath_hal и т.п.) выводятся
существенно раньше.

Нужен полный вывод dmesg, содержащий все сообщения с момента загрузки.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergey Vlasov пишет:
> Всё-таки покажите вывод dmesg.

Сейчас в результате service network restart там такое:
CPI: PCI interrupt for device 0000:00:0a.0 disabled
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
PCI: Enabling device 0000:00:0a.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 21 (level,
low) -> IRQ 209
PCI: Setting latency timer of device 0000:00:0a.0 to 64
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01043:1697 bound to 0000:00:0a.0
eth0: no link during initialization.
eth0: link up.
[root@home2680 sources.list.d]# ACPI: PCI interrupt for device
0000:00:0a.0 disabled
bash: ACPI:: command not found

- --
С уважением,
Ю.А.Широков.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7iEn+dMeS2DDLCcAQKNiAQAsDsN1g0xmE2vFIq2YlFTMLgS/UmC2lmp
M37VgmZZ1mzFF1qruBVI9KWr6MJGWLQaFPmrKK3/2nj+J2p5N099JVPDdbryYedw
oomDk/YACknq33TB7voK//icUh3FbNNZzh4Tr5+2/HbqSNO+nybZ8XAbCLI5F6dc
MoP9ev5x1Ww=
=FW1a
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergey Vlasov пишет:
> Всё-таки покажите вывод dmesg.

Ой. Прошу прощения за неаккуратный copy/paste. Собственно лог кончается
на eth0: link up, конечно.

- --
С уважением,
Ю.А.Широков.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7iF4+dMeS2DDLCcAQLRxwP/TbkZAOhh4CUUlo540w+0JkurKhviYlRU
qkDI4KBdXItJx4kIMXqEGsY7GQuRYU7HOkkNR6DaVkliLFiwjzPNoxRs5gEaZ2GI
PRPbks6u4DgakNMMCvPn1ovlSK7LcXUvXpNi30dJq8FIPOVTYhZdlGPVniuhNSG6
B90X4Xl0vPQ=
=1OyB
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergey Vlasov пишет:
> Из этого фрагмента можно понять только то, что драйвер forcedeth из
> нового ядра заработал (либо, как минимум, хорошо делает вид, что
> работает).  Сообщения от драйверов madwifi (ath_hal и т.п.) выводятся
> существенно раньше.
> 
> Нужен полный вывод dmesg, содержащий все сообщения с момента загрузки.

Полный вывод в аттаче, но, кажется, я уже нашёл нужное место.

...
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.3.3)
ath_pci: 0.9.4.5 (0.9.3.3)
ACPI: PCI Interrupt Link [LNED] enabled at IRQ 19
ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNED] -> GSI 19 (level,
low) -> IRQ 201
PCI: Setting latency timer of device 0000:05:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware revision not supported'
(HAL status 13)
ACPI: PCI interrupt for device 0000:05:00.0 disabled
...

Судя по строке 'Hardware revision not supported', вы, кажется, оказались
правы --- слишком свежий чипсет. Спасибо за советы, попробую теперь
ndiswrapper.

- --
С уважением,
Ю.А.Широков.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7iO4udMeS2DDLCcAQLiawP/X+JZGJMvV2oaCOQp1Uu8vTbed29ZdlZ5
DAOmpnWvzVfSrZjgoLSJLobR4SJtTliFudVGakP7EjDVoIeIJRx2WSfc5YU9DQ+1
PviJ/Vb62ozD2D6InWC4hDMCOM4XPEnRqdL7drv8a+CO6OrVSdkdCYxW9yQKy3IB
GIQaqdg4ED4=
=J+80
-----END PGP SIGNATURE-----

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 21499 bytes --]

Linux version 2.6.18-std-smp-alt12 (builder@apiary.armor.altlinux.org) (gcc version 4.1.1 20070105 (ALT Linux, build 4.1.1-alt12)) #1 SMP Mon Feb 11 00:44:54 MSK 2008
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000037fa8000 (usable)
 BIOS-e820: 0000000037fa8000 - 0000000037fb0000 (ACPI NVS)
 BIOS-e820: 0000000037fb0000 - 0000000037fbe000 (ACPI data)
 BIOS-e820: 0000000037fbe000 - 0000000038000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
 BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
895MB LOWMEM available.
found SMP MP-table at 000ff780
On node 0 totalpages: 229288
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 225192 pages, LIFO batch:31
DMI present.
ACPI: RSDP (v000 ACPIAM                                ) @ 0x000f9c00
ACPI: RSDT (v001 _ASUS_ Notebook 0x20070816 MSFT 0x00000097) @ 0x37fb0000
ACPI: FADT (v002 081607 FACP0918 0x20070816 MSFT 0x00000097) @ 0x37fb0200
ACPI: MADT (v001 081607 APIC0918 0x20070816 MSFT 0x00000097) @ 0x37fb0390
ACPI: MCFG (v001 081607 OEMMCFG  0x20070816 MSFT 0x00000097) @ 0x37fb0440
ACPI: SLIC (v001 _ASUS_ Notebook 0x20070816 MSFT 0x00000097) @ 0x37fb0480
ACPI: DBGP (v001 081607 DBGP0918 0x20070816 MSFT 0x00000097) @ 0x37fb0400
ACPI: BOOT (v001 081607 BOOT0918 0x20070816 MSFT 0x00000097) @ 0x37fb0600
ACPI: OEMB (v001 081607 OEMB0918 0x20070816 MSFT 0x00000097) @ 0x37fbe040
ACPI: HPET (v001 081607 OEMHPET0 0x20070816 MSFT 0x00000097) @ 0x37fb9cb0
ACPI: SSDT (v001  AMI   POWERNOW 0x00000001 AMD  0x00000001) @ 0x37fb9cf0
ACPI: DSDT (v001  F5N00 F5N00001 0x00000001 INTL 0x20051117) @ 0x00000000
ACPI: PM-Timer IO Port: 0x508
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:8 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:8 APIC version 16
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
ACPI: HPET id: 0x10de8201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 40000000 (gap: 38000000:c6c00000)
Detected 1893.244 MHz processor.
Built 1 zonelists.  Total pages: 229288
Kernel command line: auto BOOT_IMAGE=2618-std-smp-12 ro root=803 panic=30 splash=silent resume=/dev/sdb5
bootsplash: silent mode.
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
spurious 8259A interrupt: IRQ7.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 905032k/917152k available (1591k kernel code, 11680k reserved, 638k data, 192k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
hpet0: at MMIO 0xfed00000 (virtual 0xf8800000), IRQs 2, 8, 31
hpet0: 3 32-bit timers, 25000000 Hz
Using HPET for base-timer
Calibrating delay using timer specific routine.. 3790.02 BogoMIPS (lpj=7580054)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f
CPU: After vendor identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0(2) -> Core 0
CPU: After all inits, caps: 178bfbff ebd3fbff 00000000 00000410 00002001 00000000 0000011f
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
checking if image is initramfs... it is
Freeing initrd memory: 505k freed
ACPI: Core revision 20060707
ACPI: Looking for DSDT in initramfs... /DSDT.aml does not exist.
CPU0: AMD Turion(tm) 64 X2 Mobile Technology TL-58 stepping 02
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3786.26 BogoMIPS (lpj=7572530)
CPU: After generic identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f
CPU: After vendor identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1(2) -> Core 1
CPU: After all inits, caps: 178bfbff ebd3fbff 00000000 00000410 00002001 00000000 0000011f
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: AMD Turion(tm) 64 X2 Mobile Technology TL-58 stepping 02
Total of 2 processors activated (7576.29 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: 
CPU#0 had -170 usecs TSC skew, fixed it up.
CPU#1 had 170 usecs TSC skew, fixed it up.
Brought up 2 CPUs
migration_cost=195
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
Error attaching device data
Error attaching device data
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:12.0
PCI: Transparent bridge - 0000:00:08.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 35) interrupt mode.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNEA] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNEB] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNEC] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNED] (IRQs 16 17 18 19) *7
ACPI: PCI Interrupt Link [LUB0] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LUB2] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [LAZA] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [SGRU] (IRQs 20 21 22 23) *10
ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *11
ACPI: PCI Interrupt Link [LPMU] (IRQs 20 21 22 23) *7
ACPI: PCI Interrupt Link [LSA0] (IRQs 20 21 22 23) *5
ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [UB11] (IRQs 20 21 22 23) *7
ACPI: PCI Interrupt Link [UB12] (IRQs 20 21 22 23) *7
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:09: ioport range 0x250-0x253 has been reserved
pnp: 00:09: ioport range 0x256-0x25f has been reserved
pnp: 00:0b: ioport range 0x5000-0x507f has been reserved
pnp: 00:0b: ioport range 0x5080-0x50ff has been reserved
PCI: Bridge: 0000:00:08.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:0c.0
  IO window: e000-efff
  MEM window: fd800000-feafffff
  PREFETCH window: f8000000-faffffff
PCI: Bridge: 0000:00:0d.0
  IO window: disabled.
  MEM window: feb00000-febfffff
  PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:08.0 to 64
PCI: Setting latency timer of device 0000:00:0c.0 to 64
PCI: Setting latency timer of device 0000:00:0d.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag at 0x52 set to 0x1
audit: initializing netlink socket (disabled)
audit(1203283029.628:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:0c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0c.0:pcie00]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0d.0:pcie00]
vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 3750k, total 131072k
vesafb: mode is 800x600x16, linelength=1600, pages=2
vesafb: protected mode interface info at c000:d750
vesafb: pmi: set display start = c00cd786, set palette = c00cd7f0
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003 d103 d203 d303 d403 d503 da03 ff03 
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 64511 bytes,<6>...found (800x600, 12886 bytes, v3).
Console: switching to colour frame buffer device 97x34
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
NET: Registered protocol family 1
Using IPI No-Shortcut mode
ACPI: (supports S0 S3 S4 S5)
Time: hpet clocksource has been installed.
Freeing unused kernel memory: 192k freed
Executing init=/init
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-MCP67: IDE controller at PCI slot 0000:00:06.0
NFORCE-MCP67: chipset revision 161
NFORCE-MCP67: not 100% native mode: will probe irqs later
NFORCE-MCP67: 0000:00:06.0 (rev a1) UDMA133 controller
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard as /class/input/input0
hda: HL-DT-ST DVDRAM GSA-T20N, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
SCSI subsystem initialized
libata version 2.00 loaded.
ahci 0000:00:09.0: version 2.0
ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:09.0 to 64
ahci 0000:00:09.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl IDE mode
ahci 0000:00:09.0: flags: 64bit led clo pmp pio 
ata1: SATA max UDMA/133 cmd 0xF882C100 ctl 0x0 bmdma 0x0 irq 193
ata2: SATA max UDMA/133 cmd 0xF882C180 ctl 0x0 bmdma 0x0 irq 193
ata3: SATA max UDMA/133 cmd 0xF882C200 ctl 0x0 bmdma 0x0 irq 193
ata4: SATA max UDMA/133 cmd 0xF882C280 ctl 0x0 bmdma 0x0 irq 193
scsi0 : ahci
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 234441648 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ahci
ata2: SATA link down (SStatus 0 SControl 300)
scsi2 : ahci
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : ahci
ata4: SATA link down (SStatus 0 SControl 300)
  Vendor: ATA       Model: ST9120822AS       Rev: 3.AL
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
sd 0:0:0:0: Attached scsi disk sda
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.3.3)
ath_pci: 0.9.4.5 (0.9.3.3)
ACPI: PCI Interrupt Link [LNED] enabled at IRQ 19
ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNED] -> GSI 19 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:05:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
ACPI: PCI interrupt for device 0000:05:00.0 disabled
usbcore: registered new driver usbfs
usbcore: registered new driver hub
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 22 (level, low) -> IRQ 209
PCI: Setting latency timer of device 0000:00:0a.0 to 64
forcedeth: using HIGHDMA
sd 0:0:0:0: Attached scsi generic sg0 type 0
input: PC Speaker as /class/input/input1
hda: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Linux agpgart interface v0.102 (c) Dave Jones
eth0: forcedeth.c: subsystem: 01043:1697 bound to 0000:00:0a.0
ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUB2] -> GSI 21 (level, low) -> IRQ 217
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: irq 217, io mem 0xfd77ec00
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ACPI: PCI Interrupt Link [UB12] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:04.1[B] -> Link [UB12] -> GSI 20 (level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:04.1 to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:04.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:04.1
ehci_hcd 0000:00:04.1: irq 225, io mem 0xfd77e800
ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 5 ports detected
ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUB0] -> GSI 23 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:02.0: irq 193, io mem 0xfd77f000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 5 ports detected
Synaptics Touchpad, model: 1, fw: 6.1, id: 0xa3a0b3, caps: 0xa04713/0x10008
input: SynPS/2 Synaptics TouchPad as /class/input/input2
usb 1-3: new high speed USB device using ehci_hcd and address 2
ts: Compaq touchscreen protocol output
ACPI: PCI Interrupt Link [UB11] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [UB11] -> GSI 22 (level, low) -> IRQ 209
PCI: Setting latency timer of device 0000:00:04.0 to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:04.0: irq 209, io mem 0xfd77d000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
usb 1-3: configuration #1 chosen from 1 choice
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LAZA] -> GSI 21 (level, low) -> IRQ 217
PCI: Setting latency timer of device 0000:00:07.0 to 64
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 1 choice
usbcore: registered new driver libusual
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [SGRU] -> GSI 20 (level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:12.0 to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module  169.09  Fri Jan 11 14:38:28 PST 2008
Adding 614288k swap on /dev/sda5.  Priority:-1 extents:1 across:614288k
EXT3 FS on sda3, internal journal
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
  Vendor: Generic-  Model: xD/SDMMC/MS/Pro   Rev: 1.00
  Type:   Direct-Access                      ANSI SCSI revision: 00
sd 4:0:0:0: Attached scsi removable disk sdb
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda10, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
fuse init (API version 7.7)
NET: Registered protocol family 17
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Lid Switch [LID]
ACPI: Thermal Zone [THRM] (56 C)
ACPI: AC Adapter [AC0] (on-line)
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 64511 bytes,<6>...found (800x600, 12886 bytes, v3).
bootsplash: status on console 1 changed to on
usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
  Vendor: JetFlash  Model: TS512MJF2B/2L     Rev: 2.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
ready
SCSI device sdc: 1022720 512-byte hdwr sectors (524 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
SCSI device sdc: 1022720 512-byte hdwr sectors (524 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
 sdc: sdc1
sd 5:0:0:0: Attached scsi removable disk sdc
sd 5:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
usb 1-1: USB disconnect, address 4
usb 1-1: new high speed USB device using ehci_hcd and address 5
usb 1-1: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
  Vendor: JetFlash  Model: TS512MJF2B/2L     Rev: 2.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
ready
SCSI device sdc: 1022720 512-byte hdwr sectors (524 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
SCSI device sdc: 1022720 512-byte hdwr sectors (524 MB)
sdc: Write Protect is off
sdc: Mode Sense: 03 00 00 00
sdc: assuming drive cache: write through
 sdc: sdc1
sd 6:0:0:0: Attached scsi removable disk sdc
sd 6:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

C ndiswrapper беспроводная сеть тоже отказывается работать.

/etc/net/ifaces/eth1/options сейчас выглядит так:
MODULE=ndiswrapper
BOOTPROTO=yes
ONBOOT=yes

Виндовский драйвер вроде встал: ndiswrapper -l сообщает
net5211: driver installer
	device (168C:001C) present (alternate driver: ath_pci)

Но при попытке перезапустить сеть всё то же самое сообщение:
SIOCGIFFLAGS: No such device

А в логах вот что:
...
ndiswrapper version 1.47 loaded (smp=yes)
ndiswrapper: driver net5211 (,05/02/2007,5.3.0.45) loaded
PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNED] -> GSI 19 (level,
low) -> IRQ 201
ndiswrapper (ZwClose:2246): closing handle 0xf37307a8 not implemented
PCI: Setting latency timer of device 0000:05:00.0 to 64
ndiswrapper (NdisWriteErrorLogEntry:192): log: C0001389, count: 4,
return_address: f95eb064
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xedeb0000
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0x28
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xf8cf0000
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xf8cf0000
ndiswrapper (mp_init:216): couldn't initialize device: C000009A
ndiswrapper (pnp_start_device:439): Windows driver couldn't initialize
the device (C0000001)
ndiswrapper (mp_halt:258): device e92f6400 is not initialized - not halting
ndiswrapper: device eth%d removed
ACPI: PCI interrupt for device 0000:05:00.0 disabled
ndiswrapper: probe of 0000:05:00.0 failed with error -22
usbcore: registered new driver ndiswrapper
ACPI: PCI interrupt for device 0000:00:0a.0 disabled
...

Это в момент засовывания ndiswrapper в ядро при помощи modprobe,
насколько я понимаю.

- --
С уважением,
Ю.А.Широков.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7ie+OdMeS2DDLCcAQLuwgQAvxpk7n4nG28s+yuVsc0qZ8Jiz4CfRl0d
QH9zcHkzVWPUzl9+yBnburaftqcD86w7QixAiXiMTyE063oELxQpkrm2YsizaREr
oQHEM548HTJy7Aqpcra2gZqyjuJZsRAueNS2djuR2vy+Cx35/kuTB5icMOZgdCLp
KBU0EWCV+qQ=
=cgFH
-----END PGP SIGNATURE-----

Re: [Hardware] Asus F5N, network devices

[Dmitriy Kruglikov]

17.02.08, Yuriy Shirokov написал(а):
> ndiswrapper: device eth%d removed
Вот эта строка наводит на мысль...
У нас же ж ath* ...
Может тут собака порылась ?

-- 
Best regards,
 Dmitriy L. Kruglikov
 Dmitriy.Kruglikov_at_gmail_dot_com
 DKR6-RIPE
 DKR6-UANIC
 XMPP: Dmitriy.Kruglikov_at_gmail_dot_com

Re: [Hardware] Asus F5N, network devices

[Sergey Kurakin]

Здравствуйте.

On 17 February 2008, Yuriy Shirokov wrote:
> C ndiswrapper беспроводная сеть тоже отказывается работать.
> 
> Виндовский драйвер вроде встал: ndiswrapper -l сообщает
> net5211: driver installer
> 	device (168C:001C) present (alternate driver: ath_pci)
> 
> Но при попытке перезапустить сеть всё то же самое сообщение:
> SIOCGIFFLAGS: No such device

   Загруженный модуль ath_pci не даст работать ndiswrapper'у.
   Попробуйте ath_pci поставить в blacklist. Или удалите пакет с 
модулями madwifi.

-- 
WBR,
Sergey Kurakin

Re: [Hardware] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dmitriy Kruglikov пишет:
> 17.02.08, Yuriy Shirokov написал(а):
>> ndiswrapper: device eth%d removed
> Вот эта строка наводит на мысль...
> У нас же ж ath* ...
> Может тут собака порылась ?

Нет, карту с ndiswrapper я описывал как eth1 (с madwifi пробовал и так,
и так).

- --
С уважением,
Ю.А.Широков.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7mClOdMeS2DDLCcAQLjtAP9GJAJ2QENrT0+aOYf1PAwQP5Gth9o3XUC
NAxl8BFUSGYQz9iYoGeFB9MY7VzZ8gGJByb6V2j8wDSL5gIUaFL32F3Sigg0axC9
+9ISZY764lmqphfZY/5V83LBEJsIUknicH0nSjlW4XU6r1yajwblDbpUzUEPUBi/
O5YOojW/Bgk=
=oEdm
-----END PGP SIGNATURE-----

Re: [Hardware] [solved] Asus F5N, network devices

[Yuriy Shirokov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergey Kurakin пишет:
>> C ndiswrapper беспроводная сеть тоже отказывается работать.
>> Виндовский драйвер вроде встал: ndiswrapper -l сообщает
>> net5211: driver installer
>> 	device (168C:001C) present (alternate driver: ath_pci)
>> Но при попытке перезапустить сеть всё то же самое сообщение:
>> SIOCGIFFLAGS: No such device
>    Загруженный модуль ath_pci не даст работать ndiswrapper'у.
>    Попробуйте ath_pci поставить в blacklist. Или удалите пакет с 
> модулями madwifi.

Удалил kernel-modules-madwifi-std-smp. Сообщение про alternate driver
исчезло.

Потом заметил в dmesg сообщения от ndiswrapper с упоминанием wlan0.
Переименовал eth1 в wlan0. Устройство появилось.

После опускания проводного интерфейса, ifup wlan0 и запуска iwconfig и
dhcpch вручную даже появился интернет. Сейчас буду пытаться понять, как
научить его подниматься автоматически.

Спасибо за советы!

- --
С уважением,
Ю.А.Широков.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR7mG9OdMeS2DDLCcAQLcjgP7BdGATCV8V3mtzkl1zX7mb7/YvFqmHhU7
vy/hm4QIb/zcI1gUuqvWaNMK5XG/nSilebYHBeO6YNXFzvlY8YBKCruNlAC+bvpI
X4KBFHRLOqP4V/pLMXsIfxAWvp8IK/Lfw57jAAeu7FmpheVt+Ls1xq8ONpDVBuBD
eGsiQLkakwI=
=4Wqb
-----END PGP SIGNATURE-----