Re: Western Digital hard disks and ATA timeouts
Søren Schmidt wrote:
On 7Nov, 2008, at 20:12 , Peter Wemm wrote:
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick <[EMAIL PROTECTED]>
wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, and
is not adjustable without editing the ATA code yourself and increasing
the value. The FreeNAS folks have made patches available to turn the
timeout value into a sysctl.
Soren and/or others, please increase this timeout value. Five seconds
has now been deemed too aggressive a default. And please consider
migrating the timeout value into a sysctl.
The 5 second timeout has been a problem for quite a while actually.
I've had a number of instances where I've had to increase it to 20 or
30 seconds when recovering from marginal drives. The longest
"successful" recovery attempt I've seen was 26 seconds, I believe on a
Maxtor drive a few years ago. ("successful" == the drive spent 26
seconds but eventually successfully read the sector). Even the IBM
death star drives could take much longer than 5 seconds to do a
recovery 5 years ago. 5 seconds has never been a good default.
I think the timeout should be increased to at least 30 seconds. My
windows box has a timeout that goes for several minutes.
If there is concern about FreeBSD appearing to hang, I could imagine
that a console warning message could be printed after 5 seconds. But
just say "drive has not yet responded". But give it more time.
In this day and age we're generally not playing games with udma33 vs
66, notched cables, poor CRC support etc. SATA seems to have
eliminated all that. Hmm, it might make sense to increase the timeout
on SATA connections to 2 or 3 minutes by default.
Actually I do have a patch around that logs the timeout on the console
after the normal timeout (5secs), then just goes on to wait for double
the timeout and log again etc etc, final timeout was IIRC 60 secs but
could be anything.
I have a disk which I am finally getting rid of that produces READ_DMA
and WRITE_DMA errors at a pretty high rate. I did enable the extra ATA
error reporting and it doesn't seem to indicate any sort of actual
errors, just extra long itmeouts.
At one time, I did change the system to extend the timeout, but I did
not see any real improvement at 30 seconds. I suspect that an even more
extended timeout would be necessary to solve the problem.
I am removing the disk this week. Does anyone want a disk that produces
DMA timeouts at a regular rate? Would it help actually solve this problem?
Please let me know if you want such a beast and I will ship it to you.
/Joe
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Sebastien Chassot wrote: On Sun, 2009-02-01 at 17:19 +, Daniel Bye wrote: On Sun, Feb 01, 2009 at 05:42:39PM +0100, Sebastien Chassot wrote: Hi, I've upgrade to xorg7.4 and apparently keyboard and mouse are now working with hald. In xorg.conf changing "old" keybord config as no effect and I can't find how change it with hal. I've got /usr/local/etc/hal/fdi/* but no *keymap* and I don't know how build such a file. This should get you started: gb Change the `gb' in the example to your local keymap name, save the file as /usr/local/etc/hal/fdi/policy/x11-input.fdi and restart hald. This seems to have a way to enable HAL to detect a keyboard and export it to X, but what about mice? My Xorg log tells me that it is ignoring my USB mouse in addition to ignoring my keyboard, so what sort of HAL file do I add to enable it to find my mouse? Where in HAL documentation is this information found? R. Noland seemed to think it was a trivial process to make HAL do keyboards and mice? In fact it is not trivial but a pain in the ass! If you intend to inflict broken software on unsuspecting users you had better think through all of the problems and come up with explicit solutions to all of those problems so that everyone has a chance to make their systems work. There had better not be any more surprises waiting in the X 1.6 wings to surprise and confound everyone again! I'll start with that Thank you Sebastien ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Robert Noland wrote: On Sun, 2009-02-01 at 14:10 -0800, Joe Kelsey wrote: Sebastien Chassot wrote: On Sun, 2009-02-01 at 17:19 +, Daniel Bye wrote: On Sun, Feb 01, 2009 at 05:42:39PM +0100, Sebastien Chassot wrote: Hi, I've upgrade to xorg7.4 and apparently keyboard and mouse are now working with hald. In xorg.conf changing "old" keybord config as no effect and I can't find how change it with hal. I've got /usr/local/etc/hal/fdi/* but no *keymap* and I don't know how build such a file. This should get you started: gb Change the `gb' in the example to your local keymap name, save the file as /usr/local/etc/hal/fdi/policy/x11-input.fdi and restart hald. This seems to have a way to enable HAL to detect a keyboard and export it to X, but what about mice? My Xorg log tells me that it is ignoring my USB mouse in addition to ignoring my keyboard, so what sort of HAL file do I add to enable it to find my mouse? The above is only to set keyboard layout, everything to detect the keyboard is already present. Where in HAL documentation is this information found? R. Noland seemed to think it was a trivial process to make HAL do keyboards and mice? In fact it is not trivial but a pain in the ass! If you intend to inflict broken software on unsuspecting users you had better think through all of the problems and come up with explicit solutions to all of those problems so that everyone has a chance to make their systems work. We (marcus and I) have gone to great pains to try and ensure that hal behaves correctly in pretty much all mice configurations with or without sysmouse. If you don't want to use hal, set AutoAddDevices off and configure away. I did my best to follow ALL of the posted directions to absolutely NO AVAIL. When I start Xorg, it explicitly tells me it is disabling all automatic devices and refuses to use HAL or any other detectable methosd to find the mouse and/or keyboard. There is no documentation ANYWHERE about how HAL is supposed to help in any of this. There is no documentation ANYWHERE about what exaqctly the new Xorg is supposed to do about it. There is no documentation ANYWHERE about the new, secret, hidden options that you can put in your xorg.conf file to disable this whole HAL mess. The only documentation available ANYWHERE is the skimpy little paragraph that says, it works or it doesn't. No explanation about why it works or doesn't or how to determine exactly what might be wrong in your configuration to make it work or not work. I would not compalin if you actually documented what you are inflicting on us rather than just say, here it is, good luck! I understand how difficult some of these port upgrades are, but you have to realize that you have not provided ANY resources that anyone else can use to help themselves figure out their issues. I don't want to pay you with money I do not have from a job I do not have. You have to realize how many people may or may not have problems due to your blithe posting of this complicated mess. Either explain how to use HAL properly to configure X resources or disable the capability. Thank you for all of your effort so far. I really do appreciate it. /Joe There had better not be any more surprises waiting in the X 1.6 wings to surprise and confound everyone again! Are you going to stop paying me? You have no idea how many combinations of hardware and configurations for X exist, or the amount of wok that goes into making all of those combinations work. robert. I'll start with that Thank you Sebastien ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Robert Noland wrote: man xorg.conf search for Input... This provides absolutely no help. I look at my /var/log/Xorg.0.log and it tells me nothing. If I remove the keyboard and mouse input devices from xorg.conf, the log tells me that it is disabling all input devices and never says anything else. There is no evidence that hal does anything that X want to know about. How would I detect that my configuration file needs changing? Is there a message in Xorg.0.log to look for? Is there a help file somehwere which explains how to change your configuration file to allow hal to work? I cannot find any information anywhere in the system to allow me to debug my problems in any way. I want to have fully automatic configuration using whatever means will allow it. You explanations about the mysterious behavior of hal and xorg do not give me any information I can use in any way to solve my problems. Set Options "AutoAddDevices" "off" and you have to configure everything like you used to. I WANT to use the new facilities. Is it possible to debug my configuration problems? Where do I start? How do I enable this magical new world of letting hal do things for me? What changes do I make to xorg.conf to allow this? /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Robert Noland wrote: On Tue, 2009-02-03 at 15:07 +0100, Sebastien Chassot wrote: On Mon, 2009-02-02 at 16:05 -0500, Robert Noland wrote: On Mon, 2009-02-02 at 12:43 -0800, Joe Kelsey wrote: Robert Noland wrote: man xorg.conf search for Input... This provides absolutely no help. I look at my /var/log/Xorg.0.log and it tells me nothing. If I remove the keyboard and mouse input devices from xorg.conf, the log tells me that it is disabling all input devices and never says anything else. There is no evidence that hal does anything that X want to know about. How would I detect that my configuration file needs changing? Is there a message in Xorg.0.log to look for? Is there a help file somehwere which explains how to change your configuration file to allow hal to work? I cannot find any information anywhere in the system to allow me to debug my problems in any way. I want to have fully automatic configuration using whatever means will allow it. You explanations about the mysterious behavior of hal and xorg do not give me any information I can use in any way to solve my problems. Set Options "AutoAddDevices" "off" and you have to configure everything like you used to. I WANT to use the new facilities. Is it possible to debug my configuration problems? Where do I start? How do I enable this magical new world of letting hal do things for me? What changes do I make to xorg.conf to allow this? Ok, are you using gdm, xdm, or startx? You need to ensure that dbus and hald are running first. Set dbus_enable="YES" and hald_enable="YES" in your rc.conf. This FAQ says to remplace dbus/hal by gnome_enable="YES" Correct, if you using gnome, that will enable hal and dbus. zircon.zircon.seattle.wa.us$ ps xa | egrep hal\|dbus 789 ?? Is 0:00.12 /usr/local/bin/dbus-daemon --system 946 ?? Ss 0:17.94 /usr/local/sbin/hald 951 ?? IW 0:00.00 hald-runner 968 ?? IW 0:00.00 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mous 986 ?? S 0:09.15 hald-addon-storage: /dev/cd0 (hald-addon-storage) 1027 ?? IW 0:00.00 /usr/local/bin/dbus-launch --exit-with-session 1082 ?? IW 0:00.00 dbus-launch --exit-with-session /usr/local/bin/seahor 1083 ?? Is 0:00.92 /usr/local/bin/dbus-daemon --fork --print-pid 7 --pri 42823 p1 DL+0:00.00 egrep hal|dbus Attached is /etc/rc.conf. /Joe robert. http://www.freebsd.org/gnome/docs/faq2.html#full-gnome # -- sysinstall generated deltas -- # Sun Oct 23 06:00:05 2005 # Created: Sun Oct 23 06:00:05 2005 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. defaultrouter="192.168.1.1" hostname="zircon.zircon.seattle.wa.us" ifconfig_sk0="inet 192.168.1.3 netmask 255.255.255.0" linux_enable="YES" nfs_server_enable="YES" nfs_client_enable="YES" rpcbind_enable="YES" rpc_statd_enable="YES" rpc_lockd_enable="YES" sshd_enable="YES" usbd_enable="YES" svscan_enable="YES" moused_enable="YES" # Run the mouse daemon. moused_type="auto" # See man page for rc.conf(5) for available settings. moused_port="/dev/ums0" # Set to your mouse port. moused_flags="-m 3=1 -m 1=3 -m 4=6 -m 6=4 -m 5=7 -m 7=5" mysql_enable="YES" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_map_queue_enable="NO" gdm_enable="YES" dumpdev="NO" # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. ntpdate_flags=140.142.16.34 ntpdate_enable="YES" ntpd_enable=YES #amd_enable="YES" dbus_enable="YES" polkitd_enable="YES" hald_enable="YES" # The Fish generated deltas - Sat May 5 14:27:39 2007 weak_mountd_authentication="YES" # added by mergebase.sh local_startup="/usr/local/etc/rc.d" cupsd_enable="YES" apache22_enable="YES" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
6.3-RELEASE versus 5.2-RELEASE
I think I have finally decoded Jo Rhett's issue. It is very hard to decipher because the poster refuses to exactly identify their problem. The entire problem comes down to the definition of -RELEASE. Jo apparantly feels that they can ONLY run -RELEASE branded code at their workplace. That means that they cannot run any form of -STABLE. Therefore, they can only ever run 6.3-RELEASE and then only if no bugs were fixed after the official branding of 6.3-RELEASE. I cannot speak at all about the branding of 6.3-RELEASE. I run 7.0-STABLE here. What Jo seems to thik is that a certain sequence of events occurred during the 6.3-RELEASE branding. 6.3-RELEASE was marked in the tree. Sometime after this marking event occurred, bugs were ientified and subsequently fixed in the -STABLE branch. These bugs have been identified by Jo as SHOWSTOPPER bugs which will prevent him from ever using 6.3-RELEASE, since by their definition, they can only ever use the exact thing identified by the cvs tag of 6.3-RELEASE. Therefore, by Jo's definition, they can never run 6.3-anything at their shop and are forced to wait for 6.4-RELEASE, whenever that happens. Therefore, they must take on the onerous duty of examining all security fixes target for 6.3 and redo them for 6.2. Basically, they do not wish to do this and protest the EoL status given to 6.2 because they are physically prevented from using 6.3. They refuse to even try to identify whether or not 6.3-RELEASE actually has any bugs that affect them, they just assume that the presence of bugs fixed AFTER the tagging of 6.3-RELEASE in cvs certifies their inability to use the actual 6.3-RELEASE code, since they can apparantly only run binary releases direct from FreeBSD and cannot "roll their own" for some unknown reason. They are also, apparantly, prohibited from testing any code locally due to some unknowable reason. Can anyone verify that some number of bugs related to either a) gmirror, b) bge and/or c)twe were fixed after the release of 6.3? That is as far as I can tell the reason that Jo objets to EoL of 6.2, the fact that 6.3 is unusable due to these late-fixed bugs. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Closing the Jo Rhett argument
Jo Rhett has clearly stated (in offline reply) that they do not participate in the -BETA and-RC cycles leading up to -RELEASE, so they therefore do not have any issues with -RELEASE and EoL to raise. Actually, they still have the same complaints to raise about EoL, but since they refuse to participate in the -RELEASE process, they do not have valid points to raise. I ask that everyone please stop communicating with the persona known on this list as "Jo Rhett" unless and until they participate in the -BETA, -RC, and -RELEASE process. You cannot raise any sort of valid complaint about -RELEASE, EoL or bugs if you do not participate in finding bugs during the -BETA and -RC stages prior to the -RELEASE. If you instead choose to try to run -RELEASE and find bugs then, then complain about the bugs you found and continue to complain that these bugs were not found by someone else and fixed ahead of time, you have no issues and do not deserve an answer, no matter how much you try to frame it as a "policy" question. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DVD-RW doesn't write
Jerahmy Pocott wrote: On loading atapicam module it says: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 I have never managed to use burncd with any drive. In order to use atapicam, you must enable the pass? devices. My devfs.conf contains: # Commonly used by many ports linkacd0cdrom linkacd0dvd # Allow a user in the wheel group to query the smb0 device #permsmb00660 permxpt00660 permpass00660 permpass10660 The xpt0 is left over from other experiments. The pass? is required to allow general access to use of growisofs. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Heimdal version in system is ancient!
Why is the version of Heimdal in the base system 0.5.1? The port has 0.6.1 in /usr/ports/security/heimdal. How are we supposed to do any useful work when the system version of a product is in direct conflict with a port version? How do I get the latest version of Heimdal into the system? /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
On Thu, 2004-11-25 at 20:36 +0100, alex bustamante wrote: > On Thu, 2004-11-25 at 19:43 +0100, Fredrik Eriksson wrote: > > On Thu, Nov 25, 2004 at 06:07:36PM +, Mark Dixon wrote: > > > On Thursday 25 Nov 2004 17:52, Joe Kelsey wrote: > > > > > > > > The NVIDIA drivers are completely crap! They do not work and contain > > > > countless errors which will cause system failures on every single > > > > machine I have tried to use them with. Do not ever buy or attempt to > > > > use anything made by NVIDIA. They just do not work. > > > > > > Like I said, they work fine for me. > > > > Yes, but will you get the full power of the card? I think not. > > I've had lots of problems with NVidia products and *BSD. > > > > > > > I'm not going to get into a 'my graphics card is better than yours'. Its > > > very > > > boring and very offtopic. > > > > I don't think this is about which card is better than the other, more about > > NVidia being reactionary bastards who refuse the idea of open source. > > NVidia graphic cards are probably great for playing games in windos. > > > How many manufactures release their drivers in open source? Does Matrox > do it? You do not need to release your source code. You only need to publish the specs for the actual hardware. Matrox supports developers by actually publishing the specs. NVidia does not publish any information about its hardware. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fixing Posix semaphores
I have a desire to fix posix semaphores in at least 5.3. The current implementation doesn't actually follow the "spirit" of the standard, even though it technically qualifies in a somewhat degraded sense. I refer to the fact that the current implementation treats posix semaphores as completely contained inside the kernel and essentially divorced from the filesystem. The true "spirit" of the standard places the semaphores directly in the file system, similar to named pipes. However the current implementation treats the supplied "name" as a 14-character identifier, required to begin with a slash and contain no other slashes. Pretty weak. Well, in order to fix this, we need to add file system code and come up with a new type. I currently have some time to spend on something like this and am willing to put in whatever effort it takes. Does anyone want to add their own ideas or requirements? I currently run 5.3, but I suppose I could think about running current at some point in the future. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.10 vs. 5.3: iswcntrl
I am helping a friend work out problems with the latest release of streamripper. I run 5.3, he runs 4.10. The issue we currently have concerns iswcntrl, or rather the lack of iswcntrl in 4.10. Has thought been given to any sort of MFC to 4.11 or is his only recourse upgrading to 5.3? /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror Issues
I am having a real hard time with gmirror. I recently bought two new 400G SATA disks and I want to mirror them. I think I am following the directions, but I am not sure. I generally do the following steps: edit /boot/loader.conf to add geom_mirror_load. reboot into single-user gmirror label -v -b round-robin gm0 ad4s1 ad6s1 bsdlabel -w mirror/gm0 bsdlabel -e mirror/gm0 newfs mirror/gm0a When I attempt to perform the newfs, it generally goes through all of the backup super blocks and hangs the system at the end of the newfs. At that point, my only recourse is pushing the reset button. When the system comes up, GEOM_MIRROR tries to rebuild one of the providers (usually ad4s1), but never seems to succeed. Anyway, the first problem I had was not having geom_mirror loaded. The only solution seems to be adding the load to /boot/loader.conf. None of the manual pages or handbook pages says anything about this except when discusssing making your system disk mirrored. I am not doing that. So, after loading the mirror stuff, I regularly lock up the system by trying to perform simple activities on the mirror. What do I need to do differently? Here are the relevant dmesg lines: atapci0: port 0xa000-0xa007,0x9800-0x9803,0x9400-0x9407,0x9000-0x9003,0x8800-0x880f mem 0xfba0-0xfba001ff irq 18 at device 13.0 on pci0 ata2: on atapci0 ata3: on atapci0 ad4: 381554MB at ata2-master SATA150 ad6: 381554MB at ata3-master SATA150 FreeBSD zircon.zircon.seattle.wa.us 6.2-STABLE FreeBSD 6.2-STABLE #0: Sat Mar 24 16:32:06 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZIRCON amd64 amd64 amd64 FreeBSD /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror Issues
Ivan Voras wrote: Joe Kelsey wrote: So, after loading the mirror stuff, I regularly lock up the system by trying to perform simple activities on the mirror. What do I need to do differently? Here are the relevant dmesg lines: atapci0: port 0xa000-0xa007,0x9800-0x9803,0x9400-0x9407,0x9000-0x9003,0x8800-0x880f mem 0xfba0-0xfba001ff irq 18 at device 13.0 on pci0 I did almost the same thing you did with gmirror on 6.2-release on amd64 the other day and it worked. There were several complaints about "SiI" hardware in the past, though - you might want to search the lists. Thank you for the suggestion, but it does not help. There is some traffic on the list about the 3112, but I have a 3512, which does not have any list traffic about bugs. The major thing that needs doing is a detailed explanation of how to take two brand new disk drives and mirror them. Nothing in the documentation discusses this. Do you have to create file systems on the drives first? Do you have to use fdisk to slice them up? Is there a size limit on drives? I am trying to mirror two 400G drives, is this supported? There is no information anywhere that I can find about these topics. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror Issues
Joe Kelsey wrote: I am having a real hard time with gmirror. I recently bought two new 400G SATA disks and I want to mirror them. I think I am following the directions, but I am not sure. I generally do the following steps: edit /boot/loader.conf to add geom_mirror_load. reboot into single-user gmirror label -v -b round-robin gm0 ad4s1 ad6s1 bsdlabel -w mirror/gm0 bsdlabel -e mirror/gm0 newfs mirror/gm0a When I attempt to perform the newfs, it generally goes through all of the backup super blocks and hangs the system at the end of the newfs. At that point, my only recourse is pushing the reset button. When the system comes up, GEOM_MIRROR tries to rebuild one of the providers (usually ad4s1), but never seems to succeed. Anyway, the first problem I had was not having geom_mirror loaded. The only solution seems to be adding the load to /boot/loader.conf. None of the manual pages or handbook pages says anything about this except when discusssing making your system disk mirrored. I am not doing that. So, after loading the mirror stuff, I regularly lock up the system by trying to perform simple activities on the mirror. What do I need to do differently? Here are the relevant dmesg lines: atapci0: port 0xa000-0xa007,0x9800-0x9803,0x9400-0x9407,0x9000-0x9003,0x8800-0x880f mem 0xfba0-0xfba001ff irq 18 at device 13.0 on pci0 ata2: on atapci0 ata3: on atapci0 ad4: 381554MB at ata2-master SATA150 ad6: 381554MB at ata3-master SATA150 OK. I did some more testing and found a bug in the SII3512 controller. If I mount just one of the drives just as a single disk and attempt to move a 250G drive over using tar, sometime during the copying the system simply hangs. No errors, no messages, the system stops and my only recourse is jto press the reset button. For that reason, I have decided that the SII3512 is unreliable and will replace it with a Promise controller, basically the cheapest one (TX2). I hope it works better. Thank you everyone for the links to other pages. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
relocation truncated to fit
I have a problem reported to me in ports/65 about ksh93 not compiling on the sparc64 platform due to the linker reporting "relocation truncated to fit". This is an error I have never seen. I know for a fact that it is not strictly a sparc64 platform issue as I have seen reference to it in relation to amd64. However, I have never seen a resolution of the problem.I believe that this is a gcc issue. How do I fix this? I cannot find any information in the Freebsd site about this mysterious error message. I know that ksh93 works on sparc64 because the ksh93 developers are working with Sun to install it as a default shell in Solaris 11. Therefore, it works with the Sun compiler. Why do I get this error on gcc? Any help would be greatly appreciated. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
DVD Device Errors
FreeBSD zircon.zircon.seattle.wa.us 6.2-STABLE FreeBSD 6.2-STABLE #2: Sun Apr 22 14:47:33 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZIRCON amd64 I have a Sony RW DVD hooked up to my system and it does not operate properly. Here is the dmesg: acd0: DVDR at ata0-master UDMA66 When I place a movie in the player and attempt to play it I get: +acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 This is using libdvdread in mplayer or ogle. Am I missing something about setting up the player? I have also enabled atapicam in order to use the dvdrwtools, but I get similar errors, except related to writing. I have the device in group operator, to which I belong. Can anyone offer any suggestions? Thank you very much for any help. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Logitech MX700 Moiuse Prblems
I have read many messages on the various lists concerning the Logitech
MX700 mouse and button problems, especially with the scrolling wheel.
The message that provided me the real clue to what is going on was the
one to hardware@ by Joe Schmoe that went through a very complex setup
involving xorg.conf, xmodmap and imwheel. This is just too much work!
Since I always have to modify moused to make my mice operate
left-handed, I know how to use moused to accomplish the same operation
with absolutely no change to xorg.conf, xmodmap or imwheel. Here is the
entry for my mouse in usbd.conf:
device "Mouse"
devname "ums[0-9]+"
attach "/usr/sbin/moused -m 3=1 -m 1=3 -m 4=6 -m 6=4 -m 5=7 -m
7=5 -p /dev/${DEVNAME}
-I /var/run/moused.${DEVNAME}.pid ; /usr/sbin/vidcontrol -m on"
What I do there is exchange the operation of buttons 1 and 3 to provide
left-handed operation, then switch buttons 4 and 6 and buttons 5 and 7.
I do not change anything else in the standard xorg.conf file.
Now, my mouse wheel works all the time. That whole mess with xmodmap
and imwheel just confused me since I have never used or heard of imwheel
and I also haven't used xmodmap in years, although I used to use it
regularly.
I hope this helps someone else.
/Joe
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB Mosue Driver Problems
I have a Logitech MX700 USB Wireless mouse. A few days ago I posted about changing the usbd.conf entry to swap buttons 4 and 6 and buttons 5 and 7 to get the wheel scrolling to work correctly. Last night, I rebooted my system and the moused was started from rc.conf instead of usbd.conf! Since when does this happen and why should usbd.conf use the settings for the ps/2 mouse in rc.conf? If I unplug and replug the mouse, it gets the correct moused settings from usbd.conf. What exactly is happening here? This is FreeBSD crusty.zircon.seattle.wa.us 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #12: Fri Mar 31 17:43:23 PST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CRUSTY amd64 updated yesterday. /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems Booting 6.0 RC1 on ia64
I am trying to boot up 6.0 RC1 on a brand new ia64 box. I have an ASUS A8V motherboard with an AMD64 3800. I have a DVD writer attached to the ATA bus and two SATA disk drives. On my x86 box (5.4), I download the 6.0 RC1 ia64 disc ISO images and burn them onto CD-ROM. I then take the new CD-ROM and put it in the ia64 drive. The system starts the boot process (with boot drive set to the DVD writer), but errors out and asks me to insert a valid boot drive. What have I done wrong here? /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with moused or XFree86-4.03
John Merryweather Cooper writes: > After installing XFree86-4.03 (XFree86-4.02 had worked just fine), > I found myself with a mouse that would not function under X. The > pointer would appear, but it would be pinned at the top-most scan line > of the monitor--able to move laterally, but not vertically. > > The mouse in question is a Logitech MouseMan+ WheelMouse. Under 4.02, > it had worked just fine. It was attached to a PS/2 mouse port. It was > setup in sysinstall for "Auto" and PS/2 port with no other switches. > > I was curious what moused thought of the mouse. When I ran moused -p > /dev/sysmouse -i all, I was unpleasantly surprised to see it identified > as: > > /dev/sysmouse sysmouse sysmouse generic Of course it will tell you that. /dev/sysmouse is *created* by moused! In order to test the mouse, you would have to run it using the *real* port of /dev/psm0. 4.02 of X *broke* the mouse, so I kind of doubt that your were actually running 4.02. Or maybe sometime in the last month the port changed? I know that when I upgraded from 4.01 to 4.02 the mouse stuff broke completely. What were you using in your X config file? There is no way to diagnose your problem without that information. /Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Staying *really stable* in FreeBSD
Mike Porter writes: > [Lots of rambling ideas ...] First of all Mike, quite an interesting post. Unfortuantely, either the author of the book didn't understand or didn't explain the CMM well enough for you to be able to use it. I have worked as a Software Quality Engineer (really doing Quality, not being a glorfied tester as the software industry seems to call anyone who runs a test a "quality engineer", just like anyone who has written a line of code gets to call themselves a "software engineer"...) and I have helped organizations achieve CMM Level 3 and above. If you look at the actual CMM, you could argue that the general FreeBSD process qualifies for Level 2, given a little more work on the Project Management and Configuration Management fronts. The main things missing is good design documentation and real attention to CM issues. However, I do not think it is possible for any "open source" volunteer effort to get better than Level 2. It requires really dedicated resources in the upper management areas that just won't happen outside of a corporate context. Also, when you start throwing process ideas around a group like this, you might not be received very well... I suggest you go read the various XP books (eXtreme Programming). They are small and easy to digest and are much more applicable to this environment (except for the pair programming part...) /Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hardware RAID vs vinum
On Wed, 2002-05-29 at 07:11, Scott Long wrote: > On Wed, May 29, 2002 at 01:42:11PM +0930, Greg 'groggy' Lehey wrote: > > > > I'm sure that there are good reasons for small stripe sizes. I don't > > believe that efficiency is one of them. I think your problem is that > > you're looking at single-request latency. That's usually not an > > issue, though it may impact copy performance. As I said, though, > > that's not usually where you would use RAID-5. The real issue is not > > so much latency as throughput. I hope I've been able to make it more > > understandable. > It is obvious that I have tread onto religious territory here, and > as such there is probably little I can say to convince you of my > points. I think that we must then agree to disagree =-) Au contraire. There is no religion involved. Greg presented hard facts. You can either refute his facts by presenting your own hard facts or else concede the point. If you cannot refute the facts, then you, by implication, concede the argument. /Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Posix semaphore problem
On Sun, 2003-03-23 at 16:06, Mikhail Kruk wrote: > I beleive he is not using SYS V Semaphors but rahter POSIX semaphors. I > don't know about 5.0, but they are definitely not supported in 4.x Posix semaphores in 5.0 are supported with a kludged-together mess of SYSV semaphores and posix-threads... The 5.0 implementation of posix semaphores is seriously broken. /Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Tools to modify shared libraries
Has anyone ever come across general-purpose tools for modifying shared libraries? What I want to do is to edit the list of "needed" shared libraries to correct the common mistakes that developers make in creating shared objects with large lists of shared libraries. Specifically, I want to modify linux-flashplugin6/libflashplayer.so to remove all of the idiotic references to shared libraries that the Flash 6 developers added. Since this is a plugin for Mozilla, it does not need to specify any extra shared libraries especially since Mozilla has already loaded all of them! I want to do this to make Flash 6 work with flashpluginwrapper. If I can remove the list of needed shared libraries from the DYNAMIC section of the shared library, everyone will be that much closer to a real flash 6 plugin for BSD. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/etc/libmap.conf MFC?
Does anyone have plans to MFC the /etc/libmap.conf functionality into stable? Just for curiosity, I tried the original patch on my stable sources and that patch applied with no errors. I have seen messages on CURRENT talking about fixes for various bugs, so I suspect that applying the original patch to my sources might cause problems. Anyway, this seems like just the kind of functionality to fix the "editing of shared libraries" problem I posted about earlier. It also does not seem like a real big deal to do an MFC for. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 Boot Hang when USB Devices Attached
Brandon Fosdick wrote: Joe Kelsey wrote: When I upgraded to fix the OpenSSH problems, the system started hanging at boot time right after the USB/OHCI messages whenever I had devices plugged into the USB ports (mainly a USB mouse). Now, in order to boot, I have to unplug the mouse and wait for the system to pass the USB part of boot before replugging. There are several threads discussing this ATM. If you have an nforce2 board search for the thread with the subject "fix/workaround for usb probe lockups on nForce2 mbs". Andrew Atrens posted a patch that worked for me. In the same thread Ian Dowse has offered a few other ideas to try. I haven't tried them yet. I have an ASUS A7S333 which does *not* have an nforce2 chipset. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 Boot Hang when USB Devices Attached
Kent Stewart wrote: On Friday 26 September 2003 12:06 pm, Joe Kelsey wrote: Brandon Fosdick wrote: Joe Kelsey wrote: When I upgraded to fix the OpenSSH problems, the system started hanging at boot time right after the USB/OHCI messages whenever I had devices plugged into the USB ports (mainly a USB mouse). Now, in order to boot, I have to unplug the mouse and wait for the system to pass the USB part of boot before replugging. There are several threads discussing this ATM. If you have an nforce2 board search for the thread with the subject "fix/workaround for usb probe lockups on nForce2 mbs". Andrew Atrens posted a patch that worked for me. In the same thread Ian Dowse has offered a few other ideas to try. I haven't tried them yet. I have an ASUS A7S333 which does *not* have an nforce2 chipset. Mine doesn't either and the fact it dies in the boot -s phase of updating the system is a verification of the reason to boot to single user mode. I have tried unplugging the USB devices and it will finish the boot. I won't, however, finish the installworld. boot -s hangs just like normal boot unless I unplug the mouse. After boot -s with ums unplugged, I can fsck if necessary and then mount-a, installworld, etc. with no problems. I can even plug in the mouse, not that it helps because I still have to unplug it when I repoot after mergemaster. I have never experienced a panic or other crash related to USB devices. Only the boot lockup. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Patch for boot-time USB hangs in 4.9-PRERELEASE
On Sat, 2003-09-27 at 06:05, Ian Dowse wrote: > Could people who are experiencing boot-time hangs in 4.9-PRERELEASE > try the following patch to see if it helps? I've had one positive > report so far, but it would be helpful to get more feedback to > determine if this is the right fix to be committed. Works for me (removed usb.c patch, installed kern_fork.c patch). FreeBSD zircon.zircon.seattle.wa.us 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #23: Sat Sep 27 12:40:16 PDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZIRCON i386 /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using pam_ssh with gdm
Volker Stolz wrote: Am 13. Oct 2003 um 16:56 CEST schrieb Joe Kelsey: first try, logging the following to syslog: Oct 13 07:24:30 zircon gdm[186]: Couldn't open session for joek Then, gdm resets and I reenter the password and passphrase. The second time, I get in. Apparantly, now ssh-agent has started, but pam_ssh did not pass along any authentication information, so I have to call ssh-add by hand to actually enter the key information. This means that every time I log in, I have to type my password twice and my passphrase three times. The first thing you're probably experiencing is this: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/45669 Description The pam_ssh module uses popen() to start an ssh-agent for the user during PAM authentication. However, pclose() causes the pam-module to return an error if somebody else already called waitpid(-1,...) because now pclose returns -1 and errno is set to ECHILD (observed with gdm who uses a whole bunch of processes). That fits exactly! I stumbled on a gdm error message in the logs about ssh-agent and child processes. I run 4-STABLE, your PR relates to 5-CURRENT. Has anyone doen anything about fixing this in 4-STABLE? Also, switching to only using my ssh passpharase doesn't tickle the ssh-agent child process bug. Also, why doesn't pam_ssh export my identities into ssh-agent? I still have to do a separate ssh-add to load the keys into ssh-agent. The pam_ssh man page still says that it does this, but obviously it doesn't. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
VersaLogic VSBC-8 Motherboard
I have a VersaLogic VSBC-8 motherboard (PC104 style). I want to write a device driver to deal with the built-in A-D circuitry, among other things. I have plans to take the labpc device driver and heavily modify it for my purposes. My question, has anyone else already done this or something similar? Thanks in advance. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
No Thanks for All the Help
Gee, I ask a seemingly simple question about connecting a very simple driver to the system and all of ZERO people chime in with help. The only thing anyone had to say involved something like "Read and update isa_compat.h" and I can take it from there! However, noone said that or anything else for that matter. It really upsets me because it seems that absolutely *no* documentation exists for how to connect a driver to FreeBSD 4.x. Documentation exists for 3.x and 5.x, but none for 4.x. This mailing list just seems useless to me. /Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
