Re: HP NC373i unsupported..?
The nic is running fine so far. Is there a test scenario to run to validate that it's really production-stable ? Bert-Jan wrote: Replying to my own question.. I found the B0 version of this adapter is intentionally disabled in the driver. I've commented out the case that catches the 5708_B0 and I'm recompiling the kernel. As this server has run for years without problems I'm hoping the nic will work just fine. Maybe it's disabled because someone else had problems with it that I'm about to run into.. Will keep you posted... Bert-Jan wrote: Hi folks, I just got a HP Proliant DL380 G5 and I've installed FreeBSD 8.0 on it. The nic won't come up however. dmesg shows: bce0: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce0: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 bce1: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xfa00-0xfbff irq 17 at device 0.0 on pci5 bce1: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 pciconf -lv: b...@pci0:3:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet b...@pci0:5:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet Is there a way to fix this ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HP NC373i unsupported..?
Replying to my own question.. I found the B0 version of this adapter is intentionally disabled in the driver. I've commented out the case that catches the 5708_B0 and I'm recompiling the kernel. As this server has run for years without problems I'm hoping the nic will work just fine. Maybe it's disabled because someone else had problems with it that I'm about to run into.. Will keep you posted... Bert-Jan wrote: Hi folks, I just got a HP Proliant DL380 G5 and I've installed FreeBSD 8.0 on it. The nic won't come up however. dmesg shows: bce0: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce0: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 bce1: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xfa00-0xfbff irq 17 at device 0.0 on pci5 bce1: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 pciconf -lv: b...@pci0:3:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet b...@pci0:5:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet Is there a way to fix this ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
HP NC373i unsupported..?
Hi folks, I just got a HP Proliant DL380 G5 and I've installed FreeBSD 8.0 on it. The nic won't come up however. dmesg shows: bce0: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xf800-0xf9ff irq 16 at device 0.0 on pci3 bce0: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 bce1: HP NC373i Multifunction Gigabit Server Adapter (B0) mem 0xfa00-0xfbff irq 17 at device 0.0 on pci5 bce1: /usr/src/sys/dev/bce/if_bce.c(836): Unsupported controller revision (B0)! device_attach: bce0 attach returned 19 pciconf -lv: b...@pci0:3:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet b...@pci0:5:0:0:class=0x02 card=0x7038103c chip=0x164c14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class = network subclass = ethernet Is there a way to fix this ? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Atom 330 testing
I have this exact same board, also updated the bios after some bootup trouble, and found that the onboard nic isn't supported until 7.1. Indeed it can cause trouble on older kernels because I couldn't get 7.0-release up and running properly. Luckily 7.1-RC2 was released the day after I got the board and that went up just fine. Ever since then I've had it running my home fileserver with 2x1.5TB seagate disks with gmirror and 2GB ram without problems. Warren Block schreef: Testing a mini-ITX Intel D945GCLF2 motherboard with Atom 330 processor. The 330 is the dual-core HTT version of the Atom 270 found in all the netbooks. Shows up as four processors on FreeBSD. The board has SATA, IDE, PCI, onboard video, and Realtek 8111C Ethernet. This board was shaky until I updated the BIOS from version 99 to version 150. Yay Intel for providing a bootable ISO ROM update image! It still has two major issues: 1. Get to the FreeBSD loader prompt and type a few commands. Just ? once or twice, for example. It locks up in the middle of output or the screen goes black. A hardware reset works. 2. It shuts itself off while the kernel is starting, usually just after Starting network. Disabling the onboard Realtek 8111C seems to fix this. Note that it does sometimes manage to boot with re0 enabled. Works fine after that, including network. An xubuntu 8.10 liveCD also shuts off during boot. I haven't tried other OSes. After it has turned itself off, keyboard numlock LED remains on, power and reset buttons do nothing. AC power has to be turned off or disconnected to clear it and let it start up again. Right now it has -current, although the problems seem the same as with 7-stable. I can try debugging or tests if problem #1 permits. This board would make a very nice low-power server if it could boot reliably. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: unable to logon after updating ports collection - Freebsd 7.1 stable
Roy Stuivenberg roys1...@gmail.com writes: After I completed my Freebsd 7.1 stable, and updated all the ports, I got prompted with another logonscreen. Whatever I try, I can't login with my useraccount and even not logon as root. This happened severall times now, the only way was to reinstall everything, and I was hoping to resolve this by completly finish upgrading the ports. And .. again the same problem. I'm really hoping to get some answers that will solve this problem, maybe someone had to deal with this issue before ?? I will not give up, because Freebsd stole my heart. The problem has nothing to do with ports. To restore your root/user logins: . boot into single user mode; . set a new root password; . set a new user password; . boot into multiuser mode; . login and have fun. WBR -- bsam ___ I've had the same thing happen to me not 2 weeks ago after upgrading a server from 7.0-RC2 to 7.1-RELEASE with freebsd-update. For me the problem had nothing to do with ports but with the update itself, because it replaced my pwd.db and spwd.db with the default ones (root with no password, no user accounts) and since ssh doesn't accept root logins I ended up going to the datacenter and copying the backups of those db's back. Then everything was fine again. Very strange they got replaced though.. Sounds like you've had something similar happen to you. Hopefully your machine isn't too far away. Bert-Jan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Login accounts don't work after update to 7.1
Bert-Jan i...@bert-jan.com writes: Hi Folks, I just updated one of my servers from 7.0-RC1 to 7.1-RELEASE. During the first freebsd-update install, before rebooting, I was surprised to find that it was going to change my /etc/passwd (deleting all my accounts, keeping only the built-in accounts) and /etc/pwd.db and /etc/spwd.db. I was quite suspicious so I made copies of them. freebsd-update should merge master.passwd, and re-generate all of those files from there. What did you do with master.passwd? I didn't do anything with it. I didn't know about it (linux experience talking here, only been using freebsd for a year or so). Now that I'm looking at it all the accounts are there, so it was successfully merged indeed. Note that backup copies of master.passwd are kept in /var/backup. None of the other files, because they're generated from there. After rebooting the machine came back online perfectly. I checked /etc/passwd but there were no changes yet. Then, as the docs says, I ran freebsd-update install again and it took quite a while. *Then* my /etc/passwd was changed, so I replaced it with the spare copy I made. Of That spare copy doesn't help at all; /etc/passwd is only there as a convenience to users, and isn't consulted by the system for anything. I noticed, but after logging out as root unfortunately. course I had to test it now so I exitted from root back to my own account, and you guessed it: I can't su anymore: $ su - su: who are you? I started up a second session and found my own account doesn't work anymore either. So all I have now is an open session with my own account. I should probably also have copied the two db files back and of course I should have left my running root session open and started another one. Not a very bright moment.. Does the root account itself have a password? If you installed a generic password file, it may be unprotected, and you could log in (but not su, as that requires you first be logged in as a wheel user, of which you may have none left) as root without a password if you have a local terminal (a serial console, for example), and fix things from there. Yes, root has a password. The account I was still logged in with is a wheel user but trying a second session showed I couldn't login with that account anymore either. I really made a mess of it :) Is there a way I can recover the server from this ? Of course I can put in a cd and change some passwords, but the server is in a datacenter and I don't really have the time to go there and fix it. I'm looking for a remote solution. I guess you don't have any out-of-band access to the machine, then. You may be stuck with having to go to it physically, then. Yes, I have been there the day before yesterday, the same day I screwed it up. I logged in as root and didn't even get a password prompt. It was obviously reset to the default password database. I fixed the logins by copying the backups I made of /etc/pwd.db and /etc/spwd.db back. Everything returned to normal. It reminded me that freebsd-update had told me it wanted to change things in both those files, but since they're binary it didn't show me a diff. My error thus was that I logged out as root before restoring those. Very nasty, having to drive to the datacenter (about 100km from my home) just to copy two files. But now I know for sure this won't happen to me again :) I do find it strange though, that freebsd-update replaced those files, even though it tells you it's going to change them. What is the proper way to handle this ? Can I run a command after the update finishes that regenerates the account databases from the master.passwd ? I checked the history and *I* never touched it during the update, so it was merged like it should. It's probably not much help but there's one jail running on it that's still working fine. I can login and su on that one, but I don't know if I can use it to repair the main system. I sure hope that won't help. That would defeat the point of jails, wouldn't it? ;-) Yes indeed ;) Thanks for the explanations. I still have a lot to learn of freebsd, having been a Slackware Linux user for about 7 years, I've started my first freebsd server about a year ago. So far I like it very much. Keeping the whole system updated with freebsd-update and the whole ports system is just a breeze. Sometimes like this things get screwed up, but the same has happened to me several times with Linux, so no hard feelings :) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Login accounts don't work after update to 7.1
Hi Folks, I just updated one of my servers from 7.0-RC1 to 7.1-RELEASE. During the first freebsd-update install, before rebooting, I was surprised to find that it was going to change my /etc/passwd (deleting all my accounts, keeping only the built-in accounts) and /etc/pwd.db and /etc/spwd.db. I was quite suspicious so I made copies of them. After rebooting the machine came back online perfectly. I checked /etc/passwd but there were no changes yet. Then, as the docs says, I ran freebsd-update install again and it took quite a while. *Then* my /etc/passwd was changed, so I replaced it with the spare copy I made. Of course I had to test it now so I exitted from root back to my own account, and you guessed it: I can't su anymore: $ su - su: who are you? I started up a second session and found my own account doesn't work anymore either. So all I have now is an open session with my own account. I should probably also have copied the two db files back and of course I should have left my running root session open and started another one. Not a very bright moment.. Is there a way I can recover the server from this ? Of course I can put in a cd and change some passwords, but the server is in a datacenter and I don't really have the time to go there and fix it. I'm looking for a remote solution. It's probably not much help but there's one jail running on it that's still working fine. I can login and su on that one, but I don't know if I can use it to repair the main system. Please, help ! Thanks, Bert-Jan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
