Porteus-1.2 feedback

[Ahau]

I'm not sure why nVidia is failing to load for you -- usually this is because the nVidia driver wasn't set up against the right kernel version. You could try manually installing the nVidia driver (download the driver from the nvidia website, log in to text mode, extract the downloaded file, and run the startup script -- you can then use 'changes-time' to create a module) to make sure.

Now that you've narrowed it down to kernel and/or nvidia, I found some more information that seems to match your symptoms:

https://bbs.archlinux.org/viewtopic.php?id=143545

It seems like this is a conflict issue between kernel 3.4 and nvidia 302, with a fix coming from nvidia (already in some testing packages).

[Rava]

I'm not sure why nVidia is failing to load for you -- usually this is because the nVidia driver wasn't set up against the right kernel version. You could try manually installing the nVidia driver (download the driver from the nvidia website, log in to text mode, extract the downloaded file, and run the startup script -- you can then use 'changes-time' to create a module) to make sure.

I have a running 1.2rc1, and that uses that very nVidia xzm from beny...

md5sums of my currently normal running 1.2rc1:

Code: Select all

95cca9626a27758a9bdcd5202ef73f67  [...]/boot/initrd.xz_Porteus_1.2_rc1_x86_64
f8c4a5781fbb8ffe9d26e642f8db9645  [...]/boot/vmlinuz_Porteus_1.2_rc1_x86_64
151a01c6c605235ef1d6add28477bd4a [...]/porteus/base/000-kernel.xzm
fd0d868168582ffeaaaa2cdc494d622f  [...]/porteus/base/010-nVidia-295.20-porteus-v1.2-rc1-x86_64-1beny.xzm

As you can see, the md5sums match perfectly with my "mixed" test Porteus... As I understand it, my 010-nVidia module just has to fit with vmlinuz, right?

Now that you've narrowed it down to kernel and/or nvidia, I found some more information that seems to match your symptoms:

https://bbs.archlinux.org/viewtopic.php?id=143545

It seems like this is a conflict issue between kernel 3.4 and nvidia 302, with a fix coming from nvidia (already in some testing packages).

Yup, seems indeed that this is the reason why it won't work..
And according to that forum, nvidia-295.53-2 should work...

I am not able to access the mentioned nv forum on
http://www.nvnews.net/vbulletin/showthread.php?t=179956
All I get is a "Your administrator has required a password to access this forum. Please enter this password now."
Since when do you need a password to just read in a forum... O___o

Verfasst after 20 hours 59 minutes 41 second:
Since nVidia gave me only the 295.59, I created a 010-nVidia_295.59_1.2_x86_64_Rava.xzm ... but it also has the "screen stays black after resume" error..

I still could upload it when anyone is interested... but when it asked me

Code: Select all

Install NVIDIA's 32-bit compatibility OpenGL libraries?

I replied "NO", so just the 64 bit libraries.

Aside from the suspend/resume it seems to work okay, though...

Is there a trick to see which Linux nVidia drivers there are for downloading from the nvidia site and NOT using that menu that decides for us what we should download?

[smiley]

Remix's ( ah those were the days 8)
Porteus
slitaz
tiny core

luvs compact, portable especially modulars

[Sagittarius]

@ Ahau, I also have the same problem with Retroval that secipolla mentioned: I downloaded the module and it reported that it was correctly activated but it made no difference to the sound.

[Ahau]

@Sagittarius,

If you are using saved changes or have not rebooted, then this is probably because the ~/.retrovolrc config file has not been refreshed--sorry for not mentioning this in the original instructions for the patch. Please try to remove this file:

Code: Select all

rm ~/.retrovolrc

then, log out of xfce and log back in. If it's still not working, try rebooting, and if it's not working after that, please give me the output of:

amixer controls

And we'll see what I can do for you

@Rava,

It took some hunting, but here's nvidia's archive:
64-bit: http://www.nvidia.com/object/linux_amd6 ... chive.html
32-bit: http://www.nvidia.com/object/linux_display_archive.html

[Hamza]

I am not able to access the mentioned nv forum on
http://www.nvnews.net/vbulletin/showthread.php?t=179956
All I get is a "Your administrator has required a password to access this forum. Please enter this password now."

The forum's administrator has closed the public access.

[Sagittarius]

@Sagittarius,

If you are using saved changes or have not rebooted, then this is probably because the ~/.retrovolrc config file has not been refreshed--sorry for not mentioning this in the original instructions for the patch. Please try to remove this file:

Code: Select all

rm ~/.retrovolrc

then, log out of xfce and log back in. If it's still not working, try rebooting, and if it's not working after that, please give me the output of:

amixer controls

And we'll see what I can do for you

Hi Ahau I rebooted and all is now OK. Thanks!

[att]

I am sorry for being so off-topic, but why are we discussing Porteus 1.2 here, in the "General Chat" section?
I thought that Porteus 1.2 ought to be announced in "Latest Release" .... ?

[Hamza]

"Latest Release" is locked for Administrators/Moderators. This topic has been opened to talk about Porteus v1.2 in general, from issue to publication of an article about Porteus v1.2 ... in other words, this topic is for user's feedback about experience on Porteus v1.2

[brokenman]

Interesting sig Hamza. I know what that is ulimit -u 260 is the remedy.

The announcement section is locked and monitored by groups like distrowatch. When it changes they know something is going on.

[sams]

Latest release is working super & is appreciated! I have been working with it a lot and I haven't seen a bug or been stumped to make it do anything, even kinda crazy stuff.

As a nit, I note the following in txz2xzm:

Code: Select all

find $TMPDIR/usr{/local,/}{man,info} -type l -name "*.gz" 2>/dev/null | xargs -r gunzip -f

If I read this correctly, it won't manifest a bug but I think it should look like this?

Code: Select all

find $TMPDIR/usr{/local/,/}{man,info} -type l -name "*.gz" 2>/dev/null | xargs -r gunzip -f

cheers!

[fanthom]

@sams
correct - fixed now,

(also added unpacking of man pages to dir2xzm - just in case)

thanks

[Rava]

Dunno if this is the right thread to call a bug in linux-3.4.8-kernel_update-i486-1ftm.tar.gz...

Anyhow, the kernel in boot/vmlinuz is not 3.4.8, but 3.4.4:

Code: Select all

#uname -a
Linux porteus 3.4.4-porteus #1 SMP PREEMPT Tue Jun 26 03:37:13 UTC 2012 i686 Genuine Intel(R) CPU           U1400  @ 1.20GHz GenuineIntel GNU/Linux

# file /lib/modules/3.4.*-porteus
/lib/modules/3.4.8-porteus/: directory

# ls -lo /boot/vmlinuz
-r--r--r-- 1 root 2523536 2012-06-26 16:32 /boot/vmlinuz

# md5sum /boot/vmlinuz
a28bcc069c17e09dbee068c1209929c5  /boot/vmlinuz

I already suspected something like that when I saw the timestamp of boot/vmlinuz in the tar archive...

Anyhow, the NVidia and ATI drivers, are they for 3.4.4. or 3.4.8 ?

[bour59]

boot says 3.4.4
and after in vesa-mode porteus hangs up ... french ipl needed

[fanthom]

@guys

this issue have already been addressed - please check 'Porteus v1.2 update' announcement once again.