Porteus-v1.1rc2-x86_64 ready for testing
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Porteus-v1.1rc2-x86_64 ready for testing
Please read the release announcement for further details and post bugs and requests here. This is last release candidate before the official v1.1 release and things are looking quite stable.
As usual please road test and help out with any bug fixes where possible.
If you find a bug, please make sure you have booted to 'always fresh' mode and have no rogue files in your rootcopy folder. If the problem persists then post your question here and a team of highly trained monkeys will be dispatched to look at the problem.
As per usual we will need 'Beny the great' to produce some nvidia modules.
As usual please road test and help out with any bug fixes where possible.
If you find a bug, please make sure you have booted to 'always fresh' mode and have no rogue files in your rootcopy folder. If the problem persists then post your question here and a team of highly trained monkeys will be dispatched to look at the problem.
As per usual we will need 'Beny the great' to produce some nvidia modules.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
-
- White ninja
- Posts: 10
- Joined: 14 Jan 2011, 11:13
- Location: belgium
Re: Porteus-v1.1rc2-x86_64 ready for testing
I have the impression that the cheatcode "lxde" is no longer working...
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
rc2 is very strict about proper cheatcode syntax - 'autoexec=lxde' wont work anymore.
run `cat /proc/cmdline` and make sure you have "[space]lxde[space]" or "[space]lxde[end of line]".
check /boot/porteus.cfg for the rest of booting options (there are changes to "text mode" and "vesa mode" as well).
btw: i hope this is the last time when we mess up with cheats as it always causes some confusion...
run `cat /proc/cmdline` and make sure you have "[space]lxde[space]" or "[space]lxde[end of line]".
check /boot/porteus.cfg for the rest of booting options (there are changes to "text mode" and "vesa mode" as well).
btw: i hope this is the last time when we mess up with cheats as it always causes some confusion...
Please add [Solved] to your thread title if the solution was found.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Porteus-v1.1rc2-x86_64 ready for testing
Cheaters never prosper. I agree though, we need to stabilize the cheats and i think you have just about everything covered now.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Tonio
- Contributor
- Posts: 276
- Joined: 28 Dec 2010, 16:37
- Distribution: Slackware,porteus,FreeBSD,Slax
- Location: 127.0.0.1
Re: Porteus-v1.1rc2-x86_64 ready for testing
First of all, thank you for an rc2 edition of both versions. Testing 64 bit version, I startup in text mode and login as root and type startx get nice KDE. Fireup firefox and there is no connection I check network with
and there is no ip address. I remedy the situation with dhcpcd, is this a desired change not to pick up IP address at boot?
Running with copy2ram and so far no issues other than this issue. Will let you know on other machines. Thanks!
Code: Select all
# ifconfig -a
Code: Select all
root@porteus:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr d0:27:88:01:37:9c
inet6 addr: fe80::d227:88ff:fe01:379c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:357 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31210 (30.4 KiB) TX bytes:3526 (3.4 KiB)
Interrupt:41
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:184 errors:0 dropped:0 overruns:0 frame:0
TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13940 (13.6 KiB) TX bytes:13940 (13.6 KiB)
root@porteus:~# dhclient eth0
bash: dhclient: command not found
root@porteus:~# dhcpcd eth0
dhcpcd[2724]: version 5.2.12 starting
dhcpcd[2724]: eth0: broadcasting for a lease
dhcpcd[2724]: eth0: offered 10.155.132.215 from 10.155.132.10
dhcpcd[2724]: eth0: acknowledged 10.155.132.215 from 10.155.132.10
dhcpcd[2724]: eth0: checking for 10.155.132.215
dhcpcd[2724]: eth0: leased 10.155.132.215 for 691200 seconds
dhcpcd[2724]: forked to background, child pid 2748
root@porteus:~# uname -r
3.1.1-porteus
root@porteus:~# cat /etc/porteus-version
Porteus-v1.1
root@porteus:~#
Re: Porteus-v1.1rc2-x86_64 ready for testing
Thanks fanthom for rc2
I get an error unmount pendrive from Dolphin,
I use copy2ram cheatcode. When I try to "Safely Remove" porteus boot pendrive, Dolphin says " The Device is currently busy: Cannot unmount because file system on device is busy." I don't use pendrive anyway. But this error does'nt occur any of the other pendrive.
Cheers,
Posted after 1 hour 31 minute 47 seconds:
Copy2ram cheat code works correctly without vga-detect. And pendrive umounted after startup.
I get an error unmount pendrive from Dolphin,
I use copy2ram cheatcode. When I try to "Safely Remove" porteus boot pendrive, Dolphin says " The Device is currently busy: Cannot unmount because file system on device is busy." I don't use pendrive anyway. But this error does'nt occur any of the other pendrive.
Cheers,
Posted after 1 hour 31 minute 47 seconds:
Copy2ram cheat code works correctly without vga-detect. And pendrive umounted after startup.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Tonio
probably eth0 was not available yet when rc.inet1 performed (hope that i didn't send an udev to the background by mistake). please try once again on that PC and if error reoccurs try yo add 'ifconfig' command to the booting scripts just before rc.inet1 starts.
you should see if eth0 is available during next boot.
@oranus
looks like modules from /optional folder are not copied to RAM while they should. Tomorrow will have a look on linuxrc to be 100% sure and fix it, if it's really the case.
Thanks
EDIT:\\
@oranus
fixed now - i have forgotten to detach loop device while unmounting 001-core.xzm from /opt. must do the same for 'from_iso=' cheat....
thanks.
probably eth0 was not available yet when rc.inet1 performed (hope that i didn't send an udev to the background by mistake). please try once again on that PC and if error reoccurs try yo add 'ifconfig' command to the booting scripts just before rc.inet1 starts.
you should see if eth0 is available during next boot.
@oranus
looks like modules from /optional folder are not copied to RAM while they should. Tomorrow will have a look on linuxrc to be 100% sure and fix it, if it's really the case.
Thanks
EDIT:\\
@oranus
fixed now - i have forgotten to detach loop device while unmounting 001-core.xzm from /opt. must do the same for 'from_iso=' cheat....
thanks.
Please add [Solved] to your thread title if the solution was found.
- Tonio
- Contributor
- Posts: 276
- Joined: 28 Dec 2010, 16:37
- Distribution: Slackware,porteus,FreeBSD,Slax
- Location: 127.0.0.1
Re: Porteus-v1.1rc2-x86_64 ready for testing
Does not work again. I am using textmode + copy2ram added on then logging in as rootfanthom wrote:@Tonio
probably eth0 was not available yet when rc.inet1 performed (hope that i didn't send an udev to the background by mistake). please try once again on that PC and if error reoccurs try yo add 'ifconfig' command to the booting scripts just before rc.inet1 starts.
you should see if eth0 is available during next boot.
Code: Select all
root@porteus:~# uname -r
3.1.1-porteus
root@porteus:~# cat /etc/porteus-version
Porteus-v1.1
root@porteus:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr d0:27:88:01:37:9c
inet6 addr: fe80::d227:88ff:fe01:379c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:2 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4178 (4.0 KiB) TX bytes:3526 (3.4 KiB)
Interrupt:41 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8700 (8.4 KiB) TX bytes:8700 (8.4 KiB)
Code: Select all
root@porteus:~# dhcpcd eth0
dhcpcd[2778]: version 5.2.12 starting
dhcpcd[2778]: eth0: broadcasting for a lease
dhcpcd[2778]: eth0: offered 10.155.132.215 from 10.155.132.10
dhcpcd[2778]: eth0: acknowledged 10.155.132.215 from 10.155.132.10
dhcpcd[2778]: eth0: checking for 10.155.132.215
dhcpcd[2778]: eth0: leased 10.155.132.215 for 691200 seconds
dhcpcd[2778]: forked to background, child pid 2806
root@porteus:~#
EDIT:
Starting in text mode without copy2ram, eth0 gets ip address and connection works. However on another machine with different ip. Hope to get back with more later next week.
Code: Select all
root@porteus:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:67:6c:93:9d
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::230:67ff:fe6c:939d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1965 errors:0 dropped:0 overruns:0 frame:0
TX packets:1493 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2609243 (2.4 MiB) TX bytes:228073 (222.7 KiB)
Interrupt:43 Base address:0x4000
Last edited by Tonio on 23 Nov 2011, 16:18, edited 1 time in total.
Re: Porteus-v1.1rc2-x86_64 ready for testing
Hi fanthom,
On every release you make Virtualbox.xzm file on basic state. But for using Virtualbox we need "VirtualBox Extension Pack" especially for usb2.0. So I regenerate Virtualbox.xzm with extension pack. Could you post Virtualbox with extension pack?
Thanks
On every release you make Virtualbox.xzm file on basic state. But for using Virtualbox we need "VirtualBox Extension Pack" especially for usb2.0. So I regenerate Virtualbox.xzm with extension pack. Could you post Virtualbox with extension pack?
Thanks
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Tonio
try to modify /etc/rc.d/rc.inet1 as follows:
and check if eth0 interface is available when rc.inet1 operates. if yes then all should be ok. if no then you please try to add 'sleep 3' to original rc.inet1 before:
and see if that helps.
@oranus
as per our mchat conversation - we can't include ext pack i'm afraid as it's not GPL and requires to accept Oracle license.
@all
i have added latest nVidia driver (and legacy version) to both 32 and 64 bit repos.
thanks beny.
try to modify /etc/rc.d/rc.inet1 as follows:
Code: Select all
if [ "$1" = "start" -o "$1" = "" ]; then
echo "enabling dhcpcd on all available interfaces..."
ifconfig lo down 2>/dev/null
ifconfig lo 127.0.0.1 2>/dev/null
route add -net 127.0.0.0 netmask 255.0.0.0 lo 2>/dev/null
ifconfig eth0 up && ifconfig
sleep 1
ifconfig eth0 up && ifconfig
sleep 1
ifconfig eth0 up && ifconfig
sleep 1
ifconfig eth0 up && ifconfig
for x in `ls /sys/class/net | egrep -v 'sip|lo'`; do
/sbin/dhcpcd -L -t 0 $x >/dev/null 2>&1 &
done
fi
Code: Select all
for x in `ls /sys/class/net | egrep -v 'sip|lo'`; do
@oranus
as per our mchat conversation - we can't include ext pack i'm afraid as it's not GPL and requires to accept Oracle license.
@all
i have added latest nVidia driver (and legacy version) to both 32 and 64 bit repos.
thanks beny.
Please add [Solved] to your thread title if the solution was found.
Re: Porteus-v1.1rc2-x86_64 ready for testing
Some minor problems:
rpm2txz doesn't work in rc2 and works in rc1
lzm2xzm - unsquashfs3 not found
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
/etc/rc.d/rc.messagebus: line 18: 2425 Bus error /sbin/ldconfig
...
/etc/rc.d/rc.local: line 10: /usr/bin/syslog: No such file or directory
/sbin/installpkg: line 314: 7772 Bus error /sbin/ldconfig
rpm2txz doesn't work in rc2 and works in rc1
lzm2xzm - unsquashfs3 not found
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
/etc/rc.d/rc.messagebus: line 18: 2425 Bus error /sbin/ldconfig
...
/etc/rc.d/rc.local: line 10: /usr/bin/syslog: No such file or directory
/sbin/installpkg: line 314: 7772 Bus error /sbin/ldconfig
Suggestions/corrections/additions are always welcome.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Kriss
and works ok for me.
my advice: try always fresh + base modules only.
tested on http://rpm.pbone.net/index.php3/stat/4/ ... 6.rpm.htmlrpm2txz doesn't work in rc2 and works in rc1
and works ok for me.
64bit edition does not support 32bit lzm conversion (i see no point for that). i have added a warning to lzm2xzm script - thanks.lzm2xzm - unsquashfs3 not found
something is really messed up with your modules.Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
/etc/rc.d/rc.messagebus: line 18: 2425 Bus error /sbin/ldconfig
again - must be your installation fault as rc.local comes always empty in Porteus/etc/rc.d/rc.local: line 10: /usr/bin/syslog: No such file or directory
my advice: try always fresh + base modules only.
Please add [Solved] to your thread title if the solution was found.
Re: Porteus-v1.1rc2-x86_64 ready for testing
Sorry. It's indeed problem with my changes.
Suggestions/corrections/additions are always welcome.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: Porteus-v1.1rc2-x86_64 ready for testing
32bit will lose support for squashfs3 in next version so lzm2xzm can be dropped then. Perhaps leave it for version2 as a few other scripts will need to be cleaned a little (activate scripts).
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
Re: Porteus-v1.1rc2-x86_64 ready for testing
I don't see power profiles on clean system. Even ones I've created. And can't assign them to events On AC/On battery.
Suggestions/corrections/additions are always welcome.