Re: BSDInstall: merging to HEAD
On Fri, 14 Jan 2011 12:26:43 -0600 Nathan Whitehorn nwhiteh...@freebsd.org wrote: As those of you who have been reading freebsd-sysinstall and freebsd-arch know, I have been working for a few weeks on a lightweight new installer named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 release. After two weeks of testing and bug fixes on the sysinstall list, I believe this now has all required functionality and is ready to be merged into the main source tree. I would like to do this on Tuesday, 18 January. Switching this to be the default installer would happen a few weeks after that, pending discussion on release formats with the release engineering team. This should provide a sufficient testing period before 9.0 and allow a maximal number of bugs to be discovered and solved before the release is shipped. Demo ISO for i386: http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2 SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall Wiki page: http://wiki.freebsd.org/BSDInstall I installed this under VirtualBox yesterday. The only porblem I noticed was that adding a user didn't actually work, although it appeared to do so (it asked at the end of the process whether all data for the new user were correct and then claimed to have added the user). Looking at /etc/passwd and in /home after booting the new installation showed that the user was never added. Otherwise it was a smooth install, although I didn't try anything fancy and just used the quick install and the entire disk for simpicity. -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: BSDInstall: merging to HEAD
On Sun, Jan 16, 2011 at 3:06 AM, krad kra...@gmail.com wrote: On 14 January 2011 18:26, Nathan Whitehorn nwhiteh...@freebsd.org wrote: As those of you who have been reading freebsd-sysinstall and freebsd-arch know, I have been working for a few weeks on a lightweight new installer named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 release. After two weeks of testing and bug fixes on the sysinstall list, I believe this now has all required functionality and is ready to be merged into the main source tree. I would like to do this on Tuesday, 18 January. Switching this to be the default installer would happen a few weeks after that, pending discussion on release formats with the release engineering team. This should provide a sufficient testing period before 9.0 and allow a maximal number of bugs to be discovered and solved before the release is shipped. Demo ISO for i386: http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2 SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall Wiki page: http://wiki.freebsd.org/BSDInstall Goals - The primary goal of BSDInstall is to provide an easily extensible installer without the limitations of sysinstall, in order to allow more modern installations of FreeBSD. This means that it should have additional features to support modern setups, but simultaneously frees us to remove complicating features of sysinstall like making sure everything fits in floppy disk-sized chunks. New Features: - Allows installation onto GPT disks on x86 systems - Can do installations spanning multiple disks - Allows installation into jails - Eases PXE installation - Virtualization friendly: can install from a live system onto disk images - Works on PowerPC - Streamlined system installation - More flexible scripting - Easily tweakable - All install CDs are live CDs Architecture BSDInstall is a set of tools that are called in sequence by a master script. These tools are, for example, the partition editor, the thing that fetches the distributions from the network, the thing that untars them, etc. Since these are just called in sequence from a shell script, a scripted installation can easily replace them with other things, (e.g. hard-coded gpart commands), leave steps out, add new ones, or interleave additional system modifications. Status -- This provides functionality most similar to the existing sysinstall 'Express' track. It installs working, bootable systems you can ssh into immediately after reboot on i386, amd64, sparc64, powerpc, and powerpc64. There is untested support for pc98. The final architecture on which we use sysinstall, ia64, is currently unsupported, because I don't know how to set up booting on those systems -- patches to solve this are very much welcome. There are still some missing features that I would like to see in the release, but these do not significantly impact the functionality of the installer. Some will be addressed before merging to HEAD, in particular the lack of a man page for bsdinstall. Others, like configuration of wireless networking and ZFS installation, can happen between merge and release. The test ISOs are also lacking a ports tree at the moment, which is a statement about the slow upload speed of my DSL line and not about the final layout of releases. Please send any questions, comments, or patches you may have, and please be aware when replying that this email has been cross-posted to three lists. Technical discussion (bug reports, for instance) should be directed to the freebsd-sysinstall list only. Most other discussion belongs on -sysinstall and -current. I dont follow the freebsd-sysinstall and freebsd-arc list so sorry if this has already been discussed. From what I have seen pc-sysinstall already does all these things, and can install freebsd. Therefore why are we reinventing the wheel? I don't mean this as any disrespect to the work you have done. Hi Krad, I asked this two weeks ago and in summary: - pc-sysinstall is x86-centric and porting to powerpc is non-trivial, and sysinstall is incomplete on powerpc. Nate sought to get a working powerpc port with minimal effort. Please read other replies in the archives on freebsd-arch / freebsd-sysinstall to get more info as to why things have been done the way they have been done. Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current
Marek Salwerowicz wrote: It would be nice if you enabled verbose kernel messages to get more info. Verbose log in attachment - please see it. I've meant log with problem. When you are loading modules on-fly. atapci0: AMD ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 So now it works, I am able to mount partition at ad1 ;) But as this line tells - controller still identified as generic PCI ATA, as I've predicred. It means that driver won't set transfer modes, trusting BIOS to do it. At least it will probably make hot-plug impossible. I have no idea how to fix this now. -- Alexander Motin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: TCP resident expert?
On Sat, 15 Jan 2011, William Allen Simpson wrote: Who's the kernel expert on TCP around here? ISC wants me to port TCPCT to FreeBSD. Although I've joined this list (some time ago), I've not seen any traffic discussing TCP'ish things. Need somebody willing to walk me through the processes and check my code. I don't think there's any single the expert -- rather, work on TCP is distributed over a number of developers who take various interests in the topic. At the risk of pointing fingers: Lawrence Stewart lstewart@ has recently been involved in pluggable congestion control, new congestion control algorithms, TCP tracing, and various other things, and has been among our most active hands in TCP for the last year especially. He might be the best first port of call because of this recent activity. Rui Paulo rpaulo@ did our TCP ECN support. I've had my hands in TCP data structure/locking/etc on several occasions in the last couple of years, especially relating to SMP scalability, and most recently, TCP connection CPU affinity and hardware-driven load balancing (RSS, etc) as part of work for Juniper. Andrew Opperman andre@ has done significant work on features like TSO, LRO, timers, etc in the last couple of years, and before that reworked out TCP syncache implementation (so might be of particular interest). Drew Gallatin gallatin@ was the originator of our LRO code as part of his work at Myricom, and has taken a more general interest in stack performance. Kip Macy (kmacy@) did our TCP offload implementation as part of work for Chelsio. George Neville-Neil gnn@ has been involved in TCP regression testing, as well as other TCP-related problems in the data centre. Bjoern Zeeb bz@ has been involved in our ongoing network stack virtualisation project, and has of necessity had his hands dirty in TCP. And I feel certain there are others who, entirely accidentally and much to my embarrassment, I have omitted. As Doug points out, however, the best way to reach folks interested in TCP is via the freebsd-net@ mailing list, as people come and go some over time, and taking any questions to that list will let the answers get archived. Also, as people do come and go, the mailing list may help your requests not be dropped :-). (I've CC'd that list) Robert ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: BSDInstall: merging to HEAD
On 14 January 2011 18:26, Nathan Whitehorn nwhiteh...@freebsd.org wrote: As those of you who have been reading freebsd-sysinstall and freebsd-arch know, I have been working for a few weeks on a lightweight new installer named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 release. After two weeks of testing and bug fixes on the sysinstall list, I believe this now has all required functionality and is ready to be merged into the main source tree. I would like to do this on Tuesday, 18 January. Switching this to be the default installer would happen a few weeks after that, pending discussion on release formats with the release engineering team. This should provide a sufficient testing period before 9.0 and allow a maximal number of bugs to be discovered and solved before the release is shipped. Demo ISO for i386: http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2 SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall Wiki page: http://wiki.freebsd.org/BSDInstall Goals - The primary goal of BSDInstall is to provide an easily extensible installer without the limitations of sysinstall, in order to allow more modern installations of FreeBSD. This means that it should have additional features to support modern setups, but simultaneously frees us to remove complicating features of sysinstall like making sure everything fits in floppy disk-sized chunks. New Features: - Allows installation onto GPT disks on x86 systems - Can do installations spanning multiple disks - Allows installation into jails - Eases PXE installation - Virtualization friendly: can install from a live system onto disk images - Works on PowerPC - Streamlined system installation - More flexible scripting - Easily tweakable - All install CDs are live CDs Architecture BSDInstall is a set of tools that are called in sequence by a master script. These tools are, for example, the partition editor, the thing that fetches the distributions from the network, the thing that untars them, etc. Since these are just called in sequence from a shell script, a scripted installation can easily replace them with other things, (e.g. hard-coded gpart commands), leave steps out, add new ones, or interleave additional system modifications. Status -- This provides functionality most similar to the existing sysinstall 'Express' track. It installs working, bootable systems you can ssh into immediately after reboot on i386, amd64, sparc64, powerpc, and powerpc64. There is untested support for pc98. The final architecture on which we use sysinstall, ia64, is currently unsupported, because I don't know how to set up booting on those systems -- patches to solve this are very much welcome. There are still some missing features that I would like to see in the release, but these do not significantly impact the functionality of the installer. Some will be addressed before merging to HEAD, in particular the lack of a man page for bsdinstall. Others, like configuration of wireless networking and ZFS installation, can happen between merge and release. The test ISOs are also lacking a ports tree at the moment, which is a statement about the slow upload speed of my DSL line and not about the final layout of releases. Please send any questions, comments, or patches you may have, and please be aware when replying that this email has been cross-posted to three lists. Technical discussion (bug reports, for instance) should be directed to the freebsd-sysinstall list only. Most other discussion belongs on -sysinstall and -current. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org I dont follow the freebsd-sysinstall and freebsd-arc list so sorry if this has already been discussed. From what I have seen pc-sysinstall already does all these things, and can install freebsd. Therefore why are we reinventing the wheel? I don't mean this as any disrespect to the work you have done. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current
It would be nice if you enabled verbose kernel messages to get more info. Verbose log in attachment - please see it. I've meant log with problem. When you are loading modules on-fly. so5501a% sudo kldload ata so5501a% sudo kldload atapci.ko and dmesg: pci0: driver added found- vendor=0x1022, dev=0x2082, revid=0x00 domain=0, bus=0, slot=1, func=2 class=10-10-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pci0:0:1:2: reprobing on driver added found- vendor=0x168c, dev=0x0013, revid=0x01 domain=0, bus=0, slot=17, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0116, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=15 powerspec 2 supports D0 D3 current D0 pci0:0:17:0: reprobing on driver added found- vendor=0x1022, dev=0x209a, revid=0x01 domain=0, bus=0, slot=20, func=2 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02a0, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pci0:0:20:2: reprobing on driver added atapci0: AMD ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: reset tp1 mask=03 ostat0=60 ostat1=50 ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata0: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=20 stat1=50 devices=0x2 ata0: Identifying devices: 0002 ata0: New devices: 0002 ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ata1: ATA channel 1 on atapci0 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: Identifying devices: ata1: New devices: found- vendor=0x1022, dev=0x2094, revid=0x02 domain=0, bus=0, slot=21, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 pci0:0:21:0: reprobing on driver added found- vendor=0x1022, dev=0x2095, revid=0x02 domain=0, bus=0, slot=21, func=1 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 pci0:0:21:1: reprobing on driver added pci1: driver added so5501a% so5501a% sudo kldload ataamd so5501a% sudo kldload atadisk dmesg: ad1: Skipping 80pin cable check ad1: Skipping 80pin cable check ad1: setting UDMA33 ad1: 7631MB LEXAR ATA FLASH CARD 20070228 at ata0-slave UDMA33 ad1: 15630048 sectors [15506C/16H/63S] 1 sectors/interrupt 1 depth queue GEOM: new disk ad1 GEOM: ad1: media size does not match label. so5501a% so5501a% sudo atacontrol list ATA channel 0: Master: no device present Slave: ad1 LEXAR ATA FLASH CARD/20070228 ATA/ATAPI revision 4 ATA channel 1: Master: no device present Slave: no device present so5501a% So now it works, I am able to mount partition at ad1 ;) -- Marek Salwerowicz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: BSDInstall: merging to HEAD
On 01/16/11 05:48, Garrett Cooper wrote: On Sun, Jan 16, 2011 at 3:06 AM, kradkra...@gmail.com wrote: On 14 January 2011 18:26, Nathan Whitehornnwhiteh...@freebsd.org wrote: As those of you who have been reading freebsd-sysinstall and freebsd-arch know, I have been working for a few weeks on a lightweight new installer named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 release. After two weeks of testing and bug fixes on the sysinstall list, I believe this now has all required functionality and is ready to be merged into the main source tree. I would like to do this on Tuesday, 18 January. Switching this to be the default installer would happen a few weeks after that, pending discussion on release formats with the release engineering team. This should provide a sufficient testing period before 9.0 and allow a maximal number of bugs to be discovered and solved before the release is shipped. Demo ISO for i386: http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2 SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall Wiki page: http://wiki.freebsd.org/BSDInstall Goals - The primary goal of BSDInstall is to provide an easily extensible installer without the limitations of sysinstall, in order to allow more modern installations of FreeBSD. This means that it should have additional features to support modern setups, but simultaneously frees us to remove complicating features of sysinstall like making sure everything fits in floppy disk-sized chunks. New Features: - Allows installation onto GPT disks on x86 systems - Can do installations spanning multiple disks - Allows installation into jails - Eases PXE installation - Virtualization friendly: can install from a live system onto disk images - Works on PowerPC - Streamlined system installation - More flexible scripting - Easily tweakable - All install CDs are live CDs Architecture BSDInstall is a set of tools that are called in sequence by a master script. These tools are, for example, the partition editor, the thing that fetches the distributions from the network, the thing that untars them, etc. Since these are just called in sequence from a shell script, a scripted installation can easily replace them with other things, (e.g. hard-coded gpart commands), leave steps out, add new ones, or interleave additional system modifications. Status -- This provides functionality most similar to the existing sysinstall 'Express' track. It installs working, bootable systems you can ssh into immediately after reboot on i386, amd64, sparc64, powerpc, and powerpc64. There is untested support for pc98. The final architecture on which we use sysinstall, ia64, is currently unsupported, because I don't know how to set up booting on those systems -- patches to solve this are very much welcome. There are still some missing features that I would like to see in the release, but these do not significantly impact the functionality of the installer. Some will be addressed before merging to HEAD, in particular the lack of a man page for bsdinstall. Others, like configuration of wireless networking and ZFS installation, can happen between merge and release. The test ISOs are also lacking a ports tree at the moment, which is a statement about the slow upload speed of my DSL line and not about the final layout of releases. Please send any questions, comments, or patches you may have, and please be aware when replying that this email has been cross-posted to three lists. Technical discussion (bug reports, for instance) should be directed to the freebsd-sysinstall list only. Most other discussion belongs on -sysinstall and -current. I dont follow the freebsd-sysinstall and freebsd-arc list so sorry if this has already been discussed. From what I have seen pc-sysinstall already does all these things, and can install freebsd. Therefore why are we reinventing the wheel? I don't mean this as any disrespect to the work you have done. Hi Krad, I asked this two weeks ago and in summary: - pc-sysinstall is x86-centric and porting to powerpc is non-trivial, and sysinstall is incomplete on powerpc. Nate sought to get a working powerpc port with minimal effort. Please read other replies in the archives on freebsd-arch / freebsd-sysinstall to get more info as to why things have been done the way they have been done. Here's the summary of why this doesn't use pc-sysinstall. PC-sysinstall is the backend of the PC-BSD installer, and was imported into FreeBSD in June 2010 with the goal of replacing sysinstall. It is much more full-featured that either bsdinstall or sysinstall, providing support for encrypted disks, ZFS, and mirroring. These are all good things. However, 9.0 is coming up quite soon, and pc-sysinstall still does not have a usable front-end (the code in the tree is just a script interpreter) nor support for non-x86 platforms. Adding these things
Re: BSDInstall: merging to HEAD
On Fri, Jan 14, 2011 at 19:26, Nathan Whitehorn nwhiteh...@freebsd.org wrote: As those of you who have been reading freebsd-sysinstall and freebsd-arch know, I have been working for a few weeks on a lightweight new installer named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 release. After two weeks of testing and bug fixes on the sysinstall list, I believe this now has all required functionality and is ready to be merged into the main source tree. I would like to do this on Tuesday, 18 January. Switching this to be the default installer would happen a few weeks after that, pending discussion on release formats with the release engineering team. This should provide a sufficient testing period before 9.0 and allow a maximal number of bugs to be discovered and solved before the release is shipped. Demo ISO for i386: http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2 SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall Wiki page: http://wiki.freebsd.org/BSDInstall Goals - The primary goal of BSDInstall is to provide an easily extensible installer without the limitations of sysinstall, in order to allow more modern installations of FreeBSD. This means that it should have additional features to support modern setups, but simultaneously frees us to remove complicating features of sysinstall like making sure everything fits in floppy disk-sized chunks. New Features: - Allows installation onto GPT disks on x86 systems - Can do installations spanning multiple disks - Allows installation into jails - Eases PXE installation - Virtualization friendly: can install from a live system onto disk images - Works on PowerPC - Streamlined system installation - More flexible scripting - Easily tweakable - All install CDs are live CDs Architecture BSDInstall is a set of tools that are called in sequence by a master script. These tools are, for example, the partition editor, the thing that fetches the distributions from the network, the thing that untars them, etc. Since these are just called in sequence from a shell script, a scripted installation can easily replace them with other things, (e.g. hard-coded gpart commands), leave steps out, add new ones, or interleave additional system modifications. Status -- This provides functionality most similar to the existing sysinstall 'Express' track. It installs working, bootable systems you can ssh into immediately after reboot on i386, amd64, sparc64, powerpc, and powerpc64. There is untested support for pc98. The final architecture on which we use sysinstall, ia64, is currently unsupported, because I don't know how to set up booting on those systems -- patches to solve this are very much welcome. There are still some missing features that I would like to see in the release, but these do not significantly impact the functionality of the installer. Some will be addressed before merging to HEAD, in particular the lack of a man page for bsdinstall. Others, like configuration of wireless networking and ZFS installation, can happen between merge and release. The test ISOs are also lacking a ports tree at the moment, which is a statement about the slow upload speed of my DSL line and not about the final layout of releases. Please send any questions, comments, or patches you may have, and please be aware when replying that this email has been cross-posted to three lists. Technical discussion (bug reports, for instance) should be directed to the freebsd-sysinstall list only. Most other discussion belongs on -sysinstall and -current. -Nathan Clean new virtualbox on FreeBSD host. Install - German ISO-8859-1 - vbox - Guided - ad0 - Partition - You have canceled an installation step Actually I didn't cancel anything :) After using the entire disk and installing some distributions it hangs waiting for the root password, it won't continue when I just press enter. The screen output looks garbled by a LOR. The screen waiting for the root pw is garbled too. Seems like it's not doing a carriage return, just line-feeds. I tried this again a second time and everything worked normally. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
cosmetic nit in mmc.c
In the process of making the sdhci driver work with my laptop, I noted a cosmetic issue where the SD card's serial number is not correctly reported (it's always zero). Possible patch attached, imb Index: mmc.c === --- mmc.c (revision 217480) +++ mmc.c (working copy) @@ -749,7 +749,10 @@ uint32_t retval = bits[i] shift; if (size + shift 32) retval |= bits[i - 1] (32 - shift); - return (retval ((1 size) - 1)); +if (size 32) + return (retval ((1 size) - 1)); + else + return (retval); } static void ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Soekris net5501 - how to use hardware watchdog?
Hi all, what modules to kernel should I load in order to make use of hardware watchdog installed in Soekris net5501 ? AFAIK it is located in CS5536 chip, but don't know which module is responsible for access to it? I was trying to load ichwd module, but it is only Intel watchdog module? -- Marek Salwerowicz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Soekris net5501 - how to use hardware watchdog?
On 1/16/2011 6:17 PM, Marek Salwerowicz wrote: Hi all, what modules to kernel should I load in order to make use of hardware watchdog installed in Soekris net5501 ? Hi, Try adding option CPU_SOEKRIS to your kernel. Then just startup /usr/sbin/watchdogd ---Mike ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD 8.1 re0 shows half duplex
Howdy Guys, I have a strange problem, I'm on FreeBSD 8.1 and ifconfig re0 shows half-duplex (see output) and the download speed is damn slow, maximum 20 kbps. I'm not sure how to debug this so it would be nice if someone can help me to fix it. When i change it manually via command line, the media line appeared to have 2 entries -- full-duplex and half-duplex re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:90:6e:63 inet XX netmask 0xffc0 broadcast XX media: Ethernet 100baseTX full-duplex (100baseTX half-duplex) status: active main# uname -a FreeBSD 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #0: Fri Jan 14 04:15:56 UTC 2011 root@freebsd:/usr/obj/usr/src/sys/GENERIC amd64 main# # dmesg re0: RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet port 0xe800-0xe8ff mem 0xfbeff000-0xfbef,0xf6ff-0xf6ff irq 16 at device 0.0 on pci6 re0: Using 1 MSI messages re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: MII bus on re0 re0: Ethernet address: 6c:62:6d:90:6e:63 re0: [FILTER] re0: link state changed to UP main# # pciconf -lv re0@pci0:6:0:0: class=0x02 card=0x75221462 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet # dmideco http://nopaste.unixfreunde.de/46256 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
