Page 5 of 5
Re: Porteus-v2.0-i486 bug reports
Posted: 10 Jul 2013, 22:45
by Rava
fanthom wrote:
that's weird - did you mix up the kernel versions by any chance?
Not that I know, it's a clean 2.0 install... but it acted weird once, telling me that fs / folder of / is invalid, seems there were just too many stuff loaded from the modules, so I just restarted...
please show me what 'dmesg' says about this error (you could also upgrade to kernel from rc2 as suggested by brokenman).
dmesg tells me nothing. the last info is about eth0 becoming ready... When re-run modprobe sr, dmesg says unaltered / the same.
I can use kernel and initrd without newest / 2.1rc1 001-core?
Re: Porteus-v2.0-i486 bug reports
Posted: 11 Jul 2013, 15:00
by fanthom
seems there were just too many stuff loaded from the modules
if you are talking about xzm modules then please boot into 'always fresh' mode when you debug an issue related to kernel or default ISO in general
When re-run modprobe sr, dmesg says unaltered / the same
not sure if this is typo but just in case: please modprobe 'sg' driver
I can use kernel and initrd without newest / 2.1rc1 001-core?
to upgrade the kernel you must copy /boot/syslinux/vmlinuz + /porteus/base/000-kernel.xzm from new ISO to your existing porteus. please do not upgrade other components as it may break something.
Re: Porteus-v2.0-i486 bug reports
Posted: 11 Jul 2013, 19:27
by Rava
fanthom wrote:not sure if this is typo but just in case: please modprobe 'sg' driver
I just ran
since I thought sg was the scsi driver already... ???
Re: Porteus-v2.0-i486 bug reports
Posted: 12 Jul 2013, 09:25
by fanthom
yes 'sg' is a scsi driver and that's why i asked if it were loaded when you plugged your external burner.
anyway - does it help when you load it manually?
Re: Porteus-v2.0-i486 bug reports
Posted: 12 Jul 2013, 16:42
by Rava
fanthom wrote:anyway - does it help when you load it manually?
No, like I said: "modprobe sg" exits with exit code 1 (I get that info via "echo $?" ), but not gives me any additional information of what went wrong...
Re: Porteus-v2.0-i486 bug reports
Posted: 12 Jul 2013, 17:31
by fanthom
"modprobe sg" exits with exit code 1
ok - let's track this down.
please boot 2.0 to 'always fresh' mode -> run 'modprobe sg' -> attach your external burner -> upload /var/log/dmesg to pastebin.com and link here.
if you get 'modprobe exits with code 1' then please make a screenshot of the terminal and upload to tinypic.com
also - please generate full system report (while in 'always fresh') and upload to pastebin.com.
thanks
Re: Porteus-v2.0-i486 bug reports
Posted: 13 Jul 2013, 21:36
by Rava
fanthom wrote:also - please generate full system report (while in 'always fresh') and upload to pastebin.com.
What do you mean with " full system report"? psinfo?
Re: Porteus-v2.0-i486 bug reports
Posted: 14 Jul 2013, 19:29
by fanthom
the tool is named 'Porteus System Info' and is placed in your desktopm menu under 'System' heading.
please launch PSI and dump 'full report'.
thanks