Re: Building RTAI [SEC=UNCLASSIFIED]
Alec Ari <[email protected]>
| Newsgroups | gmane.linux.real-time.rtai |
|---|---|
| Message-ID | <[email protected]> |
Hello, I've been doing RTAI kernel development for several years now. Are you sure you updated the hal-linux patch to the mainline kernel properly and fixed the conflicts (if any) correctly? Try turning kernel debugging on with earlyprintk, IPIPE debugging, compile kernel with debugging info (do NOT enable "reduce debugging info") and perhaps enable "compile with frame pointers" and "Enable verbose x86 bootup info messages" as well. You can find these options in the kernel hacking section. You can use serial debug (if necessary) and save all output to a file and let me look it over. If it's too much work, the motherboard doesn't have a serial out and as USB debug dongles can be quite expensive, snapping a video or taking some pictures will work too so I can see what's going on and whee it' s hanging. CentOS is a great platform for RTAI, however because CentOS 7 uses SystemD, I'd pick the latest version of 6. SystemD (because I'm not an expert on it, nor ever will I, by choice) makes debugging kernel issues much more difficult and many other issues such as those related to X (having to use journalctl for example instead of just raw output to Xorg.0.log) but if you're able to work with 7, try and gather as much debug info, backtraces, kernel messages (dmesg) and I'll be happy to look it over. If you can gather any logs in regards to X.org as well, that'd also be helpful as I am not exactly sure where this blinking cursor is. I have a long history of X.org development as well (Mesa and DRM.) A blinking cursor without me seeing it doesn't tell me at which stage the system is hung. You can get blinking cursors on boot at kernel decompression, GRUB/bootloader problems, a kernel bug / oops that isn't getting printed, filesystem mounting/init (systemd/early udev/initrd) or when X is star ting and can't find a display. Disabling CONFIG_FB and any DRM/AGP options in the kernel might help debugging as well, as sometimes KMS (kernel modesetting) and framebuffer drivers can interfere. Distro splash screens (having quiet on the kernel command line) and boot logos (tux penguin etc) can also become problematic. After enabling all the debugging features, post your kernel config and I'll look that over too! Thank you! Alec Ari ONE Labs _______________________________________________ Rtai mailing list [email protected] https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai