On Sat, 11 Dec 1999, Julian Elischer wrote:
> Linux have basically done this in their procfs.
If we're looking for a gross hack, we need look no further :-)
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]> Mike Smith writes:
: This is the usual poorly thought out argument, which fails to note that
: when you lose a disk you're already screwed due by /etc/fstab and the
: need to hard-mount local filesystems.
No. You aren't screwed. I have a system that needs /, /va
In message <[EMAIL PROTECTED]> Kenneth Wayne
Culver writes:
: For some reason rtc0 was not working, and I think it's because this
: variable was not initialized, here is the patch:
: -int statclock_disable;
: +int statclock_disable = 0;
There is no difference between these two statements (well
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: 2. Fix PCCARD on my laptop so I can suspend
What's the current issue? I have 0 problems suspending/resuming. I'd
like to know what is still broken, if anything, with the latest
-current.
: OR, I can work on the compiler and close my ope
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote:
: > And as for the device renaming, you didn't have to change anything from
: > sd->da. The old device names and nodes were supported in most every way.
:
: BUT not any long
Linux have basically done this in their procfs.
On Sat, 11 Dec 1999, Jordan K. Hubbard wrote:
> > Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and
> > then stat the directory nodes.
>
> AAIEE! sysctlfs!! :-)
>
> It's an interesting idea and I'm not sure why it a
> Since the recent block device vanishment, MAKEDEV all and my vinum
> volumes have failed to start.
Please read /usr/src/UPDATING if you're going to track -current
these days. The reason for this is clearly documented at the
top of that file and won't be a problem in -release since the
correct
Hi Greg,
Since the recent block device vanishment, MAKEDEV all and my vinum
volumes have failed to start.
# ls -l da[01]s1h
crw-r- 1 root operator 13, 0x00020007 Dec 12 22:56 da0s1h
crw-r- 1 root operator 13, 0x0002000f Dec 12 22:56 da1s1h
# vinum start
** no drives found: No suc
In article <[EMAIL PROTECTED]>
Marcel Moolenaar <[EMAIL PROTECTED]> writes:
> Other than that: Go ahead!
Thank you for many comments.
> BTW: Is there a special reason to have boot2 in aout?
Because nobody transplant from the i386 boot2 :-).
FreeBSD(98) porting team is always suffering from a s
On Sat, 11 Dec 1999 18:55:38 +0900,
Seigo Tanimura <[EMAIL PROTECTED]> said:
Seigo> My CS4614 has got only 4KB of the DMA buffer, frequently failing to
Seigo> play pcm blocks continuously. The following patch adds the secondary
Seigo> pcm channel buffers with the size independent from that of a
Running -current from this afternoon, I am having a strange symptom with
ppp over a pty; ppp does not detect that the pty does not support carrier,
and will cycle once per second waiting for CD to appear. Putting
``set cd off'' in my ppp.conf for that target fixed the problem, but I
thought I'd
> > "Dieter" == Dieter Rothacker <[EMAIL PROTECTED]>
>writes:
>
> Dieter> Why would you want to define "correct" numbering the
> Dieter> non-spread-out numbering? Or did I misunderstand you? I
> Dieter> have all my disks as master drives on the channels. Now,
> Dieter> when
On Sat, 11 Dec 1999, Lyndon Nerenberg wrote:
> Or worse, on a file server where you lose a low-numbered disk, not
> only does that one go away, but everything higher numbered loses as
> well. This "feature" does nothing other than introduce a gratuitous
Amen to this. If the default kernel or
> I am trying to get to current from 3.3-Release and I have just sent a
Right now one needs to be at the latest 3-STABLE to make the jump to
4-CURRENT. Please let us know if you have a problem once you've updated
to 3-STABLE.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [E
> I think this should only apply to the /dev/wd* compatability devices. ie:
> use the correct numbering for new installs onto ad*, but still support the old
> spread-out naming for wd*. This used to be more important as it required
> fiddling with $root_disk_unit, but the new mountroot code has
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these errors indicate?
Your disk is going
> The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several
> tools for a.out are needed to make boot2.
>
> I make the patch to fix this. Is there any problem?
Only in the longer term, I think. How hard would it be to port the 'new'
i386 boot2?
--
\\ Give a man a fish, and you
"Jordan K. Hubbard" wrote:
>
> > In other words, it's not a problem specific to KLD's .. but
> > it's still a problem :-)
>
> Which raises an important issue - other than walking the sysctl tree
> regularly looking for changes, how does such an application become
> aware that the sysctl space h
Oops, try this patch instead, again, it's done wrong, but I couldn't
figure out why statclock_disable was getting a value, and I don't have
time to figure it out.
--- clock.c.origSat Dec 11 19:58:15 1999
+++ clock.c Sat Dec 11 20:15:01 1999
@@ -962,7 +962,7 @@
int apic_8254_tr
I don't know if anyone else was having this problem, and I don't know that
this is a proper fix, but here goes:
For some reason rtc0 was not working, and I think it's because this
variable was not initialized, here is the patch:
--- clock.c.origSat Dec 11 19:58:15 1999
+++ clock.c Sa
On 12-Dec-99 Tim Preece wrote:
> Hello,
>
> I am trying to get to current from 3.3-Release and I have just sent a
> message to questions concerning this, however I have just seen a message
> from Adam Wight
>
> make world broken by choose-temp.c
>
> and this is my problem
>
> Please
1) The runtime-info.h target in gnu/lib/libobjc/Makefile calls
`{CC} --print-prog-name=cc1obj` -print-obj-runtime-info, which uses an
absolute path and calls the 3.3 version of cc1obj. This, of course,
breaks the make. I don't know the proper fix, but building and installing
cc1obj by hand is a
Here is a patch for my modem:
--- sio.c.orig Sat Dec 11 19:51:29 1999
+++ sio.c Sat Dec 11 19:51:20 1999
@@ -553,6 +553,7 @@
{0x31307256, NULL}, /* USR3031 */
{0x8020b04e, NULL}, /* SUP2080 */
{0x8024b04e, NULL
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hello,
I am trying to get to current from 3.3-Release and I have just sent a
message to questions concerning this, however I have just seen a message
from Adam Wight
make world broken by choose-temp.c
and this is my problem
Please how do I get around this
ps sorry if this is the wro
On Sat, Dec 11, 1999 at 02:48:12PM -0700, Lyndon Nerenberg wrote:
> > "Dieter" == Dieter Rothacker <[EMAIL PROTECTED]>
>writes:
>
> Dieter> Why would you want to define "correct" numbering the
> Dieter> non-spread-out numbering? Or did I misunderstand you? I
> Dieter> have all m
< said:
> Which raises an important issue - other than walking the sysctl tree
> regularly looking for changes, how does such an application become
> aware that the sysctl space has changed?
It's listening on a kernel notification socket. (Implementation is an
exercise left for the reader, but
phk wrote:
> This is *CURRENT* remember ? We want this transistion done and
> tested before current becomes 4.0-RELEASE. The time is NOW!
Not quite: this is -current, 4 days before a functionality freeze and
potentially less than one month before 4.0-RELEASE. Replacing critical
parts of the s
===> cc
cc -O -pipe -m486 -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\"
-I/usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_tools
-I/usr2/src/gnu/usr.bin/cc/cc/../cc_tools
-I/usr2/src/gnu/usr.bin/cc/cc/../../../../contri
...
>
> The scsi system has always been dynamic with a wiring *option* right from
> as far back as 2.0. CAM didn't change this.
as far back as 386BSD and the patchkit.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
Lyndon Nerenberg wrote:
> > "Adam" == Adam <[EMAIL PROTECTED]> writes:
>
> Adam> As I understand it, cam or pre-cam or wd or ata it is simply
> Adam> an issue of defaults. If you plan to use disks that die or
> Adam> become removed, simply read LINT on how to wire your disk
>
Alexander Leidinger wrote:
> On 11 Dec, Maxim Sobolev wrote:
> > Some time ago my soundcard (Vibra 16C), which worked just fine
> > previously, stopped being recognised/attached. Following is relevant
> > pieces of dmesg and pnpinfo:
>
> last cvsup: Dec, 9.
>
> sbc0: at port 0x220-0x22f,0x330-0x
> Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and
> then stat the directory nodes.
AAIEE! sysctlfs!! :-)
It's an interesting idea and I'm not sure why it also horrifies me at
some inner, almost cellular, level. If somebody's actually willing to
do the work of cre
> Perhaps a modtime on the sysctl tree as a gross hack? Inside of sysctl() and
> the SYSCTL() macros you would update the time every time a write was made, no
de
> added, node removed, etc. However, it is a gross hack.
You're right, it would be a gross hack. :) Also, I can see where it
would b
> other than walking the sysctl tree regularly looking for changes
Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and
then stat the directory nodes.
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 11-Dec-99 Jordan K. Hubbard wrote:
>> In other words, it's not a problem specific to KLD's .. but
>> it's still a problem :-)
>
> Which raises an important issue - other than walking the sysctl tree
> regularly looking for changes, how does such an application become
> aware that the sysctl
> In other words, it's not a problem specific to KLD's .. but
> it's still a problem :-)
Which raises an important issue - other than walking the sysctl tree
regularly looking for changes, how does such an application become
aware that the sysctl space has changed? The same holds true for a
dyn
> "Adam" == Adam <[EMAIL PROTECTED]> writes:
Adam> As I understand it, cam or pre-cam or wd or ata it is simply
Adam> an issue of defaults. If you plan to use disks that die or
Adam> become removed, simply read LINT on how to wire your disk
Adam> id's.
I understand. The poi
On Fri, Dec 10, 1999 at 05:15:29PM +0100, Poul-Henning Kamp wrote:
>
> Please, help Sos fix ATA if you know of a problem.
> Please, help fix PCCARD if you know of a problem.
Ok, so now the attitude is I need to spend all my time:
1. Fix ATA to work on my laptop (there are timeout issues)
2. F
On Sat, 11 Dec 1999, Lyndon Nerenberg wrote:
>> "Dieter" == Dieter Rothacker <[EMAIL PROTECTED]> writes:
>
>Dieter> Why would you want to define "correct" numbering the
>Dieter> non-spread-out numbering? Or did I misunderstand you? I
>Dieter> have all my disks as master drives on
Jordan K. Hubbard writes:
> > I think the latter. In 'theory' there should be no discernable
> > difference between functionality from a KLD vs. the same functionality
> > compiled directly into the kernel.
>
> Only in theory, of course. :)
>
> As Andrzej has already pointed out, modules can als
> "Dieter" == Dieter Rothacker <[EMAIL PROTECTED]> writes:
Dieter> Why would you want to define "correct" numbering the
Dieter> non-spread-out numbering? Or did I misunderstand you? I
Dieter> have all my disks as master drives on the channels. Now,
Dieter> when I hook up anot
< said:
>> [Attribution lost.]
>> So producing a.out libraries for CURRENT is silly. :-)
> Nope. You really need to think about the ISV's. Why do you think
> Netscape is still a.out? ISV's want to produce one binary that runs
> across multiple generations of FreeBSD.
Which, of course, is the
Kenneth Wayne Culver wrote:
> > > The same thing is about to apply to the woxware sound code, we have a
> > > new shiny system that works and is much better designed...
> >
> > Actually, I'm sad to say that our shiny new sound system does *not*
> > work for some of the most popular audio chipsets
On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote:
> And as for the device renaming, you didn't have to change anything from
> sd->da. The old device names and nodes were supported in most every way.
BUT not any longer. Thus we have no choice but fully make the sd->da
change. [D
On Thu, Dec 09, 1999 at 10:23:40AM +0200, Sheldon Hearn wrote:
>
> Are you sure? Any a.out binaries for FreeBSD are going to be desgined
> to work with 3.x or older.
Why??? A.out runs just fine on 4.0-R, and had better on 5.0-R.
> So producing a.out libraries for CURRENT is silly. :-)
Nop
On Sat, 11 Dec 1999, Vallo Kallaste wrote:
> I'm getting the "lost disk contact" messages every now and then, but
> only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
> an PPro machine with Intel mobo. Can it be related to newer IBM disks?
Depends on what 'now and then' is.
Just a question which I'm not sure is soundcard related. My xmms no longer
starts up anymore, it just hangs in Poll before it actually puts anything
on the display, is that because /dev/dsp isn't working?
=
| Kenneth Culver
> > The same thing is about to apply to the woxware sound code, we have a
> > new shiny system that works and is much better designed...
>
> Actually, I'm sad to say that our shiny new sound system does *not*
> work for some of the most popular audio chipsets on the market today
> (where the olde
Will the backdown to PIO mode be permanent till the next reboot of the
machine, or will the driver be able to attempt to return to DMA mode after
a timeout period. I'm only seeing these errors under really heavy disk
activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the
vinum
> On 11 Dec, Michael Kennett wrote:
> > I've just tried installing the last current snapshot (4.0-19991208-CURRENT)
> > onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card
> > (CE3B-100BTX). It failed -- the pccard was not recognized.
> >
> > I mention this because the floppies
On 11-Dec-99 Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
>>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>>: You overlook one simple thing here: If we want the ata driver tested,
>>: we need to make existing kernel configs break, otherwise people
>>:
As I recall, Joe Greco wrote:
> Hell, I've been seeing this for well over a year. The last time I mentioned
> it, everybody seemed to think I was nuts. :-)
>
> FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999
>
> routetbl289178 40961K 40961K 40960K 4357410 0 16,32,64,
On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote:
> > Subject: Re: HEADSUP: wd driver will be retired!
> > Date: Fri, 10 Dec 1999 19:19:43 +0100
> > From: Poul-Henning Kamp <[EMAIL PROTECTED]>
> >
> >
> > Maybe we should put a special marker in -currents sendmail and
> > reject all em
On Fri, Dec 10, 1999 at 11:20:19PM -0800, Jordan K. Hubbard wrote:
> my strategy on the whole affair at this point has
> been to simply make marks on a tally-sheet near my keyboard,
While there is now working support for SiS 5591, and
thus my initial objection to removal of the wd drivers is now
Soren Schmidt writes:
> It seems [EMAIL PROTECTED] wrote:
> > I've got a striped vinum partition that is occasionally going stale when
> > I get spurrious errors from the ata driver.
> >
> > I can setstate the drives and the volume back up and an fsck of the
> > partition doesn't show any
It seems Dieter Rothacker wrote:
> Hi,
>
> here I have my Bonnie++ 0.99d output:
> machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500.
> (One slice, one partition UFS)
> --
> Version 0.99d --Sequential Output-- --Sequential Input- --Random-
>-Per Chr- --Block-- -Re
On Thu, Dec 09, 1999 at 11:28:20AM +0100, Soren Schmidt wrote:
> It seems Soren Schmidt wrote:
> > It seems Richard Seaman, Jr. wrote:
> > > On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
> > >
> > > > OK, you asked for it, following is a patch to support the
> > > > sis 5591 chi
It seems [EMAIL PROTECTED] wrote:
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these er
Oleg Dobrokhotov wrote:
>
> Hello ALL,
> After Making hierarchy, in Installig everything
> >install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h
> >/usr/SNAP/include
> >install: osreldate.h - no such file or directory...
> >***Error code 71
> >Stop in /usr/src/include
> >Error code 1
Greg Childers writes:
> Hello,
>
> Seems now is the time to raise problems with ATA, so here goes. I have used the ATA
>driver
> since its introduction into -current without problem until recently. A kernel from
>October
> 5 worked fine. Now, it no longer works using ATA, but works f
[EMAIL PROTECTED] writes:
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these er
> Subject: Re: HEADSUP: wd driver will be retired!
> Date: Fri, 10 Dec 1999 19:19:43 +0100
> From: Poul-Henning Kamp <[EMAIL PROTECTED]>
>
>
> Maybe we should put a special marker in -currents sendmail and
> reject all email to the current list if they don't originate
> from such a system.
>
>
Hello ALL,
After Making hierarchy, in Installig everything
>install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h
>/usr/SNAP/include
>install: osreldate.h - no such file or directory...
>***Error code 71
>Stop in /usr/src/include
>Error code 1
--
Best regards,
Oleg
>>> If half as much energy was spent adding the missing bits of
>>> functionality to the new systems as people have been spending
>>> complaining it then we'd be there ages ago.
>>
>> Not true. It doesn't take a disk expert to complain about a policy,
>> but it takes one to fix bugs/add features
Here's my fstab:
# DeviceMountpoint FStype Options DumpPass#
/dev/ad0s1b noneswapsw 0 0
/dev/ad1s1b noneswapsw 0 0
/dev/ad0s1a / ufs rw
I would like to add an option to revert back to the old behavior of not
using the PnP stuff to probe the ISA bus. My reason for this is that my
soundcard (SB ViBRA16X) and Modem (Diamond SupraExpress 56i) both were
detected and worked fine (the SB with voxware drivers, the modem with the
sio drive
On Fri, Dec 10, 1999 at 09:31:57PM +0100, Soren Schmidt <[EMAIL PROTECTED]> wrote:
> > I've connected the disk back to the UDM33 controller and it works
> > fine. Now I get the message twice a day:
> >
> > ata0-master: ad_timeout: lost disk contact - resetting
> > ata0: resetting devices .. done
Takahashi Yoshihiro wrote:
> +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf"
> +USRDIRS+= usr/libexec/aout
> +.endif
I don't think you need to test for OBJFORMAT. Also, include MACHINE_ARCH
in case of cross-building. eg:
.if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98"
> +.if ${MA
I've got a striped vinum partition that is occasionally going stale when
I get spurrious errors from the ata driver.
I can setstate the drives and the volume back up and an fsck of the
partition doesn't show any obvious corruption.
What do these errors indicate?
ad5: status=51 error=84
ad_inter
In message <[EMAIL PROTECTED]>, Stephen McKay writes
:
>On Friday, 10th December 1999, Mike Smith wrote:
>
>>The same mentality that made the CAM cutover a "debacle" is making the
>>ata cutover a "debacle".
First of all, "core" is not really involved in this per se.
>It might be that these th
Does your /etc/fstab have character devices listed or block devices ?
If it has character devices (aka raw devices), change them to block
(remove the 'r' at the front) e.g. change: "/dev/rad0s2a" to
"/dev/ad0s2a".
It seems to be only necessary for the root filesystem.
Some people (like me) chan
On 11 Dec, Michael Kennett wrote:
> I've just tried installing the last current snapshot (4.0-19991208-CURRENT)
> onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card
> (CE3B-100BTX). It failed -- the pccard was not recognized.
>
> I mention this because the floppies/pccard/READ
The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several
tools for a.out are needed to make boot2.
I make the patch to fix this. Is there any problem?
--- Makefile.inc1 1999/12/10 16:13:41 1.102
+++ Makefile.inc1 1999/12/11 10:01:21
@@ -143,6 +143,10 @@
USRDIRS=
"Jordan K. Hubbard" wrote:
> Actually, I'm sad to say that our shiny new sound system does *not*
> work for some of the most popular audio chipsets on the market today
> (where the older "luigi" sound system did support them) and this is a
> matter of significant concern to some folks, myself inc
Hi,
here I have my Bonnie++ 0.99d output:
machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500.
(One slice, one partition UFS)
--
Version 0.99d --Sequential Output-- --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine
Hello!
Since Nov 12th, I've been having this problem, too. Is there a
solution/workaround available yet? I'm using a SCSI DAT drive and making
backups using dump or tar works, but amanda still manages to hang the machine!
Many thanks,
Christian.
AFAIR Taavi Talvik wrote on Sa , 20 Nov 1999:
>
On 11 Dec, Maxim Sobolev wrote:
> Some time ago my soundcard (Vibra 16C), which worked just fine
> previously, stopped being recognised/attached. Following is relevant
> pieces of dmesg and pnpinfo:
last cvsup: Dec, 9.
sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5
drq 1,5 on isa0
pc
> I think the latter. In 'theory' there should be no discernable
> difference between functionality from a KLD vs. the same functionality
> compiled directly into the kernel.
Only in theory, of course. :)
As Andrzej has already pointed out, modules can also be loaded and
unloaded, creating a sys
On Sat, 11 Dec 1999 18:28:42 +0800, Peter Wemm wrote:
>Dieter Rothacker wrote:
>>
>> You should use the kernel option
>> "options ATA_STATIC_ID"
>> for such cases. At least it works for me :-)
>
>I think this should only apply to the /dev/wd* compatability devices. ie:
>use the correct numb
Dieter Rothacker wrote:
> On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
>
> >Note that wd1 is not present. This caused a mild hickup when rebooting the
> >new kernel, since the new ata controller assigned the labels ad0 and ad1 to
> >the drives. It was not possible to boot in
DATA
From: [EMAIL PROTECTED]
To:
Date: Sat, 11 Dec 1999 17:16:58 PST
Subject: SKIN BECOMES DRAMATICALLY EVEN-TONED AND CLEAR...
SKIN PROBLEMS? LET "DERMACURE" SOLVE THEM!
Hello. We have good news for you.
"DERMACURE" IS MADE FOR YOUR SKIN.
If you suffer from any form of skin discolorations,
On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
>Note that wd1 is not present. This caused a mild hickup when rebooting the
>new kernel, since the new ata controller assigned the labels ad0 and ad1 to
>the drives. It was not possible to boot into multiuser mode without changing
My CS4614 has got only 4KB of the DMA buffer, frequently failing to
play pcm blocks continuously. The following patch adds the secondary
pcm channel buffers with the size independent from that of a DSP. The
patch works quite well with mpg123 and x11amp. For those who has the
similar problem could
Some time ago my soundcard (Vibra 16C), which worked just fine
previously, stopped being recognised/attached. Following is relevant
pieces of dmesg and pnpinfo:
CTL0001: start dependant
CTL0001: adding irq mask 0x20
CTL0001: adding dma mask 0x2
CTL0001: adding dma mask 0x20
CTL0001: adding io ra
Hi,
With a bit of investigating, I've found the problem described in my previous email
quoted at
the end of this message started with the commits listed below. A kernel built using
sources just before these commits works fine, whereas a kernel build just after freezes
after the line
Mounting
In message <[EMAIL PROTECTED]>, "Jordan K. Hubbard" writes:
>> The ATA driver went golden now, and to make sure nobody is distracted
>> from testing it before 4.0-RELEASE is cut, the wd driver will be
>> removed.
>>
>> It's really that simple.
>
>Well, I'm not sure that's really true yet and I wo
In message <[EMAIL PROTECTED]>, Michael Kennett writes:
>Finally, I've noticed the following messages:
>
>Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying
>Dec 11 13:54:50 rabbit last message repeated 2 times
>Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0
88 matches
Mail list logo
