``` Laptop basics: i7-2620M cores AMD graphics 7.45GiB RAM’s 953GiB total SSD’s ``` `FreeBSD-13.0-CURRENT-amd64-20200806-r363935-memstick.img`: Failed (for **both** CloverEFI and legacy BIOS modes) Below those are **untested**, ``` FreeBSD-13.0-CURRENT-amd64-20200806-r363935-disc1.iso FreeBSD-13.0-CURRENT-amd64-20200730-r363681-memstick.img FreeBSD-13.0-CURRENT-amd64-20200723-r363439-memstick.img FreeBSD-13.0-CURRENT-amd64-20200716-r363236-memstick.img FreeBSD-13.0-CURRENT-amd64-20200730-r363681-disc1.iso FreeBSD-13.0-CURRENT-amd64-20200723-r363439-disc1.iso FreeBSD-13.0-CURRENT-amd64-20200716-r363236-disc1.iso ``` https://forums.freebsd.org/threads/sony-made-vaio-vpccb17fg-issues.76547 [IMG]https://i.imgur.com/aRA3bF9h.jpg[/IMG]

@"hd_scania"#p3555 At the loader screen, choose `6.` (for boot options), then switch both `Safe mode` and `Verbose` to on. Is this a new problem, or did FreeBSD boot OK on this laptop before?

The discussion continued at https://forums.freebsd.org/threads/sony-made-vaio-vpccb17fg-issues.76547/

@"aponomarenko"#p3643 Looks like you have things well in hand over there. Thanks, however, for keeping us informed.

Yep, fixed by changing the USB stick and adding `kern.cam.ada.write_cache=0` boot option.

And i need to also get the wifi chip back to working connections My chip is codenamed `ath0` on FreeBSD and to be assigned as `wlan0` And which commands can do this? I took a break from BSD for about 0.5 years Now i need to back to BSD thru FreeBSD, then when done, i need to take some snaps to show my FreeBSD desktops on a new hardware☺️

The wireless issue was gone too, but the XFCE shell was NO mice available with the touchpad **disabled**, i have TWO USB and wireless mice but BOTH were NOT working And finally, the Plasma shell was blunk in black, so i’m yet to need to also test out **Enlightenment and Lumina** i’ve also installed on FreeBSD, alongside Plasma and XFCE

Does `/etc/rc.conf` contain `moused_enable="YES"`? Have you made any changes to the Xorg config files?

@"rvp"#p3829 Yes and `moused_type` has been set to `auto` too, but ahead `moused_enable=YES` And i haven't even touched the Xorg configs at all

And given there *were* kernel issues which got the system constantly crashed too (and now done by a note on the FreeBSD docs on kernel debugging), finally *was* likely getting `moused` crashed too

[13-CURRENT] Sony-made VAIO VPCCB17FG issues

rvp

hd_scania the AC female was expected to be loose, due to already being aged for at least a decade

So, the AC barrel socket was loose?
You can easily solder it yourself (or pay an electronics engineering student to do it for you) after you buy a replacement socket.

It is an interesting laptop, though. I don't know many laptops with 2 graphics cards in it:

vgapci1@pci0:0:2:0: class=0x030000 card=0x9080104d chip=0x01268086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '2nd Generation Core Processor Family Integrated Graphics Controller'
    class      = display
    subclass   = VGA
    ...
vgapci0@pci0:1:0:0: class=0x030000 card=0x9080104d chip=0x67411002 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M]'
    class      = display
    subclass   = VGA

hd_scania

Yeah i paid for someone in 10GBP to do for me
AC barrel socket? Unsure wtf barrel socket was, but the AC female is still being loose

rvp

hd_scania the AC female is still being loose

Same thing. Also called a receptacle, jack, ...

hd_scania

On my BOTH BSD and Linux sides, under a same battery, but too differently seen to the BOTH systems on a completely same battery
On no-systemd Linux: The battery state normal
On FreeBSD: The battery NEVER above -1% but NEVER rechargeable
Even though the transform brick is renewed, but still, the FreeBSD side has always abnormally perceived a totally wrong battery dataset

hd_scania

Then here, UNLIKELY hardware issues at all, but instead, there’ve been some fatal ACPI or kernel bugs too wrongly reading the battery data

rvp

hd_scania Then here, UNLIKELY hardware issues at all, but instead, there’ve been some fatal ACPI or kernel bugs too wrongly reading the battery data

Not exactly a FreeBSD kernel bug (see post #32 where we determined this already).

The main problem here is that your battery is providing wrong (voltage) values. The kernel takes that bogus voltage, does a small computation on it, then looks at the result, and says: "Huh?! this doesn't look right", and then removes that battery from the system. Linux, probably just skips using that voltage, but keeps the battery online. I'll have to check and see.

hd_scania And i was asked to add the line hw.x2apic_enable=0 onto the kernel command lines
But does this affect my battery UNREADABLE to the system (only on FreeBSD, but NOT on Linux)?

Highly unlikely. You probably don't need that line in /boot/loader.conf. Just remove it.

For now:

Ignore the battery stats on FreeBSD. Look at the HW/firmware-controlled battery LED, instead.
Open the laptop up and take a photo of the specs. (voltage, mAh, ...) printed on the battery pack. I'll need it to decide how to "fix" your little battery problem.

BTW: while your laptop is opened, clean the dust out from your CPU fan/heatsink. Re-apply thermal paste if you have to. 85 C is too hot for an idle system. (Or, were you compiling GCC?)

And, to get Intel CPU temp. data in hwstat add this line to /boot/loader.conf:

coretemp_load="YES"

rvp

Run the batt.sh script in post #41.

hd_scania

rvp
https://mega.nz/file/eYhBlazS#BsPWWMIMZS28wk2nbxpQO2iXX6kqRAjux9FKX8ZJV5s

hd_scania

And i was asked to add the line hw.x2apic_enable=0 onto the kernel command lines
But does this affect my battery UNREADABLE to the system (only on FreeBSD, but NOT on Linux)?

hd_scania

rvp
But on the other hands,

Without the line hw.x2apic_enable=0 STALL the system from BEFORE the init scripts
But with that line CRASHES the kernel too
But by having added coretemp on the line kldload_list in my rc.conf (or the same to be loaded in /boot/loader.conf), and the first line PERM REMOVED, will just be working fine?

Highly unlikely. You probably don't need that line in /boot/loader.conf. Just remove it.

hd_scania

rvp Open the laptop up and take a photo of the specs. (voltage, mAh, ...) printed on the battery pack. I'll need it to decide how to "fix" your little battery problem.

hd_scania

Yes i’ve just tested a few mins ago, without the line hw.x2apic_enable=0 DOESN’T work, from your coretemp kernel mods to be suggested instead, does this suggest that, my CPU overheat crashes the system?

rvp

hd_scania without the line hw.x2apic_enable=0 DOESN’T work,

Really? I thought it was the other line kern.cam.ada.write_cache=0 (post #5) which fixed that problem. Well, if that option is also needed, keep it.

hd_scania does this suggest that, my CPU overheat crashes the system?

Are you saying now that the system crashes even on A/C power, or on a (mostly) full battery (ie. green battery LED)? I thought this problem was taken care of...

It could be heat-related, I don't know. But, the temperature is much too high for an idle, or mostly idle, system. Running powerd might help. Run these commands as root:

sysrc powerd_enable=YES
sysrc powerd_flags="-a adp -b min"

coretemp_load="YES" in /boot/loader.conf is for reporting the CPU temperature on Intel Core CPUs.

And, which FreeBSD version (RELEASE, STABLE, CURRENT) do you want the fix to be applied to?

hd_scania

You mean FreeBSD is suffering of an overheat, where even on a same laptop, Linuxes aren’t?
IIRC it’s been told to me a few years ago, in hot weathers FreeBSD sometimes suffers of an overheat, on my dead laptops YES, certain FreeBSD distroes were hence constantly crashing the system too

rvp Are you saying now that the system crashes even on A/C power, or on a (mostly) full battery (ie. green battery LED)? It could be heat-related, I don't know. But, the temperature is much too high for an idle, or mostly idle, system

rvp

Need some kernel messages: make sure you have

hw.acpi.verbose=1

in /boot/loader.conf, then reboot, run the batt.sh script for a minute, and then do a dmesg:

dmesg > /tmp/dmesg.txt

Post dmesg.txt.

rvp

hd_scania You mean FreeBSD is suffering of an overheat, where even on a same laptop, Linuxes aren’t?

What I meant was that 85 degC was too hot for an idle laptop CPU. Desktop CPUs, of course, run hotter.

On my ASUS laptop:
FreeBSD with powerd and the powerd_flags I gave you, idle CPU temp: 45-50 degC
Ubuntu 19.04 stock kernel and default settings: 50-55 degC
NetBSD_9.0-STABLE with estd: 60-65 degC

As you see, Linux and FreeBSD temperatures are roughly similar--in fact, FreeBSD runs 5 degC cooler than Linux. NetBSD runs hot: 20 degC hotter than FreeBSD.

(Personally, I feel only babes should ever be hot; OSes should run cool.)

hd_scania

Here, i need to announce that the issue was SOLVED
By having ordered a cooldown panel under the laptop
And finally, my own screenshot below,

rvp

hd_scania Here, i need to announce that the issue was SOLVED
By having ordered a cooldown panel under the laptop

Great!--glad to hear this. But,

Are the battery values also OK now? (run batt.sh and post dmesg output after setting hw.acpi.verbose=1 in /boot/loader.conf)
Are the other 2 /boot/loader.conf values suggested by @aponomarenko also needed?
~~What do you mean by "cooldown panel"?~~

hd_scania

rvp Cooldown panel? Yes a cooling panel designed for desktops

rvp

hd_scania Yes a cooling panel designed for desktops

Yeah, I googled that: laptop cooling pad = Big honking fans with bells and whistles.

But, I still need answers to the other 2 questions.

hd_scania

rvp

rvp batt.sh: https://pastebin.com/ywvpyj7A
dmesg,

[hd_scania@hd-scania /home/fu1i]$ sudo dmesg|grep -Eie 'batt|power|acpi|temp'
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
ACPI APIC Table: <Sony VAIO>
acpi0: <Sony> on motherboard
acpi_ec0: <Embedded Controller: GPE 0x17, ECDT> port 0x62,0x66 on acpi0
cpu0: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci5: <ACPI PCI bus> on pcib5
battery0: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
uhub2: 4 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub3: 6 ports with 6 removable, self powered
uhub4: 6 ports with 6 removable, self powered
[hd_scania@hd-scania /home/fu1i]$

« Previous Page Next Page »