Upgrading Harware - Is reinstall required!

makh · 2020-09-17 10:30:13

Hi

I have upgraded my laptop from Hp 440G2 to Dell Vostro 14-3468.

But I used the same Hard disk.

Please inform: do I need to reinstall Linux; ... but every thing seems to be working fine!

Regards

d_fajardo · 2020-09-17 10:43:48

No but you probably need to update your network configuration since you will have a different device ID, etc.
Are you able to boot without updating the NVRAM in your new laptop? That's surprising because normally you will have to update the NVRAM entry.
Unless of course you are booting via BIOS instead of EFI. Are you?

solskog · 2020-09-17 10:49:25

I can only refer to my own experience. If both using intel CPU then keep intel-ucode, linux-firmware updated.
Check if GPU vendor are same, if not, change to respective gpu driver package, with Nvida proprietary driver you may get hardware decoding support, due to open source Nouveau not yet available for newer card.

Last edited by solskog (2020-09-17 10:50:21)

makh · 2020-09-17 10:59:16

Hi

The only error I get in boot is:

dmesg |grep error

[   16.335202] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   17.142826] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[   17.142913] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00002001/00002000
[   28.819475] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[   28.821164] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00000001/00002000
[   28.864408] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[   28.866132] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00000001/00002000
[   29.284426] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[   29.286209] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00003041/00002000
[   29.293181] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[   29.293193] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   29.293203] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[  139.671704] unchecked MSR access error: RDMSR from 0x123 at rIP: 0xffffffffbb66ba04 (native_read_msr+0x4/0x30)
[  139.671718] unchecked MSR access error: WRMSR to 0x123 (tried to write 0x0000000000000000) at rIP: 0xffffffffbb66bbe4 (native_write_msr+0x4/0x20)
[  141.772740] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20190816/psparse-529)

Regards

makh · 2020-09-17 11:01:35

d_fajardo wrote:

No but you probably need to update your network configuration since you will have a different device ID, etc.
Are you able to boot without updating the NVRAM in your new laptop? That's surprising because normally you will have to update the NVRAM entry.
Unless of course you are booting via BIOS instead of EFI. Are you?

Hi,
I installed the GPT in compatible mode method!

I dont know about NVRAM. Let me check.

Thankyou

makh · 2020-09-17 11:03:27

solskog wrote:

I can only refer to my own experience. If both using intel CPU then keep intel-ucode, linux-firmware updated.
Check if GPU vendor are same, if not, change to respective gpu driver package, with Nvida proprietary driver you may get hardware decoding support, due to open source Nouveau not yet available for newer card.

Hi

Let me see! Both machines have integrated Intel Graphics within the processor!

Thankyou

makh · 2020-09-17 11:06:09

Hi

Pulse Audio is working, but alsamixer is not!

WorMzy · 2020-09-17 11:07:18

Please don't multipost like that, you can respond to multiple people in one message, and use the edit button to amend a post if you have something to add.

V1del · 2020-09-17 11:19:08

You've apparently identified that everything seems to still work as expected, what exactly is the purpose of this thread? You can generally reuse the same harddisk, relevant module loading adjustments will happen automatically. Unless you use configuration where you explicitly reference specific hardware of your old laptop this will (..and apparently does...) work fine.

solskog · 2020-09-17 11:38:28

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

This error is related to the wireless regulatory database signature missmatch. I don't think it will break anything now. but don't known what it could cause in long term.

makh · 2020-09-17 14:09:46

Hi

@WorMzy: Ok Fine! Thankyou

@V1del: The few errors I got on startup were worrying me... infact I never thought of running a machine like this before!

@solskog: Thankyou. I hope so!

Regards,

loqs · 2020-09-17 14:35:27

solskog wrote:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
This error is related to the wireless regulatory database signature missmatch. I don't think it will break anything now. but don't known what it could cause in long term.

-2 is error code 2 made negative, which is is no such file or directory. Is the wireless-regdb package installed?

makh · 2020-09-18 14:57:32

loqs wrote:

solskog wrote:
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
This error is related to the wireless regulatory database signature missmatch. I don't think it will break anything now. but don't known what it could cause in long term.
-2 is error code 2 made negative, which is is no such file or directory. Is the wireless-regdb package installed?

Hi,

I just installed it but still have:

dmesg |grep Err
[    0.530868] RAS: Correctable Errors collector initialized.
[   18.902179] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   18.902190] pcieport 0000:00:1c.0: AER:    [ 0] RxErr                  (First)
[   30.977541] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   30.980896] pcieport 0000:00:1c.0: AER:    [ 0] RxErr                  (First)
[   31.025836] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   31.029320] pcieport 0000:00:1c.0: AER:    [ 0] RxErr                  (First)
[   31.411938] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   31.415434] pcieport 0000:00:1c.0: AER:    [ 0] RxErr                  (First)
[   31.455813] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   31.459417] pcieport 0000:00:1c.0: AER:    [ 0] RxErr                  (First)

Thankyou

solskog · 2020-09-18 23:55:54

Pls Read this thread and solution for

PCIe Bus Error: severity=Corrected

https://bbs.archlinux.org/viewtopic.php?id=242182

Arch Linux

#1 2020-09-17 10:30:13

Upgrading Harware - Is reinstall required!

#2 2020-09-17 10:43:48

Re: Upgrading Harware - Is reinstall required!

#3 2020-09-17 10:49:25

Re: Upgrading Harware - Is reinstall required!

#4 2020-09-17 10:59:16

Re: Upgrading Harware - Is reinstall required!

#5 2020-09-17 11:01:35

Re: Upgrading Harware - Is reinstall required!

#6 2020-09-17 11:03:27

Re: Upgrading Harware - Is reinstall required!

#7 2020-09-17 11:06:09

Re: Upgrading Harware - Is reinstall required!

#8 2020-09-17 11:07:18

Re: Upgrading Harware - Is reinstall required!

#9 2020-09-17 11:19:08

Re: Upgrading Harware - Is reinstall required!

#10 2020-09-17 11:38:28

Re: Upgrading Harware - Is reinstall required!

#11 2020-09-17 14:09:46

Re: Upgrading Harware - Is reinstall required!

#12 2020-09-17 14:35:27

Re: Upgrading Harware - Is reinstall required!

#13 2020-09-18 14:57:32

Re: Upgrading Harware - Is reinstall required!

#14 2020-09-18 23:55:54

Re: Upgrading Harware - Is reinstall required!

Board footer