Porteus

ncmprhnsbl wrote:

rchase wrote:... i'm wondering if it somehow transfers settings from the host(rc3)?

I used Rufus from Windows 10 on a system without an installed Porteus. Porteus' use of data from any installed copy should be better described and has undoubtedly caused very much confusion and many bug reports, but it is not the cause this time.

ok, probly not that then...
out of ideas for now...

Cinnamon x86_64
1) If right-click on desktop - Context Menu does not work
but in Linux Mint 18 Sarah Cinnamon is have this ability - look at this screenshot

2) If possible, not bad to add gnome-system-monitor in Cinnamon

3) If I clik on Start > Quit - I see this

Probably, this is due to nemo-data_3.0.3-1_all.xzm (I use in terminal poweroff or reboot comands)

4) If I try to rename file - I see effect of white font (difficult to read these white pixels)

8)

Bogomips, probably, this is due to nemo-data_3.0.3-1_all.xzm and you are opened a new bug - Linux Mint 18 Sarah Cinnamon is have icons in Context Menu, but Porteus 3.2 RC4 Cinnamon is not have these icons in Context Menu.

Hello all,

I am trying out a frugal install of Porteus 3.2 rc4 32-bit XFCE/MATE/Cinnamon on a Dell Dimension 2400 w/1GB RAM, but ethernet networking is not working. Ethernet works fine in my current Porteus 3.1 32-bit LXDE (one of neko's variants) and dmesg there includes the following:

...
[ 13.320261] ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x04, vendor 0x4243)
...
[ 13.538525] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
...
[ 13.573132] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:0f:1f:4c:fd:12
...

However, there is no mention of any ethernet in dmesg from Porteus 3.2 rc4, and ifconfig as root there shows only the lo loopback interface even though the b44 driver exists.

Any ideas on how to get ethernet running in v3.2 rc4?
My apologies if I'm being too much of a noob at this.

Hi Mythenadia.
Try this command in terminal to restart your demon of NetworkManager

Blaze wrote:Try this command in terminal to restart your demon of NetworkManager

Code: Select all

/etc/rc.d/rc.networkmanager restart

Thanks for the quick response.
Ran this in a root terminal, but still no ethernet.
Also tried manually entering my nic's MAC address in Edit Connections, but still no go.

ifconfig ethX up
where X = 0, 1, or 2 doesn't work either.

v3.2rc4 networking looks good on another computer here, and v3.1 works fine on all.

Just booted Porteus 3.2rc4 32-bit XFCE on my Panasonic CF-30 laptop and I'm getting no networking here as well even though both ethernet and wifi work fine in Porteus 3.1.

The 3.2rc4 XFCE desktop is also unusually sluggish.

Restarting networkmanager again makes no difference.

dmesg shows both eth0 and wlan0 in Porteus 3.1 but not in 3.2rc4.

Before all Thanks for your work !
I noticed a few things.

1) python seems not working. I've check on /var/log/packages file list but files are not present . I've resolved all dependencies using this packages (2 there were already, but they appeared broken)
dbus-python-1.2.4-x86_64-1.xzm,notify-python-0.1.1-x86_64-5.xzm,pycairo-1.10.0-x86_64-1.xzm,pycups-1.9.73-x86_64-1.xzm,pygobject3-3.18.2-x86_64-1.xzm,pygobject-2.28.6-x86_64-2.xzm,pygtk-2.24.0-x86_64-2.xzm,python-2.7.11-x86_64-2.xzm
2) alsamixer does not start. I've read that now is used pulseaudio. Is alsamixer necessary again ?
3) A strange thing happens to me with virtualbox. If I use bridged adapter network goed down. Using NAT all seems working fine.

Hello again after some time .... in times past I reported that 3G modems were not functional in Porteus, and the problem was resolved with the addition of usb_modeswitch and perhaps some other magic dust. Alas I now find that with the MATE rc2 candidate while the preconditions for connection via NM seem to be met, an actual connection can't be made. After some spinning of wheels NM announces a disconnection. I guess this is due to a failure to negotiate a modem connection and getting DNS from the service provider. Any chance of looking into this?

I have also seen this problem lately with the live slak from Mr Hameleers based on 14.2. We exchanged some emails on the topic and some changes were made in the user's membership of groups {eg added user to dialup) but alas the problem was not fixed. I have tried the MATE version and the KDE, but no 3G connection is possible. MATE seems to be trying to do the right thing, whereas KDE seems to lose the plot completely (as is often the case with KDE networking in my experience).

I would appreciate if you could look into this. Can send logs from failed connection attempts. There seem to be some missing wires in the DNS area is my best guess to date. There does seem to be some regression here since 3G was working in 3.1. And this may be a problm with Slackware too.

If you are talking about a usb 3G modem like a Pantech UML295 then it is because ModemManager broke in 14.1 and has continued in 14.2. You can fix the problem in 14.1 by down grading to the slackware 14.0 ModemManager, NetworkManager, and network-manager-applet. This was the only way I was able to move up to slackware 14.1. Unfortunately the fix did not work in 14.2 most likely due to the move to eudev. From what I can tell the modem is recognized by the system but when ModemManager fails to connect or receive an ipv6 response in disconnects the device. On slackware 14.2 I removed the ModemManager package to test and the device will stay connected but you are unable to access it. I guess I will have to stay with 14.1 until I can get a new modem which will work with the new ModemManager.

Blaze, to get the icons in your right click menu open settings, go to themes and enable show icons in menus.
Would post screenshot but not sure how.

i see LLVM libs are there and glx is working for radeon , thanks
this should be in 002-xorg rather than 003-desktop?

jmhoward56 wrote:Blaze, to get the icons in your right click menu open settings, go to themes and enable show icons in menus.

Themes > Settings
Just done it, thx.

@ jmhoward56 http://forum.porteus.org/viewtopic.php?f=81&t=5754