Porteus-v1.1rc2-x86_64 ready for testing
Re: Porteus-v1.1rc2-x86_64 ready for testing
@fanthom
Yes, it was because of vga-detect.
Here's the results for clean rc2:
vga-detect + optional/nVidia-*.xzm = mounted, can't unmount
vga-detect + empty optional directory = mounted, can't unmount
load=nVidia-*.xzm = unmounted, everything's fine
Here's output with loaded nVidia module (but most likely I was mistaken, there's only one driver loaded, but two modules):
lspci -v | grep 'VGA compatible' -A20 | grep Kernel
Kernel driver in use: nvidia
Kernel modules: nvidia, nouveau
/var/log/Xorg0.log
/var/log/messages
Yes, it was because of vga-detect.
Here's the results for clean rc2:
vga-detect + optional/nVidia-*.xzm = mounted, can't unmount
vga-detect + empty optional directory = mounted, can't unmount
load=nVidia-*.xzm = unmounted, everything's fine
Here's output with loaded nVidia module (but most likely I was mistaken, there's only one driver loaded, but two modules):
lspci -v | grep 'VGA compatible' -A20 | grep Kernel
Kernel driver in use: nvidia
Kernel modules: nvidia, nouveau
/var/log/Xorg0.log
/var/log/messages
Suggestions/corrections/additions are always welcome.
- fanthom
- Moderator Team
- Posts: 5591
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
everything is fine so as this bug is fixed already.Yes, it was because of vga-detect.
'lspci -k' shows which drivers are available in the system for certain chipsets and not which ones are loaded. all is fine in your case: nVidia binary controls X11 session. no worries at all.but most likely I was mistaken, there's only one driver loaded, but two modules
Please add [Solved] to your thread title if the solution was found.
Re: Porteus-v1.1rc2-x86_64 ready for testing
Hamza,
Anyway with this lzm is little thing which have no bothering with
That's I meant. L)We haven't the same version of squashfs betwwen slax remix and Porteus.
Anyway with this lzm is little thing which have no bothering with
- 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
@Hamza
I have seen your response since several days and I am trying to understand what you have written. I am confused
I have not had this problem before with any Linux based OS I have used. I have used Slackware and it uses dhcpcd to connect and it obtained an IP directly, I have used Fedora and it also got IP automagically, Slax and porteus also worked without hiccups. For some reason or another, maybe the ipv6 thingy is causing the problem? I have not asked network administrators at school what the deal is, but on these machines some have Fedora, one has Fedora & Slackware and another has FreeBSD and all get the connection started automagically. When I used copy2ram option in either 32 bit version or 64 bit Porteus rc candidate, I don't get working connection. If I use
# dhcpcd eth0
then I can connect, so something is messing up the connection, but I don't know what it is
It could the ipv6 settings, but I don't know how to troubleshoot it. Should I run
# ifconifg -a
on Fedora, Slackware, then on porteus RC2 and see and compare the differences to better understand it?
Sorry for taking a while to respond back to you and others who might have been interested in this issue. At home, if I boot Porteus, I get automagically connected
At school on some machines I don't and I will have to do above suggestion to see if I can find out what is going on 
Thanks Hamza for your input.
I have seen your response since several days and I am trying to understand what you have written. I am confused

I have not had this problem before with any Linux based OS I have used. I have used Slackware and it uses dhcpcd to connect and it obtained an IP directly, I have used Fedora and it also got IP automagically, Slax and porteus also worked without hiccups. For some reason or another, maybe the ipv6 thingy is causing the problem? I have not asked network administrators at school what the deal is, but on these machines some have Fedora, one has Fedora & Slackware and another has FreeBSD and all get the connection started automagically. When I used copy2ram option in either 32 bit version or 64 bit Porteus rc candidate, I don't get working connection. If I use
# dhcpcd eth0
then I can connect, so something is messing up the connection, but I don't know what it is

# ifconifg -a
on Fedora, Slackware, then on porteus RC2 and see and compare the differences to better understand it?
Sorry for taking a while to respond back to you and others who might have been interested in this issue. At home, if I boot Porteus, I get automagically connected


Thanks Hamza for your input.
- fanthom
- Moderator Team
- Posts: 5591
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Tonio
edited your post above as per forum rules: "no quote pyramids".
your issue seems to be time related (dhcpcd operates succesfully when booting finishes and you are logged in) and rather not ipv6. did you try my advices which i posted before:
http://porteus.org/forum/viewtopic.php?f=53&t=884#p6839
?
edited your post above as per forum rules: "no quote pyramids".
your issue seems to be time related (dhcpcd operates succesfully when booting finishes and you are logged in) and rather not ipv6. did you try my advices which i posted before:
http://porteus.org/forum/viewtopic.php?f=53&t=884#p6839
?
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
I am running from livecd and not from usb, so I did not apply your advicefanthom wrote:@Tonio
edited your post above as per forum rules: "no quote pyramids".
your issue seems to be time related (dhcpcd operates succesfully when booting finishes and you are logged in) and rather not ipv6. did you try my advices which i posted before:
http://porteus.org/forum/viewtopic.php?f=53&t=884#p6839
?

output of ifconfig from FreeBSD
Code: Select all
e213-amd64-1# ifconfig -a
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>
ether 00:21:97:ef:40:2f
inet 10.155.132.107 netmask 0xfffffc00 broadcast 10.155.135.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
- fanthom
- Moderator Team
- Posts: 5591
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
you could use 'rootcopy=' cheatcode to load something from hd while still booting from cd.I am running from livecd and not from usb, so I did not apply your adviceI did see it, but I would need to remaster the cd with the changes and see if that fixes it?
Please add [Solved] to your thread title if the solution was found.
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Tonio,
I hope you understand almost of my answer..too many technical words
Thanks.
I hope you understand almost of my answer..too many technical words

Thanks.
NjVFQzY2Rg==
- 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
Yes! I am starting to pick it up a little. Porteus did get an ip, but it was in ipv6 format which the network at work does not pick upHamza wrote:@Tonio,
I hope you understand almost of my answer..too many technical words![]()
Thanks.


What is strange is that Porteus versions 1.0, and v0.9 pick up an ipv4 automagically and the rc1/rc2 did not



Re: Porteus-v1.1rc2-x86_64 ready for testing
@Tonio,
This should be fixed in dhcpd config file.We have to ask fanthom and brokenman to fix this in Porteus.
This should be fixed in dhcpd config file.We have to ask fanthom and brokenman to fix this in Porteus.
NjVFQzY2Rg==
- Ahau
- King of Docs
- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Re: Porteus-v1.1rc2-x86_64 ready for testing
One minor fix --
please add a linebreak at the end of 001-core.xzm/etc/ld.so.conf. As it is now, if a script echoes a new line to this file, it will be appended to the last line of text, and mess things up.
Thanks!
please add a linebreak at the end of 001-core.xzm/etc/ld.so.conf. As it is now, if a script echoes a new line to this file, it will be appended to the last line of text, and mess things up.
Thanks!
Please take a look at our online documentation, here. Suggestions are welcome!
Re: Porteus-v1.1rc2-x86_64 ready for testing
Code: Select all
echo "\n"; echo "YOUR_LINE"; echo "\n"
NjVFQzY2Rg==
- Ahau
- King of Docs
- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Re: Porteus-v1.1rc2-x86_64 ready for testing
Yes, but most doinst.sh scripts simply use:
echo "/usr/lib/subdir" >> /etc/ld.so.conf && ldcondfig
And this would result in something like
"usr/lib/subdir1/usr/lib/subir2" for the final line, unless another linebreak is added.
echo "/usr/lib/subdir" >> /etc/ld.so.conf && ldcondfig
And this would result in something like
"usr/lib/subdir1/usr/lib/subir2" for the final line, unless another linebreak is added.
Please take a look at our online documentation, here. Suggestions are welcome!
Re: Porteus-v1.1rc2-x86_64 ready for testing
Code: Select all
echo "/usr/bin/file\n/usr/bin/file2";
NjVFQzY2Rg==
- fanthom
- Moderator Team
- Posts: 5591
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: Porteus-v1.1rc2-x86_64 ready for testing
@Ahau
done - thanks.
done - thanks.
Please add [Solved] to your thread title if the solution was found.