A Null Printer Cable for PLIP
Hi How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? thx -- Andriy T. Yanko System Administrator MPP MEDIA ATY1-RIPE ATY1-UANIC
Re: A Null Printer Cable for PLIP
Hi all, Andriy T.Yanko wrote: Hi How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? You can see it in net-howto, and in plip-install howto. Faster, here: http://www.tldp.org/HOWTO/PLIP-Install-HOWTO-8.html thx Nothing. Salud y Revolución. Lobo. -- Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux, para no atar mis manos con las cadenas del soft propietario. - Desde El Ejido, en Almeria, usuario registrado linux #294013 http://www.counter.li.org
Re: A Null Printer Cable for PLIP
Hello What kinds of problems do you have exactly? > How to make ___WORKING___ Null Printer Cable for use with a PLIP > connection? On my woody installation, I found two howtos and one kernel documentation. /usr/share/doc/HOWTO/en-txt/mini/PLIP.gz /usr/share/doc/HOWTO/en-txt/PLIP-Install-HOWTO.gz /usr/src/kernel-source-2.4.17/Documentation/networking/PLIP.txt Quoting PLIP.txt: Parallel Transfer Mode 0 Cable == The cable for the first transfer mode is a standard printer "null" cable which transfers data four bits at a time using data bit outputs of the first port (machine T) connected to the status bit inputs of the second port (machine R). There are five status inputs, and they are used as four data inputs and a clock (data strobe) input, arranged so that the data input bits appear as contiguous bits with standard status register implementation. A cable that implements this protocol is available commercially as a "Null Printer" or "Turbo Laplink" cable. It can be constructed with two DB-25 male connectors symmetrically connected as follows: STROBE output 1* D0->ERROR 2 - 15 15 - 2 D1->SLCT3 - 13 13 - 3 D2->PAPOUT 4 - 12 12 - 4 D3->ACK 5 - 10 10 - 5 D4->BUSY6 - 11 11 - 6 D5,D6,D7 are 7*, 8*, 9* AUTOFD output 14* INIT output 16* SLCTIN 17 - 17 extra grounds are 18*,19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end If the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only. Parallel Transfer Mode 1 The second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ``printer'' ports. This allows byte-wide transfers, and avoids reconstructing nibbles into bytes. This cable should not be used on unidirectional ``printer'' (as opposed to ``parallel'') ports or when the machine isn't configured for PLIP, as it will result in output driver conflicts and the (unlikely) possibility of damage. The cable for this transfer mode should be constructed as follows: STROBE->BUSY 1 - 11 D0->D0 2 - 2 D1->D1 3 - 3 D2->D2 4 - 4 D3->D3 5 - 5 D4->D4 6 - 6 D5->D5 7 - 7 D6->D6 8 - 8 D7->D7 9 - 9 INIT -> ACK 16 - 10 AUTOFD->PAPOUT 14 - 12 SLCT->SLCTIN 13 - 17 GND->ERROR 18 - 15 extra grounds are 19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end Once again, if the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only. HTH, chl -- Dipl. Phys. Carsten Lechte Institut fuer Experimentelle und Angewandte Physik Christian-Albrechts-Universitaet, 24098 Kiel, Germany http://www.ieap.uni-kiel.de/plasma/ag-stroth
Re: A Null Printer Cable for PLIP
On Thu, Jan 16, 2003 at 03:21:43PM +0200, Andriy T. Yanko wrote: > How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? As descibed in linux/Documentation/networking/PLIP.txt. Try the first one first (the one that doesn't connect all D0-D7 to D0-D7 on the other side). If that doesn't work, you *know* your software configuration is wrong (in which case you'll probably want to look at the irq of the parallel port driver) OR that you need to hire someone to solder for you. I have never tried the second type of cable, so won't comment on it. HTH /Y
Re: got stuck in dpkg-available-cache
On Wed, 15 Jan 2003, Blars Blarson wrote: > In article <[EMAIL PROTECTED]> > [EMAIL PROTECTED] writes: > >Try using 'apt-get update' along with the equivalent in dselect See below. > 'dselect update' is a superset of 'apt-get update', there's no need to > do the 'apt-get update'. (or use update from the dselect menu) I do know this. And of couse I always did an "apt-get update" AND "dselect update" before I tried "apt-get upgrade" oder "dselect select ... install". Although dselect uses apt, it seems to have it's own information cache, which is not updated by performing apt-get update. But anyway, I still have no clue how to clean up the mess that I caused in both systems. Bjoern
unsubscribe
Read this mail to the end... Extreamly Important
READ THIS E-MAIL TO THE END ! -TRUE STORY AS SEEN ON ABC 20-20b.htm Description: Binary data
Re: got stuck in dpkg-available-cache
Hello Bjoern. I didn't follow the thread, but maybe could add some general hints ? > Although dselect uses apt, it seems to have it's own information cache, > which is not updated by performing apt-get update. > But anyway, I still have no clue how to clean up the mess that I caused in > both systems. > Bjoern Perhaps you can begin cleaning up from dselect with 'apt-method' of update, which is running an implied apt-get clean. Have a look at man apt-get --> options "dselect-upgrade" and "apt-get clean" and also option "--list-cleanup". Also, in the aptitude-manpage, there's an interesting §: -- v Aptitude::Track-Dselect-State If this is set, Aptitude will watch the dselect state of a package and alter its own internal state whenever this changes. You almost certainly want this to be on -- in fact, I'm not entirely certain that turning it off will work >=) (if you care, please test Aptitude with this option off and let me know what breaks so I can fix it) This was added to fix the "Aptitude and dselect fight over package states" bug in 0.0.3 . default: true --^ good luck ! -- michl
Re: video on toshiba satellite 1800-100 Please Help !!
On Tue, 14 Jan 2003 13:13:01 +0100, Frederik Dannemare wrote > > try the driver from http://www.xfree86.org/~alanh/ > requires X4.2, though (look at www.apt-get.org for woody apt-get > lines) > > /frederik Hi, I upgraded to X4.2 and it's worse than before : all X is now _verry_verry_ slow :-( Does anybody have a laptop with a Trident Cyberblade Ai1 chip ? Or does anybody know where I should search ? Do you need some other informations ? Thank's for helping and giving some of your time. Thierry.
Re: video on toshiba satellite 1800-100 Please Help !!
On Thu, 2003-01-16 at 17:35, Thierry Benita wrote: > Hi, I upgraded to X4.2 and it's worse than before : all X is now _verry_verry_ > slow :-( > > Does anybody have a laptop with a Trident Cyberblade Ai1 chip ? Or does > anybody know where I should search ? I do. Cyberblade i7d (rev 92). I'm running XFree86 4.2, and it works great. I switched to 4.2, because 4.1 seems to have a couple of problems with xv: there is always a blue line some 32 pixels wide on the left side of windows using acceleration, which degenerate in all-blue windows, with no image, after a suspend cycle. Both are fixed in 4.2. Having said that, I don't understand what could be the problem with your machine. The only thing I can think of is a misconfiguration in XF86Config-4. In the "Module" section, this is what I load: Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"pex5" Load"record" Load"speedo" Load"type1" Load"vbe" Load"xie" EndSection And my "Device" section looks like this: Section "Device" Identifier "Trident Cyberblade" Driver "trident" Option "UseFBDev" "true" Option "SWCursor" EndSection I have not changed anything else (aside from configuring my keyboard and the very nice Synaptics touchpad driver). It just works. Oh, I do enable the kernel frame buffer at boot. Maybe that makes a difference? I do that with an append="video=trident:800x600,bpp=16,center,fp" in my lilo.conf. That gets me very nice high resolution text consoles. I have the Trident FB driver built into my kernel, it is not loaded as a module. I don't know if you can do this if the driver is a module. I hope this helps. -CR
A Null Printer Cable for PLIP
Hi How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? thx -- Andriy T. Yanko System Administrator MPP MEDIA ATY1-RIPE ATY1-UANIC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A Null Printer Cable for PLIP
Hi all, Andriy T.Yanko wrote: Hi How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? You can see it in net-howto, and in plip-install howto. Faster, here: http://www.tldp.org/HOWTO/PLIP-Install-HOWTO-8.html thx Nothing. Salud y Revolución. Lobo. -- Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux, para no atar mis manos con las cadenas del soft propietario. - Desde El Ejido, en Almeria, usuario registrado linux #294013 http://www.counter.li.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A Null Printer Cable for PLIP
Hello What kinds of problems do you have exactly? > How to make ___WORKING___ Null Printer Cable for use with a PLIP > connection? On my woody installation, I found two howtos and one kernel documentation. /usr/share/doc/HOWTO/en-txt/mini/PLIP.gz /usr/share/doc/HOWTO/en-txt/PLIP-Install-HOWTO.gz /usr/src/kernel-source-2.4.17/Documentation/networking/PLIP.txt Quoting PLIP.txt: Parallel Transfer Mode 0 Cable == The cable for the first transfer mode is a standard printer "null" cable which transfers data four bits at a time using data bit outputs of the first port (machine T) connected to the status bit inputs of the second port (machine R). There are five status inputs, and they are used as four data inputs and a clock (data strobe) input, arranged so that the data input bits appear as contiguous bits with standard status register implementation. A cable that implements this protocol is available commercially as a "Null Printer" or "Turbo Laplink" cable. It can be constructed with two DB-25 male connectors symmetrically connected as follows: STROBE output 1* D0->ERROR 2 - 15 15 - 2 D1->SLCT3 - 13 13 - 3 D2->PAPOUT 4 - 12 12 - 4 D3->ACK 5 - 10 10 - 5 D4->BUSY6 - 11 11 - 6 D5,D6,D7 are 7*, 8*, 9* AUTOFD output 14* INIT output 16* SLCTIN 17 - 17 extra grounds are 18*,19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end If the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only. Parallel Transfer Mode 1 The second data transfer method relies on both machines having bi-directional parallel ports, rather than output-only ``printer'' ports. This allows byte-wide transfers, and avoids reconstructing nibbles into bytes. This cable should not be used on unidirectional ``printer'' (as opposed to ``parallel'') ports or when the machine isn't configured for PLIP, as it will result in output driver conflicts and the (unlikely) possibility of damage. The cable for this transfer mode should be constructed as follows: STROBE->BUSY 1 - 11 D0->D0 2 - 2 D1->D1 3 - 3 D2->D2 4 - 4 D3->D3 5 - 5 D4->D4 6 - 6 D5->D5 7 - 7 D6->D6 8 - 8 D7->D7 9 - 9 INIT -> ACK 16 - 10 AUTOFD->PAPOUT 14 - 12 SLCT->SLCTIN 13 - 17 GND->ERROR 18 - 15 extra grounds are 19*,20*,21*,22*,23*,24* GROUND 25 - 25 * Do not connect these pins on either end Once again, if the cable you are using has a metallic shield it should be connected to the metallic DB-25 shell at one end only. HTH, chl -- Dipl. Phys. Carsten Lechte Institut fuer Experimentelle und Angewandte Physik Christian-Albrechts-Universitaet, 24098 Kiel, Germany http://www.ieap.uni-kiel.de/plasma/ag-stroth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A Null Printer Cable for PLIP
On Thu, Jan 16, 2003 at 03:21:43PM +0200, Andriy T. Yanko wrote: > How to make ___WORKING___ Null Printer Cable for use with a PLIP connection? As descibed in linux/Documentation/networking/PLIP.txt. Try the first one first (the one that doesn't connect all D0-D7 to D0-D7 on the other side). If that doesn't work, you *know* your software configuration is wrong (in which case you'll probably want to look at the irq of the parallel port driver) OR that you need to hire someone to solder for you. I have never tried the second type of cable, so won't comment on it. HTH /Y -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: got stuck in dpkg-available-cache
On Wed, 15 Jan 2003, Blars Blarson wrote: > In article <[EMAIL PROTECTED]> > [EMAIL PROTECTED] writes: > >Try using 'apt-get update' along with the equivalent in dselect See below. > 'dselect update' is a superset of 'apt-get update', there's no need to > do the 'apt-get update'. (or use update from the dselect menu) I do know this. And of couse I always did an "apt-get update" AND "dselect update" before I tried "apt-get upgrade" oder "dselect select ... install". Although dselect uses apt, it seems to have it's own information cache, which is not updated by performing apt-get update. But anyway, I still have no clue how to clean up the mess that I caused in both systems. Bjoern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unsubscribe
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Read this mail to the end... Extreamly Important
READ THIS E-MAIL TO THE END ! -TRUE STORY AS SEEN ON ABC 20-20b.htm Description: Binary data
Re: got stuck in dpkg-available-cache
Hello Bjoern. I didn't follow the thread, but maybe could add some general hints ? > Although dselect uses apt, it seems to have it's own information cache, > which is not updated by performing apt-get update. > But anyway, I still have no clue how to clean up the mess that I caused in > both systems. > Bjoern Perhaps you can begin cleaning up from dselect with 'apt-method' of update, which is running an implied apt-get clean. Have a look at man apt-get --> options "dselect-upgrade" and "apt-get clean" and also option "--list-cleanup". Also, in the aptitude-manpage, there's an interesting §: -- v Aptitude::Track-Dselect-State If this is set, Aptitude will watch the dselect state of a package and alter its own internal state whenever this changes. You almost certainly want this to be on -- in fact, I'm not entirely certain that turning it off will work >=) (if you care, please test Aptitude with this option off and let me know what breaks so I can fix it) This was added to fix the "Aptitude and dselect fight over package states" bug in 0.0.3 . default: true --^ good luck ! -- michl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: video on toshiba satellite 1800-100 Please Help !!
On Tue, 14 Jan 2003 13:13:01 +0100, Frederik Dannemare wrote > > try the driver from http://www.xfree86.org/~alanh/ > requires X4.2, though (look at www.apt-get.org for woody apt-get > lines) > > /frederik Hi, I upgraded to X4.2 and it's worse than before : all X is now _verry_verry_ slow :-( Does anybody have a laptop with a Trident Cyberblade Ai1 chip ? Or does anybody know where I should search ? Do you need some other informations ? Thank's for helping and giving some of your time. Thierry. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: video on toshiba satellite 1800-100 Please Help !!
On Thu, 2003-01-16 at 17:35, Thierry Benita wrote: > Hi, I upgraded to X4.2 and it's worse than before : all X is now _verry_verry_ > slow :-( > > Does anybody have a laptop with a Trident Cyberblade Ai1 chip ? Or does > anybody know where I should search ? I do. Cyberblade i7d (rev 92). I'm running XFree86 4.2, and it works great. I switched to 4.2, because 4.1 seems to have a couple of problems with xv: there is always a blue line some 32 pixels wide on the left side of windows using acceleration, which degenerate in all-blue windows, with no image, after a suspend cycle. Both are fixed in 4.2. Having said that, I don't understand what could be the problem with your machine. The only thing I can think of is a misconfiguration in XF86Config-4. In the "Module" section, this is what I load: Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"pex5" Load"record" Load"speedo" Load"type1" Load"vbe" Load"xie" EndSection And my "Device" section looks like this: Section "Device" Identifier "Trident Cyberblade" Driver "trident" Option "UseFBDev" "true" Option "SWCursor" EndSection I have not changed anything else (aside from configuring my keyboard and the very nice Synaptics touchpad driver). It just works. Oh, I do enable the kernel frame buffer at boot. Maybe that makes a difference? I do that with an append="video=trident:800x600,bpp=16,center,fp" in my lilo.conf. That gets me very nice high resolution text consoles. I have the Trident FB driver built into my kernel, it is not loaded as a module. I don't know if you can do this if the driver is a module. I hope this helps. -CR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
