Re: ata controller problem
Hi, On Fri, 26 Oct 2012 09:33:38 -0700 Jeremy Chadwick wrote: > Regarding this: > > http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html > > No no NO *NO*! > YES, YES, YES, YES! > The proper way to solve this problem is to user /boot/loader.conf How does this help when media is moved between machines? Erich ___ 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: ata controller problem
On Fri, 26 Oct 2012, Jeremy Chadwick wrote: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different "label" mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. Hmm. Six months to April 1? Seriously, labels provide a simple, relocatable identification mechanism that works across machines. If someone finds them confusing, it can be cleared up easily: use GPT labels when possible, otherwise use filesystem labels or glabel. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. Labels work on different machines or controllers without added configuration, and stay with the partition or filesystem. Your static config appears to not share those properties. ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: > > Hello Polytropon, > > Thanks for replying. > > > Maybe an update of FF and TB would be sufficient, so it can link > > to the present (or at least expected) libraries accordingly. > > Maybe I did not make it clear enough in the original message. The only > thing I installed from the installation DVD was the OS and the GNOME2 > metaport. Everything else including FF and TB was installed from ports, > the tarball of which I downloaded just a couple of days back. I hope you > are not suggesting that I build the GNOME2 metaport too from the ports > directory : with my internet connection, that really would take me into > the next century. Exactly that would have been the preferred solution. :-) > > You should not manually copy things. At some point, something will > > crash, and the ports infrastructure cannot take care of it. It's > > easier to use a port management tool (like portmaster) to deal > > with installing and updating of ports. > > For the present issue, it seems logical that I would need 2 versions of > libpng : one for GNOME and one for the ports being installed. Having the > two versions reside independently in /usr/lib and /usr/local/lib seems > to be the only way out. I still must admit that it defeats the purpose > of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: py-bittornado gone
On 26.10.2012 19:50, Damien Fleuriot wrote: On 26 Oct 2012, at 19:05, Artifex Maximus wrote: Hello! py-bittornado gone and I accidentally delete with portmanager at upgrade. cfv uses and I use cfv for testing torrent so I need py-bittornado (or py-bittorrent). How can I restore that package? Bye, a How about getting the original source and building from there, or a package for pkg_add ? ___ 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" Portdowngrade? http://www.freebsd.org/cgi/ports.cgi?query=portdown&stype=all It works fine in the past, but since Release 8.0 i hadn't use it. ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Hello Polytropon, Thanks for replying. > Maybe an update of FF and TB would be sufficient, so it can link > to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. I suspect that there might be folks at Mozilla who might see the light at the end of the tunnel (and the images on their buttons). I'll try roping them in with a separate message. If anything useful comes up, I'll post it to freebsd-questions as a message of possible interest to any other users who might be facing the same problem. Regards, Manish Jain bourne.ident...@hotmail.com ___ 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: py-bittornado gone
On 26 Oct 2012, at 19:05, Artifex Maximus wrote: > Hello! > > py-bittornado gone and I accidentally delete with portmanager at > upgrade. cfv uses and I use cfv for testing torrent so I need > py-bittornado (or py-bittorrent). How can I restore that package? > > Bye, > a > How about getting the original source and building from there, or a package for pkg_add ? ___ 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: ata controller problem
On Fri, Oct 26, 2012 at 06:43:28PM +0200, Polytropon wrote: > > I wish people would stop recommending this utter garbage. There is > > absolutely no justification behind using the highly convoluted labelling > > mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) > > different "label" mechanisms which do nothing but confuse the user, or > > cause other oddities/complexities. Good grief, there is so much hard > > evidence on the mailing lists over the past 5 (maybe even 7?) years > > talking about the utter mess that is filesystem/device/geom/blahblah > > labels that to recommend this is borderline insane. > > Yes, the amount of different, present (in parallel) and > differently implemented and accessible labeling mechanisms > can be confusing. There is no "the one true way" to do it. > Especially when dealing with metadata (e. g. for rare cases > of data recovery) it might make things more complicated. > > I don't agree that labels in general "do nothing but confuse > the user" - the same could be said about controllers, devices > and how they are partitioned (again, many different ways here). > But users usually don't deal with that. Sysadmins do. And they > should be able to deal with it, as it's not _that_ complicated > (from their educated and experienced point of view, I assume). > > That's why I would still say labels have their place, especially > in settings with many disks (10 and more) where concluding > "which disk?" is sometimes required, in terms of disk, not > disk _bay_. Let me make myself extra clear here -- and I won't be replying past this point (privately or publicly): What the OP wanted was to have a static mapping between a physical SATA port (e.g. Card #1 Port #0) and a device name (e.g. ada0) -- one which never changes no matter if there's a disk attached to the port or not. The wire-down method described above does this. Using labels does not. Here's a list of the wonderful fun things labels offer: - You get to remember or write down the label; don't forget it - You get to change /etc/fstab - You get to pray you never have to replace a disk, and if you do, that you remember which labelling method you used, and/or deal with partitioning complexities (see last item) - You get to be subjected to bugs in the GEOM layer or UFS layer when it comes to labels (this has happened!) - If using GPT (the only present way to align a partition properly to a 1MByte boundary -- matters greatly for SSDs due to NAND erase page size!), you're subjected to the problem where GEOM stores its metadata in the last sector, which is also where GPT stores its backup table. This is even documented in the Handbook, which is both good *and* hilarious at the same time And don't forget about the automatic vs. manual GEOM label method (but for this case I'm assuming automatic is used, since that method stores metadata). Every one of these situations has happened to at least one person in the past 5 (7?) years. They CONTINUE to happen. It cannot be denied. We FreeBSD users way too often shove our fingers into our ears and yell "LALALA" when people point out shortcomings. Blind advocacy of any kind of technology these days is something to be wary of. All that said: labels have a very, very specific purpose, backed by a list of many caveats. But "I want to ensure controller port X maps to device X at all times" is not one of those purposes. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Strange I/O problem on Freenas 0.7.2
Freenas 0.7.2 is old. Is write cache enable? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-disk.html Is ZFS in use? ZFS has a value for tuning. On 22.10.2012 07:34, Henti Smith wrote: Hi all. I'm having a very weird problem with a friends Freenas set-up. I'm trying to backup his data before migrating to nas4free or just plain FreeBSD. The setup is as follows: HP Microserver N36. 2BG Mem (1713 MB Usable) (no swap) 4 x 2000GB (ST2000DL003-9VT166 Seagate) drives in a graid5 setup. Initially he had no problems with the setup. Samba share was fine and he populated the raid set with 3TB of data, but somewhere along the line the disk I/O went VERY slow. I initially thought this might be raid related and did some tests but actually found the problem to be on the discs. [root@freenas ~]# diskinfo -c /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. I/O command overhead: time to read 10MB block 0.250736 sec =0.012 msec/sector time to read 20480 sectors 79.653738 sec =3.889 msec/sector calculated command overhead =3.877 msec/sector [root@freenas ~]# diskinfo -t /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. Seek times: Full stroke: 250 iter in 124.649884 sec = 498.600 msec Half stroke: 250 iter in 52.112172 sec = 208.449 msec Quarter stroke: 500 iter in 167.991252 sec = 335.983 msec Short forward:400 iter in 72.027133 sec = 180.068 msec Short backward: 400 iter in 150.708625 sec = 376.772 msec Seq outer: 2048 iter in 5.748059 sec =2.807 msec Seq inner: 2048 iter in 119.395823 sec = 58.299 msec Transfer rates: outside: 102400 kbytes in 39.207296 sec = 2612 kbytes/sec middle:102400 kbytes in 113.757181 sec = 900 kbytes/sec inside:102400 kbytes in 153.438159 sec = 667 kbytes/sec S.M.A.R.T. is not reporting any issues either and the speeds are similar on all the drives. No errors in /var/log either. Any help or suggestions would be appreciated. Regards Henti ___ 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"
py-bittornado gone
Hello! py-bittornado gone and I accidentally delete with portmanager at upgrade. cfv uses and I use cfv for testing torrent so I need py-bittornado (or py-bittorrent). How can I restore that package? Bye, a ___ 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: ata controller problem
On Fri, 26 Oct 2012 09:33:38 -0700, Jeremy Chadwick wrote: > Regarding this: > > http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html > > No no NO *NO*! No? :-) > I wish people would stop recommending this utter garbage. There is > absolutely no justification behind using the highly convoluted labelling > mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) > different "label" mechanisms which do nothing but confuse the user, or > cause other oddities/complexities. Good grief, there is so much hard > evidence on the mailing lists over the past 5 (maybe even 7?) years > talking about the utter mess that is filesystem/device/geom/blahblah > labels that to recommend this is borderline insane. Yes, the amount of different, present (in parallel) and differently implemented and accessible labeling mechanisms can be confusing. There is no "the one true way" to do it. Especially when dealing with metadata (e. g. for rare cases of data recovery) it might make things more complicated. I don't agree that labels in general "do nothing but confuse the user" - the same could be said about controllers, devices and how they are partitioned (again, many different ways here). But users usually don't deal with that. Sysadmins do. And they should be able to deal with it, as it's not _that_ complicated (from their educated and experienced point of view, I assume). That's why I would still say labels have their place, especially in settings with many disks (10 and more) where concluding "which disk?" is sometimes required, in terms of disk, not disk _bay_. > The proper way to solve this problem is to user /boot/loader.conf > tie-downs to assign each disk to each individual controllers' device > number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want). Please > note I said ahcichX, not ahciX. Different things. > > I have helped others in the past do this; Randy Bush is one such person. > > Taken directly from my /boot/loader.conf with a single SATA controller, > but obviously this can be adjusted to whatever you want. > > # "Wire down" device names (ada[0-5]) to each individual port > # on the SATA/AHCI controller. This ensures that if we reboot > # with a disk missing, the device names stay the same, and stay > # attached to the same SATA/AHCI controller. > # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > # > hint.scbus.0.at="ahcich0" > hint.scbus.1.at="ahcich1" > hint.scbus.2.at="ahcich2" > hint.scbus.3.at="ahcich3" > hint.scbus.4.at="ahcich4" > hint.scbus.5.at="ahcich5" > hint.ada.0.at="scbus0" > hint.ada.1.at="scbus1" > hint.ada.2.at="scbus2" > hint.ada.3.at="scbus3" > hint.ada.4.at="scbus4" > hint.ada.5.at="scbus5" That's a very nice contribution to the topic - I hadn't thought it was that easy, and it actually solves the "who comes first" kind of problems. > See CAM(4) man page (read it, don't skim!) for full details. Just > please for the love of god do not use labels to solve this. Thanks, this contains inspiration of maybe how to make access to USB devices and memory card readers more efficient (i. e. making sure they are always represented by one and the same device, instead of "the next free one"). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: ata controller problem
Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different "label" mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # "Wire down" device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at="ahcich0" hint.scbus.1.at="ahcich1" hint.scbus.2.at="ahcich2" hint.scbus.3.at="ahcich3" hint.scbus.4.at="ahcich4" hint.scbus.5.at="ahcich5" hint.ada.0.at="scbus0" hint.ada.1.at="scbus1" hint.ada.2.at="scbus2" hint.ada.3.at="scbus3" hint.ada.4.at="scbus4" hint.ada.5.at="scbus5" See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: ata controller problem
On Fri, 26 Oct 2012 14:18:16 +0200, Gerhard Schmidt wrote: > The Problem is that, if there is a Drive in one of the HotSwap Bays the > PCI-Express controller is detected as ahci0 and the onboard is detected > as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the > drives on the mainboard controller are the upper numbers which causes > the boot to fail as the Root Partition isn't there where it's expected. > The BIOS has the PCI-Express Card as second Card only so the Kernel is > Booted but the RootFS is not Found. You can use labels (GPT or UFS labels) or UFSIDs to become independent of the actual device name where things are stored on. You could also use this to make disks easier to identify (e. g. "/dev/label/red1root" = the disk with a red "1" on it, carrying the root file system). I suggest those pages for more detailed information: http://www.wonkity.com/~wblock/docs/html/disksetup.html http://www.freebsd.org/doc/handbook/geom-glabel.html Maybe as well (specific and general notes and inspiration): http://www.daemonforums.org/showthread.php?t=2666 http://www.freebsdonline.com/content/view/731/506/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html I assume that you are using UFS. > Is there a way to ensure that the onboard SATA Controller is always > probed first. I'm not sure if this can be done, but using labels should make the question go away, and the problem causing it. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Fri, 26 Oct 2012 20:03:11 +0530, Manish Jain wrote: > > Hi All, > > I recently purchased a laptop (Intel Pentium dual core) and installed > FreeBSD 8.3-i386 on it using the 'All' canned distribution. I then > downloaded the latest ports tarball and started building them. This ports snapshot is not "in sync" with the installed world and possibly installed 3rd party programs (ports) anymore. > Some of the ports required a newer version of the graphics/png port, so > I did a deinstall and reinstall in graphics/png. This removed the > previous binary libpng.so.6 and placed version libpng15.so.15 in its > stead. Things went wrong here - the GNOME desktop started crashing with > the panel not working and practically all desktop icons gone. Exactly my experience with some libjpeg update some years ago. :-) The rule usually is: If you update a port others depend on (read: depend on a specific version), you also need to update those ports. Mixing versions doesn't seem to be a good idea. > So I > guessed that the canned version of GNOME in the installation DVD had a > dependency on libpng.so.6. Correct. > I reinstalled FreeBSD 8.3, [...] Why did you reinstall the OS? Things like Gnome or PNG libarary are separated. > [...] and copied /usr/local/lib/libpng.so.6 to > /usr/lib/libpng.so.6 before building the ports a second time. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. > This time > things went a lot more smoothly. GNOME works. But Mozilla applications > like Firefox and Thunderbird present a peculiar problem - the buttons on > the Tool bar/Menu bar do not have any image on them. It seems that there is some "library collision". If you update things, update _all_ of them, in order to avoid version trouble. The best approach (in your case) would be: Install the OS, do not install anything from ports yet. Get the ports tree. Update it to the recent version. Now start installing stuff, and do it from the _same_ ports tree. Alternative: If you go with the programs installed from the media (e. g. the DVD), use pkg_add to get binary installed applications. In case you insist on compiling, get the ports tree of the _state of your installation_ (i. e. the tarball from the DVD) and use that. Do not update it. In this case, you can easily mix compiling from source and installing via binary packages. This alternative is not suggested now. :-) > While this is not > exactly a catastrophe, it is rankling to say the least. Maybe some > gentleman has faced this problem and has sorted it out. If anyone can > provide a hint on how to fix the problem, I would be grateful indeed. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
Problem with libpng + Mozilla applications on FreeBSD 8.3
Hi All, I recently purchased a laptop (Intel Pentium dual core) and installed FreeBSD 8.3-i386 on it using the 'All' canned distribution. I then downloaded the latest ports tarball and started building them. Some of the ports required a newer version of the graphics/png port, so I did a deinstall and reinstall in graphics/png. This removed the previous binary libpng.so.6 and placed version libpng15.so.15 in its stead. Things went wrong here - the GNOME desktop started crashing with the panel not working and practically all desktop icons gone. So I guessed that the canned version of GNOME in the installation DVD had a dependency on libpng.so.6. I reinstalled FreeBSD 8.3, and copied /usr/local/lib/libpng.so.6 to /usr/lib/libpng.so.6 before building the ports a second time. This time things went a lot more smoothly. GNOME works. But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. While this is not exactly a catastrophe, it is rankling to say the least. Maybe some gentleman has faced this problem and has sorted it out. If anyone can provide a hint on how to fix the problem, I would be grateful indeed. Thank you & Regards, Manish Jain bourne.ident...@hotmail.com ___ 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"
ata controller problem
Hi, i have a very strange Problem with my new Workstation. The Problem is the order of the sata controllers. The Mainboard has 6 sata Ports and i have a PCI-Express Card with 4 more sata Channels. I boot from a SSD connected to port 0 in the Mainboard. Channels 1-3 are additional Harddisks and 5 is a optical drive. I've a Hotswap-Bay for 3 SATA Drives the bay is connected to the PCI-Express Card SATA Channel. The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. So Far i could have set some devices.hints entries to sort the scsi busses. But the problem is that if there are no drives in the Bays the PCI-Expresscard is detected as ahci1 Is there a way to ensure that the onboard SATA Controller is always probed first. Regards Gerhard -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW & Online Services | ___ 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: FreeBSD help require for DellpowerEdge R620
Hi, On Fri, 26 Oct 2012 07:56:49 -0400 Rick Miller wrote: > On Fri, Oct 26, 2012 at 6:54 AM, Md Samadul Sarker > wrote: > > > > I have got DELL PowerEdge R620 which raid controller is H710. Can > > anyone help me that is there any chance to install FreeBSD on this > > and how? Any suggestions will be highly appreciated. > > I have a couple blog posts related to running FreeBSD on the R620. > You may want to read through them. > > http://blog.hostileadmin.com/2012/05/22/freebsd-on-dell-poweredge-12g-servers/ > http://blog.hostileadmin.com/2012/06/30/freebsd-dell-12g-x520-da2-10g-nic/ > > As far as I am aware, the mfi driver needed to support the H710 RAID > controller is only in stable/8 and stable/9 right now. I believe it > should be in 9.1-RELEASE, but I could be wrong. If/when 8.4-RELEASE > is dropped, it should be in there too. > oh, I just saw that I have forgotten the links in my former e-mail. As they would have been the same, I do not have to repeat them here. Erich ___ 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: FreeBSD help require for DellpowerEdge R620
On Fri, Oct 26, 2012 at 6:54 AM, Md Samadul Sarker wrote: > > I have got DELL PowerEdge R620 which raid controller is H710. Can anyone > help me that is there any chance to install FreeBSD on this and how? Any > suggestions will be highly appreciated. I have a couple blog posts related to running FreeBSD on the R620. You may want to read through them. http://blog.hostileadmin.com/2012/05/22/freebsd-on-dell-poweredge-12g-servers/ http://blog.hostileadmin.com/2012/06/30/freebsd-dell-12g-x520-da2-10g-nic/ As far as I am aware, the mfi driver needed to support the H710 RAID controller is only in stable/8 and stable/9 right now. I believe it should be in 9.1-RELEASE, but I could be wrong. If/when 8.4-RELEASE is dropped, it should be in there too. -- Take care Rick Miller ___ 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: FreeBSD help require for DellpowerEdge R620
Hi, On Fri, 26 Oct 2012 11:54:39 +0100 "Md Samadul Sarker" wrote: > I have got DELL PowerEdge R620 which raid controller is H710. Can > anyone help me that is there any chance to install FreeBSD on this > and how? Any suggestions will be highly appreciated. > just check this and you should be able to get some FreeBSD running. Erich ___ 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 help require for DellpowerEdge R620
Hi, I have got DELL PowerEdge R620 which raid controller is H710. Can anyone help me that is there any chance to install FreeBSD on this and how? Any suggestions will be highly appreciated. Thanks in advance Sarker ___ 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: rc.conf and loader.conf
On Fri, 26 Oct 2012 07:37:09 +0200 (CEST), Trond Endrestøl wrote: > However, I like to keep the lines in the /etc/rc.conf file in the same > order as they appear in the /etc/defaults/rc.conf file, and place > local stuff (from /usr/local/etc/rc.d) in alphabetical order at the > bottom of the file. Slight deviation: I tend to group settings according to their functionality (network, server stuff, console settings etc.), and also have local additions at the end of the file. However, FreeBSD also supports rc.conf.local to keep them. The rc.conf file can be seen as a shell script, containing variable assignments. It is that simple. It implies that you can arrange everything (with newlines, comments, in groups, as you wish) as long as it is valid shell syntax. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: NVIDIA proprietary driver error
On 25/10/2012 19:52, Ashkan Rahmani wrote: On Oct 25, 2012 12:02 PM, "Shane Ambler" wrote: On 25/10/2012 17:34, Ashkan Rahmani wrote: Hi, I'm going to install driver for nvidia 310M cuda enabled, but I have some problem with it. Monitor resolution must be 1366x768 xxx but resolution is 1024x768 and with lag. Sounds like your on a laptop? model details could be helpful if someone else has tried on that machine. yes it is asus k52j' no there is not second monitor. and i have just screen0 in xorg config file. what you mean from second gpu?? driver is nvidia. resolution not set. There are a few K52J variations - the K52JC has the 310M In the xorg.conf you posted the link to - you have two parts titled - Section "Device" - one has card0 nvidia the other has card1 intel. You also have two sections for Screen and two for Monitor. In the ServerLayout you have Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" My guess is that the cpu has a built-in gpu. The asus details list four corei5 options - intel says 3 of them include HD graphics see last table here - http://www.intel.com/support/processors/mobile/corei5/sb/CS-032331.htm?wapkw=corei5+540m Just wondering if the two gpu's might be creating a conflict. I would try removing the screen 1 line from serverlayout as well as the matching screen and monitor 1 details as well as the intel graphics device section - disconnecting a second monitor if it is connected. Change Driver "nv" to Driver "nvidia" and try that. xorg.conf which generated by xorg -configure detect vga vendor name as intel corporation, and set driver vesa. when i change driver to any thing else i got no devices detected error. please attention i have label on laptop body says vga is nvidia geforce 310m cuda 1gb, and another label with nvidia optimus. Have you tried running nvidia-xconfig? x11/nvidia-xconfig or nvidia-settings? x11/nvidia-settings i have an option in bios "boot vga controller selection for" which have 2 options windows 7/vista and reserved. Try changing to reserved. You may also want to try removing the nvidia sections from xorg.conf and see if you can get the intel gpu to work. Also when you reply, use reply to all so that a copy also goes to the list. It can increase your chance of someone helping. ___ 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"
PCB order
Dear Manager, We are PEAK PCB LIMITED , Located in Shenzhen, China.And we have been manufacturing of printed circuit boards for more than ten years now. We mainly offer: Single layer Double laylers Multilayer PCBs Aluminium PCB and so on Fast Delivery: Urgent Production 2~3 Days Small Production 4~5 Days Mass Production 7~8 Days If you have any inquiry,please contact us asap,we will give you the best serving and one competitive price. Thanks for your attention. Best regards, PEAK PCB LIMITTED Jason Tel:+86-0755-29100879 Fax:+86-0755-29109182 E-mail: sales7(at)peakpcb.com ___ 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"
