LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-04-2017, 08:22 AM   #1
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
HP 15-bw053od


https://www.officedepot.com/a/produc...op-156-Screen/

This went on sale (more than already always on sale) for $369 this past monday. That's a bundle price so I was forced to take a McAfee box and a mouse for the price. And < $400 out the door after taxes. Tolerable for a 2.5GHz quad core with 8GB RAM.

Mostly the same as my other laptop, the HP 15-ba053nr, with some notable exceptions.

https://www.linuxquestions.org/quest...op-4175610081/

The A10-9620P APU, not the 9600P. Slightly faster RAM. Different ethernet and wireless. Neither of which works particularly well under linux.

The first annoyance was getting the legacy boot enabled. I basically had to delete all known UEFI keys for that to take and work and allow me to boot the non-UEFI debian install that I was previously using on the ba053nr. With several cycles through the bios/uefi to figure that out.

glmark2 scored 1074
(scored about 1052 on the ba053nr)

Otherwise all the same amdgpu and debian testing (buster) or newer for GPU support as the ba053nr.

The ethernet, technically works. But dies fastly and often, I went to one of my usb ethernet dongles relatively quickly. Doing this every 2 minutes got annoying. Especially when trying to game.

# ip link set enp1s0 down; sleep 1; modprobe -r r8169; sleep 1; modprobe r8169; sleep 1; ip link set enp1s0 up mtu 1440; sleep 1; ip addr add 192.168.2.2/24 dev enp1s0; sleep 1; ip route add default via 192.168.2.1 dev enp1s0; sleep 1; ping -c 2 192.168.2.1

Using a dongle solved this quirk. I'll figure out another option sooner or later. Noting a few patches already out relating to power draw and heat or similar issues for the r8169 driver. Wireless technically exists, but I'm not entirely sure a driver exists at this point. The dmesg output hints at rtl8723b for bluetooth support, but ifconfig, iwconfig, and ip doesn't show a wireless interface (yet). So that's annoying.

Otherwise good hardware. Chrome plated hinges which differs from the ba053nr. And a more black / less gray screen than the ba053nr. The screen seems to have darker blacks. Not that i've used it much, but be ba053nr has a noticeable backlight when you hit the power button. It's hard to tell that the bw053od is on with it's screen until the press ESC to pause stuff shows on screen. I mostly use external displays and turn OFF the LCDs though. And still the annoying 1366x768 resolution on the LCD.

I just got this yesterday so more details to follow.
 
Old 11-05-2017, 12:56 AM   #2
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Fedora, Arch, & KDE Neon
Posts: 2,760

Rep: Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788
Quote:
Originally Posted by Shadow_7 View Post
And still the annoying 1366x768 resolution on the LCD.

I just got this yesterday so more details to follow.
I was really interested until I read that. Dealbreaker for me to not have a 1080P when the $250 Chuwi Lapbook 14 has 1080P.
 
Old 11-05-2017, 03:06 AM   #3
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
The deal breaker of sorts for me is that NONE of the networking cards work in linux (hopefully a non-issue in six-ish months). The r8169 does "work", but stops working in short order. Which is odd for an Ethernet device. Normally that behavior is wireless drivers and old firmware. Which normally have github drivers and kernel.org firmware that work swell if you want to jump the shark. So far I'm coming up short on alternative drivers for the networking devices on this machine. I have dongles, but that kind of makes traveling with this machine moot. Ethernet dongle to ethernet dongle with a short ethernet cable and a pocketchip (for wifi access) isn't exactly the "I'm busy, don't bother me!" statement in public.

I didn't know about the chuwi, sound interesting. But I'm older and the eyes are more fixed focal length now, so 15" and 1366x768 is readable for me without scaling. I can xrandr with --panning to have a viewport of a larger screen that scrolls around with the mouse. And there's --transform or --scale and --scale-from to make a 1080p X session scale to 1366x768, although mostly only useful for media playback with best GPU perks. Luckily my needs are CPU and RAM for this machine. More of a desktop with built in UPS. And for that, a 2.5GHz quad core trumps a 1.1GHz quad core.

$ lspci -nnk
Code:
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
	Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [103c:80c3]
	Kernel driver in use: r8169
	Kernel modules: r8169
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:d723]
	Subsystem: Hewlett-Packard Company Device [103c:8319]
Searching on [103c:80c3] (ethernet) and [10ec:d723] (wifi) results mostly in posts about I have issues. Most of which have 0 responses. And patches seem to be dated near 2008 and 2013, which probably don't apply to these devices. So far the only glimmer of hope is realtek is working on a driver, slated for Q4 2017.
 
Old 11-11-2017, 09:01 AM   #4
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
So reverting to the ndiswrapper driver for the rtl8723de wifi b/g/n device.

Mounting the windows partition: /dev/sda3

Copying the .inf and .sys files: ./Windows/System32/DriverStore/FileRepository/rtl8723de.inf_amd64_a2655c09ac6e93b0/

And applying them to linux. Not as easy as debian stable (stretch) packages are not always available in debian testing (buster).

https://wiki.debian.org/NdisWrapper

https://packages.debian.org/stretch/ndiswrapper
https://packages.debian.org/stretch/ndiswrapper-source

And click the amd64 link near the bottom to get the .deb file(s) URL(s).

$ wget -c http://http.us.debian.org/debian/poo...60-3_amd64.deb
$ wget -c http://http.us.debian.org/debian/poo...1.60-3_all.deb

One is the tools to use ndiswrapper, the other is the kernel driver. Note that non-distro supplied kernel drivers will need to be re-created / applied with each kernel update/upgrade.

Assuming you put those in their own directory and are in that directory.

$ sudo dpkg -i *.deb
$ sudo apt-get -f install
$ sudo dpkg -i *.deb

One trick of sorts to get the dependencies not yet installed.

$ sudo tar -xjvpf /usr/src/ndiswrapper.tar.bz2
$ cd ./modules/ndiswrapper/

The source code for the kernel module. Which doesn't seem to compile for a 4.13 kernel. using dkms or modules-assistant also seems to fail.

Code:
[error: ‘struct net_device’ has no member named ‘last_rx’]
As mentioned in several bug reports. Or from my own logs:

Code:
/modules/ndiswrapper/ndis.c:2464:14: error: ‘struct net_device’ has no member named ‘last_rx’
  wnd->net_dev->last_rx = jiffies;
So much for that effort. Living the dongle life I guess.
 
Old 11-18-2017, 02:14 AM   #5
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
An update gave an installed version of ndiswrapper. 1.60-5 versus 1.60-3

# ndiswrapper -i rtl8723de.inf
# ndiswrapper -mi
# ndiswrapper -ma
# ndiswrapper -l
Code:
rtl8723de : driver installed
	device (10EC:D723) present
# modprobe -r ndiswrapper
# modprobe ndiswrapper
Code:
Message from syslogd@localhost at Nov 18 02:09:02 ...
 adndisdriver: loadndisdriver: load_driver(364): couldn't load driver rtl8723de
With massive and ugly stuff in dmesg
$ dmesg
Code:
...
[649887.921406] ndiswrapper version 1.60 loaded (smp=yes, preempt=no)
[649887.945922] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'PoUnregisterPowerSettingCallback'
[649887.945938] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'PoRegisterPowerSettingCallback'
[649887.945943] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'EtwWriteTransfer'
[649887.945948] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'EtwSetInformation'
[649887.945955] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'EtwUnregister'
[649887.945960] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'EtwRegister'
[649887.945972] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
[649887.946003] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'__chkstk'
[649887.946008] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'strncpy_s'
[649887.946024] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ExGetFirmwareEnvironmentVariable'
[649887.946039] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'wcsstr'
[649887.946057] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ZwEnumerateKey'
[649887.946064] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'IoCsqInitialize'
[649887.946068] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'IoCsqInsertIrp'
[649887.946073] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'IoCsqRemoveNextIrp'
[649887.946079] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ZwDeviceIoControlFile'
[649887.946085] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ExAllocatePoolWithQuotaTag'
[649887.946090] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'PsGetVersion'
[649887.946094] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ZwQuerySystemInformation'
[649887.946104] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMFreeNetBufferSGList'
[649887.946110] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
[649887.946116] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
[649887.946123] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterWdiMiniportDriver'
[649887.946128] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterWdiMiniportDriver'
[649887.946134] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
[649887.946140] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMAllocateNetBufferSGList'
[649887.946145] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterScatterGatherDma'
[649887.946151] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterScatterGatherDma'
[649887.946169] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSynchronizeWithInterruptEx'
[649887.946175] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterInterruptEx'
[649887.946180] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterInterruptEx'
[649887.946186] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeMdl'
[649887.946214] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
[649887.946220] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
[649887.946247] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
[649887.946253] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSetBusData'
[649887.946258] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMGetBusData'
[649887.946269] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMFreePort'
[649887.946274] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMAllocatePort'
[649887.946280] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMNetPnPEvent'
[649887.946285] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
[649887.946291] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
[649887.946296] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeTimerObject'
[649887.946371] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisCancelTimerObject'
[649887.946376] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetTimerObject'
[649887.946381] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateTimerObject'
[649887.946386] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
[649887.946395] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
[649887.946399] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
[649887.946426] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisRegisterDeviceEx'
[649887.946430] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisDeregisterDeviceEx'
[649887.946437] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
[649887.946448] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
[649887.946453] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
[649887.946459] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
[649887.946463] ndiswrapper (import:232): unknown symbol: WDFLDR.SYS:'WdfVersionBindClass'
[649887.946466] ndiswrapper (import:232): unknown symbol: WDFLDR.SYS:'WdfVersionUnbind'
[649887.946470] ndiswrapper (import:232): unknown symbol: WDFLDR.SYS:'WdfVersionBind'
[649887.946474] ndiswrapper (import:232): unknown symbol: WDFLDR.SYS:'WdfVersionUnbindClass'
[649887.946477] ndiswrapper (load_sys_files:200): couldn't prepare driver 'rtl8723de'
[649887.948884] ndiswrapper (load_wrap_driver:103): couldn't load driver rtl8723de; check system log for messages from 'loadndisdriver'
[649887.951810] usbcore: registered new interface driver ndiswrapper
It was worth a shot anyway.
 
Old 11-23-2017, 11:57 PM   #6
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
After 19 days of uptime on debian buster (testing), I finally booted arch on this laptop. And so far the 8169 ethernet is stable under arch on the LTS kernel. Odd since it's a 4.9.x kernel where buster is on a 4.13 kernel. Hopefully that doesn't mean future breakage. But it's nice to have one less dongle. And with the help of a lego (megablock) structure, access to the usb 3.x port on the bottom (my orientation) of the laptop. As I note that the ba053nr variant has about 2.5 hours of battery life if left unplugged while playing runescape. Although arch complains about the setup of the [vender:device] for the video card at the initial boot. But works just fine, once you press Alt+F2 to get to a console with a login (versus the error message).
 
Old 12-22-2017, 12:58 PM   #7
deepclutch
Member
 
Registered: Nov 2004
Distribution: Debian Testing+Sid
Posts: 730
Blog Entries: 1

Rep: Reputation: 33
@Shadow 7: There is an unofficial driver for RTL8723DE wireless module and it works fine. You have to build from the sources, but that's child's play: https://www.linuxquestions.org/quest...2/#post5796518
 
Old 12-22-2017, 04:09 PM   #8
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
That's nice to know. I tried googling one and found only hints of a driver to arrive late 2017. With no actual driver links. Even though it's now mere days till 2018. I guess it's time to give buster another shot on the other laptop. Now that I know the magic github link.

Code:
$ git clone https://github.com/smlinux/rtl8723de.git
The r8169 driver did get wonky after about 20 days. Bringing down the network, modprobe -r, then modprobe of the driver brought things back though. It's been soo long since I've had network driver issues in linux. I've gotten spoiled with sbc's aimed at linux I guess. Works out of the box has been the norm, until now. Baring the usual firmware not installed by default quirks.
 
Old 12-28-2017, 02:17 PM   #9
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,581
Blog Entries: 1

Original Poster
Rep: Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778Reputation: 778
I did a fresh install of debian buster via debootstrap and the ethernet now works under debian testing/buster. I installed the github source for the wireless and iwconfig shows it has wireless extensions so things are looking good now. Without a reboot I did have to modprobe cfg80211 before doing an insmod on the 8723de.ko module. Unknown symbol errors without the pre-emptive cfg80211 module loaded. Probably self correcting if I reboot. Or I veered off course too quickly (went old school) when modprobe rtl8723de failed, as the module is actually named 8723de.

# modprobe cfg80211
# insmod /lib/modules/4.14.0-2-amd64/kernel/drivers/net/wirless/8723de.ko

# ip link set wlo1 up
# iw dev wlo1 scan

That returned results so I assume it works now. A long ways from initial impressions anyway. A laptop without networking is a scary thought.
 
Old 01-08-2018, 04:20 PM   #10
deepclutch
Member
 
Registered: Nov 2004
Distribution: Debian Testing+Sid
Posts: 730
Blog Entries: 1

Rep: Reputation: 33
Official Realtek Linux driver for RTL8723DE is available in rtlwifi-new git repository maintained by Larry Fingers. This module uses mac80211 and not cfg80211. This is the driver that will end up in kernel. The driver is available in the "extended" branch of the said repository. I believe this is better as I get better signal strength in my new HP 15-BS576TX laptop using the rtl8723de module with parameter "ant_sel=2". You can use dkms to build the module also.

Steps are explained here: https://h30434.www3.hp.com/t5/Notebo...t/true#M146866

https://h30434.www3.hp.com/t5/Notebo...t/true#M146067

Now, what is left is RTL8723DE Bluetooth support. I tried extracting Windows driver provided (few .cab files). But, cannot figure out the firmware.

Last edited by deepclutch; 01-08-2018 at 04:21 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 09:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration