Hiyas I put both outputs on to try to give whoever was reading bug report as much info as possible.
It turns out ppdev wasn't loaded. I didn't realise that was split off onto a separate kernel, module and people who I had discussed problem with on irc thought it might have been an acpi/pnp issue (maybe it still is), since some feisty vanilla installs seem to have parport0, and others like my machine do not (by default). My problem was actually not printing related(apologies if the lp output added confusion), so am not sure if you still require that information from the printing wiki. I just wanted to make use of the parallel port to connect up a jtag interface. I was just mknod'ing a char dev file by hand before, but modprobing ppdev seems to do the trick too. Apologies for time wastage if this was the intended behaviour of feisty. On 25/08/07, Pascal De Vuyst <[EMAIL PROTECTED]> wrote: > Thanks for your bug report. > Some of the above output looks like dmesg output instead of lsmod output. > Could you please check if the ppdev module is loaded and attach the missing > information described here: https://wiki.ubuntu.com/DebuggingPrintingProblems. > > ** Changed in: linux-source-2.6.20 (Ubuntu) > Assignee: (unassigned) => Pascal De Vuyst > Status: New => Incomplete > > -- > /dev/parport0 not created by system on feisty > https://bugs.launchpad.net/bugs/134637 > You received this bug notification because you are a direct subscriber > of the bug. > -- /dev/parport0 not created by system on feisty https://bugs.launchpad.net/bugs/134637 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
