Hello List, hello Alain,
I recently wanted to download the current udpcast-kernel .config but the link on the Homepage returns 404 for me: http://udpcast.linux.lu/download/udpc-config-2.6.32-rc5.txt
Additionally, I wanted to test some stuff with a USB-Memory-Stick but I could not manage to mount the filesystem (fat32) on the stick. I did not even see messages in dmesg regarding the stick being connected. I tried to test with a nonmodified udpcast-cd-image. I fear that this problem is not related to udpcast-framework but rather related to missing kernel or other framework features. However, after googling I am still none the wiser. I hope that someone can show me the right direction on where to investigate, so I can have full USB-Memory-Stick support.
Thanks & Regards Jens
On 09/12/09 11:29, Jens Breuer wrote:
Hello List, hello Alain,
I recently wanted to download the current udpcast-kernel .config but the link on the Homepage returns 404 for me: http://udpcast.linux.lu/download/udpc-config-2.6.32-rc5.txt
It's now up.
Additionally, I wanted to test some stuff with a USB-Memory-Stick but I could not manage to mount the filesystem (fat32) on the stick. I did not even see messages in dmesg regarding the stick being connected. I tried to test with a nonmodified udpcast-cd-image.
And, what was the outcome?
I fear that this problem is not related to udpcast-framework but rather related to missing kernel or other framework features. However, after googling I am still none the wiser. I hope that someone can show me the right direction on where to investigate, so I can have full USB-Memory-Stick support.
Thanks & Regards Jens
It more looks like a problem with the USB chipset module (uhci-hcd) than the VFAT or fat32 module
Regards,
Alain
On Wed, Dec 9, 2009 at 1:42 PM, Alain Knaff alain@knaff.lu wrote:
On 09/12/09 11:29, Jens Breuer wrote:
Hello List, hello Alain,
I recently wanted to download the current udpcast-kernel .config but the link on the Homepage returns 404 for me: http://udpcast.linux.lu/download/udpc-config-2.6.32-rc5.txt
It's now up.
Thank you. :)
Additionally, I wanted to test some stuff with a USB-Memory-Stick but I could not manage to mount the filesystem (fat32) on the stick. I did not even see messages in dmesg regarding the stick being connected. I tried to test with a nonmodified udpcast-cd-image.
And, what was the outcome?
The stick has not been recognized by the kernel, I think. At least nothing showed up in the logs and "fdisk -l" did not show anything. Yes, that is not really helpful information but I will test more and share my results with you.
I fear that this problem is not related to udpcast-framework but rather related to missing kernel or other framework features. However, after googling I am still none the wiser. I hope that someone can show me the right direction on where to investigate, so I can have full USB-Memory-Stick support.
It more looks like a problem with the USB chipset module (uhci-hcd) than the VFAT or fat32 module
Ok, I am going to investigate things from this point of view first. I had the feeling that I needed something like hotplug or related stuff. However, I am not a Kernel-Guru so I depend on the expertise of people who know more than I do and hopefully you put me into the right direction.
Thanks & Regards Jens
Found out what is going on:
- in newer kernels, you need to load an additional modules (ums-*.ko) for many USB storage devices. In older kernels the device-specific functionality in these modules used to be part of usb-storage, now it is a separate module. So you need to manually modprobe that module as well.
- The dialog of "disk controller modules" only proposes PCI or on-board devices (mostly for SCSI and SATA), but not USB...
- ... however the creation of the device nodes (/dev/sda*, /dev/sdb*) is only performed if a disk controller module has been selected
So, for now, the workaround is:
- manually modprobe the appropose ums-*.ko module:
modprobe ums-cypress.ko
It may fail on first attempt (due to a weird kernel or busybox bug), in that case, just try again.
- enter the "disk controller module", and pick your PATA or SATA controller (you need to pick something, or else no device nodes will be created, even though the actual module has already been loaded manually)
- near the end, /dev/sdb should appear (/dev/sda being the built-in disk)
For the next release, I'll change it such that now the ums* modules also show up in the list of disk controller modules, and that device nodes are created unconditionally.
Regards,
Alain
-
Alain Knaff -
Jens Breuer