Re: Strange text from kernel then detaching USB drive: sldoosstf sd/e v irceemo
On Mon, 2009-06-01 at 13:13 +0400, Александр Деревянко wrote: Hello all ! I got a very confusing messages from kernel then detaching one of my USB external HD (used only for backups): May 29 12:40:08 perforce kernel: GEOM_LABEL: Label ufs/Backup5 removed. May 29 12:40:08 perforce kernel: GEOM_LABEL: Label for provider da0s1 is ufs/Backup5. May 29 12:40:08 perforce kernel: GEOM_LABEL: Label for provider da0s1 is msdosfs/ . May 29 12:40:32 perforce kernel: umass0: at uhub3 port 1 (addr 2) disconnected May 29 12:40:32 perforce kernel: (da0:uGmEaOsMs_-LsAiBmE0L::0 :La0b:e0l) :m sldoosstf sd/e v irceemo May 29 12:40:32 perforce kernel: v(edda.0: May 29 12:40:32 perforce kernel: umGaEsOsM-_sLiAmBE0L::0 :L0a:b0e)l: ruefmso/vBiancgk udpe5v irceem oevnetdr.y May 29 12:40:32 perforce kernel: May 29 12:40:32 perforce kernel: umass0: detached I don't understand messages between umass0: at uhub3 port 1 (addr 2) disconnected and umass0: detached. What does it mean? Best Regards, Alexander Derevyanko. It looks like two messages goung out at the same time, if you combine the letters like this: (da0:u_m_a_s_s_-_s_i_m_0_:_0_:_a_b_e_l_ _:_ _l_o_s_t_ _d_e_v_i_c_e_o :_ _l_o_s_t_ _d_e_v_i_c_e_o _(_d_a_0_ um_a_s_s_-_s_i_m__0_:_0_:_0_:_0_)_: r_e_m_o_v_i_n_g_ _d_e_v_i_c_e_ _e_n_t_r_y (da0:_G_E_O_M___L_A_B_E_L_:_ _L_0_:_0_) _m_s_d_o_s_f_s_/_ _ _r_e_m_ v_e_d_._: __G_E_O_M___L_A_B_E_L_:_ _L_a_b_e_l: _u_f_s_/_B_a_c_k_u_p_5_ _r_e_m_o_v_e_d_. ___ 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
Xorg-6.8.1 / ATI DDC function
Hi,
i would upgrade Xorg-6.7.0 to 6.8.1 in order to
try to correct a seemingly malfunction with ATI
video card and the set {ati,radeon_drv,drm} modules.
The trouble we encounter is a bad setting of
the DCF (Dot Clock Freq.) of the ATI Card at
X startup. The result is a very high Moiré-Effect
with LCD monitors, making them unusable at their
optimal resolution.
We target the drivers because we don't have any
problem with other OS (MS ..)
Of course, changing cables and so one has no effect.
We have tried to setup our proper modeline, at
different frequencies but the driver seem to do
what it want : modeline values don't give expected
monitor frequencies.
For example, this modeline :
1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +/+
should give you a HSF (Hor. Freq.) at 63.9KHz,
but the monitor report a HSF=64.7Khz ; we don't
know how the driver and the video produce this difference.
Generally, you got a little difference arround 0.1~0.2KHz,
but not 0.7, it's a big one.
Other OS have a good behaviour (monitor report
the good frequency, and there's no Moiré Effect with
of course same resolution).
We have upgraded radeon_drv from 4.0.1 to 4.4 with
no effect.
We have emailed to Gatos (ati,radeon_drv), and they advice
to update Xorg to 6.8.2.
We have emailed to some Video veteran, and they don't
understand.
The set {Xorg6.7, ati6.5.6, radeon4.0.1} had a problem
with DDC (no DDC detection), and we hope our solution
is here, Xorg6.8.1+videoDrivers seem to correct
that (release notes).
Well, this problem concern 6 computers, and we need
a solution, no matter to change monitors neither computer.
Has anybody some advice or some information about that ?
Ho, we use FBSD-5.3
Many thanks,
v/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOWTO : Setting Up a mouse + wheel on a traditional ps/2 port in FBSD 5.3
Ted Mittelstaedt wrote: Hey Valery, a few things on this: This only works for mice that support the intellimouse protocol. Simplest way to find out if your mouse supports this is to kill the moused daemon, then issue the command: moused -p /dev/psm0 -t auto -d -f All right, this explain a lot of mis-understand things i found on the net (same parms working for one and not for others) You should NEVER set the protocol for the mouse in either Xfree86 or xorg to anything other than sysmouse, when using FreeBSD. And, if your going to run X you should -always- run moused. Ok, that's what i found. But, why X choose ps/2 when Protocol is set to Auto ? I'm afraid that informations about Protocol sysmouse are very difficult to find. I did not on my side, not even on the net nor on the FreeBSD or X documentations. Note - many wheel mice use a push on the wheel as a second button. Thank I don't understand how your X server got: My X.log whith the 'sysmouse' protocol : (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 when you had configured OptionZAxisMapping X If I knew I could probably tell you why rebooting worked. Sorry, it was the previous version of my log file. (always difficult to write a summary with a lot of pieces) Perhaps a mobo pb., or a forgot of mine, no matter to worry about that. I'm sometimes Aemnesiac too ... :o) Many thanks Ted for your tips. i hope that the whole thing will be interesting for others, sheding a light on this stuff. Just a little thing - to be clean - i found after posting : 2. Parameters /etc/X11/xorg.conf : Section InputDevice # All parms according to previous posts and ... Option Emulate3Buttons Off EndSection Regards, v/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HOWTO : Setting Up a mouse + wheel on a traditional ps/2 port in FBSD 5.3
* Setting Up a mouse + wheel on a traditional ps/2 port in FBSD 5.3 ... and others ... * 1. Must know ps2 bus : the ps/2 bus is mapped as /dev/psm0 /dev/psm0 : support only 'ps/2' protocol ( moused(8) ) moused: map /dev/psm0 as a virtual port to /dev/sysmouse (ie like /dev/ttyv0 is a virtual tty) X : work with the /dev/sysmouse virtual device as input device. xorg.conf : When setting up Protocol to Auto the protocol choosed by X is ps/2 which don't work for me (i don't know how to use a wheel with it without setting up parms for each apps) xorg.conf : setting up Protocol to sysmouse is the best way i find to use my wheel. /sysmouse/ work natively with xterm, Mozilla, and so on. No needs to change anything. 2. Parameters /etc/rc.conf : moused -p /dev/psm0 -t ps/2 /etc/X11/xorg.conf : Section InputDevice Identifier Mouse0 Driver mouse OptionProtocol sysmouse OptionDevice /dev/sysmouse OptionButtons 5 OptionZAxisMapping X EndSection 3. Some tips Testing : 1 - kill the moused daemon 2 - set mouse on console : vidcontrol -m on 3 - launch moused on foreground to see if it's work : moused -f -p /dev/psm0 -t ps/2 4 - press ^C to end 5 - if result are ok, launch moused with your previous parms 6 - set up rc.conf xorg.conf as above. 7 - try to use a lightweight wm like IceWM or twm to test, it respect well X parms. 4. Comments i don't know why, but logoff/login or reboot your computer in order to get this stuff working properly : first time i set this parms, they don't work. Because i was almost sure they must work, i rebooted my computer and they work fine. Perhaps some guy from BSD could explain ... My X.log whith the 'sysmouse' protocol : (**) Option Protocol sysmouse (**) Mouse0: Device: /dev/sysmouse (**) Mouse0: Protocol: sysmouse (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/sysmouse (**) Option BaudRate 1200 (**) Option StopBits 2 (**) Option DataBits 8 (**) Option Parity None (**) Option Vmin 1 (**) Option Vtime 0 (**) Option FlowControl None (**) Option Buttons 5 (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (**) Mouse0: BaudRate: 1200 // ... // (II) 3rd Button detected: disabling emulate3Button 5. Probed apps xterm Mozilla gVim 6. Ref. sysmouse(4), moused(8) /usr/X11R6/lib/X11/doc/README.mouse ... ... no information about sysmouse protocol http://colas.nahaboo.net/mouse-wheel-scroll/#FAQ yours v/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hard disk problem
Hello! I use FreeBSD 4.4 Stable I faced the following problem. Here is a part from messages --- ad2s1e: hard error reading fsbn 32727951 of 16363936-16364175 (ad2s1 bn 32727951; cn 32468 tn 3 sn 18) status=59 error=40 ad2s1e: hard error reading fsbn 32727967 of 16363952-16364175 (ad2s1 bn 32727967; cn 32468 tn 3 sn 34) status=59 error=40 What sort of problem with my hard disk Is it critical? Yours sincerely, Valery ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
