[SLE] The continuing saga of freezing YaST
As I mentioned in an earlier post, after I upgraded my HD to SCSI, everything works except for YaST. It freezes up at the first screen, and requires a hardware reboot to recover. Does anyone at SuSE read this list? As this a SuSE-only program, they may be the only people who can help me out. I attempted to run strace and gdb on the binary to see what I could find, but they crash along with YaST. I was able to see the point in strace where execution locks ups if I set strace to output to CRT. And by running strace on a good system, I was able to find all of the files that YaST reads. The only Yast-installed file that I could see that pertained to the HD was /var/lib/YaST/install.conf. I tried various combinations of either deleting it or adding it with parameters for the new drive, but nothing worked. There is an option for Yast that deletes that file and starts anew, but it didn't work. What I may do next is try to compile the source with debugging code and see if I can get gdb to work. Any ideas? Thanks, Rob. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
europax@home.com wrote:
As I mentioned in an earlier post, after I upgraded my HD to SCSI, everything works except for YaST. It freezes up at the first screen, and requires a hardware reboot to recover.
Does anyone at SuSE read this list? As this a SuSE-only program, they may be the only people who can help me out.
I attempted to run strace and gdb on the binary to see what I could find, but they crash along with YaST. I was able to see the point in strace where execution locks ups if I set strace to output to CRT. And by running strace on a good system, I was able to find all of the files that YaST reads. The only Yast-installed file that I could see that pertained to the HD was /var/lib/YaST/install.conf. I tried various combinations of either deleting it or adding it with parameters for the new drive, but nothing worked. There is an option for Yast that deletes that file and starts anew, but it didn't work.
What I may do next is try to compile the source with debugging code and see if I can get gdb to work. Any ideas?
Have you emailed feedback@suse.de or the maintainer of YaST? That should get more response than the list. And if you do figure it out, could you post it to the list or to me personally, since I used to have this problem, and I fear I may have this problem again in the near future... Just a note to everyone - if you spot bugs in the dist. then when you email the list about them, also CC: the message to feedback@suse.de... SuSE can't do anything if they don't know about the bugs ;-) Thanks, Chris -- Apologies to everyone who has been waiting for replies off me over the past few weeks - I've been away from my computer. I'll try to catch up with my email over the coming days, but don't be surprised if you get a reply in a month's time... __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I solved the problem late last night by accident. I found that I still had an alias in modules.conf for the scsi hostadapter. I now have SCSI AIC7xxx driver built into the kernel. When I got rid of that it started working. I don't know why this would affect Yast, except that when I straced a working Yast, I found it loaded all types of system config files. It does a lot more than you would imagine in that short time before the Yast menu pops up! Straces output is about 10 pages long :) Rob. Chris Reeves wrote:
Have you emailed feedback@suse.de or the maintainer of YaST? That should get more response than the list. And if you do figure it out, could you post it to the list or to me personally, since I used to have this problem, and I fear I may have this problem again in the near future...
Just a note to everyone - if you spot bugs in the dist. then when you email the list about them, also CC: the message to feedback@suse.de... SuSE can't do anything if they don't know about the bugs ;-)
Thanks, Chris -- Apologies to everyone who has been waiting for replies off me over the past few weeks - I've been away from my computer. I'll try to catch up with my email over the coming days, but don't be surprised if you get a reply in a month's time... __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, On Sun, 16 Apr 2000, Chris Reeves wrote:
Just a note to everyone - if you spot bugs in the dist. then when you email the list about them, also CC: the message to feedback@suse.de... SuSE can't do anything if they don't know about the bugs ;-)
Exactly :) But please do not forget to remove "feedback@suse.de" when you answer on such a report on the list. Since we use a trouble ticket system for incoming feedback, the resulting thread won't be of any help for the feedback guys since each post will generate a new trouble ticket. Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer 90443 Nuernberg, Germany -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
chris.reeves＠iname.com -
europax＠home.com -
grimmer＠suse.de