USB - current

Anyone ever tries to patch -current (3.99.9) to include USB support?
I know there was a discussion some while ago about patching gt.c, but, I 
tried without luck..

I got this:
dmesg: (boot with an old Maxtor plucked in)
[snip]
viaide0: secondary channel interrupting at irq 15
atabus1 at viaide0 channel 1
uhci0 at pci0 dev 9 function 2: VIA Technologies VT83C572 USB Controller 
(rev. 0x02)
uhci0: can't map i/o space
uhci1 at pci0 dev 10 function 0: VIA Technologies VT83C572 USB 
Controller (rev. 0x61)
uhci1: interrupting at irq 9
usb0 at uhci1: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 10 function 1: VIA Technologies VT83C572 USB 
Controller (rev. 0x61)
uhci2: interrupting at irq 0
usb1 at uhci2: USB revision 1.0
uhub1 at usb1
uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
VIA Technologies VT8237 EHCI USB Controller (USB serial bus, interface 
0x20, revision 0x63) at
pci0 dev 10 function 2 not configured

Re: USB - current

On Oct 4, 2005, at 5:39 PM, Arne Jensen wrote:

>
> Anyone ever tries to patch -current (3.99.9) to include USB support?
> I know there was a discussion some while ago about patching gt.c,  
> but, I tried without luck..
>
> I got this:
> dmesg: (boot with an old Maxtor plucked in)

When I asked a bit ago (perhaps off-list) IIRC NEC chipset USB cards  
work OK, VIA might be problematic.

I bought an inexpensive NEC chipset USB card a little while ago, but  
have not had time to install it to try it out.

HTH.

Brian

Re: USB - current

Hi Brian
Well I'm a bit confused.
dmesg report this:
..
uhci0 at pci0 dev 9 function 2: VIA Technologies VT83C572 USB Controller 
(rev. 0x02)
uhci0: can't map i/o space
uhci1 at pci0 dev 10 function 0: VIA Technologies VT83C572 USB 
Controller (rev. 0x61)
uhci1: interrupting at irq 9
usb0 at uhci1: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 10 function 1: VIA Technologies VT83C572 USB 
Controller (rev. 0x61)
uhci2: interrupting at irq 0
usb1 at uhci2: USB revision 1.0
uhub1 at usb1
uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
VIA Technologies VT8237 EHCI USB Controller (USB serial bus, interface 
0x20, revision 0x63) at pci0 dev 10 function 2 not configured
tlp1 at pci0 dev 12 function 0: DECchip 21143 Ethernet, pass 4.1
..
Especially the sentence: "uhci0: can't map i/o space" was worrying me.

If I pluck in a memory-stick dmesg reports this:
..
umass0 at uhub1 port 2 configuration 1 interface 0

Re: USB - current

On Oct 5, 2005, at 5:05 AM, Arne Jensen wrote:

>
> But "mount_msdos /dev/sd0d /mnt" actually mount the bird. - And  
> it's works 
>
> Arne

Could be  what was meant by "problematic" :)

Glad it is working.  I have great expectations for my card now!  Some  
weekend I'll have time to take care of computer tasks...

-Brian

Fwd: Revised estimate for release date of NetBSD 3.0

"Process (pid 1) got signal 12" after successful restore process

Hi all,

I've got "Process (pid 1) got signal 12" after I
successfully created a 2.0.2 port, burnt it and
restored a Qube 2. I am a newbie in NetBSD, but an
expert in Linux. Seems that the system can not find
the /bin/sh shell interpreter, which was the original
message before the one I show here.

Please, anyone -- how did this problem occured and how
do I fix it?

Thanks!

	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

SCSI on RAQ2+

I'm thinking of hooking up my DDS2 Tape drive to my RAQ2+ (on-board SCSI) for
backups.  Has anyone had success with this setup?  I checked the archives via
Google and haven't seen anything were anyone reported success with the
on-board SCSI on a RAQ, just via an add-in card on the Qube2's.

Thanks,

Robert Thille

--
Robert Thille                7575 Meadowlark Dr.; Sebastopol, CA 95472
Home: 707.824.9753    Office/VOIP: 707.780.1560     Cell: 707.217.7544
Robert.Thille <at> rangat.org   YIM:rthille   http://www.rangat.org/rthille
Cyclist, Mountain Biker, Freediver, Kayaker, Rock Climber, Hiker, Geek
May your spirit dive deep the blue, where the fish are many and large!

Lock ups with Samba 3.0.14 and NetBSD 2.0.2

Hi All,

I've recently replaced my faulty drive (200Gb) with a new one (500Gb).  I
decided to forgo the use of the Promise Ultra100 TX2 IDE card in favour of
quieter cooling from a PCI slot fan, i.e. single large drive instead of the
Rushmere solution.  

Unfortunately I'm experiencing quite a few lockups when transferring large
quantities of data to the Qube, these manifest themselves at random periods
but seem to allow about 5-40Gb to be transferred before the Qube locks up.

I've looked through the mailing list and though there seems to be a number
of you who have experienced something similar I can't locate a definitive
solution to the problem.  Should I switch back to the Rushmere solution and
put up with a noisy 40mm fan, or should I investigate moving back to 1.6.1
or an older version of Samba? ...or is there something else I could
consider?

Thanks in advance,

Sean.

Re: "Process (pid 1) got signal 12" after successful restore process

I have fixed it. The instructions on the documentation
site were not up to date. I have asked Alex and he
pointed me to the right document.

--- Evgueni Tzvetanov <attroppa <at> yahoo.com> wrote:

> Hi all,
> 
> I've got "Process (pid 1) got signal 12" after I
> successfully created a 2.0.2 port, burnt it and
> restored a Qube 2. I am a newbie in NetBSD, but an
> expert in Linux. Seems that the system can not find
> the /bin/sh shell interpreter, which was the
> original
> message before the one I show here.
> 
> Please, anyone -- how did this problem occured and
> how
> do I fix it?
> 
> Thanks!
> 
> 
> 
> 	
> 		
> __________________________________ 
> Yahoo! Mail - PC Magazine Editors' Choice 2005 
> http://mail.yahoo.com
> 

	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

-current currently safe for -cobalt?

Hi;

I've running -current from the last netboot CD that was so nicely  
built , early July I think (did any of that info ever make it onto  
the official netbsd site??) with a -current pkgsrc from about the  
same time.

Is it safe to update my pkgsrc at this time?  I've occasionally read  
of some issues on the main -netbsd mailing list.

Thanks,

Brian