k1r1t0 has quit [Read error: Connection reset by peer]
SuperMarioSF has quit [Ping timeout: 246 seconds]
gliffy has quit [Ping timeout: 248 seconds]
norayr has left #maemo-leste [Disconnected: closed]
norayr has joined #maemo-leste
radv has joined #maemo-leste
<radv>
PTI
<radv>
I have a pine phone. I bought it because I have an N900 and wanted a new device to run maemo. I have never been able to boot maemo (or anything) from a MicroSD card in the pine phone. any thought would be useful.
<radv>
the pine phoe forums have not been useful.
<humpelstilzchen[>
How did you install the pinephone distributions on the SD?
<radv>
i tried using dd to create the image, but the device doesnt recognize the sd card at all. eventually i used balenaEtcher from a pc runnning windows 11
<radv>
i'm fairly sure it's a device hardware problem, not a problem with the maemo image...still thought someone here might be able to put me on some useful path
<humpelstilzchen[>
Maybe try a different sd card?
<radv>
i have
<humpelstilzchen[>
ok, what exact dd command have you used?
<radv>
most reciently I did not use any because the device doesn't know there's a cardin the slot.
<radv>
lsblk only gives me results for he emmc
nela has quit [Ping timeout: 260 seconds]
nela has joined #maemo-leste
mro has quit [Remote host closed the connection]
<buZz>
radv: hey, got it working yet? :D
<buZz>
radv: maybe your dipswitches inside the pinephone have the SD slot disabled? not sure if thats possible
<buZz>
but some of those dipswitches dis/enable specific hardware
<buZz>
radv: lsblk will -always- just list devices it sees :P if there's no card (or no valid partition!!) on the device, it wont be visible in lsblk
<buZz>
try a ls /dev/mmc* to see if mmc0(?) is the only device it sees (regardless of partitions, those would be mmc0p1 etc)
gliffy has joined #maemo-leste
<radv>
ls /dev/mmc* shows only the mmcblk2 i.e. the emmc storage
<radv>
this thing abut dipswitches is new information
<bencoh>
you can also check /sys/bus/mmc/devices/
<bencoh>
and find /sys/devices -iname mmc_host
<buZz>
radv: there are dipswitches under the battery lid
<radv>
oh, those...i dont think theres on for the microsd card.
<buZz>
radv: did you read dmesg? it might tell you about if it saw any other mmc device
<buZz>
radv: wouldnt hurt to confirm they are all on , though ;)
<radv>
true
<radv>
ls /sys/bus/mmc/devices returns mmc1:0001 and mmc2:0001
<buZz>
so, it does see it
<buZz>
radv: its possible that whatever kernel you are currently running just lacks support for SD cards ;)
<buZz>
iirc i did need to flash something onto the pinephone before i could boot
<radv>
hum. i'm skeptical
<radv>
even so wouldnt it read the sdcard first oon startup?
<buZz>
only if written correctly
<radv>
hum
<radv>
okay
<buZz>
if you write the .img file to a -partition- , it wont work ;)
<radv>
well this is something
<buZz>
> Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.
<buZz>
alright, you didnt answer the dd command question :P
<radv>
i guess i shuld check with the Arch Linux folks about
<buZz>
why? arch doesnt even support ARM
<radv>
thats what i have running right now
<buZz>
you mean alarm? thats not arch, its a forked distro
<buZz>
by 1 person mostly
Twig has joined #maemo-leste
<buZz>
writing the SD card is something you do on a different machine though, usually
mro has joined #maemo-leste
<radv>
which doesnt reognize the card with lsblk or fdisk but shows it in the /sys/bus/mmc/devices file
<radv>
yeah, i mean alarm
<buZz>
i would just assume alarm very iffy, its a mess of a distro
<buZz>
why cant you use a normal PC to write the SD card?
maemish_ has joined #maemo-leste
mro has quit [Remote host closed the connection]
<radv>
i did...i mean one with windows
<radv>
i used balenaEtcher
<radv>
that wouldnt cause the problem, would it?
ceene has quit [Remote host closed the connection]
<buZz>
i never had any success with etcher or windows
mro has joined #maemo-leste
<radv>
maybe etchers creating a partition a few blocks away from what the device can read...
<buZz>
maybe etcher is a website ;)
<radv>
i guess ive got to figure out how to write to the sd card using the pine phone and a archlike system that cant see the card
<buZz>
what does dmesg say when you insert a SD card -while booted- on the pinephone with alarm?
<radv>
i'd downloaded some balenaetcher softwware
<radv>
geesh my typings ugly with this keyboard
<radv>
...hang on...
<radv>
well while the card is in, withoutremoving and reinserting...its saying "no support for cards volts" about something
<radv>
sunxi mmc 1c0f000.mmc
<radv>
it's refrencing an SDIO card
radv has quit [Quit: Client closed]
radv has joined #maemo-leste
<radv>
battery fell out
mro has quit [Remote host closed the connection]
<radv>
i do not get the voltage error when the card is not in the slot
<radv>
grumble...now the keyboards not working...ill be back later. thanks for working with me
<buZz>
sounds like the kernel isnt setting up voltages correctly
radv has quit [Quit: Client closed]
gliffy has quit [Ping timeout: 252 seconds]
radv has joined #maemo-leste
<radv>
i can't see if there've been any comments here in he last hour.
<radv>
other then this Arch fork I'm using now I had some problems with the microsd card reader when I had Manjaro on the device, but I had may other problems with that system.
<buZz>
18:56:42 < buZz> sounds like the kernel isnt setting up voltages correctly
<buZz>
radv: try a external USB sdcard thingy then?
<radv>
I'd try installing Maemo Leste on the emmc, but on the wiki for the pine phone, under installation I'm reading "Note: currently not working"
<radv>
yeah, ive thought about the external usb, but it makes the device less portable
<buZz>
radv: you need it a single time
<buZz>
just to make the SD card
<buZz>
the -kernel- sets up voltages for devices
<buZz>
seemingly the kernel that alarm ships for PP is crap and doesnt do it correctly
mro has joined #maemo-leste
<Wizzup>
alarm = arch arm?
maemish_ has quit [Quit: Connection closed for inactivity]
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
<Wizzup>
uvos: so I have the module blacklisted and still get the same problem