From: mag <ma...@ro...> - 2002-02-12 03:36:30
|
> Hmm, so can I safely assume that you're using the linux-sh-dc from > CVS? Yep. > > Another idea that crossed my mind, was that this could be caused by > me > > trying to use devfs, but not having the devfsd (yet). But I don't > think > > that that's the problem, because I am pretty sure it does not even > get > > to the first startup scripts anyway, and that's where it is normally > > started. > > Could you let us know if it still fails if you use the manually > created > device node (`mknod gdrom b 250 0')? I tried doing that and compiling devfs out of the kernel, but that did not do anything. > Also, I've attached a patch that prints out GD-ROM command values in > hex. > If the problem persists, could you send a dump of the command values > printed? > > If it's something more, I'll try to look into it. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. gdrom_do_command: 00: 70 1f 00 00 00 00 gdrom_do_command: 06: 00 00 00 00 00 00 gdrom_do_command: 00: 30 20 00 00 96 00 gdrom_do_command: 06: 00 00 00 00 01 00 GD-ROM: Got larger result maple(1,0): Connected(function 0x1) input0: controller(0xf06fe): Dreamcast Controller maple(0,0): Connected(function 0x1) input1: controller(0xf06fe): Dreamcast Controller maple(0,1): Connected(function 0xe) maple(0,1): No driver for function(s): e. Any ideas on what's wrong here? Thanks, mag. |