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!
Lite-on iHAP122-06 drive not found in MUT (Is now but why?)
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
Lite-on iHAP122-06 drive not found in MUT (Is now but why?)
Last edited by Mercedes350se on Mon 14 Nov 2011, 07:07, edited 1 time in total.
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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?"
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?"
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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?
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?
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.
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.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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.
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.
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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 !
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 !
make sure it is connected to the end of the data cable not the middle connection.Mercedes350se wrote:It is the only drive on the secondary connector so I have set it to master.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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
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 .
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: Select all
ls -l /dev/hd*
ls -l /dev/sd*
ls -l /dev/cdrom
ls -l /sys/block
ls -l /sys/class/blockthey 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 .
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
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
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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.
# 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.
Parts of the post is the explanation from " make menuconfig " inside the kernel source .I do not understand your post regarding /dev/core given my very small knowledge of Linux.
As far as i understand it ,
the crash kernel ability is to save information into RAM
when a kernel crashes
AND if booted with the kernel parameter " panic=N " [ where N is seconds before reboot ]
after reboot the crash kernel data can be read from RAM [ using dd command i guess ] .
So the data would survive a reboot but not a poweroff .
Why most linux distros dont configure their kernels with a default panic=X parameter i dont know , but i guess everyone trying linux would have missed that feature once a while i guess .
Maybe the psychological influence of the word " panic " keeps them away to do this .
Because there are so many post about " Kernel panic .. not syncing ... " i would suggest a "panic=30" or "panic=60" default value .
Barry knows it is possible to adjust the default kernel command line parameters :
# grep -i VIDEO /etc/modules/*
/etc/modules/DOTconfig-3.0.7:CONFIG_CMDLINE="video=640x480"
Karl,
You keep showing us these command line tidbits that give useful information.
Is there a place one can look for a list of them and their function?
I have been using Puppy for a while now and I still am a real dummy in a lot of things linux.
As a matter of fact, if it was not for Puppy and the friendly community here, I would have been trapped in Windows.
I still have Windows installed as there are some applications that just will not run in Wine.
I remember running DBan from a DBan CD on a drive that had viruses major on it.
This was for a reinstall of Windows on a friends PC.
When I booted from the windows install cd and ran fdisk, I was told no drives existed.
It took Puppy and GParted to make the drive visible to Windows.
You keep showing us these command line tidbits that give useful information.
Is there a place one can look for a list of them and their function?
I have been using Puppy for a while now and I still am a real dummy in a lot of things linux.
As a matter of fact, if it was not for Puppy and the friendly community here, I would have been trapped in Windows.
I still have Windows installed as there are some applications that just will not run in Wine.
I remember running DBan from a DBan CD on a drive that had viruses major on it.
This was for a reinstall of Windows on a friends PC.
When I booted from the windows install cd and ran fdisk, I was told no drives existed.
It took Puppy and GParted to make the drive visible to Windows.
line:1861 panic= [KNL] Kernel behaviour on panic: delay <timeout>
would be one of the google hits for "kernel parameters" .
It is ^ only 90MB ^ to dl kernel source once and even without applying any patches for AUFS or USBSTORAGE it is the only way to gain a little more detailed information .
The default .config in the kernel src is very very poor ( would compile only 3 modules ... ) so adjusting the DOTconfig is the most time consuming part of compiling a kernel (2GHz Processor 1GB DDR-RAM ~2hrs.) .
AND on a full install you dont need the USB or AUFS patches .
I have not compiled a kernel for ~6 month now , but detected that i have to thrash 3 crappy kernels that had booted on a Giga-ByteTechnologyCo.,LTD GA8IDX
AND
ECS K7S5A
board
BUT NOT on a
ASUS P4S8X-X
.....
would be one of the google hits for "kernel parameters" .
It is ^ only 90MB ^ to dl kernel source once and even without applying any patches for AUFS or USBSTORAGE it is the only way to gain a little more detailed information .
The default .config in the kernel src is very very poor ( would compile only 3 modules ... ) so adjusting the DOTconfig is the most time consuming part of compiling a kernel (2GHz Processor 1GB DDR-RAM ~2hrs.) .
AND on a full install you dont need the USB or AUFS patches .
I have not compiled a kernel for ~6 month now , but detected that i have to thrash 3 crappy kernels that had booted on a Giga-ByteTechnologyCo.,LTD GA8IDX
AND
ECS K7S5A
board
BUT NOT on a
ASUS P4S8X-X
.....
-
Mercedes350se
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28