I had a similar problem on my nVidia AMD 64 set up, but it went away
on non nvidia mother boards. I analyzed the problem was because the
nvidia motherboard uses proprietary firmware that needs to loaded by
the kernel boot process. The firmware isn't part of a true OSS
distro like Dyne. Maybe you have a similar problem.
Have you tried it on other systems???
Richard Hamel-Smith wrote:
> Ok, this is what I get when I connect my USB stick
> .......................................
>
> usb 2-2: USB disconnect, address 2
> usb 2-2: new full speed USB device using uhci_hcd and address 3
> usb 2-2: configuration #1 chosen from 1 choice
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 3
> usb-storage: waiting for device to settle before scanning
> Vendor: M-SysT5 Model: Dell Memory Key Rev: 5.04
> Type: Direct-Access ANSI SCSI revision: 00
> SCSI device sda: 249599 512-byte hdwr sectors (128 MB)
> sda: Write Protect is off
> sda: Mode Sense: 45 00 00 08
> sda: assuming drive cache: write through
> SCSI device sda: 249599 512-byte hdwr sectors (128 MB)
> sda: Write Protect is off
> sda: Mode Sense: 45 00 00 08
> sda: assuming drive cache: write through
> sda: sda1
> sd 0:0:0:0: Attached scsi removable disk sda
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> usb-storage: device scan complete
>
> ..........................................................
> are you seeing anything like that?
> just after you insert the USB stick,
> type dmesg in a xterm
>
> If you get output similar to the above, then your USB stick is recognised
> If not, ...
>
> the /etc/fstab file on my system has the following entry for the USB
> stick, which
> by the way, is called /dev/sda1
>
> /dev/sda1 /mnt/usb vfat defaults,user 0 2
>
> This line means that the USB stick is mounted with a VFAT filesystem,
> which I believe, is the
> filesystem Windows95 originally came with.
>
> Anyhow, to mount it manually, you would use
>
> mount -t vfat /dev/sda1 /mnt/usb
>
> But Dyne:bolic does all this automatically for you.
>
> Now, I know you have Dyne:bolic version 2.2 but did you try version
> 2.1? I ask because I have come across some other problems with 2.2,
> which did not occur with 2.1.
> Perhaps, your USB stick will be recognised with 2.1. If you have the
> bandwidth, I'd suggest downloading 2.1.
> The only real difference I've noticed between 2.1 and 2.2 is that 2.2
> includes some VoIP apps. But you can always download Skype for Linux
> instead. So you won't really lose anything going to 2.1.
>
> And another thing, does your USB stick work on any other Linux distro,
> like Knoppix perhaps? Does it work under Windows, do you know? Knoppix
> is generally accepted as being the most hardware compatible version of
> Linux. It's what I fall back to if I get problems with hardware.
>
> Can you try another USB stick? Or is the problem with all USB sticks?
>
> About formatting the USB stick, I've never had to do this personally.
> But it's easy enough to do. To format your USB stick with a VFAT
> filesystem, type
>
> mkfs.vfat /dev/sda1
>
> Of course, It will wipe any files there when you do this.
>
> Hope this helps,
> Richard
>
>
> On 10/23/06, Karlo Prstac <darion696@???> wrote:
>> Well i typed into the xTerminal
>>
>> [d:b]: dmesg|tail
>>
>> and this popped out:
>>
>>
>> [drm]Setting GART location based on old memory map
>> [drm]LOading R300 microcode
>> [drm]Writeback test succeeded in 1 usecs
>> FAT:bogus number in reserveds sectors
>> VFS:Can't find a valid FAT file system on dev sda1
>>
>>
>> What does that mean?
>> And can i format my stick from dyne:bolic,because i tried form windows adn
>> nothing happened.
>> If yes,from where?
>> 2006/10/22, Richard Hamel-Smith <richardhamelsmith@???>:
>>> right-click
>>> from the menu, select xterm
>>> type
>>>
>>> dmesg
>>>
>>> you should see a bunch of messages
>>>
>>> to read them slowly, use
>>>
>>> dmesg | less
>>>
>>> Richard
>>>
>>>
>>> On 10/22/06, Karlo Prstac <darion696@???> wrote:
>>>> Well,AFAIR it worked with dyne:bolic 1.2,not sure though...
>>>> And where can i find the dmesg command?
>>>>
>>>> 2006/10/22, Richard Hamel-Smith <richardhamelsmith@???>:
>>>>> it means that your usb device was not recognised by the kernel
>>>>> since the usb device itself was not recognised, no filesystem could be
>>>>> found on it
>>>>> the message suggests you look into the output of the dmesg command to
>>> see
>>>>> if
>>>>> that can help
>>>>> so post the output from the dmesg command and maybe someone can
>>> indicate
>>>>> what
>>>>> you need to do
>>>>>
>>>>> did this particular usb device work with any previous versions of
>>>>> dyne:bolic?
>>>>>
>>>>> Richard
>>>>>
>>>>> On 10/22/06, Karlo Prstac <darion696@???> wrote:
>>>>>> Hey I get this message when i try to acces my usb in dyne:bolic 2.2:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Mounting /mnt/usb
>>>>>> mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
>>>>>> missing codepage or other error
>>>>>> In some cases useful info is found in syslog - try
>>>>>> dmesg | tail or so
>>>>>> Mount failed
>>>>>>
>>>>>> Done
>>>>>> There was one error.
>>>>>>
>>>>>>
>>>>>> What does that mean?
>>>>>> Please help fast!
>>>>>> --
>>>>>> Karlo Prstac
>>>>>>
>>>>>> Use dyne:bolic!
>>>>>>
>>>>>> Dyne:bolic forum: www.dynebolicforum.tk
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> dynebolic mailing list
>>>>> dynebolic@???
>>>>> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>>>>>
>>>>
>>>>
>>>> --
>>>> Karlo Prstac
>>>>
>>>> Use dyne:bolic!
>>>>
>>>> Dyne:bolic forum: www.dynebolicforum.tk
>>>>
>>>>
>>> _______________________________________________
>>> dynebolic mailing list
>>> dynebolic@???
>>> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>>>
>>
>>
>> --
>> Karlo Prstac
>>
>> Use dyne:bolic!
>>
>> Dyne:bolic forum: www.dynebolicforum.tk
>>
>>
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>
::
Re: [dyne:bolic] Need help with the…
