Quote:
Originally Posted by schoneschein
I also installed on an SD card and really couldn't figure out how anyone was getting installs to the internal memory to work! I just had a thought about your problem: Did you check that you have free space on the Obuntu root partition? If it was incorrectly sized, that could explain why you ended up with a broken system.
Also, is your wifi working in the stock OS? (did you eliminate the possibility of a hardware problem?)
I guess I should look at the other thread before I comment here, because you've probably checked these things and much more!
One more thought, though: If you're still having trouble, since you're using an SD card, maybe you should try the other Obuntu version on a different card.
|
Thanks - they are all useful suggestions. The wireless does work when running the Onyx OS, so it doesn't look like a hardware problem. I don't think that I've got a broken system as much as an incomplete one (as I dare say was intended). The problem, as far as I can see, is that the wireless firmware won't load. Everything else, with a few exceptions, seems to work. All the partitioning has been on the SD card which now also has got the apt-mirror repository taking up an additional 8GB so there was plenty of space. I have tried different SD cards with no change, though not the earlier version of Obuntu yet. I'll probably try to find another copy of the firmware in case that is where the problem is coming from. As I seemed to be making some headway (although alas not much today), I've kept going with the current version. Trying the earlier version on another SD card is a good suggestion. I might try to do that, since it is unlikely to disturb the existing setup, though it will take a while.
The same errors with the same wireless chipset have occurred elsewhere, it just isn't all that clear from some of those postings just what the solution is. It seems to be some sort of timing issue, which is why I was attempting to blacklist the driver from loading during the boot process. It seems as though one can vary the timeout in the insmod command that calls the ar6000.ko module but I can't find what configuration file is calling it during the boot process.
The error messages and the references to other discussions of them are in the last three posts of this page:
https://www.mobileread.com/forums/sho...217438&page=12
Quote:
Originally Posted by schoneschein
I wish I could remember more clearly what I had to do to get everything working. I did spend a very long time on this, first of all because I have an Artatech model, and had to flash the Booxstor firmware.
|
I've had to use the MFG tool to reflash the device which I presume it does with the Booxtor firmware.
I try to keep as extensive a collection of notes as I possibly can. I certainly know about things taking forever to get working. This has taken months. One has to keep coming back to things and try to figure out just where one had got up to.
I've now found what I think are the header files and they are indeed oddly named.
Code:
apt-cache search headers
returns:
Code:
linux-headers-imx51 - Linux kernel headers for imx51 machines
linux-headers-2.6.31-607-imx51 - Linux kernel headers for version 2.6.31 on I.MX51-based systems
Rather than:
linux-headers-2.6.35.3-power
which couldn't be found.
The chipset is actually i.MX50 which is a dedicated one for eReaders. So not quite i.MX51 but probably close enough. The sources file suggests that i.MX51 was used by Obuntu. Indeed, it seems to be telling me that these headers are installed anyway.
Apologies for the long delays between replies. Alas I've got to fit this in between other things. Keep us informed on how you go with your communications and finding parts (hopefully of acceptable quality).