seaken64
I experimented with two separate LiveUSB drives. One is a drive I’ve had for awhile and was started with antiX-17. The second is new and using the current 17.3.1. Both are 32-bit and installed on 8Gb USB with persistence. The older one is set to persist-all. The newer one is set to persist-static. The older drive gives an error when booted on a computer with less than 2Gb of RAM but I choose to “C”ontinue and it continues to boot with no apparent problems. (I’m assuming it uses a general static file instead of the root persistance file. But I don’t really know this).
I have several computers that have a Broadcom ethernet or Wifi adapter. Sometimes the LiveUSB does not detect either the ethernet or wireless adapter. I noticed that with my older LiveUSB it detects the wireless on one of my computers where the new one does not. But that same older USB does not detect the ethernet on a computer I have not tried it on yet. Once when I setup the blacklist file correctly and manually entered the correct driver using the modprobe command the wifi networking came to life.
After shutting down I looked at the saved state files and I can see the settings are saved for each machine. I put it in another machine and that machine also gets it’s own settings files. When I put the older USB back in a machine it has already been in, and reboot, the network does not start automatically. But I can run Ceni and reconfigure and it works. This may be because the root persistance file is not loaded if I have to enter “C” to continue.
On the Ceni screen is a list of Logical Interfaces in the lower right portion of the Ceni screen. On the older USB this list includes at least two logical names that do not hold to the typical “wlanx” naming scheme. They are named wlx001nnnnnnnnn and wlx002nnnnnnnnn where the n’s are a bunch of letters and numbers. There is also eth1, eth2, eth3, and wlan2. On the new USB that list has eth0, eth3, wlan1, wlan2 and wlan3.
I do usually get the network interface to be either eth0, eth1, or wlan0 or wlan1. On some of my computers I have two ethernet adapters or two wireless adapters. On one laptop I have a third adapter named wmx1 assigned as ethernet.
So I get that the persistance routines are saving settings for each machine and that the interface is usually named eth0 or wlan0. But it does not seem to always work out that way. I have had both eth3 and wlan2 used. I can’t say it was not me who made that assignment. I may have played with selecting one of those Logical Devices from the list in an attempt to get the networking on when it didn’t happen automatically. But I don’t recall doing that or being successful at assigning one of those ID’s. All I can say is I have had eth3 or wlan2 and they do not show on the Conky by default.
It is not a problem. I have figured out a way to deal with it if the interface does not come up automatically or gets a device name other than the standard four ID’s. What I was hoping for was a more dynamic indicator on either the Conky or the task bar that will show whatever ID is in play. I haven’t found such a widget yet. As long as I get one of the four device ID’s used by Conky I don’t need to worry about it. I will try to pay closer attention in the future as to what I did that may have led to an eth3 or wlan2 ID assignment. I am curious as to how those non-standard Logical interface ID’s got on the Ceni list. Where did they come from?
Seaken64