Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 17 hrs, 7 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 5 hrs ago - more...
| The Following 4 Users Say Thank You to reinob For This Useful Post: | ||
|
2012-09-06
, 21:03
|
|
Posts: 22 |
Thanked: 28 times |
Joined on Aug 2012
|
#502
|
Originally Posted by reinob
If the USB port actually worked, I wouldn't have to go through all of this just to reflash the kernel
Meaning whatever you break on the rootfs (as well as the kernel partition) you can always flash again, that is, assuming that your USB port is working OK
.I just tried using flasher built into the n900 image by adding it to a custom boot script (keymap doesn't let me type the dash symbol). I'm getting "Unable to enumerate USB ports" or something of that sort. I'm probably missing modules of some kind (phonet? As that seems to be what makes flasher on PCs work). Will try to modprobe that and see...
| The Following User Says Thank You to aeon_light For This Useful Post: | ||
|
|
2012-09-07
, 00:10
|
|
Posts: 20 |
Thanked: 8 times |
Joined on Apr 2012
|
#503
|
Originally Posted by neomarky
Don't use application manager. Install it from the commandline using dpkg.
help..!
i cant install pali's uboot.. it said "unable to install uboot tools incompatible application package.."
am i missing something..? Tia..
| The Following User Says Thank You to mongrol For This Useful Post: | ||
|
|
2012-09-07
, 13:18
|
|
Posts: 20 |
Thanked: 5 times |
Joined on Sep 2012
|
#504
|
Originally Posted by mongrol
you're right i did use HAM.. it's working now.. thank you for your help..
Don't use application manager. Install it from the commandline using dpkg.
|
|
2012-09-07
, 13:41
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#505
|
Originally Posted by aeon_light
AFAIK the way to locally flash a kernel is
If the USB port actually worked, I wouldn't have to go through all of this just to reflash the kernel
I just tried using flasher built into the n900 image by adding it to a custom boot script (keymap doesn't let me type the dash symbol). I'm getting "Unable to enumerate USB ports" or something of that sort. I'm probably missing modules of some kind (phonet? As that seems to be what makes flasher on PCs work). Will try to modprobe that and see...
Code:
softupd --local & flasher -k image --local -f
[ OR, have a look at the postint script for kernel-flasher or kernel-power-flasher. Can't do that at the moment (work PC) ]
Good luck!
| The Following 4 Users Say Thank You to reinob For This Useful Post: | ||
|
|
2012-09-07
, 22:13
|
|
Posts: 22 |
Thanked: 28 times |
Joined on Aug 2012
|
#507
|
Originally Posted by reinob
I got "could not connect to 127.0.0.1" before the execution of flasher when using softupd - after which flasher came up with the same error. Kernel-power-flasher's postinit uses fiasco-image-update in sbin, which might work better, but I'm actually a bit hesitant to flash the kernel directly from the script without enabling R&D mode and turning off the watchdogs first, since this could result in the N900 getting shut down by the watchdog in the middle of a flash, which would leave me with no way to back out without fixing the USB port.
AFAIK the way to locally flash a kernel is
(see http://talk.maemo.org/showpost.php?p=922006&postcount=4)Code:softupd --local & flasher -k image --local -f
[ OR, have a look at the postint script for kernel-flasher or kernel-power-flasher. Can't do that at the moment (work PC) ]
Good luck!
Edit 1: fiasco-image-update is apparently just a script running the commands from before. Oh well. I'm probably still just missing some module that it expects to be loaded... Well, that or a script that's supposed to be run after preinit.
Edit 2: Can I flash a kernel locally from a chroot? (Say, I started RescueOS, extracted a rootfs backup to what would be my /home directory on the N900, mount all necessary dev, sys, and tmpfs stuff and then chroot and flash.)
Last edited by aeon_light; 2012-09-08 at 04:09.
|
|
2012-09-08
, 19:51
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#508
|
Originally Posted by reinob
You need also loopback device to flash locally.
AFAIK the way to locally flash a kernel is
(see http://talk.maemo.org/showpost.php?p=922006&postcount=4)Code:softupd --local & flasher -k image --local -f
[ OR, have a look at the postint script for kernel-flasher or kernel-power-flasher. Can't do that at the moment (work PC) ]
Good luck!
Correct script is shown here : http://talk.maemo.org/showpost.php?p...postcount=1102
| The Following 3 Users Say Thank You to Fabry For This Useful Post: | ||
|
|
2012-09-11
, 19:41
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#509
|
Here is bootmenu item file for rescue os:
EDIT:
Above file was edited. Store rescue os files to /boot and run:
$ u-boot-update-bootmenu
Last edited by pali; 2012-09-11 at 20:11.
Code:
ITEM_NAME="RescueOS" ITEM_KERNEL="2.6.37" ITEM_INITRD="rescueOS-initrd-0.5.3.img" ITEM_CMDLINE="rootdelay root=/dev/ram0" ITEM_OMAPATAG="1"
Above file was edited. Store rescue os files to /boot and run:
$ u-boot-update-bootmenu
Last edited by pali; 2012-09-11 at 20:11.
| The Following 6 Users Say Thank You to pali For This Useful Post: | ||
|
|
2012-09-11
, 21:01
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#510
|
Pali,
Just to be sure: I can remove the images from /boot once images are generated in /home/user/MyDocs/bootmenu.img.d after the u-boot-update-bootmenu command? Especially the rescueOS image eats too much from my rootfs....
Just to be sure: I can remove the images from /boot once images are generated in /home/user/MyDocs/bootmenu.img.d after the u-boot-update-bootmenu command? Especially the rescueOS image eats too much from my rootfs....
Plus, *we* are missing something from you, namely the exact (error) output when you run dpkg to install u-boot.