You are not logged in.
Pages: 1
I bought a Shimian 27" 2560x1440 display - an awesome monitor for under $300 shipped. Unfortunately, the proprietary Nvidia drivers choke on the EDID. I guess this is the future, huge, hi res, unbelievably awesome monitor for the cost of eating out 3 times, but the monitor won't work because of a driver issue even though the video card is happy. Anyhow, the Nouveau drivers work, but they flood the invalid portion of the EDID to dmesg. dmesg now gives me page after page of binary data - which doesn't include the usual stuff which I need to troubleshoot other issues.
Is there a way to increase the size of what dmesg holds? Is this logged to the file system somewhere? Is there a way to make Nouveau less verbose? Any other ideas?
I realize this could belong in a Nouveau forum, but I am more interested in the dmesg issues deal with the Nouveau problem than fixing the problem itself. If I fix the Nouveau issue, this could just happen again with another piece of hardware.
Offline
check man dmesg and dmesg --help .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ok, so there is an easy way to increase the size, but nothing on the man or --help applies to my other issues.
Offline
Is this logged to the file system somewhere?
/var/log/dmesg.log
(i think it is emptied at boot)
Is there a way to make Nouveau less verbose?
check the -n , --console-level level parameter for dmesg .
depending on which level those binary data messages from nouveau are, you might be able to block them from being logged.
Last edited by Lone_Wolf (2012-06-16 00:41:13)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1