On Fri, Sep 19, 2003 at 08:02:31AM +0200, Soren Schmidt wrote:
It seems Jan Srzednicki wrote:
As far as problems with dagrab and cdda2wav are conserned - this is
because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread
What's happened to CDIOCREADAUDIO friends)
I've
Hello there,
I still have problems with ATAng, with kernel from 15th of September.
First of all, the drive still does not get detected properly. Funny
thing is that after some playing with atacontrol attach/detach, it
finally gets detected. And later on, it is normally detected, before.
Same
Hello,
I'm getting the following warning when running xmms with libthr:
Warning: pid 589 used static ldt allocation.
See the i386_set_ldt man page for more info
When I use libkse, I don't get this warning. As I understand, someone's
is hunting down static LDT usage, so here's my feedback. ;)
On Thu, Sep 18, 2003 at 03:54:36PM +0200, Soren Schmidt wrote:
It seems Jan Srzednicki wrote:
First of all, the drive still does not get detected properly. Funny
thing is that after some playing with atacontrol attach/detach, it
finally gets detected. And later on, it is normally detected
On Thu, Sep 18, 2003 at 11:46:35AM -0500, Steve Ames wrote:
On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote:
Anyhow, what I need to be able to tell what may be going on, is that
you boot verbose and get me the output from dmesg from a boot that
found all device, and from a
On Fri, Sep 19, 2003 at 01:32:45AM +0300, Vladimir Kushnir wrote:
Um. Do you see the same crash if both drives contain CDs at boot time?
If not, this could be a consequence of the error condition corruption
problem others have been reporting.
Thomas.
These crashes started before
On Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new stuff
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
Hello,
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is giving up on buffers. During the next boot
all filesystems are checked because of improper dismount. Here follow
the
On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new
On Sun, Aug 31, 2003 at 04:57:57PM +0200, Soren Schmidt wrote:
It seems Jan Srzednicki wrote:
ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66
ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66
ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR
Hello sir,
I've just cvsupped the new -C source, and installed a new kernel. My
CD-RW could not be detected:
FreeBSD 5.1-CURRENT #7: Sun Aug 31 12:21:57 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOONDANCE
Preloaded elf kernel /boot/kernel/kernel at 0xc0545000.
Preloaded elf module
On Mon, 20 Jan 2003, David Schultz wrote:
First two entries clearly correspond to the missing file, which should
have been put in /home/lost+found. But, the poroblem is that no lost+found
directory was created, while it should (as fsck_ffs(8) says). I guess its
a bug, probably in the
On Wed, 22 Jan 2003, Garrett Wollman wrote:
Would that be a big problem to allow some fsck option not to erase all
these softupdates-pending inodes, but to put them in lost+found as usual?
It certainly couldn't be done with the background fsck, because
background fsck works on a snapshot
Hello,
After building new world and installing new kernel, I rebooted my machine
to launch a new kernel. The system mysteriously failed to flush 22 disk
buffers, and after reboot fsck was launched. I have the following
partitions:
/ - UFS1
/usr - UFS2
/home - UFS1
This massive disk mangling
On Sat, 30 Nov 2002, Manfred Antar wrote:
I guess dump is not ready for UFS2
I just have made dump and restore of my 3GB UFS2 /usr partition and did
not experience any problems with that. Working on -CURRENT from Nov 24th.
--
-- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE
On Sat, 30 Nov 2002, Matthias Schuendehuette wrote:
I just have made dump and restore of my 3GB UFS2 /usr partition and
did not experience any problems with that. Working on -CURRENT from
Nov 24th.
Sure you dumped an UFS2 filesystem?
Here's my try:
root@current - /root
104 # uname -a
On Sun, 1 Dec 2002, Jan Srzednicki wrote:
Hm, this is weird. I'm sure I have dumped an UFS2 filesystem earlier and
it worked. Now I get similar error messages as you. Yes, I'm absolutely
sure that the filesystem was UFS2 - played with extattrctl on it, checked
it with dumpfs and was not able
Hello there,
I have -CURRENT from Saturday on my box. I have SB 128PCI on my board, the
module detects it without problems and seems to work fine. But the problem
is that the sound is not clear; there happen to be some itchy noises from
time to time, when I push up the system load. I wonder
Hello there,
As UFS2 is not backward compatible at all, I wonder why the old fstype in
disklabel is being kept:
#size offsetfstype [fsize bsize bps/cpg]
a: 102400004.2BSD 2048 16384 64008 # (Cyl.0 - 63*)
c: 186103260unused0 0
19 matches
Mail list logo
