Initial Boot over USB?


80 posts   Page 3 of 4   1, 2, 3, 4
by sdjf » Sun Dec 16, 2012 2:18 pm
Finally have diagnostics by logging in with keyboard without monitor, running a script located in /boot that writes output of dmesg, everything.log and lsmod to files in /boot.

Note that at the moment these diagnostics were created, I have my older Zaurus plugged in to the Pi, the sl5500 "Collie".

http://sdjf.esmartdesign.com/raspberryp ... Dec5am.txt
http://sdjf.esmartdesign.com/raspberryp ... Dec5am.txt
http://sdjf.esmartdesign.com/raspberryp ... Dec5am.txt

Zaurus is clearly recognized and zaurus module has been loaded.

What else needs to be seen or done now?
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Sun Dec 16, 2012 2:22 pm
ifconfig -a > /boot/net.txt
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Sun Dec 16, 2012 3:11 pm
pepedog wrote:ifconfig -a > /boot/net.txt

Code: Select all
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:f0:f7:64  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ifb0: flags=130<BROADCAST,NOARP>  mtu 1500
        ether 5e:6c:13:ae:fe:c6  txqueuelen 32  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ifb1: flags=130<BROADCAST,NOARP>  mtu 1500
        ether 86:7c:ef:88:91:ca  txqueuelen 32
 (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 36  bytes 2572 (2.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 2572 (2.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
usb0: flags=4098<BROADCAST,MULTICAST>  mtu 1494        ether 8a:a4:c1:8f:7a:ca  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by sdjf » Mon Dec 17, 2012 1:34 am
I did it, I just got to ssh in to my Pi from my Zaurus Collie SL5500! Now my challenge is figuring out why I can do it from one Zaurus but not the other, but I succeeded with one of them! The SL6000 is more important as it has a good keyboard, so do need to get it debugged.

Interface is using usb0 on the Pi end and usbd0 on the PDA side. No need to get involved with GPIO serial access! USB is working just fine! Thank you all for your help.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by ghans » Mon Dec 17, 2012 7:23 am
Congratulations !
What is your cmdline.txt ? What changes did you do to the kernel ?


ghans
• Don't like the board ? Missing features ? Change to the prosilver theme ! You can find it in your settings.
• Don't like to search the forum BEFORE posting 'cos it's useless ? Try googling : yoursearchtermshere site:raspberrypi.org
Posts: 4769
Joined: Mon Dec 12, 2011 8:30 pm
Location: Germany
by micerinos » Mon Dec 17, 2012 10:24 am
Hey, nice to hear that!
Reading the posts, seems like I'm missing something. How did you managed to do it? Is it a custom image with symbolic links to conf files? An ext3 partition for rootfs? The script you run on boot, is also part of a customization of the image?

Cheers
Posts: 74
Joined: Fri Nov 09, 2012 11:15 am
Location: Madrid, Spain
by sdjf » Mon Dec 17, 2012 1:45 pm
No custom image or kernel modifications required, the only reason I might have needed that would have been if the zaurus.ko module was not built in. But zaurus module is already built in to the standard kernel now. I did this with the basic vanilla 18 Sep hard float Arch image, just working with files in the boot partition.

My cmdline.txt is:

sdhci-bcm2708.enable_llm=1 sdhci-bcm2708.sync_after_dma=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 console=ttyAMA0,38400 kgdboc=ttyAMA0,38400 console=tty1 loglevel=6 root=/dev/mmcblk0p2 init=/bin/systemd rootfstype=ext4 rootwait ip=192.168.129.3:192.168.129.2:127.0.0.1:255.255.255.0:rpi:usb0:off

My Raspberry Pi is assigned IP 192.168.129.3
The PDA is at the IP 192.168.129.2

Besides editing /boot/cmdline.txt, the other special things I needed to do were:

1. create a bash script with my PDA to place in /boot on the Pi's SD card, as well as edit there using the PDA, if I want to add or modify any commands in the script. I called the script testing.sh, as it has a bunch of debugging queries in it. Output of all commands in the script are specifically routed to files in /boot. Make sure the script includes a line as follows:

ifconfig usb0 192.168.129.3 netmask 255.255.255.0 up

2. Make sure that the zaurus module has been loaded on the Pi, I do not recall if it loaded automatically or if I had to do an insmod or modprobe to get it to appear in lsmod. Note I cannot really check this unless I run step 3 first, but step 3 and the ones after will not result in a successful interface unless that module is loaded. So it takes a few trials to examine output of lsmod if things are not working.

3. Plug in my USB keyboard to the Pi and turn on the Pi. No monitor, just watching the flashing of the ACT light to gauge what is going on. Enter the following, with delays as needed between entries.
I had to keep things simple by putting all essential commands in the script as otherwise I cannot be sure all other critical commands are entered properly.
root
root
sync
/boot/testing.sh

3. Set up the interface on the Zaurus. The sl5500 does not need sudo, when run these commands on the sl6000, they need to be prefaced by sudo and use the different IP that is the one for the sl6000, in the ifconfig command.

ifconfig usbd0 192.168.129.2 netmask 255.255.255.0 up
route add default gw 192.168.129.3

4. On the Zaurus, ping the Pi with "ping 192.168.129.3" to confirm connection.

5. login via ssh (which I had already installed on the zaurus)

ssh 192.168.129.3 -2

Note that the "-2" is needed as my Zaurus uses Version 1 of ssh by default, and the Pi insisted on version 2.

I think those are the critical steps. I still am having trouble getting the zaurus sl6000 ifconfig command to work. I think it has something to do with the built in samba that may be interfering. I do not use samba, but it is there by default in the SL6000.

And the SL5500 Collie has totally crashed a couple of times when I tried to insert media into the Pi when I was logged in via ssh, so still trying to get the hang of how to work with the setup, but the hardest part is over, getting in the first time via ssh over plain USB.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by sdjf » Tue Dec 18, 2012 4:20 pm
Examining dmesg, I believe that the Zaurus module is not binding to my sl6000. On my PDA, I can make sure devices are bound to appropriate drivers with /etc/hotplug/usb.distmap, but find no such file on the Pi. How do I get the sl6000 to get bound to the zaurus module?

The entries from dmesg for the sl6000 that is not able to establish network connection with Pi are:

[ 2.546002] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[ 2.649998] usb 1-1.3: New USB device found, idVendor=04dd, idProduct=8004
[ 2.650026] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.650045] usb 1-1.3: Product: SL Series
[ 2.650060] usb 1-1.3: Manufacturer: Sharp

The entry for the sl5500 which is recognized by Pi and bound to the zaurus module and has been able to sometimes ping and ssh in to the Pi is very short, shows driver registered:

[ 18.063755] zaurus 1-1.3:1.0: usb0: register 'zaurus' at usb-bcm2708_usb-1.3, Sharp Zaurus
SL-5x00, e6:c3:44:70:57:f4
[ 18.063970] usbcore: registered new interface driver zaurus

All the above was taken from the following full dmesg output if you want to see in context:

http://sdjf.esmartdesign.com/raspberryp ... Dec5am.txt

Is it a bug in the Zaurus module or is there something I can add to a configuration file somewhere?
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by sdjf » Tue Dec 18, 2012 6:28 pm
I think I have the answer. The following seems to bind the SL6000 to a serial driver.

/usr/lib/modules/3.2.27-5-ARCH+/modules.alias

alias usb:v04DDp8004d*dc02dsc*dp*icFFisc02ip* safe_serial

and that would explain the problem - it should look like what the lines that bind to zaurus module look like:

alias usb:v04DDp8004d*dc02dsc*dp*icFFisc02ip* zaurus

No idea why they figured the SL6000 would use a serial interface and the other Zauruses would act like Zauruses. But this should make a difference.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Tue Dec 18, 2012 7:57 pm
We get it from upstream, same place as raspbian, so you have to report here
https://github.com/raspberrypi/linux/issues
If they won't patch it's still possible we could
Or you might get it in the pistore (joke)
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Tue Dec 18, 2012 8:40 pm
Examining that file more closely, it looks like this is more than a simple change in the entry(ies) in modules.aliases. There are quite a few Sharp devices that have multiple entries in that file, to allow different kinds of interfaces. So it is more a problem with the mechanism by which the driver/module is chosen.

Some devices are limited to one module or interface type, but others including my 04DD 8004 have 2 or 3 entries.

# grep v04DD /usr/lib/modules/3.2.27-5-ARCH+/modules.alias | grep -Ev ipaq|sort|wc -l
18
# grep v04DD /usr/lib/modules/3.2.27-5-ARCH+/modules.alias | grep -Ev ipaq|sort|head
alias usb:v04DDp8001d*dc02dsc*dp*icFFisc02ip* safe_serial
alias usb:v04DDp8002d*dc02dsc*dp*icFFisc02ip* safe_serial
alias usb:v04DDp8003d*dc02dsc*dp*icFFisc02ip* safe_serial
alias usb:v04DDp8004d*dc*dsc*dp*ic02isc06ip00*
cdc_ether
alias usb:v04DDp8004d*dc*dsc*dp*ic02isc06ip00*
zaurus
alias usb:v04DDp8004d*dc02dsc*dp*icFFisc02ip* safe_serial
alias usb:v04DDp8005d*dc*dsc*dp*ic02isc06ip00*
cdc_ether
alias usb:v04DDp8005d*dc*dsc*dp*ic02isc06ip00*
zaurus
alias usb:v04DDp8006d*dc*dsc*dp*ic02isc06ip00*
cdc_ether
alias usb:v04DDp8006d*dc*dsc*dp*ic02isc06ip00*
zaurus
#

Just posted the first few devices to give you the idea. How much information will they need at github?

It looks like what I will do is comment out the lines that make my SL6000 bind to modules other than zaurus as a temporary fix.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by sdjf » Thu Jan 17, 2013 5:49 pm
Even with newest test image, I continue to get "bad cdc descriptor" error when plug on sl6000 to the Pi. Reported issue at github and they say it needs reporting upstream, but where does that mean?

https://github.com/raspberrypi/linux/issues/180

I cannot remove the cdc_ether module as the zaurus module uses it. The reason I cannot get the sl6000 to use the zaurus module is that the sl6000 claims to be a CDC Ether device even though it is not, and the sl5500 does not do that.

Is there a way to blacklist the cdc-ether module, similar to the old hotplugging? I tried just blacklisting it in the following, but that had no effect:

echo "blacklist cdc_ether" >> /etc/modules-load.d/blacklist.conf

Oh, commenting out the lines binding the sl6000 to cdc-ether in the modules.alias file did not prevent the cdc-ether module from trying to bind to the sl6000, and preventing the zaurus module from binding to the device.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Thu Jan 17, 2013 7:24 pm
I don't know what to say. Is there an x86 forum discussing how it's done? I'm going for a look.
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Fri Jan 18, 2013 12:46 am
I am not sure about x86 forums, but I had found this thread that I think provides a patch, but I am not sure in all this what is going on. It seems to be the cdc-ether module is what needs to be modified, unless blacklisting will work. If it does, then we are good.

[bug?] Samsung Galaxy S won't tether through USB due to bad CDC descriptors -- Linux USB
http://www.spinics.net/lists/linux-usb/msg56644.html

I will check tonight, do not recall if I tried connecting sl6000 after rebooting the Pi with a blacklist file in the right place.

Hey, there may be a solution here, but I do not understand it. And it is Arch!!!!

https://bbs.archlinux.org/viewtopic.php?id=144056
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Fri Jan 18, 2013 1:39 am
That's a fair amount of work. Definitely without any vodka in system
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Fri Jan 18, 2013 2:17 am
LOL. If I tried connecting through the serial interface, would the zaurus module be unnecessary? I do not want to use minicom, I have a horrible time when I try to use it, and I want the sl6000 to be able to use VNC to the Pi, can that be done over the serial GPIO?

But they said it is an upstream issue, maybe I should ask at github where they meant?
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Fri Jan 18, 2013 9:42 am
Serial w old mean minicom, or something similar. You won't be networking with the pi, just controlling.
kernel.org is upstream, not likely anything can be done.
The question is, the mods mentioned, will it only support one type of zaurus at a time?
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Fri Jan 18, 2013 2:43 pm
One type of zaurus at a time would mean cannot do what want. Intention was to have the sl5500 running a script all the time, reminding me to do things, take meds, etc., and waiting for me to answer if I have done them, or keep bugging me. I have something similar running locally on the sl5500, but memory is too limited to handle more than one item. Have already modified script to be more versatile, if ran on Pi.

But also want to use Pi to do lots of desktop things neither zaurus can do - due to limited memory - open pdfs, go to freenode, and other stuff.

I will consult a zaurus pal - I thought he was using serial to do vnc with his zaurus sl5500, but maybe I am wrong.

Oh, cannot get in to pi right now to check, but I do recall seeing something deep in the file system where it had recorded the product number of the sl5500 and it did not look like it could have two devices, I see what you mean. It was somewhere in a cdc_ether directory, under zaurus.

Not sure what you mean by networking vs. controlling. If I could ssh in from commandline from sl6000 over serial, that would be worth doing, even if all I had access to was command line in doing so, but would want to do so from a normal terminal, not minicom.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Fri Jan 18, 2013 3:01 pm
Quite likely you won't understand any of this, but you will recognise bits
https://github.com/raspberrypi/linux/bl ... b/zaurus.c
It is the source of the driver
The thread you pointed out talks about changing some of it, you don't have to be a kernel engineer, or even know C to do that, but are they talking about an actual zaurus or a phone?
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Fri Jan 18, 2013 7:03 pm
I really think the problem is not the zaurus driver but the cdc-ether driver that tries binding zaurus devices, at least as I understand the discussion. really did seem to me that the cdc-ether driver mounted before the zaurus driver is the culprit, and zaurus driver does depend on it for collie connecting, so cannot totally remove it.

maybe i am not understanding, you are right, but that is what it looks like to me, that the cdc-ether needs to skip trying to bind to zaurus-type devices, whether they are zauruses or phones that use that false CDC MLM configuration.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by pepedog » Fri Jan 18, 2013 10:21 pm
This is old, but so am I
http://www.linux-usb.org/usbnet/
Note that until a patch to the CDCEther driver (on Linux 2.4 only) is available, preventing it from talking to these Zaurus products, you might need to add that driver to /etc/hotplug/blacklist to prevent confusion like having your Zaurus appear as eth0 and then not work right (because of the CRC). Some users have also found they need to shrink the mtu on the Zaurus, with ifconfig usb0 mtu 1000

Also, possibly, and I don't know with blacklisting, who is to say that if blacklisted initial load is blocked, but if another module subsequently requires it, it loads?
Posts: 986
Joined: Fri Oct 07, 2011 9:55 am
by sdjf » Sun Jan 20, 2013 2:34 am
thanks, that is a good page. What I feel fairly clear on, from reading the blacklist documentation for hotplugging that is in my blacklist files on the Zaurus, is that blacklisting just keeps the module from attaching to devices, but it is left free for other modules.

Blacklisting looks to work that way with hotplugging, but I have not had a chance to determine whether it works properly in systemd. the documentation out there is terribly inconsistent. When I moved the blacklist file to wherever it really goes, it interpreted the work blacklist as a driver that it did not recognize!

But I am getting to a point where I think I would rather just spend my time getting things working on the sl5500, and accept that better access to the Pi will have to wait until I can get a monitor and, if that does not work out, I may have to take the vodka route with the cdcether driver. I still think it ought to be available, but since it looks like the Pi cannot have two usbnet devices attached at the same time, I think I would rather just let it be the sl5500. That is hard, as I cannot access any hardware keyboard for it as it has to stay in it's docking station (there is a built in keyboard but only accessible when on battery power and for very brief periods).

But what I plan on doing with the sl5500 will keep the pi and sl5500 very, very busy, and I do not want to tie up the sl6000 with the alarm script it will be running. It will have popups that are terribly annoying as well as sound (when can get speakers) and I do not want those popups on the sl6000.

Doing much better now that have a better keyboard for the Pi, it means have not had to reflash in so many days that I do not remember the last time, and think things are more under control.
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by ghans » Sun Jan 20, 2013 7:15 pm
Good to see that you are coming along. :)

Just as reminder: the serial console trick does not need SSH , because its a very short physical connection.
You can log in from your Pi onto your Zaurus , or from your Zaurus onto the Pi , or from one Zaurus onto the other (AFAIK).
Depending on the situation , you might need a level shifter , but you get complete commandline acess.

I don't think VNC or anything graphical is possible though. Too high bandwith requirements.
But i thought USBNet wouldn't be workable either ...


ghans
• Don't like the board ? Missing features ? Change to the prosilver theme ! You can find it in your settings.
• Don't like to search the forum BEFORE posting 'cos it's useless ? Try googling : yoursearchtermshere site:raspberrypi.org
Posts: 4769
Joined: Mon Dec 12, 2011 8:30 pm
Location: Germany
by sdjf » Sun Jan 20, 2013 7:46 pm
ghans wrote:Good to see that you are coming along. :)


thanks, yes, I was determined. And have done it with no monitor. It has been hard, but I have succeeded. I don't think someone without much Linux command line experience could do it, that is for sure. I had to keep plugging away.

ghans wrote:Just as reminder: the serial console trick does not need SSH , because its a very short physical connection.
You can log in from your Pi onto your Zaurus , or from your Zaurus onto the Pi , or from one Zaurus onto the other (AFAIK).
Depending on the situation , you might need a level shifter , but you get complete commandline acess.


What is going on is I have two Zauruses - the older one, the sl5500 aka the collie, is getting into the pi via ssh, doing scp, and I am working on getting a vncserver installed on the Pi. But I have no hardware keyboard access for it when it is attached to the Pi and it is hard to use because of that.

The other Zaurus is much better, it has USB capabilities and I am typing on a regular keyboard with it now, but it cannot connect to the Pi using USB because of issues with the cdc-ether module. If I had to fortitude to recompile that, maybe it might be a go, but apparently only one zaurus device can be attached via usb0 to the Pi at a time, and if that is the case, I prefer it to be the collie because of what I wanted to do on all 3 devices.

At this point, I have to decide if it is worth the hassle to get the serial connection going, given that the collie can ssh and hopefully vnc in. I have seen people having issues getting the software tweaked, and am not sure I want to spend the time on it now.

ghans wrote:I don't think VNC or anything graphical is possible though. Too high bandwith requirements...
But i thought USBNet wouldn't be workable either ...


No, I think you are right about the graphical interface. A zaurus friend said there is no IP capability over serial, and there has to be some, if I understand this correctly. Maybe I will try serial access at some point, but not right now.

This is a big disappointment, I had plans for both Zauruses to have simultaneous full access to everything on the Pi, but at least one of them has it. And rather than spin my wheels trying to get limited serial access for the sl6000 to the Pi, I am working on getting things set up the way I want on the Pi, with a goal of getting to the point of being able to use it to do something more than just figure out how to get it working. :o)
FORUM TIP: To view just one person's posting history, sign in, click on their user name, then click on "Search User's Posts." || This Pi owner is running Arch on 512MB Model B.
Posts: 1304
Joined: Fri Mar 16, 2012 5:20 am
Location: California
by ghans » Sun Jan 20, 2013 9:35 pm
No, I think you are right about the graphical interface. A zaurus friend said there is no IP capability over serial, and there has to be some, if I understand this correctly. Maybe I will try serial access at some point, but not right now.

This leads to the question ... how did dial-up work then ?

http://www.tldp.org/HOWTO/PPP-HOWTO/direct.html

I really have to stop googling stuff ... look what i found ... and there is more !

http://nst.sourceforge.net/nst/docs/scripts/null-modem-ppp.html
http://nst.svn.sourceforge.net/viewvc/nst/trunk/src/scripts/null-modem-ppp/null-modem-ppp.sh?revision=4397&content-type=text%2Fplain

ghans
• Don't like the board ? Missing features ? Change to the prosilver theme ! You can find it in your settings.
• Don't like to search the forum BEFORE posting 'cos it's useless ? Try googling : yoursearchtermshere site:raspberrypi.org
Posts: 4769
Joined: Mon Dec 12, 2011 8:30 pm
Location: Germany