Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[Abandoned]: MX-17: No network with the live system.

Message
Author
chrisk
Forum Novice
Forum  Novice
Posts: 11
Joined: Tue Feb 20, 2018 5:17 pm

Re: MX-17: No network with the live system.

#21 Post by chrisk » Mon Feb 26, 2018 10:08 am

Thank You, dolphin.

Earlier I had removed the wl module using modprobe -r but this had no effect. The same applies to removing it with the MX Network Assistant, as you had suggested.

Frankly, I think that this is no wonder because the processes which I need are in STAT D and therefore cannot be controlled, not even by using kill -9 <PID>. On the other hand, I would beleive that those processes would need to be restarted.

Unfortunately the blacklist, when modified using the MX Network Assistant, is not persistent. I also tried to modify /etc/modprobe.d/broadcom-sta-dkms.conf but this is volatile as well. And the squashfs is mounted ro on /live/linux.

Therefore, *IF* these problems are caused by wl (which isn't really confirmed yet), wl should not be loaded at boot time. How could I accomplish that ?

Also, I would speculate that this issue would rather NOT be due to Bluetooth, if that is otherwise working fine on your laptop.

Later on I will report whether wl is loaded under SolydX and SparkyLinux.

Regards,
Chris

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 22421
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-17: No network with the live system.

#22 Post by Jerry3904 » Mon Feb 26, 2018 10:47 am

Therefore, *IF* these problems are caused by wl (which isn't really confirmed yet), wl should not be loaded at boot time. How could I accomplish that ?
You can block it using MX Network Assistant, as DO already showed.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9305
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-17: No network with the live system.

#23 Post by dolphin_oracle » Mon Feb 26, 2018 10:49 am

if you need system files to be changeable, then you need to use a persistence option. those files will change with root persistence enabled.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

chrisk
Forum Novice
Forum  Novice
Posts: 11
Joined: Tue Feb 20, 2018 5:17 pm

Re: MX-17: No network with the live system.

#24 Post by chrisk » Wed Feb 28, 2018 6:24 am

Thanks to all. The wl driver is now persistently blacklisted, see the attachment:
NetDrivers.png
Regrettably, this has no significant effect:

Code: Select all

demo@mx1:~
$ ps axu|grep D
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         176  0.0  0.0      0     0 ?        D    10:57   0:00 [kworker/2:3]
root        3701  0.0  0.0      0     0 ?        D    10:57   0:00 [kworker/3:2]
root        6398  0.0  0.0  40520  2936 ?        D    10:57   0:00 /sbin/cgmanager --daemon -m name=systemd
root        7118  0.0  0.1  46424  4724 ?        D    10:57   0:00 /lib/systemd/systemd-logind
root        7158  0.0  0.1 287464  7576 ?        Dl   10:57   0:00 /usr/lib/policykit-1/polkitd --no-debug
root        7164  0.0  0.3 397032 12984 ?        Dsl  10:57   0:00 /usr/sbin/NetworkManager
root        7200  0.0  0.1 224556  5212 ?        Ds   10:57   0:00 /usr/sbin/nmbd -D
root        7249  0.0  0.3 307840 12376 ?        D    10:57   0:00 /usr/sbin/smbd -D
demo        7466  0.0  0.6 422216 25452 ?        Dl   10:58   0:00 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
demo        7637  0.0  0.2 308544 11364 ?        D    10:58   0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
root        7908  0.0  0.0  43292  1796 pts/4    D+   11:02   0:00 ifconfig
demo        8011  0.0  0.2 308544 11548 ?        D    11:03   0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
demo        8585  0.0  0.0  48064  1000 pts/5    S+   11:19   0:00 grep D
demo@mx1:~
I'd also like to mention that the system is notably slow when starting programs, such as e. g. a root terminal, the MX Network Assistant, or the screenshot facility. Each of these take about 30 secs (estimated) to appear on screen.

{ Side note: For some reason the automatic creation of a rootfs file for persistent storage failed on first try.

I had chosen boot options #15 (dostore) and subsequently #4 (persist_static). The tool suggested a size of 4096 MiB, leaving about 10 GiB on the 16 GB USB stick. After the failure the tool proceeded to automatically create a homefs with a size of about 3.6 GiB, which succeeded.

On second try I got the rootfs created with a size of 3 GiB selected manually. }

Regards,
Chris
You do not have the required permissions to view the files attached to this post.

tradonal
Forum Novice
Forum  Novice
Posts: 78
Joined: Mon Sep 25, 2017 11:43 am

Re: MX-17: No network with the live system.

#25 Post by tradonal » Fri Mar 02, 2018 1:17 pm

re,
STAT -D is bad, I think it would be better to settle this to start, it's just my opinion .....
as root that gives:

Code: Select all

root@mx1:/
# ps ax
on my system there is no STAT-D

and

Code: Select all

root@mx1:/
# dmesg -x --level=emerg,warn,alert,crit,err

EDIT/
for info you can watch here
the num is the pid of the output of ps ax

Code: Select all

root@mx1:/
# cat /proc/5988/
attr/            comm             fd/              map_files/       net/             personality      setgroups        syscall
autogroup        coredump_filter  fdinfo/          maps             ns/              projid_map       smaps            task/
auxv             cpuset           gid_map          mem              oom_adj          root/            stack            timerslack_ns
cgroup           cwd/             io               mountinfo        oom_score        sched            stat             uid_map
clear_refs       environ          limits           mounts           oom_score_adj    schedstat        statm            wchan
cmdline          exe              loginuid         mountstats       pagemap          sessionid        status           
root@mx1:/
exemple;

Code: Select all

root@mx1:/
# ps ax | grep -i gvfs-udisks2
 2813 ?        Sl     0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
 6506 pts/0    S+     0:00 grep --color=auto -i gvfs-udisks2
 
root@mx1:/
# cat /proc/2813/
attr/            comm             fd/              map_files/       net/             personality      setgroups        syscall
autogroup        coredump_filter  fdinfo/          maps             ns/              projid_map       smaps            task/
auxv             cpuset           gid_map          mem              oom_adj          root/            stack            timerslack_ns
cgroup           cwd/             io               mountinfo        oom_score        sched            stat             uid_map
clear_refs       environ          limits           mounts           oom_score_adj    schedstat        statm            wchan
cmdline          exe              loginuid         mountstats       pagemap          sessionid        status           
root@mx1:/
and to know what is the possibilities given here
https://linux.die.net/man/5/proc

;)

Post Reply

Return to “Hardware /Configuration”