2010-09-16, 20:22
Sure no probs -- how do I attach a file here?
FYI even if I give you the driver, the problem is that after I got the network working using the above documented method, when I reboot the machine, the xbmc logo comes up for a couple of seconds, but the graphics are low resolution, like the graphics mode has gone wrong, then the "XBMCLive login:" message appears on a text-mode black full screen.
I tried startx, /usr/bin/xbmc etc and it says something about can't find display.
Seems like something has corrupted X server or something... just guessing.
If this method can't be fixed then I thought of a plan B:
- unpack the XBMC live .iso file and then insert the driver into the right path where the installer/network detection code expects to find it, and then re-make the .iso and burn it again to USB stick and try reinstalling. This should be the most pain-free method of solving this issue, but I don't have the necessary knowledge of how to do this, so if anyone does know... please help!
A quick look at the unpacked .iso file shows there are '.udeb' files, which I assume are packed files that the installer uses during installation, so my next homework is to find out about their composition... sigh....
FYI even if I give you the driver, the problem is that after I got the network working using the above documented method, when I reboot the machine, the xbmc logo comes up for a couple of seconds, but the graphics are low resolution, like the graphics mode has gone wrong, then the "XBMCLive login:" message appears on a text-mode black full screen.
I tried startx, /usr/bin/xbmc etc and it says something about can't find display.
Seems like something has corrupted X server or something... just guessing.
If this method can't be fixed then I thought of a plan B:
- unpack the XBMC live .iso file and then insert the driver into the right path where the installer/network detection code expects to find it, and then re-make the .iso and burn it again to USB stick and try reinstalling. This should be the most pain-free method of solving this issue, but I don't have the necessary knowledge of how to do this, so if anyone does know... please help!
A quick look at the unpacked .iso file shows there are '.udeb' files, which I assume are packed files that the installer uses during installation, so my next homework is to find out about their composition... sigh....