Re: fxp driver - bsd.rd vs bsd
First guess is do you have /etc/mygate ? --STeve Andre' On June 24, 2014 3:47:27 PM EDT, Stefan Olsson wrote: >Hi, >My colleague is after trying to install Current onto an old Dell PC >several >times now. -She can go through the install without problem, she gets >connected >with dhcp and can download the filesets, so obviously she has network >connection. -However, after rebooting into the freshly installed system >(still >set to dhcp), the machine will just not appear on the network. -While >it was >installing it could be pinged, but as soon as it restarts into the >installed >Current, it will not reply to ping anymore, it is not accessible over >ssh and >it is impossible to connect from it as well. -"ifconfig fxp0" tells me >that >the state is active and it appears to have kept the same ip-address as >it had >when it was being installed. -Cables have been changed and it was >connected to >ports on other switches to no avail. -I was just wondering what would >be the >difference between being booted into bsd.rd vs bsd - in the latter fxp >seems >to have some kind of issue while it is working fine while in >"install-mode"?-We will work around this issue by using a different >machine, >but I am still curious, how come it works fine while installing, but >not when >it is actually installed? Any clue-sticks to hit me with? >Cheers
Re: fxp driver - bsd.rd vs bsd
Subject: Re: fxp driver - bsd.rd vs bsdFrom: andres@msu.eduDate: Tue, 24 Jun 2014 17:43:57 -0400To: stur...@hotmail.com; misc@openbsd.org First guess is do you have /etc/mygate ? --STeve Andre' -It doesn't really matter if I have mygate or not as this is on the LAN, no routing involved. It works fine to ping from other hosts on the LAN while it is installing (after getting an address from dhcp), but it doesn't reply to ping after rebooting to the *fresh* install of current.
Re: fxp driver - bsd.rd vs bsd
previously on this list Stefan Olsson contributed: > However, after rebooting into the freshly installed system (still > set to dhcp), the machine will just not appear on the network. -While it was > installing it could be pinged I don't really use DHCP but believe there are various types. On Android it bypasses the filter all together. You could make sure logging is enabled in pf.conf and see what the following shows tcpdump -n -e -ttt -i pflog0 -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___
Re: fxp driver - bsd.rd vs bsd
On Tue, Jun 24, 2014 at 03:47:27PM -0400, Stefan Olsson wrote: > Hi, > My colleague is after trying to install Current onto an old Dell PC several > times now. -She can go through the install without problem, she gets connected > with dhcp and can download the filesets, so obviously she has network > connection. -However, after rebooting into the freshly installed system (still > set to dhcp), the machine will just not appear on the network. -While it was > installing it could be pinged, but as soon as it restarts into the installed > Current, it will not reply to ping anymore, it is not accessible over ssh and > it is impossible to connect from it as well. -"ifconfig fxp0" tells me that > the state is active and it appears to have kept the same ip-address as it had > when it was being installed. -Cables have been changed and it was connected to > ports on other switches to no avail. -I was just wondering what would be the > difference between being booted into bsd.rd vs bsd - in the latter fxp seems > to have some kind of issue while it is working fine while in > "install-mode"?-We will work around this issue by using a different machine, > but I am still curious, how come it works fine while installing, but not when > it is actually installed? Any clue-sticks to hit me with? > Cheers The GENERIC kernel loads firmware patches into some fxp models. Perhaps your fxp model doesn't like that? To test this theory, try removing the call to fxp_load_ucode() in ftp_init() in the file /usr/src/sys/dev/ic/fxp.c and recompile the GENERIC kernel. If that makes it work please supply the output of pcidump -v and dmesg so a proper fix can be devised. Index: fxp.c === RCS file: /cvs/src/sys/dev/ic/fxp.c,v retrieving revision 1.115 diff -u -p -r1.115 fxp.c --- fxp.c 28 Dec 2013 03:34:59 - 1.115 +++ fxp.c 24 Jun 2014 21:06:31 - @@ -1193,7 +1193,6 @@ fxp_init(void *xsc) fxp_scb_cmd(sc, FXP_SCB_COMMAND_RU_BASE); #ifndef SMALL_KERNEL - fxp_load_ucode(sc); #endif /* Once through to set flags */ fxp_mc_setup(sc, 0);
fxp driver - bsd.rd vs bsd
Hi, My colleague is after trying to install Current onto an old Dell PC several times now. -She can go through the install without problem, she gets connected with dhcp and can download the filesets, so obviously she has network connection. -However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged, but as soon as it restarts into the installed Current, it will not reply to ping anymore, it is not accessible over ssh and it is impossible to connect from it as well. -"ifconfig fxp0" tells me that the state is active and it appears to have kept the same ip-address as it had when it was being installed. -Cables have been changed and it was connected to ports on other switches to no avail. -I was just wondering what would be the difference between being booted into bsd.rd vs bsd - in the latter fxp seems to have some kind of issue while it is working fine while in "install-mode"?-We will work around this issue by using a different machine, but I am still curious, how come it works fine while installing, but not when it is actually installed? Any clue-sticks to hit me with? Cheers
