Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 7 hrs, 23 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 11 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days ago -
n770 youtube video (0)
to General by nmdv - 5 days, 23 hrs ago - more...
|
2017-08-17
, 20:49
|
|
Posts: 334 |
Thanked: 2,004 times |
Joined on Oct 2013
@ Fin
|
#1342
|
If I am correct the serial port is accessed via 3.5mm headphone plug in N950. So there wouldn't be need to tear phone apart(maybe). But somebody needs to comfirm this. 
__________________
necunos.com - Join the movement for freedom of mobile
necunos.com - Join the movement for freedom of mobile
|
|
2017-08-17
, 21:19
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#1343
|
I have journalctl installed, so I think I have the full right to assume it's systemd.
My steps were:
1. Create a partition, setup ubiboot
2. Mount the partition from the ubiboot rescue, follow this guide:
http://blog.lazy-evaluation.net/post...bootstrap.html
3. install the kernel package linux-image-armmp
That's the normal upstream kernel, as provided by Debian.
I guess I have no serial cable...
My steps were:
1. Create a partition, setup ubiboot
2. Mount the partition from the ubiboot rescue, follow this guide:
http://blog.lazy-evaluation.net/post...bootstrap.html
3. install the kernel package linux-image-armmp
That's the normal upstream kernel, as provided by Debian.
I guess I have no serial cable...
|
|
2017-08-17
, 21:57
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1344
|
What I meant; what is the debian rootfs you installed to your mmcblk0p4 partition?
When your kernel boots does it find all it needs on the rootfs?
And you still did not answer; how far does the boot go, do you see anything at all on your device screen after ubiboot hands the execution to the debian kernel?
And another thing; have you checked that the debian kernel handles the CPU L2 cache initialization correctly? (See the section 4. of ubiboot README file...)
When your kernel boots does it find all it needs on the rootfs?
And you still did not answer; how far does the boot go, do you see anything at all on your device screen after ubiboot hands the execution to the debian kernel?
And another thing; have you checked that the debian kernel handles the CPU L2 cache initialization correctly? (See the section 4. of ubiboot README file...)
|
|
2017-08-18
, 16:48
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#1345
|
[QUOTE=juiceme;1532806]What I meant; what is the debian rootfs you installed to your mmcblk0p4 partition?
When your kernel boots does it find all it needs on the rootfs?[/code]
I created an empty ext4 partition and bootstrapped latest Debian Stretch onto it using `debootstrap`.
Here's my kernel config, I don't really know what to look for: https://pastebin.com/1T9DBbbb
Maybe the problem is that I didn't append the device tree part manually?
Last edited by marmistrz; 2017-08-18 at 17:06.
When your kernel boots does it find all it needs on the rootfs?[/code]
I created an empty ext4 partition and bootstrapped latest Debian Stretch onto it using `debootstrap`.
Originally Posted by juiceme
I don't know. I have no journal logs in /var/log, even though I use persistent storage mode in journald.conf
And you still did not answer; how far does the boot go, do you see anything at all on your device screen after ubiboot hands the execution to the debian kernel?
Originally Posted by juiceme
How can I check it?
And another thing; have you checked that the debian kernel handles the CPU L2 cache initialization correctly? (See the section 4. of ubiboot README file...)
Here's my kernel config, I don't really know what to look for: https://pastebin.com/1T9DBbbb
Maybe the problem is that I didn't append the device tree part manually?
__________________
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
Last edited by marmistrz; 2017-08-18 at 17:06.
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
|
2018-03-01
, 16:56
|
|
Posts: 1,196 |
Thanked: 1,413 times |
Joined on Aug 2011
|
#1346
|
I would like to telnet with ubiboot small on my Ubuntu 17.10 i386.
when i run telnet 192.168.2.15 not work.
Unable to connect to remote host...
when i run ifconfig -a i have no usb0 in the list
my n9 is named enp0s29....
Do i need to set up something before run telnet command
when i run telnet 192.168.2.15 not work.
Unable to connect to remote host...
when i run ifconfig -a i have no usb0 in the list
my n9 is named enp0s29....
Do i need to set up something before run telnet command
 |
|
2018-03-01
, 19:15
|
|
Posts: 634 |
Thanked: 3,266 times |
Joined on May 2010
@ Colombia
|
#1347
|
Originally Posted by n950
Try the following:
I would like to telnet with ubiboot small on my Ubuntu 17.10 i386.
when i run telnet 192.168.2.15 not work.
Unable to connect to remote host...
when i run ifconfig -a i have no usb0 in the list
my n9 is named enp0s29....
Do i need to set up something before run telnet command
Code:
ifconfig enp0s29 up 192.168.2.1
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
| The Following 5 Users Say Thank You to wicket For This Useful Post: | ||
|
|
2018-03-02
, 11:13
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1348
|
Originally Posted by wicket
Yes.
That ought to bring up the USB interface on the same subnet as the N9.
0.3.6-tiny is a stripped/limited version that does not have dhcpd enabled.
The tiny version was made specifically for the people who have bad kernel partition so that it can fit in there... It's recommended to use 0.3.7 for everybody else.
| The Following 3 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2018-03-02
, 17:06
|
|
Posts: 634 |
Thanked: 3,266 times |
Joined on May 2010
@ Colombia
|
#1349
|
Originally Posted by juiceme
There are versions 0.3.6 and 0.3.7? What??? Where does one even find these? They are not mentioned in the README, nor wiki page, nor can they be found under http://www.swagman.org/juice/ubiboot/ubiboot-02/. I just took ubiboot-02_0.3.5_301013.tar and flashed zImage_2.6.32.54-ubiboot-02-small_060114 as it seemed to be the latest.
Yes.
0.3.6-tiny is a stripped/limited version that does not have dhcpd enabled.
The tiny version was made specifically for the people who have bad kernel partition so that it can fit in there... It's recommended to use 0.3.7 for everybody else.
If I'm honest, I found the documentation (README and wiki) to be out of date and incomplete. After a lot of pain, I eventually figured it out.
Parts of the README I found confusing:
The corresponding "G_OS<x>_<y>_FILE" is the path to the bootable kernel.
The G_OS<x>_PARTITION and G_OS<x>_NAME identifiers define the partition
where the boot kernels are searched for.
For example, Harmattan kernels are by default located on mmcblk0p2 in the
/boot/ directory, which resolves to "/boot/Harmattan/boot/" in the script.
When you are running Harmattan, this dame directory resolves to /boot/
It's not clear that each rootfs should be copied/unpacked to a dedicated partition unless handled by a preinit script. This really confused me. Combined with the problems mentioned above, I incorrectly thought that maybe G_OS<x>_<y>_FILE was being used to specify the rootfs location as well as the kernel.
I don't want to sound like I'm complaining, I just hope this will help others to avoid the problems I had. Although it would also be nice if you would fix the documentation juiceme.
It might also be nice to have a new ubiboot with a recent kernel and recent kexec tools.
EDIT: One more thing, my experience would have been far less painful if ubiboot had printed an error message to tell me that my kernel image was not found before running kexec. I had no idea why it was failing and thought there was a problem with the kernel I built.
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
Last edited by wicket; 2018-03-02 at 18:38.
| The Following 4 Users Say Thank You to wicket For This Useful Post: | ||
|
|
2018-03-02
, 18:44
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1350
|
Ya @wicket!
These are all valid critique points, I admit that I have always been somewhat lazy to document things!
Indeed I should at some point take time to tidy up things a bit...
The fact is that ubiboot is a bit of work-in-progress-stalled-indefinetely when my attention turned to other things, sadly. I kind of was in the middle of updating some new functionality into it (device charging, wlan set-up, etc...) when I stopped working on it.
Most if not all sources are in my github, except some experimental stuff still in my personal svn repo.
These are all valid critique points, I admit that I have always been somewhat lazy to document things!
Indeed I should at some point take time to tidy up things a bit...
The fact is that ubiboot is a bit of work-in-progress-stalled-indefinetely when my attention turned to other things, sadly. I kind of was in the middle of updating some new functionality into it (device charging, wlan set-up, etc...) when I stopped working on it.
Most if not all sources are in my github, except some experimental stuff still in my personal svn repo.
How's the init system in your kernel; is it expecting to use systemd or sysvinit? As I presume you are taking some arm debian disk image and integrating that with the elinux kernel?
Any other way to access the device requires you to have a daemon running in it, which basically means your userland needs to start.
For debugging init problems this is not the optimal strategy
[OK, yes there are other ways of course, you could build serial-emulation-for-usb in your kernel, or route kernel logging to audio port or modulate the status led with it... however you probably don't want to know about those methods]