Re: Linux not adhering to BIOS Drive boot order?
Florent Cueto Java developer Socks via HTTP Homepage : http://www.javawork.net (A program to tunnel socks requests via HTTP). - Original Message - From: "Venkatesh Ramamurthy" <[EMAIL PROTECTED]> To: "'David Woodhouse'" <[EMAIL PROTECTED]>; "Venkatesh Ramamurthy" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "'Alan Cox'" <[EMAIL PROTECTED]> Sent: Tuesday, January 16, 2001 5:19 PM Subject: RE: Linux not adhering to BIOS Drive boot order? > > It should be possible to read the BIOS setting for this option and > > behave accordingly. Please give full details of how to read and interpret > > the information stored in the CMOS for all versions of AMI BIOS, and I'll > > take a look at this. > [Venkatesh Ramamurthy] When i meant BIOS setting option i meant the > SCSI BIOS settings not system BIOS option. The two SCSI controllers are of > different make. This situation is made worse when the system has many cards > of different makes and one of the controller somewhere in the middle of all > the slots is made the boot controller. > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux not adhering to BIOS Drive boot order?
Florent Cueto Java developer Socks via HTTP Homepage : http://www.javawork.net (A program to tunnel socks requests via HTTP). - Original Message - From: "Venkatesh Ramamurthy" [EMAIL PROTECTED] To: "'David Woodhouse'" [EMAIL PROTECTED]; "Venkatesh Ramamurthy" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; "'Alan Cox'" [EMAIL PROTECTED] Sent: Tuesday, January 16, 2001 5:19 PM Subject: RE: Linux not adhering to BIOS Drive boot order? It should be possible to read the BIOS setting for this option and behave accordingly. Please give full details of how to read and interpret the information stored in the CMOS for all versions of AMI BIOS, and I'll take a look at this. [Venkatesh Ramamurthy] When i meant BIOS setting option i meant the SCSI BIOS settings not system BIOS option. The two SCSI controllers are of different make. This situation is made worse when the system has many cards of different makes and one of the controller somewhere in the middle of all the slots is made the boot controller. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
kernel 2.2.16 in redhat 7.0
The kernel provided with the redhat 7.0 cannot be compiled with ip masquerading on & icmp masquerading on (using gcc and kgcc, I got the same error). I could not found any information about that. Anyone can help ?
Re: 2.2 / 2.4 ethernet detection order
I got the same problem. The consequence was that if my eth0 card (static ip) was "ifupped" before my eth1 card (dhcp), it became impossible to ifup my eth1 card (I could no more obtain an ip from the dhcp server). - Message d'origine - De : James Lewis Nance <[EMAIL PROTECTED]> À : <[EMAIL PROTECTED]> Envoyé : mardi 5 septembre 2000 15:55 Objet : 2.2 / 2.4 ethernet detection order > Hello All, > I have a box with 2 ethernet cards. One is a ne2k-pci and one is a > tulip. Under 2.2.X the ne card is eth0 and the tulip is eth1. Unfortunatly > if I boot a 2.4.X kernel, the tulip card is assigned eth0 and the ne card > eth1, which of course breaks all my networking setup scripts. I can get > the 2.4.X kernels to assign 2.2.X identities by using command line args > like (from memory): > > ethers=eth1 > > but unfortunatly at least one of the cards does not work if I try this. > I "solved" the problem by using kernel modules and an /etc/modules.conf > file that looks like this: > > alias eth0 ne2k-pci > alias eth1 tulip > > but I would really rather not use a modular kernel. I have no idea what I > would do if I had two identical network cards in the computer. Is there > a better way to solve this problem? > > Thanks, > > Jim > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
