Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 31 Jul 2014, 00:00
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Updated Universal Installer
Moderators: deshlab, Flash, GuestToo, Ian, JohnMurga, Lobster
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Tue 24 Apr 2007, 14:26    Post subject:  

Quote:
Everybody: Please test this, at least the first few stages, when it just detects your HW

From 2.15CE live-DVD, with a pup_save on hdd1...your new PUI detects both a USB stick (sdb) and an SCSI hard disk (sda).
Back to top
View user's profile Send private message 
Dougal


Joined: 19 Oct 2005
Posts: 2505
Location: Hell more grotesque than any medieval woodcut

PostPosted: Tue 24 Apr 2007, 16:07    Post subject:  

Sit Heel Speak wrote:
Quote:
Everybody: Please test this, at least the first few stages, when it just detects your HW

From 2.15CE live-DVD, with a pup_save on hdd1...your new PUI detects both a USB stick (sdb) and an SCSI hard disk (sda).


You mean a "real" SCSI drive? Or SATA? If it's a real scsi, I need help in trying to figure out how to know it's scsi and not sata... (I know sata might have "ATA" at the vendor -- 1st part of the name in probedisk -- but don't know if scsi drives will have "scsi" written anywhere...

If it's a real scsi I can give you more things to test...

_________________
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Back to top
View user's profile Send private message 
Gn2


Joined: 16 Oct 2006
Posts: 936
Location: virtual - Veni vidi, nihil est adpulerit

PostPosted: Tue 24 Apr 2007, 17:36    Post subject:  

Quote:
help in trying to figure out how to know it's scsi

Philosophy

Architecture
*****************

The Linux SCSI Generic (sg) Driver:

SG3 Utils

SG-IO

Great Fun All: sg_raw ~ cdrecord-scanbus( outputs much same data)

TOOLS
LSSCSI/MAPSCSI
Back to top
View user's profile Send private message 
Gn2


Joined: 16 Oct 2006
Posts: 936
Location: virtual - Veni vidi, nihil est adpulerit

PostPosted: Tue 24 Apr 2007, 18:21    Post subject:  

Wot is LS-120?
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1504
Location: Maine, USA

PostPosted: Tue 24 Apr 2007, 19:42    Post subject: Autodetected CDROM incorrect  

Thanks very much, Dougal, for tackling the installer to make it more "universal". I have tested your new version (as of yesterday) and find that it does not correct a related problem introduced in 2.15. It relies on /dev/cdrom and /dev/dvd as set during initialization or by the drive wizard.

However, in 2.14 the wizard shows the detected drive correctly, as hdc; the 2.15 wizard incorrectly shows hdb. This causes the installer to persistantly prompt for insertion of a CD into hdb!

The workaround, of course, is to run the wizard to set hdc. This suggests that the dialog might recommend the user do that.

But the main problem is that the initial cdrom detection is invalid; however, the installer is what shows the crazy behavior when the user relies on the default detection. (My PC has only a primary-master HD and secondary-master CDRW. My other PC with 2 HDs gets even more bizarre -- the HDs are offered as the CDROM candidates.)

Here are the differing wizard dialog boxes:
Quote:
2.14:
Puppy has probed your PC and found these CD/DVD drives:
/dev/hdc LITE-ON_LTR-48125W

Puppy thinks the default CDROM reader drive is: /dev/hdc
Puppy thinks the default DVD reader drive is:
Puppy thinks the default burner drive is: /dev/hdc

DEVICE LINKS:
/dev/cdrom is currently linked to: /dev/hdc.
/dev/dvd is currently linked to: .

2.15:
Puppy has probed your PC and found these CD/DVD drives:
/dev/hdc LITE-ON_LTR-48125W

Puppy thinks the default CDROM reader drive is: /dev/hdb
Puppy thinks the default DVD reader drive is: /dev/hdb
Puppy thinks the default burner drive is:

DEVICE LINKS:
/dev/cdrom is currently linked to: /dev/hdb.
/dev/dvd is currently linked to: /dev/hdb.

I also note that the 2.15 version misleadingly shows a DVD device, even though the device is only a CDROM.

I hope you can correct these regressions as part of your upgrade to the installer (and that on which it depends). Thanks in advance.

Richard
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Tue 24 Apr 2007, 20:03    Post subject:  

Dougal, the 'init' script distinguishes between sata and true scsi drives, well, it does so in the latest 2.16. Information is written to /etc/rc.d/PUPSTATE, and it has the variable 'SATADRIVES='
...I could put some more variables in there.
I think Pup 2.14 also creates SATADRIVES variable.

In the init script, USBDRIVES is the USB drives (but not USB CD/DVD drives), SATADRIVES is the SATA drives (but not SATA CD/DVD drives).
The USBDRIVES variable is not exported as that can change, but you can dynamically test if a drive is USB or SATA by checking against the SATADRIVES variable. The same thing holds for testing if it is a true SCSI drive.
Back to top
View user's profile Send private message Visit poster's website 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Tue 24 Apr 2007, 21:20    Post subject:  

Dougal wrote:
You mean a "real" SCSI drive? Or SATA?

Real SCSI. Vintage-1998 Seagate ST32155W on an Adaptec AHA-2940UW PCI SCSI controller. Delighted to help...
Back to top
View user's profile Send private message 
bobn9lvu


Joined: 11 Jul 2006
Posts: 173

PostPosted: Tue 24 Apr 2007, 21:44    Post subject:  

Ok, BUT if installed on a scsii drive, WILL it boot from that drive??? Shocked
That's what inquiring minds want to know?? Wink

Bob Cool

_________________
Puppy Linux - Lift your leg at Redmond. Razz Twisted Evil Razz
Back to top
View user's profile Send private message 
Dougal


Joined: 19 Oct 2005
Posts: 2505
Location: Hell more grotesque than any medieval woodcut

PostPosted: Wed 25 Apr 2007, 09:47    Post subject:  

Users of boot loaders: Please help.

Grub users: I am trying to get the script to autodetect a grub installation. Please run the attached script (in a terminal) and see if it gives the right results.
Note: do not place the script in /tmp as scripts don't work well from within there.

Lilo users: I'm thinking of possibly adding support for Lilo, so any info will be helpful.
Examples:
The output of "disktype /dev/hda" (if had has Lilo installed to it's MBR)
Same for "hda1" if Lilo is installed to that partition (is it possible with Lilo, or only with Grub?)
Also the output of "fdisk -l"
Where is the menu file? With grub it's called "menu.lst" and located in /hda1/boot/grub/ (for example).
Also what the entries look like for a full install and for a frugal.


I will reply to recent posts shortly.
find-grub.gz
Description 
gz

 Download 
Filename  find-grub.gz 
Filesize  2 KB 
Downloaded  395 Time(s) 

_________________
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Back to top
View user's profile Send private message 
Dougal


Joined: 19 Oct 2005
Posts: 2505
Location: Hell more grotesque than any medieval woodcut

PostPosted: Wed 25 Apr 2007, 11:30    Post subject:  

SHS: I'm more interested in simple info on how to know (from within a script) that it's a scsi drive. I know of lsscsi, but that means adding it to Puppy and waiting for the next release so people test with it etc. and also I don't like to rely on such contraptions (see probedisk/probepart and all the trouble they cause in Puppy). Lsscsi also gives you a lot of info -- I just want to know: scsihd or satahd?

As for the "sg" module, if I recall correctly, when I worked on adding scsi modules to my initrd.gz I tried it on my machine (=no scsi devices) and it caused my two IDE cdroms to be given scd0 and scd1 -- as well as the usual hdc and hdd -- which will cause a mess (and dmesg had a warning saying not to use it since it's deprecated…).
So I didn't put "sg" in with the scsi modules.


Rerwin: I was wondering if I should use /dev/cdrom /dev/dvd or actually look for devices… the reason I chose it this way was
1) laziness… couldn't be bothered doing the whole looking for cdroms
2) it seemed simpler to write the code this way. I guess I could just create a loop that goes through the cdroms
3) I try and assume that if the code in rc.local0 does a lot to check the drives, then the links are ok…

I'll see, I might just go to using device names (not rely on anything…).

The wizard is beyond my control…


Barry: the SATADRIVES parameter is not very reliable, so I don't use it. When I added scsi modules to my init script I thought of also creating a SCSIDRIVES parameter, but it's not worth the trouble and I don't like to rely on it for finding files: for example, if PMEDIA is "satahd" I just scan all "sd" devices…


Bobn9lvu: I think that Sage keeps complaining about Grub not being able to boot scsi. Is that so? If so it's a matter of using Lilo (I might get to that…).
However, you also need the init to be able to boot scsi… Jesse just tried my modified version with a scsi drive and it worked, but froze in rc.modules… so that's another hurdle in the way to booting off scsi drives.

_________________
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Back to top
View user's profile Send private message 
Gn2


Joined: 16 Oct 2006
Posts: 936
Location: virtual - Veni vidi, nihil est adpulerit

PostPosted: Wed 25 Apr 2007, 11:42    Post subject:  

Where does "disktype" come from - another "puppy variant " ?
fdisk -l will output all probe located hard drives
lspci/lsusb & sg_io (IOCTRL/sg3) > utilities probe M/Brd bus /DMA return of OEM device capabilities
(dmesg shows boot probe results - tail /var/log files last system events)

NTIM to others - I have long maintained - use of "generic" names such as cdrom/dvd etal - was poor Linux NON nomenclature -
They are NOT true block devices - (only symlinks)
~ Have caused vast confusion over Distro variants using same
Names/mount points are optional (calll any "Pink Elephants" if wished - just ensure symlnks/loader Cfg's point where needed)
Why the reluctance to Linux conventions > everything is user syscal accessed as a file ?

/etc/lilo.conf is the configuration for Lilo loader

http://www-128.ibm.com/developerworks/linux/library/l-bootload.html

http://syslinux.zytor.com/faq.php (emulation when loader exceeds media size limit)
Quote:
# $Header: /var/cvsroot/gentoo-x86/sys-boot/lilo/files/lilo.conf,v 1.2 2004/07/18 04:42:04 dragonheart Exp $
# Author: Ultanium
#
# Start LILO global section
#
# Faster, but won't work on all systems:
#compact
# Should work for most systems, and do not have the sector limit:
{above line refers to old 1024cyl limitation}
lba32
# If lba32 do not work, use linear:
#linear
# MBR to install LILO to:
boot = /dev/hda
map = /boot/.map
# If you are having problems booting from a hardware raid-array
# or have a unusual setup, try this:
#disk=/dev/ataraid/disc0/disc bios=0x80 # see this as the first BIOS disk
#disk=/dev/sda bios=0x81 # see this as the second BIOS disk
#disk=/dev/hda bios=0x82 # see this as the third BIOS disk
# Here you can select the secondary loader to install. A few
# examples is:
#
# boot-text.b
# boot-menu.b
# boot-bmp.b
#
install = /boot/boot-menu.b # Note that for lilo-22.5.5 or later you
# do not need boot-{text,menu,bmp}.b in
# /boot, as they are linked into the lilo
# binary.
menu-scheme=Wb
prompt
# If you always want to see the prompt with a 15 second timeout:
#timeout=150
delay = 50
# Normal VGA console
vga = normal
# VESA console with size 1024x768x16:
#vga = 791
#
# End LILO global section
#
# Linux bootable partition config begins
#
image = /boot/bzImage
root = /dev/hda3
#root = /devices/discs/disc0/part3
label = Gentoo
read-only # read-only for checking
#
# Linux bootable partition config ends
#
# DOS bootable partition config begins
#
other = /dev/hda1
#other = /devices/discs/disc0/part1
label = Windows
table = /dev/hda
#
# DOS bootable partition config ends
#

Sorry - Sg is NOT deprecated - try to use virtual file system for removable media without it
The "versions" have changed (sg-sd-sr-st)
If you re-read Docs - it's use is Esp valuable for naming convention variables ! (hot-plugging, daisy-chain/first found claims)
Sg is generic driver - used to address the V/FS of device
VARIABLES
Back to top
View user's profile Send private message 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Wed 25 Apr 2007, 15:40    Post subject:  

@Dougal: I don't have a SATA drive, only a USB stick and the SCSI drive, but, does this provide clues?

Seagate=SCSI hard disk
SanDisk = USB stick

Samsung, WDC (Western Digital), and Fujitsu are all IDE disks.

Can someone please post the output of probedisk on a SATA drive?
probedisk and jesseprobeusb in 2.15CE with SCSI disk and USB stick.png
 Description   
 Filesize   8.01 KB
 Viewed   915 Time(s)

probedisk and jesseprobeusb in 2.15CE with SCSI disk and USB stick.png

Back to top
View user's profile Send private message 
bostonvaulter


Joined: 26 Sep 2006
Posts: 269

PostPosted: Wed 25 Apr 2007, 15:49    Post subject:  

Here's my output of find-grub, I ran it from /root

# time ./find-grub
grub installed to MBR of device |hda|

real 0m5.713s
user 0m0.110s
sys 0m0.130s
#


This is correct. I have an internal ide hard drive. Grub is installed on hda5 (well the /boot directory is there, i don't know if you actually call it "installed" there)

Jason

_________________

Back to top
View user's profile Send private message 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Wed 25 Apr 2007, 16:40    Post subject:  

...ehrrrm, perhaps my earlier enthusiasm was premature...

When installing a full hd Puppy...there should be, somewhere, a vmlinuz and an initrd.gz on the destination disk, right?
Back to top
View user's profile Send private message 
Dougal


Joined: 19 Oct 2005
Posts: 2505
Location: Hell more grotesque than any medieval woodcut

PostPosted: Wed 25 Apr 2007, 17:07    Post subject:  

bostonvaulter wrote:
# time ./find-grub
grub installed to MBR of device |hda|


That's actually not good... my script also looks for the "menu.lst" file, which should be in /hda5/boot/grub/ (I assume).

Am I correct in assuming where it should be? Maybe I should make the script more verbose, to find out where the problem is.


SHS: You mean the files that should be in /boot are missing?


Gn2: disktype is an app that gives info about drives -- if I do disktype /dev/hda it tells me that grub is installed to it (MBR).
If I have grub installed to, say, hda3 -- disktype /dev/hda3 will say grub is installed there.

I use fdisk -l for finding bootable partitions, but there isn't always a bootable partition! For example the case when grub is installed to a partition...

_________________
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1088s ][ Queries: 13 (0.0105s) ][ GZIP on ]