MX Linux Phone?

Message
Author
SwampRabbit
Posts: 3602
Joined: Tue Jun 14, 2016 2:02 pm

Re: MX Linux Phone?

#11 Post by SwampRabbit »

antiX-Dave wrote: Sun Aug 02, 2020 1:24 pm There is an xfce recipe for mobian on the pinephone (as well as others).
EX: https://gitlab.com/rrico542/mobian-x-recipes
Prebuilt images are/were available via rico but I have not looked recently.
I was considering modifying the openbox recipe and trying to make a custom one that does away with systemd and instead works with runit (with sysv as a fallback if the runit build did not work) but have not found the time to do so.
Thanks for sharing that!

Question is, what kind of effort would come of having to built and maintain another version off of a different base?

Could we do the same thing off the Debian base but pull things from Mobian if needed?
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.

antiX-Dave
Developer
Posts: 372
Joined: Mon Apr 16, 2012 4:51 pm

Re: MX Linux Phone?

#12 Post by antiX-Dave »

SwampRabbit wrote: Sun Aug 02, 2020 1:34 pm
Thanks for sharing that!

Question is, what kind of effort would come of having to built and maintain another version off of a different base?

Could we do the same thing off the Debian base but pull things from Mobian if needed?
1. A considerable amount would be needed. Especially if you do not have the appropriate hardware from my experience, however I have just started in the arm department.

2. Mobian is debian... just the mobile version from what I perceived. It used to be sort of abandoned in the main debian wiki IIRC. (Edit: I may be incorrect in this according to here https://wiki.debian.org/PinePhone)
They have a separate repository, mostly for Pine Phone specific items / tweaks as far as I know. The goal is to push everything upstream and move toward the normal debian repo/system. From what I can tell, the difficulty is that most of the current Debian packages are set in such a way where they are mostly for "computer" systems and not so much "mobile/phone" as well as "computer" systems. So the seperate repository is used till the changes can be made in the official debian repo. I am not 100% on this though. Maybe the best is to consult on their matrix chat.

The debian repository in use is bullseye, then the mobian is repo.mobian-project.org

So, yes in theory the same could be done as MX/antiX on arm as already done for i386/amd64. It just needs someone with time and hardware to start taking on the project I suppose. Clearly though it will be quite rough compared to the current versions.

inxi output if it helps.

Code: Select all

System:    Kernel: 5.7-pinephone aarch64 bits: 64 compiler: gcc v: 9.3.0 
           parameters: console=ttyS0,115200 no_console_suspend panic=10 consoleblank=0 loglevel=7 root=/dev/mmcblk2p2 rw 
           splash plymouth.ignore-serial-consoles vt.global_cursor_default=0 
           Console: tty 0 Distro: Debian GNU/Linux bullseye/sid 
Machine:   Type: ARM Device System: Pine64 PinePhone Braveheart (1.1) details: N/A serial: <filter> 
Battery:   ID-1: axp20x-battery charge: 32% condition: N/A volts: 3.9/2.9 model: N/A type: N/A serial: N/A status: Charging 
CPU:       Topology: Quad Core model: N/A variant: cortex-a53 bits: 64 type: MCP arch: ARMv8 family: 8 model-id: N/A 
           stepping: 4 microcode: N/A 
           features: Use -f option to see features bogomips: 0 
           Speed: 480 MHz min/max: 480/1152 MHz Core speeds (MHz): 1: 480 2: 480 3: 480 4: 480 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: sun50i-a64-mali driver: lima v: kernel bus ID: N/A chip ID: allwinner:1c40000 
           Device-2: sun50i-a64-dw-hdmi driver: sun8i_dw_hdmi v: N/A bus ID: N/A chip ID: allwinner:1ee0000 
           Device-3: sun50i-a64-display-engine driver: sun4i_drm v: N/A bus ID: N/A chip ID: allwinner:display-engine 
           Display: server: No display server data found. Headless machine? tty: 171x47 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: sun50i-a64-dw-hdmi driver: sun8i_dw_hdmi bus ID: N/A chip ID: allwinner:1ee0000 
           Device-2: simple-audio-card driver: N/A bus ID: N/A chip ID: simple-audio-card:hdmi-sound 
           Device-3: simple-audio-card driver: asoc_simple_card bus ID: N/A chip ID: simple-audio-card:sound 
           Sound Server: ALSA v: k5.7-pinephone 
Network:   Device-1: regulator-fixed driver: reg_fixed_voltage v: N/A port: N/A bus ID: N/A chip ID: regulator-fixed:vbat-wifi 
           Device-2: sun50i-a64-emac driver: N/A port: N/A bus ID: N/A chip ID: allwinner:soc 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: wwan0 state: unknown mac: N/A 
Drives:    Local Storage: total: 22.08 GiB used: 4.42 GiB (20.0%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/mmcblk0 model: SU08G size: 7.40 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
           scheme: MBR 
           ID-2: /dev/mmcblk2 model: N/A size: 14.68 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 0x8 
           scheme: MBR 
Partition: ID-1: / raw size: 14.56 GiB size: 14.27 GiB (98.03%) used: 4.36 GiB (30.6%) fs: ext4 block size: 4096 B 
           dev: /dev/mmcblk2p2 
           ID-2: /boot raw size: 121.1 MiB size: 113.3 MiB (93.53%) used: 47.6 MiB (42.0%) fs: ext4 block size: 1024 B 
           dev: /dev/mmcblk2p1 
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 1.91 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/mmcblk0p2 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Repos:     Packages: apt: 1173 lib: 716 flatpak: 0 
           Active apt repos in: /etc/apt/sources.list 
           1: deb http://deb.debian.org/debian bullseye main
           Active apt repos in: /etc/apt/sources.list.d/extrepo_mobian.sources 
           1: deb deb-src [arch=amd64 arm64 armhf] http://repo.mobian-project.org/ mobian main non-free
Info:      Processes: 177 Uptime: 5h 22m Memory: 1.88 GiB used: 615.7 MiB (31.9%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: N/A Shell: Bash v: 5.0.16 running in: tty 0 (SSH) inxi: 3.1.05 

heywoodidaho
Posts: 12
Joined: Tue Jul 21, 2020 4:53 pm

Re: MX Linux Phone?

#13 Post by heywoodidaho »

I'll check out mobian as soon as I complete the hardest part. Getting the thing in my hands.

Post Reply

Return to “General”