Testing 16.04.4 ,64 bit, LTS on a LiveDVD

[anonprivate]

I can't. I have an installed version 14.04 and have no trouble with this OS. I am testing a livedvd (16.04.4). Of course I am switching back and forth, version 16 is not yet ready for installation on my system - it keeps disconnecting from the router.

I believe that my posts have made it clear regarding the installed OS (no problem) and the livedvd (problem), there should be no confusion.

Best wishes.

Ps. The iso file checked. The drive often determines the write speed.

[GreyGeek]

Is this possible in the livedvd
Could I not try this by giving a command in the terminal?

See msg #18 in this thread.
You switch back and forth between the LiveDVD and the install so frequently it is hard to determine which you are running at any given time. Don't bother trying to change anything on the LiveDVD. As long as it passed the checksum option in its startup menu it is OK. If it didn't then you need to checksum the ISO file. If the ISO file checksum is good then you need to reburn a LiveDVD at the slowest speed your CDROM allows. If the ISO is bad then download and check a fresh copy. Let's keep the issues related to an installed system, and not the LiveDVD.

[anonprivate]

Is this possible in the livedvd
Could I not try this by giving a command in the terminal?

[GreyGeek]

Then the problem isn't power management. Did you change the nohwencrypt PARM to 1 ?

As root create a file called 'rt61pci.conf" in /etc/modprobe.d/" and add the following
Code:

options rt61pci nohwencrypt=1

and save it.

Then restart the network service using systemctl or log out and log back in.

[anonprivate]

Ref.kubuntu 16.04.4 - LiveDVD

I switched off power management and connected to the router via wi-fi. Unfortunately, after about 10 mins the connection dropped.

[citizen]

What do you plan to do when support (updates) for 14.04 stops?

I have been waiting for 18.04 to come out and then get the initial "bugs/complaints" ironed out. I came to KDE4 when it all went to hell the first time and I have watched 5 have the same mess. I have avidly avoided 16.04 and all non LTS until it's way more stable.
I really, really miss the stability I had in 12.04, it was way better than the 14.04 I am on.

[anonprivate]

That's because wlan0 is NOT your wifi device. In 14.04 it was, but not in 16.04. If you'll check back in the logs you posted you'll notice that it was renamed:

So, the device name you must use is wlp3s2.
The iwconfig man pages shows:

SYNOPSIS
      iwconfig [interface]
      iwconfig interface [essid X] [nwid N] [mode M] [freq F]
                         [channel C][sens S ][ap A ][nick NN ]
                         [rate R] [rts RT] [frag FT] [txpower T]
                         [enc E] [key K] [power P] [retry R]
                         [modu M] [commit]

So something like
sudo iwconfig wlp3s2 power off
should work.

Thank you

Why should power on tend to lead to the wi-fi connection disconnecting?

[GreyGeek]

I loaded the LiveDVD and set the wi-fi parameters to be the same as for the installed 14.04 OS.

iwconfig (from the Terminal in the livedvd) revealed that the power management is on. I tried using the command sudo iwconfig wlan0 power off; but I received the message: Error, No such device.

Hence the power management is on. Is there another way to switch it off in the livedvd. I switched all powers off the settings box. The status of power management in the installed OS (14.04) is Off.

I wonder if the power management being on when using the livedvd accounts for the disconnection?

That's because wlan0 is NOT your wifi device. In 14.04 it was, but not in 16.04. If you'll check back in the logs you posted you'll notice that it was renamed:

[ 164.010814] rt61pci 0000:03:02.0 wlp3s2: renamed from wlan0

So, the device name you must use is wlp3s2.
The iwconfig man pages shows:

SYNOPSIS
       iwconfig [interface]
       iwconfig interface [essid X] [nwid N] [mode M] [freq F]
                          [channel C][sens S ][ap A ][nick NN ]
                          [rate R] [rts RT] [frag FT] [txpower T]
                          [enc E] [key K] [power P] [retry R]
                          [modu M] [commit]

So something like
sudo iwconfig wlp3s2 power off
should work.

[anonprivate]

I loaded the LiveDVD and set the wi-fi parameters to be the same as for the installed 14.04 OS.

iwconfig (from the Terminal in the livedvd) revealed that the power management is on. I tried using the command sudo iwconfig wlan0 power off; but I received the message: Error, No such device.

Hence the power management is on. Is there another way to switch it off in the livedvd. I switched all powers off the settings box. The status of power management in the installed OS (14.04) is Off.

I wonder if the power management being on when using the livedvd accounts for the disconnection?

[anonprivate]

Yes, they will always be there. I have the same Nvidia that you have, and you lose the nice splash screen that is built in because the crappy "DOS" style one comes up before the Nvidia starts up. Not only will you have it at boot, but also at shutdown. And it is usually semi-verbose and flashes colors in the text. Super ugly and very 1980. You are not crazy, nothing is broken, that's how it works. I'm on 14.04 by the way and this has always been the case with Kubuntu for me. It did not do this in Mint KDE though.

What do you plan to do when support (updates) for 14.04 stops?

[GreyGeek]

Have you any advice that will stop the router connection dropping using the liveDVD

No. The only wifi changes you can make running a LiveDVD are those in memory (/sys/...). Since rt61pci has only one PARM, nohwcrypt, which probably isn't the cause of your problem, that leaves cfg80211 and mac80211 as the other two modules which might affect your problem. Mac80211 has 6 PARMs, 3 of which relate to disconnections. Cfg80211 has 3, none of which probably relates to your problem.

In a previous post I showed you how to make changes to PARMs in memory.

[GreyGeek]

What are 'parms'

Do you mean run 'lspci' when the livedvd is running?

No, not "lspci".
In Linux kernel modules have the *.ko extension, for Kernel Object. These modules are the things that are loaded during boot up that drive the various devices connected to your system. During their loading they how they behave can be adjusted by setting their PARM's. Not all modules have PARM's. Some have a lot. In earlier days Linux users had to adjust the Linux source software using a configuration program to activate the modules they needed to run their specific hardware, then they compiled those modules into the kernel. Today, all modules are precompiled and can be added or removed as needed without having to recompile the kernel.

The "lsmod" command lists the modules that have already been loaded and are being used. "rmmod" can be used to remove modules. "modprobe" can be used to add or remove modules. Use the man command to learn about each one. You can remove a loaded mod using "modprobe -r modname" and then add it using "modprobe modname parm=something". In your case something like "modprobe rt61pci nohwcrypt=1"

Most, but not all, modules have PARMeters that can be adjusted during loading. "modinfo module" gives the details of the module and lists any available PARM's.

You should understand that sometimes certain modules are loaded in sets, and have to be loaded or unloaded in specific order. Wifi modules are like that. If you "rmmod rt61pci" you'll probably get a message stating that rt61pci cannot be removed because other modules depend on it. You'll have to start at the bottom of the chain (cfg80211?) and work your way up. Then rt61pci can be removed. When installing rt61pci (modprobe rt61pci) the additional mods necessary for it will be loaded automatically, in the correct order

[anonprivate]

Thanks to Snohog for enclosing the output in tags

[anonprivate]

Put in your code tags FIRST, then paste the text between them. Posting long output like you did will result in people not wanting to scroll through the output to get to any comments that might be below it. You should edit that post and add the tags.

Browsing is slow because your wifi speed is slow, probably because of all the background connecting and reconnecting and failed buffer flushing. If you haven't got IPv6 set up to run normally then forget about any mention of it in the dmesg.

According to your iwconfig listing the power is already set to off, just like mine.

Power off: see above.

Notice that the PARM is "nohwcrypt", i.e., no hardware encryption. Set to "N" (0 or false) means that it is set to DO hardware encryption (double negative). To turn off encryption set nohwcrypt to 1 (or true). I'm not familiar with using "N" and "Y" for Boolean values.

You can't do this on a LiveDVD because you can't write to a LiveDVD. You can only change values that are in memory, specifically
/sys/module/rt61pci/drivers/pci:rt61pci/module/parameters/nohwcrypt

echo 1 > /sys/module/rt61pci/drivers/pci:rt61pci/module/parameters/nohwcrypt

(IF rt61pci is your driver name, I can't see what it is right now)

You can't hurt a CD by attempting to write to it because the process will fail. You can scratch it with a knife or something. That should do the trick!

Have you checked the LiveDVD's checksum?

Have you any advice that will stop the router connection dropping using the liveDVD

[GreyGeek]

Put in your code tags FIRST, then paste the text between them. Posting long output like you did will result in people not wanting to scroll through the output to get to any comments that might be below it. You should edit that post and add the tags.

The only way I can connect to the router is by switching off the wi-fi button, and then switching it back on. Otherwise the system cannot find the router

Browsing is very slow. Is this because I am using a liveDVD

In the live DVD. what about using sudo iwconfig wlan0 power off?
and how about ignoring ipv6? How would I do this in Terminal?

Browsing is slow because your wifi speed is slow, probably because of all the background connecting and reconnecting and failed buffer flushing. If you haven't got IPv6 set up to run normally then forget about any mention of it in the dmesg.

According to your iwconfig listing the power is already set to off, just like mine.

First, In kubuntu 14.04 I have power off, but in the live dvd, it looks like the the power is on. Can I do any harm by typing into the terminal in the live dvd: sudo iwconfig wlan0 power off, to see if that prevents my disconnection.

I will run the livedvd and check the dmesg as well as the free -h

I don't know how to set nohwcrypt. I would have thought that nohwcrypt=N would turn encryption off. Are there other factors to consider in turning hardware encryption on or off?

Regards

Power off: see above.

Notice that the PARM is "nohwcrypt", i.e., no hardware encryption. Set to "N" (0 or false) means that it is set to DO hardware encryption (double negative). To turn off encryption set nohwcrypt to 1 (or true). I'm not familiar with using "N" and "Y" for Boolean values.

You can't do this on a LiveDVD because you can't write to a LiveDVD. You can only change values that are in memory, specifically
/sys/module/rt61pci/drivers/pci:rt61pci/module/parameters/nohwcrypt

echo 1 > /sys/module/rt61pci/drivers/pci:rt61pci/module/parameters/nohwcrypt

(IF rt61pci is your driver name, I can't see what it is right now)

You can't hurt a CD by attempting to write to it because the process will fail. You can scratch it with a knife or something. That should do the trick!

Have you checked the LiveDVD's checksum?