FAA minimal Porteus question

Non release banter
quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

FAA minimal Porteus question

Post#1 by quotaholic » 11 May 2015, 23:22

Trying to build a minimal environment that can work on seriously old computers. That and an uupcoming Ras-Pi-II project.

So I have Kernel, base, xorg, devel and thats it in /base
I build JWM and load that module for a window manager.

xwmconfig see's JWM and offers to do its xinitrc.jwm trick.

On reboot I get odd behavior with a flashing xterm window that is titled "Login".
Closing that window causes the wm to close and go back to console.

Can I assume that I do not have a login manager and that one is needed? If so tips on setup?

Thanks in advance
quotaholic

User avatar
brokenman
Site Admin
Site Admin
Posts: 5576
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: minimal Porteus question

Post#2 by brokenman » 12 May 2015, 01:06

I am working on a thin client version of Porteus. Super lightweight. Also bought a Pi and will start compiling for it when I get some time. Best way to test is to start with the base and xorg module. Then add openbox. Boot to init 3 and then type in: startx 2>/tmp/out

You will of course need something usable in your xinitrc file like: exec openbox-session

If it fails you can read the logs at /tmp/out and also /var/log/Xorg.log

Good luck
How do i become super user?
Wear your underpants on the outside and put on a cape.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#3 by quotaholic » 12 May 2015, 02:11

Thanks for the tip! Super useful.

Any tips for error two on the installer?

Here is my debug.... installing to sde
daryl@Vostro /mnt/sde1/boot $ cat debug.txt
device: /dev/sde
partition: /dev/sde1
partition number: 1
partition mount point: /mnt/sde1
installation path: /mnt/sde1/boot
subfolder:
filesystem: ext4
bootloader: lilo
error code: 2
system: Vostro 4.0.0-sabayon x86_64
mount details: /dev/sde1 /mnt/sde1 ext4 rw,relatime,data=ordered 0 0
full partition scheme:
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 138.6 MiB, 145352704 bytes, 283892 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2094ca70

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 1324621511 1324414664 631.5G 7 HPFS/NTFS/exFAT
/dev/sda3 1324621824 3907028991 2582407168 1.2T f W95 Ext'd (LBA)
/dev/sda5 1324621825 1328816475 4194651 2G 82 Linux swap / Solaris
/dev/sda6 1328818176 1412708351 83890176 40G 83 Linux
/dev/sda7 1412710400 3907008511 2494298112 1.2T 83 Linux





Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000a4397

Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 3907024064 3907024002 1.8T 7 HPFS/NTFS/exFAT



Disk /dev/sdc: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd2beaba6

Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 63 2930273500 2930273438 1.4T 7 HPFS/NTFS/exFAT


Disk /dev/sde: 14.6 GiB, 15610576896 bytes, 30489408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C61D8EF0-B795-4C4F-B012-4B6974CCF35C

Device Start End Sectors Size Type
/dev/sde1 2048 30474239 30472192 14.5G EFI System

User avatar
fanthom
Site Admin
Site Admin
Posts: 4621
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: minimal Porteus question

Post#4 by fanthom » 12 May 2015, 07:16

Code: Select all

Disk /dev/sde: 14.6 GiB, 15610576896 bytes, 30489408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
GPT partition scheme is not supported by the installer. you have to repartition to DOS.
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#5 by quotaholic » 13 May 2015, 17:12

Thanks, tried GPT after a number of fails on dos tables. Most windows "linux to usb" utilities seem to be a workaround.

I would be super excited for a minimal Porteus. More so for a Rasberry PI edition. Hoping to grab a version two in a few weeks.

I cant afford to contribute at the moment but if I can participate in either effort please let me know how.

Thanks and thumbs-up!

quotaholic

User avatar
fanthom
Site Admin
Site Admin
Posts: 4621
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: minimal Porteus question

Post#6 by fanthom » 14 May 2015, 08:43

maybe i was wrong about GPT partitions - i have never run the installer against them.
anyway - its a know issue that when device is mounted by udisks2 helpers then installer wont work. please mount device manually and try again.
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#7 by quotaholic » 14 May 2015, 18:42

Switched away from Sabayon last night in favor of Slackware-current. Let me try again and report back after I get home. I had tried this in /var/run/media.... as well as hand mounting on /mnt/sdd1 from /dev/sdd1. Ironically that trick I tried with liloinst.sh only worked once as well on that OS. Did not manually mount /proc in tests.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: minimal Porteus question

Post#8 by Bogomips » 15 May 2015, 16:43

quotaholic wrote:Trying to build a minimal environment that can work on seriously old computers. That and an uupcoming Ras-Pi-II project.
Couldn't work out why the last post was timestamped ahead of time, until realised looking at date of joining :)
Upon 4 Year Forum Anniversary, methinksImage are in Order.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#9 by quotaholic » 15 May 2015, 19:53

Time does fly. Congrats Porteus! Good eyes!

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#10 by quotaholic » 23 May 2015, 20:58

Has anyone here been successful in getting DirectFB to work on Porteus?

User avatar
wread
Module Guard
Module Guard
Posts: 1098
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: minimal Porteus question

Post#11 by wread » 24 May 2015, 14:02

Yes, I have it working :)
here is the link

Enjoy! 8)
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#12 by quotaholic » 24 May 2015, 16:52

Many thanks wread! Do you mind If I ask a few basic questions?

I have a 32 bit version that I build from slackpkg -> txz2xzm. How does one implement?

I notice some programs add to the menus and one that looks like debugging, ddd. I am hoping to save some install space with this.

Will this work as a replacement for the xorg.xzm? OR is it meant to drop in to x and replace only the xserver? Have a cute JWM based build that I am working on.

Thanks again!

quotaholic

User avatar
wread
Module Guard
Module Guard
Posts: 1098
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: minimal Porteus question

Post#13 by wread » 24 May 2015, 17:34

Hi, quotaholic!
DirectFB seems to act directly on the drivers of your computer, instead of playing the client-server game, similar as with Windows.

There are many new versions of graphics handling, as X cannot handle threads in an elegant way. Xcb is the answer to this problem, and qt5 is going this way (kde5 is following it apparently).

Another proposal is Wayland, I think similar to DirectFB, but still waiting for deeper development..

I just downloaded the last version of DirectFB and tested a couple of programs on 64 bits, compiled on Porteus.
You can recompile the sources (the 64 executables are in the tar archive) for 32 bits, they work straightforward with the command line included.

Enjoy!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
fanthom
Site Admin
Site Admin
Posts: 4621
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: minimal Porteus question

Post#14 by fanthom » 24 May 2015, 17:52

@quotaholic
please check if kernel has framebuffer driver for your GPU as you may get better performance comparing to plain VESA. if you are running KMS enabled intel/nvidia/radeon driver then do not do anything (best performance).
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: minimal Porteus question

Post#15 by quotaholic » 24 May 2015, 18:40

Thanks guys.

Heh...
My gpu is an AMD Geode GX1. I have 256mb of ram to load Portues and windowing system in to and 400mhz of cpu. Circa 1997.
This hardware pretty much excludes weyland as compositing will not work well. Running a user contributed e16.xzm with translucency was even a bit hard. QT is simply too heavy for the hardware as well. That and QT is not a small library by any means. Using JWM as window manager in order to try to avoid heavy libraries. I have a 500mb hard drive to work with / within.

Dont get me wrong, I am not doing this for fun. This is an obligatory build that I am working on.
I think that weyland is going to be the future and especially on an embedded approach. e17 without compositing effects works well on the hardware but e18 with partial weyland integration almost made it unusable, even with compositing disabled. That being said with nvidia driver and e18 on my slackware desktop is a recipe for a light weight speedy experience with great effects(compositing enabled). As it is, booting to jwm desktop on target 400mhz hardware takes over 7.5 minutes from pressing the power button. It's fairly usable once it loads despite long application start times. 4 of the seven minutes are spent waiting for x to load after the login prompt shows. Using this as my xorg: http://webdt.org/forum/viewtopic.php?f=3&t=334#p1836 with two changes: no busid:(commented that and any penmount references) and vesa as driver. Geode driver fails to associate well and gets skipped by x. Handling the touchscreen via an rc.local file which moprobes penmount and then uses inputattach (from debain repo) to send /dev/ttyS0 to /dev/input/event3. Gpm from slackware should be in the "pasture". No way to handle newer serial or combo multitouch serial / usb touchscreens (inputattach -pmm1)

That being said this is good practice for my next project which will involve Porteus and a Rasberry PI2. I am hoping to utilize a small set of libraries on the PI2 as well. This is where my interest in DirectFb comes from. I dont need x forwarded over the network or the other features that a full x stack offers.

As it sits I have a 235mb iso with 05-devel, kernel, core, xorg, opera, working blueman, jwm, xfe, utils to get a serial touchscreen working on gpm, xinput_calibrator. If directfb could help save real estate and eliminate xorg.xzm I want to know how.

@Fanthom, I believe I do as I am using stock 3.1 kernel however if it turns out that I do not it would be easy to implement thanks to that wonderful "Compilation of custom kernel" document that Porteus provides in the tutorials. I'll try video=lxfb:800x600-16@60 on an upcoming reboot to see if the fb gets forced.

So back to my last question. Say I hit build.porteus.org and make a minimal iso with base and kernel. Add in xzm for directfb, and add Xcb. What commands to I use to start a graphic system with directfb? Any tips on the directfbrc or links would be greatly appreciated too. Mailing lists for directfb seem to skip over the "how to start" and jump to the "how to remedy". I'll happily rebuild a kernel and share with the needed options if needed. This holiday weekend is perfect for such a project.

quotaholic

:Yahoo!: Happy Holiday Weekend All!

Post Reply