Re: ati, radeon, dri (drm) confusion

[Adam K Kirchhoff]

Have you tried loading the radeon kernel module from /boot/loader.conf?
Or even from the console, before starting X?

Adam

On Mon, 2012-07-16 at 00:08 +0100, Anton Shterenlikht wrote:
> My X behaves really weird lately [1,2],
> so I went back to basics. Can somebody
> please comment on whether what I'm doing
> seems correct. Thanks
> 
> HP Compaq 6715s laptop
> FreeBSD 10.0-CURRENT #9 r238259M  amd64
> 
> vgapci0@pci0:1:5:0: class=0x03 card=0x30c2103c chip=0x791f1002 
> rev=0x00
> hdr=0x00
> vendor = 'ATI Technologies Inc'
> device = 'RS690M [Radeon X1200 Series]'
> class  = display
> subclass   = VGA
> 
> which, according to radeon(4x), is
> supported by radeon driver.
> 
> I've got in the kernel, amongst other things,:
> 
> deviceagp
> devicedrm
> deviceradeondrm
> devicevga
> 
> I then see in dmesg:
> 
> $ dmesg | grep vga
> vgapci0:  port 0x4000-0x40ff mem 
> 0xc010-0xc80f,0
> xd020-0xd020,0xd030-0xd03f irq 19 at device 5.0 on pci1
> vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> $ dmesg | grep -i agp
> $ dmesg | grep -i radeon
> 
> Is this expected that there's nothing
> related to either agp on radeon in dmesg?
> 
> Anyway, if I do X auto-configure, i.e.
> X -configure, I get in the resulting
> xorg.conf.new:
> 
> Identifier  "Card0"
> Driver  "radeon"
> VendorName  "Advanced Micro Devices [AMD] nee ATI"
> BoardName   "RS690M [Radeon X1200 Series]"
> BusID   "PCI:1:5:0"
> 
> Is that correct?
> 
> I then see in /var/log/Xorg.0.log:
> 
> drmOpenDevice: node name is /dev/dri/card0
> Failed to change owner or group for file /dev/dri! 2: No such file or 
> directory
> Failed to change owner or group for file /dev/dri/card0! 2: No such file or 
> dire
> ctory
> drmOpenDevice: open result is -1, (No such file or directory)
> Failed to change owner or group for file /dev/dri/card0! 2: No such file or 
> dire
> ctory
> drmOpenDevice: open result is -1, (No such file or directory)
> drmOpenDevice: Open failed
> [drm] failed to load kernel module "radeon"
> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
> [dri] Disabling DRI.
> 
> I guess this is not good, right?
> 
> Please advise
> 
> [1] http://lists.freebsd.org/pipermail/freebsd-x11/2012-June/012100.html
> [2] http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035171.html
> 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: DRI for Radeon HD5450 on FreeBSD 9.0

[Adam K Kirchhoff]

Dear list,

I own a radeon HD5450 and I would like to know how well it is supported
by freeBSD 9, in partocular DRI and 3D accelaeration.

I have a fresh 9.0/amd64 on my machine and Xorg fails to initialise the
DRI.  It says (from Xorg-0.log):

(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 338 x 270

As the last line of the snippet displays it, I use radeon(4x) as driver.

I used the page

http://people.freebsd.org/~anholt/dri/troubleshooting.html  


to try to diagnose the problem and it seems that none of the driver agp
radeondrm and drm is able to initaialize correctly.

Can you enable DRI for HD5450 on FreeBSD 9.0 ?
Do you have some useful documentation to show me?

In any of these cases, I would say ``thanks!''
--
Best regards,
Michael


Neither 2D nor 3D acceleration are supported on any HD5xxx or higher 
GPU.  Nor will they be supported till radeon KMS is implemented.


Adam


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: X11 - radeon or radeonhd? (ATI Radeon HD 2400 XT)

[Adam K Kirchhoff]

On Fri, 2 Jan 2009 21:23:50 +0100
Roland Smith  wrote:

> On Fri, Jan 02, 2009 at 01:42:38PM -0500, Adam K Kirchhoff wrote:
> > On Friday 02 January 2009 13:32:57 Ewald Jenisch wrote:
> > > Hi,
> > >
> > > I've got a PC (Dell) that came with a Radeon HD 2400 XT (RV610
> > > chipset).
> > >
> > > Afaik there isn't 3D support yet with this card, so my primary
> > > goal is to get it working as far as 2D and speed is concerned (I
> > > don't want to go for "vesa" if at all possible)
> > >
> > >
> > > Which driver should I use for this card - radeon or radeonhd?
> > >
> > > Anything to consider besides having either "Driver radeon" or
> > > "Driver radeonhd" in the xorg.conf in order to get going?
> > >
> > > Thanks much in advance for any clue,
> > > -ewald
> > 
> > Either radeon or radeonhd should be fine.  Feature-wise, they are
> > at the same level.  No other changes are required.
> > 
> > Very recently DRM support was added for those cards, giving them
> > much faster 2D acceleration via EXA (without DRM support, only XAA
> > is supported) 
> 
> I've tried a HD3450 (RV620 chip) and a X1650Pro (RV535 chip) with both
> ati and radeonhd drivers.
> 
> As of radeonhd 1.2.4 the X1650Pro works fine with XAA, to which it
> defaults. EXA wasn't very fast:
> 
> (--) Chipset RV535 found
> (**) RADEONHD(0): Selected XAA 2D acceleration.
> (**) RADEONHD(0): Option "XaaNoOffscreenPixmaps" "true"
> (II) RADEONHD(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Scanline Image Writes
> Setting up tile and stipple cache:
> 32 128x128 slots
> 28 256x256 slots
> 16 512x512 slots

EXA isn't fast (at least on Radeons) without DRM support.  This is not
available in the FreeBSD source tree, but is available (for FreeBSD) via
freedesktop git (for that particular GPU).  

Adam

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: X11 - radeon or radeonhd? (ATI Radeon HD 2400 XT)

[Adam K Kirchhoff]

On Fri, 2009-01-02 at 20:38 +0100, cpghost wrote:
> On Fri, Jan 02, 2009 at 01:42:38PM -0500, Adam K Kirchhoff wrote:
> > On Friday 02 January 2009 13:32:57 Ewald Jenisch wrote:
> > > Hi,
> > >
> > > I've got a PC (Dell) that came with a Radeon HD 2400 XT (RV610 chipset).
> > >
> > > Afaik there isn't 3D support yet with this card, so my primary goal is
> > > to get it working as far as 2D and speed is concerned (I don't want to
> > > go for "vesa" if at all possible)
> > >
> > >
> > > Which driver should I use for this card - radeon or radeonhd?
> > >
> > > Anything to consider besides having either "Driver radeon" or "Driver
> > > radeonhd" in the xorg.conf in order to get going?
> > >
> > > Thanks much in advance for any clue,
> > > -ewald
> > 
> > Either radeon or radeonhd should be fine.  Feature-wise, they are at the 
> > same 
> > level.  No other changes are required.
> > 
> > Very recently DRM support was added for those cards, giving them much 
> > faster 
> > 2D acceleration via EXA (without DRM support, only XAA is supported) and Xv 
> > support as well.  Unfortunately, this is limited to linux at the moment, 
> > but I 
> > *believe* Robert Noland has begun investigating how to port those changes 
> > over.
> 
> IIRC, it was related to having to use a more recent Xorg and MesaGL
> for the latest changes to work.  As soon as the ports freeze is over,
> I assume they would get merged in.

We're talking about the kernel modules here, not Xorg and Mesa.  The DRM
is necessary for EXA and Xv (as well as an updated DDX).  And based on
the conversations between Robert and the Linux/ATI folks, it is not as
simple as merging the changes in.  The new gart support necessary for
r600/r700 cards, for example, is completely linux specific, as I
understand it.

> I'm also hoping to see support for DRI and Xv and even 3D in RV780
> chipsets soon, esp. now that AMD has finally decided to release the
> RV600/700 specs to the public:
> 
> http://www.phoronix.com/scan.php?page=article&item=amd_r600_oss_3d&num=1
> 
> -cpghost.


The specs are not yet available.  The only thing newly available is the
DRM and updated DDX.  The specs be available as soon as they finish
sanitizing the documents and get approval.  This will hopefully be
"soon". :-)

Adam



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: X11 - radeon or radeonhd? (ATI Radeon HD 2400 XT)

[Adam K Kirchhoff]

On Friday 02 January 2009 13:32:57 Ewald Jenisch wrote:
> Hi,
>
> I've got a PC (Dell) that came with a Radeon HD 2400 XT (RV610 chipset).
>
> Afaik there isn't 3D support yet with this card, so my primary goal is
> to get it working as far as 2D and speed is concerned (I don't want to
> go for "vesa" if at all possible)
>
>
> Which driver should I use for this card - radeon or radeonhd?
>
> Anything to consider besides having either "Driver radeon" or "Driver
> radeonhd" in the xorg.conf in order to get going?
>
> Thanks much in advance for any clue,
> -ewald

Either radeon or radeonhd should be fine.  Feature-wise, they are at the same 
level.  No other changes are required.

Very recently DRM support was added for those cards, giving them much faster 
2D acceleration via EXA (without DRM support, only XAA is supported) and Xv 
support as well.  Unfortunately, this is limited to linux at the moment, but I 
*believe* Robert Noland has begun investigating how to port those changes 
over.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: loader.conf fbsd 7-release

[Adam K Kirchhoff]

On Tue, 2008-12-16 at 13:19 -0500, Gary Hartl wrote:
> Hi all;
> 
> I need to add something to loader.conf which according to me should be in
> /boot
> 
> Has something changed so that it wouldn't be there anymore.
> 
> Or do i just create it and it will parse it out at boot.
> 
> I need to add 
> 
> accf_http_load="YES"
> 
> to correct a problem with apache22 giving me the prompt/error
> 
> (2)No such file or directory: Failed to enable the 'httpready' Accept Filter
> 
> Thanks 
> 
> Gary 

If /boot/loader.conf does not exist, you can create it and add that
line.

Adam



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: firewire vs IDE DVD.

[Adam K Kirchhoff]

There is no /dev/acd0c on my system :-)  Just a /dev/acd0 and a
/dev/acd0t01 (neither of which work).

Adam

On Tue, 26 Aug 2003, Matthew Graybosch wrote:

> On 15:03 Tue 26 Aug , Adam K Kirchhoff wrote:
> >
> > Anyone?  The same IDE drive plays back DVDs with mplayer under NetBSD
> > without any problems, however NetBSD seems to be using some IDE-to-SCSI
> > emulation.  Is it impossible to get IDE DVD drives to play back DVD
> > videose under FreeBSD?
>
> I'm going to try to send this message one last time. Try looking for
> /dev/acd0c instead of /dev/acd0; I use the former and make sure its
> permissions are set to 666.
>
> --
> Matthew Graybosch
> http://www.starbreaker.net
> "The best way to lose an argument is to throw the first punch."
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: firewire vs IDE DVD.

[Adam K Kirchhoff]

Anyone?  The same IDE drive plays back DVDs with mplayer under NetBSD
without any problems, however NetBSD seems to be using some IDE-to-SCSI
emulation.  Is it impossible to get IDE DVD drives to play back DVD
videose under FreeBSD?

On Mon, 25 Aug 2003, Adam K Kirchhoff wrote:

>
> Me again.
>
> I've grabbed the output from mplayer and the dump from ktrace/kdump and
> posted them at:
>
> http://memory.visualtech.com/kdump.txt (975 kB)
> http://memory.visualtech.com/mplayer.txt (1 kB)
>
> From mplayer.txt, you see that it's complaing:
>
> "Couldn't open DVD device: /dev/dvd"
>
> Now /dev/dvd is a symlink to /dev/acd0:
>
> [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/dvd
> lrwxr-xr-x  1 root  wheel  3 Aug 25 15:54 /dev/dvd -> /dev/acd0
>
> And /dev/acd0 looks like:
>
> [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/acd0
> crw-r--r--  1 root  operator  117,   0 Aug 25 15:36 /dev/acd0
>
> Note:  user 'adamk' is part of the 'operator' group.  In addition, I've
> tried this as root just in case there's some strange permission thing
> going on.  Still no luck.
>
> *Any* ideas?
>
> Adam
>
> On Mon, 25 Aug 2003, Adam K Kirchhoff wrote:
>
> >
> > I'm hoping someone can help me out here.
> >
> > I recently moved a firewire card and DVD drive that had been in my FreeBSD
> > box to another computer.  I replaced it with an IDE DVD drive.  The
> > probelm is that now I can't get mplayer or vlc to play any DVDs that had
> > previously worked with the firewire drive.
> >
> > I have, of course, made sure that /dev/dvd is a symbolic link to /dev/acd0
> > instead of /dev/cd0 (as it used to be).  The only difference that I can
> > think of is that FreeBSD sees the firewire drive as a scsi drive and sees
> > the ide drive as an ide drive.  Is DVD playback just not supported on IDE
> > drives on FreeBSD -CURRENT?
> >
> > Adam
> >
> >
> >
> >
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: firewire vs IDE DVD.

[Adam K Kirchhoff]

Me again.

I've grabbed the output from mplayer and the dump from ktrace/kdump and
posted them at:

http://memory.visualtech.com/kdump.txt (975 kB)
http://memory.visualtech.com/mplayer.txt (1 kB)

>From mplayer.txt, you see that it's complaing:

"Couldn't open DVD device: /dev/dvd"

Now /dev/dvd is a symlink to /dev/acd0:

[ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/dvd
lrwxr-xr-x  1 root  wheel  3 Aug 25 15:54 /dev/dvd -> /dev/acd0

And /dev/acd0 looks like:

[ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/acd0
crw-r--r--  1 root  operator  117,   0 Aug 25 15:36 /dev/acd0

Note:  user 'adamk' is part of the 'operator' group.  In addition, I've
tried this as root just in case there's some strange permission thing
going on.  Still no luck.

*Any* ideas?

Adam

On Mon, 25 Aug 2003, Adam K Kirchhoff wrote:

>
> I'm hoping someone can help me out here.
>
> I recently moved a firewire card and DVD drive that had been in my FreeBSD
> box to another computer.  I replaced it with an IDE DVD drive.  The
> probelm is that now I can't get mplayer or vlc to play any DVDs that had
> previously worked with the firewire drive.
>
> I have, of course, made sure that /dev/dvd is a symbolic link to /dev/acd0
> instead of /dev/cd0 (as it used to be).  The only difference that I can
> think of is that FreeBSD sees the firewire drive as a scsi drive and sees
> the ide drive as an ide drive.  Is DVD playback just not supported on IDE
> drives on FreeBSD -CURRENT?
>
> Adam
>
>
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: About Sony i.Link

[Adam K Kirchhoff]

FreeBSD -CURRENT recognized the firewire DVD-ROM drive I had attached to
it.  If the install floppies support IEEE1394 (and I don't know if they
do), the DVD-ROM drive will just show up as /dev/cd* (depending on the
number of SCSI or firewire drives on the machine)

Have you tried booting off the floppies and seeing if it recognizes the
drive?

Adam

On Mon, 25 Aug 2003, DenniZ wrote:

> How can i install FreeBsd 5.1 from CDROM - Sony i.LINK
> CD-RW DVD-ROM Drive IEEE 1394 SBP2?
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

firewire vs IDE DVD.

[Adam K Kirchhoff]

I'm hoping someone can help me out here.

I recently moved a firewire card and DVD drive that had been in my FreeBSD
box to another computer.  I replaced it with an IDE DVD drive.  The
probelm is that now I can't get mplayer or vlc to play any DVDs that had
previously worked with the firewire drive.

I have, of course, made sure that /dev/dvd is a symbolic link to /dev/acd0
instead of /dev/cd0 (as it used to be).  The only difference that I can
think of is that FreeBSD sees the firewire drive as a scsi drive and sees
the ide drive as an ide drive.  Is DVD playback just not supported on IDE
drives on FreeBSD -CURRENT?

Adam



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: linux compatability

[Adam K Kirchhoff]

On Sat, 28 Dec 2002, [ISO-8859-1] Mikko Työläjärvi wrote:

> On Sat, 28 Dec 2002, Adam K Kirchhoff wrote:
>
> > Hey folks,
> >
> > I'm noticing some odd behaviour with the linux compatability
> > recently.  I have this small gnome app called gnome-run.  It links against
> > a number of gnome libraries that I've copied from my linux partition over
> > to /compat/linux and put in the appropriate directories.
> >
> > The problem is, when executing this app, the linker seems to try
> > and load the libaudiofile.so.0 file from my FreeBSD installation instead
> > of my /compat/linux installation.  When running gnome-run it only does
> > this for that one library (though other apps have shown this to be a
> > problem with other libraries such as libgmodule-2.0.so.0,
> > libglib-2.0.so.0, and libgobject-2.0.so.0)
> >
> > This is what happens when I try to launch "gnome-run" from an
> > xterm:
> >
> > [ adamk@sorrow ~ ]$ gnome-run
> > gnome-run: error while loading shared libraries:
> > /usr/local/lib/libaudiofile.so.0: ELF file OS ABI invalid
> >
> > Well, of course the OS ABI is invalid.  The libaudiofile library
> > it's trying to load is for FreeBSD, not Linux.  But, if I move the
> > libaudiofile.so.0 file from /usr/local/lib to /usr/local/lib/old, and
> > try to launch gnome-run, everything works fine.  So, if the FreeBSD
> > version of the library isn't present, it then looks for the Linux version.
> >
> > Any ideas what's going on or how to fix this?
>
> Run "/compat/linux/sbin/ldconfig".  That should update the path cache
> of the (linux) dynamic linker.

Didn't help :-(

> I assume the permissions on the libs already are reasonable.

[ adamk@sorrow ~ ]$ ls -l /compat/linux/usr/lib/libaudiofile.so.0*
lrwxr-xr-x  1 root  wheel  21 Dec 28 14:33
/compat/linux/usr/lib/libaudiofile.so.0 -> libaudiofile.so.0.0.2
-rwxr-xr-x  1 root  wheel  158396 Dec 28 14:33
/compat/linux/usr/lib/libaudiofile.so.0.0.2

Solved it!

It's LD_LIBRARY_PATH.  If you have the same FreeBSD library in your
LD_LIBRARY_PATH, it tries to use that library instead of the linux one :-)

Mikko, thanks for your help.  It was your tip on permissions that got me
to try the app as root.  When I saw that they worked as root, I realized
it had to be something in my environment.

Adam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

linux compatability

[Adam K Kirchhoff]

Hey folks,

I'm noticing some odd behaviour with the linux compatability
recently.  I have this small gnome app called gnome-run.  It links against
a number of gnome libraries that I've copied from my linux partition over
to /compat/linux and put in the appropriate directories.

The problem is, when executing this app, the linker seems to try
and load the libaudiofile.so.0 file from my FreeBSD installation instead
of my /compat/linux installation.  When running gnome-run it only does
this for that one library (though other apps have shown this to be a
problem with other libraries such as libgmodule-2.0.so.0,
libglib-2.0.so.0, and libgobject-2.0.so.0)

This is what happens when I try to launch "gnome-run" from an
xterm:

[ adamk@sorrow ~ ]$ gnome-run
gnome-run: error while loading shared libraries:
/usr/local/lib/libaudiofile.so.0: ELF file OS ABI invalid

Well, of course the OS ABI is invalid.  The libaudiofile library
it's trying to load is for FreeBSD, not Linux.  But, if I move the
libaudiofile.so.0 file from /usr/local/lib to /usr/local/lib/old, and
try to launch gnome-run, everything works fine.  So, if the FreeBSD
version of the library isn't present, it then looks for the Linux version.

Any ideas what's going on or how to fix this?

Adam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: VIA USB support problem...

[Adam K Kirchhoff]

Well, the bootloader definately loads the acpi driver, and this USB
controller is *definately* UHCI, not OHCI.  In addition, the default
kernel (which has both UCHI and OHCI support), doesn't get the USB working
either.  And yet, this kernel works flawlessly on an Intel motherboard I
have, USB and all.

Anyone else have any ideas?

Adam

On Fri, 27 Dec 2002, Sergey V. Golitzyn wrote:

>
>
> Sorry, i was wrong  about acpi, in the manuals said what
> ///
>  Note that the acpi driver is automatically loaded by the bootloader, and
>  should not normally be compiled into the kernel.
> //
>
> but i have it in kernel and system is stable, as i can see... :-)))
>
> Sergey V. Golitzyn (Russia)
>
>
>
> On Friday 27 December 2002 05:27, Sergey V. Golitzyn wrote:
> > Try to add
> >
> > device  acpi
> > device  ohci# OHCI PCI->USB interface
> >
> > into your kernel configuration...
> >
> > Any more diffrances i don't see...
> > See my kernel, if it will help you ...
> >
> > On Friday 27 December 2002 05:01, you wrote:
> > > On Fri, 27 Dec 2002, Sergey V. Golitzyn wrote:
> > > > On Friday 27 December 2002 02:44, Adam K Kirchhoff wrote:
> > > > > I'm having a difficult time getting any USB devices to work under
> > > > > -CURRENT with a VIA UHCI controller.
> > > > >
> > > > > uhci0:  port 0xd400-0xd41f irq 5 at device
> > > > > 7.2 on pci0 usb0:  on uhci0
> > > > > usb0: USB revision 1.0
> > > > > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > > > > uhub0: 2 ports with 2 removable, self powered
> > > > > uhub0: port error, restarting port 1
> > > > > uhub0: port error, giving up port 1
> > > > > ums0: Logitech USB Receiver, rev 1.10/15.00, addr 2, iclass 3/1
> > > > > ums0: 7 buttons and Z dir.
> > > > > uhub0: port error, restarting port 2
> > > > > uhub0: port error, giving up port 2
> > > > > uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr
> > > > > 3 uhub1: 4 ports with 4 removable, self powered
> > > > > ugen0: Logitech product 0xc207, rev 1.00/1.04, addr 4
> > > > > ugen0: setting configuration index 0 failed
> > > > > device_probe_and_attach: ugen0 attach returned 6
> > > > > uhci1:  port 0xd800-0xd81f irq 5 at device
> > > > > 7.3 on pci0 usb1:  on uhci1
> > > > > usb1: USB revision 1.0
> > > > > uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > > > > uhub2: 2 ports with 2 removable, self powered
> > > > > uhub2: port error, restarting port 1
> > > > > uhub2: port error, giving up port 1
> > > > > uhub2: port error, restarting port 2
> > > > > uhub2: port error, giving up port 2
> > > > >
> > > > > The above is from dmesg...  As you can see, it detects the UHCI
> > > > > controller, and sees the various devices (Logitech joystick: ugen0,
> > > > > Logitech mouse: ums0) but they're completely unusable.  I'm
> > > > > *assuming* it has something to do with the "port error" messages, but
> > > > > I'm not sure how to fix this.
> > > > >
> > > > > So, I guess the real question is, where should I be asking about
> > > > > this?
> > > >
> > > > As You Can see bellow, I have the same VIA USB and Logitech USB mouse,
> > > > but it's fine working from September, but I Have Another problem, my TV
> > > > Tuner Playung Audio, but don't show picture when i use "fxtv"... %-))
> > > > As a result I Have TV Radio :-
> > > >
> > > > Try to Attach You Kernel Configuration and Preloaded modules? may be
> > > > you forgot load USB module
> > >
> > > USB is compiled directly into the kernel, as you can see from the
> > > configuration file I've attached.
> > >
> > > Adam
>
>
>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: VIA USB support problem...

[Adam K Kirchhoff]

On Fri, 27 Dec 2002, Sergey V. Golitzyn wrote:

> On Friday 27 December 2002 02:44, Adam K Kirchhoff wrote:
> > I'm having a difficult time getting any USB devices to work under -CURRENT
> > with a VIA UHCI controller.
> >
> > uhci0:  port 0xd400-0xd41f irq 5 at device 7.2
> > on pci0 usb0:  on uhci0
> > usb0: USB revision 1.0
> > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > uhub0: port error, restarting port 1
> > uhub0: port error, giving up port 1
> > ums0: Logitech USB Receiver, rev 1.10/15.00, addr 2, iclass 3/1
> > ums0: 7 buttons and Z dir.
> > uhub0: port error, restarting port 2
> > uhub0: port error, giving up port 2
> > uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr 3
> > uhub1: 4 ports with 4 removable, self powered
> > ugen0: Logitech product 0xc207, rev 1.00/1.04, addr 4
> > ugen0: setting configuration index 0 failed
> > device_probe_and_attach: ugen0 attach returned 6
> > uhci1:  port 0xd800-0xd81f irq 5 at device 7.3
> > on pci0 usb1:  on uhci1
> > usb1: USB revision 1.0
> > uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub2: 2 ports with 2 removable, self powered
> > uhub2: port error, restarting port 1
> > uhub2: port error, giving up port 1
> > uhub2: port error, restarting port 2
> > uhub2: port error, giving up port 2
> >
> > The above is from dmesg...  As you can see, it detects the UHCI
> > controller, and sees the various devices (Logitech joystick: ugen0,
> > Logitech mouse: ums0) but they're completely unusable.  I'm *assuming* it
> > has something to do with the "port error" messages, but I'm not sure how
> > to fix this.
> >
> > So, I guess the real question is, where should I be asking about this?
>
> As You Can see bellow, I have the same VIA USB and Logitech USB mouse, but
> it's fine working from September, but I Have Another problem, my TV Tuner
> Playung Audio, but don't show picture when i use "fxtv"... %-))
> As a result I Have TV Radio :-
>
> Try to Attach You Kernel Configuration and Preloaded modules? may be you
> forgot load USB module

USB is compiled directly into the kernel, as you can see from the
configuration file I've attached.

Adam

#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files. 
# If you are in doubt as to the purpose or necessity of a line, check first 
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.369 2002/10/19 16:54:07 rwatson Exp $

machine i386
cpu I686_CPU
ident   SORROW
maxusers0

#To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" #Default places to look for devices.

makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols

options INET#InterNETworking
options INET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control lists
options UFS_DIRHASH #Improve performance on big directories
options MD_ROOT #MD is a potential root device
options NFSCLIENT   #Network Filesystem Client
options NFSSERVER   #Network Filesystem Server
options NFS_ROOT#NFS usable as root device, requires NFSCLIENT
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options EXT2FS  #Linux filesystem
options PROCFS  #Process filesystem (requires PSEUDOFS)
options PSEUDOFS#Pseudo-filesystem framework
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI
optio

VIA USB support problem...

[Adam K Kirchhoff]

I'm having a difficult time getting any USB devices to work under -CURRENT 
with a VIA UHCI controller.

uhci0:  port 0xd400-0xd41f irq 5 at device 7.2 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
ums0: Logitech USB Receiver, rev 1.10/15.00, addr 2, iclass 3/1
ums0: 7 buttons and Z dir.
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr 3
uhub1: 4 ports with 4 removable, self powered
ugen0: Logitech product 0xc207, rev 1.00/1.04, addr 4
ugen0: setting configuration index 0 failed
device_probe_and_attach: ugen0 attach returned 6
uhci1:  port 0xd800-0xd81f irq 5 at device 7.3 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhub2: port error, restarting port 1
uhub2: port error, giving up port 1
uhub2: port error, restarting port 2
uhub2: port error, giving up port 2

The above is from dmesg...  As you can see, it detects the UHCI
controller, and sees the various devices (Logitech joystick: ugen0, 
Logitech mouse: ums0) but they're completely unusable.  I'm *assuming* it 
has something to do with the "port error" messages, but I'm not sure how 
to fix this.  

So, I guess the real question is, where should I be asking about this?

Adam


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message