[PC-BSD Testing] Fwd: usb drive not be able to mount

Hans Ruhe hansruhe1 at gmail.com
Tue Dec 3 07:54:21 PST 2013


---------- Forwarded message ----------
From: Hans Ruhe <hansruhe1 at gmail.com>
Date: 2013/12/3
Subject: Re: [PC-BSD Testing] usb drive not be able to mount
To: Kris Moore <kris at pcbsd.org>


Hi Kris,
Here is the data you asked for.

Also I tested 10.0 stable p4 (I use it right now :-)  and  the driver for
nivdia cards is not working correctly. I tried changing resolution but it
failed several times.

Here is the output of X.org log; the usb output is in the attached file.

    Information    [    29.983] (II) VESA(0): Total Memory: 224 64KB banks
(14336kB)
    Information    [    29.983] (II) VESA(0): <default monitor>: Using
default hsync range of 31.50-48.00 kHz
    Information    [    29.983] (II) VESA(0): <default monitor>: Using
default vrefresh range of 50.00-70.00 Hz
    Information    [    29.983] (II) VESA(0): <default monitor>: Using
default maximum pixel clock of 65.00 MHz
    Information    [    29.983] (WW) VESA(0): Unable to estimate virtual
size
    Information    [    29.983] (II) VESA(0): Not using built-in mode
"1600x1200" (no mode of this name)
    Information    [    29.983] (II) VESA(0): Not using built-in mode
"1280x1024" (no mode of this name)
    Information    [    29.983] (II) VESA(0): Not using built-in mode
"1024x768" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"800x600" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"640x480" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"640x400" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x400" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x240" (no mode of this name)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x200" (no mode of this name)
    Information    [    29.984] (WW) VESA(0): No valid modes left. Trying
less strict filter...
    Information    [    29.984] (II) VESA(0): <default monitor>: Using
hsync range of 31.50-48.00 kHz
    Information    [    29.984] (II) VESA(0): <default monitor>: Using
vrefresh range of 50.00-70.00 Hz
    Information    [    29.984] (II) VESA(0): <default monitor>: Using
maximum pixel clock of 65.00 MHz
    Information    [    29.984] (WW) VESA(0): Unable to estimate virtual
size
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"1600x1200" (hsync out of range)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"1280x1024" (hsync out of range)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"640x400" (hsync out of range)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x400" (hsync out of range)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x240" (illegal horizontal timings)
    Information    [    29.984] (II) VESA(0): Not using built-in mode
"320x200" (illegal horizontal timings)
    Information    [    29.984] (--) VESA(0): Virtual size is 1024x768
(pitch 1024)
    Information    [    29.984] (**) VESA(0): *Built-in mode "1024x768"
    Information    [    29.984] (**) VESA(0): *Built-in mode "800x600"
    Information    [    29.984] (**) VESA(0): *Built-in mode "640x480"
    Information    [    29.984] (==) VESA(0): DPI set to (96, 96)
    Information    [    29.984] (II) VESA(0): Attempting to use 60Hz
refresh for mode "1024x768" (118)
    Information    [    29.984] (II) VESA(0): Attempting to use 60Hz
refresh for mode "800x600" (115)
    Information    [    29.985] (II) VESA(0): Attempting to use 60Hz
refresh for mode "640x480" (112)
    Information    [    29.985] (**) VESA(0): Using "Shadow Framebuffer"
    Information    [    29.985] (II) Loading sub module "shadow"
    Information    [    29.985] (II) LoadModule: "shadow"
    Information    [    29.985] (II) Loading
/usr/local/lib/xorg/modules/libshadow.so
    Information    [    29.986] (II) Module shadow: vendor="X.Org
Foundation"
    Information    [    29.986]     compiled for 1.12.4, module version =
1.1.0
    Information    [    29.986]     ABI class: X.Org ANSI C Emulation,
version 0.4
    Information    [    29.986] (II) Loading sub module "fb"
    Information    [    29.986] (II) LoadModule: "fb"
    Information    [    29.987] (II) Loading
/usr/local/lib/xorg/modules/libfb.so
    Information    [    30.002] (II) Module fb: vendor="X.Org Foundation"
    Information    [    30.002]     compiled for 1.12.4, module version =
1.0.0
    Information    [    30.002]     ABI class: X.Org ANSI C Emulation,
version 0.4
    Information    [    30.002] (==) Depth 24 pixmap format is 32 bpp
    Information    [    30.002] (II) Loading sub module "int10"
    Information    [    30.002] (II) LoadModule: "int10"
    Information    [    30.002] (II) Loading
/usr/local/lib/xorg/modules/libint10.so
    Information    [    30.002] (II) Module int10: vendor="X.Org Foundation"
    Information    [    30.002]     compiled for 1.12.4, module version =
1.0.0
    Information    [    30.002]     ABI class: X.Org Video Driver, version
12.1
    Information    [    30.002] (II) VESA(0): initializing int10
    Information    [    30.002] (II) VESA(0): Bad V_BIOS checksum
    Information    [    30.002] (II) VESA(0): Primary V_BIOS segment is:
0xc000
    Information    [    30.023] (II) VESA(0): VESA BIOS detected
    Information    [    30.023] (II) VESA(0): VESA VBE Version 3.0
    Information    [    30.023] (II) VESA(0): VESA VBE Total Mem: 14336 kB
    Information    [    30.023] (II) VESA(0): VESA VBE OEM: NVIDIA
    Information    [    30.023] (II) VESA(0): VESA VBE OEM Software Rev:
112.8
    Information    [    30.023] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA
Corporation
    Information    [    30.023] (II) VESA(0): VESA VBE OEM Product: GF108
Board - 1071v101
    Information    [    30.023] (II) VESA(0): VESA VBE OEM Product Rev:
Chip Rev
    Information    [    30.025] (II) VESA(0): virtual address = 0x805400000,
    Information        physical address = 0xf1000000, size = 14680064
    Information    [    30.047] (II) VESA(0): Setting up VESA Mode 0x118
(1024x768)
    Information    [    30.154] (==) VESA(0): Default visual is TrueColor
    Information    [    30.154] (==) VESA(0): Backing store disabled
    Information    [    30.154] (==) VESA(0): DPMS enabled
    Information    [    30.154] (==) RandR enabled
    Information    [    30.154] (II) Initializing built-in extension
Generic Event Extension
    Information    [    30.154] (II) Initializing built-in extension SHAPE
    Information    [    30.154] (II) Initializing built-in extension MIT-SHM
    Information    [    30.154] (II) Initializing built-in extension
XInputExtension
    Information    [    30.154] (II) Initializing built-in extension XTEST
    Information    [    30.154] (II) Initializing built-in extension
BIG-REQUESTS
    Information    [    30.154] (II) Initializing built-in extension SYNC
    Information    [    30.154] (II) Initializing built-in extension
XKEYBOARD



2013/12/2 Kris Moore <kris at pcbsd.org>

>  Well, all the USB drives show up as /dev/da*. How about this, plugin
> your device and run "gpart show". Do you see your USB media? Can you send
> me that output, along with "ls /dev/da*"?
>
>
> On 12/02/2013 15:00, Hans Ruhe wrote:
>
>   Hi Kris,
>  I also noticed that it appeared as a Ssci device ?
>  Hope that the Freebsd team can solve the issue,
>
>  Best regards,
>  Hans
>
>
> 2013/12/2 Kris Moore <kris at pcbsd.org>
>
>>  On 12/01/2013 12:12, Hans Ruhe wrote:
>> >
>> > Hello Kris and team,
>> >
>> > I think that the issue lies with the intel chipset or something.
>> > Everytime again, I get this error.
>> >
>> > Next system will be an AMD based system, the new FM2+ socket boards
>> > are very promissing as well as the processor that comes with it, it
>> > handles the memory directly instead via via.
>> >
>> > Also AMD has a much better SATA implementation, SATA 600 has been
>> > around for a few years now, and now as I have this Haswell board
>> > finally Intel supports SATA 600 on all the connectors.
>> >
>> > Here is the reasaon why my Seagate usb drive could not be mounted (see
>> > deamonlog) and I included a systemlog as well.
>> > Hopefully you can solve the issue.
>> >
>> > Best regards,
>> > Hans
>> >
>> >
>>
>>  So, the USB disk doesn't even show up with a /dev/da* device name? I see
>> that it is trying to use XHCI, USB 3.0? We may need to send this over to
>> one of the FreeBSD USB folks, see what the error may be.
>>
>> --
>> Kris Moore
>> PC-BSD Software
>> iXsystems
>>
>> _______________________________________________
>> Testing mailing list
>> Testing at lists.pcbsd.org
>> http://lists.pcbsd.org/mailman/listinfo/testing
>>
>
>
>
> _______________________________________________
> Testing mailing listTesting at lists.pcbsd.orghttp://lists.pcbsd.org/mailman/listinfo/testing
>
>
>
> --
> Kris Moore
> PC-BSD Software
> iXsystems
>
>
> _______________________________________________
> Testing mailing list
> Testing at lists.pcbsd.org
> http://lists.pcbsd.org/mailman/listinfo/testing
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20131203/084838d5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpartetcusbdrivehans.odt
Type: application/vnd.oasis.opendocument.text
Size: 16113 bytes
Desc: not available
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20131203/084838d5/attachment-0001.bin>


More information about the Testing mailing list