On Monday 26 May 2003 14:33, John Allison wrote:

hello,

thank you for fixing the e1000.0 driver. i was wondering if you could help me mount the initdisk image file off of the udpcast floppy 20030524 so i can add a new driver for the zircom combo cards we have. i can mount the image a see where all the drivers are but i can't change anything because i get an error that the image is read only. all i want to do see remove the drivers i don't need and add the one that i will make the next two months of summer imaging fast. any help would be great. just for info. i am running redhat 9, been useing udp for about 1 year and i am a linux user not a linux programer, so if you could give some details in the instructions. but most of all thank you for the e1000.0 drive.

JT John Allison Technician Alamance-burlington school system

For space saving, this is a romfs filesystem. The Romfs filesystem has been designed for compactness: Both the romfs filesystem image itself, and the driver to access it are much smaller than other alternatives, such as minixfs.

In order to change it, you need to copy it off the disk to another directory, do your changes, and then make a new romfs:

mkdir dir.old mount -o loop -t romfs initrd dir.old cp -a dir.old dir.new umount dir.old

[edit your dir.new here]

genromfs -d dir.new -f - -A 4096,/bin/busybox -A 4096,/bin/lzop | gzip -9 -c

initrd.gz

Or, maybe, just make an floppy which contains the xircom card from the get-go?:

/usr/lib/udpcast/makeImage -m 'e1000 xircom_cb' -f /dev/fd0 -k /boot/vmlinuz-2.4.21-rc3-udpcast

N.B. There is currently no cardmgr included for now. However, as far as I know, cardmgr is only needed for *_cs drivers anyways, not for *_cb.

Alain

On Monday 26 May 2003 18:19, John Allison wrote:

i tried to use the second disk with extra mods on it and found that the zircom driver is there but i keep getting a error.

"no sockets loaded"

i don't know what the means

(John Allison \206)

This means that no driver for the PCMCIA socket is loaded yet. Unfortunately, loading the PCMCIA is not yet automated (this will be fixed in the next version).

However, you can do this manually. With Alt+F2, you can switch to another virtual console where you can get a shell. Type Alt+F2, then return to activate the shell.

Then do the following commands (after the tar file has been loaded from the second disk):

modprobe pcmcia_core

Then one of the following, depending on the type of PCMCIA socket that you have. If you don't know which, just try them all:

modprobe i82092 modprobe i82365 modprobe tcic modprobe yenta_socket

Then, finally:

modprobe ds

Then, go back to the user-interface with Alt+F1, and retry loading the card driver. With a *_cb driver, this should be possible. With a *_cs driver, you'd need cardmgr, which will be included in the next version.

(Oh, and btw: when writing mails, please don't put any control characters into your message. Control characters are characters whose code is between 0-31 or between 128 and 159. On some software, it makes it hard to reply to you. I had to replace the 134 after your name with its octal expression (\206)in order to be able to send this reply)

Regards,

Alain

On Tue, 27 May 2003, John Allison wrote:

i got your email about the pcmcia driver socket but i ran into a problem.

modprobe pcmcia_core (return back to prompt no problem)

modprobe i82092 (loaded something and then returned no driver or file by that name found) modprobe i82365 (loaded something and then returned no driver or file by that name found) modprobe tcic (loaded something and then returned no driver or file by that name found) modprobe yenta_socket (loaded something and then returned no driver or file by that name found)

modprobe ds (loaded something and then said that operation not allowed)

As an idea:

You might want to use Google to get a clearer idea about the problem. I do not want to speak for Alan, but it's better to let machines answer simple questions. That'll give clever people a break, since there's a chance that they'll use it to hack on their software within that gained time. *t

-- ----------------------------------------------------------- Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 -----------------------------------------------------------

i also saw that the net-mod disk did not have all the pcmcia drivers so i added them myself and all is working fine. thanks for all the help and looking for to the next release of udp.

Alain Knaff alain@knaff.lu writes:

On Tuesday 27 May 2003 15:49, John Allison wrote:

...

hello

i got your email about the pcmcia driver socket but i ran into a problem.

modprobe pcmcia_core (return back to prompt no problem)

modprobe i82092 (loaded something and then returned no driver or file by that name found) modprobe i82365 (loaded something and then returned no driver or file by that name found) modprobe tcic (loaded something and then returned no driver or file by that name found) modprobe yenta_socket (loaded something and then returned no driver or file by that name found)

modprobe ds (loaded something and then said that operation not allowed)

now i am guessing that this mean that the pcmcia socket on the dell laptop is not linux friendly. am i right or just not doing something right. when

Just noticed that the net-mod.tar.gz did not contain any drivers for the PCMCIA sockets (it contained drivers only for the cards...). I've made another tar containing the missing drivers:

http://udpcast.linux.lu/udpcast/20030524/pcmcia.tar.gz

Put this on the same floppy than net-mod.tar.gz (it should fit), and udpcast should untar both into the ramdisk. After that, one of the modprobes for i82092, i82365, tcic or yenta_socket should succeed.

Regards,

Alain

(John Allison †)