Puppy Linux Discussion Forum

[Bruce B]

uname -a
Linux RIPLinuX 2.6.33.2 #1 SMP Thu May 27 10:56:32 EST 2010 i686 GNU/Linux

On Lupu 5.20

It has been working swell, so I'll leave it this way, I suppose.

I have RIPLinuxX installed on the same partition as Puppy frugal, and it appears that it is picking up the RIPLinuxX kernel and not the Puppy kernel, but even that doesn't make sense because I told grub were to find the kernel.

Now that I discovered this, I could fix it, but considering it has been working great probably won't.

~

I thought it worth mentioning that this phenomena maybe can occur, even though I told Puppy where to find things as shown below:

kernel (hd0,1)/520/vmlinuz ro pmedia=atahd psubdir=520 pfix=nocopy,fsck pdev1=sda2

That's all, just an announcement unless someone like Barry or an interested developer wants me to look into it to try and figure out why. Or hopefully, someone already knows how this could happen.

~

[MinHundHettePerro]

[Karl Godt]

Doesn't the Puppy kernel has something like
Thu May 27 10:56:32 EST 2010
Thu May 27 10:56:32 GMT-8 2010

Not sure though .

Had a look here :
http://distrowatch.com/table.php?distribution=rip
and
http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
For the moment it seems to me that the rip and puppy kernel are unintended twins by their respective "make" rs .

RIP is some 160 MB, think I will dl it .

[James C]

Lucid 528.005

[Karl Godt]

Thanks for pointing me to it .

bash-3.2# strings vmlinuz-orig | grep EST
2.6.33.2 (root@puppypc) #1 SMP Thu May 27 10:56:32 EST 2010

bash-3.2# strings /boot/vmlinuz-orig | grep GMT
2.6.30.5 (root@puppypc) #1 SMP Tue Sep 1 15:48:26 GMT-8 2009

All my kernels that i had compiled on Iguleder's dpup two years ago had GMT-8 because i had omitted to set the local time back then . It had been the 2.6.33.2 kernel running . Will have to check . There are i think several updated kernels for 2.6.30.5 because aufs had been updated but not for 2.6.33.2 as it seems on http://bkhome.org/sources .

[Karl Godt]

Hmm.. seems that woof is capable to recompile the kernel .

DOTconfig-K2.6.33.2-5APR2010-SMP-TICKLESS is on Barry's site
and the vmlinuz :
bash-3.2# strings vmlinuz-2.6.33.2-2010-04-05 |grep puppy
2.6.33.2 (root@puppypc) #1 SMP Mon Apr 5 12:55:04 Local time zone must be set--see zic m

[Bruce B]

Thanks very much for the interest

Here are some more details.

My hard disk doesn't work when cold, as in room temperature. I normally run the computer 24/7

If I boot the machine cold, the hard disk is not identified or located. After a few minutes, it warms up. I reboot it and it stops at the GRUB menu.

I've learned I have to wait more minutes before booting. The partitions may not be ready.

One day, I booted Puppy and the on screen text indicated RIPLinuX was trying to load but in a disorganized hodgepodge of goodness knows what software. And it failed to boot and just locked up at a point.

I rebooted and it happened again.

In looking at the on screen text output, I thought something is horribly wrong and maybe making a mess of my partition.

I booted again and this time Puppy booted and I've never had a problem since.

I only discovered the RIPLinuX kernel is running a couple days ago.

GRUB specifies kernel (hd0,1)/520/vmlinuz

but it uses: kernel (hd0,1)/boot/vmlinuz

This would seem to me a GRUB problem. BTW it is a hacked GRUB version 0.97

Do you think?

~~~~

What about the hard disk not being functional when cool?

It doesn't necessarily have to be the hard drive, it could be something in the motherboard or its IDE controller.

The best way to check would be to buy a new hard drive. Because the hard drive can be used on other computers, but if its the motherboard, I'll scrap the machine, and remove reusable hardware.

After posting this 'bug' I think to myself the problem may be unheard of and unique to my machine.

I've also done a full e2fsck check on the partition with no apparent problems found.

~~~~

Thoughts?

[npierce]

[Karl Godt]

Another thought of mine would be that you are running RIP linux with the Puppy kernel . In my experience it is likely that a kernel boots and a Distro gets up til the X-Desktop but without any additionally modules loaded .

Would be interesting to see lsmod output .

[Bruce B]

Thaks for the interest Karl

It is running Puppy for sure, because the software, desktop and apps are all Puppy. Even the loop devices:

Output of mount
rootfs on / type rootfs (rw,relatime)
/dev/sda2 on /initrd/mnt/dev_save type ext3 (rw,noatime,errors=continue,data=ordered)
/dev/loop1 on /initrd/pup_rw type ext3 (rw,noatime,errors=continue,data=ordered)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop4 on /initrd/pup_ro4 type squashfs (ro,noatime)
/dev/loop5 on /initrd/pup_ro5 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=e82f6409)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=112508k)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sdb2 on /mnt/sdw2 type ext3 (rw,noatime,errors=continue,data=journal)

Output of lsmod

Module Size Used by

Code:

iptable_mangle          1189  0 iptable_nat             2666  0 nf_nat                 10083  1 iptable_nat ipt_REJECT              1485  1 nf_conntrack_ftp        4020  0 nf_conntrack_irc        2359  0 iptable_filter           958  1 xt_state                 895  4 nf_conntrack_ipv4       7063  7 iptable_nat,nf_nat nf_conntrack           36999  6 iptable_nat,nf_nat,nf_conntrack_ftp,nf_conntrack_irc,xt_state,{cut} nf_defrag_ipv4           755  1 nf_conntrack_ipv4 ip_tables               7321  3 iptable_mangle,iptable_nat,iptable_filter snd_intel8x0           19143  0 snd_ac97_codec         75789  1 snd_intel8x0 ac97_bus                 686  1 snd_ac97_codec snd_pcm_oss            26845  0 snd_mixer_oss           9963  1 snd_pcm_oss snd_pcm                45385  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_seq_dummy            907  0 snd_seq_oss            18888  0 snd_seq_midi            3156  0 snd_rawmidi            11924  1 snd_seq_midi snd_seq_midi_event      3592  2 snd_seq_oss,snd_seq_midi snd_seq                32379  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer              11986  2 snd_pcm,snd_seq snd_seq_device          3601  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd                    30859  10 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,{cut} soundcore               3403  1 snd snd_page_alloc          4645  2 snd_intel8x0,snd_pcm ohci1394               20716  0 serio_raw               2928  0 ieee1394               50116  1 ohci1394 fbcon                  27736  0 tileblit                1509  1 fbcon font                    6916  1 fbcon bitblit                 3514  1 fbcon softcursor               805  1 bitblit shpchp                 21148  0 pci_hotplug            18286  1 shpchp forcedeth              40937  0 pcspkr                  1179  0 i2c_nforce2             4236  0 i2c_core               11497  1 i2c_nforce2 nvidia_agp              3640  1 agpgart                18904  1 nvidia_agp parport_pc             19055  0 parport                20387  1 parport_pc evdev                   5517  0 thermal                 9263  0 button                  3522  0 processor              24987  0 fuse                   42549  0 aufs                  110466  1 nls_iso8859_1           2937  0 nls_cp437               4465  0 usbhid                 18009  0 usb_storage            29717  1 squashfs               15984  3 ohci_hcd               16937  0 ssb                    29373  1 ohci_hcd ehci_hcd               25830  0 usbcore                91279  5 usbhid,usb_storage,ohci_hcd,ehci_hcd floppy                 40152  0

[01micko]

Intriguing Bruce

It has been found that hostname conflicts can slow down your PC. Is all performing OK?

I did research on this when we went over to a unique hostname setup in woof by appending ${RANDOM} to "puppyc" very early on in the initial boot.

Different ways to determine hostname in puppy:

[Bruce B]

01micko,

[starhawk]

Bruce B, do you hear a clicking sound while your hard drive is being slow? That would tend to indicate impending failure of the drive.

...could also be that the controller on the computer's motherboard is on its way out.

[01micko]

[Bruce B]