> You might want to see what debugging messages you've got being generated. > Try reconfiguring syslogd to redirect 'kernel.debug' to a seperate logfile.
I must admit never checking anything else but /var/log/messages. I get the same messages in kern.log and syslog: localhost kernel: usb.c: registered new driver skeleton localhost kernel: usb-skeleton.c: USB HC08 device now attached to /dev/usbskel0 localhost kernel: usb.c: skeleton driver claimed interface c3fb92c0 localhost kernel: usb-skeleton.c: USB 68HC08JB8 Driver v0.1 localhost kernel: Unable to handle kernel paging request at virtual address 00011fbc localhost kernel: printing eip: localhost kernel: c48283d6 localhost kernel: *pde = 00000000 localhost kernel: Oops: 0000 localhost kernel: CPU: 0 which I do not find very helpful > Also, I assume that the open and close calls are fine (no seg faults) but > the write causes the problem? Try changing the write call to send a zero > lengh buffer, this should be successfully caught by the skeleton and output > some debugging. I will check this when I get physical access to my usb-enabled computer again. > Also, why bother taking the devfs stuff out, why not use it? Mainly because I do not understand it, and since I do not run devfsd (I did compile it and enable this option in my kernel, but I would like to avoid multiplying difficulties and would at first like to have everything working with my current /dev setup and then try to understand what devfsd does). Actually, what is the default location of the USB devs ? At the moment I manually created /dev/usbskel0 (with major 180 and minor 200 -- I do not have any oyher USB peripheral), but should it be in /dev/usb/usbskel0 ? Thanks for the help, Jean-Michel _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
