Debian image

Hi,

I tried to install debian tonight (according to the elinux page) but I
failed for two reasons:
- my pegasus network dongle was not identified. I've rebuild the
kernel with pegasus build into it, but still when booting the
interface would not come up, let alone get an IP address
- my PS/2 keyboard and mouse which are connected to the beagle using a
PS/2 to USB adapter was not found (maybe the hub was not iterated, I
have not really an idea what causes this, all is build into the kernel
and kbd and mouse work with angstrom without requiring modules).

Still I would like to run debian. So my questions:
Has someone an idea on how to resolve this.
And if possible can someone make an image available that I could just
dump on an SD card (or a partition of the card).

Thanks alot for your help!

Frans

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.

http://elinux.org/BeagleBoardDebian#QEMU_install_method_via_debian-installer_.28emulated_arm_core_via_Desktop_PC.29

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,

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

Regards,

A simple question : have you tried other USB device ?
Which revision is your beagleboard ? Is the usb device configured as
host (see elinux pages) and not gadget as it is by default ?
You shall use a high-speed USB HUB because they are some trouble with
full speed devices.

Anyway u can also put dmesg log when plugging one of these devices.

I may put somewhere a debian-armel img as a ~800 Mo tar.gz archive .

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).
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.

I will also give it a try with the oer17 kernel and send a pastebin.
Again something for tomorrow.

Best regards, frans.

...well, it's not just you and it's not just Debian...

I have been trying out lots of different kernels and distributions on
my B5 board.

It's a total crap shoot to see if my hub, Dell keyboard, Dell mouse
and Asix 10/100 Ethernet are going to all show up or not...

Again, there must be some section of the .config that is there in one
kernel and not in another.

- dan

Hi,

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

Regards,

Hi,

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

Regards,

Hey Robert,

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...

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=blobdiff;f=drivers/net/usb/asix.c;h=aee6f1af983c858b2caec0219010052f8fbd9d1e;hp=de57490103fcd05e58a8610d7fb77b3dbc0ffc20;hb=f52873756ae021cb312ce24248ef21af9c7daa0b;hpb=b42067185d9ea1dc6de51fa6245e1b4969b6cbad

Maybe it's time to pull in some of the 2.6.28 stable patches.. (or
mostly usb devices..)

Regards,

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.

Regards,

Hi,

> 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/l

> 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-r17http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=df4…

Not that strange. I just phrased it wrong :slight_smile:
I used your kernel, then moved to .15 then realised of course pegasus
was not compiled in, so I changed the config file to add pegasus into
the kernel, build that and tested on angstrom. No pegasus module
needed.
Then I went booting that kernel the the lenny initrd, but the network
does not come up.

> 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.

I think I tried that, but will try some more later today.

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

Will look that up too.

Thanks alot, Frans

Robert:
  Could you point me to a place that tells how to do the steps you
suggest? I'm new to this and I'm finding it's taking a long time to
get my arms around all the tools that are used.

--Mark

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

patch-bb-2.6.28.sh (4.13 KB)

Some answers on the questions I promised to get back on:

My pegasus device lists as
Bus 001 Device 003: ID 083a:b004 Accton Technology Corp.
it works under angstrom.

If I boot with
http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-79d042a-oer17
the pegasus dongle is not recognized (at least the led does not
lighten).
I've tried plugging into
- ehci port directly (I have rev C2 hw)
- ehci port through hub
- otg port through hub
- otg port directly (not sure if that is powerwise ok, but decided to
give it a try anyway).
No indication of any activity, not on the dongle, not in the boot log

A pastebin of the boot log is at http://pastebin.com/m31c0eaaf

I've also put the same image on another card which boots angstrom.
This one recognizes the card and starts the dongle.
boot log for that one is at:
http://pastebin.com/m6b5828ec

For now I am out of ideas....

Frans

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,

Hi Robert,

Could be. This specific type of card indeed gave me a problem. It is a
Kingston 4GB SDHC class 6 card. I hav e two of them and they both have
this problem (although they work fine on opensuse)
I've worked around this with a timing patch
http://groups.google.nl/group/beagleboard/browse_thread/thread/80671d3f08315b65#
However, I assumed it would not be a problem with the debian installer
as it uses an initrd.
(actually I would like to use the card only for booting and install on
a usb hard disk.
Note sure why it would want to do something with the sd card at all.
I'll try with another card.

Frans

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 )

Regards,

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,