Date: Fri, 29 May 2009 19:00:14 GMT From: Ralf Folkerts <ralf.folkerts@gmx.de> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/135040: FreeBSD/amd64 does not (always) detect disk on SB600/AliveXFire eSata 2 Message-ID: <200905291900.n4TJ0Dxo061504@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/135040; it has been noted by GNATS.
From: Ralf Folkerts <ralf.folkerts@gmx.de>
To: bug-followup@FreeBSD.org, ralf.folkerts@gmx.de
Cc:
Subject: Re: amd64/135040: FreeBSD/amd64 does not (always) detect disk on
SB600/AliveXFire eSata 2
Date: Fri, 29 May 2009 20:56:55 +0200
Hi Alexander and John,
the Systems seems to work OK now! Thanks for the fast responses!
The hw.physmem works 1a; put it into loader.conf (after entering manual
for the first boot) and it really works fine.
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-STABLE #0: Sat May 23 17:58:51 CEST 2009
root@:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) Dual Core Processor 5050e (2593.00-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x2001<SSE3,CX16>
AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
TSC: P-state invariant
Cores per package: 2
usable memory = 3475714048 (3314 MB)
avail memory = 3353473024 (3198 MB)
I finished two buildworld/buildkernel/installworld/installkernel now,
running cvsup of ports and also some other tasks in parallel - no
Problem. Now I put my "normal" Disk back in and will try a portupgrade.
Well, it does work OK for me now (it seems). However, is there a chance
to get this problem circumvented (in case its a Hardware-Bug) or solved
(in case there is something not working OK in a driver) or maybe even
both? If so, could I help? How?
Cheers,
_ralf_
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905291900.n4TJ0Dxo061504>