Midori hangs, Numlock, Capslock led blinks, reboots

[hakerdefo]

Strange. Now, while I was logging in, numlock, capslock led blinked, system hung, nad rebooted.
I had wiped this HDD before installing Salix xfce 14.

Wonder if Salix OS XFCE14 is really stable?

It's either a corrupt RAM-HDD or a corrupt install. Check the Salix ISO you've downloaded for integrity. md5 of i486-32-bit ISO is cdf4bf0768e6a6c4fef030e946f013fa and md5 of x86_64-64-bit is 063dd6c24b74f8a58ef483933808af40
And i can assure you that Salix is as stable & solid as Rock of Gibraltar.
First check the ISO md5 and if it matches then i'm afraid you might have to replace the RAM module.

[san2ban]

I had checked the md5 sum before burning the .iso image on to the disk. It matched

I have clearly mentioned that while logging in itself the LED blinks and reboots. Inconsistent. Sometimes hangs after 10 minutes.

I dual boot with Win XP on sda, Salix on sdb. But if it were to be a memory issue, winxp als should have behaved the same way?

Anyway, today I will run memtest. In office now. Will try at home

[thenktor]

I dual boot with Win XP on sda, Salix on sdb. But if it were to be a memory issue, winxp als should have behaved the same way?

No, that says nothing. The only halfway reliable method to make sure the RAM is functional is running a memory test for a long time. And in my experience faulty memory most times is the cause of an unstable system. You also can check your dard disks with smartctl, which should be done on a regular basis anyway. Furthermore graphic cards a likely to happen due to undersized cooling.

[san2ban]

Booted to winxp, observed for 2 hours, never hung or rebooted. Restarted, booted into salix xfce 14, logged in. Was trying to log in to Salix forums, Numlock, Capslock LED blinked, system hung, and after few seconds, rebooted.
Really fed up

1. Quit Archlinux due to systemd biases
2. Went to Funtoolinux. Good. Compiling tkes a lot of time, due to my old hardware.
3. Came to Salix. It hangs, reboots
4. Go back to Funtoo, this weekend

[hakerdefo]

I have clearly mentioned that while logging in itself the LED blinks and reboots. Inconsistent. Sometimes hangs after 10 minutes. I dual boot with Win XP on sda, Salix on sdb. But if it were to be a memory issue, winxp als should have behaved the same way?

This tells us that it is not a Salix problem. If it were a Salix problem it would've been consistent in it's occurance. There would've been a fix pattern. And yes it doesn't look like faulty RAM. Only part of your computer that is different between Salix and Windows is Harddisk. You have two Harddisks. It is likely that your disk sdb that houses Salix is faulty. I would suggest you to check the sata data cable and sata power cable of your drive sdb. And if it still doesn't work you can test install Windows on sdb. If sdb is failing then Windows would also give symptoms like bluescreens and reboots. But if Windows work fine then you can try and reinstall Salix on sdb and check how things go the second time round!

[knome]

I had checked the md5 sum before burning the .iso image on to the disk. It matched

Which means it still could be a bad burn. You can try the following check from Salix if you get enough time before your LED's blinkety-blink and you suffer rebootiness...

Insert your SalixCD/DVD. Start Thunar and left-click to mount and open the Salix disc shown in the side-panel. Open a Terminal from here and do...

Code: Select all

/usr/bin/md5sum -c CHECKSUMS.md5 | less

This will check the integrity of all the files on the disk.

[mimosa]

Another strategy if you don't get long enough for that would be to create an image of the CD in another distro or even OS, then check the md5sum of the image. If it tallies, you know your burn was good. However, it's still possible you got a "bad read" because of problems with the optical drive.

If you find nothing conclusive, it may be worth just reinstalling Salix (if you have the patience) taking note of any special options you choose or tricky points you may encounter. You could also investigate how to do so using a USB stick rather than an optical disk, which apart from anything else is kinder to the environment and your purse. There must be something on the wiki about this. Unetbootin may not be the best way though I believe it does work with 14.0. But I think Salix's in-house technology is smoother and more reliable. Basically just copy over the files and run the script to make it bootable.

You could also use Salix Live for diagnostic purposes.

[san2ban]

Thank you all for your kind replies. Mimosa and others are right. Looks like it is an issue with RAM, though with WinXP it does not show up. May be because winxp is 32 bit, and all linux os I install are 64bit?

I was installing Dragora Linux. Half way through, when packages were being loaded, "kernel Panic', machine error' message was displayed. As before, Numlock, Capslock LED started blinking. But there was an announcement on the screen, saying machine would be rebooted in 30 seconds

I have ordered 2 X 1GB DDR2 533MHz PC2-4200 non-registered, non-ECC RAM. This is the only thing this MOBO, ECS P4M800PRO-M2 Rev.2 will accept. Lousy MOBO. Anyway, hard on cash also, so...

I will report back, after I receive and replace them.

[thenktor]

Did you run http://www.memtest86.com/ ?

[san2ban]

riends
Salix OS is not for me. I replaced Kingston 533MHz DD2 PC42oo, 1GB X 2. Reloaded Salix. Updated packages.
When I was Using midori, again capslock, numlock blinked, midori hung, system rebooted after 30 seconds
Rupees 2400 down the drain!

Anyway, I will go back to Funtoo linux