IsaacDFP | # 241 | 2011-01-11, 11:54 | Report

What does this mean then...?

WARNING: Installing the customized osso-wlan will break seamless upgrades to new PR versions.
Most likely you will have to reinstall normal osso-wlan version before you can do OTA upgrades.

Radicalz38 | # 242 | 2011-01-11, 12:00 | Report

You can't upgrade OTA(Over The Air)
in short you can't (apt-get upgrade)

Either you need to reflash a new firmware or reflash a new firmware. You don't have a choice.

All that if........................................... There is PR1.4 coming

Mentalist Traceur | # 243 | 2011-01-11, 15:37 | Report

To be specific, the modification to osso-wlan ITSELF doesn't break update capabilities.

HOWEVER, because of how dpkg/apt-get handle dependencies/versions-of-stuff on the N900, stock-system stuff often gets screwed. So because lxp packaged the osso-wlan modification as a package that dpkg interprets as another version of the stock osso-wlan package, it throws a hissy-fit about dependencies when you try to do some of the updating/uninstalling/blah processes.

There's the tech savvy solution of editing relevant 'control' files - hawaii suggested that, I believe - I honestly am not knowledgeable enough to do that myself - but you can also just reinstall the normal osso-wlan when you need to, and reinstall the modded version after you're done with whatever dpkg complains about. Though that would wear down your flash chip, ever so slightly more.

hawaii | # 244 | 2011-01-11, 18:23 | Report

You can modify the debian/control file from within the package, adjust the Depends versioning and re-package and install.

I do it on device using a small shell script that does the dirty work of unpackaging/tar'ing, prompts for a version change and builds $filename_modified.deb ready for installation.

I suggest you do it on a workstation, however.

Mentalist Traceur | # 245 | 2011-01-11, 21:00 | Report

Any chance of you sharing that script? I can figure out how to do it manually eventually, but if nothing else it would make both learning and doing easier.

I got to the point where I can unpack the control.tar.gz, and I know how to use vi or anything else to edit the control file specifically. That's pretty obvious, naturally. However, am I supposed to be editing the osso-wlan control file? Or is this a procedure I'm supposed to do on the future control files of packages that conflict with the updated osso-wlan?

I don't see anything in the depends file that would break future compatibility in the osso-wlan .deb included with lxp's driver/kernel, so I'm guessing you meant editing the future files that object to this package? If so, is there a way to just edit the files in the osso-wlan fix .deb? Could it be as simple as changing the package name or version in the control file, and/or renaming the .deb?

(Looking over this thead for your previous post on the subject now to see if answers this or gives any hints from which I can figure this out.)

- Edit -

NVM on the what-to-edit part. Your last post said that.

So, can I just re-tar, re-gzip, and then re-ar the files back together now that I've edited the control file?

---

Last edited by Mentalist Traceur; 2011-01-11 at 21:13. Reason: Figured out part of it. (remove "-1" from Version line)

hawaii | # 246 | 2011-01-11, 21:32 | Report

Use "dpkg-deb -x" to extract the contents to a temporary working directory.
Use "dpkg-deb --control" to yank out the debian/control files to the temp dir.
Modify your control file with your favourite editor and then repackage the entire directory using "dpkg -b".

jstokes | # 247 | 2011-01-11, 21:44 | Report

http://ubuntuforums.org/showthread.php?t=636724 works; you need to remove the stat stuff so it builds each time. I would also recommend to make it use /var/tmp, instead. Naturally it needs to be run as root to ensure files' permissions stay intact and, of course, replace vi with run-standalone.sh leafpad if the latter's more your cup of tea. You may also consider adding a line to rm -rf the temp folder to save space (although temp-reaper will do so anyway on the next boot)

Edit: Make it use /bin/sh, too

---

Last edited by jstokes; 2011-01-11 at 22:03.

Mentalist Traceur | # 248 | 2011-01-11, 22:01 | Report

Thank you both. (I already did it manually using tar, gzip, and ar, came back online to edit my above post, and saw these. But thank you. Your approaches are ridiculously better and faster.)

TiagoTiago | # 249 | 2011-01-11, 22:20 | Report

Could someone make a vidtut on installing this, starting with the risks and concerns someone that isn't up to speed should have in mind, then with all the preparations, next installing it, and lastly how to get back to power or stock kernel if desired, please?

Haider | # 250 | 2011-01-11, 22:35 | Report

Someone help me out. I am 17 and I dont have a credit card or any other card. How can I get these drivers?