Seems it is not a driver issue. My localy conected printer works good.
So, if it is a driver issue, than it is Bering driver issue.
> This sounds more like a driver issue. Did You try to connect printer
> directly? If yes - what were the results?
>
> S�awek Adamski wrote:
>> Yes, it wasn't precise. Sorry. I was using Leaf Bering 1.0 without
>> printer. From 2003 I was using Leaf Bering 1.2 with printer. The
>> printing works nearly good. Nearly means that the printer always was
>> waiting (about 100 seconds) before it prints the last page of last
>> printing job.
>> I was searching how to resolve this troublesome symptom. And I found
>> nothing. Nothing beside an advice to use samba.
>> Lately I configured my first Bering-uClibc 3.1 floppy without samba
>> (and without hdsupp, netstatn, sftp, snort too - they are still not
>> configured). It was working as previous, Leaf Bering 1.2. Means I'm
>> waiting for the last page of last job.
>> OK, I said - is time for samba :-). On my floppy was no place for
>> samba. I prepared CD adding new packages. Now I'm trying to configure
>> first of them - samba.
>> If anybody needs more info please keep in mind that I know nothing
>> about linux. And I know only little more about net :-).
>>
>> --
>> S�awek
>>
>> C.Dummy pisze:
>>> What are You trying to achieve? What is the problem? Did You try to
>>> use p9100 package without getting into samba?
>>> Andrey
>>> S�awek Adamski wrote:
>>>> Hello
>>>>
>>>> I,m using Bering Leaf from 2000. First Bering Leaf 1.0, from 2003
>>>> Bering Leaf 2003 and now Bering-uClibc 3.1
>>>>
>>>> My Info:
>>>>
>>>> ------- start of info -----------
>>>> firewall# uname -a
>>>> Linux firewall 2.4.34 #1 Tue Jan 23 20:12:21 CET 2007 i686 unknown
>>>> firewall# ip addr show
>>>> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>>> inet 127.0.0.1/8 scope host lo
>>>> 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
>>>> link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>>>> 3: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc
>>>> pfifo_fast qlen 1000
>>>> link/ether 00:0a:cd:00:91:71 brd ff:ff:ff:ff:ff:ff
>>>> inet 212.76.51.79/22 brd 212.76.51.255 scope global eth0
>>>> 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>>>> link/ether 00:0a:cd:00:99:f9 brd ff:ff:ff:ff:ff:ff
>>>> inet 192.168.0.1/24 brd 192.168.0.255 scope global eth1
>>>> firewall# ip route show
>>>> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.1
>>>> 212.76.48.0/22 dev eth0 proto kernel scope link src 212.76.51.79
>>>> default via 212.76.51.254 dev eth0
>>>> firewall# lsmod
>>>> Module Size Used by Not tainted
>>>> lp 4880 1
>>>> parport_pc 14228 1
>>>> parport 10880 1 [lp parport_pc]
>>>> softdog 1392 1
>>>> ipt_ipp2p 5908 0
>>>> ipt_state 272 18
>>>> ipt_helper 400 0 (unused)
>>>> ipt_conntrack 692 0
>>>> ipt_REDIRECT 480 0 (unused)
>>>> ipt_MASQUERADE 1024 1
>>>> ip_nat_irc 1704 0 (unused)
>>>> ip_nat_ftp 2152 0 (unused)
>>>> iptable_nat 14388 3 [ipt_REDIRECT ipt_MASQUERADE
>>>> ip_nat_irc ip_nat_ftp]
>>>> ip_conntrack_irc 2484 1
>>>> ip_conntrack_ftp 3132 1
>>>> ip_conntrack 16548 2 [ipt_state ipt_helper ipt_conntrack
>>>> ipt_REDIRECT ipt_MASQUERADE ip_nat_irc ip_nat_ftp iptable_nat
>>>> ip_conntrack_irc ip_conntrack_ftp]
>>>> 8139too 11944 2
>>>> mii 1820 0 [8139too]
>>>> crc32 2620 0 [8139too]
>>>> vfat 8492 0 (unused)
>>>> isofs 15732 0
>>>> ide-detect 132 0 (unused)
>>>> ide-cd 26748 0
>>>> ide-disk 11372 0
>>>> ide-core 88280 0 [ide-detect ide-cd ide-disk]
>>>> cdrom 25568 0 [ide-cd]
>>>> firewall# /sbin/shorewall status
>>>> Shorewall-3.4.7 Status at firewall - Tue Feb 24 20:45:10 UTC 2009
>>>>
>>>> Shorewall is running
>>>> State:Started (Tue Feb 24 19:18:40 UTC 2009)
>>>>
>>>> firewall# iptables -t nat -nvL
>>>> Chain PREROUTING (policy ACCEPT 1657 packets, 113K bytes)
>>>> pkts bytes target prot opt in out source destination
>>>> 193 27099 net_dnat all -- eth0 * 0.0.0.0/0 0.0.0.0/0
>>>>
>>>> Chain POSTROUTING (policy ACCEPT 133 packets, 9702 bytes)
>>>> pkts bytes target prot opt in out source destination
>>>> 1246 63116 eth0_masq all -- * eth0 0.0.0.0/0 0.0.0.0/0
>>>>
>>>> Chain OUTPUT (policy ACCEPT 219 packets, 20625 bytes)
>>>> pkts bytes target prot opt in out source destination
>>>>
>>>> Chain eth0_masq (1 references)
>>>> pkts bytes target prot opt in out source destination
>>>> 1114 53472 MASQUERADE all -- * * 192.168.0.0/24
>>>> 0.0.0.0/0
>>>>
>>>> Chain net_dnat (1 references)
>>>> pkts bytes target prot opt in out source destination
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28111 to:192.168.0.11
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28111 to:192.168.0.11
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28112 to:192.168.0.12
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28112 to:192.168.0.12
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28113 to:192.168.0.13
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28113 to:192.168.0.13
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28114 to:192.168.0.14
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28114 to:192.168.0.14
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28115 to:192.168.0.15
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28115 to:192.168.0.15
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28116 to:192.168.0.16
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28116 to:192.168.0.16
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28117 to:192.168.0.17
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28117 to:192.168.0.17
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28118 to:192.168.0.18
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28118 to:192.168.0.18
>>>> 0 0 DNAT tcp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 tcp dpt:28119 to:192.168.0.19
>>>> 0 0 DNAT udp -- * * 0.0.0.0/0
>>>> 0.0.0.0/0 udp dpt:28119 to:192.168.0.19
>>>> ------- end of info -----------
>>>>
>>>> And my messages:
>>>>
>>>> ------- start of messages -----------
>>>> Feb 24 19:18:34 firewall syslogd 1.4.1: restart.
>>>> Feb 24 19:18:34 firewall kernel: klogd 1.4.1, log source =
>>>> /proc/kmsg started.
>>>> Feb 24 19:18:34 firewall kernel: BIOS-provided physical RAM map:
>>>> Feb 24 19:18:34 firewall kernel: 64MB LOWMEM available.
>>>> Feb 24 19:18:34 firewall kernel: Initializing CPU#0
>>>> Feb 24 19:18:34 firewall kernel: Memory: 62544k/65536k available
>>>> (864k kernel code, 2604k reserved, 97k data, 60k init, 0k highmem)
>>>> Feb 24 19:18:34 firewall kernel: Dentry cache hash table entries:
>>>> 8192 (order: 4, 65536 bytes)
>>>> Feb 24 19:18:34 firewall kernel: Inode cache hash table entries:
>>>> 4096 (order: 3, 32768 bytes)
>>>> Feb 24 19:18:34 firewall kernel: Mount cache hash table entries: 512
>>>> (order: 0, 4096 bytes)
>>>> Feb 24 19:18:34 firewall kernel: Buffer cache hash table entries:
>>>> 4096 (order: 2, 16384 bytes)
>>>> Feb 24 19:18:34 firewall kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
>>>> Feb 24 19:18:34 firewall kernel: CPU: L2 cache: 512K
>>>> Feb 24 19:18:34 firewall kernel: Checking 'hlt' instruction... OK.
>>>> Feb 24 19:18:34 firewall kernel: PCI: PCI BIOS revision 2.10 entry
>>>> at 0xfd943, last bus=1
>>>> Feb 24 19:18:34 firewall kernel: PCI: Using configuration type 1
>>>> Feb 24 19:18:34 firewall kernel: PCI: Probing PCI hardware
>>>> Feb 24 19:18:34 firewall kernel: PCI: Using IRQ router PIIX/ICH
>>>> [8086/7110] at 00:07.0
>>>> Feb 24 19:18:34 firewall kernel: Limiting direct PCI/PCI transfers.
>>>> Feb 24 19:18:34 firewall kernel: Linux NET4.0 for Linux 2.4
>>>> Feb 24 19:18:34 firewall kernel: Based upon Swansea University
>>>> Computer Society NET3.039
>>>> Feb 24 19:18:34 firewall kernel: Serial driver version 5.05c
>>>> (2001-07-08) with MANY_PORTS SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled
>>>> Feb 24 19:18:34 firewall kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
>>>> Feb 24 19:18:34 firewall kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
>>>> Feb 24 19:18:34 firewall kernel: Real Time Clock Driver v1.10f
>>>> Feb 24 19:18:34 firewall kernel: Floppy drive(s): fd0 is 1.44M
>>>> Feb 24 19:18:34 firewall kernel: FDC 0 is a National Semiconductor
>>>> PC87306
>>>> Feb 24 19:18:34 firewall kernel: Initializing Cryptographic API
>>>> Feb 24 19:18:34 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0
>>>> Feb 24 19:18:34 firewall kernel: IP Protocols: ICMP, UDP, TCP, IGMP
>>>> Feb 24 19:18:34 firewall kernel: IP: routing cache hash table of 512
>>>> buckets, 4Kbytes
>>>> Feb 24 19:18:34 firewall kernel: TCP: Hash tables configured
>>>> (established 4096 bind 8192)
>>>> Feb 24 19:18:34 firewall kernel: NET4: Unix domain sockets 1.0/SMP
>>>> for Linux NET4.0.
>>>> Feb 24 19:18:34 firewall kernel: RAMDISK: Compressed image found at
>>>> block 0
>>>> Feb 24 19:18:34 firewall kernel: Freeing initrd memory: 395k freed
>>>> Feb 24 19:18:34 firewall kernel: Freeing unused kernel memory: 60k
>>>> freed
>>>> Feb 24 19:18:34 firewall kernel: Uniform Multi-Platform E-IDE driver
>>>> Revision: 7.00beta4-2.4
>>>> Feb 24 19:18:34 firewall kernel: ide: Assuming 33MHz system bus
>>>> speed for PIO modes; override with idebus=xx
>>>> Feb 24 19:18:34 firewall kernel: hda: ATAPI 32X CD-ROM drive, 256kB
>>>> Cache
>>>> Feb 24 19:18:34 firewall kernel: Uniform CD-ROM driver Revision: 3.12
>>>> Feb 24 19:18:34 firewall kernel: 8139too Fast Ethernet driver 0.9.26
>>>> Feb 24 19:18:34 firewall kernel: PCI: Found IRQ 11 for device 00:0e.0
>>>> Feb 24 19:18:34 firewall kernel: eth0: RealTek RTL8139 at
>>>> 0xc4846c00, 00:0a:cd:00:91:71, IRQ 11
>>>> Feb 24 19:18:34 firewall kernel: PCI: Found IRQ 9 for device 00:10.0
>>>> Feb 24 19:18:34 firewall kernel: PCI: Sharing IRQ 9 with 00:07.2
>>>> Feb 24 19:18:34 firewall kernel: eth1: RealTek RTL8139 at
>>>> 0xc4848800, 00:0a:cd:00:99:f9, IRQ 9
>>>> Feb 24 19:18:34 firewall kernel: IPP2P v0.8.2 loading
>>>> Feb 24 19:18:34 firewall kernel: Software Watchdog Timer: 0.05,
>>>> timer margin: 60 sec
>>>> Feb 24 19:18:34 firewall kernel: parport0: PC-style at 0x378
>>>> [PCSPP(,...)]
>>>> Feb 24 19:18:34 firewall kernel: lp0: using parport0 (polling).
>>>> Feb 24 19:18:34 firewall kernel: eth0: link up, 100Mbps,
>>>> full-duplex, lpa 0x41E1
>>>> Feb 24 19:18:34 firewall dhcpcd.exe: interface eth0 has been
>>>> configured with new IP=212.76.51.79
>>>> Feb 24 19:18:34 firewall kernel: eth1: link up, 100Mbps,
>>>> full-duplex, lpa 0x45E1
>>>> Feb 24 19:18:40 firewall root: Shorewall started
>>>> ------- end of messages -----------
>>>>
>>>> I'm using boot CD maked with isolinux. Works. Nearly. Samba printer
>>>> doesn't work. My windows machine doesn't see the net path to
>>>> printer. Seems the HOW-TO is old.
>>>>
>>>> My isolinux.cfg:
>>>>
>>>> ------- start of file -----------
>>>> display syslinux.dpy
>>>> timeout 0
>>>> append reboot=bios
>>>> default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
>>>> LEAFCFG=/dev/cdrom:iso9660 PKGPATH=/dev/fd0:msdos,/dev/cdrom:iso9660
>>>> syst_size=22M tmp_size=226M log_size=4M
>>>> ------- end of file -----------
>>>>
>>>> My leaf.cfg:
>>>>
>>>> ------- start of file -----------
>>>> # This file is parsed as a shell script
>>>> # Kernel command line parameters are available as KCMD_<variable>
>>>> # ie: KCMD_LRP contains the LRP= portion of the kernel command line
>>>> # NOTE: For kernel command line settings that do not include an equals
>>>> # sign (ie: rw or similar), the variable is set to itself, allowing
>>>> # for easy testing (ie: KCMD_rw=rw).
>>>>
>>>> # LRP and PKGPATH variables now support whitespace (space, tab,
>>>> newline)
>>>> # as well as commas for seperators.
>>>>
>>>> # Uncomment for more verbose execution.
>>>> #VERBOSE=1
>>>>
>>>> # Other variables you might want to set in this file include:
>>>> # LRP Packages to load
>>>> # PKGPATH Device(s) to load packages from
>>>> # CONFIGDB Configuration database
>>>> # MODDB Modules database
>>>> # syst_size Size of root ramdisk
>>>> # tmp_size Size of /tmp ramdisk
>>>> # log_size Size of /var/log ramdisk
>>>>
>>>> # Example:
>>>> #LRP="$KCMD_LRP rsync"
>>>> LRP="root config etc modules iptables dhcpcd shorwall ulogd dnsmasq
>>>> dropbear mhttpd openntpd webconf p9100 hdsupp netstatn samba sftp
>>>> snort"
>>>>
>>>> # The first entry is the backup device.
>>>> # If equal packages exist on multiple devices, the ones on the left
>>>> most device have precedence.
>>>> # PKGPATH="/dev/fd0u1680:msdos"
>>>>
>>>> # Experts only: the name of the config and modules databases can be
>>>> changed, choose an unique name.
>>>> #CONFIFGDB=configdb
>>>> #MODDB=moddb
>>>> #syst_size=6M
>>>> #log_size=2M
>>>> syst_size=22M
>>>> tmp_size=226M
>>>> log_size=4M
>>>> ------- end of file -----------
>>>>
>>>> Samba configuration file:
>>>>
>>>> ------- start of file -----------
>>>> # Global parameters
>>>> [global]
>>>> workgroup = DOMEK
>>>> netbios name = spfw
>>>> guest account = pcguest
>>>> encrypt passwords = yes
>>>> wins support = yes
>>>> name resolve order = wins lmhosts hosts bcast
>>>> log file = /var/log
>>>>
>>>> [homes]
>>>> comment = All printers
>>>> path = /tmp/storage/tmp
>>>> create mask = 0700
>>>> print ok = Yes
>>>> read only = No
>>>> browseable = No
>>>>
>>>> [hp5550samba]
>>>> path = /tmp/storage/tmp/samba
>>>> read only = No
>>>> # quest ok = Yes
>>>> min print space = 128
>>>> print ok = Yes
>>>> printer name = lp
>>>> oplocks = No
>>>> share modes = No
>>>> ------- end of file -----------
>>>>
>>>> and finally inittab:
>>>>
>>>> ------- start of file -----------
>>>> # /etc/inittab: configuration.
>>>>
>>>> # Boot-time system configuration/initialization script.
>>>> ::sysinit:/etc/init.d/rcS
>>>> ::sysinit:mkdir /tmp/storage
>>>> ::sysinit:mkdir /tmp/storage/spool
>>>> ::sysinit:mkdir /tmp/storage/spool/lpd
>>>> ::sysinit:mkdir /tmp/storage/tmp
>>>> ::sysinit:mkdir /tmp/storage/tmp/samba
>>>> ::sysinit:chown nobody /tmp/storage/tmp/samba
>>>> ::wait:/etc/init.d/rc 2
>>>> ::wait:echo "lp:lp=/dev/lp0:sd=/tmp/storage/spool/lpd:mx#0:sh" >
>>>> /etc/printcap
>>>>
>>>> # /sbin/getty invocations for selected ttys
>>>> #
>>>> # Format:
>>>> # <id>::<action>:<process>
>>>> tty1::respawn:/sbin/getty 38400 tty1
>>>> tty2::respawn:/sbin/getty 38400 tty2
>>>>
>>>> # Example how to put a getty on a serial line (for a terminal)
>>>> #
>>>> #ttyS0::respawn:/sbin/getty -L ttyS0 19200 vt100
>>>> #ttyS1::respawn:/sbin/getty -L ttyS1 19200 vt100
>>>>
>>>> # Example how to put a getty on a modem line.
>>>> #
>>>> #ttyS3::respawn:/sbin/mgetty -x0 -s 57600 ttyS3
>>>>
>>>> # Stuff to do when restarting the init process
>>>> ::restart:/sbin/init
>>>>
>>>> # Stuff to do before rebooting
>>>> ::ctrlaltdel:/sbin/reboot
>>>> ::shutdown:/etc/init.d/rc 0
>>>> ------- end of file -----------
>>>>
>>>> In the HOW-TO is written, that I ought to use smb.lrp and lpd.lrp.
>>>> But in version 3.1 i don't see them. I use samba.lrp in that place.
>>>> And I didn't modify /var/lib/lrpkg/root.dev.mk and
>>>> /var/lib/lrpkg/root.dev.mod. p910nd works with out that.
>>>>
>>>> I want to change p910nd with samba printer. Maybe I must prepare
>>>> /var/lib/lrpkg/root.dev.mk and /var/lib/lrpkg/root.dev.mod, burn
>>>> them and copy them to /var/lib/lrpkg in inittab after mounting CD?
>>>> Maybe I must delete p910nd from packages list? Maybe I must do
>>>> somethig else. But what?
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>>>> Francisco, CA
>>>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>>>> Enterprise
>>>> -Strategies to boost innovation and cut costs with open source
>>>> participation
>>>> -Receive a $600 discount off the registration fee with the source
>>>> code: SFAD
>>>>
http://p.sf.net/sfu/XcvMzF8H>>>> ------------------------------------------------------------------------
>>>>
>>>> leaf-user mailing list:
leaf-user@...
>>>>
https://lists.sourceforge.net/lists/listinfo/leaf-user>>>> Support Request --
http://leaf-project.org/>>>>
>>>>
>>>
>>>
>>> __________ NOD32 Informacje 3889 (20090225) __________
>>>
>>> Wiadomosc zostala sprawdzona przez System Antywirusowy NOD32
>>>
http://www.nod32.com lub
http://www.nod32.pl>>>
>>>
>>
>>
>>
>
>
> __________ NOD32 Informacje 3893 (20090226) __________
>
> Wiadomosc zostala sprawdzona przez System Antywirusowy NOD32
>
http://www.nod32.com lub
http://www.nod32.pl>
>