Unknown NV_ARC
 

Re: My old 2008 HP G60 Intel Core2 Duo T5800 bits:64 Laptop…

This post is only to describe boot process after unlocking crypt – I am aware of the could not open policy file….etc.
Then: waiting for /dev to be fully populated I get:

nvidiafb: unknown NV_ARC
The next line is simply “H” followed by next line “done”
Everything seems to be working just fine with no graphical issues…
Am I okay with leaving as is..?


Graphics:
Device-1: NVIDIA G98M [GeForce 9200M GS] vendor: Hewlett-Packard
driver: nouveau v: kernel arch: Tesla pcie: speed: 2.5 GT/s lanes: 16
ports: active: LVDS-1 empty: HDMI-A-1,VGA-1 bus-ID: 01:00.0
chip-ID: 10de:06e8 class-ID: 0300
Device-2: Chicony Webcam type: USB driver: uvcvideo bus-ID: 1-5:3
chip-ID: 04f2:b091 class-ID: 0e02 serial: SN0001
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: nouveau display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: LVDS-1 model: AU Optronics 0x10ec res: 1366x768 hz: 60
dpi: 101 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") modes:
max: 1366x768 min: 640x350
OpenGL: renderer: NV98 v: 3.3 Mesa 20.3.5 direct render: Yes

Might explain things . Or not. At least yours boots and work.

Lot of boot incompletions/hangups when one searches your error message.

https://www.reddit.com/r/linuxquesti..._driver_error/

interesting link
 

Thanks – interesting link..

It suggests that blacklisting - “modprobe.blacklist=nvidiafb to the kernel cmdline - that causes the error message to be absent.”
Do we presume that this kills the conflict..?
Is there a difference 'twixt my NV_ARC & NV_ARCH..?

Anyhow if it ain't broke don’t try to fix it...

ps Did Hazel have a similar issue before my time here..?