Re: 2008.0 on ECS AMD690GM-M2 motherboard - help! - Mandriva
This is a discussion on Re: 2008.0 on ECS AMD690GM-M2 motherboard - help! - Mandriva ; On Feb 18, 4:46 pm, dmat...@sbcglobal.net wrote:
> Trying to set up a new system for htpc. ECS AMD690GM-M2 motherboard,
Well, not too much progress. Booted from rescue CD and set
"debug" in /etc/udev/udev.conf. Also modified lilo various ways
but ...
-
Re: 2008.0 on ECS AMD690GM-M2 motherboard - help!
On Feb 18, 4:46 pm, dmat...@sbcglobal.net wrote:
> Trying to set up a new system for htpc. ECS AMD690GM-M2 motherboard,
Well, not too much progress. Booted from rescue CD and set
"debug" in /etc/udev/udev.conf. Also modified lilo various ways
but this was as good as any (acpi=force and leaving acpi off did not
get very far):
failsafe acpi=off notsc console=tty0 console=ttyS0,38400
and booted that with a laptop logging off the serial line. Before
doing so made these BIOS changes:
load optimized defaults
DRAM timing mode auto -> maxmemclk
memory clock ddr2 400 -> ddr2 800
spread spectrum disabled -> enabled (the SATA disk jumper is off,
so it is set to SS enabled.)
changed the boot order to CD, Disk, Nothing
boot other device enabled -> disabled
full screen logo enabled ->disabled
fdc controller enabled -> disabled (no floppy in system)
init display first pci slot -> onboard (onboard is only display)
ACPI xsdt disabled -> enabled
HPET support, left it at enabled. (in previous attempts it was
disabled)
ran memtest for a while, no errors,.
There
were thousands and thousands of lines of udev output ending with this
and stepping from there right into some sort of failed disk access. It
looks like all sorts of udevd processes went into the background and
some of them pop up later.
udevd-event[1837]: run_program: '/sbin/pam_console_apply' returned
with status 0
udevd-event[1837]: pass_env_to_socket: passed -1 bytes to socket '/org/
freedesktop/hal/udev_event',
udevd-event[1837]: pass_env_to_socket: passed -1 bytes to socket '/org/
kernel/udev/monitor',
udevd-event[1837]: udev_event_run: seq 1448 finished with 0
udevd[866]: udev_done: seq 1448, pid [1837] exit with 0, 18 seconds
old
udevsettle[880]: main: timeout waiting for queue
Wait timeout. Will continue in the background.udevd[866]:
get_ctrl_msg: udevd message (ENV) received, unset 'STARTUP'
udevd[866]: get_ctrl_msg: udevd message (ENV) received, unset
'MODPROBE_DEBUG'
[FAILED]
EXT3-fs error (device sda5): ext3_get_inode_loc: <6>sd 2:0:0:0: [sda]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_O
K
EXT3-fs error (device sda5): ext3_find_entry: reading directory
#1184903 offset 0
EXT3-fs error (device sda5): ext3_get_inode_loc: unable to read inode
block - inode=831810, block=1671307
EXT3-fs error (device sda5): ext3_get_inode_loc: unable to read inode
block - inode=831810, block=1671307
EXT3-fs error (device sda5): ext3_get_inode_loc: unable to read inode
block - inode=828263, block=1671196
udevd-event[1692]: run_program: EXT3-fs error (device sda5):
ext3_get_inode_loc: exec of program unable to read inode block -
inode=
828975, block=1671218'/lib/udev/cdrom
_id' failed
udevd-event[1763]: run_program: exEXT3-fs error (device sda5):
ext3_get_inode_loc: ec of program '/unable to read inode block - inod
e=828970, block=1671218sbin/alsa.agent'
failed
udevd-EXT3-fs error (device sda5): ext3_get_inode_loc: event[1689]:
rununable to read inode block - inode=828785, block=1671212_prog
ram: '/lib/
udev/cdrom_id' returned with staEXT3-fs error (device sda5):
ext3_find_entry: tus 1
udevd-evreading directory #1184357 offset 0ent[1689]: udev_
rules_get_name: EXT3-fs error (device sda5): ext3_get_inode_loc: rule
applied, 'sunable to read inode block - inode=828975, block=16
71218r0' becomes 'sr0
'
udevd-event[EXT3-fs error (device sda5): ext3_get_inode_loc: 1689]:
run_progrunable to read inode block - inode=828970, block=167121
8am: 'cdrom_id --
export /dev/.tmpEXT3-fs error (device sda5): ext3_get_inode_loc:
-11-0'
udevd-eunable to read inode block - inode=828785,
block=1671212vent[1748]: run_
program: '/sbin/EXT3-fs error (device sda5): ext3_get_inode_loc:
alsa.agent' retuunable to read inode block - inode=861256, block=17
36749rned with status
1
udevd-event[1748]: udev_event_run: seq 1471 finished with -1
udevd[866]: udev_done: seq 1471, pid [1748] exit with 1, 134 seconds
old
udevd-event[1750]: run_program: '/lib/udev/net_create_ifcfg' returned
with status 0
udevd-event[1750]: run_progEXT3-fs error (device sda5):
ext3_get_inode_loc: ram: 'net_actionunable to read inode block -
inode=76281
etc. etc. It was all very nasty after this.
The bizarre thing is after booting from the rescue disk (acpi=off,
text mode) there is no problem whatsoever with the disks. I ran
e2fsck
on both partitions (sda1 = /boot, sda5 = /) and there were no errors.
I also noticed that the rescue CD was only running on one processor,
its dmesg showed this:
Booting processor 1/1 eip 3000
Not responding
Inquiring remote APIC #1
... APIC #1 ID: 1000000
.... APIC #1 VERSION: 80050010
.... APIC #1 SPIF: ff
CPU #1 not responding - cannot use it.
So maybe the CPU is broken, but no way to tell really unless I load
windows
or get some other version of Linux running.
Here is everything before the udev started
Linux version 2.6.22.9-desktop-1mdv (lcapitulino@n5.mandriva.com) (gcc
version 4.2.2 20070909 (prerelease) (4.2.2-0.RC.1mdv2008.0))
#1 SMP Thu Sep 27 04:07:04 CEST 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000037fe0000 (usable)
BIOS-e820: 0000000037fe0000 - 0000000037fe3000 (ACPI NVS)
BIOS-e820: 0000000037fe3000 - 0000000037ff0000 (ACPI data)
BIOS-e820: 0000000037ff0000 - 0000000038000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
895MB LOWMEM available.
found SMP MP-table at 000f3c80
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229344
HighMem 229344 -> 229344
early_node_map[1] active PFN ranges
0: 0 -> 229344
DMI 2.5 present.
ATI board detected. Disabling timer routing over 8254.
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 6:8 APIC version 17
Processor #1 6:8 APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 2
Allocating PCI resources starting at 40000000 (gap: 38000000:a8000000)
swsusp: Registered nosave memory region: 000000000009f000 -
00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 -
00000000000f0000
swsusp: Registered nosave memory region: 00000000000f0000 -
0000000000100000
Built 1 zonelists. Total pages: 227553
Kernel command line: BOOT_IMAGE=test root=805 failsafe acpi=off notsc
console=tty0 console=ttyS0,38400
notsc: Kernel compiled with CONFIG_X86_TSC, cannot disable TSC.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 2099.950 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 904220k/917376k available (2139k kernel code, 12132k reserved,
691k data, 280k init, 0k highmem, 0k BadRAM)
virtual kernel memory layout:
fixmap : 0xffe16000 - 0xfffff000 (1956 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf7fe0000 ( 895 MB)
.init : 0xc03ca000 - 0xc0410000 ( 280 kB)
.data : 0xc0316d67 - 0xc03c3c84 ( 691 kB)
.text : 0xc0100000 - 0xc0316d67 (2139 kB)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay using timer specific routine.. 4311.66 BogoMIPS
(lpj=2155831)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0(2) -> Core 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Early unpacking initramfs... done
Freeing initrd memory: 499k freed
CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Not responding.
Inquiring remote APIC #1...
.... APIC #1 ID: 1000000
.... APIC #1 VERSION: 80050010
.... APIC #1 SPIV: ff
CPU #1 not responding - cannot use it.
Total of 1 processors activated (4311.66 BogoMIPS).
ExtINT not setup in hardware but reported by MP table
ENABLING IO-APIC IRQs
...TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
Brought up 1 CPUs
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
PCI: PCI BIOS revision 3.00 entry at 0xf9ff0, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PnPBIOS: Disabled
PCI: Probing PCI hardware
PCI: Transparent bridge - 0000:00:14.4
PCI->APIC IRQ transform: 0000:00:12.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:13.0[A] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:13.1[B] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:13.2[C] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:13.3[B] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:13.4[C] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:13.5[D] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:14.1[A] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:14.2[A] -> IRQ 17
PCI->APIC IRQ transform: 0000:01:05.0[A] -> IRQ 18
PCI->APIC IRQ transform: 0000:02:05.0[A] -> IRQ 22
PCI: Cannot allocate resource region 1 of device 0000:00:14.0
PCI: Bridge: 0000:00:01.0
IO window: e000-efff
MEM window: fdd00000-fdefffff
PREFETCH window: d8000000-dfffffff
PCI: Bridge: 0000:00:14.4
IO window: d000-dfff
MEM window: fdc00000-fdcfffff
PREFETCH window: fdf00000-fdffffff
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
audit: initializing netlink socket (disabled)
audit(1203454983.499:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
TCP cubic registered
NET: Registered protocol family 1
Using IPI No-Shortcut mode
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 280k freed
Red Hat nash version 4.2.17mdk sSCSI subsystem initialized
tarting
Loading scsi_mod.ko modahci 0000:00:12.0: controller can't do 64bit
DMA, forcing 32bit
ule
Loading libata.ko module
Loading ahci.ko module
Clocksource tsc unstable (delta = 195873339 ns)
input: ImPS/2 Generic Wheel Mouse as /class/input/input1
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl
SATA mode
ahci 0000:00:12.0: flags: ncq ilck led clo pmp pio
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 cmd 0xf880c100 ctl 0x00000000 bmdma 0x00000000
irq 16
ata2: SATA max UDMA/133 cmd 0xf880c180 ctl 0x00000000 bmdma 0x00000000
irq 16
ata3: SATA max UDMA/133 cmd 0xf880c200 ctl 0x00000000 bmdma 0x00000000
irq 16
ata4: SATA max UDMA/133 cmd 0xf880c280 ctl 0x00000000 bmdma 0x00000000
irq 16
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-7: WDC WD1600AAJS-60PSA0, 21.12M22, max UDMA/100
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/100
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATAPI: TSSTcorp CDDVDW SH-S203N, SB01, max UDMA/100
ata4.00: configured for UDMA/100
scsi 2:0:0:0: Direct-Access ATA WDC WD1600AAJS-6 21.1 PQ: 0
ANSI: 5
scsi 3:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S203N SB01 PQ: 0
ANSI: 5
Loading ata_piixsd 2:0:0:0: [sda] 312581808 512-byte hardware sectors
(160042 MB)
..ko module
Loadsd 2:0:0:0: [sda] Write Protect is off
ing sd_mod.ko mosd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
dule
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2 < sda5 sda6 >
sd 2:0:0:0: [sda] Attached SCSI disk
Loading scsi_wait_scan.ko moduleEXT3-fs: INFO: recovery required on
readonly filesystem.
Loading jbd.koEXT3-fs: write access will be enabled during recovery.
module
Loading ext3.ko module
Mounting /proc filesystem
Mounting sysfs
Creakjournald starting. Commit interval 5 seconds
ting device fileEXT3-fs: recovery complete.
s
Mounting tmpfEXT3-fs: mounted filesystem with ordered data mode.
s on /dev
Creating root device
No resume device specified
Trying userspace resume from suspend.conf file
No resume device in suspend.conf
echo: cannot open /sys/power/suspend2/do_resume for write: 2
echo: cannot open /sys/power/tuxonice/do_resume for write: 2
Mounting root filesystem /dev/root with flags relatime
Switching to new root
unmounting old /proc
unmounting old /sys
INIT: version 2.86 booting
Setting default font (lat0-16): [ OK ]
Welcome to Mandriva Linux 2008.0
Press 'I' to enter interactive startup.
Configuring kernel parameters: [ OK ]
Setting clock (utc): Tue Feb 19 13:03:12 PST 2008 [ OK ]
Starting udev:
Anything stand out as a fixable error or the source of these problems?
Thanks,
David Mathog
-
Re: 2008.0 on ECS AMD690GM-M2 motherboard - help!
On Feb 19, 10:03 pm, dmat...@sbcglobal.net wrote:
There was also an IRQ disabled in these runs, it showed up in the log
file as:
udevd[866]: udev_done: seq 1365, pid [1600] exit with 0, 3 seconds old
udevd[866]: udev_done: seq 1368, pid [1608] exit with 0, 2 seconds old
udevd[866]: udev_done: seq 1369, pid [1609] exit with 0, 2 seconds old
udevd[866]: udev_done: seq 1377, pid [1623] exit with 0, 1 seconds old
udevd[866]: udev_done: seq 1379, pid [1625] exit with 1, 1 seconds old
udevd[866]: udev_done: seq 1380, pid [1626] exit with 1, 1 seconds old
udevd[866]: udev_event_run: seq 1366 forked, pid [1652], 'add' 'pci',
2 seconds old
udevd-event[1653]: run_program: '/sbin/modprobe
pci:v000010ECd00008167sv00001019sd00008167bc02sc00 i00'
udevd[866]: udev_event_run: seq 1381 forked, pid [1653], 'add' 'pci',
1 seconds old
udevd-event[1655]: run_program: '/sbin/modprobe
pci:v00001022d00001102sv00000000sd00000000bc06sc00 i00'
udevd[866]: udev_event_run: seq 1384 forked, pid [1655], 'add' 'pci',
0 seconds old
udevd-event[1657]: run_program: '/sbin/modprobe
pci:v00001022d00001103sv00000000sd00000000bc06sc00 i00'
udevd[866]: udev_event_run: seq 1385 forked, pid [1657], 'add' 'pci',
0 seconds old
udevd[866]: udev_event_run: seq 1386 forkDisabling IRQ #16
Whatever that means.
Regards,
David Mathog
-
Re: 2008.0 on ECS AMD690GM-M2 motherboard - help!
On Wed, 20 Feb 2008 01:03:19 -0500, wrote:
> There
> were thousands and thousands of lines of udev output ending with this
> and stepping from there right into some sort of failed disk access. It
> looks like all sorts of udevd processes went into the background and
> some of them pop up later.
I'd try booting into run level 1 withthe following kernel boot paramaters
1,nopinit,debug,loglevel=8,noisapnp,nosmp
Another possibility is that the sata kernel module is not being installed
in initrd.
Boot from the rescue cd, and run "lsmod |grep sata".
Run mkintrd with --with=sata_module.
Regards, Dave Hodgins
--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
-
Re: 2008.0 on ECS AMD690GM-M2 motherboard - help!
David W. Hodgins wrote:
> Boot from the rescue cd, and run "lsmod |grep sata".
> Run mkintrd with --with=sata_module.
Bizarrely, I could not identify a unique "SATA" module.
Here's the story. An old IDE disk was added to the system
and 2008.0 installed on it, then
booted from that installation. At the udev stage it sat there for
just over 3 minutes and then finished booting to failsafe. That's at
least better than the SATA disk did. Sadly when the IDE based one
came up there was no /dev/sda. At least this time dmesg could be run
and it was clear that the disabled IRQ was for the SATA controller.
So look for different modules in the two states, because the rescue
CD could mount either IDE or SATA:
1. On the IDE boot: lsmod > /root/lsmod_ide.txt
2. Boot rescue CD: lsmod > /mount_point_for_ide/root/lsmod_rescue.cd
Then compared the two files. There were a few more file system types in
the rescue one, and some sound drivers in the IDE one, but otherwise all
the modules were the same! They were, however, listed in different
orders. Ugh, module load order problem, I'm NOT going there. If anyone
cares, it appeared that the most likely problem was the way sd_mod and
sr_mod loaded.
So back to the BIOS. The SATA controller has 4 modes, the default was
"Native IDE" so I tried changing it to "AHCI". Reboot from IDE, still
getting disable on IRQ#16. But dmesg said to try irqpoll, and that
helped. Finally managed to get a mostly clean boot on the IDE disk with:
kernel parameters: acpi=off irqpoll
BIOS: SATA controller at AHCI
This went through the udev in just a couple of seconds. Those settings
worked as well for the SATA disk. So some progress, at least now it
is possible to boot to running Mandriva 2008.0.
On the minus side...
1. It still only recognizes a single CPU, not both.
2. still have to use acpi=off or it will lock on any boot, rescue or
Mandriva 2008.0. For 2008.0 it always stops at:
Net: Registered Protocol family 2
(Anybody have a guess why it stops there???)
Tonight I'll try the latest Kernel, hopefully that will resolve both of
those remaining issues and I can move on to the "easy" stuff, like
getting the graphics to work on this card. Mandriva 2008 tried to
configure the graphics but did not succeed. Hopefully the proprietary
ATI drivers will resolve that.
Regards,
David Mathog
-
Re: 2008.0 on ECS AMD690GM-M2 motherboard - help!
On Thu, 21 Feb 2008 12:01:19 -0500, David Mathog wrote:
> This went through the udev in just a couple of seconds. Those settings
> worked as well for the SATA disk. So some progress, at least now it
> is possible to boot to running Mandriva 2008.0.
What does lspci -vvv show for the sata controller?
Regards, Dave Hodgins
--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)