RE: Netra X1 install problem/oddity
Good call. I found it in the initrd.img file. So I removed that module, saved, and it booted just fine with network. I am getting some errors on the TX side according to ifconfig BUT everything appears to be working fine on this box. The stats below are lying as the network interface is sending and receiving (did 1 byte pings for a couple seconds) and it but no traffic is being logged. I assume this is a driver issue and not really anything to do with the hardware but if you have any ideas of how to fix or if it's even important, please let me know. Anyway, it's working now so I'll start to play with the machines. Thanks for the help and I'm sure that I'll ask for more later debian:~# ifconfig eth1 Link encap:Ethernet HWaddr 00:03:BA:0C:38:D5 inet addr:10.0.16.113 Bcast:10.0.16.255 Mask:255.255.255.0 inet6 addr: fe80::203:baff:fe0c:38d5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:164 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:112 dropped:0 overruns:0 carrier:112 collisions:0 txqueuelen:1000 RX bytes:61864 (60.4 KiB) TX bytes:0 (0.0 b) Interrupt:9 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) > -Original Message- > From: Richard Mortimer [mailto:[EMAIL PROTECTED] > Sent: Monday, June 02, 2008 4:07 PM > To: Gary W. Smith > Cc: Steve Haavik; Martin Habets; debian-sparc@lists.debian.org > Subject: RE: Netra X1 install problem/oddity > > Hello, > > I'm working from memory here but I vaguely remember having a similar > problem some time ago. I seem to remember that the kernel module and > blacklist files are built into the initrd/initramfs files. I think that > you need to regenerate that to get the changes to work during boot. > > I cannot easily get access to my X1 at the moment so I cannot check > myself - sorry. > > Richard > > On Mon, 2008-06-02 at 07:53 -0700, Gary W. Smith wrote: > > Steve, > > > > Thanks for the follow up on this. I did the echo trick but it still > > didn't work. I also did remove dmfe.ko and then issue depmod -a to > > rebuild the catalog but it still loads the module. It seems like > this > > module is in the kernel or something. Anyway, I'll play around with > > it a little more. In a worse case scenario, I'll script something on > > startup. > > > > Gary > > > > > > > ______________ > > From: Steve Haavik [mailto:[EMAIL PROTECTED] > > Sent: Mon 6/2/2008 4:25 AM > > To: Gary W. Smith > > Cc: Martin Habets; debian-sparc@lists.debian.org > > Subject: RE: Netra X1 install problem/oddity > > > > > > I've still got a few Netra X1's running. > > From my notes: > > > > First thing after booting the tftpimage jump to a shell and: > > > > modprobe -r dmfe > > modprobe -r tulip > > modprobe tulip > > > > Then you can continue the install. > > > > After it reboots to the new system: > > > > echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist > > > > If all else fails you could track down and delete dmfe.ko but you'd > > have > > to remember to do that after every kernel upgrade. The above method > > worked > > fine on my production boxes. > > > > > > > -- > Richard Mortimer <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Netra X1 install problem/oddity
Hello, I'm working from memory here but I vaguely remember having a similar problem some time ago. I seem to remember that the kernel module and blacklist files are built into the initrd/initramfs files. I think that you need to regenerate that to get the changes to work during boot. I cannot easily get access to my X1 at the moment so I cannot check myself - sorry. Richard On Mon, 2008-06-02 at 07:53 -0700, Gary W. Smith wrote: > Steve, > > Thanks for the follow up on this. I did the echo trick but it still > didn't work. I also did remove dmfe.ko and then issue depmod -a to > rebuild the catalog but it still loads the module. It seems like this > module is in the kernel or something. Anyway, I'll play around with > it a little more. In a worse case scenario, I'll script something on > startup. > > Gary > > > __ > From: Steve Haavik [mailto:[EMAIL PROTECTED] > Sent: Mon 6/2/2008 4:25 AM > To: Gary W. Smith > Cc: Martin Habets; debian-sparc@lists.debian.org > Subject: RE: Netra X1 install problem/oddity > > > I've still got a few Netra X1's running. > From my notes: > > First thing after booting the tftpimage jump to a shell and: > > modprobe -r dmfe > modprobe -r tulip > modprobe tulip > > Then you can continue the install. > > After it reboots to the new system: > > echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist > > If all else fails you could track down and delete dmfe.ko but you'd > have > to remember to do that after every kernel upgrade. The above method > worked > fine on my production boxes. > > > -- Richard Mortimer <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Netra X1 install problem/oddity
Steve, Thanks for the follow up on this. I did the echo trick but it still didn't work. I also did remove dmfe.ko and then issue depmod -a to rebuild the catalog but it still loads the module. It seems like this module is in the kernel or something. Anyway, I'll play around with it a little more. In a worse case scenario, I'll script something on startup. Gary From: Steve Haavik [mailto:[EMAIL PROTECTED] Sent: Mon 6/2/2008 4:25 AM To: Gary W. Smith Cc: Martin Habets; debian-sparc@lists.debian.org Subject: RE: Netra X1 install problem/oddity I've still got a few Netra X1's running. >From my notes: First thing after booting the tftpimage jump to a shell and: modprobe -r dmfe modprobe -r tulip modprobe tulip Then you can continue the install. After it reboots to the new system: echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist If all else fails you could track down and delete dmfe.ko but you'd have to remember to do that after every kernel upgrade. The above method worked fine on my production boxes.
RE: Netra X1 install problem/oddity
I've still got a few Netra X1's running. From my notes: First thing after booting the tftpimage jump to a shell and: modprobe -r dmfe modprobe -r tulip modprobe tulip Then you can continue the install. After it reboots to the new system: echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist If all else fails you could track down and delete dmfe.ko but you'd have to remember to do that after every kernel upgrade. The above method worked fine on my production boxes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Netra X1 install problem/oddity
Martin, I finally have one of the Netra's up and running. I ran into a small problem though. I have the issue with dmfe walking over tulip. I followed a couple articles on how to blacklist the driver to no avail. I added dmfe to my blacklist.local and it seems to be ignored. I also created a file called dmfe-blacklist and added (both from samples) debian:/etc/modprobe.d# cat dmfe-blacklist blacklist dmfe debian:/etc/modprobe.d# cat blacklist.local blacklist dmfe I found one article that said I could disable it in the boot config under lilo, but I don't know where to begin on this. My background is with RedHat/rPath Linux using grub. Gary > -Original Message- > From: Martin Habets [mailto:[EMAIL PROTECTED] On Behalf Of > Martin Habets > Sent: Sunday, June 01, 2008 7:30 AM > To: Gary W. Smith > Cc: debian-sparc@lists.debian.org > Subject: Re: Netra X1 install problem/oddity > > I remember seeing something like this as well. Seems like a bug in > partman. > The only way I got around it is to partition the disk using fdisk. > Getting fdisk on the machine was the tricky part, it was not on my > installation > media. I put the executable on another server, and copied that over > from > the install shell. > > -- > Martin > --- > > 30 years from now GNU/Linux will be as redundant a term as MERT/UNIX is > today. - Martin Habets > --- > > > On Sat, May 31, 2008 at 04:27:57PM -0700, Gary W. Smith wrote: > > Hello, > > > > I've been working to get Debian current installed on a Netra X1 from > a > > netboot over LOM. I first encountered the problem with the tulip > driver > > (requiring me to shell out, unload dmfe/tulip and then load tulip). > As > > is well on the network front. The problem is after it downloads all > of > > the install from ftp, it comes up and states that it cannot find any > > disks and asks me to load a driver. > > > > So I shell again and I can see /dev/hda in /proc/partitions (20gb). > I > > run partman from the shell and it sees no drives. Thinking that it's > > because of the former Sun partition, I dd if=/dev/zero of=/dev/had > bs=1M > > count=1 to clear any partitions. I then run partman and it now sees > a > > 1MB disk drive. > > > > Any ideas on why this might be happening and how I can work around > it. > > I have several of these machines that I'd like to build out in the > next > > couple days for a project, but they just aren't cooperating. > > > > Gary > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Netra X1 install problem/oddity
Martin, Thanks for the follow up. I also tried this approach. I downloaded the fdisk.deb package using wget by dropping to the shell and it fails to see any partition either. I might try to pull one of the dirves, see if I can fdisk it on another system, then drop it back in and see if that works for me. Gary From: Martin Habets on behalf of Martin Habets Sent: Sun 6/1/2008 7:30 AM To: Gary W. Smith Cc: debian-sparc@lists.debian.org Subject: Re: Netra X1 install problem/oddity I remember seeing something like this as well. Seems like a bug in partman. The only way I got around it is to partition the disk using fdisk. Getting fdisk on the machine was the tricky part, it was not on my installation media. I put the executable on another server, and copied that over from the install shell. -- Martin --- 30 years from now GNU/Linux will be as redundant a term as MERT/UNIX is today. - Martin Habets --- On Sat, May 31, 2008 at 04:27:57PM -0700, Gary W. Smith wrote: > Hello, > > I've been working to get Debian current installed on a Netra X1 from a > netboot over LOM. I first encountered the problem with the tulip driver > (requiring me to shell out, unload dmfe/tulip and then load tulip). As > is well on the network front. The problem is after it downloads all of > the install from ftp, it comes up and states that it cannot find any > disks and asks me to load a driver. > > So I shell again and I can see /dev/hda in /proc/partitions (20gb). I > run partman from the shell and it sees no drives. Thinking that it's > because of the former Sun partition, I dd if=/dev/zero of=/dev/had bs=1M > count=1 to clear any partitions. I then run partman and it now sees a > 1MB disk drive. > > Any ideas on why this might be happening and how I can work around it. > I have several of these machines that I'd like to build out in the next > couple days for a project, but they just aren't cooperating. > > Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Netra X1 install problem/oddity
I remember seeing something like this as well. Seems like a bug in partman. The only way I got around it is to partition the disk using fdisk. Getting fdisk on the machine was the tricky part, it was not on my installation media. I put the executable on another server, and copied that over from the install shell. -- Martin --- 30 years from now GNU/Linux will be as redundant a term as MERT/UNIX is today. - Martin Habets --- On Sat, May 31, 2008 at 04:27:57PM -0700, Gary W. Smith wrote: > Hello, > > I've been working to get Debian current installed on a Netra X1 from a > netboot over LOM. I first encountered the problem with the tulip driver > (requiring me to shell out, unload dmfe/tulip and then load tulip). As > is well on the network front. The problem is after it downloads all of > the install from ftp, it comes up and states that it cannot find any > disks and asks me to load a driver. > > So I shell again and I can see /dev/hda in /proc/partitions (20gb). I > run partman from the shell and it sees no drives. Thinking that it's > because of the former Sun partition, I dd if=/dev/zero of=/dev/had bs=1M > count=1 to clear any partitions. I then run partman and it now sees a > 1MB disk drive. > > Any ideas on why this might be happening and how I can work around it. > I have several of these machines that I'd like to build out in the next > couple days for a project, but they just aren't cooperating. > > Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
