Linux Format forums

I have the same problem

winterfeld — Thu May 03, 2012 9:09 pm

Author: winterfeld

Posted: Thu May 03, 2012 9:09 pm

Just spotted your post. I have been trying to install Centos 6.2 64 bit for the past week. I have tried the full twin DVD version, DVD and CD live versions and the minimal install. I also tried the magazine LXF156 cover disk 32 bit version. All installed properly in partition sda11 on the first hard disk. They recognised a 1 terabite ntfs external usb harddisk and made a good job of all the other hardware.

However both the mouse and keyboard die after 5 minutes or less, or when I change user to root (immediate response). The mouse is a short lead usb cable attached to a ps2 cable and port and the keyboard is usb on an extender cable (the keyboard was a freebe with my Linux Format Subscription about 5 years ago. German with lots of useless keys). All this hardware otherwise works without problem under windoze 7 and XP but Centos is a dead duck. I had been looking forward to making it my core system as it has the Long term Support.

It also has an odd habit of dumping the boot into the boot partition and not in root which is a nightmare as grub2 does not like it. That boots all my other systems, the bootloader being derived from LinuxMint 12.

So do not go changing the system board as I did for another usb problem. Nightmare. I smell a rat with power and heat control, although no problem with linux mint and suse. I do not understand what is going on with the solution in the previous posts......

Re: Wicked hardware problem - freezing {Solved - I hope}

GregS — Tue Jan 10, 2012 5:08 am

Author: GregS

Posted: Tue Jan 10, 2012 5:08 am

Thanks for all the suggestions.

I have opened the case, de-dusted (not much) and reseated boards (only the Nvidia card to seat); pulled the memory chips and run them each singly, no change.

dmesg shows the following (edited,but I've left in the bits that appear pertinent especially keyboard and mouse, sorry if it is a bit big):

Code:

[root@localhost ~]# dmesg | tail
u32 classifier
Actions configured
netfilter PSD loaded - (c) astaro AG
IFWLOG: register target
usbcore: registered new interface driver snd-usb-audio
eth0: no IPv6 routers present
ata2.00: configured for UDMA/133
ata2: EH complete
EXT4-fs (sda1): re-mounted. Opts: commit=0
EXT4-fs (sda3): re-mounted. Opts: commit=0
[root@localhost ~]# dmesg
Linux version 2.6.38.8-pclos1.bfs (root@localhost.localdomain) (gcc version 4.5.2 (GCC) ) #1 SMP PREEMPT Sat Jun 4 04:13:21 CDT 2011
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000bf770000 (usable)
BIOS-e820: 00000000bf770000 - 00000000bf788000 (ACPI data)
BIOS-e820: 00000000bf788000 - 00000000bf7dc000 (ACPI NVS)
BIOS-e820: 00000000bf7dc000 - 00000000c0000000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
Malformed early option 'acpi'
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI 2.6 present.
.
.
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:16 nr_node_ids:1
PERCPU: Embedded 12 pages/cpu @ec800000 s26240 r0 d22912 u262144
pcpu-alloc: s26240 r0 d22912 u262144 alloc=1*4194304
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
.
.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 778000
Kernel command line: BOOT_IMAGE=linux root=UUID=f56b9650-e06b-44e5-a091-cd63f20de6ee quiet nokmsboot vmalloc=256M acpi=on resume=UUID=7e737343-84a2-491a-9e39-d4bd1f0a6afc splash=silent vga=788
.
.
Initializing CPU#0
Initializing HighMem for node 0 (0002ebfe:000bf770)
Memory: 3099304k/3136960k available (3339k kernel code, 37204k reserved, 1645k data, 512k init, 2371016k highmem)
virtual kernel memory layout:
fixmap : 0xffab5000 - 0xfffff000 (5416 kB)
pkmap : 0xff400000 - 0xff800000 (4096 kB)
vmalloc : 0xef3fe000 - 0xff3fe000 ( 256 MB)
lowmem : 0xc0000000 - 0xeebfe000 ( 747 MB)
.init : 0xc05df000 - 0xc065f000 ( 512 kB)
.data : 0xc0442fb5 - 0xc05de780 (1645 kB)
.text : 0xc0100000 - 0xc0442fb5 (3339 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
.
.
Detected 3209.994 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 6419.98 BogoMIPS (lpj=3209994)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 9 MCE banks
CPU0: Thermal monitoring enabled (TM1)
using mwait in idle threads.
ACPI: Checking initramfs for custom DSDT
ACPI: Core revision 20110112
ftrace: allocating 15027 entries in 30 pages
Overriding APIC driver with bigsmp
Enabling APIC mode: Physflat. Using 1 I/O APICs
Leaving ESR disabled.
.
.
CPU 1 irqstacks, hard=ec4c4000 soft=ec4c6000
Booting Node 0, Processors #1
Initializing CPU#1
Leaving ESR disabled.firewire_core: created device fw0: GUID 001e8c0000c3e85e, S400
scsi 8:0:0:0: Direct-Access SMSC 223 U HS-CF 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:1: Direct-Access SMSC 223 U HS-MS 1.95 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdc] Attached SCSI removable disk
scsi 8:0:0:2: Direct-Access SMSC 223 U HS-SM 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:3: Direct-Access SMSC 223 U HS-SD/MMC 1.95 PQ: 0 ANSI: 0
scsi 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:1: Attached scsi generic sg4 type 0
sd 8:0:0:2: Attached scsi generic sg5 type 0
sd 8:0:0:3: Attached scsi generic sg6 type 0
sd 8:0:0:1: [sdd] Attached SCSI removable disk
sd 8:0:0:3: [sdf] Attached SCSI removable disk
sd 8:0:0:2: [sde] Attached SCSI removable disk
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Adding 2047996k swap on /dev/sda2. Priority:-1 extents:1 across:2047996k
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1)
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 41 for MSI/MSI-X
r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xef6aa000, e0:cb:4e:3e:0f:9a, XID 083000c0 IRQ 41
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64

CPU 2 irqstacks, hard=ec4d2000 soft=ec4d4000
#2
Initializing CPU#2
Leaving ESR disabled.
CPU 3 irqstacks, hard=ec4de000 soft=ec4e0000
#3
Initializing CPU#3
Leaving ESR disabled.
Brought up 4 CPUs
Total of 4 processors activated (25679.22 BogoMIPS).
devtmpfs: initialized
.
.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
reserve RAM buffer: 000000000009fc00 - 000000000009ffff
reserve RAM buffer: 00000000bf770000 - 00000000bfffffff
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource hpet
Switched to NOHz mode on CPU #0
Switched to NOHz mode on CPU #3
Switched to NOHz mode on CPU #1
Switched to NOHz mode on CPU #2
pnp: PnP ACPI init
ACPI: bus type pnp registered
.
.

pnp 00:10: [mem 0xfed90000firewire_core: created device fw0: GUID 001e8c0000c3e85e, S400
scsi 8:0:0:0: Direct-Access SMSC 223 U HS-CF 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:1: Direct-Access SMSC 223 U HS-MS 1.95 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdc] Attached SCSI removable disk
scsi 8:0:0:2: Direct-Access SMSC 223 U HS-SM 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:3: Direct-Access SMSC 223 U HS-SD/MMC 1.95 PQ: 0 ANSI: 0
scsi 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:1: Attached scsi generic sg4 type 0
sd 8:0:0:2: Attached scsi generic sg5 type 0
sd 8:0:0:3: Attached scsi generic sg6 type 0
sd 8:0:0:1: [sdd] Attached SCSI removable disk
sd 8:0:0:3: [sdf] Attached SCSI removable disk
sd 8:0:0:2: [sde] Attached SCSI removable disk
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Adding 2047996k swap on /dev/sda2. Priority:-1 extents:1 across:2047996k
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1)
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 41 for MSI/MSI-X
r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xef6aa000, e0:cb:4e:3e:0f:9a, XID 083000c0 IRQ 41
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
-0xffffffff]
system 00:10: [mem 0x00000firewire_core: created device fw0: GUID 001e8c0000c3e85e, S400
scsi 8:0:0:0: Direct-Access SMSC 223 U HS-CF 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:1: Direct-Access SMSC 223 U HS-MS 1.95 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdc] Attached SCSI removable disk
scsi 8:0:0:2: Direct-Access SMSC 223 U HS-SM 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:3: Direct-Access SMSC 223 U HS-SD/MMC 1.95 PQ: 0 ANSI: 0
scsi 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:1: Attached scsi generic sg4 type 0
sd 8:0:0:2: Attached scsi generic sg5 type 0
sd 8:0:0:3: Attached scsi generic sg6 type 0
sd 8:0:0:1: [sdd] Attached SCSI removable disk
sd 8:0:0:3: [sdf] Attached SCSI removable disk
sd 8:0:0:2: [sde] Attached SCSI removable disk
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Adding 2047996k swap on /dev/sda2. Priority:-1 extents:1 across:2047996k
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1)
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 41 for MSI/MSI-X
r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xef6aa000, e0:cb:4e:3e:0f:9a, XID 083000c0 IRQ 41
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
000-0x0009ffff] could not be reserved
system 00:10: [mem 0x000c0000-0x000cffff] could not be reserved
system 00:10: [mem 0x000e0000-0x000fffff] could not be reserved
system 00:10: [mem 0x00100000-0xbfffffff] could not be reserved
system 00:10: [mem 0xfed90000-0xffffffff] could not be reserved
system 00:10: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp: PnP ACPI: found 17 devices
ACPI: ACPI bus type pnp unregistered
PnPBIOS: Disabled
.
.firewire_core: created device fw0: GUID 001e8c0000c3e85e, S400
scsi 8:0:0:0: Direct-Access SMSC 223 U HS-CF 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:1: Direct-Access SMSC 223 U HS-MS 1.95 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdc] Attached SCSI removable disk
scsi 8:0:0:2: Direct-Access SMSC 223 U HS-SM 1.95 PQ: 0 ANSI: 0
scsi 8:0:0:3: Direct-Access SMSC 223 U HS-SD/MMC 1.95 PQ: 0 ANSI: 0
scsi 0:0:0:0: Attached scsi generic sg0 type 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:1: Attached scsi generic sg4 type 0
sd 8:0:0:2: Attached scsi generic sg5 type 0
sd 8:0:0:3: Attached scsi generic sg6 type 0
sd 8:0:0:1: [sdd] Attached SCSI removable disk
sd 8:0:0:3: [sdf] Attached SCSI removable disk
sd 8:0:0:2: [sde] Attached SCSI removable disk
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Adding 2047996k swap on /dev/sda2. Priority:-1 extents:1 across:2047996k
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1)
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
r8169 0000:02:00.0: setting latency timer to 64
r8169 0000:02:00.0: irq 41 for MSI/MSI-X
r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xef6aa000, e0:cb:4e:3e:0f:9a, XID 083000c0 IRQ 41
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64

Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 4972k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
audit: initializing netlink socket (disabled)
type=2000 audit(1325434521.469:1): initialized
highmem bounce pool size: 64 pages
.
.
vesafb: framebuffer at 0xf9000000, mapped to 0xef480000, using 1875k, total 14336k
vesafb: mode is 800x600x16, linelength=1600, pages=2
vesafb: protected mode interface info at c000:b840
vesafb: pmi: set display start = c00cb8a3, set palette = c00cb8fe
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 100x37
fb0: VESA VGA frame buffer device
intel_idle: MWAIT substates: 0x1120
intel_idle: v0.4 model 0x25
intel_idle: lapic_timer_reliable_states 0xffffffff
ERST: Table is not found!
isapnp: Scanning for PnP cards...
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Linux agpgart interface v0.103
brd: module loaded
i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
Registering the dns_resolver key type
Using IPI No-Shortcut mode
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
psmouse serio1: ID: 10 00 64
isapnp: No Plug & Play device found
Refined TSC clocksource calibration: 3209.959 MHz.
Switching to clocksource tsc
input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input1
registered taskstats version 1
rtc_cmos 00:03: setting system clock to 2012-01-01 16:15:23 UTC (1325434523)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 512k freed
.
.
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module 290.10 Wed Nov 16 19:27:25 PST 2011
.
.
hda-codec: no NID for mapping control Independent HP:0:0
NET: Registered protocol family 10
r8169 0000:02:00.0: eth0: link down
r8169 0000:02:00.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
r8169 0000:02:00.0: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
NET: Registered protocol family 17
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip6_tables: (C) 2000-2006 Netfilter Core Team
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
ip_set version 4 loaded
ctnetlink v0.93: registering with nfnetlink.
ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
xt_time: kernel timezone is +1100
u32 classifier
Actions configured
netfilter PSD loaded - (c) astaro AG
IFWLOG: register target
usbcore: registered new interface driver snd-usb-audio
eth0: no IPv6 routers present
ata2.00: configured for UDMA/133
ata2: EH complete
EXT4-fs (sda1): re-mounted. Opts: commit=0
EXT4-fs (sda3): re-mounted. Opts: commit=0
[root@localhost ~]#

I have yet to try disabling IDE in BIOS (thanks NetSpec) until I read up a bit more o it

Other than that, I'm stumped.

Re: Wicked hardware problem - freezing {Solved - I hope}

GregS — Sun Jan 01, 2012 3:01 am

Author: GregS

Posted: Sun Jan 01, 2012 3:01 am

nelz wrote:

You don't build a kernel from scratch, you start with the existing configuration and tweak it. But trying to do this on flakey hardware is asking for massive hair loss. A modified kernel won't fix broken hardware.

Run memtest overnight, give all components a yank and spank as DM suggested. If the problem persists, try a different PSU. Dodgy power supplies can not only cause random hardware problems, they also cause hardware damage. Cheap PSUs are never a wise investment.

Thanks nelz.

So far, memtest shows no errors.

Next thing is to open the box and see what comes of that.

I'll keep you posted (once I get back from holidays...)

Re: Wicked hardware problem - freezing {Solved - I hope}

nelz — Thu Dec 29, 2011 9:32 am

Author: nelz

Posted: Thu Dec 29, 2011 9:32 am

You don't build a kernel from scratch, you start with the existing configuration and tweak it. But trying to do this on flakey hardware is asking for massive hair loss. A modified kernel won't fix broken hardware.

Run memtest overnight, give all components a yank and spank as DM suggested. If the problem persists, try a different PSU. Dodgy power supplies can not only cause random hardware problems, they also cause hardware damage. Cheap PSUs are never a wise investment.

Re: Wicked hardware problem - freezing {Solved - I hope}

Dutch_Master — Thu Dec 29, 2011 6:19 am

Author: Dutch_Master

Posted: Thu Dec 29, 2011 6:19 am

I'd suggest re-seating the various components on your mainboard first, before rushing out for a new mainboard. And it wouldn't hurt blowing the dust way with a can of pressured air either... If you have more then one stick of memory, try removing one to see if the stability improves. If it doesn't, swap the memory sticks (one out, the other in). As memory sticks are cheaper then a new mainboard, get yourself one (of an arbitrary size, say 1 GB) and try with that. Next in line is the PSU: if it fries, it may take the internal components with it by spiking a high voltage on the internal power lines. If you have another PSU available, swap it to see if that results in a stable system again (mind, it could be too late anyway!)...

If any or all of the above scares you, find yourself a decent computer shop that offers such a service and have it checked over. Or perhaps a local computer club, even if they only 'do' Win-OS...

As for the script: it's pretty much "ready to run", just install the required packages (build-essential and libncurses5-dev). Oh, and comment out (or remove) the 'make oldconfig' line, then remove the # in front of the 'make menuconfig' line to have a somewhat newbee friendly interface for configuring the kernel

Re: About your Issue.

GregS — Thu Dec 29, 2011 5:26 am

Author: GregS

Posted: Thu Dec 29, 2011 5:26 am

supermine290 wrote:

First off it does sound like a hardware issue. I have had issues with Nividia cards and there are some tricks/proper ways to get them working on certain problematic distros. It in all honesty almost sounds like your motherboard is starting to fail. Since you said you switched keyboards and mouse and it did not fix your issue.

So unless you want to roll your own kernel there are things you can check before you go out and buy a new motherboard. The first thing you can do is right after it flakes can you get the keyboard and mouse working if you reboot? If you can't reboot (A hard shutdown then power up not just the reboot command) with them unplugged and then do that again with them plugged in to see if you can get them working again. If you can right after it run this command.

Code:

cat /var/log/messages || tail

Code:

cat /var/log/dmesg || tail

dmesg may need to be run as sudo.

These commands will show you the ending few lines of the messages and dmesg log file. Look through those for anything that is throwing a error ,or post here so I/We can look through it. that should let you know if it is really a hardware issue and if so where it could possible be.

I believe in trying to figure out what the issue is first and if it is really hardware that is failing ,or if it is a bug in the kernel. Because if it is a hardware failing issue a new kernel build would not do anything but waste your time(which being in the army I know can be scarce). I have been using Linux for a long time and I have had similar issues myself.

I look forward to your response.

Thanx.

When I can boot it up without hitting it, I'll try this.

System crashes out anywhere from almost immediately after startup to half an hour of working OK. Mouse pointer freezes, keyboard also; neither able to input ergo REISUB won't close down. My box has a reboot button (momentary power interrupt I guess) so I use that and it reboots and (usually) works OK until next crash.

Building a kernal from scratch is going to be last resort of desperation - i think i'd prefer to just buy a new box first.

Even with the help given by Dutch Master (thanx for that too) there are still too many variables / unknowns /assumed knowledge that, without direct access to some sort of support, I'm not game to try and work through.

More to follow...

About your Issue.

supermine290 — Wed Dec 28, 2011 12:09 pm

Author: supermine290

Posted: Wed Dec 28, 2011 12:09 pm

First off it does sound like a hardware issue. I have had issues with Nividia cards and there are some tricks/proper ways to get them working on certain problematic distros. It in all honesty almost sounds like your motherboard is starting to fail. Since you said you switched keyboards and mouse and it did not fix your issue.

So unless you want to roll your own kernel there are things you can check before you go out and buy a new motherboard. The first thing you can do is right after it flakes can you get the keyboard and mouse working if you reboot? If you can't reboot (A hard shutdown then power up not just the reboot command) with them unplugged and then do that again with them plugged in to see if you can get them working again. If you can right after it run this command.

Code:

cat /var/log/messages || tail

Code:

cat /var/log/dmesg || tail

Re: Wicked hardware problem - freezing {Solved - I hope}

Dutch_Master — Wed Dec 28, 2011 5:13 am

Author: Dutch_Master

Posted: Wed Dec 28, 2011 5:13 am

Here's a quick guide for building your own kernel, based on a Debian 6 (Squeeze) system, or derivative (Ubuntu, Mint, etc).

First, install the build-essential package. Next, create a text file containing the following: (HINT: copy/paste!)

Code:

#! /bin/bash
#
# Small script for building a new 3.1 kernel
# Requires minor editing for latest stable kernel version
# The make install and mkinitramfs steps requires root permissions. It is assumed you have
# the Debian build-essential package and its dependencies installed.
# This script is released under the GPL: http://www.gnu.org/copyleft/gpl.html

# To keep things tidy a new directory is created. Remove both lines if you don't want this.

mkdir ~/kernel
cd ~/kernel

# edit these lines to represent the latest stable kernel from the kernel.org guys

wget -qhttp://www.kernel.org/pub/linux/kernel/v3.0/linux-3.1.6.tar.bz2
tar -xjf linux-3.1.6.tar.bz2
cd linux-3.1.6

# this part may fail if the new kernel has features not supported in the old one.
# Run manually and accept all defaults, then comment out the next line with a # in front

make oldconfig

# Alternatively, if you never build a kernel before, comment out the above line and remove
# the comment from the one below.
# Note: it requires the libncurses5-dev package to be installed first!
# It offers a text-based menu for configuring the kernel.
# Use the spacebar, arrow and enter keys to navigate and select options.

# make menuconfig

# This is the part that does the actual work

make && make modules && make modules_install && make install && mkinitramfs -o /boot/initrd.img-3.1.6 3.1.6

# The last portion of the above line should be edited if another kernel version is used!

# Now you need to edit your bootloader to add the new kernel.
# After you've done that, and checked thoroughly twice, it's time to reboot into your new kernel.
# If Grub 2 is installed, which it is when you've installed Debian Squeeze from scratch, remove
# the comment hash of the next line, it automagically updates the grub menu to include the new kernel.
# update-grub

exit 0

Save it as kernel-build.txt in your home directory. Edit the file if you want to store the (unpacked) source elsewhere on your system. If you think you're done, create a copy and save it as kernel-build.sh and make it executable:

Code:

chmod +x kernel-build.sh

Now is the big moment: run the script! (mind: as root!)

Code:

sh ./kernel.sh

If you've chosen the "make menuconfig" option, it'll pop up automagically and the script won't resume before you've finished configuring it. Depending on the amount of other work you do while it performs the magic, expect a total compile time of about an hour minimum.

This is the most reliable way of building and installing a new kernel under Debian. debian has several tools to build a kernel package that can be installed with its own package management system (dpkg) but do far I have not succeeded in getting the d*mn thing to work! Others have reported success with that method though.

The script above owes a lot to the chap behind the digitalhermit.com website, but it's now unreachable...

Re: Wicked hardware problem - freezing {Solved - I hope}

GregS — Tue Dec 27, 2011 11:22 pm

Author: GregS

Posted: Tue Dec 27, 2011 11:22 pm

Dutch_Master wrote:

Did it occur to you that it might be a hardware issue? Does the mainboard have onboard graphics? If it does, give it a whirl. Otherwise, try Debian Stable and roll in your own kernel (it's not that difficult, honest!) and the nVidia drivers. Mind, do get the latest stable kernel from the kernel.org guys (3.1 and up), don't bother with the 2.6.32.whatever sources in the Debian repo's!

Thanks.

I'm almost certain it is hardware - Mint just gave up the ghost, so I rolled out the latest (LXF 149) PCLinuxOS (which I've had success with on a Dell box that doesn't take kindly to most other distros) and it is freezing as well.

Don't think there is an on-board graphics; I had the nvidia card fitted when the box was built and it is the only video connector plug showing.

WRT 'roll your own kernel', I'm sure it is not difficult if you know exact what you're doing...but like most things Linux, there is a dearth of comprehensible instruction available to me to do it with.

Also, my nearest LUG is around 100km distant since I moved onto base here (Army) so I am no longer able to get support from that angle; I'm effectively on my own ergo attempting to harvest the accumulated wisdom of this place!

Additionally, SWMBO demands minimal downtime (doesn't even understand the need for routine updates tieing up 'her' PC) so i don't have a lot of time to fiddle.

Re: Wicked hardware problem - freezing {Solved - I hope}

Dutch_Master — Tue Dec 27, 2011 6:18 am

Author: Dutch_Master

Posted: Tue Dec 27, 2011 6:18 am

Did it occur to you that it might be a hardware issue? Does the mainboard have onboard graphics? If it does, give it a whirl. Otherwise, try Debian Stable and roll in your own kernel (it's not that difficult, honest!) and the nVidia drivers. Mind, do get the latest stable kernel from the kernel.org guys (3.1 and up), don't bother with the 2.6.32.whatever sources in the Debian repo's!

Wicked hardware problem - freezing {Solved - I hope}

GregS — Tue Dec 27, 2011 4:44 am

Author: GregS

Posted: Tue Dec 27, 2011 4:44 am

I seem to have a persistent hardware(?) problem...I am encountering regular freezing (both mouse and keyboard, can't even REISUB) and I cannot locate a source of the problem.

This has manifested since about Fedora 9 (IIRC the last distro that worked flawlessly; I upgraded about 12 months after it ceased to be supported as it was getting flaky (which begs another question: why does every distro I've used fall on it's sword once it is out of support???).

I have tried Fedora 10 & 11, but neither would work with my nvidia card; several other distros from the montly DVD, some of which sort-of worked and others wouldn't even install, finally settling on Ubuntu (nothing after 9.04 would work reliably) which did at least configure the nvidia card and work OK.

Now that has recently ceased to function (malloc errors with XSane, several users getting black screens on login to KDE 4.x) and of course no longer maintained so unable to update or add software.

I have tried CentOS and Mint from recent coverdisks, but now I'm getting persistently the same problem that caused me to drop Fedora (I'd been exclusively using Red Hat since RH 9) in the first place.

I have been using Fedora fro the coverdisks fairly seamlessly on a Toshiba laptop for some years (now on 15) without problems, although I don't use the wireless modem fitted.

Computer specs are ASUS P7P557 board, Intel Core i5 650@ 3.20GHz dual-core processor, 4 GB RAM and nVidia G92 [GeForce GTS 250]; and bog-standard keyboard and optical mouse (replacing PS2 ball mouse which I first thought may have been the problem).

I'm nearing wit's end; I have tried a swag of mainstream distros and (of those that would install) all have manifested about the same fault, some immediately and others after a period of acceptable performance.

It would seem, therefore, to be hardware-related, but I'm not in a position to swap out components to find out which may be the culprit.

I have also considered a hardware-customised distro such as Gentoo, but I don't have enough knowledge about the inner workings of Linux to be able to configure it. I got most of the way through the how-to in LXF139 and decided it wasn't for me.

I don't mind the CLI - been using it since CP/M - but the esoteric arcana of config file editing is beyond me without a detailed, step-by-step 'Dummies' reference to work from and what I have seen from the available information convinces me that I have neither the secret sign nor the handshake...

Is there any suitable diagnostic tool that may help identify the problem?

Would a simplistic distro like Puppy be more bullet-proof.

Any suggestions?
==================================
Updated 14 Jan:
Changed out PS2 keyboard and rodent for USB types (had only PS2 to check with previously) and problem seems to have been solved(?) - looks like the PS2 connector on the motherboard has a fault?!