Reply
 
Thread Tools Display Modes
  #1  
Old 05-03-2011, 09:54 PM
byt3s byt3s is offline
Junior Member
 
Join Date: May 2011
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Unhappy PC-BSD - Ethernet - Problems -
Hello,


Yesterday I installed the latest version of PC BSD (8.2) for my old HP Compaq with an AMD64 processor with 512MB of RAM.

I am very impressed with the desktop and the audio events that trigger when certain things happen. The piano and xylophone sounds are refreshing.

Last night I successfully set up the system and was downloading packages and surfing the net. Then when I went back to the PCBSD box and logged back in I could not connect to the Internet.

I thought it may of been funny business (denial of service) or something with my hardware or router I do not understand. I went to bed and thought that the Internet connection would be back after some hours, as this was this case with FreeBSD8.2 I tried earlier in the week.

Although when I woke up and tested the system the Internet still was not accessible. I then booted up with the Linux Lucid Puppy Live CD and was able to access the Internet. I then shutdown and booted back into PC-BSD and access to the Internet was achieved. Then I made an update to PC BSD and rebooted to install the update and upon the reboot the Internet was back off.

I was reading around for solutions and am confused on how exactly to edit some of the system files in Kate, for instance, without breaking the operating system.

be free

P.S. - below is the dmesg output... I ran out of space with this post. Thanks for reading. Have an excellent day. PC BSD is awesome.

Last edited by byt3s; 05-03-2011 at 09:57 PM. Reason: needed to add more information
Reply With Quote
  #2  
Old 05-03-2011, 09:55 PM
byt3s byt3s is offline
Junior Member
 
Join Date: May 2011
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Lightbulb dmesg output for Ethernet Internet Networking help
Here is the dmesg with kernel/system info or something:

[bytes@morph3us] /home/bytes# dmesg
Copyright (c) 1992-2011 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.2-RELEASE #7: Wed Feb 16 13:33:10 PST 2011
root@build8x64.pcbsd.org:/usr/obj/usr/pcbsd-build82/fbsd-source/8.2/sys/PCBSD amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3500+ (2204.61-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x20ff2 Family = f Model = 2f Stepping = 2
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE, CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,M MX,FXSR,SSE,SSE2>
Features2=0x1<SSE3>
AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow !+,3DNow!>
AMD Features2=0x1<LAHF>
real memory = 536870912 (512 MB)
avail memory = 414240768 (395 MB)
ACPI APIC Table: <HP-CPC AWRDACPI>
ioapic0 <Version 1.1> irqs 0-23 on motherboard
Cuse4BSD v0.1.13 @ /dev/cuse
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <HP-CPC AWRDACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 1bdf0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory, RAM> at device 0.0 (no driver attached)
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
pci0: <memory, RAM> at device 0.6 (no driver attached)
pci0: <memory, RAM> at device 0.7 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci2: <ACPI PCI bus> on pcib2
vgapci0: <VGA-compatible display> mem 0xfc000000-0xfcffffff,0xe0000000-0xefffffff,0xfb000000-0xfbffffff irq 16 at device 5.0 on pci0
nvidia0: <GeForce 6150 LE> on vgapci0
vgapci0: child nvidia0 requested pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: [ITHREAD]
pci0: <memory, RAM> at device 9.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 10.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 10.1 (no driver attached)
pci0: <memory, RAM> at device 10.2 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfe02f000-0xfe02ffff at device 11.0 on pci0
ohci0: [ITHREAD]
usbus0: <OHCI (generic) USB controller> on ohci0
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0
ehci0: [ITHREAD]
usbus1: EHCI version 1.0
usbus1: <EHCI (generic) USB 2.0 controller> on ehci0
atapci0: <nVidia nForce MCP51 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 13.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <nVidia nForce MCP51 SATA300 controller> port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 20 at device 14.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
atapci2: <nVidia nForce MCP51 SATA300 controller> port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 21 at device 15.0 on pci0
atapci2: [ITHREAD]
ata4: <ATA channel 0> on atapci2
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci2
ata5: [ITHREAD]
pcib3: <ACPI PCI-PCI bridge> at device 16.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pci3: <simple comms> at device 10.0 (no driver attached)
pci0: <multimedia, HDA> at device 16.1 (no driver attached)
nfe0: <NVIDIA nForce 430 MCP13 Networking Adapter> port 0xf200-0xf207 mem 0xfe02b000-0xfe02bfff irq 23 at device 20.0 on pci0
miibus0: <MII bus> on nfe0
rlphy0: <RTL8201L 10/100 media interface> PHY 13 on miibus0
rlphy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, auto, auto-flow
nfe0: Ethernet address: 00:17:31:a6:73:20
nfe0: [FILTER]
acpi_tz0: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x73 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: cannot reserve I/O port range
powernow0: <Cool`n'Quiet K8> on cpu0
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS WARNING: Recommended minimum RAM size is 512MB; expect unstable behavior.
ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
Consider tuning vm.kmem_size and vm.kmem_size_max
in /boot/loader.conf.
ZFS filesystem version 4
ZFS storage pool version 15
Timecounter "TSC" frequency 2204610919 Hz quality 800
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <nVidia> at usbus0
uhub0: <nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <nVidia> at usbus1
uhub1: <nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
acd0: DVDR <TSSTcorpCD/DVDW TS-H552L/0614> at ata0-master UDMA33
ad4: 190782MB <Seagate ST3200827AS 3.AHH> at ata2-master UDMA100 SATA 1.5Gb/s
Root mount waiting for: usbus1 usbus0
uhub0: 8 ports with 8 removable, self powered
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
uhub1: 8 ports with 8 removable, self powered
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
(probe0:ata0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:ata0:0:0:0): CAM status: SCSI Status Error
(probe0:ata0:0:0:0): SCSI status: Check Condition
(probe0:ata0:0:0:0): SCSI sense: NOT READY asc:3a,1 (Medium not present - tray closed)
cd0 at ata0 bus 0 scbus0 target 0 lun 0
cd0: <TSSTcorp CD/DVDW TS-H552L 0614> Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
Root mount waiting for: usbus1
Trying to mount root from ufs:/dev/label/rootfs0
ugen0.2: <Kensington> at usbus0
ums0: <Kensington Kensington Ci75m Wireless Notebook Mouse, class 0/0, rev 1.10/1.12, addr 2> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen0.3: <vendor 0x058f> at usbus0
umass0: <vendor 0x058f USB Reader, class 0/0, rev 1.10/1.00, addr 3> on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0000
umass0:2:0:-1: Attached to scbus2
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: NOT READY csi:0,aa,55,40 asc:3a,0 (Medium not present)
da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
da0: <Generic USB SD Reader 1.00> Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI status: Check Condition
(probe0:umass-sim0:0:0:1): SCSI sense: NOT READY csi:0,aa,55,40 asc:3a,0 (Medium not present)
da1 at umass-sim0 bus 0 scbus2 target 0 lun 1
da1: <Generic USB CF Reader 1.01> Removable Direct Access SCSI-0 device
da1: 1.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
(probe0:umass-sim0:0:0:2): TEST UNIT READY. CDB: 0 40 0 0 0 0
(probe0:umass-sim0:0:0:2): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:2): SCSI status: Check Condition
(probe0:umass-sim0:0:0:2): SCSI sense: NOT READY csi:0,aa,55,40 asc:3a,0 (Medium not present)
da2 at umass-sim0 bus 0 scbus2 target 0 lun 2
da2: <Generic USB SM Reader 1.02> Removable Direct Access SCSI-0 device
da2: 1.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
(probe0:umass-sim0:0:0:3): TEST UNIT READY. CDB: 0 60 0 0 0 0
(probe0:umass-sim0:0:0:3): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:3): SCSI status: Check Condition
(probe0:umass-sim0:0:0:3): SCSI sense: NOT READY csi:0,aa,55,40 asc:3a,0 (Medium not present)
da3 at umass-sim0 bus 0 scbus2 target 0 lun 3
da3: <Generic USB MS Reader 1.03> Removable Direct Access SCSI-0 device
da3: 1.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
hdac0: <NVidia MCP51 High Definition Audio Controller> mem 0xfe024000-0xfe027fff irq 22 at device 16.1 on pci0
hdac0: HDA Driver Revision: 20100226_0142
hdac0: [ITHREAD]
hdac0: HDA Codec #0: Realtek ALC883
pcm0: <HDA Realtek ALC883 PCM #0 Analog> at cad 0 nid 1 on hdac0
pcm1: <HDA Realtek ALC883 PCM #1 Analog> at cad 0 nid 1 on hdac0
pcm2: <HDA Realtek ALC883 PCM #2 Digital> at cad 0 nid 1 on hdac0
Reply With Quote
  #3  
Old 05-04-2011, 02:28 PM
kmoore134's Avatar
kmoore134 kmoore134 is offline
Administrator
 
Join Date: May 2005
Location: Knoxville, TN
Posts: 2,568
Thanks: 0
Thanked 162 Times in 127 Posts
Default dmesg output for Ethernet Internet Networking help
Can you send the "dmesg" output after the network goes down? Also the
output of "ifconfig"? To save those outputs to a file:

% dmesg > dmesg.out
% ifconfig > ifconfig.out
__________________
----
Kris Moore
PC-BSD Founder
Reply With Quote
  #4  
Old 05-04-2011, 07:36 PM
byt3s byt3s is offline
Junior Member
 
Join Date: May 2011
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Thumbs up
Hi kmoore134,

The dmesg in this thread was when I could not access the Internet...does some of the data say otherwise? Please let me know.

Thank you for explaining the syntax to output those commands to a file. I copy and pasted into Kate before.

Also, won't the ifconfig give away too much info about very sensitive stuff like internal ip etc? haha

I must say again that PC-BSD is a very cool operating system. My Internet connection has been up since last night, so I have no complaints now. Thanks for the reply.
Reply With Quote
  #5  
Old 05-05-2011, 03:05 PM
kmoore134's Avatar
kmoore134 kmoore134 is offline
Administrator
 
Join Date: May 2005
Location: Knoxville, TN
Posts: 2,568
Thanks: 0
Thanked 162 Times in 127 Posts
Default PC-BSD - Ethernet - Problems -
You could hide the IP info if need be

But since that dmesg output is from after the failure, I don't see any
obvious driver errors / warning notices. If it happens again, maybe give
"dhclient <nic>" a shot as root, see if the connection comes back up
__________________
----
Kris Moore
PC-BSD Founder
Reply With Quote
  #6  
Old 05-05-2011, 08:08 PM
byt3s byt3s is offline
Junior Member
 
Join Date: May 2011
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Talking
"dhclient <nic>" -- typing this exactly, without quotes of course, will possibly connect my computer to the Internet?

Or does there need to be some parameter between the "carrots" where "nic" is?

Everything seems to be running smoothly now. I am not sure why I lost my Ethernet Internet connection as initially described at the beginning of my thread.

Thank you for your help, kmoore134.
Reply With Quote
  #7  
Old 05-06-2011, 01:26 PM
kmoore134's Avatar
kmoore134 kmoore134 is offline
Administrator
 
Join Date: May 2005
Location: Knoxville, TN
Posts: 2,568
Thanks: 0
Thanked 162 Times in 127 Posts
Default PC-BSD - Ethernet - Problems -
"dhclient" just grabs the IP address from your DHCP server again, and
sometimes fixes any hiccups you run into. Usage it like this:

# dhclient em0

Replace em0 with your ethernet device name
__________________
----
Kris Moore
PC-BSD Founder
Reply With Quote
  #8  
Old 05-20-2011, 06:26 PM
byt3s byt3s is offline
Junior Member
 
Join Date: May 2011
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Talking
Hi KMoore134 and World,

I ran into some network connection problems again unfortunately. It seems the problem can be resolved without getting too technical by rebooting until PC-BSD finds a connection to my ethernet driver thing.

From my experience, the dhclient <nic> konsole script did not work. I appreciate the tip though. It is nice to learn.

Also when I can not find a connection to the Internet my inet address, when entering ifconfig in konsole, is all zeros, as dhcp can not find an ip address.

From reading the manual on the desktop, I found a way to read a manual page on this topic in konsole. Here is some of the output from reading a man page on the konsole:

Code:
[bytes@morph3us] /home/bytes# man nfe
Formatting page, please wait...Done.
NFE(4)                 FreeBSD Kernel Interfaces Manual                 NFE(4)

NAME
     nfe — NVIDIA nForce MCP Ethernet driver

SYNOPSIS
     To compile this driver into the kernel, place the following lines in your
     kernel configuration file:

           device miibus
           device nfe

     Alternatively, to load the driver as a module at boot time, place the
     following line in loader.conf(5):

           if_nfe_load="YES"

DESCRIPTION
     The nfe driver supports PCI Ethernet adapters based on the NVIDIA nForce
     Media and Communications Processors (MCP), such as the nForce, nForce 2,
     nForce 3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77
     and MCP79 Ethernet controller chips.

I tried changing one of the configuration files in either boot or root but was not allowed to edit it. I found some more information on editing these files on some FreeBSD webpages.

My question is basically which config file should I edit and how? I am thinking that adding a line of code as mentioned in the above man page would allow my ethernet driver to automatically connect each time.

Is loader.conf(5) located in boot or root? Hope this makes since.

I really like the free and open source PC-BSD though. Very exciting.

Thank you,

#bytes
Reply With Quote
  #9  
Old 05-23-2011, 07:05 PM
kmoore134's Avatar
kmoore134 kmoore134 is offline
Administrator
 
Join Date: May 2005
Location: Knoxville, TN
Posts: 2,568
Thanks: 0
Thanked 162 Times in 127 Posts
Default PC-BSD - Ethernet - Problems -
/boot/loader.conf is the file you want to edit, but "nfe" is already
loaded by default on PC-BSD.

Most likely you want to look at the end of /etc/rc.conf and see what
ifconfig_nfe0="" is set to, it should be DHCP, but its possible that
dhclient isn't working like you said.

Do you get any error messages from the output of "dmesg" when it fails
to connect?
__________________
----
Kris Moore
PC-BSD Founder
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 10:32 AM.


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.

Copyright 2005-2010, The PC-BSD Project. PC-BSD and the PC-BSD logo are registered trademarks of iXsystems.
All other content is freely available for sharing under the terms of the Creative Commons Attribution License.