LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Puppy (http://www.linuxquestions.org/questions/puppy-71/)
-   -   5.2.8.004 locks up on bark (http://www.linuxquestions.org/questions/puppy-71/5-2-8-004-locks-up-on-bark-930779/)

davoid 02-22-2012 06:59 PM

5.2.8.004 locks up on bark
 
Trying to test-drive pup5.2.8 but locks up on me in gui as soon as dog barks then everything but mouse is dead. Current system has SuSe 10.3 but the repositories are now gone and the newer SuSe runs on here but way to slow with it's bloatware! My system is 1.8 AMD Sempron with 1 gig ram vid is GeForce4 MX 440 with AGP8X. I've tried apci=off, pfix=nocopy and pfix=nox. When I use pfix=nox and then startX I get farther cause the bark is delay some that method. I somehow think it is related to the sound card (a pci ensoniq) or it's drivers. Any ideas???

Topaz 02-23-2012 02:47 PM

Try this
When you use the pfix=nox do you get the command line, If you do type in xorgwizard and try to set up display from the wizard Do not use startx. The wizard is keys only no mouse untill you get to the testing stage.
Once you get to the desktop use the quickpet to install the nivida driver.

Good luck

Karl Godt 02-23-2012 04:38 PM

For now i can only say that Xorg has its own features (including kernel drivers)and includes loading of drivers via the modprobe command .

Xorg 1.7.x does not make any porobs with my hardware but Puppy Xorg 1.3.0 does .

Xorg is unf. not so easy to compile like the kernel ...

davoid 02-24-2012 09:24 AM

Thanks Topaz & Karl for the reponse.
Still no go! xorgwizard gives MV: CANNOT STAT /usr/bin bla bla blah Dir or file not found. However xorg-setup works but tried several combos with no luck, as soon as you hear the barks it locks up.

Karl Godt 03-05-2012 04:54 PM

Havent powered up my nvidia 440 somewhat AMB board K7 1GHz .

I can't remember any probs with the Xorg driver nv_drv.so and nouveau_drv.so with Puppy 4/5 series Xorg 1.3.0 and 1.7.6 .

Never needed to install any advanced nvidia kernel and Xorg module nor mesa dri.so .

The problem might be that Puppys binaries are mostly compiled i486 and might missing some instructions on the amd cpu .

It seems that Xorg , xinit, openbox/jwm are having troubles .

You are only able to view the /var/log/Xorg.0.log if you poweroff hard , but not the /tmp/xerrs.log .

One possibility i would try is to run
Code:

mp `which xwin`
and adjust the lines that look like these

Code:

Xorg)
  echo "Starting X, specs in /etc/X11/xorg.conf, startup apps /root/.xinitrc..."
  #v2.11 G2 suggested -br for black background instead of checked...
  #w479 ***AWFUL HACK*** running pup 218, retro k2.6.18.8, my laptop, Xorg hangs
  #    if have '-nolisten tcp'. until find out why, this workaround...
  if [ "$KERNELVER" = "2.6.18.8" ];then
  /usr/bin/xinit /root/.xinitrc -- -ignoreABI -config $XORGCONFFILE -br > /tmp/xerrs.$HAVEX.log 2>&1
  RETval1=$?
  else
  /usr/bin/xinit /root/.xinitrc -- -ignoreABI -config $XORGCONFFILE -br -nolisten tcp > /tmp/xerrs.$HAVEX.log 2>&1

to something like
Code:

Xorg)
  echo "Starting X, specs in /etc/X11/xorg.conf, startup apps /root/.xinitrc..."
  #v2.11 G2 suggested -br for black background instead of checked...
  #w479 ***AWFUL HACK*** running pup 218, retro k2.6.18.8, my laptop, Xorg hangs
  #    if have '-nolisten tcp'. until find out why, this workaround...
  if [ "$KERNELVER" = "2.6.18.8" ];then
  /usr/bin/xinit /root/.xinitrc -- -ignoreABI -config  /etc/X11/xorg.conf -logfile /root/Xorg.0.log -br > /root/xerrs.log 2>&1
  RETval1=$?
  else
  /usr/bin/xinit /root/.xinitrc -- -ignoreABI -config /etc/X11/xorg.conf -br -logfile /root/Xorg.0.log -nolisten tcp > /root/xerrs.log 2>&1

to direct the log output from Xorg to /root to get them merged there . If you run USB frugal in PUPMODE 13 , also run xwin like
Code:

xwin &;sleep 5s;/usr/sbin/snapmergepuppy
to get the tmpfs files rescued .


All times are GMT -5. The time now is 06:59 AM.