On 04/25/2015 09:33 PM, don fisher wrote:
Sorry, I thought you gave me more credit than that. My system hang is probably not wicked based.
Sorry. You're not always a clear communicator. After all, this thread you started, this Subject: is about wicked (sic). Now you mention boot hand but you've been going on about networking conflict. Where does it clash?
It usually occurs during boot.
WHAT usually occurs during boot? The problem with wickd?
It may be my graphics system, but I do not know because I receive no information.
Yes you do, you just don't know where to look.
I miss my rs232 port and the boot logs. I may have to get a usb to rs232 adapter.
WTF? When I want to see the boot messages, when there is problems booting, long delays, or a hang., I edit the boot command line. At the grub2 prompt I type 'e' and get the editor for the line I've chose. It may be the normal one or it may be one of the "Advanced Options" such as a "recovery mode". Usually I skip the recovery mode unless I'm concerned with the graphics side of things. Usually I just remove the "splash=silent quiet". I then get a lot of streaming output, the kind of thing that back in the days of Linux 0.9x in a distant century past would, as you mention, require a serial hook-up. "Yes it used to be but we changed all that". hang? Well maybe not. A lot of the time I see a fsck rebuilding my disk from the logs. As mentioned, I use ResiserFS and its very good about logs and recovery, but this can take some time. I don't know about BtrFS. As for ext[234], YMMV. As I've also mentioned, I keep many past kernels and configurations. Its one way of doing debugging. There are many possible command line options for booting. Some have been mentioned in this forum in the past; they are documented both in the system docs - RTFM - as well as on-line - "go google". Try 'man 7 bootparam' for starters. You might be interested in things like 'panic=N' By default the kernel will not reboot after a panic, but this option will cause a kernel reboot after N seconds (if N is greater than zero). You can also set the kernel log level for those messages I mentioned. loglevel= level be paranoid, set that to 0 or 1 !!! I've also found that, since the messages can be confusing when the SMP kernel & systemd is running multiple fscks in parallel to disable multi-threading & SMP. KISS. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org