raja wrote: ↑12 Apr 2019, 19:36
Booted ISO. Looks okay.
Takes 20 seconds to Desktop. May be I will remove some packages to cut down time and memory use.
For sure, everything inside Modules are extras, if you try an Always fresh boot it became a fresh Porteus 4.0 with a Kernel 5.0.7 without Modules, BTW Kernel-firmware is there to support extra firmware that help in some certain circumstances, so you could remove it without problem
Yours is the first build where I could connect to my Phone via Bluetooth and transfer files. Blueman and Bluez packages alone not enough for Porteus-4.0.
Probably Porteus developers didn't consider to add Blueman to keep a very small ISO, but it is not our case
Since you have included many packages/scripts, "dmesg" shows lots of REISERFS errors.
Code: Select all
4.369846] REISERFS warning (device loop20): sh-2006 read_super_block: bread failed (dev loop20, block 16, size 4096)
[ 4.692036] REISERFS warning (device loop23): sh-2006 read_super_block: bread failed (dev loop23, block 16, size 4096)
[ 4.987070] REISERFS warning (device loop26): sh-2006 read_super_block: bread failed (dev loop26, block 16, size 4096)
[ 5.084062] REISERFS warning (device loop27): sh-2006 read_super_block: bread failed (dev loop27, block 16, size 4096)
[ 5.184138] REISERFS warning (device loop28): sh-2006 read_super_block: bread failed (dev loop28, block 16, size 4096)
[ 5.491056] REISERFS warning (device loop31): sh-2006 read_super_block: bread failed (dev loop31, block 16, size 4096)
[ 6.135021] REISERFS warning (device loop37): sh-2006 read_super_block: bread failed (dev loop37, block 16, size 4096)
[ 6.573915] REISERFS warning (device loop41): sh-2006 read_super_block: bread failed (dev loop41, block 16, size 4096)
[ 7.866776] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 2, size 4096)
[ 7.866784] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 16, size 4096)
[ 8.087845] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 2, size 4096)
[ 8.087852] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 16, size 4096)
I am not sure about it, but looks like something fail with the hard-drive that have a reiserfs, maybe you could try to open and Terminal,
Code: Select all
su
type your password, then
umount /dev/sdaX
reiserfsck --check /dev/sdaX
check whats display , then
reiserfsck --fix-fixable /dev/sdaX
X is the partition number
But I am certainly it is not cause of the O.S , maybe is your filesystem
When you activate new xzm modules, application is not listed in menu, however program runs through 'run'.
For some reason its not listening immediately to menu , my theory is because openbox menu is loading an old xml generated file, anyway you can , open Run 'it is going to open xfce4-appfinder and every new loaded module is going to be there'
Since Windows 10 sets local time and Linux sets UTC time, there will be a problem while switching. I leave UTC time without setting zone, as it matches local time or in some builds, I copy zone information to /etc. I even tried ntp.
Well done, and glad that you find a solution.
With 3 /4 tabs in Browser, memory use touches nearly 2MB. My system got only 4MB stick.
I am not sure about what you mean. but i have 7 tabs opened and it is taking 1.27GB of space in my memory with another stuff opened, in any case you should use your favorite browser, the one included in modules is to have a browser out of the box and something that I considered that deserve to take a look.
But, build is stable and runs smoothly.
Thanks
I wish its a good experience with Openbox
I need a help which I was asking neko a couple of times. Since you too are using neko's initrd, systemd, tell me where is the reference to FOLDER an variable listed in regular porteus in "linuxrc" file.
Its listed to porteus as always I just added SGN_ID=kernel-v5.0.7-1 in my initrd/init_conf to load kernel-v5.0.7-1-x86_64.cfg, everything still default as neko build Kernel 5.0.7
Both grub and syslinux can not find cfg file in porteus folder if you store porteus direcory in say ignis. "from" cheatcode not used in grub. "from=/mnt/sdax/ignis/porteus" fails to boot, if set in cfg file..
Really you dont need to load porteus.cfg for excample this is my grub setting to load my O.S
Code: Select all
set root='(hd0,X)'
linux /boot/syslinux/vmlinuz initrd=/boot/syslinux/initrd.xz changes=/porteus
initrd /boot/syslinux/initrd.xz
When X is the partition number
In regular porteus distribution, I edit linuxrc file ""FOLDER=/porteus-4.0/porteus and they boot without any problem. In one partition I have 6 distributions, with different directory names and they all boot.
I face problem with yours and nekos. I added a line FOLDER =*** to
init_conf file, before sgn line. No use. Should I do somewhere in /lib64/systemd/systemd?
PleaseClarify. Thanks