LinHES Forums
http://forums.linhes.org/

System freeze when ifconfig NIC on Asus Pundit
http://forums.linhes.org/viewtopic.php?f=2&t=1774		 Page 1 of 1
Author:  geekraver [ Sat Jun 19, 2004 2:16 am ]
Post subject:  System freeze when ifconfig NIC on Asus Pundit
Hi all

I was using the previous version of KnoppMyth fine on my Asus Pundit. For the past few months I've dabbled with and finally discarded SageTV (waste of money), and am now keen to try the new KnoppMyth. However, the DHCP config of the NIC fails. When I try a manual ifconfig to assign it an address, the whole OS freezes up (I get a "bcm4400: eth0 NIC Link is Up, 100Mbps full duplex" but that's it; then I'm hosed). I know the NIC is fine; it seems like this must be a breaking change in the driver (Broadcom 4401). Anyone else experienced this? What would be the least painless way of fixing this (given that I want to use KnoppMyth to avoid the pain of manually installing Myth).

thanks
Geek
Author:  cesman [ Sat Jun 19, 2004 9:22 am ]
Post subject: 
You can use the earlier version that did work then simply update to the newest debs.
Author:  verlaine [ Sun Jun 27, 2004 8:27 am ]
Post subject: 
I've got the same problem with my pundit.

Which version of knoppmyth have you installed to avoid this NIC problem ?

Thanks
Author:  cesman [ Sun Jun 27, 2004 9:47 am ]
Post subject: 
Less I'm mistaken, R4V2.
Author:  Dennis L [ Sun Jun 27, 2004 5:01 pm ]
Post subject:  Re: System freeze when ifconfig NIC on Asus Pundit
I was quite surprised to see my Pundit box hang while commencing the install of R4V4.1, and after a bit of investigation found that the "pump -i eth0" command was the root cause. (This command does the initial set up of the eth0 interface).

As I use a wireless card and do not need the broadcomm NIC, as work around I did the following.

As soon as the very firstinstall screen is presented for Knoppmyth, I hit ALT-F2 to get another screen.
1. Get the pump process id
# ps -aux
2. Kill the process
# kill -15 <process pump -i eth0 process id>

As a permanent fix, one could get the latest Broadcomm driver.

Cheers
Dennis


geekraver wrote:
Hi all

I was using the previous version of KnoppMyth fine on my Asus Pundit. For the past few months I've dabbled with and finally discarded SageTV (waste of money), and am now keen to try the new KnoppMyth. However, the DHCP config of the NIC fails. When I try a manual ifconfig to assign it an address, the whole OS freezes up (I get a "bcm4400: eth0 NIC Link is Up, 100Mbps full duplex" but that's it; then I'm hosed). I know the NIC is fine; it seems like this must be a breaking change in the driver (Broadcom 4401). Anyone else experienced this? What would be the least painless way of fixing this (given that I want to use KnoppMyth to avoid the pain of manually installing Myth).

thanks
Geek
Author:  kminder [ Fri Jul 16, 2004 9:18 pm ]
Post subject: 
I'm having this problem too and I know just enough to be dangerous. This is doubly true when it comes to mucking with kernel modules. How should one go about upgrading the broadcom drivers when the darn thing won't boot. The steps below are what I tried with the resulting error at the end. After a reboot, my system hangs at the same point as described in the other post.

I had a working system on a very old release R3 possibly so I don't have access to R4V2 iso files as was recommended by cesman. It seems like the upgrade from V2 to V4.1 was problematic anyway. Why oh why did the grabber stuff break. I miss my MythTV.

Boot using the CD.
Exit the install program. (6. Quit)
mount -w /dev/hda1 /mnt
chroot /mnt
cd /usr/src
mkdir bcm4401-linux-3-0-7
cd bcm4401-linux-3-0-7
wget http://www.broadcom.com/docs/driver_dow ... -3.0.7.zip
unzip *.zip
cd linux
tar xcvf *.gz
cd bcm4400-3.0.7
cat README.txt
cd src
make
make install

depmod: *** Unresolved symbols in /lib/modules/2.4.25-chw/kernel/arch/i386/kernel/apm.o
Author:  cesman [ Sat Jul 17, 2004 6:09 pm ]
Post subject: 
Odd that you'd get an unresolved symbol w/ apm.o. When I compiled then kernel, I got no unresolved symbols. The only things I can figure is something must have broke with bcm4400-source(which compiled ok) that I got when I made the latest releases...
Author:  kminder [ Sat Jul 17, 2004 6:23 pm ]
Post subject: 
So this should have worked then? I wasn't really sure that this was the correct approach. Anybody have any other suggestions?
Author:  cesman [ Sat Jul 17, 2004 9:27 pm ]
Post subject: 
If you've gotten the latest source from broadcom and it compiled and install ok, then you maybe ok(I don't have a Pundit). If the only problem you have is unresolved symbol w/ apm, you can ignore or remove the module. After 'make install', modprobe bcm4400 and configure. Please let me know if this works...
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/