Op maandag 20 augustus 2018 00:47:26 CEST schreef Carlos E. R.:
On Sunday, 2018-08-19 at 14:33 -0700, don fisher wrote:
On 08/19/2018 01:45 PM, Knurpht-openSUSE wrote:
Op zondag 19 augustus 2018 22:33:27 CEST schreef Carlos E. R.:
On 2018-08-19 22:31, Knurpht-openSUSE wrote: His problem is not yet solved.
And it never will as long as Don keeps coming with things 'found on the internet', like 'a patch in /sys' ( which is regenerated at boot ), without providing links we can check. As long as he doesn't provide proper info, everything is just shooting in the dark, and this gets even worse since we do not know what's being done and undone.
I am often criticized for making my posts too long, by people that are evidently charged by message length. This thread now contains 94 messages, some not really related to the problem that I am trying to solve.
The link you referenced offering a solution to the E2500 card problem, was offers on Ubuntu forums, <https://ubuntuforums.org/showthread.php?t=2350778>. And as you suggested, the commands have to be applied on each reboot. I do not know where it comes from, just that it works. And I am often told that I am lazy and should search Google for solutions.
If this hack works for you, it is possible to apply them on every boot automatically.
In the directory "/etc/init.d" create one of these scripts, or edit if it exist:
after.local
Runs after runlevel is complete. Right, I know "runlevels" do not exist with systemd. Fine, "target".
Carlos, don't you agree this is bringing Don further and further away from a default install? With the knowledge displayed so far, IMNSHO that's maybe working around some issues, but not really solving his issues.
boot.local
This one runs at the very first possible, before evaluating targets, I believe. I verified it does run in 42.3.
halt.local
Not in your case.
Or, create a systemd service in /etc/systemd/system.
How early do you want it to run?
There have been many problems with this Alienware a13 3 computer, so I am going in multiple directions at once. I do not know why the leap 42.3 installation DVD works fine, but the Leap 15 stalls examining USB devices. This DVD worked fine on my other Alienware computers, so I do not believe it is faulty.
Nevertheless, test it, because they can degrade. On boot, select the option to verify instead of installation.
You should report this issue in Bugzilla.
There was no firmware support for the Qualcomm Atheros QCA6174 wlan adapter, so I replaced the hardware with an Intel 8260 IEEE 802.11ac - Wi-Fi Adapter. The Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller does not work and the message you referenced was my temporary fix.
I an currently concerned about the nouveau support for the NVIDIA GP106M [GeForce GTX 1060 Mobile]. I see the driver nouveau listed in the brief crash dumps left on my screen. I miss the option of writing the complete boot output to the printer port, if any existed.
Crumbs. Does it have Nvidia AND Intel video? They are problematic. Daniel Bauer also has deep problems with his.
It is possible to dump kernel log entries via network, if the network card is working. I think there is another procedure to dump via usb.
Maybe devs could develop a method to dump boot messages to a raw disk partition. No filesystem support needed. Dangerous if the wrong partition is chosen.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org