![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Workaround for faulty motherboard
Jun. 27th, 2006 08:15 amGet your very own Plush tachikoma here
In other news, my computer is now working in a satisfactory manner! A while ago it had developed an error caused by something generating a bad interrupt request.![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
rialian and I looked at it and tried a few things, but it still generated the same error. The only solution we found was to use a very old Debian kernel which didn't even have the correct drivers for my printer (that was why I thought my printer had died - it hadn't, but the old Debian kernel didn't have the right drivers for it. Eventually tlttlotd looked at it, and ended up building a new kernel for it which was tailored especially to my machine. It was late, though, so it hadn't been tested by the time he had to leave (thank you very much tlttlotd for all the time and effort.) After WtT, foxgrrl stayed with us for a while. While she was with us, she not only gave us a wonderful collection of photographs, but she also donated some time to install the new kernel. After the installation was complete, she realized that the interrupt error was still there - it was a hardware problem and not a kernel problem as we had expected. She went through and disabled the peripherals one by one - the error was still there. Finally she coded some kind of workaround which I know not of for it originates within the Realms of Higher Coding, accessible only by few (Thank you foxgrrl for all the time and effort you donated toward getting my macine running - I hope your stay was enjoyable!)
So this week came the real test of how the computer worked - there were two problems remaining - getting the printer working again and getting the DVD drives both running. I tweaked things a little and got the printer running. I still don't know how I did that. I decided to use the 950C again and give the new one torialian, because I know I have the exact drivers for the 950C. When I first connected it, reloaded the driver, and sent a test page to print, it began to print a job I'd sent prior to WtT. Never mind that I'd shut down the computer, booted up with a different kernel, and used a different printer prior to WtT. Never mind that there was NOTHING in the print queue. It still wanted to print that job. Finally I guess it got tired of printing that same job multiple times, because it spontaneously fixed itself. So I take credit for fixing the printer part.
Last night the DVD drives were still acting up, sorialian took a look at them. After a short while of tweaking things and making sure they were initialized properly, they both worked!
So now the interrupt error is officially workarounded. Maybe it would have been easier just to get a new motherboard rather than take up a team of Linux doctors' valuable time (I have a feeling that was a one-time privilege)... But it's working well now. Thanks everyone.
In other news, my computer is now working in a satisfactory manner! A while ago it had developed an error caused by something generating a bad interrupt request.
rialian and I looked at it and tried a few things, but it still generated the same error. The only solution we found was to use a very old Debian kernel which didn't even have the correct drivers for my printer (that was why I thought my printer had died - it hadn't, but the old Debian kernel didn't have the right drivers for it. Eventually tlttlotd looked at it, and ended up building a new kernel for it which was tailored especially to my machine. It was late, though, so it hadn't been tested by the time he had to leave (thank you very much tlttlotd for all the time and effort.) After WtT, foxgrrl stayed with us for a while. While she was with us, she not only gave us a wonderful collection of photographs, but she also donated some time to install the new kernel. After the installation was complete, she realized that the interrupt error was still there - it was a hardware problem and not a kernel problem as we had expected. She went through and disabled the peripherals one by one - the error was still there. Finally she coded some kind of workaround which I know not of for it originates within the Realms of Higher Coding, accessible only by few (Thank you foxgrrl for all the time and effort you donated toward getting my macine running - I hope your stay was enjoyable!)So this week came the real test of how the computer worked - there were two problems remaining - getting the printer working again and getting the DVD drives both running. I tweaked things a little and got the printer running. I still don't know how I did that. I decided to use the 950C again and give the new one to
rialian, because I know I have the exact drivers for the 950C. When I first connected it, reloaded the driver, and sent a test page to print, it began to print a job I'd sent prior to WtT. Never mind that I'd shut down the computer, booted up with a different kernel, and used a different printer prior to WtT. Never mind that there was NOTHING in the print queue. It still wanted to print that job. Finally I guess it got tired of printing that same job multiple times, because it spontaneously fixed itself. So I take credit for fixing the printer part.Last night the DVD drives were still acting up, so
rialian took a look at them. After a short while of tweaking things and making sure they were initialized properly, they both worked!So now the interrupt error is officially workarounded. Maybe it would have been easier just to get a new motherboard rather than take up a team of Linux doctors' valuable time (I have a feeling that was a one-time privilege)... But it's working well now. Thanks everyone.
