3.00 Frugal Install from-and-to HDD -- Xorg Probing Trouble

Booting, installing, newbie
Post Reply
Message
Author
pandobud
Posts: 4
Joined: Fri 12 Oct 2007, 03:47

3.00 Frugal Install from-and-to HDD -- Xorg Probing Trouble

#1 Post by pandobud »

I'm newb in linux and puppyworld. Need help in a detailed manner.

Here's the problem:
I am trying to frugal-install Puppy 3.00 from-and-to my laptop's harddrive (that doing initial configuration from within windows XP, then reboot into puppy). But the installation froze at the Xorg probing stage.

My laptop is a Toshiba Dynabook SS2000 DS80P/2 with the following spec:
P-3 800 MHz, 256MB, 20GB, with Trydent Video Accelerator CyberBlade XP Ai1 emplying up to 16MB shared memory, with Windows XP Professional XP2 installed.

--------------------------------

Using the following technique, I managed to get the frugal installation going without using a CD/floppy drive:

1. Extract puppy-3.00-seamonkey.iso, and copy vmlinuz, initrd.gz,
pup_xxx.sfs and zdrv_xxx.sfs, then put in c:\puppy300
Note: When I did this from Windows, the extracted filename on the CD
becomes upper-case characters (e.g. PUP_XXX.SFS), so after copying them to the hard drive partition I renamed them to lower-case letters.

2. Download Grub For Dos from
http://sarovar.org/download.php/672/gru ... e22.tar.gz or Get the newest version from
http://sarovar.org/projects/grub4dos/

3. Extract grldr from grub_for_dos-0.4.1pre22.tar.gz to c:\.
The rest of the files in the archive are unnecessary. (If your default compression/archive program doesn't like *.gz files, try 7-Zip from www.7-zip.org.)

4. Append c:\grldr="PuppyLinux 3.00" to c:\boot.ini and
change "timeout=0" to "timeout=10" (this will give you a 10 second
boot-delay to choose wether to boot default windows installation or
to boot Puppy).
To view and edit the Boot.ini file on WindowsXP:
1. Right-click on My Computer, and then click Properties.
2. On the Advanced tab, click Settings under Startup and
Recovery.
3. Under System Startup, click Edit.

5. Create a new text file called menu.lst and save it to c:\

6. Open menu.lst in a text editor and paste the following text in
the file:

title Puppy Linux 3.00
rootnoverify (hd0,0)
kernel (hd0,0)/puppy300/vmlinuz root=/dev/ram0 pmedia=idehd
pdev1=hda1 psubdir=puppy300
initrd (hd0,0)/puppy300/initrd.gz

7. Save menu.lst

8. Reboot, and choose "PuppyLinux 3.00" at the boot menu.

9. Things loaded fine but froze at Xorg display hardware probing stage.

----------------------------------

To fix this, I used hints from:

- "Neomagic problem with 2.13 solved" @
http://www.murga-linux.com/puppy/viewtopic.php?t=14140

- "Toshiba Portege 4010 - xorg - 2.17" @
http://www.murga-linux.com/puppy/viewtopic.php?t=20123

I will summarize the steps below:

1. Just before the boot process starts the xorgwizard you will have to break the sequence by typing "ctrl c" this will get you to the prompt, (might take a few tries) then you can type

mp /usr/X11R7/bin/xwin

This will open up xwin inan editor(mp), then scroll down to line 167 and comment out the lines with a # (as shown in the code below)
When done do a ctrl s to save the changes then ctrl q to exit mp.
(on earlier puppy versions xwin had to be commented out from line
260, in Puppy v2.17 this has moved up to line 133. In Puppy v3.00 this has moved up to line 167)

Code: Select all

#Puppy Xorg Video Wizard... 
#if [ -f /usr/X11R7/bin/Xorg ];then 
# if [ -f /etc/X11/xorg.conf ];then 
#  if [ "`readlink /usr/X11R7/bin/X`" = "Xorg" ];then 
#   #v2.13 video hardware profile (must be same as in xorgwizard)... 
#   DDCPROBE="`ddcprobe`" 
#   PROFILECHIP="`echo "$DDCPROBE" | grep '^oem: ' | head -n 1 | cut
-f 2-4 -d ' ' | tr ' ' '_' | sed -e 's/[^0-9a-zA-Z]/_/g'`" 
#   PROFILEMONITOR="`echo "$DDCPROBE" | grep --extended-regexp
'^monitorrange: |^monitorid: |^eisa: ' | head -n 1 | cut -f 2 -d ':'
| sed -e 's/ //g' | sed -e 's/[^0-9a-zA-Z]/_/g'`" 
#   HARDWAREPROFILE="${PROFILECHIP}${PROFILEMONITOR}" 
#   #find out if current xorg.conf matches this profile... 
#   CURRENTPROFILE="`cat /etc/X11/xorg.conf | grep
'^#PuppyHardwareProfile' | cut -f 2 -d '=' | cut -f 1 -d ' '`" 
#   if [ ! "$CURRENTPROFILE" = "$HARDWAREPROFILE" ];then 
#    #video hardware has changed. either changed monitor or booting
different PC. 
#    #same current xorg.conf as a profiled filename... 
#    mv -f /etc/X11/xorg.conf /etc/X11/xorg.conf.${CURRENTPROFILE} 
#    #if a previous profiled filename for new hardware, use that... 
#    [ -f /etc/X11/xorg.conf.${HARDWAREPROFILE} ] && cp -af
/etc/X11/xorg.conf.${HARDWAREPROFILE} /etc/X11/xorg.conf 
#   fi 
#  fi 
# fi 
 if [ ! -f /etc/X11/xorg.conf ];then 
  rm -f /etc/.XLOADED 2> /dev/null #not necessary, precaution. 
  #1st dialog offers to use Xvesa... 
  /usr/sbin/xorgwizard 
  HAVEX="`readlink /usr/X11R7/bin/X`" 
 fi 
fi
2. After commenting those parts out you can run xorgconfig and set the monitor/screen and graphics chip by answering some questions it ask, save it.

3. At the prompt:

cd /usr/X11R7/bin
rm -f /usr/X11R7/bin/X
ln -s /usr/X11R7/bin/Xorg /usr/X11R7/bin/X

4. Then run xwin by typing at the prompt:

xwin jwm

------------------------------

But after successfully identifying my mouse and my keyboard layout (which is a japanese jp106 keyboard) it's stuck again saying that X is exiting, and I need to retype xwin [fvwm95|jwm] to restart X.

I tried all possible-matching combinations of Xorgsetup parameters for my laptop, but none worked out. I still got the same message.

Any idea how to fix this?
Many thanks in advance
User avatar
HairyWill
Posts: 2928
Joined: Fri 26 May 2006, 23:29
Location: Southampton, UK

#2 Post by HairyWill »

Have a look at
http://puppylinux.org/wikka/BootParms
try disabling pcmcia or acpi with kernel parameters and use the default puppy xorgwizard

Does xvesa work?
pandobud
Posts: 4
Joined: Fri 12 Oct 2007, 03:47

#3 Post by pandobud »

Tried nopcmcia and acpi=off in the following menu.lst

Code: Select all

title PuppyLinux v3.00
rootnoverify (hd0,0)
   kernel (hd0,0)/puppy300//vmlinuz root=/dev/ram0 nopcmcia acpi=off
pmedia=idehd pdev1=hda1 psubdir=puppy300
   initrd (hd0,0)/puppy300//initrd.gz
Still a no go :(

xvesa didn't work from the start, and also after the above feat.
Nevermore
Posts: 366
Joined: Sat 26 Nov 2005, 14:23
Location: Italy

#4 Post by Nevermore »

same problem over here with a toshiba satellite 4030cds
its a no go..
i tried to edit xwin but i just end up with a crumpled screen and the computer hangs..
i am still using version 2.14 that is the last working one..

i was thinking
since i already have a xorg.conf perfectly working on my 2.14, could i force puppy to use that instead and not overwrite my installation one?
--
/sbin/Nevermore
cherriepuppy
Posts: 74
Joined: Sun 11 Dec 2005, 20:27
Location: uk

#5 Post by cherriepuppy »

hi nevermore

should be possible to use your prevoius xorg.conf, you will still have to comment out the lines in xwin, as xwin will try to overwrite your xorg.conf when it tries to run the xorgwizard.

cherriepuppy
SJPUP
Posts: 4
Joined: Wed 17 Oct 2007, 19:23

#6 Post by SJPUP »

i'm also having problems with Xorg on this old laptop. Puppy 2.17 works really well but in 3.01 it's not working. using the xorg.conf from 2.17 gets me a readable screen but the cursor gets split into 3, and whenever it leaves X it has a scrambled screen that can't be read.

the laptop has siliconmotion lynxem graphics. does it need a different driver?
ICPUG
Posts: 1308
Joined: Mon 25 Jul 2005, 00:09
Location: UK

#7 Post by ICPUG »

Pandobud

Despite your attempt to unify the threads regarding the Toshiba problem, a new one got started here:

http://www.murga-linux.com/puppy/viewtopic.php?t=22269

This has a little more information on how the xorg.conf should be set. It looks like the resolution can only be set to 800x600.

Hope this helps you.

ICPUG
Azure
Posts: 1
Joined: Thu 18 Oct 2007, 15:45

#8 Post by Azure »

Count me in, same problem but with a ThinkPad i Series 1200 1161 71G (Celeron 600MHz (128KB), 192MB RAM, 10.0GB, SMI Lynx EM4, XGA).

Up to 2.17 I was using xorg perfectly and vesa worked right too. Now xorg autoprobing will hang up and vesa will work but give me garbage ASCII when shutting off, so I cannot tell puppy if I want to save or not.

My main problem is that I got accustomed to this great distro (I'm a n00b feeling like a pro) and now everything else I try feels slow, chubby and complicated :cry:

Thanks for making me puppy-dependant... :(
Post Reply