headers
Michael Butler | 1 Mar 2009 02:47
Favicon

Re: MITSUMI USB FDD with USB4BSD does not work, neither


Hans Petter Selasky wrote:
> On Saturday 28 February 2009, Yoshihiro Ota wrote:
>> I have a MITSUMI USB fdd and pluged in to 8-CURRENT.
>> FreeBSD 8.0-CURRENT #5 r189058M: Thu Feb 26 11:29:13 EST 2009
>>
>> It printed as following but nothing happened there after.
>>
>> ugen0.3: <MITSUMI> at usbus0
>> umass0: <MITSUMI MITSUMI USB FDD, class 0/0, rev 1.10/1.00, addr 3> on
>> usbus0 umass0:  SCSI over Bulk-Only; quirks = 0x0100
>                                         ^^^ your device is listed with quirks.
> Maybe the quirks are incorrect. Please check the quirk table in
> /sys/dev/usb/storage/umass.c

This is a similar symptom to that which I observed .. the "standard"
USB2 code and quirks do this with my external USB drive:

ugen4.2: <Sunplus Technology Inc.> at usbus4
umass0: <Bulk Only Interface> on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:3:0:-1: Attached to scbus3
xptioctl: pass driver is not in the kernel
xptioctl: put "device pass" in your kernel config file
umass0: at ushub4, port 3, addr 2 (disconnected)

If I add a quirk entry in umass.c, I get this (once):

ugen4.2: <Sunplus Technology Inc.> at usbus4
umass0: <Bulk Only Interface> on usbus4
(Continue reading)

Permalink | Reply | 0 comments |
headers
Luke Dean | 1 Mar 2009 04:40
Picon
Favicon

Future of the axe driver?


I've got a Netgear FA120 usb-to-ethernet device.  I don't use it
regularly, but it has saved the day on many occasions.

I'm running FreeBSD 7.1 right now, not CURRENT, and this device is
supported by the axe driver.

I've been trying to follow the news with CURRENT, and it sounds like axe
is being phased out for a couple of different reasons.  I saw posts about
how it doesn't fit with the way CURRENT wants to do locking or with the
new usb changes.  I browsed the CVS repository and saw that its code had
been moved into the attic this week.

Has axe been phased out?  Will there be another driver to support my
device when I decide to move to FreeBSD 8?  Is there anything I can do to
help preserve support for this device?
_______________________________________________
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 | 3 comments |
headers
Andrew Thompson | 1 Mar 2009 05:37
Picon
Favicon

Re: Future of the axe driver?

On Sat, Feb 28, 2009 at 07:40:02PM -0800, Luke Dean wrote:
> 
> I've got a Netgear FA120 usb-to-ethernet device.  I don't use it
> regularly, but it has saved the day on many occasions.
> 
> I'm running FreeBSD 7.1 right now, not CURRENT, and this device is
> supported by the axe driver.
> 
> I've been trying to follow the news with CURRENT, and it sounds like axe
> is being phased out for a couple of different reasons.  I saw posts about
> how it doesn't fit with the way CURRENT wants to do locking or with the
> new usb changes.  I browsed the CVS repository and saw that its code had
> been moved into the attic this week.
> 
> Has axe been phased out?  Will there be another driver to support my
> device when I decide to move to FreeBSD 8?  Is there anything I can do to
> help preserve support for this device?

Im not sure what posts were saying it was going to be phased out but it
isnt true and the hardware is very much supported. The driver now lives
under a slighty different location of sys/dev/usb/net/if_axe.c

Andrew
_______________________________________________
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 | 2 comments |
headers
Alexander Motin | 1 Mar 2009 09:43
Picon
Favicon

Re: ata problems <at> r189170

Larry Rosenman wrote:
> With the 189195 version from csup, I get all sorts of timeouts from my
> ATA drives in ahci mode.
> 
> Kernel from:
> FreeBSD borg.lerctr.org 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Mon Feb  9 
> 10:21:36 CST 2009     root <at> borg.lerctr.org:/usr/obj/usr/src/sys/BORG  amd64
> 
> works, the current (as of this writing) sources do NOT. Ideas on what to 
> get?
> 
> dmesg from the running kernel:

What do you mean by "all sorts of timeouts"? Can you show examples with 
verbose messages enabled?

--

-- 
Alexander Motin
_______________________________________________
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
Larry Rosenman | 1 Mar 2009 09:34
Gravatar

Re: ata problems <at> r189170

On Sat, 28 Feb 2009, Alexander Motin wrote:

> Sam Leffler wrote:
>> Sam Leffler wrote:
>>> Sam Leffler wrote:
>>>> HEAD  <at>  r189170 fails to boot on a T41.  Two cd/dvd drivers are recognized 
>>>> (only 1 exists) and I get complaints of the form (and transcribed):
>>>> 
>>>> acd1: WARNING - ATAPI_IDENTIFY taskqueue timeout - completing request 
>>>> directory
>>>> 
>>>> (similarly for acd0) until there's a panic:
>>>> 
>>>> panic: mtx_lock() of destroy mutex  <at>  .../../../kern_sema.c:79
>>>> 
>>>> (stack trace uninteresting).
>>>> 
>>> 
>>> boot -v shows:
>>> 
>>> acd0: setting PIO4 on CH4 chip
>>> acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - ...
>>> acd0: setting UDMA32 on ICH4 chip
>>> ata1: Identifying devices: 00030000
>>> ata: New devices: 00000000
>>> ata1: reinit done ..
>>> panic ...
>> reverting r189166 gets me a bootable kernel.
>
> Looks like while fixing small problems I have found bigger ones. Try please
(Continue reading)

Permalink | Reply | 2 comments |
headers
Norikatsu Shigemura | 1 Mar 2009 10:16
Picon
Favicon

ktemp(8) on Phenom II

Hi Rui!

	I got Phenom II machine.  But k8temp(8) doesn't work.
	DO you have any idea?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
hostb4 <at> pci0:0:24:3:     class=0x060000 card=0x00000000 chip=0x12031022 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices (AMD)'
    device     = '(Family 10h) Athlon 64/Opteron/Sempron Miscellaneous Control'
    class      = bridge
    subclass   = HOST-PCI
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_______________________________________________
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 | 13 comments |
headers
Luke Dean | 1 Mar 2009 10:22
Picon
Favicon

Re: Future of the axe driver?


On Sat, 28 Feb 2009, Andrew Thompson wrote:

> On Sat, Feb 28, 2009 at 07:40:02PM -0800, Luke Dean wrote:
>>
>> I've got a Netgear FA120 usb-to-ethernet device.  I don't use it
>> regularly, but it has saved the day on many occasions.
>>
>> I'm running FreeBSD 7.1 right now, not CURRENT, and this device is
>> supported by the axe driver.
>>
>> I've been trying to follow the news with CURRENT, and it sounds like axe
>> is being phased out for a couple of different reasons.  I saw posts about
>> how it doesn't fit with the way CURRENT wants to do locking or with the
>> new usb changes.  I browsed the CVS repository and saw that its code had
>> been moved into the attic this week.
>>
>> Has axe been phased out?  Will there be another driver to support my
>> device when I decide to move to FreeBSD 8?  Is there anything I can do to
>> help preserve support for this device?
>
> Im not sure what posts were saying it was going to be phased out but it
> isnt true and the hardware is very much supported. The driver now lives
> under a slighty different location of sys/dev/usb/net/if_axe.c
>
>
> Andrew
>

There were a series of posts by Robert Watson titled
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rui Paulo | 1 Mar 2009 14:48
Picon
Favicon

Re: ktemp(8) on Phenom II

Hi,

On 1 Mar 2009, at 09:16, Norikatsu Shigemura wrote:

> Hi Rui!
>
> 	I got Phenom II machine.  But k8temp(8) doesn't work.
> 	DO you have any idea?
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
> - - - - - - -
> hostb4 <at> pci0:0:24:3:     class=0x060000 card=0x00000000  
> chip=0x12031022 rev=0x00 hdr=0x00
>    vendor     = 'Advanced Micro Devices (AMD)'
>    device     = '(Family 10h) Athlon 64/Opteron/Sempron  
> Miscellaneous Control'
>    class      = bridge
>    subclass   = HOST-PCI
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
> - - - - - - -

Try replacing 0x1103 by 0x1203 in k8temp.c.

Does that work?

--
Rui Paulo
Permalink | Reply | 12 comments |
headers
Norikatsu Shigemura | 1 Mar 2009 15:43
Picon
Favicon

Re: ktemp(8) on Phenom II

Hi Rui!

On Sun, 1 Mar 2009 13:48:28 +0000
Rui Paulo <rpaulo <at> freebsd.org> wrote:
> > chip=0x12031022 rev=0x00 hdr=0x00
> >    vendor     = 'Advanced Micro Devices (AMD)'
> >    device     = '(Family 10h) Athlon 64/Opteron/Sempron  
> > Miscellaneous Control'

> Try replacing 0x1103 by 0x1203 in k8temp.c.
> Does that work?

	I got following results:

$ sysctl -a | fgrep -e k8 -e temperature
dev.cpu.0.temperature: 143
dev.cpu.1.temperature: 143
dev.k8temp.0.%desc: AMD K8 Thermal Sensors
dev.k8temp.0.%driver: k8temp
dev.k8temp.0.%parent: hostb4
dev.k8temp.0.sensor0.core0: 143
dev.k8temp.0.sensor0.core1: 143
dev.k8temp.0.sensor1.core0: 143
dev.k8temp.0.sensor1.core1: 143

	Accordingly BIOS reports CPU temperature is 32-36 celsius
	(=89-97 fahrenheit).  I don't know what is '143'.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
(Continue reading)

Permalink | Reply | 11 comments |
headers
Rainer Hurling | 1 Mar 2009 16:01
Picon
Favicon

Logitech QuickCam 9000 Pro

I am owner of a webcam Logitech QuickCam 9000 Pro. On new usb stack it 
is shown as

ugen1.2: <product 0x0990 Logitech> at usbus1, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON

On old usb stack it was listed as

ugen0: <vendor 0x046d product 0x0990, class 239/2, rev 2.00/0.05, addr 
2> on uhub0

Could this webcam be added to the list of known devices for the new 
stack, please? Let me know if I can test something or provide some more 
information.

Thanks in advance,
Rainer Hurling
_______________________________________________
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 | 16 comments |

Gmane