Humpelst1lzchen has quit [Ping timeout: 245 seconds]
Humpelstilzchen has joined #neo900
lobito has joined #neo900
lobito1 has quit [Quit: Leaving.]
ecloud is now known as ecloud_wfh
<freemangordon>
DocScrutinizer05: ok, going to try to boot it
_whitelogger has quit [Ping timeout: 272 seconds]
_whitelogger has joined #neo900
Pali has joined #neo900
mvaenskae has quit [Ping timeout: 250 seconds]
DocScrutinizer05 has quit [Remote host closed the connection]
DocScrutinizer05 has joined #neo900
DocScrutinizer05 has quit [Remote host closed the connection]
<Pali>
DocScrutinizer05: Hi, IIRC in some RFC or BCP is written that only text/plain format of emails should be implemented by all clients... Do you know it? where it could be? I'm trying to find out if really html only emails violates some standards... because I think yes!
<freemangordon>
oh, yeah, I forgot you got those mails too
<freemangordon>
:)
nicksydney has quit [Remote host closed the connection]
lobito has quit [Quit: Leaving.]
mvaenskae has joined #neo900
<drathir>
its happen nokia buy alcatel...
kolp has joined #neo900
sparetire has quit [Quit: sparetire]
lobito has joined #neo900
SylvieLorxu has joined #neo900
mvaenskae has quit [Ping timeout: 256 seconds]
che1 has joined #neo900
freemangordon_ has joined #neo900
che1 has quit [Ping timeout: 264 seconds]
che11 has joined #neo900
DocScrutinizer05 has joined #neo900
mvaenskae has joined #neo900
che11 has quit [Ping timeout: 245 seconds]
mvaenskae has quit [Quit: Lost terminal]
<DocScrutinizer51>
Pali: sorry was offline, no idea why. I don't know of any such RFC re html email
<DocScrutinizer51>
pleae see my mail signature
<bencoh>
Pali: you might be referring to rfc822, but html didnt exist back then :)
mvaenskae has joined #neo900
mvaenskae has quit [Ping timeout: 248 seconds]
mvaenskae has joined #neo900
jusa_ has quit [Ping timeout: 244 seconds]
jusa_ has joined #neo900
mvaenskae has quit [Ping timeout: 244 seconds]
<freemangordon_>
DocScrutinizer05: did you see my mail where I read and write to onenand successfuly?
<DocScrutinizer05>
sure
<DocScrutinizer05>
did you see my mail I sent 5 min ago?
<freemangordon_>
do you want me to perform more testing?
<freemangordon_>
yes
<freemangordon_>
but that's what Nik did :)
<freemangordon_>
I could try to write u-boot to onenand
<freemangordon_>
to see if it will boot it
<DocScrutinizer05>
freemangordon_: could you for example load a matching xloader to RAM via kermit or whatever and then write the complete xloader to the right addr in NAND?
<DocScrutinizer05>
hey! :-D
<DocScrutinizer05>
beaten me to it
<freemangordon_>
:)
<freemangordon_>
ok, will try to write xloader. later on, when I am back home
<DocScrutinizer05>
:-D
* DocScrutinizer05
just fights with a UPS which is detected by dang linux as HIDraw
<DocScrutinizer05>
however I'm afraid I need to clean out some bogus entry in udev database
<DocScrutinizer05>
0003:0665:5161.000F is a generic USB-serial converter not necessarily a HID device
<DocScrutinizer05>
evidence: this UPS
<DocScrutinizer05>
seems udev tries to configure a HID which fails and results in USB eject event
<DocScrutinizer05>
now if only I knew how systemd fscked up udev db
<kerio>
rofl
<kerio>
when everything is systemd, all the problems are caused by systemd
<DocScrutinizer05>
actually this time it seems systemd-udevd behaves identical to udev ?
jonsger has joined #neo900
mvaenskae has quit [Ping timeout: 246 seconds]
mvaenskae has joined #neo900
<freemangordon>
DocScrutinizer05: could you release the USER button, so I can test if what I've flashed to onenand actually works
<DocScrutinizer05>
the ROMBOOT will fal back to OneNAND after 3 seconds of listening to serial/USB
<freemangordon>
hmm, ok
<freemangordon>
doesn't work then :)
<freemangordon>
lets see if uboot will read back what I wrote afte the reset
<freemangordon>
well, it is there
che11 has joined #neo900
<freemangordon>
maybe my entry point address is wrong
<freemangordon>
well, shouldn't be, BL is supposed to read it from the start of the image
<freemangordon>
DocScrutinizer05: are you sure the current SYSBOOT have onenand boot enabled?
<DocScrutinizer05>
quite, yes
<DocScrutinizer05>
anyway I can remove the paperclip but it's a PITA to re-install it
<freemangordon>
as I am sure there is xloader in flash
<freemangordon>
well...
<freemangordon>
lemme first try something
<freemangordon>
do not remove the clip for now
<DocScrutinizer05>
unpressed USER
<DocScrutinizer05>
sory too late
<freemangordon>
ok :)
<freemangordon>
going to reset
<freemangordon>
ok, no signs of life, you may put the paperclip back, sorry :)
<DocScrutinizer05>
np, I found out it's of conveient strength so the switch is bistable
<DocScrutinizer05>
USER pressed
<freemangordon>
thanks
che11 has quit [Ping timeout: 272 seconds]
arcean has joined #neo900
<DocScrutinizer05>
on a sidenote: after depressing experiences with NUT, I installed ViewPower and iked the UPS via freshly purchased USB<->RS232 adapter ;-) Works fine
<DocScrutinizer05>
s/iked/linked/
che1 has joined #neo900
<dos1>
wow, great progress! \o/
<freemangordon>
hmm, ok, I have xloader flashed in nand, for sure, but it won't boot
<freemangordon>
I guess we'll need CHFLASH section in image
<wpwrak>
looks very good indeed now.
<wpwrak>
(just finished catching up with the mails, while the gas workers are taking a break ...)
<infobot>
At http://en.wikipedia.org/wiki/.cm (URL), Wikipedia explains: "{{Infobox Top level domain |name=.cm |background=#CCF |image= |introduced=1995 |type=Country code top-level domain |status=Active |registry=Camtel |sponsor=Camtel |intendeduse=Entities connected with |actualuse=Takes advantage of misspellings of .com domains, like .co |restrictions=Local presence not required |structure=Registrations are made directly at the second level (there are also ...
<kerio>
my fucking god
<kerio>
infobot: you're useless
* infobot
starts crying and hides from kerio in the darkest corner of the room. :(
<kerio>
aww :c
<kerio>
~botsnack
<infobot>
thanks, kerio
<kerio>
np
<DocScrutinizer05>
.cm is the country code top-level domain (ccTLD) for Cameroon.
<wpwrak>
has a weird whois entry
<kerio>
anyway, i helped him set up some shit
<wpwrak>
"Registrant Name: Camtel | ANTIC l Legacy-Escrow"
<wpwrak>
"Domain Status: inactive"
<kerio>
so i have root
<kerio>
wpwrak: at least you're getting something
* DocScrutinizer05
waves and goes afk for an hour
<kerio>
whois: cm.whois-servers.net: nodename nor servname provided, or not known
<kerio>
anyway, we have a fancy setup with qemu-kvm+libvirt
<kerio>
and by fancy i mean pretty shit
<kerio>
but it works
<kerio>
libvirt is so goddamn awkward
<DocScrutinizer05>
freemangordon: does that 4096/2 apply only for "xloader" - read: the stuff that ROMBOOT loads?
<DocScrutinizer05>
freemangordon: also I think sth is *very* buggy in uBoot
<freemangordon>
DocScrutinizer05: yes, BR only
<freemangordon>
naah, uboot os fine
<DocScrutinizer05>
gooood
<kerio>
also, ipv6 is fucking cheating
<freemangordon>
you just need to feed him the correct data (uboot)
<DocScrutinizer05>
why doesn't it rwad/write chunks < NNNNNNN bytes?
mvaenskae has quit [Ping timeout: 276 seconds]
<DocScrutinizer05>
I mean, only 4096 was a reasonable lower limit for chunk size
<kerio>
DocScrutinizer05: do you want a vm
<DocScrutinizer05>
kerio: tanks, not needed right now
<DocScrutinizer05>
thanks even
<DocScrutinizer05>
you could offer one to devuan
<DocScrutinizer05>
;-)
<kerio>
would they appreciate an ipv6-only thing
<DocScrutinizer05>
they are searching for jenkins slaves
<DocScrutinizer05>
I guess that's irrelevant
<DocScrutinizer05>
build-slave
<DocScrutinizer05>
master needs to know about IP anyway, no matter if v6 or v4
<DocScrutinizer05>
last build took them 3 days
<dos1>
as long as their master talks ipv6 it should be fine afaik
<DocScrutinizer05>
>> FYI and to sync a bit on progress, Nextime is completing a total rebuild of all packages for all target architectures via our CI. it took at least 3 days for that, phew.<<
<kerio>
idk if we can spare that many cpu cycles actually
<DocScrutinizer05>
/join #devuan ping nextime
<kerio>
(also i have to ask the actual server owner for something like this i guess)
rjeffries has joined #neo900
<DocScrutinizer05>
well, CPU is the only thing they're really interested in, storage and BW are modest
<merlin1991>
Hm i should utilize my server for stuff like that, it's super idle
<DocScrutinizer05>
I suggested to maemo aka wikiwide already, also to techstaff head warfare
<DocScrutinizer05>
freemangordon: send the invoice for the wisky to Neo900 UG ;-)
<kerio>
DocScrutinizer05: yeah but the kernel can just ignore those
<kerio>
from the cmdline, even
<kerio>
and so does uboot
<freemangordon>
hmm, doesn't seem to work after power-cycle :(
<DocScrutinizer05>
kerio: it doesn't matter what kernel can ignore when the actual partitioning in NAND doesn't match
<kerio>
go drink your whiskey, deal with this tomorrow
<kerio>
DocScrutinizer05: that was what i was confused about - i thought NAND didn't really have a partition table
<freemangordon>
shit! my ssh session got disconnected, that is why there was nothing :D
<kerio>
ROFL
<DocScrutinizer05>
kerio: exactly, it doesn't
<bencoh>
:D
<DocScrutinizer05>
freemangordon: hehe, good
<kerio>
so what xloader believes doesn't really matter
<dos1>
oh those naugthy ssh sessions!
<kerio>
it's what uboot and then the kernel believe
<bencoh>
freemangordon: looks like your router drank all your whiskey
<DocScrutinizer05>
kerio: please grow a brain! when there's no room on NAND then you can't flash a larger uBoot
<DocScrutinizer05>
I asked for leaving enough room to allow uBoot to grow eventually
<bencoh>
actually ... do we really want combined uboot+kernel ?
<kerio>
oh, in fmg's mind
<kerio>
like
<kerio>
in the minds of the developers
<DocScrutinizer05>
bencoh: prolly not
<kerio>
because nothing in the future ROM will depend on hardcoded values, other than the address of uboot itself
<freemangordon>
yeah, everything works fine, bb
<bencoh>
(anyway, neo900 shouldnt want or care about any of this ;)
<kerio>
yay ^_^
<bencoh>
\o/
<kerio>
bencoh: definetely not
<kerio>
but that's already possible
<DocScrutinizer05>
guys, all I asked for was to leave some gap after uBoot (yet to get done) when flashing a linux rootfs to NAND (yet to be done)
<DocScrutinizer05>
or rather kernel
<kerio>
why kernel
<DocScrutinizer05>
because that's the next thing needed after uBoot
<kerio>
we could be real people
<kerio>
and boot a kernel stored in /boot
<kerio>
in a extfs partition
<kerio>
er
<kerio>
ubi
<DocScrutinizer05>
well, we for sure could do this, I dunno if uBoot can do this
<kerio>
my n900 boots a kernel stored on the emmc
<kerio>
on vfat
<kerio>
but that's probably easier
<DocScrutinizer05>
uBoot only knows vfat afaik
<kerio>
istr that ubifs support wasn't added in because of space issues
<dos1>
ext as well
<kerio>
dos1: can it do ubifs
<kerio>
or jffs2
<DocScrutinizer05>
no
<dos1>
but I don't think it knows mtd based filesystems
<kerio>
uboot can do ubi
<DocScrutinizer05>
that's why there's a mtb "kernel" partition
<DocScrutinizer05>
mtd even
<kerio>
there's a mtd kernel partition because it's the simplest solution
<kerio>
not because it's the best solution
<DocScrutinizer05>
aha
<kerio>
it makes it really awkward to have multiple kernels installed in parallel, for instance
<DocScrutinizer05>
whatever, for my request that's pretty much 100% irrelevant
<kerio>
yeah yeah
<kerio>
"be mindful that uboot could grow"
<DocScrutinizer05>
yeah, for example when it needs to learn ubifs
* kerio
votes for a jffs2 partition
<DocScrutinizer05>
why?
<kerio>
well, maybe even ubifs
<DocScrutinizer05>
jffs2 afaik got 'obsoleted' by ubi
<kerio>
but a separate partition
<bencoh>
yeah, why ?
<DocScrutinizer05>
since we're for sure not going to flash an original FIASCO image to Neo900, we are free to clean up quite a number of quirks in fremantle that never been cleaned up due to backward compatibility reasons. Like e.g. optification
<kerio>
DocScrutinizer05: what about the stuff that relies on the broken partitioning?
<Openbot>
thx bencoh
<DocScrutinizer05>
which is?
<kerio>
or relies on the partitioning in general
<DocScrutinizer05>
which is?
<kerio>
flopswap and similar
<DocScrutinizer05>
meh
<kerio>
uboot-flasher
<kerio>
kernel-power-flasher
<DocScrutinizer05>
flopswap will just work
<DocScrutinizer05>
U mad
<kerio>
somad
* DocScrutinizer05
suggests to kerio to flash WinCE kernel
<bencoh>
qnx!
<DocScrutinizer05>
honestly kernel-power-flasher isn't an *app+, by any metrics
<kerio>
bootmenu is not an app either
<kerio>
it doesn't have an icon
<DocScrutinizer05>
pfff
<kerio>
(the actual solution would be to just include bootmenu in the main distro)
* DocScrutinizer05
heads out using his time in better ways
<kerio>
i win :D
<bencoh>
meh >_<
<kerio>
endurance is important
<DocScrutinizer05>
trolling not, though
<bencoh>
it's not friday
<kerio>
bootmenu is deep in the realm of booting the system
<DocScrutinizer05>
kerio: I'm feeling kick-happy
<kerio>
and that's definetely fptf's realm
<DocScrutinizer05>
sorry, that's nonsense. bootmenu is a userland app
<kerio>
kick me if you want, but keeping /sbin/preinit as is just to keep the current bootmenu setup is stupid
<kerio>
hell no
<kerio>
it runs BEFORE INIT
<DocScrutinizer05>
so what?
<kerio>
it's akin to running an initrd
<kerio>
that shit's not userland by any means
<DocScrutinizer05>
again, you're free to fork maemo and run your own distro
<DocScrutinizer05>
or go pester CSSU guys about that preinit stuff
<DocScrutinizer05>
FPTF is not about fixing maemo
<Openbot>
things like bootmenu should be inbuilt
<DocScrutinizer05>
Openbot: same applies to you
<Openbot>
ooo what ??
<DocScrutinizer05>
fix it in maemo and maybe FPTF will adopt the patches
<Openbot>
ah that
<DocScrutinizer05>
goal of FPTF maemo is to stay as close to stock maemo as possible, NOT to fix stuff that didn't get fixed in stock for one reason or another
justbrowsing has joined #neo900
<DocScrutinizer05>
such approach would be pretty poettering
<DocScrutinizer05>
I wonder how good they are with those internal mechano-electrical things like e.g. the GND lever springs etc
<DocScrutinizer05>
yeah, looks nice
<dos1>
anyway, it's good that I got two whites
<dos1>
already managed to break the spring in camera door in one of them :P
<DocScrutinizer05>
honestly I'm very happy when we finally sourced NNN refurbished original N900 incl antennas and magnets and buttons and springs and slider mech and LCD and digitizer and...
<dos1>
btw. the black one feels crappy in touch
<DocScrutinizer05>
:-(
<dos1>
white one otoh feels pretty good
<dos1>
black one however has white stripe, so camera door works
<DocScrutinizer05>
do they have magnets?
<dos1>
(however, I've broken it as well to put it onto white one, so it would have black window around white body, but failed :D)
<dos1>
I'm checking if the backcover triggers µsd (u)mount right now
<DocScrutinizer05>
for the black/white stripe you better use simple sticky tape or felt pen
<dos1>
I just have to find some sd card in mess on my desk
<dos1>
black marker wasn't enough
<DocScrutinizer05>
why not watch the sys/ node?
<DocScrutinizer05>
(black marker) prolly not black in IR
<dos1>
if you can quickly point me to the correct sys node, then why not
<DocScrutinizer05>
mompls
<DocScrutinizer05>
sorry can't find it in /sys/devices/platform/gpio-switch
<DocScrutinizer05>
it's prolly under mmc somewhere
<dos1>
well, already found a card
<dos1>
black one works, white one doesn't
<dos1>
where is that magnet placed?
norly has quit [Quit: Leaving.]
<DocScrutinizer05>
in the middle bottom of the U shaped groove where the stand rests
<DocScrutinizer05>
only thing I can provide for now is Apr 15 22:53:50 IroN900 kernel: [50955.659118] mmc0: cover is open, card is now inaccessible
<DocScrutinizer05>
well, I don't think I know anything more that's worth looking at, right now
<DocScrutinizer05>
IR window maybe
<DocScrutinizer05>
might easily be fake or non-existent
<DocScrutinizer05>
dos1: ^^^
<dos1>
hah, good call
<dos1>
seems black
<DocScrutinizer05>
they all do ;-)
<DocScrutinizer05>
though you can guess they might be transparent to IR when checking against a bright light source
<dos1>
seems totally black while shining a light through it, while original one it a bit redish :P
Pali has quit [Remote host closed the connection]
<DocScrutinizer05>
yes, exactly
<DocScrutinizer05>
so odds are it's a fake like the antennas
<dos1>
so my "seems black" meant "seems it's just a black piece of plastic"
<DocScrutinizer05>
you could test by covering the IR LED of a consomer remote control with the window
jonsger has quit [Quit: jonsger]
<DocScrutinizer05>
afk, bbl
che1 has quit [Ping timeout: 276 seconds]
jake42 has quit [Ping timeout: 246 seconds]
<XDS2010>
DocScrutinizer05: i don't know if i am going to be able to go back to a resistive screen at this point. its been so long since i've used my n900. i've gotten so used to my new android devices. this project seems to be taking so long. not that i mind that its just by the time devices actually start to ship the technology would have changed so drastically it
<XDS2010>
might not even work with current towers a year after launch and then there are probably other unforeseen issues that may arise. im also not trying to criticize the projects handling but it makes me wonder if we are taking enough risks
<XDS2010>
At the very least i hope you can understand how i'm feeling.
<XDS2010>
Also, I don't mind using legacy hardware. On the contrary i encourage it. But i want everyone to be on the same page too.
jake42 has joined #neo900
<merlin1991>
XDS2010: I don't think 3g is going out of service any time soon
<dos1>
"might not even work with current towers a year after launch" uhm? that would apply to any phone launched year ago as well then
<DocScrutinizer05>
what's wrong with LTE?
<DocScrutinizer05>
it's so cutting edge ven modem manufs as well as jolla have not completely supported it *yet*
<XDS2010>
They are already starting to decommission CDMA in some places and LTE won't be here forever soon it will be gone too just like AMPS.
<DocScrutinizer05>
aha
<XDS2010>
I've already heard of talks on LTE-A
<DocScrutinizer05>
afk, bbl
<XDS2010>
merlin1991: they have already begun decommissioning it in some parts of canada
<XDS2010>
the US and other countries will follow soon
<dos1>
as I said, there's no difference between buying neo900 or any recent mainstream phone then
<merlin1991>
totally the reason why even csd still works here ...
<XDS2010>
dos1: not saying don't buy a neo900 i'm saying are we looking at all the angles
jake42 has quit [Ping timeout: 250 seconds]
<dos1>
well, where I live even my old Nokia 3310 still works well ;)
<XDS2010>
lol one of the best phones ever
<DocScrutinizer05>
there simply is no newer technology than LTE
<XDS2010>
LTE-A is used in some parts of the northeast
<DocScrutinizer05>
worrying about lifetime of Long Term Evolition right now seems a tad paradox
<XDS2010>
im not worried. im being proactive
<DocScrutinizer05>
>>that its just by the time devices actually start to ship the technology would have changed so drastically it might not even work with current towers a year after launch << sounds much like useless worrying
<DocScrutinizer05>
anyway there *is no newer* RAT available
<DocScrutinizer05>
maybe faster LTE modems, yes
<XDS2010>
dos1: i miss the nokia 82xx series :P
<DocScrutinizer05>
ours can only go half as fast as the fastest currently available ones. That doesn't mean it won't work in a year. It will work with basically all networks worldwide even in 5 years
<DocScrutinizer05>
probably even in 10 years
<XDS2010>
would it be possible to put a sat RAT on the board ?
<DocScrutinizer05>
not really
<XDS2010>
even with a protruding antenna port ?
<DocScrutinizer05>
we checked our options
xes has quit [Quit: leaving]
<DocScrutinizer05>
well, with a protruding antenna it might be theoretically possible, but then we're not talking about a Neo900 anymore
<DocScrutinizer05>
also no modem modules available for any SAT RAT
<XDS2010>
if you look at the terrastar GENUS the phone is actually very small considering its specs
<DocScrutinizer05>
none I know of at least
xes has joined #neo900
rjeffries has joined #neo900
jake42 has joined #neo900
<DocScrutinizer05>
also sat phones are of very limited practical use regarding the common usecase. They fail indoors for obvious reasons
<DocScrutinizer05>
just like GPS, only easier
<XDS2010>
Not true anymore. With QZ orbiting indoor calls on a clear day work ok
<DocScrutinizer05>
anyway I'm definitely afk now
<XDS2010>
l8
<dos1>
hah, white housing with black cover also looks cool, if not cooler
<dos1>
but it's probably easier to fix backcover than that IR window to have 100% funcional device
mvaenska1 has joined #neo900
xes_ has joined #neo900
wpwrak has quit [Disconnected by services]
wpwrak_ has joined #neo900
wpwrak_ is now known as wpwrak
xes has quit [Ping timeout: 250 seconds]
demure_ has joined #neo900
demure has quit [Ping timeout: 248 seconds]
mvaenskae has quit [Ping timeout: 248 seconds]
xes_ has quit [Quit: leaving]
xes has joined #neo900
<DocScrutinizer05>
well, i'd test it. Maybe it's _not_ a fake
<DocScrutinizer05>
pointing a CIR exactly on the outside of the window and looking to the inside with a N900 main camera will tell quite clearly if it's fake or IR-transparent
<DocScrutinizer05>
dos1: ^^^
<DocScrutinizer05>
the IR is seen as blue light by N900 cam