Menu
▾
▴
|
From: Kevin K. <sup...@gm...> - 2004-12-20 21:29:23
|
i posted this yesterday on the leaf mailing list, was hoping to get a fix soon and it's not had any hits yet, so i'm re-posting - hope that's not a problem. anyway, to the problem: the lcd4linux module can't gain access to the parallel port. i'm using bering-uClibc, 2.1 on a EPIA 5000 mini-itx motherboard. on startup i'm loading the ppdev.o, parport.o, and parport_pc.o modules and the messages file under /var/log shows "parport0: PC-style at 0x378 [PCSPP(,...)]" on boot-up. however, when i run the lcd4linux module - after everything initializes and it goes to set up the parallel port i get: parport.c: using ppdev /dev/parport0 parport: open(/dev/parport0) failed: No such device HD44780: could not initialize parallel port! any assistance would be appreciated, i'm not sure why it says there's no device parport0, since it seems to initialize properly on boot-up. thanks, kevin. |
|
From: Michael R. <re...@eu...> - 2004-12-21 04:39:43
|
Hi Kevin, > i posted this yesterday on the leaf mailing list, was hoping to get a > fix soon and it's not had any hits yet, so i'm re-posting - hope > that's not a problem. No. it is not. > the lcd4linux module can't gain access to the parallel port. > i'm using bering-uClibc, 2.1 on a EPIA 5000 mini-itx motherboard. > > on startup i'm loading the ppdev.o, parport.o, and parport_pc.o > modules and the messages file under /var/log shows "parport0: PC-style > at 0x378 [PCSPP(,...)]" on boot-up. > > however, when i run the lcd4linux module - after everything > initializes and it goes to set up the parallel port i get: > parport.c: using ppdev /dev/parport0 > parport: open(/dev/parport0) failed: No such device > HD44780: could not initialize parallel port! > > any assistance would be appreciated, i'm not sure why it says there's > no device parport0, since it seems to initialize properly on boot-up. Hmmm... - is there a /dev/parport0 device file? (or is it called /dev/parport/0)? - what's the major/minor number of /dev/parport0? - as a quick hack, you could try to specify "Port 0x378" in your lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is ugly, but if it works... who cares :-) bye, Michael -- Michael Reinelt <re...@eu...> http://members.eunet.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Martin H. <ma...@he...> - 2004-12-21 09:55:57
|
Hi Michael, Michael Reinelt wrote: > - as a quick hack, you could try to specify "Port 0x378" in your > lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is > ugly, but if it works... who cares :-) no, that will not work on a LEAF box - raw I/O is not allowed from userspace on the LEAF kernels (part of the grsecurity patches we apply). Martin |
|
From: Kevin K. <sup...@gm...> - 2004-12-21 15:29:42
|
As Martin said, i'm blocked from directly accessing the port - that's why i'm onto the parport type access. I neglected to mention that i'm really not familiar with linux that much and have only learned as much as required to setup and use this LEAF box. i'd really love some direction as to how to check how exactly the parport device should be accessed. if i look under /dev/ i see parport0, parport1, etc. up to parport3. i believe leaf does not use the subdirectory system for parport devices like some other linux distributions (i'm always up for being corrected, though).. i'm not sure what you mean by major/minor number of /dev/parport0 - please direct me as to how to provide more information on this front. is there a way to check and see that the parallel port is actually configured and ready for use? how do i know if i'm just not calling it properly with the port specification of /dev/parport0 ? i greatly appreciate the help, i'd love to sort this out but i don't know enough about it to move ahead any farther on my own. On Tue, 21 Dec 2004 10:55:37 +0100, Martin Hejl <ma...@he...> wrote: > Hi Michael, > > Michael Reinelt wrote: > > - as a quick hack, you could try to specify "Port 0x378" in your > > lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is > > ugly, but if it works... who cares :-) > no, that will not work on a LEAF box - raw I/O is not allowed from > userspace on the LEAF kernels (part of the grsecurity patches we apply). > > Martin > |
|
From: Michael R. <re...@eu...> - 2004-12-21 21:10:54
|
Hi there, > Michael Reinelt wrote: > >> - as a quick hack, you could try to specify "Port 0x378" in your >> lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is >> ugly, but if it works... who cares :-) > > no, that will not work on a LEAF box - raw I/O is not allowed from > userspace on the LEAF kernels (part of the grsecurity patches we apply). Oh, silly me - now I remember.... bye, Michael -- Michael Reinelt <re...@eu...> http://members.eunet.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Kevin K. <sup...@gm...> - 2004-12-22 00:40:00
|
talked through a few things Michael - turns out the modules were loading in the wrong order, switched the load order to parport.o, parport_pc.o, and lastly ppdev.o and it's working now. thanks a lot, appreciate the help - great package, looks great, i'll be playing with the configuration options for a while. On Tue, 21 Dec 2004 22:10:43 +0100, Michael Reinelt <re...@eu...> wrote: > Hi there, > > > Michael Reinelt wrote: > > > >> - as a quick hack, you could try to specify "Port 0x378" in your > >> lcd4linux.conf. Then it will not use ppdev, but raw port i/o (which is > >> ugly, but if it works... who cares :-) > > > > no, that will not work on a LEAF box - raw I/O is not allowed from > > userspace on the LEAF kernels (part of the grsecurity patches we apply). > > Oh, silly me - now I remember.... > > bye, Michael > > -- > Michael Reinelt <re...@eu...> > http://members.eunet.at/reinelt > GPG-Key 0xDF13BA50 > ICQ #288386781 > |
