About 3 years ago I had installed Caldera Linux 2.4 on this Notebook PC and it auto-detected my Dynalink 1433 PCMCIA card modem as 'Model AT&T 1428 VQE chipset' , and I had no problem getting it to function. Now, SuSE 8.0 Professional cannot detect ANY pcmcia card (modem or ethernet) on the same Notebook and all it can do is display a message in the Console log as follows: "PCI: No IRQ known for interrupt Pin A of device 00:13:0 PCI: No IRQ known for interrupt Pin A of device 00:13:1 Please try using pci=biosirq" This question was referred to SuSE Support more than 10 days ago but to date it remains unanswered ! Please could someone tell me WHERE I am supposed to enter "pci=biosirq". Tried all the likely locations without success. The much acclaimed Yast2 tool is not able to detect a simple PCMCIA card on a Linux distro in the year 2002, while in 1997 a much older distro had no problem with it ! And SuSE 90 day support seems to be waiting for the 90 days to elapse - this to me is hard to believe. I have gone through all the HOWTOS and faqs and man pages, also sdb online and still don't have a clue and this is really frustrating as I know for sure that the problem is not the hardware. Hoping someone out there can help solve this question Regards and TIA Roy
On Fri, May 10, 2002 at 12:13:06AM +0200, Roy Leembruggen wrote:
About 3 years ago I had installed Caldera Linux 2.4 on this Notebook PC and it auto-detected my Dynalink 1433 PCMCIA card modem as 'Model AT&T 1428 VQE chipset' , and I had no problem getting it to function.
Have you tried setting PCMCIA_SYSTEM=external in /etc/sysconfig/pcmcia? Best Regards, Keith -- LPIC-2, MCSE, N+ Got spam? Get spastic http://spastic.sourceforge.net
All, Thanks to Ray - all I needed was to add the word "rlogin" to the file /etc/securetty. All happy and insecure now :-) Damian Ray Schwamberger wrote ... Make sure that rsh and rlogin are in you /etc/securetty file and possibly /etc/hosts.equiv. Like you said, this is very bad practice but it is commonly done in clustering environments to ease inter-node communication. Damian Ohara wrote:
Hi,
I know it's not recommended, but as part of our root admin management tool I need to rsh into machines as root without knowing the root password for that machine.
This was OK on pre-8.0 machines (just add the remote machinename in /root/.rhosts) but is strange under 8.0.
As root on the client this works OK ...
rsh servername w
However, this ...
rsh servername
for an interactive login, asks for a password.
This is the point. I don't have the root password on the remote box (and don't want it).
Anybody shed any light on why non-interactive works but interactive doesn't when there's a trust set up?
I've looked through Suse.com/SDB ... Google ... etc etc and played with the rshd entry in inetd.conf - using -h and so on (and /etc/pam.d/rsh)
Thanks,
Damian :-)
-- Damian O'Hara using: SuSE Linux 8.0 12:25pm up 13 days, 22:57, 21 users, load average: 0.55, 0.60, 0.54
participants (3)
-
Damian Ohara -
Keith Winston -
Roy Leembruggen