what exactly could be
causing this bizarre behavior ? If this is of any help, the exact model
number of the HD is MAXTOR 4K040H2 and I was using UFS2 on both
drives. Thanks in advance.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http
the system in a
severely broken state. And even if it did not, data corruption would
happen again in 8-12 days.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
but no
errors were found.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Obviously, /dev/smb is still nowhere to be seen :(
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
mean that my kernel is not compiled with
smbus support (would be weird) or that sysutils/consolehm is compiled
with smbus support disabled (I don't see any appropriate make options in
the port Makefile) ? Thank you for your time.
Sincerely,
Dan Naumov
P.S: if the full dmesg output is needed, I
even though I have device smb in my kernel config. I've also noticed a
line saying pci0: serial bus, SMBus at device 7.4 (no driver
attached) in my dmesg.
So it's no intpm hardware.
What drivers should I be using then ? I had lm_sensors on Linux work
with this hardware...
Sincerely,
Dan
config on, but if any of
you people want them, I can send them attached to a private mail.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
-pthread
when compiling them from source myself. Not in the slightest. This is
BAD BAD BAD for usability.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Tue, 2003-09-23 at 23:25, Dan Naumov wrote:
On Tue, 2003-09-23 at 23:13, Daniel Eischen wrote:
I understand that folks want to wave their hands and say just make
-pthread work and do whatever it needs to.
I am one of those folks as well. As an end-user, I am not interested in
hacking
]
===
Is this something I should worry about ?
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
?
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Mon, 2003-09-22 at 00:42, Daniel Eischen wrote:
We've already been over this before. The problem is not
as bad as you think, and there are other platforms that
don't have -pthread.
And those platforms would be?
Sincerely,
Dan Naumov
___
[EMAIL
On Sat, 2003-09-20 at 12:32, David R. Colyer wrote:
Is atapicam a kernel config option?
[14:11]-[jago]-[~]: cat /usr/src/sys/i386/conf/JAGO | grep atapicam
#device atapicam# BROKEN in -CURRENT !!!
Hope this helps.
Sincerely,
Dan Naumov
Hello
Seeing as -pthread support has been removed from -CURRENT breaking
_LOTS_ of ports, is it possible to get it back into a local source
tree ? If so, how ? Thanks in advance.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http
On Sun, 2003-09-21 at 04:09, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Doug Barton [EMAIL PROTECTED] writes:
: I'd really like to see this change backed out, at minimum until the
: ports freeze is over.
My thoughts exactly.
Sincerely,
Dan Naumov
NVIDIA GeForce4 Ti4200 (I tried both avaible driver sets)
Creative SB128 PCI
Lite-On DVD/CDRW Combo Drive LTC-48161H
Maxtor 40 GB HD
Seagate 16 GB HD
Thanks in advance.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
I forgot to add that excessive heat and faulty ram are ruled out, I've
checked system temp and it seems to be OK, memtest has also passed all
tests completely without giving any errors. It *COULD* theoretically be
the HD going bad, but how could I possibly check this?
Sincerely,
Dan Naumov
, today's -CURRENT
fails to boot (both single- and multiuser). It gets stuck right after:
acd0: CDRW LITE-ON COMBO LTC-48161H at ata1-master PIO4
Disabling atapicam in the kernel or detaching the drive from the system
works around the problem.
Sincerely,
Dan Naumov
just
let things be as they are ?
Sincerely,
--
Dan Naumov [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
the installation of a NetBSD system. I think it's a good
idea.
Sincerely,
--
Dan Naumov [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
them avaible through ports. But
that's all IMHO and not very likely to happen to FreeBSD in my lifetime
;)
Sincerely,
--
Dan Naumov [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
,
--
Dan Naumov [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
3.2.1 for a long
time and everything compiled absolutely fine. This leads me to believe
that there are not only arch-specific, but also OS-specific GCC issues.
Can anyone else confirm this ?
Sincerely,
--
Dan Naumov [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
23 matches
Mail list logo
