Hi,

Any ideas, I had Suse 8.2 running happily on my shuttle sv25 P3 box for over a year and occasionally when shutting down it would stop at the sound driver. This was not to bad because I could press the reset button and then turn it off as it started to boot.
Any way new PC, Asus terminator K7 DDR with XP 2600+ (I think) and suse 9.1. Been working fine for a couple of weeks (apart from the sound (have to set master volume with the headphone level!?) anyway it also stopped on shutdown at the sound driver.
Problem is the terminator has no reset button, so had to pull the plug out of the back, when the started the next day, it got stuck in the bios and the screen did not come on. Restarted it again, (with the power lead – don’t you just love ATX psus) and it boots straight in to the bios. After resetting the processor speed it seemed to boot fine.
Any ideas what may be causing it to stop at the sound driver…. I used to think it was an oddness of the shuttle, but the same problem on different kernel and processor type makes me wonder.

Any inspirations would be appreciated,

Cheers

daceo

I was looking into the setup in the yast, and I noticed that there was a strange setting to do with AC97 chip set anomalies... the default selling seems to be -1. I set this to 0 and touch wood I have not had any problem since.

I thought I had fixed this one, but it happened again… and I think I have made the link to what is happening. I have a headless server running slack 10 ish and it is set up with NFS and samba. When the suse box has been accessing the server using nfs, when I come to shut it down it stops at the sound driver. I have also found that I can get it to continue by doing a cntrl alt del….. this happened on suse 8.2 and 9.1.

Any ideas?

one of those silly things that I guess happens. I hadn't unmounted the nfs before shutting down...