headers
Jon Drews | 1 Sep 2004 01:06
Picon

Re: [PLEASE TEST] Better support for Synaptics Touchpads

On Mon, 30 Aug 2004 18:42:17 -0600, Jon Drews <jon.drews <at> gmail.com> wrote:
> OK:
> 
>  I put this in device.hints and my mouse works in X but not at the
> xterm. FreeBSD 5.3 B2 no longer locks up when configuring the mouse
> with sysinstall.
> 
> hint.psm.0.flags="0x200"

OK the mouse is working in the console now. I am still using the above hint.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
J.R. Oldroyd | 1 Sep 2004 01:35
Favicon

Re: Current 8/27/2004, DVD problems

Afraid not.

Just to confirm since my line numbers seem to be a few off yours...

I have:
__FBSDID("$FreeBSD: src/sys/dev/ata/ata-lowlevel.c,v 1.46 2004/08/27 22:14:45 sos Exp $");

And after adding the extra call to ata_wait() there are now TWO ata_wait()s:

int
ata_generic_command(struct ata_device *atadev, u_int8_t command,
                    u_int64_t lba, u_int16_t count, u_int16_t feature)
{
    if (atadebug)
        ata_prtdev(atadev, "ata_command: addr=%04lx, command=%02x, "
                   "lba=%jd, count=%d, feature=%d\n",
                   rman_get_start(atadev->channel->r_io[ATA_DATA].res),
                   command, (intmax_t)lba, count, feature);

    /* ready to issue command ? */
    if (ata_wait(atadev, 0) < 0) {
        ata_prtdev(atadev, "timeout waiting for ready command=%02x\n", command);
        return -1;
    }

    /* select device */
    ATA_IDX_OUTB(atadev->channel, ATA_DRIVE, ATA_D_IBM | atadev->unit);

    /* ready to issue command ? */
    if (ata_wait(atadev, 0) < 0) {
(Continue reading)

Permalink | Reply | 1 comment |
headers
Lukas Ertl | 1 Sep 2004 01:35
Picon
Favicon

Re: PLEASE TEST: IPI deadlock avoidance patch

On Tue, 31 Aug 2004, Craig Boston wrote:

> So it seems that gvinum RAID-5 is a key factor in the corruption, and
> SMP greatly increases the odds of it happening...
>
> Is it worth creating a PR so this doesn't get lost amid the release
> madness?

PR isn't necessary, it's my number one task right now (which isn't easy, 
since the corruption isn't really repeatable at will).  Gimme a little more 
time.

thanks,
le

--

-- 
Lukas Ertl                         http://homepage.univie.ac.at/l.ertl/
le <at> FreeBSD.org                     http://people.freebsd.org/~le/
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Kenneth Stailey | 1 Sep 2004 01:37
Picon
Favicon

Re: Problem with SiI3114 SATA RAID using 5.3-BETA1-20040823

One more detail.  When booted from 5.2.1-p8

hermes# atacontrol list
ATA channel 0:
    Master: acd0 <SONY CD-RW CRX230ED/4YS1> ATA/ATAPI rev 5
    Slave:       no device present
ATA channel 1:
    Master:      no device present
    Slave:       no device present
ATA channel 2:
    Master:  ad4 <Maxtor 6Y200M0/YAR51HW0> ATA/ATAPI rev 7
    Slave:       no device present
ATA channel 3:
    Master:  ad6 <Maxtor 6Y200M0/YAR51HW0> ATA/ATAPI rev 7
    Slave:       no device present
ATA channel 4:
    Master:      no device present
    Slave:       no device present
ATA channel 5:
    Master:      no device present
    Slave:       no device present
hermes# atacontrol status ar0
ar0: ATA RAID1 subdisks: ad4 ad6 status: READY
hermes#

When booted from 5.3-BETA1

Fixit# atacontrol list
ATA channel 0:
    Master: acd0 <SONY CD-RW CRX230ED/4YS1> ATA/ATAPI revision 5
(Continue reading)

Permalink | Reply | 0 comments |
headers
Charles Swiger | 1 Sep 2004 01:53
Picon

Re: suggestion for /usr/src/UPDATING

On Aug 31, 2004, at 6:22 PM, Evan Dower wrote:
> This seems to me like a very good idea. Some people are very 
> accustomed to the current defaults.  They can just leave things alone. 
>  [ ... ]  In fact, I'd be perfectly happy if you couldn't change the 
> default keys but could only add to them. That is, r and l would always 
> work, but you could configure it so that other letters/keys would also 
> have the same functions.

OK.  I am happy with the notion of "everybody wins", so I've updated 
the code as you've suggested, and also made more effort to retain 
GNU-style spacing in the changes:

http://www.pkix.net/~chuck/sdiff2.diff

--

-- 
-Chuck

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Tim Robbins | 1 Sep 2004 02:23
Picon
Favicon

Re: NFS mounted full disk gives funny stats on 5.3B2 (negative Avail?)

On Tue, Aug 31, 2004 at 03:59:28PM +0200, Volker Stolz wrote:
> The negative Avail-stats seem to be mistranslated. Is this worth send-pr'ing
> or is it a known problem? Please cc: replies.

See PR kern/18874.

Tim
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Deng XueFeng | 1 Sep 2004 03:20
Picon
Favicon

Re: [BETA PATCH] VESA mode support for syscons


----- Original Message ----- 
From: "Sascha Wildner" <saw <at> online.de>
To: "Deng XueFeng" <dsnofe <at> msn.com>
Sent: Wednesday, September 01, 2004 12:05 AM
Subject: Re: [BETA PATCH] VESA mode support for syscons


> Deng XueFeng wrote:
> 
>>>Thanks. It seems to me that the modes you were writing about are not 
>>>true VESA modes (at least the card doesn't return info on them). I guess 
>> 
>> what's info?
>> could you give a example or you dmesg file?
> 
> Deng,
> 
> during kernel initialization the VESA module probes all possible mode 
> numbers and looks if the adapter returns a valid mode. In your dmesg you 
> can see that no WXGA modes are recognized and they are also not 
> rejected. So I think this is because these modes are only accessible to 
> hardware specific drivers.
Thanks to explain this. I wanna try linux to see what mode  it support.

> 
> Oh, I saw that there are threads on freebsd-current. The issues people 
> are having there with their moused complaining are due to some changes 
> in vidcontrol that DragonFly has done. Since the mouse pointer is common 
> to all terminals it can be turned on (and off) only once. After that, it
(Continue reading)

Permalink | Reply | 8 comments |
headers
FreeBSD Tinderbox | 1 Sep 2004 04:14
Picon
Favicon

[current tinderbox] failure on i386/pc98

TB --- 2004-09-01 00:51:34 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2004-09-01 00:51:34 - starting CURRENT tinderbox run for i386/pc98
TB --- 2004-09-01 00:51:34 - checking out the source tree
TB --- 2004-09-01 00:51:34 - cd /home/tinderbox/CURRENT/i386/pc98
TB --- 2004-09-01 00:51:34 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2004-09-01 00:56:44 - building world (CFLAGS=-O2 -pipe)
TB --- 2004-09-01 00:56:44 - cd /home/tinderbox/CURRENT/i386/pc98/src
TB --- 2004-09-01 00:56:44 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2004-09-01 02:00:44 - building generic kernel (COPTFLAGS=-O2 -pipe)
TB --- 2004-09-01 02:00:44 - cd /home/tinderbox/CURRENT/i386/pc98/src
TB --- 2004-09-01 02:00:44 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Wed Sep  1 02:00:44 UTC 2004
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
>>> Kernel build for GENERIC completed on Wed Sep  1 02:14:02 UTC 2004
(Continue reading)

Permalink | Reply | 0 comments |
headers
takawata | 1 Sep 2004 04:38
Picon
Favicon

Re: acpi_video on SONY VAIO PCG-Z1 [was: acpi_video users needed]

In message <20040831131628.GA2156 <at> laptoxa.toxa.lan>, Toxa さんいわく:
>On Tue, Aug 31, 2004 at 07:41:11PM +0900, takawata <at> jp.freebsd.org wrote:
>> >dev.acpi_sny.0.brightness=10
>> >sysctl: oid 'dev.acpi_sny.0.brightness' is read only
>> >
>> >nothing happens...
>
>> Sorry, please refetch it from
>
>> http://www.init-main.com/acpi_snc.tar.gz
>
>acpi_sny0: detached
>acpi_snc0: <Sony system controller> on acpi0
>[(17:12)(49.34%)(p6):~/tmp/acpi_snc ] sysctl -a|grep snc
>dev.acpi_snc.0.%desc: Sony system controller
>dev.acpi_snc.0.%driver: acpi_snc
>dev.acpi_snc.0.%location: handle=\_SB_.PCI0.LPC0.SNC_
>dev.acpi_snc.0.%pnpinfo: _HID=SNY5001 _UID=0
>dev.acpi_snc.0.%parent: acpi0
>dev.acpi_snc.0.brightness: 94
>[(17:12)(49.34%)(p6):~/tmp/acpi_snc ] sudo sysctl
>dev.acpi_snc.0.brightness=10
>dev.acpi_snc.0.brightness: 94 -> 10
>[(17:13)(49.51%)(p6):~/tmp/acpi_snc ] sudo sysctl
>dev.acpi_snc.0.brightness=100
>dev.acpi_snc.0.brightness: 10 -> 100
>[(17:13)(49.51%)(p6):~/tmp/acpi_snc ] 
>
>Yes, it works, thanks a lot! Now I'm wondering how to resume lid from
>suspending. Machine resumes well and I can log in remotely but monitor
(Continue reading)

Permalink | Reply | 10 comments |
headers
Brian Reichert | 1 Sep 2004 07:20

how 'supported' are 3ware Escalade controllers?

I'm speccing a budget RAID fileserver, and stumbled across some
interesting prospects.

This page describes a eight-channel ATA RAID card, the 7506-8:

  <http://www.3ware.com/products/parallel_ata.asp>

This page says there is support for other cards in this family, but
doesn't explicitly cite the 7506-8, and cites some firmwar issues:

  <http://people.freebsd.org/~msmith/RAID/#3ware>

The manpage for the driver itself seems prety broad:

  <http://www.freebsd.org/cgi/man.cgi?query=twe&sektion=4&manpath=FreeBSD+5.2.1-RELEASE>

Can someone explicitly tie these references together?  Is the 7506-8
going to cut it?

Of course, I'm open to any anti-recommendations WRT this card, as
well, so feel free to chuck me any feedback...

--

-- 
Brian Reichert				<reichert <at> numachi.com>
37 Crystal Ave. #303			Daytime number: (603) 434-6842
Derry NH 03038-1713 USA			BSD admin/developer at large	
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 12 comments |

Gmane