[Udpcast] Udpcast 20030601: support for integrating custom scripts and improved PCMCIA handling
There is a new version, 20030601, which makes it easyer to include custom scripts to be run before or after the transfer.
* Udpcdialog now has hooks that are called before and after the actual transfer:
/udpreceiver.pre This script is invoked before starting udpreceiver
/udpreceiver.post This script is invoked after udpreceiver has finished. It gets called with a single parameter, which is the exit status of udpreceiver
/udpsender.pre This script is invoked before starting udpsender.
/udpsender.post This script is invoked after udpsender has finished. It gets called with a single parameter, which is the exit status of udpsender
* These scripts can easily be put into the initrd by using makeImage's new --merge option:
makeImage -c cd.img -k /boot/vmlinuz-2.4.21-rc6-udpcast \ --merge /udpreceiver.pre=my-pre-script \ --merge /udpreceiver.post=my-post-script
* There is now better support for PCMCIA cards (cardmgr included, automatic probing for "socket" driver modules). However, this is still largely untested.
* lzop is now integrated in busybox, rather than being a statically compiled standalone binary. This saves some space.
Have fun,
Alain
i tried the new udp 20030601 with dell c600 laptops and it did not work. i went back to loading the drivers for the sockets by hand. this seems to work fine. i used the 2003052* udp floppy and added the pcmcia drivers to it and then loaded them by hand. to get this to work i had to put the cardmrg (for the *.cs drivers) into the /bin directory. once i had all of the pieces into place it works. just letting you know.
(John Allison )
On Tuesday 10 June 2003 20:52, John Allison wrote:
i tried the new udp 20030601 with dell c600 laptops and it did not work. i went back to loading the drivers for the sockets by hand. this seems to work fine. i used the 2003052* udp floppy and added the pcmcia drivers to it and then loaded them by hand. to get this to work i had to put the cardmrg (for the *.cs drivers) into the /bin directory. once i had all of the pieces into place it works. just letting you know.
(John Allison !!@$%@!@#$%!#@*&)
Hmm, I think I understand where these problems might be coming from: the i82092 module can be inserted "succesfully" even if no such socket exists. However, I have a strong suspicion that when this happens, it actually prevents other PCMCIA socket modules from working (i.e. if i82092 is inserted before the right module, it won't work).
In today's version (20030610), the bin/probecards script loads the modules in such an order that i82092 comes last. Moreover, after a successful insertion, it stops trying to insert more socket modules (just in case the i82092 is capable of messing up stuff, even _after_ insertion of the correct module)
[N.B. If you use floppies, please be aware that the udpcflop.img does not contain any PCMCIA modules. You need udpcflop-pcmcia.img for that]
Could you try it out whether this works better?
Thanks,
Alain
hello
i would love to try this update for you but where can i get it.. there is no link to it and the latest version on the site is 20030527
Alain Knaff alain@knaff.lu writes:
On Tuesday 10 June 2003 20:52, John Allison wrote:
i tried the new udp 20030601 with dell c600 laptops and it did not work. i went back to loading the drivers for the sockets by hand. this seems to work fine. i used the 2003052* udp floppy and added the pcmcia drivers to it and then loaded them by hand. to get this to work i had to put the cardmrg (for the *.cs drivers) into the /bin directory. once i had all of the pieces into place it works. just letting you know.
(John Allison !!@$%@!@#$%!#@*&)
Hmm, I think I understand where these problems might be coming from: the i82092 module can be inserted "succesfully" even if no such socket exists. However, I have a strong suspicion that when this happens, it actually prevents other PCMCIA socket modules from working (i.e. if i82092 is inserted before the right module, it won't work).
In today's version (20030610), the bin/probecards script loads the modules in such an order that i82092 comes last. Moreover, after a successful insertion, it stops trying to insert more socket modules (just in case the i82092 is capable of messing up stuff, even _after_ insertion of the correct module)
[N.B. If you use floppies, please be aware that the udpcflop.img does not contain any PCMCIA modules. You need udpcflop-pcmcia.img for that]
Could you try it out whether this works better?
Thanks,
Alain
(John Allison )
On Wednesday 11 June 2003 14:04, John Allison wrote:
hello
i would love to try this update for you but where can i get it.. there is no link to it and the latest version on the site is 20030527
It's all under http://udpcast.linux.lu/current/
After this, it depends whether you want the floppy image, the CD Image, the makeImage RPM, ...
For instance, the PCMCIA floppy image is http://udpcast.linux.lu/current/udpflop-pcmcia.img
Alain
hello
i downloaded the update and tested on two differnet latop pcmcia cards. one 3com and the other xircom. the drivers tried to load and it looks like that did but no connection. i rebooted and alt-f2 and loaded the drivers by hand and they connected.
(John Allison )
On Wednesday 11 June 2003 14:44, John Allison wrote:
hello
i downloaded the update and tested on two differnet latop pcmcia cards. one 3com and the other xircom. the drivers tried to load and it looks like that did but no connection. i rebooted and alt-f2 and loaded the drivers by hand and they connected.
(John Allison )
Did you get any error messages?
Which drivers did you load by hand: Only the card drivers (*_cs), or also the socket driver(s) (i82092, yenta_socket, ...)?
Btw, this weird Shift-Control-F after your name is still there...
Alain
hello no error message. the screen shows some drivers loading and then it ask if you want to use dhcp or not. you go through the rest of the process just like normal. but at the end there is no connection. but if you alt+f2 and load drivers it works. the drivers i loaded were pcmcia_core first. then the i82092, yenta_socket. then modprobe ds to finsh. this works and i get connection. i am useing the *.cs driver i think. whichever one needs the cardmgr.
Alain Knaff alain@knaff.lu writes:
On Wednesday 11 June 2003 14:44, John Allison wrote:
hello
i downloaded the update and tested on two differnet latop pcmcia cards. one 3com and the other xircom. the drivers tried to load and it looks like that did but no connection. i rebooted and alt-f2 and loaded the drivers by hand and they connected.
(John Allison )
Did you get any error messages?
Which drivers did you load by hand: Only the card drivers (*_cs), or also the socket driver(s) (i82092, yenta_socket, ...)?
Btw, this weird Shift-Control-F after your name is still there...
Alain
On Wednesday 11 June 2003 17:59, John Allison wrote:
hello no error message. the screen shows some drivers loading and then it ask if you want to use dhcp or not. you go through the rest of the process just like normal. but at the end there is no connection.
What do you mean by "at the end there is no connection"? That DHCP does not succeed to get an address? If that happens, you _always_ get an error message. There is no code path where DHCP fails without an error message. If it fails much later, when exactly does it fail? At the very end, after starting udp-receiver / udp-sender
Btw, did you get the screen where you get to chose a network module? If not, this means that the system has found a card and succeeded to read its Mac address. If it is unable to get a DHCP address, this means that maybe there is some problem on the DHCP server.
Did you try to enter an IP Address and Netmask manually? In that case, what happens exactly? Does manual configuration fail (i.e. error message after entering netmask). If you do get an error message, what does it say. If you don't, what else happens?
Could you also check whether the probecards script gave any error messages (you can watch them with Alt-F7, when you are at the driver selection screen, or, in case the driver selection screen is skipped, at the "do you want DHCP" screen)
Regards,
Alain
hello alain
i will use alt+f7 to watch the scripts. when i say no connection is that the sender will not talk to the receiver. useing the xircom cards with a 10/100 switch i get a connection light when the sender/receivers are setup and talking to each other. this happens when i load the drivers for the pcmcia and socket and xircom card by hand. i am useing static ip's and not dhcp. what happens is that when you boot useing the 20036010 for pcmcia script start like it should. i choose english from th list and then it it tries to autoprobe the nic and i get a flash of code going up the screen that looks like the drivers loading. then it comes back to the screen where it ask if you want dhcp or static ip. i don't get the screen where i can choose my own nic. i use static (no dhcp server yet) and setup all that (ip address and subnet mask). then its changes to a black screen with the standard "sender setup ready to image" screen. it looks like everything is okay but when i setup the receiver that doesn't connect and the lights on the switch are not on. Now if i load the drivers by hand:
modprobe pcmcia_core modprobe i82092 modprobe yenta_socket modprobe ds
the lights on the switch are lite and the sender and receiver have a connection and i can cast. again there are no error messages or screens. everything looks like it should.
Alain Knaff alain@knaff.lu writes:
On Wednesday 11 June 2003 17:59, John Allison wrote:
hello no error message. the screen shows some drivers loading and then it ask if you want to use dhcp or not. you go through the rest of the process just like normal. but at the end there is no connection.
What do you mean by "at the end there is no connection"? That DHCP does not succeed to get an address? If that happens, you _always_ get an error message. There is no code path where DHCP fails without an error message. If it fails much later, when exactly does it fail? At the very end, after starting udp-receiver / udp-sender
Btw, did you get the screen where you get to chose a network module? If not, this means that the system has found a card and succeeded to read its Mac address. If it is unable to get a DHCP address, this means that maybe there is some problem on the DHCP server.
Did you try to enter an IP Address and Netmask manually? In that case, what happens exactly? Does manual configuration fail (i.e. error message after entering netmask). If you do get an error message, what does it say. If you don't, what else happens?
Could you also check whether the probecards script gave any error messages (you can watch them with Alt-F7, when you are at the driver selection screen, or, in case the driver selection screen is skipped, at the "do you want DHCP" screen)
Regards,
Alain
-
Alain Knaff -
John Allison