Adapter quirk: no zero length

I’ve already searched this up online and it does not appear to be that common. Has anyone else seen this?

Looks like it has to do with my msi graphics card.

System boots and works as it should.

Boot log output (only the relevant bit).

Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x0018, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x0019, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001a, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001b, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001c, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001d, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001e, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-0: adapter quirk: no zero length (addr 0x001f, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-1: adapter quirk: no zero length (addr 0x0018, size 0, write)
Aug 15 17:29:04 desktop kernel: i2c i2c-1: adapter quirk: no zero length (addr 0x0019, size 0, write)

From what I can tell with some research, this is just informational and shouldn’t usually cause any issues. :thinking:

I don’t recall seeing such errors myself though; maybe I ought to check my boot logs. :wink:

You would have noticed it if you have verbose boot turned on. The text comes up in bright red at the start of the boot process.

And thanks for your reply. The couple of posts I found on the subject also suggested that it’s not a big problem.

1 Like

I do have verbose boot; I removed “quiet” and “splash” from the GRUB commandline. (I also removed “Plymouth” from the hooks= line in /etc/mkinitcpio.conf but take care if you are using encryption; best to ask first).

What effect does that have?

No (more or less pretty) picture/animation during boot - just text scrolling by.

Remove “splash” from the line:
GRUB_CMDLINE_LINUX_DEFAULT=
in
/etc/default/grub too.

It’s easily reversible … just add the keyword again in the two files.

1 Like

Thanks, but that’s the thing that I already knew. That’s how I always enable verbose boot.

What I would like to know is, what does this do? I have no idea.

It doesn’t include the plymouth binary in the initial ram disk.
… the animation will not be as smooth because while the initrd is started, plymouth isn’t there - only later, when the root is switched to the real file system.

If you have encryption, for example - you won’t have a fancy password prompt, but just TTY looking input.

Thanks for explaining. :+1: