dmesg > hm.txt Produces An Empty File

More
6 years 11 months ago #149650 by BigBird
After running dmesg to look for hostmot2's pin assignments, I find that the file is empty. In other words if, after clearing the log file with "dmesg -c", I start LinuxCNC (which runs fine - no issues there) and then type "dmesg > hm.txt", hm.txt is empty.

If I don't clear dmesg first....I just end up seeing all the Linux start up stuff, but nothing from hostmot2. So it's like hostmot2 or whatever is responsible for writing messages to dmesg isn't working.

I'm using:

Linux LinuxCNC 4.9.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux

It worked fine under Wheezy.

Any ideas?

Thanks

Please Log in to join the conversation.

More
6 years 11 months ago #149655 by tommylight
Start Linuxcnc from the terminal, you can see there everything regarding Mesa .
If you want just the pins:
mesaflash --device "card number here" --readhmid

Please Log in to join the conversation.

More
6 years 11 months ago #149659 by BigBird
"Start Linuxcnc from the terminal..." works. Thanks!!!

But the second suggestion needs a correction:

--redhmid

should be:

--readhmid

so the command that worked for me was:

sudo mesaflash --device 5i24 --readhmid

Please Log in to join the conversation.

More
6 years 11 months ago #149660 by PCW
Driver messages are not logged to the kernel log with the userland version of
LinuxCNC (which you are using), instead they are logged to the console
so you can see them by launching LinuxCNC from a terminal, that said,
tommylights suggestion of mesaflash --readhmid is generally a better way if
you want a pinout list

Please Log in to join the conversation.

Time to create page: 0.162 seconds
Powered by Kunena Forum