Hi Frans,
Couple questions, what
For comparison, this is one of the pegasus based usb-ethernet devices
i regularly test my kernels with. (it's at work, so i can't test it at
the moment.) http://www.newegg.com/Product/Product.aspx?Item=N82E16833156133
but i haven't had those issues you are seeing with:
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-9a6536c-oer8
or
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-79d042a-oer14
(both of these are exactly the same as angstrom's defconfig, except
for i've enabled all usb-Ethernet modules to be built-in)
Note all of the *.deb based images (except for oer17) the usb-Ethernet
modules are built as external modules.
What kernel are you using for the native install procedure?
Sorry, i don't have the capabilities of uploading one of my debian
images, but you can do the qemu based native install to populate your
sd card.
As far as your usb/ps2, i'm not sure, let me dig a little into
menuconfig and roll a CC-v2.6.28-79d042a-oer17
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Hi,
Didn't think i was that tired (reread my reply..)...
Frans give this uImage/kernel a try, use minicom, dump your complete
boot log and post to pastebin. I've enabled some USB message debugging
along with forcing the beagle in host mode.
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-79d042a-oer17
On Thu, Mar 26, 2009 at 8:00 AM, Frans Meulenbroeks
<fransmeu...@gmail.com> wrote:
>
> Thanks for all replies.
>
> To answer some of the questions:
> My board is a rev C2 one.
> I think I tried with the hub both on the EHCI port as well as on the
> OTG port. The hub is definitely enumerated.
> I'll re-check both ports tomorrow.
>
> Also it is a high speed hub, both pegasus and kbd+mouse work with
> angstrom 2.6.28-r15. I've also tried installing debian with this
> kernel, but to no avail (also not after compiling the pegasus driver
> in).
Source wise, this would match :
http://www.rcn-ee.com/deb/kernel/beagle/lenny/v2.6.28-79d042a-oer15/linux-image-2.6.28-oer15_1.0lenny_armel.deb
> Under angstrom I need no additional modules for pegasus or kbd, but if
> I use that same kernel with the lenny initrd the pegasus adapter led
> remains off and the kbd and mouse are not working.
Strange, since they aren't actually builtin till 2.6.28-r17
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=df49f5e7f5a14c6736806f3163787608c958f4c9
> I will also give it a try with the oer17 kernel and send a pastebin.
> Again something for tomorrow.
>
> Best regards, frans.
>
One note, I had a little bit of time this morning to mess around with
this usb device again (pegasus II). At times it doesn't correctly
load, (mac addresss would be 00:00:00:etc...) unplugging and
replugging would fix it.
Dan -
What asix based device do you have? I just picked up this usb300m
linksys model:
Bus 002 Device 006: ID 0b95:7720 ASIX Electronics Corp. AX88772
>
> Dan -
>
> What asix based device do you have? I just picked up this usb300m
> linksys model:
>
> Bus 002 Device 006: ID 0b95:7720 ASIX Electronics Corp. AX88772
>
> Regards,
>
Note: This works fine for me with kernel:
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-79d042a-oer14
I am gonna make you cry...
Here is my Asix 10/100:
http://www.alibaba.com/product-gs/205667152/3_Port_Hub_with_Ethernet_adapter.html
3-port hub with Ethernet!
...all I did was add the AX88772a product ID to the end of the
drivers/net/usb/asix.c device driver:
// ASIX 88772a
USB_DEVICE(0x0db0, 0xa877),
.driver_info = (unsigned long) &ax88772_info,
},
Cool! good to hear!
PS. Looks like it was added to the 2.6.28.(8) stable branch...
Maybe it's time to pull in some of the 2.6.28 stable patches.. (or
mostly usb devices..)
Yeah, I saw it there.
I am having a hard time navigating all of the various Beagleboard 'git' trees.
I think that the OE and Angstrom userland build systems are great. I
am seeing a lot of interest in Android.
...I am just used to building the kernel the old fashoned way.
I would really like to find the latest and greatest with defconfig's
for both Angstrom and Android.
- dan
Hi Dan,
Tony Lindgren's tree is nice for a baseline image.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary
Just add Koen's defconfig, along with his patches listed in
openembedded to get DSS2.
Hi Mark,
Currently I pull stuff directly from the Angstrom tree, I do have an
example listed here.
http://elinux.org/BeagleBoardDebian#Rebuilding_.2A.deb_Kernel.27s_from_Source
It's a little dated, but gives you a good idea how to rebuild Koen's
angstrom kernel from source.
Basically use Tony's Omap tree as a base (
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary
)
Add Angstrom's patches and defconfig to get DSS2 / etc...
I'm also attaching my current 2.6.28-oer17 patch script used to setup
rcn-ee.com/deb to give you some ideas.
ps: patch oe-release.diff is just used to keep the deb name somewhat
sane/shorter..
Regards
Thanks for the data Frans!
This might be an mmc card problem.
Looking at (the failed one) : http://pastebin.com/m31c0eaaf
Line 343:
mmcblk0: error -110 transferring data
end_request: I/O error, dev mmcblk0, sector 7896960
If you look at the (working one): http://pastebin.com/m6b5828ec
The device doesn't get registered till after the mmcblk is mounted.
334: mmcblk0: mmc0:f1a7 SD02G 1.91 GiB
337: pegasus 2-2.2:1.0: setup Pegasus II specific registers
Since the kernel is the same, who is the manufacture of this card?
(for comparison)
Regards,
Okay thats weird, I'm subscribed and usually these messages end up in
my inbox...
It shouldn't need access till the partition stage, this part of the bootargs:
ramdisk_size=8192 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,8M
during the install phase, should force it to use the initrd we've
loaded into ram.
Note, i haven't tested this method when the sd card is fully
partitioned. (usually just one 50Mb fat32 partition )
Hi Frans,
Nope that works fine.. (extra partitions)
Saved the boot log here: http://pastebin.com/m7f0ce81a
bootargs are on line 54 (same as yours 49: http://pastebin.com/m31c0eaaf)
mmc is init: on line 340 (yours: line 333)
The only real difference is:
mmcblk0: error -110 transferring data
end_request: I/O error, dev mmcblk0, sector 7896960
Regards,
This is the one i'm running on my c2 hardware, boots uImage off a mmc
card, using usb-otg, with usb harddrive(root for fedora), mostec
ethernet, etc..
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-79d042a-oer17
Note: i haven't tested any of the 2.6.29's on c2 hardware yet, on
rcn-ee.com, just b* hardware..
Did updating uboot on the C2 board from 2008.10 to 2009.01 help with
booting debian in my previous message?
Hi Frans,
Nope, nothing in debian's initrd is beagle/omap specific, just make
sure to buildin your ethernet modules.
rev c uboot works fine on rev b.
On Apr 2, 2009 4:11 AM, "Frans Meulenbroeks" <fransmeu...@gmail.com> wrote:
Already gave Robert a private reply, but want to mention this to the
mailing list too:
- Make sure you use the right u-boot. Versions for rev B and rev C
differ and a rev B u-boot will not enable the EHCI port. Also there
might be issues with the OTG port.
- if you get SD errors, use the latest angstrom 2.6.28 kernel. This
one has a patch for those error -110
- make sure that your ethernet modules is build in. Again that is the
case with the latest angstrom 2.6.28 kernel
I'm working on 2.6.29, already added the sd/mmc timing fix, will add
the modules as well, probably this evening.
My installer starts and both ethernet and the kbd are recognized.
Didn't have time yet to actually do a full install.
Frans.
On Apr 1, 10:59 pm, Robert Nelson <robertcnel...@gmail.com> wrote: > > Are there modules in the ini...
> Robert Nelsonhttp://www.rcn-ee.com/
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subs...