00:06
<
youmukonpaku1337 >
apritzel: get practically the same bootlog with that env var set for initrd high... i wonder what could be the issue here
00:07
<
youmukonpaku1337 >
should i try manually defining dev ram0 and the address for initrd?
00:20
apritzel has quit [Ping timeout: 480 seconds]
00:23
montjoie_ has joined #linux-sunxi
00:25
montjoie has quit [Ping timeout: 480 seconds]
00:57
<
smaeul >
Loading Ramdisk to 48f39000, end 48f39000 ... OK
00:58
<
smaeul >
youmukonpaku1337: looks like U-Boot thinks your initramfs size is zero. you may need to remove the "0x" prefix from your numbers
00:58
<
youmukonpaku1337 >
oh true
00:58
<
youmukonpaku1337 >
might try
00:58
<
youmukonpaku1337 >
but probs after i get some sleep
00:58
<
youmukonpaku1337 >
q
00:59
youmukon1 has joined #linux-sunxi
00:59
youmukon1 has quit []
01:00
youmukon1 has joined #linux-sunxi
01:01
youmukon1 has quit []
01:01
youmukon1 has joined #linux-sunxi
01:01
youmukonpaku1337 is now known as Guest1397
01:01
youmukon1 is now known as youmukonpaku1337
01:01
<
youmukonpaku1337 >
ugh
01:02
<
youmukonpaku1337 >
why the hell did weechat set my nick to youmukon1
01:03
<
youmukonpaku1337 >
oh my laptop didnt close connection when going to sleep
01:03
<
youmukonpaku1337 >
fun
01:07
Guest1397 has quit [Ping timeout: 480 seconds]
01:18
vagrantc has quit [Ping timeout: 480 seconds]
03:59
hexdump01 has joined #linux-sunxi
04:01
hexdump0815 has quit [Ping timeout: 480 seconds]
05:26
JohnDoe_71Rus has joined #linux-sunxi
05:50
freemangordon has joined #linux-sunxi
06:06
vagrantc has joined #linux-sunxi
06:46
warpme has joined #linux-sunxi
06:47
vagrantc has quit [Ping timeout: 480 seconds]
07:38
evgeny_boger has joined #linux-sunxi
07:46
evgeny_boger has quit [Ping timeout: 480 seconds]
08:26
junari has joined #linux-sunxi
08:31
<
junari >
hi to all. Maybe someone found a UART driver patch for RS485 flow control via GPIO?
09:04
junari has quit [Ping timeout: 480 seconds]
09:13
apritzel has joined #linux-sunxi
09:21
bauen1 has quit [Ping timeout: 480 seconds]
10:01
junari has joined #linux-sunxi
10:01
apritzel has quit [Remote host closed the connection]
10:04
apritzel has joined #linux-sunxi
10:22
junari_ has joined #linux-sunxi
10:30
junari has quit [Ping timeout: 480 seconds]
10:39
junari_ has quit [Ping timeout: 480 seconds]
11:04
<
karlp >
does the dtr-gpios or rts-gpios device tree bindings not work for you?
11:04
<
karlp >
combined with rs485-rts-active-low
11:05
<
karlp >
sorry, sorry, not that one, the other one...
11:17
kuba2k2 has joined #linux-sunxi
11:21
junari_ has joined #linux-sunxi
11:24
junari_ is now known as junari
11:25
<
junari >
there is should be serial_rs485 structure for that
11:36
junari has quit [Remote host closed the connection]
12:05
bauen1 has joined #linux-sunxi
12:08
youmukon1 has joined #linux-sunxi
12:08
DarkNeutrino has quit [Ping timeout: 480 seconds]
12:08
DarkNeutrino has joined #linux-sunxi
12:09
junari has joined #linux-sunxi
12:10
junari has joined #linux-sunxi
12:11
hentai has quit [Remote host closed the connection]
12:11
youmukonpaku1337 has quit [Read error: Connection reset by peer]
12:11
hentai has joined #linux-sunxi
12:11
hentai has quit [Remote host closed the connection]
12:48
youmukonpaku1337 has joined #linux-sunxi
12:48
youmukon1 has quit []
12:48
<
youmukonpaku1337 >
a
12:59
<
youmukonpaku1337 >
smaeul: nope not it :(
12:59
<
youmukonpaku1337 >
Loading Ramdisk to 486ab000, end 48f38400 ... OK
12:59
<
youmukonpaku1337 >
but still panic
13:00
<
smaeul >
can you paste the full log, with `setenv initrd_high ffffffff` as well?
13:00
<
youmukonpaku1337 >
oh ok i didnt do the initrd high
13:00
<
youmukonpaku1337 >
let me try that
13:00
<
youmukonpaku1337 >
one sec
13:04
<
youmukonpaku1337 >
smaeul: alright even with that it panicked so lemme paste it
13:07
<
smaeul >
well you have "Unpacking initramfs...", so the kernel sees the initramfs, so I'm guessing the problem is with the initramfs contents
13:07
<
smaeul >
how did you generate it?
13:11
<
youmukonpaku1337 >
smaeul: downloaded an alpine minirootfs, added in the kernel modules that megi provided and packed it in cpio
13:11
<
smaeul >
yes, but what command to generate the cpio archive?
13:11
<
youmukonpaku1337 >
one sec
13:12
<
youmukonpaku1337 >
find ./ | cpio --create -H newc > output.cpio
13:12
<
youmukonpaku1337 >
in the alpine rootfs root dir
13:19
<
smaeul >
youmukonpaku1337: well there's your problem. the alpine minirootfs doesn't contain an /init, so it's not a complete initramfs as-is
13:20
<
smaeul >
you can do `ln -s sbin/init init` from the root of the initramfs directory, but the minirootfs doesn't include openrc, so at most you'll get some gettys
13:22
<
smaeul >
that would at least not crash
13:22
JohnDoe_71Rus has quit []
13:22
<
smaeul >
or if you just want an interactive shell, /init can be a short shell script
13:23
<
smaeul >
mount -t proc proc /proc && mount -t devtmpfs dev /dev && setsid sh -i </dev/ttyS0 >/dev/ttyS0 2>&1 && reboot -f
13:23
<
smaeul >
or similar
13:24
<
youmukonpaku1337 >
im pretty sure minirootfs does include openrc
13:24
<
youmukonpaku1337 >
but yeah i just need an interactive shell and then ill check if i can get something proper
13:29
<
youmukonpaku1337 >
huh
13:29
<
youmukonpaku1337 >
i do remember using openrc in a chroot
13:29
<
youmukonpaku1337 >
i guess not then
13:51
kuba2k2 has quit [Ping timeout: 480 seconds]
14:11
<
youmukonpaku1337 >
smaeul: I HAVE A SHELL!!!!!!!!
14:11
<
youmukonpaku1337 >
LETS FUCKING GOOO
14:11
<
youmukonpaku1337 >
uhhhh
14:11
<
youmukonpaku1337 >
ok so minor issue
14:12
<
youmukonpaku1337 >
after like 20 seconds it disabled dcdc2 which is the cpu power supply???? wtf
14:14
<
apritzel >
youmukonpaku1337: do you have regulator-always-on; in the dcdc2 node?
14:14
<
youmukonpaku1337 >
lemme check
14:14
<
youmukonpaku1337 >
if i dont thats insanely funny
14:15
kuba2k2 has joined #linux-sunxi
14:15
<
youmukonpaku1337 >
apritzel: i do
14:16
<
youmukonpaku1337 >
so thats mildly concerning
14:16
<
smaeul >
how do you know dcdc2 is getting disabled? regulator-always-on should definitely prevent that
14:16
<
youmukonpaku1337 >
~ # ldo2: disabling
14:16
<
youmukonpaku1337 >
dcdc2: disabling
14:16
<
youmukonpaku1337 >
and then i lose input
14:17
<
youmukonpaku1337 >
so i think it powered off
14:18
<
smaeul >
alright, double-check your dts -- remember, it's the copy embedded inside U-Boot that is being used
14:18
<
smaeul >
also, if you have "&cpu0 { cpu-supply = <®_dcdc2>; };" in the DTS, then Linux should keep the regulator on anyway, though currently this requires having a cpufreq driver loaded
14:18
<
youmukonpaku1337 >
smaeul: yes thats what im reading
14:19
<
youmukonpaku1337 >
smaeul: the bootlog does mention something about cpufreq iirc
14:20
<
youmukonpaku1337 >
nvm it doesnt
14:20
<
youmukonpaku1337 >
as for my cpu0 in dts
14:20
<
smaeul >
youmukonpaku1337: alright, though also make sure you rebuilt U-Boot after you changed the DTS
14:20
<
youmukonpaku1337 >
i did not change it
14:20
<
youmukonpaku1337 >
lol
14:21
<
youmukonpaku1337 >
because dcdc2 is always on anyway
14:21
<
youmukonpaku1337 >
wait lemme reboot and try again xddd
14:21
<
smaeul >
well you changed it at some point, because you wrote it :)
14:22
<
youmukonpaku1337 >
yes and thats whats in my latest build xd
14:22
<
youmukonpaku1337 >
i always rebuild when i change dts
14:23
junari_ has joined #linux-sunxi
14:23
<
smaeul >
just checking
14:23
<
smaeul >
you can also try `ls /proc/device-tree/soc/i2c@1c2ac00/pmic@34/regulators/dcdc2` (I think that path is right) before it dies to make sure regulator-always-on is there at runtime
14:24
<
youmukonpaku1337 >
sure one sec
14:24
<
youmukonpaku1337 >
lemme just paste the commands i used to boot here so i dont have to scroll for 2 hours in minicom lmao
14:24
<
youmukonpaku1337 >
=> setenv bootargs "earlycon=uart,mmio32,0x1c28400 console=ttyS0,115200n8"
14:24
<
youmukonpaku1337 >
=> setenv initrd_high 0xffffffff
14:24
<
youmukonpaku1337 >
=> bootz 0x42000000 0x43300000:7DF800 $fdtcontroladdr
14:26
<
youmukonpaku1337 >
smaeul: no such file or directory
14:26
<
youmukonpaku1337 >
huh
14:26
<
youmukonpaku1337 >
/proc/device-tree exists but when i ls it it says "no such file or directory"
14:26
<
youmukonpaku1337 >
wtf
14:27
<
apritzel >
maybe the kernel doesn't export it, you can try /sys/firmware/devicetree/base instead
14:29
<
smaeul >
and I might have got some part of the path wrong, too
14:29
<
apritzel >
yeah, that's tricky. I had the same idea, but gave up figuring out the exact path :-D
14:29
<
youmukonpaku1337 >
apritzel: nope :p
14:29
junari has quit [Ping timeout: 480 seconds]
14:29
<
youmukonpaku1337 >
not it
14:30
<
youmukonpaku1337 >
this is mildly concerning
14:30
<
smaeul >
so maybe check each part successively
14:30
<
smaeul >
unfortunately regulators don't have an equivalent of `clk_ignore_unused` for a temporary workaround
14:33
<
youmukonpaku1337 >
oh yea maybe im missing ldo2?
14:33
<
youmukonpaku1337 >
hmm
14:34
<
youmukonpaku1337 >
might be that lemme add it
14:35
<
apritzel >
ldo2 is probably crucial too (for the PLLs?), but dcdc2 should stay on regardless
14:36
<
youmukonpaku1337 >
what the hell is ®_dcdc3 {
14:36
<
youmukonpaku1337 >
regulator-always-on;
14:36
<
youmukonpaku1337 >
regulator-min-microvolt = <1200000>;
14:36
<
youmukonpaku1337 >
regulator-max-microvolt = <1200000>;
14:36
<
youmukonpaku1337 >
regulator-name = "vdd-int-pll";
14:36
<
youmukonpaku1337 >
};
14:38
<
youmukonpaku1337 >
meh ill add it
14:42
<
apritzel >
careful with adding random regulators, your board might not like the voltage on those pins
14:44
<
youmukonpaku1337 >
fair
14:44
<
youmukonpaku1337 >
but can't know if it works without trying :P
14:44
<
youmukonpaku1337 >
oh fuck
14:45
<
apritzel >
there are examples of boards using the same SoC and the same PMIC, but one board using a particular regulator for 1.8V, another board the same regulator for 3.3V
14:45
<
youmukonpaku1337 >
Error: arch/arm/dts/.sun5i-a13-pocketbook-616.dtb.pre.tmp:82.1-11 Label or path reg_dcdc2 not found
14:45
<
youmukonpaku1337 >
Error: arch/arm/dts/.sun5i-a13-pocketbook-616.dtb.pre.tmp:89.1-11 Label or path reg_dcdc3 not found
14:45
<
youmukonpaku1337 >
FATAL ERROR: Syntax error parsing input tree
14:45
<
youmukonpaku1337 >
Check /home/q/pbkernel/pb-6.4/u-boot/arch/arm/dts/.sun5i-a13-pocketbook-616.dtb.pre.tmp for errors
14:45
<
youmukonpaku1337 >
make[2]:
*** [scripts/Makefile.lib:335: arch/arm/dts/sun5i-a13-pocketbook-616.dtb] Error 1
14:45
<
youmukonpaku1337 >
make[1]:
*** [dts/Makefile:44: arch-dtbs] Error 2
14:45
<
youmukonpaku1337 >
make:
*** [Makefile:1156: dts/dt.dtb] Error 2
14:45
<
youmukonpaku1337 >
goddamit
14:45
<
youmukonpaku1337 >
how do i cross compile dtbs lmao
14:46
<
apritzel >
it's probably just a typo somewhere
14:46
<
apritzel >
it gives you some breadcrumbs to follow
14:47
<
youmukonpaku1337 >
nope
14:48
<
youmukonpaku1337 >
nothing that wouldnt compile on my phone..
14:49
<
youmukonpaku1337 >
also are dtbs architecture agnostic
14:49
<
apritzel >
yes, there is no "cross" in compiling DTs
14:50
<
apritzel >
it's just source level DT to DTB, which is the same everywhere
14:50
<
youmukonpaku1337 >
got it
14:51
<
youmukonpaku1337 >
well this is uhhh
14:51
<
youmukonpaku1337 >
weird
14:51
<
youmukonpaku1337 >
i have absolutely no idea why it isnt compiling
14:51
<
apritzel >
well, check your DT source again
14:51
<
apritzel >
or look at that file it tells you to look at
14:54
<
youmukonpaku1337 >
uh
14:54
<
youmukonpaku1337 >
diff arch/arm/dts/sun5i-a13-pocketbook-616.dts arch/arm/dts/.sun5i-a13-pocketbook-616.dtb.pre.tmp
14:54
<
youmukonpaku1337 >
206a207
14:54
<
youmukonpaku1337 >
> #include "sunxi-u-boot.dtsi"
14:54
<
youmukonpaku1337 >
in the tmp file\
14:54
<
youmukonpaku1337 >
only difference
14:55
<
youmukonpaku1337 >
as for my DT source
14:56
<
youmukonpaku1337 >
take a look at this i suppose? i see nothing wrong
14:59
<
apritzel >
move ®_dcdc2 and ®_dcdc3 below the #include "axp209.dtsi" line
15:00
<
youmukonpaku1337 >
oh ok
15:02
<
apritzel >
that seems to fix it for me
15:02
JohnDoe_71Rus has joined #linux-sunxi
15:05
<
youmukonpaku1337 >
apritzel: built lets goo
15:07
apritzel has quit [Remote host closed the connection]
15:08
junari has joined #linux-sunxi
15:08
junari has quit [Remote host closed the connection]
15:08
apritzel has joined #linux-sunxi
15:08
junari has joined #linux-sunxi
15:12
mripard has quit [Quit: mripard]
15:13
<
youmukonpaku1337 >
apritzel: smaeul: that fixed it
15:13
<
youmukonpaku1337 >
so ig i just needed to add some regulators
15:13
<
apritzel >
why? anything broken?
15:15
kuba2k2 has quit [Ping timeout: 480 seconds]
15:15
<
youmukonpaku1337 >
apritzel: yeah i had it turn off the cpu power supply after 10 seconds if you havent seen that :P
15:16
<
youmukonpaku1337 >
now fixed by adding some regulators from megi's dtb to mine
15:16
<
youmukonpaku1337 >
so uh
15:16
<
youmukonpaku1337 >
i have a shell
15:16
<
apritzel >
check the MMCs (cat /proc/partitions)
15:16
<
youmukonpaku1337 >
major minor #blocks name
15:17
<
youmukonpaku1337 >
179 0 7634944 mmcblk1
15:17
<
youmukonpaku1337 >
179 1 7130112 mmcblk1p1
15:17
<
youmukonpaku1337 >
179 2 32768 mmcblk1p2
15:17
<
youmukonpaku1337 >
179 3 1 mmcblk1p3
15:17
<
youmukonpaku1337 >
179 5 16384 mmcblk1p5
15:17
<
youmukonpaku1337 >
179 6 16384 mmcblk1p6
15:17
<
youmukonpaku1337 >
179 7 35328 mmcblk1p7
15:17
<
youmukonpaku1337 >
259 0 250368 mmcblk1p8
15:17
<
youmukonpaku1337 >
259 1 100352 mmcblk1p9
15:17
<
youmukonpaku1337 >
259 2 16384 mmcblk1p10
15:17
<
youmukonpaku1337 >
179 8 4096 mmcblk1boot0
15:17
<
youmukonpaku1337 >
179 16 4096 mmcblk1boot1
15:17
<
youmukonpaku1337 >
sd isnt plugged in so lemme add that
15:17
<
youmukonpaku1337 >
might transfer the stuff i need over it xd
15:18
<
apritzel >
so it seems like the eMMC is somewhat working then
15:18
<
apritzel >
I'd give it some stability test
15:18
<
youmukonpaku1337 >
how
15:19
<
youmukonpaku1337 >
~~just write it over with zeros???~~
15:19
<
apritzel >
if you are happy to lose everything on it: maybe
15:19
<
apritzel >
or you back the partitions up one by one to an SD card
15:19
<
youmukonpaku1337 >
its not like i can boot into pocketbook os anyway :P
15:19
<
apritzel >
or run md5sum on the block device
15:20
<
youmukonpaku1337 >
and if i need stock os i can pull it off another pocketbook i have
15:20
<
youmukonpaku1337 >
so fuck backups
15:20
<
apritzel >
well, then you could put your alpine rootfs into one partition, and lose the initrd
15:21
<
youmukonpaku1337 >
id rather set up debian on mmc
15:21
<
apritzel >
or a Debian bootworm no-cloud image
15:21
<
youmukonpaku1337 >
so that i dont need musl bullshit
15:21
<
apritzel >
*bookworm, rather
15:21
<
youmukonpaku1337 >
why not a sid rootfs apritzel :p
15:21
<
youmukonpaku1337 >
i like sid
15:22
<
apritzel >
then don't complain when something is broken ...
15:22
<
youmukonpaku1337 >
of course :P
15:22
<
youmukonpaku1337 >
anyway ill also need a boot partition i assume
15:22
<
apritzel >
I mean you probably have enough issues with the DT and kernel and what not
15:22
<
youmukonpaku1337 >
meh fair guess ill grab bookworm
15:23
<
youmukonpaku1337 >
worst case i upgrade to sid with sourceslist
15:23
<
smaeul >
u-boot can read ext4, so you don't really
_need_ a boot partition
15:23
<
youmukonpaku1337 >
yeah but id rather not have to boot over FEL each time
15:23
<
youmukonpaku1337 >
xD
15:24
<
youmukonpaku1337 >
plus i need to use a modded otg cable or stuff anyway
15:24
<
apritzel >
you can just put your u-boot-sunxi-with-spl.bin into the eMMC boot partition
15:24
<
smaeul >
FEL is unrelated to (GPT) partitions. U-Boot goes on that mmcblk1boot0 device
15:25
<
youmukonpaku1337 >
oh ok
15:25
<
youmukonpaku1337 >
will i need to write a kernel cmdline n stuff
15:26
<
youmukonpaku1337 >
i assume i will
15:26
<
youmukonpaku1337 >
oh also where would boot.scr containing that kinda stuff go
15:28
<
apritzel >
on a boot partition ;-), but I think this could also be the root partition, just something that U-Boot would scan
15:29
junari_ has quit [Ping timeout: 480 seconds]
15:29
<
youmukonpaku1337 >
hm ok
15:29
<
youmukonpaku1337 >
so uh
15:29
<
youmukonpaku1337 >
how can i install debian
15:29
<
youmukonpaku1337 >
in uh
15:29
<
youmukonpaku1337 >
simple steps
15:33
<
youmukonpaku1337 >
apritzel
15:35
<
apritzel >
without USB and network that's tricky: I'd try to get hold of some armhf image, and just dd that to an eMMC partition
15:36
<
youmukonpaku1337 >
oh i can just throw it onto sd cant i
15:39
<
smaeul >
PPP over UART :D
15:41
<
apritzel >
smaeul: ah, thanks, I just realised that the cloud images are 64-bit only
15:42
<
smaeul >
yeah, this has all the other architectures, including ports (read: RISC-V)
15:43
<
smaeul >
I'm assuming the Debian kernel already has everything needed for A13 enabled, so it should be pretty much dd-able
15:44
<
apritzel >
it looks like a .qcow2 in there, some one more hurdle before that ...
15:46
<
smaeul >
of course by "dd" I mean "qemu-img dd" ;)
15:46
<
apritzel >
and even after "qemu-img convert" it's a 10GB image file, so some more massaging needed
15:47
<
apritzel >
but hey: nobody said it would be a walk in the park ...
15:49
vagrantc has joined #linux-sunxi
15:51
<
apritzel >
Ubuntu had this nice "core" image some years back, some convenient 30ish MB image file that had enough to apt-get everything else
16:12
hentai has joined #linux-sunxi
16:52
junari has quit [Remote host closed the connection]
17:06
<
youmukonpaku1337 >
apritzel: the image when converted with qemu-img for armhf is 265mb :P
17:08
<
youmukonpaku1337 >
but i cant mount it
17:10
<
apritzel >
if you are looking at the dqib image the smaeul mentioned above: the one I checked had the partition starting at 64KB
17:10
<
youmukonpaku1337 >
nvm
17:11
<
youmukonpaku1337 >
apritzel: is that a bad thing
17:11
<
apritzel >
well, it means you need to give that offset to mount if you want to loop mount it
17:11
<
apritzel >
or dd it
17:12
<
youmukonpaku1337 >
kay
17:12
<
youmukonpaku1337 >
but yeah i got an image
17:12
<
youmukonpaku1337 >
and converted with dd
17:12
<
youmukonpaku1337 >
tis 650m
17:12
<
apritzel >
yes, that's about the size I got as well
17:12
<
youmukonpaku1337 >
apritzel: so uh how would i go about writign that image to emmc and making it boot
17:14
<
apritzel >
if you got the raw filesystem image, I'd write it to an SD card, then dd it on the board to one of the eMMC partitions
17:14
<
youmukonpaku1337 >
apritzel: idk i just used qemu-img convert :p
17:15
<
youmukonpaku1337 >
also one more thing, alpine doesnt see the sd, can it not hotplug orwhat
17:15
<
youmukonpaku1337 >
also
17:15
<
youmukonpaku1337 >
why the hell isnt sys mounted on /sys
17:15
<
youmukonpaku1337 >
alpine as in the rootfs i have booted through fel xf
17:15
<
youmukonpaku1337 >
xd
17:16
<
apritzel >
because someone needs to mount it there. Normally this is done by the init scripts
17:17
<
apritzel >
if you now shoehorn a normal rootfs into an initramfs, you probably cannot use the normal init scripts
17:19
<
youmukonpaku1337 >
wait cant i just mount sysfs on /sys
17:19
<
youmukonpaku1337 >
there we go
17:19
<
youmukonpaku1337 >
mounted
17:21
<
apritzel >
sure you can, but you also
*have* to, every time you boot it
17:21
<
apritzel >
same with proc
17:21
<
youmukonpaku1337 >
proc is mounted
17:21
<
youmukonpaku1337 >
apritzel: i used the simple init script made by smaeul :p
17:21
<
youmukonpaku1337 >
just missed sysfs
17:27
<
youmukonpaku1337 >
apritzel: also where do i put uboot xd
17:27
<
youmukonpaku1337 >
as in how do i install it
17:29
<
apritzel >
pick the right chapter
17:31
<
youmukonpaku1337 >
apritzel: so i assume i can write to the mmcblkXboot?
17:31
<
youmukonpaku1337 >
huh
17:31
<
apritzel >
that's what I would suggest
17:32
<
youmukonpaku1337 >
im not sure whether to use boot1 or boot0
17:32
<
apritzel >
be bold! just pick one ;-)
17:32
<
youmukonpaku1337 >
why not both :D
17:33
<
youmukonpaku1337 >
apritzel: also how can i wipe emmc and make one root partition
17:33
<
youmukonpaku1337 >
cause theres like 10
17:33
<
youmukonpaku1337 >
and idk how to use fdisk
17:33
<
apritzel >
then you would need to look that up ;-)
17:35
<
youmukonpaku1337 >
apritzel: can i just dd from devzero then make a new partition table with a single partition>
17:37
<
apritzel >
just use fdisk to remove all partitions, then create new one
17:45
<
youmukonpaku1337 >
apritzel: first sector 16 is ok?
17:47
<
youmukonpaku1337 >
i guess it is then
17:47
<
youmukonpaku1337 >
made a partition
17:47
<
youmukonpaku1337 >
lemme put stuff i need onto sd and see
17:50
apritzel has quit [Ping timeout: 480 seconds]
18:56
bauen1 has quit [Ping timeout: 480 seconds]
18:58
JohnDoe_71Rus has quit []
19:05
utsweetyfish has quit [Remote host closed the connection]
19:05
utsweetyfish has joined #linux-sunxi
19:12
apritzel has joined #linux-sunxi
19:25
<
youmukonpaku1337 >
apritzel: i instead extracted the rootfs from the image and am gonna put it into a normal image without offset :D
19:31
utsweetyfish has quit [Remote host closed the connection]
19:33
utsweetyfish has joined #linux-sunxi
19:53
<
youmukonpaku1337 >
apritzel: uhhh so i may have a problem
19:53
kuba2k2 has joined #linux-sunxi
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:5744: Corrupt filesystem
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1): ext4_dirty_inode:5948: inode #12: comm dd: mark_inode_dirty error
19:54
<
youmukonpaku1337 >
JBD2: Spotted dirty metadata buffer (dev = mmcblk0p1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:5744: Corrupt filesystem
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1): ext4_dirty_inode:5948: inode #12: comm dd: mark_inode_dirty error
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:5744: Corrupt filesystem
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1): ext4_dirty_inode:5948: inode #12: comm dd: mark_inode_dirty error
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:5744: Corrupt filesystem
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1): ext4_dirty_inode:5948: inode #12: comm dd: mark_inode_dirty error
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:5744: Corrupt filesystem
19:54
<
youmukonpaku1337 >
EXT4-fs error (device mmcblk0p1): ext4_dirty_inode:5948: inode #12: comm dd: mark_inode_dirty error
19:54
<
youmukonpaku1337 >
1120+0 records in
19:54
<
youmukonpaku1337 >
1120+0 records out
19:54
<
youmukonpaku1337 >
quite concerning
19:54
immibis has joined #linux-sunxi
19:58
warpme has joined #linux-sunxi
20:06
kuba2k2 has quit []
20:12
<
youmukonpaku1337 >
and now i cant get uboot nor alpine to see the sd card wtf
20:13
<
youmukonpaku1337 >
apritzel
20:13
<
youmukonpaku1337 >
=> mmc dev 0
20:13
<
youmukonpaku1337 >
Error enabling VMMC supply : 21504024
20:14
<
youmukonpaku1337 >
i reformatted it like twice already
20:34
<
youmukonpaku1337 >
apritzel: so uhh
20:36
<
apritzel >
for U-Boot to access the SD card you need to compile in REGULATOR_AXP and some I2C support
20:36
<
apritzel >
but it should work in Linux, have you tried it there?
20:36
<
youmukonpaku1337 >
apritzel: i have, and it worked before :p
20:37
<
youmukonpaku1337 >
as for linux, nothing in dmesg and no device appears
20:46
warpme has joined #linux-sunxi
20:48
<
youmukonpaku1337 >
apritzel: so uhh
20:49
bauen1 has joined #linux-sunxi
21:56
DarkNeutrino has quit [Read error: Connection reset by peer]
21:56
DarkNeutrino has joined #linux-sunxi
22:37
utsweetyfish has quit [Remote host closed the connection]
22:38
utsweetyfish has joined #linux-sunxi
22:50
utsweetyfish has quit [Remote host closed the connection]
22:51
utsweetyfish has joined #linux-sunxi
23:27
utsweetyfish has quit [Remote host closed the connection]
23:27
utsweetyfish has joined #linux-sunxi
23:52
utsweetyfish has quit [Remote host closed the connection]
23:53
utsweetyfish has joined #linux-sunxi
23:58
apritzel has quit [Ping timeout: 480 seconds]