Re: [Cooker] PCMCIA problems
Same problem here.. no luck with the DWL650 either. (does work sometimes but very slow and takes ages tp find the AP 1meter away...) BErnard James Sparenberg wrote: On Wed, 2003-01-29 at 06:19, Matt Phillips wrote: On Tue, Jan 28, 2003 at 11:04:35PM -0800, James Sparenberg wrote: I'm trying to get wireless working. I can't even get 2 of the most supported cards around to work. D-Link DWL-650 and an Orinoco Gold I used from a friend of mine. 2.4.19-18mdk was the last kernel that worked with my D-Link DWL-650; you might try that if you can find it. I reported this at the time, but nobody seemed to care (and it was before cooker used bugzilla to track such things). -Matt Matt Thanks will look for it. I'm running 2.4.19-16mdk now as well and still having trouble. Could I trouble you for some off list help in getting it to work? James . -- Digital Objects Ltd Internet security / Web hosting & design / Web enabled applications PO Box 60510, Titirangi Waitakere City Phone: 0800 LETS DOIT (538736) Fax: +64 9 8128 368 www.digitalobjects.co.nz
Re: [Cooker] PCMCIA problems
On Wed, 2003-01-29 at 06:19, Matt Phillips wrote: > On Tue, Jan 28, 2003 at 11:04:35PM -0800, James Sparenberg wrote: > > I'm trying to get wireless working. I can't even get 2 of the most > > supported cards around to work. D-Link DWL-650 and an Orinoco Gold I > > used from a friend of mine. > > 2.4.19-18mdk was the last kernel that worked with my D-Link DWL-650; you > might try that if you can find it. I reported this at the time, but > nobody seemed to care (and it was before cooker used bugzilla to track > such things). > > -Matt Matt Thanks will look for it. I'm running 2.4.19-16mdk now as well and still having trouble. Could I trouble you for some off list help in getting it to work? James
Re: [Cooker] PCMCIA problems
On Tue, Jan 28, 2003 at 11:04:35PM -0800, James Sparenberg wrote: > I'm trying to get wireless working. I can't even get 2 of the most > supported cards around to work. D-Link DWL-650 and an Orinoco Gold I > used from a friend of mine. 2.4.19-18mdk was the last kernel that worked with my D-Link DWL-650; you might try that if you can find it. I reported this at the time, but nobody seemed to care (and it was before cooker used bugzilla to track such things). -Matt -- Matt Phillips <[EMAIL PROTECTED]> ICT-Carlisle, Operation Mobilisation Public PGP Key: http://moses.om.org/~mattp/gpg.asc
Re: [Cooker] PCMCIA problems
James Sparenberg wrote: Vincent, I've been pulling what hair I have left out lately over a problem that may or may not be related. What I've found when insert a cardbus style pcmcia card (32 bit ones) or any USB device is that hotplug attempts to start everything on the PCI bus. Which on this comp is everything. VGA sound the works. Older non Cardbus PCMCIA cards that have a static IRQ demand work fine. PCI assigns everthing to IRQ 11 (this is a designed by Manf IRQ and I can't change it.) When you do insert the pcmcia card do tail -f /var/log/messages and I'm willing to bet you see a similar event happening. Hotplug also insists on loading uhci even though usb-uhci is it's replacement and the fact that uhci is in the blacklist in /etc/hotplug/blacklist. BTW I'm trying to get wireless working. I can't even get 2 of the most supported cards around to work. D-Link DWL-650 and an Orinoco Gold I used from a friend of mine. and I get same issues with dlink 680tx cardbus nic James On Tue, 2003-01-28 at 15:05, Vincent Meyer, MD wrote: Hello, There are still problems with PCMCIA support, which have been there for some time. I haven't bothered to test to see if they'd been fixed since pre 9.0 days.. and today discovered that they are indeed still a problem. Plugging and unplugging pcmcia cards can cause the interupt handler in the kernel to crash. Message that EIP is at (2.4.21pre3-2mdk) then a register dump then <0> kernel panic Aiee, killing interupt handler! In interupt handler, not syncinf. The caps lock and scroll lock lights blinking. Also, more annoying than anything else, is when the modem is plugged in at boot time (can't plug it in later - the interupt handler will crash about 25% of the time), and you try to use it it's busy. Have to modprobe -r serial_cs then modprobe serial_cs to get it to work. Additional info or files or whatever needed to help debug, let me know and i'll send it.
Re: [Cooker] PCMCIA problems
Vincent, I've been pulling what hair I have left out lately over a problem that may or may not be related. What I've found when insert a cardbus style pcmcia card (32 bit ones) or any USB device is that hotplug attempts to start everything on the PCI bus. Which on this comp is everything. VGA sound the works. Older non Cardbus PCMCIA cards that have a static IRQ demand work fine. PCI assigns everthing to IRQ 11 (this is a designed by Manf IRQ and I can't change it.) When you do insert the pcmcia card do tail -f /var/log/messages and I'm willing to bet you see a similar event happening. Hotplug also insists on loading uhci even though usb-uhci is it's replacement and the fact that uhci is in the blacklist in /etc/hotplug/blacklist. BTW I'm trying to get wireless working. I can't even get 2 of the most supported cards around to work. D-Link DWL-650 and an Orinoco Gold I used from a friend of mine. James On Tue, 2003-01-28 at 15:05, Vincent Meyer, MD wrote: > Hello, > > There are still problems with PCMCIA support, which have been there for some > time. I haven't bothered to test to see if they'd been fixed since pre 9.0 > days.. and today discovered that they are indeed still a problem. > > Plugging and unplugging pcmcia cards can cause the interupt handler in the > kernel to crash. Message that EIP is at (2.4.21pre3-2mdk) > then a register dump then > <0> kernel panic > Aiee, killing interupt handler! > In interupt handler, not syncinf. > > The caps lock and scroll lock lights blinking. > > Also, more annoying than anything else, is when the modem is plugged in at > boot time (can't plug it in later - the interupt handler will crash about 25% > of the time), and you try to use it it's busy. Have to modprobe -r serial_cs > then modprobe serial_cs to get it to work. > > Additional info or files or whatever needed to help debug, let me know and > i'll send it. > > V. >
[Cooker] PCMCIA problems
Hello, There are still problems with PCMCIA support, which have been there for some time. I haven't bothered to test to see if they'd been fixed since pre 9.0 days.. and today discovered that they are indeed still a problem. Plugging and unplugging pcmcia cards can cause the interupt handler in the kernel to crash. Message that EIP is at (2.4.21pre3-2mdk) then a register dump then <0> kernel panic Aiee, killing interupt handler! In interupt handler, not syncinf. The caps lock and scroll lock lights blinking. Also, more annoying than anything else, is when the modem is plugged in at boot time (can't plug it in later - the interupt handler will crash about 25% of the time), and you try to use it it's busy. Have to modprobe -r serial_cs then modprobe serial_cs to get it to work. Additional info or files or whatever needed to help debug, let me know and i'll send it. V.
Re: [Cooker] pcmcia problems on acer travelmate 202T
On Mon, Mar 11, 2002 at 10:54:33PM +0100, Guillaume Cottenceau wrote: > Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: > > > On Mon, Mar 11, 2002 at 05:26:01PM +0100, Guillaume Cottenceau wrote: > > > Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: > > > > > > When did you first saw this msg "get dev info failed"? What beta, > > > what kernel? When I fixed your problem, you didn't see it? When > > > did you have a working situation? > > > > I got the rc1 .img to work. I cold booted it instead of warm booting. > > Should not matter, but it does... > > So, to sum up, when you cold boot the rc1 it works?? I am not sure I always can do it, but, yes, I can do it sometimes, cold booting. A bit strange, I think. keld
Re: [Cooker] pcmcia problems on acer travelmate 202T
Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: > On Mon, Mar 11, 2002 at 05:26:01PM +0100, Guillaume Cottenceau wrote: > > Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: > > > > When did you first saw this msg "get dev info failed"? What beta, > > what kernel? When I fixed your problem, you didn't see it? When > > did you have a working situation? > > I got the rc1 .img to work. I cold booted it instead of warm booting. > Should not matter, but it does... So, to sum up, when you cold boot the rc1 it works?? -- Guillaume Cottenceau - http://www.frozen-bubble.org/
Re: [Cooker] pcmcia problems on acer travelmate 202T
On Mon, Mar 11, 2002 at 05:26:01PM +0100, Guillaume Cottenceau wrote: > Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: > > When did you first saw this msg "get dev info failed"? What beta, > what kernel? When I fixed your problem, you didn't see it? When > did you have a working situation? I got the rc1 .img to work. I cold booted it instead of warm booting. Should not matter, but it does... Keld
Re: [Cooker] pcmcia problems on acer travelmate 202T
Keld Jørn Simonsen <[EMAIL PROTECTED]> writes: [...] > * needs memory_cs Can you print messages before that? To obtain them, switch to console #3 the fastest you can once kernel booted, and when there is no more new lines printed out, Shift-PageUp to see the top messages. > *file-not-found-in-archive memory_cs.o (maybe you can try another boot floppy such >as 'other.img' for seldom used SCSI modules) > * warning: insmod failed (memory_cs (null)) (2) > * CM: get dev info on socket 0 failed: When did you first saw this msg "get dev info failed"? What beta, what kernel? When I fixed your problem, you didn't see it? When did you have a working situation? -- Guillaume Cottenceau - http://www.frozen-bubble.org/
[Cooker] pcmcia problems on acer travelmate 202T
Here is a transcript of the log, as requested: This is with the pcmcia.img of rc1, network.img gave similar results. I have also tried other.img , the result there was a lot worse. * needs memory_cs *file-not-found-in-archive memory_cs.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * warning: insmod failed (memory_cs (null)) (2) * CM: get dev info on socket 0 failed: * CM: initiating socket 1 * CM: socket 1: Anonymeous Memory * have to insmod memory_cs * needs memory_cs *file-not-found-in-archive memory_cs.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * warning: insmod failed (memory_cs (null)) (2) * CM: get dev info on socket 0 failed: * cardmgr rc: 0 * Total memory: 192 Mbytes * PCI: device 10b9 5237 is "" (usb-ohci) * needs usbcore *file-not-found-in-archive usbcore.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * needs usb-ohci *file-not-found-in-archive usb-ohci.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * warning: insmod failed (usb-uhci (null)) (2) * have to insmod usb-storage * needs usbcore *file-not-found-in-archive usbcore.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * needs scsi_mod * needs usb-storage *file-not-found-in-archive usb-staorage.o (maybe you can try another boot floppy such as 'other.img' for seldom used SCSI modules) * warning: insmod failed (usb-staorage (null)) (2) * USB: couldn't mount /proc/bus/usb * USB: could not open proc file * unsetting automatic (and that was the end. keld
[Cooker] PCMCIA problems
Hello, I have a Future Domain PCMCIA SCSI 1 card. This card worked fine with the kernel-pcmcia-cs 2.2.18 kernel, but not with the 2.4 kernel. On inserting the card the following is output : scsi: Usage: fdomain=,[,] scsi: Bad LILO/INSMOD parameters? scsi: Cannot locate chip at port base 0x0 scsi: Bad LILO/INSMOD parameters? Try to free nonexistant resource <0140 - 014F> With the 2.2.18 kernel the card was reported as using port base 0x140 and IRQ 9. So far all I've managed to achieve by editing the /etc/pcmcia/config file is to disable the PCMCIA services all together !!! Please could anyone tell me what I should be doing to get this card working ? Thanks, Owen
[Cooker] pcmcia problems with kernel-2.2.17-21mdk
I found a problem with pcmia tree of kernel-sources-2.2.17-21mdk : although giving exact modules installation dir during configuration, everything get installed in /home/chmou/rpm/buildroot... :-) -- Guillaume Rousse Murphy's law : If anything can go wrong, it will. O'Tool's commentary : Murphy was an optimist.
[Cooker] pcmcia-problems with Tokenring
Hi,
since a few days I have big problems on Mandrake Beta (all latest fixes
installed) with my
Thinkpad + Tokenring (PCMCIA) and DHCP.
Always when I enable dhcp the system crashed during boot with
kernel-panic.
I'm not sure if this is a kernel-, dhcp- or pcmcia-problem.
I tryed several things - different versions of dhcp but without success.
>From a previous kernel-oops I saw that maybe something is wrong with the
ibmtr_cs kernel-modul.
So my next step would be to get the last pcmcia-package from
pcmcia-cs.sourceforge.net
which is pcmcia-cs.11-Oct-00.tar.gz (pcmcia-cs-3.1.22), Mandrake has
version pcmcia-cs-3.1.20.
I tryed to comile this but without success, all what I get is something
like this:
[root@mumpel pcmcia-cs-3.1.22]# make all
...
/usr/src/linux/include/linux/sched.h:503: warning: `__set_current_state'
redefin
ed
../include/pcmcia/k_compat.h:169: warning: this is the location of the
previous
definition
In file included from /usr/src/linux/include/linux/fs.h:12,
from /usr/src/linux/include/linux/tty.h:20,
from /usr/src/linux/include/linux/sched.h:21,
from /usr/src/linux/include/linux/vmalloc.h:4,
from /usr/src/linux/include/asm/io.h:102,
from ../include/pcmcia/k_compat.h:184,
from cs.c:35:
/usr/src/linux/include/linux/wait.h:19: redefinition of
`wait_queue_head_t'
../include/pcmcia/k_compat.h:64: `wait_queue_head_t' previously declared
here
{standard input}: Assembler messages:
{standard input}:9: Warning: Ignoring changed section attributes for
.modinfo
make[1]: *** [cs.o] Error 1
make[1]: Leaving directory `/usr/src/pcmcia-cs-3.1.22/modules'
make: *** [all] Error 2
So I was not able to compile this on Mandrake, I tryed to compile this
on a SuSE-distribution and it works without probs.
So I think Mandrake has a bug or some strange kernel-src-modifications.
Please can anyone help me to get this working again
Compiling, ibmtr_cs, dhcp
The new hackerkernels from the Beta and from cooker have all unresolved
symbols (depmod -a)
in ibmtr_cs.o so I can't use this too.
Thanks for any help
Udo
Re: [Cooker] PCMCIA Problems
On 29 Dec 1999, Pixel wrote: > Seth Mos <[EMAIL PROTECTED]> writes: > > > > > The ifport is not available on pcmcia install to set the port in another state. > > I need that one also to get a Compaq 10/100 card going in 100Mbit which > > with the foolproof (tm) auto negotiation will work only in 10Mbit. > > So inclusion with the pcmcia bootdisk would be appreciated. > > > > ok, i put ifport at install > Thanks :-) Spiffy installer btw :-) Greets, Seth Mos
Re: [Cooker] PCMCIA Problems
Seth Mos <[EMAIL PROTECTED]> writes: > > The ifport is not available on pcmcia install to set the port in another state. > I need that one also to get a Compaq 10/100 card going in 100Mbit which > with the foolproof (tm) auto negotiation will work only in 10Mbit. > So inclusion with the pcmcia bootdisk would be appreciated. > ok, i put ifport at install
[Cooker] PCMCIA Problems
Hi, Installation problems with an brand new Xircom Realport RBEM56G-100 + Modem Cardbus card. The card is found during pcmcia install correctly. Initialised on 100Mb-FD but carrier errors. This on itself is not the largest problem. It does however prevent DHCP from working. Setting a static IP does work to get the connection going. Setting eth0 in promiscious mode also helps in getting it going. Packet errors al the way. throughput is about 400KB/s max. This card is probably one of the newest xircom revisions. This behaviour occurs on both an 3com 630 switch and a netgear fs108. The 3com also thinks filtering out the corrupt packtes is funny. ;-) The ifport is not available on pcmcia install to set the port in another state. I need that one also to get a Compaq 10/100 card going in 100Mbit which with the foolproof (tm) auto negotiation will work only in 10Mbit. So inclusion with the pcmcia bootdisk would be appreciated. I updated pcmcia-cs to 3.1.8 to get better results from the card. Wich helped ethernet somewhat but killed the modem. 2.2.14-11mdk kernel on a Dell Inspirion 7500 with a TI-1225 pcmcia Controller. No problems as of yet with the maestro 2E btw. Seems to work decent enough. Greets, Seth Mos -- Greets Don't fear the pinguin, just use it (sort of). Why is the MTBF of software close to negative? icq: 9605300|http://stimpy.multiweb.nl/
Re: [Cooker] PCMCIA Problems: LanPro EP4000A and Apollo RE450CT
Troels Liebe Bentsen <[EMAIL PROTECTED]> writes: > I am having problems installing on LanPro EP4000A and Apollo RE450CT on > oxygen, 6.0 and 6.1. > Redhat 5.2 and 6.0 have no problems. > > It seems that part of the pcmcia i broken the pcnet_cs driver it uses > for > both cards are there but i can not utilize them. > > I Redhat 5.2 and 6.0 the installation detects the card and moves on, but > in > mandrake the card is not detected and none of the cards in the list uses > pcnet_cs driver. i added the missing modules to the list. could you try out this boot disk? ftp://ftp.mandrakesoft.com/pub/pixel/pcmcia.img
[Cooker] PCMCIA Problems: LanPro EP4000A and Apollo RE450CT
I am having problems installing on LanPro EP4000A and Apollo RE450CT on oxygen, 6.0 and 6.1. Redhat 5.2 and 6.0 have no problems. It seems that part of the pcmcia i broken the pcnet_cs driver it uses for both cards are there but i can not utilize them. I Redhat 5.2 and 6.0 the installation detects the card and moves on, but in mandrake the card is not detected and none of the cards in the list uses pcnet_cs driver. Please help so this problem can be fixed before 7.0. thanks Troels Liebe Bentsen
