<tmlind>
might be worth testing.. i typed up the description on what i suspect might be happening on the "failed to enable" clkctrl errors..
<tmlind>
i noticed this with the recent lakml iopoll changes being discussed for timekeeping suspended
<tmlind>
uvos: maybe grep your logs for "failed to enable" or "failed to disable", if that happens for spi, then cpcap read/write will fail
<tmlind>
i'll post it to the lists maybe next week as rfc unless it's proven to not help before that
<tmlind>
oh and if m-l kernel .config has armv6 disabled, then ARM_ERRATA_754327 option must be enabled
mrkrisprolls has quit [Ping timeout: 265 seconds]
<tmlind>
hmm i'm at least seeing some "failed to disable" errors here based on quick testing
<tmlind>
but i think those might be ok, if a device is configured for autoidle disabling it's clock won't immediately do anything
fab_ has joined #maemo-leste
xmn has quit [Ping timeout: 248 seconds]
Twig has joined #maemo-leste
ceene has joined #maemo-leste
Twig has quit [Ping timeout: 240 seconds]
Twig has joined #maemo-leste
fab_ has quit [Quit: fab_]
pere has quit [Ping timeout: 248 seconds]
Blikje has joined #maemo-leste
pere has joined #maemo-leste
fab_ has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__>
tmlind: i have not recently seen any hangs whatsoever
<uvos__>
tmlind: i also have no sutch thing in my logs, going back qutie far
<uvos__>
tmlind: i will build the m-l kernel with the patch none the less
<tmlind>
uvos__: ok i just saw it again yesterday. not sure if that will help, i'll test with geert's iopoll patches and clkctrl using iopoll to see if it makes a difference
<uvos__>
you seeing a stability issue we dont has to be a first :P
<tmlind>
heh yeah this has been happening for few years though after about two weeks of uptime
<tmlind>
well at least i suspect this is what is happening
<tmlind>
just a guess at this point though
<freemangordon>
uvos__: please enable n900 fmtx while at it
<freemangordon>
tmlind: do you use leste or just leste kernel?
<freemangordon>
or neither :)
<tmlind>
freemangordon: one d4 with m-l, one with alpine
supositware[m] has quit [Remote host closed the connection]
<freemangordon>
and both devices hang?
<tmlind>
have not used m-l for that long at a time but same kernel more or less yeah
<tmlind>
are you seeing over two week uptime on regular basis?
<Wizzup>
I currently have 13 days and 21:35 :p
<Wizzup>
but usually it's not that high
Twig has quit [Ping timeout: 264 seconds]
Twig has joined #maemo-leste
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
<tmlind>
yeah ok might be worth grepping the logs if it hangs in a week or so
<freemangordon>
but don;t remember having a hang for at least 3 months
pere has joined #maemo-leste
uvos__ has quit [Ping timeout: 268 seconds]
<Wizzup>
I think I had one once with mpv
uvos__ has joined #maemo-leste
ceene has quit [Remote host closed the connection]
fab_ has quit [Quit: fab_]
<maxwelld>
right now 7 days uptime for my droid. i guess because the battery drained and it died. otherwise it would not shut down.
xmn has joined #maemo-leste
nela has quit [Quit: bye]
nela has joined #maemo-leste
chrisgadget has joined #maemo-leste
chrisgadget has quit [Client Quit]
<uvos__>
my d4 is been up 6 days atm
<uvos__>
but im pretty sure i have had >14 days occasionally
<uvos__>
d4 is currenty been really stable
uvos__ has quit [Ping timeout: 246 seconds]
mrkrisprolls has joined #maemo-leste
uvos__ has joined #maemo-leste
jack has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
Wizzup: did you receive my email ? (dumps)
<Wizzup>
yes
<Wizzup>
I'm assembling furniture atm :( (moving)
<Wizzup>
should be done in ~2 days
<dsc_>
2 days... a big couch
<Wizzup>
other stuff too :)
<dsc_>
:>
<arno11>
Wizzup: ok good luck man :)
jack has quit [Quit: jack]
<arno11>
fun stuff: combining mplayer-xv accel-ffmpeg-yt-dlp(with python3.7), N900 is able to stream youtube and lot of catchupTV's (240-360p)
<dsc_>
nice
<arno11>
yes and so probably 480-720p on d4
akossh has joined #maemo-leste
maemish_ has joined #maemo-leste
<maemish_>
Is there coming the chimaera release?
<arno11>
maemish: chimaera release is already there
<arno11>
and works great
<maemish_>
Aa, I thought there would be news posted on maemo forum.
<arno11>
oh ok i see. News from devs will be posted soon i think.
Twig has quit [Remote host closed the connection]
Twig has joined #maemo-leste
<sicelo>
arno11: email about N900 voice calls?
<maemish_>
Checked also Leste news and twitter but no mention.
<arno11>
sicelo: btw did you receive the 2 mails i send you few weeks ago ? (voice calls process)
<maemish_>
So overclocking setup needs to be done again after every dist and kernel upgrade?
<sicelo>
arno11: yes, thanks i did :-)
<arno11>
maemish: for the moment yes
<arno11>
sicelo: ok :)
<dsc_>
a bit strange, the touchscreen on my d4 stopped working
<dsc_>
sometimes it works ... like 5% of the time
<sicelo>
i haven't been able to try it out yet, because of some projects at work, but things are getting better now. i'd be happy to get any updates you may have, if you don't mind
<arno11>
sicelo: sure no probs
<sicelo>
tyvm
<dsc_>
hmm, fixed it
<sicelo>
how
<dsc_>
new SD card with maemo-leste-1.0-armhf-droid4-20230430.img.xz >_>
<arno11>
dsc_: corrupted files you think ?
<dsc_>
I had bbq ribs earlier, maybe something wrong with my finger where it doesnt detect touches
<dsc_>
i tried another d4 device and same issue
<dsc_>
xD
<arno11>
lol
<sicelo>
seems you need a new finger :p
<maemish_>
Was it that I can run distupgrade on Leste to chimaera from an older build or do I need to dd new image?
<arno11>
maemish: distupgrade should work but if your older build is slow, probably better to dd a new one
<arno11>
and be careful to expand sd card on first boot.
<arno11>
and normally swap will setup automatically on fresh install
<arno11>
N900+swap+extanded sd root partition+overclock+good fast sd works really well
<arno11>
excepting during the first 30 sec once hildon desktop loaded
<maemish_>
But do I do something wrong here. Using LMDE version of Mint. I use usb format to format the sdcard to fat32, then use the usb image writer to write the image to the card.
<maemish_>
It goes quite far atleast on loading the image with N900.
<Wizzup>
why not use dd?
<arno11>
indeed
<maemish_>
Not wanting to answer.
<maemish_>
But so fat32 is right for the card as format?
<arno11>
maemish: you don't need to format
<arno11>
just follow getting started wiki
<Wizzup>
maemish_: no it is not
<Wizzup>
if the image writer does the same as dd, it doesn't matter what you do beforehand
<maemish_>
So because I normally never use dd I always when I want to install Leste forget how the dd works. So I search "dd image linux" and then I get different guides with different options. If the one at the wikipage is correct the N900 page could have that guide linked. But even that didn't work.
<sixwheeledbeast>
that isn't the same command you posted, bs is unlikely an issue is how much it writes in one go.
<sixwheeledbeast>
The is uncompressing with xzcat and then I assume dd is reading the pipe for if=
<maemish_>
I used the one from wiki after I tried with the one I posted. Neither worked and N900 boots again before launch.
norayr has quit [Ping timeout: 246 seconds]
antranigv has quit [Ping timeout: 240 seconds]
maxwelld has quit [Ping timeout: 268 seconds]
<maemish_>
Trying now the previous chimaera image
<sixwheeledbeast>
is if and of correct
uvos__ has quit [Remote host closed the connection]
<maemish_>
Can you give then here what you use?
<sixwheeledbeast>
they will vary based on the system
<maemish_>
Could not get the previous chimaera either
<maemish_>
to boot to desktop
<sixwheeledbeast>
who knows what /dev/sdb is
norayr has joined #maemo-leste
antranigv has joined #maemo-leste
<maemish_>
My sdcard
maxwelld has joined #maemo-leste
<maemish_>
To which it dd and then starts to boot up the leste on n900 but it stops where I have shown with pictures above
<maemish_>
By the way pawnexpress for N900 has an app for overclocking with a slider. Seems nice.