problems with kernel 2.6.3 and bcm4400 module
Hello, Im new here, and i have a little problem; firs of all, sorry for my english.
Ive recently installed Gentoo 2004.0, but i've had some problems. I installed kernel 2.4.22 and almost everything worked great. I cant make the ethernet work. In the installation cd i can use it, and conect to the internet, but not when i restart the So. also, theres a problem mounting a ntfs and a fat32 partitions ("wrong fs ty, bad option, bad superblock on hda1" and "hdb1") so i decied to try kernel 2.6.3. i configured it, and compiled it. but when i restart, and i select the new option in grub (3 options: linux with 2.4.22, linux with 2.6.3, and windows), it starts to boot but it gets stuck in a few seconds, just after loading the ntfs driver (with read and write suport) Please, someone could help me? Thanks! |
Change the type of support for ntfs.. Instead of builtin, go modules and vis versa. If all else fails, remove ntfs support.
|
Actually, I do need ntfs suport, I need to read (even it wold be great to write) to a ntfs partition... since its my "primary" partition and is where almost everything its located...
maybe just removing write suport or changin it to modules could work? thanks again |
Regarding the bcm44 modules, they're dodgy as all hell. You can try downloading the ones frmo the broadcom site, they're a little better, although still goddam awful.
As to the 2.6 kernel series, make sure you have module-init-tools installed if you want to use modules! You don't need this for the 2.4 / 2.5 series, but using 2.6.x, unless you have module-init-tools you can't insert modules... And recompiling the whole goddamn kernel each time you wanna change config is just a ... |
well, im not much skilled in linux, so i must do it the way i know :(
i marked the ntfs suport as module and now all works, but i keep having the same error mounting and with ethernet. I supose the mount problem is because i mut have something bad in the fstab, so here it is: ------------------------------------------------- /dev/cdroms/cdrom0 /mnt/cdrom auto auto,ro,user 0 0 /dev/cdroms/cdrom1 /mnt/cdrom2 auto auto,ro,user 0 0 /dev/hda1 /mnt/c ntfs rw,user 0 0 /dev/hda2 none swap sw 0 0 /dev/hda3 / ext3 noauto,noatime 1 1 /dev/hdb1 /mnt/d vfat rw,user 0 0 /dev/fd0 /mnt/floppy auto noauto,user 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 ------------------------------------------------- and about the bcm44. why it works fine in the instalaltion cd but not when I boot the system? here is the error : ------------------------------------------------- (...) * Bringing eth0 up... [OK] * Bringing eth1 up... SIOCSIFARDDR : no such device. eth1, unknown interface: no such device. SIOCSIFBRDADDR : no such device. eth1, unknown interface: no such device. SIOCSIFNETMASK : no such device. * Failed to bring eth1 up. (...) ------------------------------------------------- Well, the eth0 is another ethernet card, and it seems to work just fine, but my internet is throught that broadcom onbord, so i must make it work. Thanks again for all. |
I've resolved the mounting problem but I still need help with the ethernet ...
I've downloadede the bcm4401 driver for linux from the broadcom website, and ive installed it using make, insmod bcm4400.o, and make install. Everything seemded to go fine in the compilation, but after rebooting there was the same error again. I've even used emerge bcm4400 and everything gone fine. but the error again! :( thxs for helping me again.... |
OK, it sounds like you're almost there. To make sure a module gets inserted every time you boot, add the module name to the file /etc/modules. Anything listed there the kernel will try to load at start up; hopefully you're all good after this.
Also worth noting it that it's generally best practice to use modprobe, rather than insmod. Modprobe looks in /lib/modules/<kernel version>/ to find the correct module and inserts it, while insmod has to find the file from the path specified. Modprobe also loads all the modules that the module you're trying to load depends on. BUT, don't worry too much about that stuff, it's the first paragraph you need! |
yes, finally ive done it... but everytime I boot i have to load the module using modpobe, then using ifconfig eth1 ip netmask ip up to bring it up and then add a gateway usin route add default gateway.
I tryed to use a script in /etc/init.d and configure it to load via rc-update, but i dont know why, it fails. i have to do it manually :( |
If you edit the /etc/network/interfaces file and put in something like
auto eth0 iface eth0 inet static address 192.168.1.1 netmask 255.255.255.0 gateway 192.168.1.254 substituting appropriate values. If you're getting your address via dhcp, then you can just have auto eth0 iface eth0 inet dhcp 'ifup eth0 ' should then bring the interface up, and it should happen automatically on boot. |
hum... now i have another problem, now i even cant use iternet.
Sudently, i cant use the route comand, the ifconfig sais both eth0 and eth1 are up and running, here is the error: bash-2.05b# modprobe bcm4400 bash-2.05b# ifconfig eth1 213.xxx.xxx.xxx netmask 255.255.255.192 bash-2.05b# route add default gw 213.96.166.1 SIOCADDRT: Network is unreachable |
hum... now i have another problem, now i even cant use iternet.
Sudently, i cant use the route comand, the ifconfig sais both eth0 and eth1 are up and running, here is the error: bash-2.05b# modprobe bcm4400 bash-2.05b# ifconfig eth1 213.xxx.xxx.xxx netmask 255.255.255.192 bash-2.05b# route add default gw 213.96.166.1 up SIOCADDRT: Network is unreachable ------------------------------------------- "If you edit the /etc/network/interfaces file and put in something like" I dont have such file. I even have the /etc/network folder... should I create it? |
All times are GMT -5. The time now is 10:24 AM. |