Porteus-v4.0 bug reports
Posted: 04 Jul 2018, 12:42
with these modifs I can boot but no wlan lnterfce
Code: Select all
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5112] device (eth0): link connected
Jul 6 17:07:25 porteus kernel: [ 31.651592] r8169 0000:02:00.0 eth0: link up
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5128] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5140] policy: auto-activating connection 'Wired connection 1'
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5169] device (eth0): Activation: starting connection 'Wired connection 1' (36c(...)e)
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5176] device (eth0): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5181] manager: NetworkManager state is now CONNECTING
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5195] device (eth0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5207] device (eth0): state change: config -> ip-config (reason 'none', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.5270] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.6114] dhcp4 (e
th0): dhclient started with pid 1093
Jul 6 17:07:25 porteus dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 6 17:07:25 porteus dhclient: DHCPOFFER of 192.168.0.107 from 192.168.0.1
Jul 6 17:07:25 porteus dhclient: DHCPREQUEST for 192.168.0.107 on eth0 to 255.255.255.255 port 67
Jul 6 17:07:25 porteus dhclient: DHCPACK of 192.168.0.107 from 192.168.0.1
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8069] dhcp4 (eth0): address 192.168.0.107
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8069] dhcp4 (eth0): plen 24 (255.255.255.0)
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8070] dhcp4 (eth0): gateway 192.168.0.1
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8070] dhcp4 (eth0): lease time 604800
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8070] dhcp4 (eth0): nameserver '192.168.0.1'
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8071] dhcp4 (eth0): state changed unknown -> bound
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8094] device (eth0): state change: ip-config -> ip-check (reason 'none', internal state 'manag
ed')
Jul 6 17:07:25 porteus dhclient: bound to 192.168.0.107 -- renewal in 298847 seconds.
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8109] device (eth0): state change: ip-check -> secondaries (reason 'none', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8118] device (eth0): state change: secondaries -> activated (reason 'none', internal state 'managed')
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8123] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8134] manager: NetworkManager state is now CONNECTED_SITE
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8136] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8158] device (eth0): Activation: successful, device activated.
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8170] manager: startup complete
Jul 6 17:07:25 porteus NetworkManager[1029]: <info> [1530889645.8179] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 6 17:07:25 porteus nm-dispatcher: req:1 'up' [eth0]: new request (0 scripts)
Jul 6 17:07:25 porteus nm-dispatcher: req:1 'up' [eth0]: completed: no scripts
Jul 6 17:07:25 porteus nm-dispatcher: req:2 'connectivity-change': new request (0 scripts)
Jul 6 17:07:25 porteus nm-dispatcher: req:2 'connectivity-change': completed: no scripts
Jul 6 17:07:26 porteus ModemManager[1043]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0': not supported by any plugin
In previous post I gave you x86_64 links, sorry, correct links for your i586 are:
On my newer laptop no external device is recognized after suspend.
That sucks. Funnily enough, I tried switching on WLAN on my Android, connect the Android Smartphone via USB to the laptop and activate USB tethering. Et voilà it works. Now I have a functioning "wired connection 2", but still, the cabled LAN that should be eth0 is still not working.
Code: Select all
Jul 7 18:44:56 porteus kernel: [31820.288034] usb 2-1.3: new high-speed USB device number 5 using ehci-pci
Jul 7 18:44:56 porteus kernel: [31820.367805] usb 2-1.3: New USB device found, idVendor=04e8, idProduct=6860
Jul 7 18:44:56 porteus kernel: [31820.367813] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 7 18:44:56 porteus kernel: [31820.367817] usb 2-1.3: Product: SAMSUNG_Android
Jul 7 18:44:56 porteus kernel: [31820.367821] usb 2-1.3: Manufacturer: SAMSUNG
Jul 7 18:44:56 porteus kernel: [31820.367825] usb 2-1.3: SerialNumber: *whatever*
Jul 7 18:44:59 porteus kernel: [31823.252036] usb 2-1.3: reset high-speed USB device number 5 using ehci-pci
Jul 7 18:45:06 porteus kernel: [31830.420053] usb 2-1.3: reset high-speed USB device number 5 using ehci-pci
Jul 7 18:45:06 porteus kernel: [31830.498329] usb 2-1.3: device firmware changed
Jul 7 18:45:06 porteus kernel: [31830.498561] usb 2-1.3: USB disconnect, device number 5
Jul 7 18:45:06 porteus kernel: [31830.673036] usb 2-1.3: new high-speed USB device number 6 using ehci-pci
Jul 7 18:45:06 porteus kernel: [31830.752199] usb 2-1.3: New USB device found, idVendor=04e8, idProduct=6863
Jul 7 18:45:06 porteus kernel: [31830.752206] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 7 18:45:06 porteus kernel: [31830.752210] usb 2-1.3: Product: SAMSUNG_Android
Jul 7 18:45:06 porteus kernel: [31830.752214] usb 2-1.3: Manufacturer: SAMSUNG
Jul 7 18:45:06 porteus kernel: [31830.752218] usb 2-1.3: SerialNumber: *whatever*
Jul 7 18:45:06 porteus mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Jul 7 18:45:06 porteus mtp-probe: bus: 2, device: 6 was not an MTP device
Jul 7 18:45:07 porteus kernel: [31831.519918] usbcore: registered new interface driver cdc_ether
Jul 7 18:45:07 porteus kernel: [31831.533781] rndis_host 2-1.3:1.0 usb0: register 'rndis_host' at usb-0000:00:1d.0-1.3, RNDIS device, xx:...:xx
Jul 7 18:45:07 porteus kernel: [31831.533848] usbcore: registered new interface driver rndis_host
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.3956] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.3973] device (usb0): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.3981] device (usb0): link connected
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4004] keyfile: add connection in-memory (94(...)55,"Wired connection 2")
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4015] settings: (usb0): created default wired connection 'Wired connection 2'
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4049] device (usb0): state change: unavailable -> disconnected (reason 'none', internal state 'managed')
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4057] policy: auto-activating connection 'Wired connection 2'
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4073] device (usb0): Activation: starting connection 'Wired connection 2' (94c92e6f-ae60-3dad-83cf-5ed49a949a55)
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4077] device (usb0): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4081] manager: NetworkManager state is now CONNECTING
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4090] device (usb0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4099] device (usb0): state change: config -> ip-config (reason 'none', internal state 'managed')
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4105] dhcp4 (usb0): activation: beginning transaction (timeout in 45 seconds)
Jul 7 18:45:07 porteus NetworkManager[1029]: <info> [1530981907.4283] dhcp4 (usb0): dhclient started with pid 14390
Jul 7 18:45:07 porteus dhclient: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 4
Jul 7 18:45:09 porteus dhclient: DHCPOFFER of 192.168.42.63 from 192.168.42.129
Jul 7 18:45:09 porteus dhclient: DHCPREQUEST for 192.168.42.63 on usb0 to 255.255.255.255 port 67
Jul 7 18:45:09 porteus dhclient: DHCPACK of 192.168.42.63 from 192.168.42.129
Jul 7 18:45:09 porteus ModemManager[1043]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3': not supported by any plugin
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9017] dhcp4 (usb0): address 192.168.42.63
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9017] dhcp4 (usb0): plen 24 (255.255.255.0)
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9017] dhcp4 (usb0): gateway 192.168.42.129
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9018] dhcp4 (usb0): lease time 3600
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9018] dhcp4 (usb0): hostname 'porteus'
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9018] dhcp4 (usb0): nameserver '192.168.42.129'
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9018] dhcp4 (usb0): state changed unknown -> bound
Jul 7 18:45:09 porteus dhclient: bound to 192.168.42.63 -- renewal in 1361 seconds.
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9043] device (usb0): state change: ip-config -> ip-check (reason 'none', internal state 'managed')
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9054] device (usb0): state change: ip-check -> secondaries (reason 'none', internal state 'managed')
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9061] device (usb0): state change: secondaries -> activated (reason 'none', internal state 'managed')
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9064] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9073] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9075] policy: set 'Wired connection 2' (usb0) as default for IPv4 routing and DNS
Jul 7 18:45:09 porteus NetworkManager[1029]: <info> [1530981909.9098] device (usb0): Activation: successful, device activated.
Jul 7 18:45:09 porteus dbus-daemon[523]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.0' (uid=0 pid=1029 comm="/usr/sbin/NetworkManager ") (using servicehelper)
Jul 7 18:45:09 porteus dbus-daemon[523]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 7 18:45:09 porteus nm-dispatcher: req:1 'up' [usb0]: new request (0 scripts)
Jul 7 18:45:09 porteus nm-dispatcher: req:1 'up' [usb0]: completed: no scripts
Jul 7 18:45:09 porteus nm-dispatcher: req:2 'connectivity-change': new request (0 scripts)
Jul 7 18:45:09 porteus nm-dispatcher: req:2 'connectivity-change': completed: no scripts
all's ok with porteusv3.1 and porteusv3.2.2can't see my webmail on porteusv4.0 on these two machines
-processor Intel(R) Pentium(R) D CPU 2.80GHz (i586)
-processor Intel(R) Pentium(R) 4 CPU 2.66GHz (i586)
Code: Select all
guest@porteus:~$ find /var/lib/pkgtools/packages/ -iname *modem*
-> /var/lib/pkgtools/packages/ModemManager-1.8.0-x86_64-1
guest@porteus:~$ find /var/lib/pkgtools/packages/ -iname *network*
-> /var/lib/pkgtools/packages/NetworkManager-openvpn-1.2.8-x86_64-1jay
-> /var/lib/pkgtools/packages/NetworkManager-pptp-1.2.4-x86_64-1jay
-> /var/lib/pkgtools/packages/NetworkManager-vpnc-1.2.4-x86_64-1jay
-> /var/lib/pkgtools/packages/network-manager-applet-1.8.12-x86_64-2
-> /var/lib/pkgtools/packages/NetworkManager-1.10.10-x86_64-1
-> /var/lib/pkgtools/packages/network-scripts-15.0-noarch-8
guest@porteus:~$
Activate xfce module after login to cinnamon - maybe will help after while without re-login. Or rename xfce that it would loaded before cinnamon and boot Porteus with these two modules - maybe some package/component is missing.
Should I try some of the modules and/or kernel/initrc to check out if it changes my issue with LAN no being recognized after suspend?Blaze wrote: ↑14 Jul 2018, 08:22tome, I use different base of Porteus. Final version and Porteus-XFCE-v4.0-dev-x86_64.iso
Code: Select all
884062fdeec0983b0c2b2e097c60fb79 Porteus-XFCE-v4.0-dev-x86_64.iso