Or just run diskparts(8) again.
--- Begin Message ---
I'm not having a good day. I said:
> Also, after restarting partfs you need to reload the
> partition information:
>
> disk/prep -p /dev/sdXX/data >/dev/sdXX/ctl
Of course it should be:
disk/fdisk -p /dev/sdXX/data >/dev/sdXX/ctl
>> > ohci. oddly, my uhci ich9r machine doesn't recognize
>> > either of my extensive collection of two usb devices.
>>
>> You may be running the usbd with faulty dump.c. If your
>> devices show up in /dev/usb0/1/status with just one
>> line and 0x00 for Class/Subclass/Proto, then you're
>>
> > ohci. oddly, my uhci ich9r machine doesn't recognize
> > either of my extensive collection of two usb devices.
>
> You may be running the usbd with faulty dump.c. If your
> devices show up in /dev/usb0/1/status with just one
> line and 0x00 for Class/Subclass/Proto, then you're
> almost
>> Are you killing the old usbd before starting a new one?
>
> yes.
>
>> And is this uhci or ohci?
>
> ohci. oddly, my uhci ich9r machine doesn't recognize
> either of my extensive collection of two usb devices.
You may be running the usbd with faulty dump.c. If your
devices show up in /dev/u
> We added booting via the BIOS to 9load specifically for USB
Oh yes, I had forgotten that. None of my machines seem to be
willing to boot from any of my usb flash drives. However I have
just successfully resurrected my experiment with using a kfs
on usb disk as root - see /contrib/miller/usb/bo
> Sorry, I have no ohci hardware so I don't think I can
> help. Did the uhci machine recognise your devices
> before the recent update to add ohci support?
just got the machine monday.
i don't think i have any older kernels with usb
compiled in, but i'll see what i can find.
i'd like to rule out
> ohci. oddly, my uhci ich9r machine doesn't recognize
> either of my extensive collection of two usb devices.
Sorry, I have no ohci hardware so I don't think I can
help. Did the uhci machine recognise your devices
before the recent update to add ohci support?
> Are you killing the old usbd before starting a new one?
yes.
> And is this uhci or ohci?
ohci. oddly, my uhci ich9r machine doesn't recognize
either of my extensive collection of two usb devices.
- erik
> i've got things pretty wedged now -- usbd won't start
Are you killing the old usbd before starting a new one?
And is this uhci or ohci?
I'm not having a good day. I said:
> Also, after restarting partfs you need to reload the
> partition information:
>
> disk/prep -p /dev/sdXX/data >/dev/sdXX/ctl
Of course it should be:
disk/fdisk -p /dev/sdXX/data >/dev/sdXX/ctl
disk/prep -p /dev/sdXX/plan9 >/dev/sdXX/ctl
>> Where is 9fat, fs and nvram created by disk/prep?
>
> Did you forget the 'w' command?
Also, after restarting partfs you need to reload the
partition information:
disk/prep -p /dev/sdXX/data >/dev/sdXX/ctl
Oh yes, I misread the situation:
term% disk/prep /dev/sdXX/plan9
empty0 2 (2 sectors, 1.00 KB)
9fat 2 3 (29998 sectors, 14.64 MB)
fs 3 256913(226913 sectors, 110.79 MB)
nvram 256913 256914(1 sectors, 512 B
> Where is 9fat, fs and nvram created by disk/prep?
Did you forget the 'w' command?
Hello,
Thank you for working for usb support.
In trying usb/disk I have a question:
term% usb/disk
term% disk/partfs /n/disk/0/data
term% disk/mbr /dev/sdXX/data
term% disk/fdisk -baw /dev/sdXX/data
term% disk/prep /dev/sdXX/plan9
empty0 2 (2 sectors, 1.00 KB)
9fat
thanks for the update. i have switched to a slightly
more agreeable key but i have a new way to fail. the key
works the first time. but the second time i connect the same
key, i get
; usbfat:
setupreq: write err: No response
usb/disk: describedevice: error writing usb de
We added booting via the BIOS to 9load specifically for USB (though it
may have other uses), so that we wouldn't have to add to 9load and
maintain 8,000 lines, and growing, of complex USB code (though that's
likely due to the inherent complexity of USB rather than being the
fault of those who have
> geoff pointed out that usb/disk pulls in a lot of stuff and might need
> some work to run in the kernel.
Usb root can be done by putting usb/disk and usb/usbd into /boot and
hacking /sys/src/9/boot/local.c a bit. I tried it once and it worked
albeit slowly. However, getting 9load to use usb di
> Do you mean why doesn't the ctl file accept partition commands?
> You can always use fs(3) for that. But usb root is not very
> practical anyway, at least with uhci, because of a stubborn
> bug in the driver which makes transfers very very slow. Now
> there's ohci support I would be interested
> Actually, partfs(8) provides devsd-compatible partitions
Cool - I hadn't noticed when that appeared.
Actually, partfs(8) provides devsd-compatible partitions and is
probably a better choice for this than fs(3). It wasn't cited in
usbdisk(4)'s SEE ALSO, but it is now.
> one final question, is there an advantage to usb/disk creating a fs
> that's incompatable with devsd? it would seem to make booting
> from usb root difficult.
Do you mean why doesn't the ctl file accept partition commands?
You can always use fs(3) for that. But usb root is not very
practical a
Warning!, the dump.c I sent Sape has a bug.
search for "len = b[0]-1", in pdesc(), replace that with
"len = b[0]".
sorry for the mistake.
> From: [EMAIL PROTECTED]
> To: 9fans@cse.psu.edu
> Reply-To: 9fans@cse.psu.edu
> Date: Tue Feb 12 15:36:36 CET 2
>> Nemo found a bug in usb/lib/dump.c that may well account for
>> this. I incorporated his change (and fixed a bug in his code :-).
>> I'll ask Geoff to push it out today.
>>
>> Sape
>
> excellent. i'll give it a shot.
>
> - erik
Give it a shot now:
/sys/src/cmd/usb/lib/dump.c
#
> Nemo found a bug in usb/lib/dump.c that may well account for
> this. I incorporated his change (and fixed a bug in his code :-).
> I'll ask Geoff to push it out today.
>
> Sape
excellent. i'll give it a shot.
- erik
> usbd is exiting when i have a camera which is off
> attached:
>
> ; usb/usbd -v
> ; echo $status
> usbd 1827: usbd: setup0: usb0/1: transaction error
>
> - erik
Nemo found a bug in usb/lib/dump.c that may well account for
this. I incorporated his change (and fixed a bug in his code :-).
I'll
> Looking at /sys/src/cmd/usb/usbd/usbd.c, I wonder whether
> your problem has something to do with these lines?
>
> //unconscionable kludge (testing camera)
> if(d->class == 10) setup0(d, RH2D|Rinterface, SET_INTERFACE, 10, 0, 0);
thanks for the suggestion, but the camera was a red herring.
it
Looking at /sys/src/cmd/usb/usbd/usbd.c, I wonder whether
your problem has something to do with these lines?
//unconscionable kludge (testing camera)
if(d->class == 10) setup0(d, RH2D|Rinterface, SET_INTERFACE, 10, 0, 0);
> ; usb/usbd -v
Try 'usb/usbd -d1' for more information.
usbd is exiting when i have a camera which is off
attached:
; usb/usbd -v
; echo $status
usbd 1827: usbd: setup0: usb0/1: transaction error
- erik
29 matches
Mail list logo
