#dmesg — Public Fediverse posts

Dear #lazyweb

Frustratingly a recent #debian update broke #kodi's ability to play #1080p videos. I don't get much more from kodi's log than "error <general>: eglSwapBuffers failed (EGL_BAD_ALLOC)". I've tried messing with various setting to no avail and nothing obvious appears in #dmesg output. The 720p videos still play fine and I know some of the failing videos worked last week before the update.

Any hints welcome ;-)

Dear #lazyweb

Frustratingly a recent #debian update broke #kodi's ability to play #1080p videos. I don't get much more from kodi's log than "error <general>: eglSwapBuffers failed (EGL_BAD_ALLOC)". I've tried messing with various setting to no avail and nothing obvious appears in #dmesg output. The 720p videos still play fine and I know some of the failing videos worked last week before the update.

Any hints welcome ;-)

Dear #lazyweb

Frustratingly a recent #debian update broke #kodi's ability to play #1080p videos. I don't get much more from kodi's log than "error <general>: eglSwapBuffers failed (EGL_BAD_ALLOC)". I've tried messing with various setting to no avail and nothing obvious appears in #dmesg output. The 720p videos still play fine and I know some of the failing videos worked last week before the update.

Any hints welcome ;-)

Dear #lazyweb

Frustratingly a recent #debian update broke #kodi's ability to play #1080p videos. I don't get much more from kodi's log than "error <general>: eglSwapBuffers failed (EGL_BAD_ALLOC)". I've tried messing with various setting to no avail and nothing obvious appears in #dmesg output. The 720p videos still play fine and I know some of the failing videos worked last week before the update.

Any hints welcome ;-)

Dear #lazyweb

Frustratingly a recent #debian update broke #kodi's ability to play #1080p videos. I don't get much more from kodi's log than "error <general>: eglSwapBuffers failed (EGL_BAD_ALLOC)". I've tried messing with various setting to no avail and nothing obvious appears in #dmesg output. The 720p videos still play fine and I know some of the failing videos worked last week before the update.

Any hints welcome ;-)

dmesg is almost pretty in the dark

I was just leaving my flat to go and buy some obligatory Saturday night peanut butter (crunchy, of course), when dmesg -w, which I was running to troubleshoot my network, suddenly looked pretty in the dark.

:3

dmesg is almost pretty in the dark

I was just leaving my flat to go and buy some obligatory Saturday night peanut butter (crunchy, of course), when dmesg -w, which I was running to troubleshoot my network, suddenly looked pretty in the dark.

:3

dmesg is almost pretty in the dark

I was just leaving my flat to go and buy some obligatory Saturday night peanut butter (crunchy, of course), when dmesg -w, which I was running to troubleshoot my network, suddenly looked pretty in the dark.

:3

dmesg is almost pretty in the dark

I was just leaving my flat to go and buy some obligatory Saturday night peanut butter (crunchy, of course), when dmesg -w, which I was running to troubleshoot my network, suddenly looked pretty in the dark.

:3

dmesg is almost pretty in the dark

I was just leaving my flat to go and buy some obligatory Saturday night peanut butter (crunchy, of course), when dmesg -w, which I was running to troubleshoot my network, suddenly looked pretty in the dark.

:3

* pre start check
* pneumatic pressure build
* clutch & gear I
* press gas slowly release clutch till gear engage
* instrument scan RPM meter glance
* mirror scan
* next gear

#MyFirstToot #spawn #Whoami #dmesg #man

* pre start check
* pneumatic pressure build
* clutch & gear I
* press gas slowly release clutch till gear engage
* instrument scan RPM meter glance
* mirror scan
* next gear

#MyFirstToot #spawn #Whoami #dmesg #man

* pre start check
* pneumatic pressure build
* clutch & gear I
* press gas slowly release clutch till gear engage
* instrument scan RPM meter glance
* mirror scan
* next gear

#MyFirstToot #spawn #Whoami #dmesg #man

* pre start check
* pneumatic pressure build
* clutch & gear I
* press gas slowly release clutch till gear engage
* instrument scan RPM meter glance
* mirror scan
* next gear

#MyFirstToot #spawn #Whoami #dmesg #man

* pre start check
* pneumatic pressure build
* clutch & gear I
* press gas slowly release clutch till gear engage
* instrument scan RPM meter glance
* mirror scan
* next gear

#MyFirstToot #spawn #Whoami #dmesg #man

У меня нет звука, но я должен слышать: история одной регрессии ядра

Что делать, если после очередного обновления Linux на старом ноутбуке намертво отвалился звук, а в логах висит зловещее CORB reset timeout и 0xFFFF ? Переустановка аудио-серверов не поможет, параметры загрузчика GRUB система упорно игнорирует, а LTS-ядро больше не гарантирует стабильности. В этой статье разбираем, как спуститься в логи dmesg , понять, почему устройство «задыхается» на шине PCI, и заставить ядро заново проинициализировать аудиокарту «на горячую» с помощью sysfs и systemd. Найти звук

https://habr.com/ru/articles/1022090/

#linux #dmesg #pci #systemd #troubleshooting #sndhdaintel #kernel #alsa #старое_железо #archlinux

У меня нет звука, но я должен слышать: история одной регрессии ядра

Что делать, если после очередного обновления Linux на старом ноутбуке намертво отвалился звук, а в логах висит зловещее CORB reset timeout и 0xFFFF ? Переустановка аудио-серверов не поможет, параметры загрузчика GRUB система упорно игнорирует, а LTS-ядро больше не гарантирует стабильности. В этой статье разбираем, как спуститься в логи dmesg , понять, почему устройство «задыхается» на шине PCI, и заставить ядро заново проинициализировать аудиокарту «на горячую» с помощью sysfs и systemd. Найти звук

https://habr.com/ru/articles/1022090/

#linux #dmesg #pci #systemd #troubleshooting #sndhdaintel #kernel #alsa #старое_железо #archlinux

У меня нет звука, но я должен слышать: история одной регрессии ядра

Что делать, если после очередного обновления Linux на старом ноутбуке намертво отвалился звук, а в логах висит зловещее CORB reset timeout и 0xFFFF ? Переустановка аудио-серверов не поможет, параметры загрузчика GRUB система упорно игнорирует, а LTS-ядро больше не гарантирует стабильности. В этой статье разбираем, как спуститься в логи dmesg , понять, почему устройство «задыхается» на шине PCI, и заставить ядро заново проинициализировать аудиокарту «на горячую» с помощью sysfs и systemd. Найти звук

https://habr.com/ru/articles/1022090/

#linux #dmesg #pci #systemd #troubleshooting #sndhdaintel #kernel #alsa #старое_железо #archlinux

$ dmesg|less

#Linux #dmesg #sh #bash #csh #ksh #zsh #fish #programming #OpenSource #mathematics #technology

$ dmesg|less

#Linux #dmesg #sh #bash #csh #ksh #zsh #fish #programming #OpenSource #mathematics #technology

$ dmesg|less

#Linux #dmesg #sh #bash #csh #ksh #zsh #fish #programming #OpenSource #mathematics #technology

$ dmesg|less

#Linux #dmesg #sh #bash #csh #ksh #zsh #fish #programming #OpenSource #mathematics #technology

$ dmesg|less

#Linux #dmesg #sh #bash #csh #ksh #zsh #fish #programming #OpenSource #mathematics #technology

I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

Here is the message (reformatted to hopefully suit mastodon's boxes):
[ 0.205100] apple-properties: device path parse error -19 at 0x14:
00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
00000050: 12 04 ..

"-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

#linux #UnifiedExtensibleFirmwareInterface

I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

Here is the message (reformatted to hopefully suit mastodon's boxes):
[ 0.205100] apple-properties: device path parse error -19 at 0x14:
00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
00000050: 12 04 ..

"-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

#linux #UnifiedExtensibleFirmwareInterface

I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

Here is the message (reformatted to hopefully suit mastodon's boxes):
[ 0.205100] apple-properties: device path parse error -19 at 0x14:
00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
00000050: 12 04 ..

"-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

#linux #UnifiedExtensibleFirmwareInterface

I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

Here is the message (reformatted to hopefully suit mastodon's boxes):
[ 0.205100] apple-properties: device path parse error -19 at 0x14:
00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
00000050: 12 04 ..

"-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

#linux #UnifiedExtensibleFirmwareInterface

I have two #iMacs running #debian. Today, I decided to look at that #dmesg that flashes by as I boot. I do not feel any great problem, but, well, curiosity has got the better of me.

Here is the message (reformatted to hopefully suit mastodon's boxes):
[ 0.205100] apple-properties: device path parse error -19 at 0x14:
00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a R............A..
00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00 ..............,.
00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00 ..A.A.P.L.,.i.g.
00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00 -.p.l.a.t.f.o.r.
00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 04 00 m.-.i.d.........
00000050: 12 04 ..

"-19" is -ENODEV (no device). The efi table at offset 0x14 reads 01 01 06 00 00 02 ... I have no idea what the parser is expecting, or why these bytes cause it to plerk.

I have never ever looked at the EFI code before, nor really at EFI at all. It has always JustWorked for me. But ... well, now I am curious.

It is the remotest of chances, but, does anyone out there have a clue or *clue for me?

#linux #UnifiedExtensibleFirmwareInterface

fw_update(8) now checks dmesg(8) output in addition to dmesg.boot https://www.undeadly.org/cgi?action=article;sid=20251230094932 #openbsd #firmware #fw_update #dmesg

fw_update(8) now checks dmesg(8) output in addition to dmesg.boot https://www.undeadly.org/cgi?action=article;sid=20251230094932 #openbsd #firmware #fw_update #dmesg

fw_update(8) now checks dmesg(8) output in addition to dmesg.boot https://www.undeadly.org/cgi?action=article;sid=20251230094932 #openbsd #firmware #fw_update #dmesg

fw_update(8) now checks dmesg(8) output in addition to dmesg.boot https://www.undeadly.org/cgi?action=article;sid=20251230094932 #openbsd #firmware #fw_update #dmesg

fw_update(8) now checks dmesg(8) output in addition to dmesg.boot https://www.undeadly.org/cgi?action=article;sid=20251230094932 #openbsd #firmware #fw_update #dmesg

I may try to sell a hardened debian on an enc persistent part - a nvme bootable usb4 device, lots of 'extras' installed - some of it depends on the hw obviously #dmesg #thunder chiken #debian blends

I may try to sell a hardened debian on an enc persistent part - a nvme bootable usb4 device, lots of 'extras' installed - some of it depends on the hw obviously #dmesg #thunder chiken #debian blends

I may try to sell a hardened debian on an enc persistent part - a nvme bootable usb4 device, lots of 'extras' installed - some of it depends on the hw obviously #dmesg #thunder chiken #debian blends

I may try to sell a hardened debian on an enc persistent part - a nvme bootable usb4 device, lots of 'extras' installed - some of it depends on the hw obviously #dmesg #thunder chiken #debian blends

[Перевод] Диагностика неполадок в Linux: эти 4 шага помогут исправить 99% ошибок

Любая неожиданная ошибка в Linux может выбесить. Но хорошая новость в том, что почти каждую проблему в Linux можно решить, если действовать просто и системно. Всего четыре базовых шага, которые подходят почти под любую ситуацию. Главное, оставаться последовательным. Эффективная диагностика в Linux — это системный подход, когда вы проверяете по одному возможному источнику проблемы за раз. В этой статье я разберу основные шаги, которыми чаще всего пользуются системные администраторы, когда Linux выдает ошибку. Этот подход одинаково хорошо работает и на серверах Linux, и на настольных системах и поможет вам справиться с чем угодно — от проблем при загрузке до «упрямых» приложений, которые не хотят нормально запускаться. 4 шага диагностики

https://habr.com/ru/companies/otus/articles/967276/

#линукс #диагностика_Linux #поиск_ошибок #системное_администрирование #логирование #journalctl #dmesg #анализ_логов #сбой_загрузки #неисправности_серверов

[Перевод] Диагностика неполадок в Linux: эти 4 шага помогут исправить 99% ошибок

Любая неожиданная ошибка в Linux может выбесить. Но хорошая новость в том, что почти каждую проблему в Linux можно решить, если действовать просто и системно. Всего четыре базовых шага, которые подходят почти под любую ситуацию. Главное, оставаться последовательным. Эффективная диагностика в Linux — это системный подход, когда вы проверяете по одному возможному источнику проблемы за раз. В этой статье я разберу основные шаги, которыми чаще всего пользуются системные администраторы, когда Linux выдает ошибку. Этот подход одинаково хорошо работает и на серверах Linux, и на настольных системах и поможет вам справиться с чем угодно — от проблем при загрузке до «упрямых» приложений, которые не хотят нормально запускаться. 4 шага диагностики

https://habr.com/ru/companies/otus/articles/967276/

#линукс #диагностика_Linux #поиск_ошибок #системное_администрирование #логирование #journalctl #dmesg #анализ_логов #сбой_загрузки #неисправности_серверов

[Перевод] Диагностика неполадок в Linux: эти 4 шага помогут исправить 99% ошибок

Любая неожиданная ошибка в Linux может выбесить. Но хорошая новость в том, что почти каждую проблему в Linux можно решить, если действовать просто и системно. Всего четыре базовых шага, которые подходят почти под любую ситуацию. Главное, оставаться последовательным. Эффективная диагностика в Linux — это системный подход, когда вы проверяете по одному возможному источнику проблемы за раз. В этой статье я разберу основные шаги, которыми чаще всего пользуются системные администраторы, когда Linux выдает ошибку. Этот подход одинаково хорошо работает и на серверах Linux, и на настольных системах и поможет вам справиться с чем угодно — от проблем при загрузке до «упрямых» приложений, которые не хотят нормально запускаться. 4 шага диагностики

https://habr.com/ru/companies/otus/articles/967276/

#линукс #диагностика_Linux #поиск_ошибок #системное_администрирование #логирование #journalctl #dmesg #анализ_логов #сбой_загрузки #неисправности_серверов

I was thinking about the https://dmesgd.nycbug.org/dmesgd?do=index&fts=cybersec website.

Do you guys believe that it is ok, to post your dmesg ? Or... doing it might raise security concerns ?

Thanks in advance, Yours Truly

#dmesg #nycbug #openbsd #freeBSD #dragonflybsd

I was thinking about the https://dmesgd.nycbug.org/dmesgd?do=index&fts=cybersec website.

Do you guys believe that it is ok, to post your dmesg ? Or... doing it might raise security concerns ?

Thanks in advance, Yours Truly

#dmesg #nycbug #openbsd #freeBSD #dragonflybsd

I was thinking about the https://dmesgd.nycbug.org/dmesgd?do=index&fts=cybersec website.

Do you guys believe that it is ok, to post your dmesg ? Or... doing it might raise security concerns ?

Thanks in advance, Yours Truly

#dmesg #nycbug #openbsd #freeBSD #dragonflybsd

I was thinking about the https://dmesgd.nycbug.org/dmesgd?do=index&fts=cybersec website.

Do you guys believe that it is ok, to post your dmesg ? Or... doing it might raise security concerns ?

Thanks in advance, Yours Truly

#dmesg #nycbug #openbsd #freeBSD #dragonflybsd

Playing in my dmesg output again.

Since the miniPC has a broken GPU and CPU (APU one die) thanks to Gigabytes puny small APU fan, I seek messages to find more unstable things the kernel found so I can disable them,.

#Linux #POST #dmesg #kernel

Playing in my dmesg output again.

Since the miniPC has a broken GPU and CPU (APU one die) thanks to Gigabytes puny small APU fan, I seek messages to find more unstable things the kernel found so I can disable them,.

#Linux #POST #dmesg #kernel

Playing in my dmesg output again.

Since the miniPC has a broken GPU and CPU (APU one die) thanks to Gigabytes puny small APU fan, I seek messages to find more unstable things the kernel found so I can disable them,.

#Linux #POST #dmesg #kernel

Playing in my dmesg output again.

Since the miniPC has a broken GPU and CPU (APU one die) thanks to Gigabytes puny small APU fan, I seek messages to find more unstable things the kernel found so I can disable them,.

#Linux #POST #dmesg #kernel

Playing in my dmesg output again.

Since the miniPC has a broken GPU and CPU (APU one die) thanks to Gigabytes puny small APU fan, I seek messages to find more unstable things the kernel found so I can disable them,.

#Linux #POST #dmesg #kernel

When was the last time that you ran

`dmesg|less` on your linux system?

You **NEVER** did?

You dont know what you are missing my POSIX dweller!

Look at the awsome input to your brains!!!

Of course you should first run

`man dmesg` since you should not trust a command which uses sudo from a stranger on the internet

https://www.man7.org/linux/man-pages/man1/dmesg.1.html

<< dmesg - print or control the kernel ring buffer

Yes on debian based machines, for some odd reason you are not allowed to run dmesg anymore as a regular user, so I run

`sudo dmesg|less`

Now you know what dmesg does, run it and learn to the bit, what happens on your linux machine when you cycle through the POST sequence

#POSIX #Linux #dmesg #POST

When was the last time that you ran

`dmesg|less` on your linux system?

You **NEVER** did?

You dont know what you are missing my POSIX dweller!

Look at the awsome input to your brains!!!

Of course you should first run

`man dmesg` since you should not trust a command which uses sudo from a stranger on the internet

https://www.man7.org/linux/man-pages/man1/dmesg.1.html

<< dmesg - print or control the kernel ring buffer

Yes on debian based machines, for some odd reason you are not allowed to run dmesg anymore as a regular user, so I run

`sudo dmesg|less`

Now you know what dmesg does, run it and learn to the bit, what happens on your linux machine when you cycle through the POST sequence

#POSIX #Linux #dmesg #POST