Re: [9fans] usb configuration
On 04/03/2014 12:28, Steve Simon wrote: And I hate its scroll button, but I love its three buttons! I hate scroll buttons too. I was very happy when I discovered the dell DY651A mouse: http://www8.hp.com/uk/en/products/oas/product-detail.html?oid=403895#!tab=features also branded as IBM M-U0013-o -Steve Thank you Steve. Now, what is miss would be a mouse like the Dell DY651A + a lateral scrolling wheel, maybe. [The thing is that I took the habit of using scrolling wheels, maybe this is a habit I can forget. Forgetting such habits may help to do better work in the sense that it would avoid compulsive maneuvers, compulsive scroll here. And let the good ideas flow.] Nicolas
Re: [9fans] Raspberry Pi: won't recognize the USB mouse
Sorry, my suggested correction is still wrong. b[0] is the length of
the whole descriptor not the length of the string. So I suggest this
(I tested it on exactly one device) -
static char*
mkstr(uchar *b, int n)
{
Rune r;
char *us;
char *s;
char *e;
if(n = 2 || b[0] n || (b[0] 1) != 0)
return strdup(none);
n = (b[0] - 2)/2;
b += 2;
...
Or according to taste, one could do this (not tested) -
static char*
mkstr(uchar *b, int n)
{
Rune r;
char *us;
char *s;
char *e;
if(n b[0])
n = b[0];
if(n = 2 || (n 1) != 0)
return strdup(none);
n = (n - 2)/2;
b += 2;
...
I'm not sure which I prefer. They are semantically slightly different
(if one of b[0] or n is odd).
Re: [9fans] Raspberry Pi: won't recognize the USB mouse
Apologies for last message, it was meant to be directed to quans...@quanstro.net as part of a conversation. Please ignore.
Re: [9fans] imac keyboard issues
I wouldn't spend time on this ... there are many better cheaper choices of keyboard to use with plan 9.
Re: [9fans] imac keyboard issues
On Wed Mar 5 06:02:56 EST 2014, 9f...@hamnavoe.com wrote: I wouldn't spend time on this ... there are many better cheaper choices of keyboard to use with plan 9. since it's not clear to me what the issue is, and setaddress returns a transaction error, i was going on the assumption that there was something slightly off about ehci setup. is this a bad assumption? - erik
Re: [9fans] imac keyboard issues
since it's not clear to me what the issue is, and setaddress returns a transaction error, i was going on the assumption that there was something slightly off about ehci setup. is this a bad assumption? I think it is. Transaction error covers a multitude of sins. If you suspect ehci, try the same experiment with the non-ehci raspberry pi.
Re: [9fans] imac keyboard issues
since it's not clear to me what the issue is, and setaddress returns a transaction error, i was going on the assumption that there was something slightly off about ehci setup. is this a bad assumption? I think it is. Transaction error covers a multitude of sins. If you suspect ehci, try the same experiment with the non-ehci raspberry pi. this is from a pi: /boot/usbd: /dev/usb/ep4.0: port 1 attach sts 0x101 /boot/usbd: /dev/usb/ep4.0: port 1: attached status 0x103 /boot/usbd: opendev 0x65538 /dev/usb/ep8.0 /boot/usbd; /dev/usb/ep4.0: port 1: maxpkt 8 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 usbotg: ep8.0 error intr 0402 /boot/usbd: /dev/usb/ep8.0 csp hub.0.0 vid 0x05ac did 0x1003 refs 1 Mitsumi Electric Mitsumi Electric none conf: cval 1 attrib a0 50 mA iface csp hub.0.0 alt 0 attr 3 ival 255 ep id 1 addr 129 dir in type intr itype 0 maxpkt 1 ntds 1 /boot/usbd: /dev/usb/ep4.0: port 1: configed: /dev/usb/ep8.0 /boot/usbd: hub 0x65b98 allocated: ports 3 pwrms 100 max curr 50 pwrm 1 cmp 1 leds 0 usb/hub... /boot/usbd: /dev/usb/ep8.0 port 1: sts - 0x0 - - 0x100 /boot/usbd: /dev/usb/ep8.0 port 2: sts - 0x0 - - 0x100 /boot/usbd: /dev/usb/ep8.0: port 3 attach sts 0x101 /boot/usbd: /dev/usb/ep8.0: port 3: attached status 0x103 /boot/usbd: opendev 0x65c98 /dev/usb/ep9.0 usbotg: ep9.0 error intr 0082 usbotg: ep9.0 error intr 0082 usbotg: ep9.0 error intr 0082 usbotg: ep9.0 error intr 0082 /boot/usbd: /dev/usb/ep8.0: port 3: attach setaddress: i/o error /boot/usbd: closedev 0x65c98 /dev/usb/ep9.0 /boot/usbd: /dev/usb/ep4.0 port 1: sts p 0x101 - ep 0x103 - erik
Re: [9fans] imac keyboard issues
usbotg: ep9.0 error intr 0082 /boot/usbd: /dev/usb/ep8.0: port 3: attach setaddress: i/o error 0082 is a transaction error - so the problem wasn't in the ehci layer.
Re: [9fans] Welcome Plan 9 community
On 03/04/2014 12:19 AM, Alexandru Gheorghe wrote:
On 03/03/2014 10:53 PM, Lyndon Nerenberg wrote:
On Mar 3, 2014, at 12:52, Alexandru Gheorghe alghe.glo...@gmail.com wrote:
should we gather some configuration steps/examples for known stable
builds of vbox and post them in a wiki somewhere(?)
Yes! That's what the wiki is for.
sure, I agree. I am only enquiring so as to brainstorm if we should
actually (and be better of) providing a sort of how-to in debugging
network setup on plan9 (besides what is already on the net).
i.e., even if somebody runs into trouble (ultimately), it is better off
posting his output of:
cat /net/ndb
ls /net | grep ether (optional)
ls /net/ether*
ip/ipconfig -DGP
in case he/she is running in recv timeout for 15 secs; shortcut:
ppid=`{ps | grep ipconfig | awk '{print $2}'}
echo kill /proc/$ppid/note
sorry for the ` as I am writing from GNU/Linux
this may not fully represent what is needed, but this is what I could
gather in few minutes of man pages and some trial and error, after only
30 minutes of Plan9 experience. so I am sure far more experienced users
from the mailinglist can contribute to the article
I will try to tackle it this weekend from this approach/point of view,
maybe I can come up with something rather useful, if not, at least
networking setup for the build I use of vbox/os/v
ersion etc.
Hmm, actually related to this, I encounter dhcprecv read timed out.
I searched and seems there are some interrupt related issues, this
happens with VirtualBox (4.1.18_Debian r78361) for me, not on bare
metal. NIC is in NAT, tried with a second NIC in bridged; definitely not
the NIC as the below code also points out in !0 and !1
dhcp.c:
---
void
dhcprecv(void)
{
[...]
uchar buf[8000], vopts[256], taddr[IPaddrlen];
[...]
memset(buf, 0, sizeof buf);
alarm(1000);
!0 n = read(conf.fd, buf, sizeof buf);
alarm(0);
if(n 0){
rerrstr(err, sizeof err);
!1 if(strstr(err, interrupt) == nil)
warning(dhcprecv: bad read: %s, err);
else
DEBUG(dhcprecv: read timed out);
return;
n - ipconfig.h:
typedef struct Conf Conf;
[...]
struct Conf
{
[...]
/* dhcp specific */
int fd;
Any ideas? I don't seem to find plan9.ini to try the fix Akshat Kumar
pointed out in [1]; all the other answers from erik and ron are bare
metal hardware related (like the original post). How to deal with this
in VirtualBox?
Chipset is PIIX3 [2]
References:
[1]
https://groups.google.com/forum/?_escaped_fragment_=topic/comp.os.plan9/9nlmIoY4-C8#!topic/comp.os.plan9/9nlmIoY4-C8
[2] https://www.virtualbox.org/manual/ch03.html#settings-motherboard
(under Chipset section) -- there is another option ICH9 and the MSI
seems a plus; not sure how this will interact with Plan9 but I'll give
it a go
--
; Alexandru Gheorghe
; alghe.global {at} gmail {dot} com
; OpenPGP key ID 0xCAF985D2
signature.asc
Description: OpenPGP digital signature
Re: [9fans] Welcome Plan 9 community
On Wed, Mar 5, 2014 at 8:23 PM, Alexandru Gheorghe alghe.glo...@gmail.com wrote: On 03/04/2014 12:19 AM, Alexandru Gheorghe wrote: On 03/03/2014 10:53 PM, Lyndon Nerenberg wrote: On Mar 3, 2014, at 12:52, Alexandru Gheorghe alghe.glo...@gmail.com wrote: should we gather some configuration steps/examples for known stable builds of vbox and post them in a wiki somewhere(?) I've got some instructions for running Plan 9 on Virtual Box, I was going to post them on the wiki as Alexandru Gheorghe suggested. I got onto the wiki and tried to edit the sandbox as a first step but got a curious error when I tried to Put: Wiki commit 1028330739 12 -1: '/sys/lib/wiki/d/2.hist' permission denied. Anyway here are the instructions for future reference. PLAN9 INSTALL = VirtualBox -- Set up VM in Virtual Box v4.3.8, OS X 9 host, recent (2014-03-02) CD Plan9.iso 64MB RAM 2GB hard disk NAT network, Intel PRO/1000 MT Server (82545EM) PIIX3 chipset PS/2 Mouse No USB No Serial No Sound VT-x/AMD-V enabled Storage PIIX4 IDE controller Install from CD --- Monitor: 1024x768x8 VESA Mouse: PS2INTELLIMOUSE Accept all defaults Location of archives: / Plan 9 boot, install MBR Remove the virtual CD from the virtual drive Reboot (type CTRL-T CTRL-T R) Login - Accept default on 'Root is from:' User: glenda Get familiar with rio/acme Net Access -- Open /rc/bin/termrc in acme Uncomment the lines # if (! test -e /net/ipifc/0/ctl) # ip/ipconfig and reboot.
Re: [9fans] Welcome Plan 9 community
On 03/05/2014 10:23 PM, Alexandru Gheorghe wrote:
On 03/04/2014 12:19 AM, Alexandru Gheorghe wrote:
On 03/03/2014 10:53 PM, Lyndon Nerenberg wrote:
On Mar 3, 2014, at 12:52, Alexandru Gheorghe alghe.glo...@gmail.com wrote:
should we gather some configuration steps/examples for known stable
builds of vbox and post them in a wiki somewhere(?)
Yes! That's what the wiki is for.
sure, I agree. I am only enquiring so as to brainstorm if we should
actually (and be better of) providing a sort of how-to in debugging
network setup on plan9 (besides what is already on the net).
i.e., even if somebody runs into trouble (ultimately), it is better off
posting his output of:
cat /net/ndb
ls /net | grep ether (optional)
ls /net/ether*
ip/ipconfig -DGP
in case he/she is running in recv timeout for 15 secs; shortcut:
ppid=`{ps | grep ipconfig | awk '{print $2}'}
echo kill /proc/$ppid/note
sorry for the ` as I am writing from GNU/Linux
this may not fully represent what is needed, but this is what I could
gather in few minutes of man pages and some trial and error, after only
30 minutes of Plan9 experience. so I am sure far more experienced users
from the mailinglist can contribute to the article
I will try to tackle it this weekend from this approach/point of view,
maybe I can come up with something rather useful, if not, at least
networking setup for the build I use of vbox/os/v
ersion etc.
Hmm, actually related to this, I encounter dhcprecv read timed out.
I searched and seems there are some interrupt related issues, this
happens with VirtualBox (4.1.18_Debian r78361) for me, not on bare
metal. NIC is in NAT, tried with a second NIC in bridged; definitely not
the NIC as the below code also points out in !0 and !1
dhcp.c:
---
void
dhcprecv(void)
{
[...]
uchar buf[8000], vopts[256], taddr[IPaddrlen];
[...]
memset(buf, 0, sizeof buf);
alarm(1000);
!0 n = read(conf.fd, buf, sizeof buf);
alarm(0);
if(n 0){
rerrstr(err, sizeof err);
!1 if(strstr(err, interrupt) == nil)
warning(dhcprecv: bad read: %s, err);
else
DEBUG(dhcprecv: read timed out);
return;
n - ipconfig.h:
typedef struct Conf Conf;
[...]
struct Conf
{
[...]
/* dhcp specific */
int fd;
Any ideas? I don't seem to find plan9.ini to try the fix Akshat Kumar
pointed out in [1]; all the other answers from erik and ron are bare
metal hardware related (like the original post). How to deal with this
in VirtualBox?
Chipset is PIIX3 [2]
References:
[1]
https://groups.google.com/forum/?_escaped_fragment_=topic/comp.os.plan9/9nlmIoY4-C8#!topic/comp.os.plan9/9nlmIoY4-C8
[2] https://www.virtualbox.org/manual/ch03.html#settings-motherboard
(under Chipset section) -- there is another option ICH9 and the MSI
seems a plus; not sure how this will interact with Plan9 but I'll give
it a go
OK, bad idea. I got it fixed finally.
Chipset for motherboard certainly: PIIX3
NIC info:
- Attached: NAT
- Adapter type (changing this made it working): Intel PRO/1000 MT Server
(82545EM)
- Promisc. mode: Deny
- No port forwarding
Can ping IPs (Google dns: 8.8.8.8 for example), now I have to setup dns.
--
; Alexandru Gheorghe
; alghe.global {at} gmail {dot} com
; OpenPGP key ID 0xCAF985D2
signature.asc
Description: OpenPGP digital signature
Re: [9fans] Welcome Plan 9 community
On Wed, Mar 5, 2014 at 8:23 PM, Alexandru Gheorghe alghe.glo...@gmail.com wrote: Hmm, actually related to this, I encounter dhcprecv read timed out. I got those kind of errors for every type of network card apart from 'Intel PRO/1000 Server (82545EM)' Which one are you using? Pete
Re: [9fans] Welcome Plan 9 community
On 03/05/2014 10:43 PM, Peter Hull wrote:
NAT network, Intel PRO/1000 MT Server (82545EM)
so it seems this nic model works best with Plan9 within VirtualBox
PIIX3 chipset
and this as well
thanks!
--
; Alexandru Gheorghe
; alghe.global {at} gmail {dot} com
; OpenPGP key ID 0xCAF985D2
signature.asc
Description: OpenPGP digital signature
