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 Sat 18 May 2013, 08:55
All times are UTC - 4

 Forum index » House Training » Beginners Help ( Start Here)
Lite-on iHAP122-06 drive not found in MUT (Is now but why?)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [19 Posts]   Goto page: 1, 2 Next
Author Message
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Fri 04 Nov 2011, 03:05    Post subject:  Lite-on iHAP122-06 drive not found in MUT (Is now but why?)  
I decided to purchase a new IDE DVD burner. It duly arrived and was installed. It is on the secondary IDE connector on the mobo. It is the only drive on that connector.

Taking note of the jumper position (CS) - strange I thought but it worked with the old drive - placed it in the same position on the new drive. Booted up and nothing in MUT.

OK, try MA. Again zip!

I notice there is an enormous amount of CPU activity while just typing this.

Is it DOA or am I missing something?

Edit: Went into BIOS during reboot. It is identified correctly!
Last edited by Mercedes350se on Mon 14 Nov 2011, 03:07; edited 1 time in total
Back to top
View user's profile Send private message 
Lobster
Official Crustacean


Joined: 04 May 2005
Posts: 15109
Location: Paradox Realm
PostPosted: Fri 04 Nov 2011, 03:21    Post subject:  
Quote:
Booted up and nothing in MUT


You must be a time traveler . . .
Is MUT still around?

Which Puppy version?
Is the device recognized in the BIOS?
_________________
Puppy WIKI
Back to top
View user's profile Send private message Visit poster's website 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Fri 04 Nov 2011, 03:55    Post subject:  
Hi Lobster.

Yes you could say that! I still enjoy my Puppy 3.01. Yes BIOS recognises it.

After my original post I rebooted with my LiveCD of 4.1.2 and the drive was found. Hmm.

Rebooting back into 3.01 and, this time, using Pmount the drive is found. Call me contrary but I prefer MUT.

The question now is, "Can I get MUT to recognise the drive?"
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Tue 08 Nov 2011, 18:22    Post subject:
Subject description: Curious and Curiouser		  
I have been offered a .pet to try. In order to make anything I do easily reversible I have a 3.01 frugal install. If I fix it till it breaks then it is simply a matter of copying over the 'pristine' save file. If it works in the frugal then it is added to the HDD install.

Booted into the frugal and, out of curiosity, clicked the mut menu item - dear readers you have probably guessed - there was the new drive!

I also have a 3.01 frugal install on a USB stick. Tried there and, lo and behold, the drive was found.

OK. Back to the hard drive install and as expected the drive is not found by mut, however, if I start Pmount and quit without doing anything then try mut the drive is found.

What is the difference between the frugal install and the HDD install to make mut act like this?
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 3687
Location: Charleston S.C. USA
PostPosted: Wed 09 Nov 2011, 00:46    Post subject:  
My best idea is the full install is basically setup and configured for what was in the computer when the full install was performed.
A frugal install, boots just like a new install, looking for everything, and then finds the save file and uses it.
I would say the full install is not expecting to have to look for new hardware.
3.0.1 is using some really old core Puppy programs. They have been much improved in newer versions of Puppy.
_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
Puppy Help 101 An interactive tutorial for Puppy 5.2.5
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Wed 09 Nov 2011, 02:43    Post subject:  
Thank you.

There must be some "looking for new hardware" else how would USB sticks be recognised after being plugged in to an operating computer?

I have found a work around - outlined above - so I will use that in the short term.

I will try the .pet in my frugal install but, given that mut finds the drive, I am not sure if that would help my HDD install.
Back to top
View user's profile Send private message 
cthisbear

Joined: 29 Jan 2006
Posts: 2942
Location: Sydney Australia
PostPosted: Wed 09 Nov 2011, 04:03    Post subject:  
" It is on the secondary IDE connector

Taking note of the jumper position (CS) "

Change it to slave.

I never use CS.

Chris.
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Wed 09 Nov 2011, 06:16    Post subject:  
It is the only drive on the secondary connector so I have set it to master.
Back to top
View user's profile Send private message 
Karl Godt


Joined: 20 Jun 2010
Posts: 2671
Location: Kiel,Germany
PostPosted: Wed 09 Nov 2011, 13:12    Post subject:  
Make sure the appropriate drivers are loaded .
The puppy scripts do a dd if=/dev/sr1 of=/dev/null bs=512 count=1 to update the drive . If the drive is not yet listed in /dev it would not work .

The scripts also look in /sys/[class/]block for the drives .

mut[2] i think mostly looks in /proc .

The difference between frugal and full is also the initrd.gz which may load drivers differently than /etc/rc.d/rc.sysinit .

AND initrd.gz changes much !
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 3687
Location: Charleston S.C. USA
PostPosted: Wed 09 Nov 2011, 17:33    Post subject:  
Mercedes350se wrote:
It is the only drive on the secondary connector so I have set it to master.

make sure it is connected to the end of the data cable not the middle connection.
_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
Puppy Help 101 An interactive tutorial for Puppy 5.2.5
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Thu 10 Nov 2011, 02:52    Post subject:  
@Karl Godt,

How can I tell if, or not, the drive is listed in /dev?

As an aside in /dev there is an exclamation mark which shows as symlink to ../proc/kcore. What is that?

@bigpup,

Thank you. I know about that.
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Thu 10 Nov 2011, 06:01    Post subject:  
Something else to consider. If I go into Setup>CD/DVD drive Wizard the new drive is there.

What the ... ?
Back to top
View user's profile Send private message 
Karl Godt


Joined: 20 Jun 2010
Posts: 2671
Location: Kiel,Germany
PostPosted: Thu 10 Nov 2011, 06:34    Post subject:  
FOR an IDE kernel :

IDE CONTROLLER 1 :

MASTER = /dev/hda
SLAVE == /dev/hdb

IDE CONTROLLER 2 :

MASTER = /dev/hdc
SLAVE == /dev/hdd

REGARDLESS if HARDDISK or CDROMDRIVE

USB is always /dev/sda,/dev/sdb,/dev/sdc etcetera

#******************************************#

FOR a SATA kernel :

HARDDISKDRIVES=/dev/sda,/dev/sdb,dev/sdc etcetera

regardless if INTERNAL or USB ; but internals come first


CDROMDRIVES=/dev/sr0,/dev/sr1,/dev/sr2 etcetera

regardless if INTERNAL or USB ; but internals come first

#****************************************************#

I have bought a LogiLink AU0006C USB2.0 to IDE & SATA adapter some days ago , and what i can say for now :

And old and worn out internal CDROMDRIVE connected that way showed up as /dev/sr0 AFTER modprobing usb-storage[.ko] .
[ i am not sure for now if i had a IDE or SATA kernel running that time(s) ]

I was able to transfer the win drivers and (poor)docs for that adapter from the included CD to Puppy that way .

The adapter does work , also moving partitions on an attached IDE HARDDRIVE , but it seems it needs to plug in the power cord fist , then the data adapter , then plug out the power cord and plug in the power cord again .. While that I had rox open at /sys/block and /sys/class/block and had to hit the update/refresh icon/button in the rox menu bar manually .
Maybe ums-datafab.ko has to be loaded for that adapter also , but to find out more about that I'll experiment with it another day .

You do not tell much about your HARDWARE setup , but i noticed on one board [ asus p4s8x-x ] , that if only one IDE cable is connected to the board it has to be connected to controller-port IDE-1 . Connecting it to IDE-2 the HARDDISKDRIVE did not show up in the BIOS .

to see which devices are available i would use
Code:
ls -l /dev/hd*
ls -l /dev/sd*
ls -l /dev/cdrom
ls -l /sys/block
ls -l /sys/class/block


And for full installations :
they tend load drivers differently each day , especially after hard poweroff on slow machines
[ maybe due to old/buggy udevd/pup_event_backend_d ] ,
mainly to observe at the USB part of the "loading kernel modules" screen .
If part of the code grep a word(DRIVER-NAME) somewhere in the /tmp directory ,
and the /tmp directory still exists after a hard poweroff ,
some drivers get not loaded automatically next boot .

Frugals mount /tmp -t tmpfs
so unmounting /tmp deletes everything in /tmp ,
but full installations do not mount /tmp .
/tmp gets deleted by /etc/rc.d/rc.shutdown and unfortunately not by /etc/rc.sysinit||/sbin/init .

I suspect a hard reset
and due /sbin/pup_event_backend_modprobe did grep a DRIVER-NAME in /tmp/pup_event_module_devpath_log
and exit 0 if found
it did not load much drivers the next boot .
The grep /tmp/pup_event_module_devpath_log is to prevent to load drivers second time .

Puppy 5 has got /sbin/pup_event_backend_modprobe_protect for that ,
but in new racy much of *_backend_modprobe* is disabled .

I dont know anything about Puppy 3 or earlier .
Back to top
View user's profile Send private message Visit poster's website 
Karl Godt


Joined: 20 Jun 2010
Posts: 2671
Location: Kiel,Germany
PostPosted: Thu 10 Nov 2011, 07:00    Post subject:  
ABOUT /dev/core :

grep CORE /etc/modules/*
/etc/modules/DOTconfig-K2.6.30.5-01SEPT09-TICKLESS-SMP:# CONFIG_PROC_KCORE is not set

There is no help available for this kernel option.
Symbol: PROC_KCORE [=y]
Type : boolean
Prompt: /proc/kcore support
Defined at fs/proc/Kconfig:31
Depends on: PROC_FS [=y] && MMU [=y] && !ARM
Location:
-> File systems
-> Pseudo filesystems
-> /proc file system support (PROC_FS [=y])

I have enabled PROC_KCORE @some of my kernels
and had not yet time to experiment with it .

rox > File 'kcore' > Properties :
SIZE : 1016M ##i have 1GB DDR-RAM installed
Type : application/x-core program crash data

bash-3.2# file /proc/kcore
/proc/kcore: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style

2# ls -lsF !$
ls -lsF /proc/kcore
0 -r-------- 1 root root 1065349120 2011-11-10 11:58 /proc/kcore
Back to top
View user's profile Send private message Visit poster's website 
Mercedes350se

Joined: 16 Apr 2008
Posts: 477
PostPosted: Sat 12 Nov 2011, 22:30    Post subject:  
Thank you for the detailed explanations. The ls commands you suggested give:

# ls -l /dev/hd*
brw-r--r-- 1 root root 3, 0 2001-02-13 10:43 /dev/hda
brw-r----- 1 root 6 3, 1 2000-09-27 00:31 /dev/hda1
brw-r----- 1 root 6 3, 10 2000-09-27 00:31 /dev/hda10
brw-r----- 1 root 6 3, 11 2000-09-27 00:31 /dev/hda11
brw-r----- 1 root 6 3, 12 2000-09-27 00:31 /dev/hda12
brw-r----- 1 root 6 3, 13 2000-09-27 00:31 /dev/hda13
brw-r----- 1 root 6 3, 14 2000-09-27 00:31 /dev/hda14
brw-r----- 1 root 6 3, 15 2000-09-27 00:31 /dev/hda15
brw-r----- 1 root 6 3, 16 2000-09-27 00:31 /dev/hda16
brw-r--r-- 1 root root 3, 2 2011-09-02 11:35 /dev/hda2
brw-r--r-- 1 root root 3, 3 2001-02-13 10:43 /dev/hda3
brw-r--r-- 1 root root 3, 4 2001-02-13 10:43 /dev/hda4
brw-r--r-- 1 root root 3, 5 2001-02-13 10:43 /dev/hda5
brw-r--r-- 1 root root 3, 6 2001-02-13 10:43 /dev/hda6
brw-r--r-- 1 root root 3, 7 2001-02-13 10:43 /dev/hda7
brw-r--r-- 1 root root 3, 8 2001-02-13 10:43 /dev/hda8
brw-r--r-- 1 root root 3, 9 2001-02-13 10:43 /dev/hda9
brw-r--r-- 1 root root 3, 64 2001-02-14 03:49 /dev/hdb
brw-r--r-- 1 root root 3, 65 2001-02-14 03:49 /dev/hdb1
brw-r--r-- 1 root root 3, 66 2001-02-14 03:49 /dev/hdb2
brw-r--r-- 1 root root 3, 67 2001-02-14 03:49 /dev/hdb3
brw-r--r-- 1 root root 3, 68 2001-02-14 03:49 /dev/hdb4
brw-r--r-- 1 root root 3, 69 2001-02-14 03:49 /dev/hdb5
brw-r--r-- 1 root root 3, 70 2001-02-14 03:49 /dev/hdb6
brw-r--r-- 1 root root 3, 71 2001-02-14 03:49 /dev/hdb7
brw-r--r-- 1 root root 3, 72 2001-02-14 03:50 /dev/hdb8
brw-r--r-- 1 root root 3, 73 2001-02-14 03:50 /dev/hdb9
brw-r--r-- 1 root root 22, 0 2001-02-14 03:50 /dev/hdc
brw-r--r-- 1 root root 22, 1 2001-02-14 03:50 /dev/hdc1
brw-r--r-- 1 root root 22, 2 2001-02-14 03:50 /dev/hdc2
brw-r--r-- 1 root root 22, 3 2001-02-14 03:50 /dev/hdc3
brw-r--r-- 1 root root 22, 4 2001-02-14 03:50 /dev/hdc4
brw-r--r-- 1 root root 22, 5 2001-02-14 03:50 /dev/hdc5
brw-r--r-- 1 root root 22, 6 2001-02-14 03:50 /dev/hdc6
brw-r--r-- 1 root root 22, 7 2001-02-14 03:50 /dev/hdc7
brw-r--r-- 1 root root 22, 8 2001-02-14 03:50 /dev/hdc8
brw-r--r-- 1 root root 22, 9 2001-02-14 03:50 /dev/hdc9
brw-r--r-- 1 root root 22, 64 2001-02-14 03:51 /dev/hdd
brw-r--r-- 1 root root 22, 65 2001-02-14 03:51 /dev/hdd1
brw-r--r-- 1 root root 22, 66 2001-02-14 03:51 /dev/hdd2
brw-r--r-- 1 root root 22, 67 2001-02-14 03:51 /dev/hdd3
brw-r--r-- 1 root root 22, 68 2001-02-14 03:51 /dev/hdd4
brw-r--r-- 1 root root 22, 69 2001-02-14 03:51 /dev/hdd5
brw-r--r-- 1 root root 22, 70 2001-02-14 03:51 /dev/hdd6
brw-r--r-- 1 root root 22, 71 2001-02-14 03:51 /dev/hdd7
brw-r--r-- 1 root root 22, 72 2001-02-14 03:51 /dev/hdd8
brw-r--r-- 1 root root 22, 73 2001-02-14 03:51 /dev/hdd9
# ls -l /dev/cdrom
lrwxrwxrwx 1 root root 8 2011-11-13 02:38 /dev/cdrom -> /dev/hdc

Note that on this machine I have one HD with 4 partitions with
the OS HDD install on hda1
Data on hda2
Music on hda3, and
frugal install on hda4

The cdrom is hdc.

I do not understand your post regarding /dev/core given my very small knowledge of Linux.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [19 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
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.0864s ][ Queries: 11 (0.0053s) ][ GZIP on ]