EU: We gonna switch from Microsoft to Linux.

Linux: hold my beer...

#eu #microsoft #switch #linux #bug #dmesg #kernel #bug #crash #driver #buggy #fault #faulty #failure #flimsy #unstable #prototype #mockup #potemkinvillage #realitycheck #ux #brittle #fragile #unpredictable #unreliable

Hey People,

When your #OpenBSD upgrades to 7.9 are done, don’t forget to upload the #dmesg to https://dmesgd.nycbug.org/dmesgd?do=index

It helps idiots like me select supported hardware from time to time 😬 Thank you.

Also make sure the devs get to know what works or not: https://www.openbsd.org/faq/faq4.html#SendDmesg

#79HYPE

* 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

4. to test bad blocks on hard disk on Linux, sudo pv -nb /dev/sda > null or replace /dev/sda with the device identifier of your hard disk.

The errors will print in dmesg (comfortable viewing with command dmesg -TL=always|less -R).

pv may need to be installed as a separate package usually called pv.

It doesn't have a menu entry Menu->System->Hard Disks->"Check bad sectors on your hard disk".

It doesn't even have a menu entry Menu->System->Hard Disks->"Display instructions how to check bad sectors on your hard disk from command line", which I assume would be much easier to implement than the actual menu function, and almost as useful for me.

User experience (UX).

#sudo #linux #dmesg #badblocks #harddisk #hdd #devnull #root #ux #userexperience

Tag der Arbeit.

Das sieht mir sehr nach viel Arbeit aus!

Oder nach e-Müll?

#FotoVorschlag #linux #linuxmint #lenovo #fehlermeldungen #dmesg #errormessages

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

Что делать, если после очередного обновления 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

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