Quote:
Originally Posted by schoneschein
Hi Wong,
It's nice to see that someone else is still working with one of these!
Thanks for the suggestion. I did a search for the part number of the screen and found some for around $100. It seems to be fairly easy to get. And it looks like the digitizer is actually behind the screen and is not adhered, so it shouldn't be hard to switch it.
The only reason I haven't yet ordered a screen is that I've been hoping someone would tell me it's probably the cable, since I know that these were failure prone.
|
Yes - I wasn't aware that the cables were prone to failure. Obviously it would help to know which part failed and your experiments seem to point to the cable.
I was thinking more of ebay. I did see a M92 for parts in the States a few months ago but I missed it as I was too busy at the time. Given that the M96 is supposed to be just an upgrade of the M92 they also probably share alot of the same parts. They seem to look exactly the same and if I remember correctly people were disappointed that it had the same screen. That might be another route to getting compatible parts, although I'm not sure how you'd track them down. It would be great to have a list of part numbers like in the IBM service manuals.
Quote:
Originally Posted by schoneschein
As for Obuntu:
The newest image wouldn't even boot for me. You got a lot further than I did. I believe that I did follow the same procedure that's described for the newest build.
|
Thanks for this. It could still come in handy. I've only had any success with the external install onto the SD card rather than the internal memory, which is more of a manual install. So I've oddly never had any success with the more automatic procedure.
Quote:
Originally Posted by schoneschein
It sounds like you may have a broken distribution. Most things work out of the box. However, if you want to try fixing it, you can download on a computer the .deb packages you need, copy to your sdcard, and install them using dpkg. (You shouldn't have to compile anything)
|
Yes - you are right about this. I was too pessimistic about this possibility from what I'd read earlier. I've now downloaded a large part of the repository with apt-mirror and will be attempting to install what I need from the SD card this way. The problem has always been finding a way to get access to the repository as Obuntu is rather incomplete out the box.
I've just attempted to install the kernel headers and it couldn't find them so I'll have to look into that further (perhaps a naming issue) but I was just able to install emacs so I must have found the right repository. So it does look like I've finally found a way to bring the repository to Obuntu in place of connecting Obuntu to it.
Quote:
Originally Posted by schoneschein
I assume that you checked dmesg to see if the wireless adapter is recognized, and, if so, ifconfig?
|
Yes - the errors turn up in dmesg - the problem seems to be with the loading the wireless firmware by the driver (module). I've discussed it at some length in the Obuntu images thread. I couldn't even blacklist the module. I eventually managed to brute force blacklist it by renaming it. But even then the firmware still failed to load (same errors) when I loaded the module manually, so I'm now mainly just trying to go around it. Certainly, USB wireless adapters are recognized on the USB bus but I've had the problem of not being able to install the drivers without a wireless or any other connection.
Thanks for your help!