You are not logged in.
Hello slitaz-team,
Dear community,
I tried to run SliTaz under Microsoft Hyper-V, Installation was not an issue, but boot stops after loopback with system freeze
After a little analyzing i found out that the problem seems to be the HyperV legacy Network Adapter which emulates a DECChip 21140 and does not seem to work under SliTaz.
I got it managed to start the System (with Default loopback Adapter) and did get the tulip module load and eth0 showed up but after ifconfig eth0 up system still freezes.
It seems to be a incompatibility between the HyperV DEC Emulator Driver and the tuilp in slitaz
root@slitaz:~# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 03)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02)
00:08.0 VGA compatible controller [0300]: Microsoft Corporation Hyper-V virtual VGA [1414:5353]
00:0a.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21140 [FasterNet] [1011:0009] (rev 20)
root@slitaz:~# lsmod
Module Size Used by Not tainted
floppy 41138 0
button 3602 0
tulip 37375 0
root@slitaz:~#
root@slitaz:~# tazhw detect-pci
Detected PCI devices Kernel modules
================================================================================
> Module in use: tulip
================================================================================
root@slitaz:~#
root@slitaz:~# ifconfig -a
dummy0 Link encap:Ethernet HWaddr EA:6D:7F:53:D7:9A
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:15:5D:00:01:0F
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:9 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
best regards and thank you in advance for your help
kid8home
Offline
Blacklist tulip module to stop auto-load and freeze.
Blacklist info: https://wiki.archlinux.org/index.php/kernel_modules#Blacklisting
Open terminal as root,
[c]modprobe tulip[/c]
Check /var/log/messages and dmesg for errors related to tulip driver loading.
Search google for errors to find possible solution.
Offline
Thanky you mojo for you Feedback
I was busy analyzing the logs, but was not able to find something.
i tried to blacklist all the Drivers i found in the bootlog, without success.
I was not able to find Errors in dmesg and Messages, but what is strange in the bootlog is that several Ethernet Drivers are loaded even if i use the bootoption nomodeset
I assume the problem is somewhere in the area of the de4x5 module, but why are all the other Ethernet Drivers like e1000,e100, Dmfe, winbound-840 loaded before the initd/rcS, can i avoid this?
Offline
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]