243750496 commented 6 years ago

install:

download https://github.com/genodeftest/Netgear-A6210/tree/port-to-4.13 for NETGEAR A6210
not this one https://github.com/genodeftest/Netgear-A6210/tree/4.13-fix-only

sudo mv '/home/atc/Downloads/Netgear-A6210-port-to-4.13' /usr/src/netgear-a6210-2.5.0
sudo dkms install netgear-a6210/2.5.0

device not managed : You should look at the contents of the file /var/lib/NetworkManager/NetworkManager.state. It should look something like this:

[main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Change any from 'false' to 'true' to re-enable networking. It may work better if you first stop NetworkManager:

Edit /etc/NetworkManager/NetworkManager.conf and change:

managed=false to

managed=true Restarted network-manager:

sudo service network-manager restart No change. Then I tried:

touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf sudo service network-manager restart All three network cards came back on-line.

Or: If you don't have it installed, could you install the package rfkill and post the output of "rfkill list"? If it's software blocked enter "rfkill unblock #" where # is the number of the blocked item in the list, or "rfkill unblock name". If it reports it to be hard blocked check out the wireless switch in your laptop.

I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf.

[main] plugins=ifupdown,keyfile dns=dnsmasq

[ifupdown] managed=false

[keyfile] unmanaged-devices=mac:00:26:2d:fd:5c:e0 changed to

[main] plugins=ifupdown,keyfile dns=dnsmasq

[ifupdown] managed=false

#[keyfile]

#unmanaged-devices=mac:00:26:2d:fd:5c:e0

device not ready: To fix this I had to disable secure boot in the UEFI BIOS page on startup." Yes... secure boot is useless and doesn't allow you to install some proprietary drivers such as some very common Realtek Ethernet devices and as i can see that goes for the mediatek wifi drivers-firmware too

i have done all of previous said, but still can't discover anything and show up ,if i typed sudo service network-manager restart then it will be device not ready ,still none-functionable not managed nothing worked

device not ready

could u please help me ?thx a lot!

desktop :Ubuntu budgie 17.10

kernel 4.13

genodeftest commented 6 years ago

What about kernel logs? Anything in dmesg or journalctl -b about that kernel module, about NetworkManager, …? Does lsmod list this kernel module at all?

genodeftest commented 6 years ago

Can you please put this output into code boxes or paste it into a gist? Comments are pretty bad for pasting log files.

243750496 commented 6 years ago

where the log file locate ? maybe it's easy to upload the log file

genodeftest commented 6 years ago

where the log file locate?

I don't understand what you mean. Can you please rephrase it?

You can find gist here: https://gist.github.com/ (that's like pastebin). It is better to put output of dmesg, journalctl or other log files into gists, because reading them here is quite hard.

243750496 commented 6 years ago

hereis the output https://gist.github.com/243750496/e0d8212a807d0ace106a8b6b546549c2

genodeftest commented 6 years ago

By the way, if you run journalctl -b > filename.txt, the logs from journald will be written to the file named "filename.txt". This way you don't have to copy so much stuff from a terminal.

243750496 commented 6 years ago

hereis all three files dmesg.txt journalctlb.txt lsmod.txt

genodeftest commented 6 years ago

As you can see in these lines:

11月 19 05:24:30 ATC kernel: usb 4-3.1: new SuperSpeed USB device number 3 using xhci_hcd
11月 19 05:24:30 ATC kernel: usb 4-3.1: New USB device found, idVendor=0846, idProduct=9053
11月 19 05:24:30 ATC kernel: usb 4-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
11月 19 05:24:30 ATC kernel: usb 4-3.1: Product: A6210
11月 19 05:24:30 ATC kernel: usb 4-3.1: Manufacturer: NETGEAR
11月 19 05:24:30 ATC kernel: usb 4-3.1: SerialNumber: 100

The USB device is detected by the kernel.

According to


11月 19 05:24:31 ATC systemd[1]: smartd.service: Main process exited, code=exited, status=17/n/a
11月 19 05:24:31 ATC systemd[1]: smartd.service: Unit entered failed state.
11月 19 05:24:31 ATC systemd[1]: smartd.service: Failed with result 'exit-code'.

your smartd is broken, maybe by configuration? Anyway, that's probably unrelated to your problem with Netgear A6210.

You have this line:

avahi-daemon[1099]: Failed to open /etc/resolv.conf: Invalid argument

in the logs, which might indicate an issue with avahi. Please try whether you can connect to the internet through an ethernet cable. If yes, then this is not causing your connection problem.

As I understand this, there are some problems in NetworkManager

11月 19 05:24:31 ATC NetworkManager[1086]: ((src/devices/nm-device.c:1452)): assertion '<dropped>' failed

so initialization of a device fails. This seems to be the core issue, although I can't tell you why it fails. You probably need start the kernel and NetworkManager in debug mode to tell you more.

There is a crash in ModemManager:

11月 19 05:24:32 ATC systemd[1]: ModemManager.service: Main process exited, code=dumped, status=11/SEGV
11月 19 05:24:32 ATC NetworkManager[1086]: <info>  [1511040272.2988] ModemManager disappeared from bus
11月 19 05:24:32 ATC systemd[1]: ModemManager.service: Unit entered failed state.
11月 19 05:24:32 ATC systemd[1]: ModemManager.service: Failed with result 'core-dump'.

so please go and report it to your distribution vendor (Ubuntu, at launchpad.net) maybe they can fix it. I doubt this is related to your problem here though.

There is no crash or other bug reported in the mt7662u kernel module, so it does not fail fatally. I am out of more tips/ideas for now.

From lsmod: mt7662u_sta is in that list, so the kernel module gets loaded correctly.

243750496 commented 6 years ago

You probably need start the kernel and NetworkManager in debug mode to tell you more.

1.how to enter the debug mode???

2.what info should i provide to vendor in debug mode??

genodeftest commented 6 years ago

Debug mode: Add the "debug" flag to your kernel command line. You can get there by presing "e" key during boot which will put you into grub's edit mode. Add " debug" to the command line and make sure to remove all other logging-related stuff like "quiet" and "rhgb".
I have no clue without looking at the files. If you prefer to keep this metadata private, you may want to send me an email (see my profile).

243750496 commented 6 years ago

What should i remove?all?where to add debug flag?

genodeftest commented 6 years ago

In the line that reads wraps, there is a word "quiet". Replace it by "debug".

After reboot, try to use the network, then reboot again without these changes. Your linux will start normally if you don't change anything. Any changes in this grub config menu will be lost on next reboot.

243750496 commented 6 years ago

What's next if i entered debug mode?just login and shut down then to enter normal start to copy the log file out? btw: if don't set debug flag will i get nomal start?

Whether debug kernel mode will create a log file that contain key data? But where the log file locate ？

genodeftest commented 6 years ago

What's next if i entered debug mode?just login and shut down then to enter normal start to copy the log file out?

As written above: After reboot, try to use the network, then reboot again without these changes.

btw: if don't set debug flag will i get nomal start?

As written above: Yes. Your linux will start normally if you don't change anything. Any changes in this grub config menu will be lost on next reboot.

Whether debug kernel mode will create a log file that contain key data?

No, it will not create a specific log file.

But where the log file locate

After changing the command line, booting and trying to connect to a network, use dmesg and journalctl -b as before. Or if you rebooted already, you may want to use journalctl -b -1 (or higher numbers instead of 1, see the manual for details) to select logs from previous boots.

243750496 commented 6 years ago

here is new logs: dmesg.new.txt journalctlb.new.txt

genodeftest commented 6 years ago

Have you tried connecting the USB device to a different USB port using a different USB cable?

genodeftest commented 6 years ago

I could not find anything in the logs hinting to an issue, so I cannot help you.

243750496 commented 6 years ago

i fogot to enable wifi at the debug time , maybe this time the log may help btw: this time i connect the wifi adapter directly to PC without and usb cable

dmesg-with-wifi-opened.txt journalctlb-with-wifi-opened.txt

genodeftest commented 6 years ago

Your journalctl output contains this line:

ModemManager.service: Main process exited, code=dumped, status=11/SEGV

Please get this bug fixed. Maybe your software is very outdated. In case you are running software without installing updates, don't expect anyone to help you.

There is a warning from nvidia graphics driver, you should take a look.

NVRM: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported.

What does systemctl status --full NetworkManager-wait-online.service give you? I'm asking because of

11月 27 09:22:50 ATC systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILURE
11月 27 09:22:50 ATC systemd[1]: Failed to start Network Manager Wait Online.
11月 27 09:22:50 ATC systemd[1]: NetworkManager-wait-online.service: Unit entered failed state.
11月 27 09:22:50 ATC systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.

in your logs.

Have you tried connecting the device to a USB 2.0 port?

Conclusion of current state:

The device correctly shows up on USB hub (see latest dmesg/journalctl files)
The kernel module is loaded

The best clue I have is that the issue is related to this log entry:

NetworkManager[1077]: ((src/devices/nm-device.c:1452)): assertion '<dropped>' failed

Which goes wrong in nm_device.c:

NMDeviceType
nm_device_get_device_type (NMDevice *self)
{
g_return_val_if_fail (NM_IS_DEVICE (self), NM_DEVICE_TYPE_UNKNOWN);

return NM_DEVICE_GET_PRIVATE (self)->type;
}

… and I don't have any clue about how to get this fixed. It looks like an issue "before" or within NetworkManager.

243750496 commented 6 years ago

so what to do next ? paste the bug to ubuntu lanchpad or fix by do something to fix by myself (no coding)?but what should i provide? the log file or your last posts?

genodeftest commented 6 years ago

so what to do next ? paste the bug to ubuntu lanchpad or fix by do something to fix by myself (no coding)?but what should i provide? the log file or your last posts?

I don't know for sure. I doubt this issue can be solved without coding, but I am not sure whether it is a bug in this kernel module or in NetworkManager. You may want to try to report a bug against NetworkManager and add a link here to all of the logs and posts.

franckgarnier21 commented 6 years ago

I have the same bug during the pppd on a VPN connection in Ubuntu 17.10

NetworkManager[27095]: ((src/devices/nm-device.c:1452)): assertion '' failed

Do you have more information to solve it ?

genodeftest commented 6 years ago

Do you have more information to solve it ?

Read the NetworkManager code (maybe while debugging the assertion failure) and find out whether this is a bug in NetworkManager or in the kernel.

243750496 commented 6 years ago

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733138 i had post the bug to launchpad, still no official reply now

jurobystricky / Netgear-A6210

device not managed #88

desktop :Ubuntu budgie 17.10

kernel 4.13