|
|
Tuesday, April 01, 2003
editing and viewing cron files
I have been asked recently about cron files under linux. Here is what I told them.No IRQ known for interrupt pin A of device 00:3.0. Please try using pci=biosirq.
Okay, I got two new servers and I loaded Red Hat 7.3 on them. The networking did not get configured during install. This was my first clue that the system did not see the cards.Comments:
on 05/29 at 11:44 AM said:
BRILLIANT!!!
I’ve been fighting with my Asus A7M266-D dual athlon for days now. Upgraded the “AwardBIOS”, disabled onboard components, manually configured IRQs, fiddled with MPS1.4 BIOS settings, to no avail - with RedHat9.0-smp the network card would just puke with a syslog of ‘eth0: could not reserve IRQ 0’. Works fine under Win2K, fine under RH9.0, so it can’t be a hardware problem now could it!
Thanks to your advice I tried setting the BIOS’s PnP OS setting to ‘No’ ... and it worked first time. Who’d of thought.
on 06/22 at 01:49 AM said:
Excellent work!
Here’s my story ...
ASUS P4SDX Motherboard with onboard LAN (sis900)
D-Link DFE-530TX PCI 10/100 LAN card
RedHat 9.0
Same type of problem: unable to get the system to recognize either LAN interface. Similar error messages to those you describe.
Tried adding “pci=biosirq” to the bootloader (GRUB) config file ... no success.
Toggled “PnP OS” setting in the BIOS as you suggested ... kudzu found the two ethernet controllers (and the sound controller to boot!) and everything works just fine.
Thanks!
on 12/29 at 08:36 AM said:
Anyone with problems such as:
Buggy MP Table
or
usb-ohci found no IRQ check BIOS Settings
Just change PNP OS setting to No in BIOS. Works like a charm after a long lonely struggle....
THANKS MOOSE
Asus A7M266 with NEC Usb controller and Logitech ball mouse
on 01/08 at 10:28 AM said:
I was configuring a Notebook Toshiba Satellite 2180CDT, trying to configure two network cards, a 3Com and a Realtek, without success.
After reading this article, I enter in the BIOS, and change the “Card mode” from “Auto Detect” to “CardBus Mode”.
Works for me, now I can run both without problems.
Thanks for Moose!
on 01/21 at 06:54 AM said:
I got exactly the same problem with the “No IRQ known ...”, BUT i am not able to set the pnp-bios flag “off”, because the bios of my notebook just doesn’t support this.
Is there a way to tell linux to manage the irq’s?
SuSE 9.0 and Knoppix were able to detect my pcmcia card, but all other 2.4 distro’s weren’t (i want to use fedora core 1)
Thx in advance,
Stefan
Moose on 01/21 at 05:01 PM said:
Stef,
Check google… Obviously since two distros do it, the others “can”. The question is what are they doing - what scripts are the instantiating during boot that are different? Follow the boot process for a “bad” distro and for a “good” distro. You will learn a lot, and probably find out how they did it.
Best I can do.
Moose
can log in to box, but can’t get to irc server…
<B>can log in to box, but can't get to irc server...</B> I got that message today from sockmonk. I used an IRC client, and got the following error. <I>Unable to connect to port 6667 of server : Resource temporarily unavailable</I> Hmm... wonder what that could be... I knew irc.lplug.org was up, I was logged on to it. I knew networking was working, I was using it.Lost Root Password - RH 7.2
<B>Resetting Root Password without knowing it.</B> I got a call from Asbury the other day. It seems that after moving a Red Hat 7.2 development server the new admin could not log in as root. First, I told him to make sure caps lock was off. He tried again but with the same results. I then walked him through booting from a CD in rescue mode and clearing out Root's password.Comments:
on 07/01 at 04:45 AM said:
Step 6: Edit the shadow file,
how to do ?.. shadow & edit ?.
Moose on 07/01 at 08:16 PM said:
The shadow file is /etc/shadow. You edit it with vi or whatever your favorite editor is.
-Moose
