<Somasis>
personally I think the case should be a bit more durable, but that's mostly from me fumbling with it while getting it put together. aside from that though, it looks nice
Astralix has joined #radxa
<Somasis>
right now I'm compiling a kernel and such for it and I'm going to be putting Exherbo Linux on it
<pstef>
Is it possible to push your custom Linux onto NAND?
<pstef>
I guess that's what I've tried but I couldn't tell, because I had inserted an SD card and it had been sitting there... and once I booted the board, df -h showed the root partition being mounted on an 8 gig partition, so I guess I fudged that up.
<cyrevolt>
nice, Exherbo is fun :) have fun with it Somasis ^^
<cyrevolt>
pstef, for that to work you would need to work on the bootloader
<cyrevolt>
how is Exherbo anyway, Somasis? I've never taken a closer look at it because it seemed kind of dead to me... I didn't know anyone was actually using it :D
<Somasis>
it's fun, I maintain some packages and stuff for it
<Somasis>
I'd been using Arch before but got bored with arch and wanted something different
<Somasis>
it's not so much dead as it has stablized a bit
<pstef>
cyrevolt: thanks.
<cyrevolt>
awesome... is Paludis similar to BSD's pkg-tool? I'm a Gentoo user btw, and Gentoo's Portage kinda originates from FreeBSD :D
<Somasis>
I think it's more akin to portage in terms of the way it works and how it's configured, but in terms of how you actually use it it's more in it's own class
<Somasis>
the package format is kind of similar to ebuilds from gentoo, a lot of the ideas and stuff behind the format are like it but it's not compatible with portage
<naobsd>
or you may use mainline kernel with kexec as "more functional bootloader"
field^Mop has quit [Ping timeout: 258 seconds]
<cyrevolt>
hmm I wish it was as easy as on x86 :D
<naobsd>
oops. I really don't like such info on forums
<cyrevolt>
I guess that was totally misleading then :D
<naobsd>
there is no reason to believe such a random talk without technical consideration
<naobsd>
you may be able to port GRUB ARM to Rockchip with necessary work
<cyrevolt>
yea well
<naobsd>
btw RK3188Loader(L)_Vxxx.bin is not u-boot
<cyrevolt>
I wanted a Android / Gentoo dual boot, so I'm now basically setting up Android on the NAND first
<cyrevolt>
ah ok good to know, thank you :)
<naobsd>
but there is u-boot for rockchip too, it should be RK3188Loader...uboot.bin
<naobsd>
cyrevolt: for dual boot, you may use recovery partition for 2nd OS, but I recommend to use SD
<naobsd>
... use SD for alternative OS
<Somasis>
okay so I rebooted... and it still doesn't work
<Somasis>
nothing from dmesg saying anything about it either
<naobsd>
Somasis: OTG port on RR never work from beginning? or you can use adb or mount fuction after Android boot?
<Somasis>
it appears to not be recognized on my laptop's end, I haven't gotten it to be recognized at all on here
<Somasis>
and I'm about to try that
<cyrevolt>
naobsd: I'll use SD. Are 64GB cards fine actually? Or should I prefer 32?
<naobsd>
cyrevolt: capacity shouldn't be a problem (but I don't have 32/64GB card)
<Somasis>
okay, after getting into android it seems to be recognized. I think the issue might have been the USB cord I was using. I'll try loader mode now and see if it works
<cyrevolt>
well I know that when running Android on the Radxa Rock I had trouble using a 64GB sd card
<cyrevolt>
it couldn't really use it, but that might be limitations of Android
<naobsd>
ah, change USB cable and/or PC is common solution :)
<naobsd>
cyrevolt: you tried exFAT? I'm not sure RR Android support it
<Somasis>
I was using an old cord from my raspberry pi, I guess maybe it was power only, not data transferring
<naobsd>
cyrevolt: if you use FAT32, it may work
<Somasis>
because it did power on with it plugged in, but no data or anything, so...
<cyrevolt>
you should now have device 2207:310b in lsusb
<cyrevolt>
well at least I do :D
<Somasis>
I've got a 2207:0010 device in there which wasn't there before
<Somasis>
I haven't mounted it in loader mode yet though so maybe that's why the ID is different, I don't know exactly what decides those IDs :)
<cyrevolt>
ah that could be the ID that Android supplies then
<cyrevolt>
the IDs are provided by the connected device
<Somasis>
ah
<cyrevolt>
that is why you can use them to allow r/w access etc
<cyrevolt>
in udev rules, you might have done that before =)
<cyrevolt>
awesome... either it was the update of KOTOR or the new Android image I just flashed, but anyway, I can install Star Wars: Knights of the Old Republic now - yeehaw :)
<naobsd>
oh I didn't know KOTOR is released for Android. good news ;)
<cyrevolt>
it was just released on 23rd
<cyrevolt>
now I cannot run it because I guess it tries to download to the insufficient internal storage
<cyrevolt>
-.-
<cyrevolt>
I really hate that about Android
<Somasis>
hmm, no found rockusb device
<Somasis>
but it shows in dmesg and lsusb now
<Somasis>
and it's in loader mode, the android with the exlaimation point and all
ganbold___ has joined #radxa
<Somasis>
any ideas?
orangecms has joined #radxa
<Somasis>
it's definitely recognized now, product is radxa_rock_pro and all
<orangecms>
hmm well and I just flashed a more recent boot.img - now it's missing the kernel modules and doesn't want to resume boot -.-
<orangecms>
are you trying to flash as a regular user? or as root?
<Somasis>
root
<orangecms>
for regular users, you will need to write a udev rule
<orangecms>
hmm
<Somasis>
it also failed with regular
<orangecms>
as root it should work
<Somasis>
wait
<Somasis>
it's recognized now, out of loader mode...huh
<orangecms>
it leaves the loader mode after 2 minutes of no operation
<Somasis>
what should the hdmi output look like when in loader mode?
<Somasis>
I'm assuming the screen with the android and the exclaimation point are the loader mode's appearance...
<orangecms>
gimme a second, I'll check
<Somasis>
alright, thanks
<orangecms>
I have no output actually
<Somasis>
okay there we go
<Somasis>
turns out that's not loader mode
<Somasis>
I thought it had to have green light and all
<orangecms>
nope, only red
<orangecms>
anyway, I switched back to an older boot.img ... now it's complaning about /dev/mmcblk... missing -.-
<orangecms>
oh, maybe because I haven't inserted it LOL :D
<Somasis>
how do I change the parameter? the instructions on the wiki are a bit confusing...
<orangecms>
you need to flash it through the flash tool
<orangecms>
path/to/upgrade_tool di -p /path/to/parameter
<orangecms>
... and don't forget to put the rootfs on the first partition, not like I just did without partitioning x)
cyrevolt has quit [*.net *.split]
ganbold__ has quit [*.net *.split]
ganbold___ is now known as ganbold
orangecms is now known as cyrevolt
<cyrevolt>
oh that is me btw :D
<Somasis>
hmm
<Somasis>
...this is the method for flashing an android, not a linux image, isn't it.
<Somasis>
the stuff on the wiki refers to building android stuff
<Somasis>
and how you'd get a parameter file
<Somasis>
and such
<Somasis>
I don't get any of that from compiling a kernel
<Somasis>
however, this debian server image flashed fine so maybe I'll just try and bootstrap Exherbo from there
<Somasis>
that'd make it much easier
<cyrevolt>
I guess so, yes
<cyrevolt>
well I have my Gentoo up and running :) yeeeehaw
<cyrevolt>
... and I cannot find out the root password :D
<Somasis>
any way to turn off the blinking green light?
<Somasis>
I'd be fine with it if it were on all the time but the blinking just hurts my eyes
<Somasis>
wait, never mind, found the LED page
mrcan_ has joined #radxa
Astralix1 has joined #radxa
mrcan has quit [Ping timeout: 245 seconds]
Astralix has quit [Ping timeout: 250 seconds]
hipboi has quit [Ping timeout: 250 seconds]
hipboi has joined #radxa
ganbold has quit [Read error: Connection reset by peer]
cyrevolt has quit [Quit: Leaving]
ganbold_ has joined #radxa
<Somasis>
are there any newer versions of the kernel aside from 3.0?
<Somasis>
systemd requires 3.8, apparently...
<Somasis>
wait, no, it doesn't, but I do still need it for a different program
<naobsd>
about newer version, you may use mainline kernel
<naobsd>
about systemd, which kernel and userland doesn't work?
<Somasis>
systemd is fine actually, I misread some stuff, and I got the issues with the program I'm using sorted out too
<Somasis>
systemd needs 3.8 for support for some security system in the kernel
<Somasis>
but I don't need that
<Somasis>
are there any plans to upgrade the kernel sources to be closer to the current mainline any time, though? I don't mean like up to date entirely, but at least based off a more recent longterm release
<naobsd>
as far as I know, currently no one try to support LTS kernel
<naobsd>
mainline kernel is always available
<naobsd>
you can try mainline when you want
hipboi has quit [Read error: Connection timed out]
hipboi has joined #radxa
wickwire has joined #radxa
Astralix1 has quit [Read error: Connection reset by peer]
Astralix has joined #radxa
wickwire_ has joined #radxa
wickwire has quit [Ping timeout: 240 seconds]
field^Mop has joined #radxa
wickwire__ has joined #radxa
wickwire_ has quit [Ping timeout: 255 seconds]
ChanServ has quit [shutting down]
ChanServ has joined #radxa
mrcan_ has quit [Read error: Connection reset by peer]
mrcan_ has joined #radxa
field^Mop has quit [Ping timeout: 245 seconds]
wickwire_ has joined #radxa
wickwire__ has quit [Ping timeout: 258 seconds]
wickwire_ has quit [Read error: Connection reset by peer]