Re: Network install

Il lun, 2004-01-12 alle 00:48, Carlos Eduardo Coelho Baptista ha scritto: > Alessandro Riz wrote: > > >Hi, > > I'm trying to install debian ppc from internet, at home I've an adsl > >connection (I use pppoe), but I've a dynamic ip, during the installation > >it tell me to configure the network but

Re: Network install

Il lun, 2004-01-12 alle 00:48, Carlos Eduardo Coelho Baptista ha scritto: > Alessandro Riz wrote: > > >Hi, > > I'm trying to install debian ppc from internet, at home I've an adsl > >connection (I use pppoe), but I've a dynamic ip, during the installation > >it tell me to configure the network but

Re: Network install

Alessandro Riz wrote: Hi, I'm trying to install debian ppc from internet, at home I've an adsl connection (I use pppoe), but I've a dynamic ip, during the installation it tell me to configure the network but what ip should I use? If I leave it blank it doesn't connect to internet! Somebody has a

Network install

Hi, I'm trying to install debian ppc from internet, at home I've an adsl connection (I use pppoe), but I've a dynamic ip, during the installation it tell me to configure the network but what ip should I use? If I leave it blank it doesn't connect to internet! Somebody has already try to do this?

Re: PowerPC CHRP network install

On Wed, Oct 22, 2003 at 11:20:18AM -0500, Rolf Brudeseth wrote: > > > > > > On Wed, Oct 22, 2003 at 10:18:26AM -0500, Rolf Brudeseth wrote: > > > > > > > > > > > > > > > > On Tue, Oct 21, 2003 at 11:26:04PM +0200, Gaudenz Steinlin wrote: > > > > > Am Die, den 21.10.2003 schrieb Rolf Brudeseth u

Re: PowerPC CHRP network install

> On Wed, Oct 22, 2003 at 10:18:26AM -0500, Rolf Brudeseth wrote: > > > > > > > > > > > On Tue, Oct 21, 2003 at 11:26:04PM +0200, Gaudenz Steinlin wrote: > > > > Am Die, den 21.10.2003 schrieb Rolf Brudeseth um 22:08: > > > > > > > > > > > > > > > On a PowerPC CHRP system, with the boot-floppie

Re: PowerPC CHRP network install

Chris Tillman wrote: > Actually, it's very difficult to use the current CD image without a > CD. It makes the assumption that the CD is there, and the last time I > tried, I couldn't fool it into thinking the hard disk was where it > wanted to look. We need to have options available for mirrors on

Re: PowerPC CHRP network install

On Wed, Oct 22, 2003 at 10:18:26AM -0500, Rolf Brudeseth wrote: > > > > > > On Tue, Oct 21, 2003 at 11:26:04PM +0200, Gaudenz Steinlin wrote: > > > Am Die, den 21.10.2003 schrieb Rolf Brudeseth um 22:08: > > > > > > > > > > > > On a PowerPC CHRP system, with the boot-floppies installer, I was >

Re: PowerPC CHRP network install

> On Tue, Oct 21, 2003 at 11:26:04PM +0200, Gaudenz Steinlin wrote: > > Am Die, den 21.10.2003 schrieb Rolf Brudeseth um 22:08: > > > > > > > > > On a PowerPC CHRP system, with the boot-floppies installer, I was able > > > to boot the zImage through BOOTP and load the initrd with NFS, and boot

Re: PowerPC CHRP network install

On Tue, Oct 21, 2003 at 11:26:04PM +0200, Gaudenz Steinlin wrote: > Am Die, den 21.10.2003 schrieb Rolf Brudeseth um 22:08: > > > > > > I downloaded the debian-installer via cvs and read the documentation. It > > appears to indicate that there are two supported netinst methods; however, > > both

Re: PowerPC CHRP network install

Am Die, den 21.10.2003 schrieb Rolf Brudeseth um 22:08: > > > I downloaded the debian-installer via cvs and read the documentation. It > appears to indicate that there are two supported netinst methods; however, > both require a CD? No, you dont' need to burn the image on a CD. > > On a PowerPC

PowerPC CHRP network install

I downloaded the debian-installer via cvs and read the documentation. It appears to indicate that there are two supported netinst methods; however, both require a CD? On a PowerPC CHRP system, with the boot-floppies installer, I was able to boot the zImage through BOOTP and load the initrd wit

Re: Network Install won't connect

Hello Colin Am 14-Jul-02 schrieb Colin Foran: > Nope, looks good. eth0 and loopback only. Ive got a few more ideas to try > out, ill post my results either later tonight or early tomarrow. Ive got a > sneaking suspicion that ive miss something painfully obvious, im going to > check it out now. I

Re: Network Install won't connect

Nope, looks good. eth0 and loopback only. Ive got a few more ideas to try out, ill post my results either later tonight or early tomarrow. Ive got a sneaking suspicion that ive miss something painfully obvious, im going to check it out now. I cant thank you enough for sticking with this though, tha

Re: Network Install won't connect

I remember that when I installed my Debian, a few weeks ago, I had some kind of trouble with a non-existent interface, which appeared nonetheless in ifconfig, and that messed up my configuration. Is it possible you'd have the same problem ? you can check on that by just doing an "ifconfig". I think

Re: Network Install won't connect

well you know, once you manage to get through ATT's gateway you're able to access the DNS servers, which should resolve the names for you. But I'm not sure I understood your previous message; have you been able to ping the gateway, or establish some kind of communication with anything ? I think the

Re: Network Install won't connect

Just a quick one: Would it be possible to supply the ip address to the debian site in the arp list ? once the system is sort of installed i mean. It seems as though i could just pick most of the things i needed it it were possible. -Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su

Re: Network Install won't connect

Hey guys. Well i punched in different addressing information during the install, and i suppose we have gotten somewhere. Everything i used came off of the mac OS 9.1 tcp/ip control pannel. So now instead of timing out when attempting to contact the debian ftp site, i get a "hostname could not be re

Re: Network Install won't connect

As for me, nothing much, sorry ! I was going to suggest doing what you've just done, so if it doesn't work I am quite puzzled, especially since it worked on the MacOs. One caveat though : it is likely that the IP address that it gives to your RedHat machine is linked (by your provider) to the Ether

Re: Network Install won't connect

Well i've tried a new method of manually configureing the network during installation, using only numbers i know to be good. (from this machine, bothing use the same modem, etc) and that just gets me to the same spot i was before. Im willing to try get myself to believe that this is one of my own

Re: Network Install won't connect

Yeah, you hit the nail on the head. Right now, untill everything gets together, im just switching the cable back and forth between machines. But AT&T allows up to three different machines per account. i figured id do an ip masquerade setup, but that wont be untill i know i can get the debian machin

Re: Network Install won't connect

On Fri, 2002-07-12 at 16:08, Laurent Steffan wrote: > Hello again, > > -- > Reçu de Colin Foran le 11/07/02 à 3:11 > > >> BTW, where did you get your other "default gateway" id (66.31.248.1) ? > > > >I've got another machine running RedHat (this one). I had figured that > sice we > >really had no

Re: Network Install won't connect

Hello again, -- Reçu de Colin Foran le 11/07/02 à 3:11 >> BTW, where did you get your other "default gateway" id (66.31.248.1) ? > >I've got another machine running RedHat (this one). I had figured that sice we >really had no idea what was going on with the mac, it might prove wiser >to use a >va

Re: Network Install won't connect

Laurent Steffan wrote: > I see two ways out of this : > > 1) you can reboot your Linux machine, note all initialization performed > ... > > 2) or, you can reboot with Mac OS 9, go to the TCP/IP Control Panel, note > ... Assuming that the ifconfig output is at least partially correct, it might b

Re: Network Install won't connect

> BTW, where did you get your other "default gateway" id (66.31.248.1) ? I've got another machine running RedHat (this one). I had figured that sice we really had no idea what was going on with the mac, it might prove wiser to use a valid address. In hindsight though, that doesnt really sound too

Re: Network Install won't connect

(Follow-up to my previous message) ATT Broadband does indeed provide the unusual subnet mask that I talked about, so my doubts about this specific point were not founded. Bye, LMS == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant

Re: Network Install won't connect

The information you get from ifconfig does not seem very coherent to me either. Josh already mentioned the incoherence about the broadcast address, and with the full addresses we see that it goes farther. The subnet mask, although unusual, is legal, and might have been selected by your ISP. Howeve

Re: Network Install won't connect

> > > Also, I have to say -- there is something very odd with the formatting > of that output. Yes, im copying off of the screen next to me. But i checked and rechecked, everys correct > > > eth0 Link encap:Ethernet HWaddr 00:90:27:B4:1A:8A > inet addr:10.1.0.101 Bcast:10.1.0.255

Re: Network Install won't connect

On Jul 11 2002, Colin Foran wrote: > Sorry guys. Im trying to install on a stock 9500, OSX wont be on > there anytime soon ; ) Why not? I did that last week... Check XPostFacto, if you don't believe me. > Link encap: Ethernet HWaddr: *** You don't gain anything co

Re: Network Install won't connect

Colin Foran <[EMAIL PROTECTED]> writes: > The ifconfig output: > Link encap: Ethernet HWaddr: *** > inet addr:24.218.255.40bcast:255.255.255.255mask:255.255.248.0 > UP BROADCAST RUNNING MTU 1500 Metric 1 > RX pakets:6 errors:3 dopped:0 frame 3 > TX packets: 3 errors:0 dr

Re: Network Install won't connect

> Sorry guys. Im trying to install on a stock 9500, OSX wont be on there anytime soon ; ) The ifconfig output: Link encap: Ethernet HWaddr: *** inet addr:24.218.255.40bcast:255.255.255.255mask:255.255.248.0 UP BR

Re: Network Install won't connect

Colin Foran <[EMAIL PROTECTED]> writes: > I tried it a few more times, but each time i get: > eth0: Host name lookup failure > > I'll read up on route a bit more tonight. the correct syntax for adding a default route is this: route add default gw dev Hope that helps, but you really need to po

Re: Network Install won't connect

On Thu, Jul 11, 2002 at 01:27:06PM +0200, Manuel Reiter wrote: > If you post the full output of '/sbin/ifconfig eth0' and '/sbin/route -n' > we might find a solution. > > If you have networking up and running under MacOS, can you access the > network parameters there and compare the gateway addres

Re: Network Install won't connect

Manuel Reiter wrote: If you have networking up and running under MacOS, can you access the network parameters there and compare the gateway addresses? (Sorry, don't know where to find these in MacOs, but I'm sure they're there.) MacOS X is very UNIX-like, so, ifconfig is available on it as well

Re: Network Install won't connect

> > If you have networking up and running under MacOS, can you access the > > network parameters there and compare the gateway addresses? (Sorry, don't > > know where to find these in MacOs, but I'm sure they're there.) > > MacOS X is very UNIX-like, so, ifconfig is available on it as well. Open

Re: Network Install won't connect

Hi, > > DestinationGatewayGenmaskFlagsMetric > > RefUseIFace > > 24.128.224.0*blahU > > blahblahblaheth0 > > default24.218.224.10.0.0.0 > > UG

Re: Network Install won't connect

Hi Colin, > Yes, i do. i was just about to sent you an email saying no, but after about 2 > 1/2 minutes the second line showed up. That was because route tried to lookup your gateways name and failed. 'route -n' should be faster. > DestinationGatewayGenmaskFlagsMe

Re: Network Install won't connect

> > > I suspect that you don't have a default route set. I realize that you > had problems with the command I suggested: > > route add default gw dev eth0 > > But it may be worth another try. I tried it a few more times, but each time i get: eth0: Host name lookup failure I'll read up on route

Re: Network Install won't connect

On Wednesday 10 July 2002 07:59 pm, Colin Foran wrote: > john: > do you know any way i could manualy change this? ifconfig mabey? > > -Cheers You can try doing the /sbin/route del default and /sbin/route add default gw eth0. I don't have much experience with the exact syntax, but if you have ac

Re: Network Install won't connect

john: do you know any way i could manualy change this? ifconfig mabey? -Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Network Install won't connect

On Wednesday 10 July 2002 04:28 pm, Colin Foran wrote: > John: > Yes, i do. i was just about to sent you an email saying no, but after > about 2 1/2 minutes the second line showed up. > > DestinationGatewayGenmaskFlagsMetric > RefUseIFace > 24.128.224

Re: Network Install won't connect

John: Yes, i do. i was just about to sent you an email saying no, but after about 2 1/2 minutes the second line showed up. DestinationGatewayGenmaskFlagsMetric RefUseIFace 24.128.224.0*blahU blah

Re: Network Install won't connect

On Wednesday 10 July 2002 03:49 pm, Colin Foran wrote: > > Do you have a default route? > > Sorry ? As root, type this: /sbin/route As an example, here is mine: [EMAIL PROTECTED]:~$ /sbin/route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Ifac

Re: Network Install won't connect

> > Do you have a default route? > Sorry ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Network Install won't connect

> > > route add default gw dev eth0 ..snip.. Ill give it a shot again. Im heading out for a short while, but im a night owl, so ill post my luck tonight. > > I know that this may sound absurd, but you could try and do a base > install with a modem and once you have something working, then switch

Re: Network Install won't connect

On Wednesday 10 July 2002 02:28 pm, Colin Foran wrote: > After taking another shot, i cant ping either of two nameservers. > I really have no idea what configuration files to look at on a debian > base install, does anyone know of anything that might be tripping up > the connection to the name reso

Re: Network Install won't connect

Colin Foran <[EMAIL PROTECTED]> writes: > After taking another shot, i cant ping either of two nameservers. I > really have no idea what configuration files to look at on a debian > base install, does anyone know of anything that might be tripping up > the connection to the name resolution server

Re: Network Install won't connect

On Wed, 2002-07-10 at 22:28, Colin Foran wrote: > After taking another shot, i cant ping either of two nameservers. > I really have no idea what configuration files to look at on a debian base > install, does anyone know of anything that might be tripping up the > connection to the name resolution

Re: Network Install won't connect

After taking another shot, i cant ping either of two nameservers. I really have no idea what configuration files to look at on a debian base install, does anyone know of anything that might be tripping up the connection to the name resolution servers? Thanks again -Cheers -- To UNSUBSCRIBE, ema

Re: Network Install won't connect

> > > Have you checked a known-good CD in your drive? Does it work under > MacOS? If so, it could _still_ be a SCSI cabling problem; its not > guaranteed that MacOS drives the SCSI bus at the same speed as Linux > does. I was going to say the drive was fine, but after you mention it i did get a lo

Re: Network Install won't connect

On 9 Jul, this message from Michel Dänzer echoed through cyberspace: > On Tue, 2002-07-09 at 22:49, Colin Foran wrote: >> > >> > >> > sorry I lost the beginning of the thread but check >> > >> > cat /proc/sys/net/ipv4/icmp_echo_ignore_all >> > >> > which has to be '1' for successful ping.

Re: Network Install won't connect

On 9 Jul, this message from Colin Foran echoed through cyberspace: > One of my devout mac friends brought up an interesting point. the PRAM > batterie on > this machine is shot, could that somehow be corrupting my scsi cdrom reads? No. The empty PROM battery will make your hardware clock reset

Re: Network Install won't connect

On 9 Jul, this message from Colin Foran echoed through cyberspace: >> And finally what does /sbin/route report? > > DestinationGatewayGenmaskFlagsMetric > RefUseIface > 24.218.224.0* 255.255.248.0 U > OO

Re: Network Install won't connect

On Jul 09 2002, Cesar Cardoso wrote: > Is the Ethernet card of the 9500 a Tulip one? No, it's a mace on-board card. I still suspect of (in)correct configuration in this case. I'd recommend the original poster some lower level analysis, like seeing if he can ping hi

Re: Network Install won't connect

> > I thought of this because my 5500 has a Tulip built-in card on it, and > the Linux Tulip driver is b0rked big time, works for a minute or two > then stops. I dont have any idea what this could be anymore. Ive scoured usenet, no one seems to have had this problem. Id rather get away with not h

Re: Network Install won't connect

Em Qua, 2002-07-10 às 14:48, Colin escreveu: > > > > > > Is the Ethernet card of the 9500 a Tulip one? > > > > Im really not sure, im using the built in ethernet port. Im assuming the > driver > is working though, dhcp was able to configure my network fine I thought of this because my 5500 has a

Re: Network Install won't connect

> > > Is the Ethernet card of the 9500 a Tulip one? > Im really not sure, im using the built in ethernet port. Im assuming the driver is working though, dhcp was able to configure my network fine -Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Con

Re: Network Install won't connect

On Tue, 2002-07-09 at 15:38, Scott Patterson wrote: > Check your physical connection. Is the ethernet cable connected? Is the > cable good? I've been burned many times by a loose/bad connection. > Colin said the connection works good on MacOS. It looks to me like a software problem. Is the Ether

Re: Network Install won't connect

One of my devout mac friends brought up an interesting point. the PRAM batterie on this machine is shot, could that somehow be corrupting my scsi cdrom reads? none of the errors seem consistant with each other. ill get an incurable media error at one sectore one attempt, then not at the same spot

Re: Network Install won't connect

On Tue, 2002-07-09 at 22:49, Colin Foran wrote: > > > > > > sorry I lost the beginning of the thread but check > > > > cat /proc/sys/net/ipv4/icmp_echo_ignore_all > > > > which has to be '1' for successful ping. > > > > > > Well this raises an interesting problem. vi seems totally shot on th

Re: Network Install won't connect

> > > sorry I lost the beginning of the thread but check > > cat /proc/sys/net/ipv4/icmp_echo_ignore_all > > which has to be '1' for successful ping. > > Well this raises an interesting problem. vi seems totally shot on the base install, i cant delete. so i tried to replace it with an icmp_e

Re: Network Install won't connect

Hi, sorry I lost the beginning of the thread but check cat /proc/sys/net/ipv4/icmp_echo_ignore_all which has to be '1' for successful ping. HTH -- M.f.G. Georg Koss mailto: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? C

Re: Network Install won't connect

> > > When you did an 'ifconfig', did your eth0 appear to have a valid IP > address (i.e. one assigned by your ISP)? It would be strange to be able > to send/receive data from your ISP's DHCP server, but not their nameserver. > yes, its almost identical to the ip address of this computer. seems va

Re: Network Install won't connect

On Tue, Jul 09, 2002 at 02:28:12PM -0400, Colin Foran wrote: > > > > > > What does the file /etc/network/interfaces look like? > > iface eth0 inet dhcp > Mine has 2 more lines: auto lo eth0 iface lo inet loopback -- *--v- Installing Debian GNU/Linux 3.0 v--* |

Re: Network Install won't connect

Colin Foran wrote: Scott Patterson wrote: Check your physical connection. Is the ethernet cable connected? Is the cable good? I've been burned many times by a loose/bad connection Yeah, everything seems fine. It was an eBay computer, but just to test it out I surfed around a bit under the M

Re: Network Install won't connect

Scott Patterson wrote: > Check your physical connection. Is the ethernet cable connected? Is the > cable good? I've been burned many times by a loose/bad connection Yeah, everything seems fine. It was an eBay computer, but just to test it out I surfed around a bit under the Mac OS. No problems on

Re: Network Install won't connect

Check your physical connection. Is the ethernet cable connected? Is the cable good? I've been burned many times by a loose/bad connection. Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Network Install won't connect

> > > What does the file /etc/network/interfaces look like? iface eth0 inet dhcp > > Also what does /sbin/ifconfig report? etholink encap:Ethernet HWaddr **mac address** inet addr: **ip address** bcase **mask** UP BROADCAST RUNNING MTU: 1500 Metric:1 RX pa

Re: Network Install won't connect

> > > Probably your nameserver information in /etc/resolv.conf is incorrect. > Can you ping your nameservers? The ip addresses in resolv.conf are correct, but when i ping them i get 100% packet loss. 100% recieved when i ping localhost though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wit

Re: Network Install won't connect

On Tue, 2002-07-09 at 12:08, Colin Foran wrote: > Hey guys. I've got my 9500 connected to the internet now, but none of the > packages can connect. I've booted into Mac OS 9.1, and the connection is > valid, > was was able to open web pages with Netscape Explorer. > But whenever I run base-config,

Network Install won't connect

Hey guys. I've got my 9500 connected to the internet now, but none of the packages can connect. I've booted into Mac OS 9.1, and the connection is valid, was was able to open web pages with Netscape Explorer. But whenever I run base-config, i get timed out. this has happened with both http and ftp,

Re: debian network install via PCMCIA?

a generic error >: when I try to start the PCMCIA software for a network install. I also >: get the same error when using the debian ramdisk.img.gz file as the >: ramdisk. what about using your linuxppc2k vmlinux as BootX kernel, copying all modules, System.map + pcmcia/config.opts to th

Re: debian network install via PCMCIA?

: when I try to start the PCMCIA software for a network install. I also >: get the same error when using the debian ramdisk.img.gz file as the >: ramdisk. >: what about using your linuxppc2k vmlinux as BootX kernel, copying all modules, System.map + pcmcia/config

debian network install via PCMCIA?

linux file as the BootX kernel and root.bin as ramdisk (both from the potato powermac subdir). But I get a generic error when I try to start the PCMCIA software for a network install. I also get the same error when using the debian ramdisk.img.gz file as the ramdisk. I decided to complete t

Re: network install problems on 7200/90

At 01:29 AM 4/3/2001, Peter Cordes wrote: On Mon, Apr 02, 2001 at 11:33:29AM -0700, Peter Canning wrote: It seems to me that it can't be the kernel that is at fault, since it works fine configured statically, or using dhcpcd. It seems to me that dhcpcd must being doing something different th

Re: network install problems on 7200/90

This is the problem which I mistakenly labeled as "the MACE driver being completely broken". And since I last tried using it, I speculated that pump was the culprit. Now I'm glad someone confirmed it. The problem does indeed exist in kernel 2.4.2. Adam On Mon, Apr 02, 2001 at 11:33:29AM -0700,

Re: network install problems on 7200/90

On Mon, Apr 02, 2001 at 11:33:29AM -0700, Peter Canning wrote: > It seems to me that it can't be the kernel that is at fault, since it works > fine configured statically, or using dhcpcd. It seems to me that dhcpcd > must being doing something different than pump. My personal preference > woul

Re: network install problems on 7200/90

My experience (using a PowerMac 7300) is a mixture of these two experiences. What I have seen, using a 2.2.18 kernel I built myself, is: (1) if I configure /etc/network/interfaces to use a static IP address, networking works great, (2) if I use dhcpcd (I have to get the deb from potato since its

Re: network install problems on 7200/90

On Sat, Mar 24, 2001 at 06:50:05PM -0500, Adam Goode wrote: > Yes, I have had this problem. The short answer is: MACE is completely > broken in recent 2.2 and 2.4 kernels. It seems to be able to send 1-2 > packets before failing with "lost a status word". These few initial > packets allow DHCP to w

Re: network install problems on 7200/90

MACE seems to work "fine" on all my old worlds: 7200/75, 7600/200, 8500/200MP. 2.2.18pre21 and 2.2.17. I'm using the TP port. a Adam Goode wrote: > > Yes, I have had this problem. The short answer is: MACE is completely > broken in recent 2.2 and 2.4 kernels. It seems to be able to send 1-2 >

Re: network install problems on 7200/90

Yes, I have had this problem. The short answer is: MACE is completely broken in recent 2.2 and 2.4 kernels. It seems to be able to send 1-2 packets before failing with "lost a status word". These few initial packets allow DHCP to work ok, while everything else fails. I don't know how to fix it, al

network install problems on 7200/90

Hi all! I'm trying to install Debian on my 7200/90. After getting a boot-floppy that recognized my keyboard (2.2.19, 2000-11-22), I was able to boot into the install program. Now I wan't to get the drivers/modules from the network. eth0 (MACE) is configured ok and the default route is ok, but I'm