LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 07-04-2005, 09:00 PM   #1
shuuhen
Member
 
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127

Rep: Reputation: 20
Debian 3.1 dhcp success then failure


So I'm trying to net-install Debian 3.1 r0a (Sarge) on a StarMax 3000 (ppc). After figuring out which kernel and ramdisk to use with BootX, the base install goes fine and I reboot to finish the install. During the basic install from the CD my ethernet card was detected fine and everything was configured, but after the reboot it cannot find eth0. The installer seemed to install

My /etc/network/interfaces
Code:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp
When I type lspci I do find the ethernet controller listed as
Code:
0000:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
ifconfig lists the loopback interface, but nothing else. ifconfig eth0 says "eth0: error fetching interface information: Device not found"

I know this ethernet card works with Linux, because I used it with Yellow Dog Linux 3.0.1. Any ideas why it's not working?

Any help would be greatly appreciated.
 
Old 07-04-2005, 09:56 PM   #2
mjrich
Senior Member
 
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046

Rep: Reputation: 45
Surprised it didn't work straight off -- it's quite a common chip. Have you tried
Code:
insmod r8169
ifconfig eth0 up
ifconfig
If this is works, then it may just be a matter of ensuring that the module is loaded before /etc/network/interfaces tries to bring it up.

Cheers,

mj
 
Old 07-04-2005, 10:17 PM   #3
shuuhen
Member
 
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127

Original Poster
Rep: Reputation: 20
insmod just returns with 'no module by that name found'.

/lib/modules/2.4.27-apus/kernel/drivers/net only has dummy.o, plip.o and tun.o. The part that surprised me is it worked fine when it first booted from the CD to install the minimal set of files.

I think the Debian installer decided to install the wrong kernel. It should have installed 2.4.27-powerpc, but I have 2.4.27-apus. I'm thinking if I can find a good PPC Live CD, then find the files that should have been installed, I can ftp the files from my laptop.
 
Old 07-04-2005, 11:33 PM   #4
mjrich
Senior Member
 
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046

Rep: Reputation: 45
Sounds like a plan

Let us know how you get on with installing the correct kernel.

Cheers,

mj
 
Old 07-05-2005, 12:59 AM   #5
shuuhen
Member
 
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127

Original Poster
Rep: Reputation: 20
When the installer got to partitioning, I went back which took me to the menu where you can select different install steps, execute a shell or abort install. I executed a shell (it gave me ash) so I could see what the ramdisk had for modules, etc. After I continued the install, it asked me about each step. When it got to the kernels, it let me select the kernels, so I got to pick the 2.6.8-powerpc kernel instead of the 2.4.27-apus kernel.

Even though that is working, for some reason I don't have the correct vmlinux kernel for BootX. The cd does seem to have a 2.6.8-powerpc kernel, but it insists "VFS: Cannot open root device sda2" even though the 2.4.27-powerpc kernel would open it fine. I may still need to use a Live CD, but this way to ftp something to my laptop, then ftp the file from the laptop to the partition with BootX.

Hopefully tomorrow I will have time to try the Live CD idea.
 
Old 07-05-2005, 01:58 AM   #6
mjrich
Senior Member
 
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046

Rep: Reputation: 45
Sda2 -- sounds like you might be using a Sata drive. Guess there's a slim chance that the 2.6.8-powerpc kernel is missing default support for your driver, but that does seem pretty unusual.

Good luck with the Live cd...

Cheers,

mj
 
Old 07-07-2005, 12:53 AM   #7
shuuhen
Member
 
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127

Original Poster
Rep: Reputation: 20
The sda drive is actually a SCSI drive. I'm starting to wonder if there are issues with the 2.6 kernel and BootX.

So far the Live CD is not working. Ubuntu Live CD; boots, but doesn't seem to have a way of getting to anything other than the ash shell that was also on the Debian disc.
 
Old 07-09-2005, 01:37 PM   #8
shuuhen
Member
 
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127

Original Poster
Rep: Reputation: 20
Well, now the NIC is recognized and the correct module is loaded. I went through the install again but after it finished the base install, I executed a shell and copied the modules the install disc uses when it boots to the target disk's modules directory.

Right now the net install is running. So far the only issue I had was the first FTP server I tried wasn't found.
 
Old 07-09-2005, 07:14 PM   #9
mjrich
Senior Member
 
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046

Rep: Reputation: 45
Great news !

Cheers,

mj
 
Old 07-09-2005, 08:32 PM   #10
zero79
Member
 
Registered: Nov 2003
Location: Ohio
Distribution: Debian Unstable
Posts: 460

Rep: Reputation: 30
you should submit this as a bug report against the discover1-data package using reportbug. i had a similar problem during sarge's testing phase. the issue was that the stage 1 installer was not loading the kernel module for my 1394 controller. so i had a different enumeration of my network interfaces during stage 1 and stage 2, which broke networking during stage 2 (because the installer assumes that this enumeration does not change) even though there was not a problem with my network card per se. something similar could be going on with your system. give them the output of "lspci" and "lspci -n". the developers added loading of the firewire kernel module for my 1394 controller, and the installer works flawlessly now.

you can check out my bug report here (i'd say start looking at the end first because in my original reports, i had no idea what the problem was) http://bugs.debian.org/cgi-bin/bugre...22&archive=yes

Last edited by zero79; 07-09-2005 at 09:01 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Compilation Failure success Rate 1500% drache777 Linux - Newbie 8 01-13-2005 07:41 PM
eMachines M5310: Success and failure QuatMosk Linux - Laptop and Netbook 0 12-29-2004 03:27 PM
DHCP failure at startup subversivesoul Linux - Networking 1 01-27-2004 02:14 AM
mysterious dhcp failure ev64 Linux - Networking 6 08-26-2003 12:18 AM
M$ .Net - Success or Failure X11 General 15 05-28-2002 01:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 02:20 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration