Pls help me with my first Debian install on the BB...

Robert Nelson wrote:

It's good to hear your making progress. I'll run some more tests
tonight and update the wiki.

Which D-Link adapter? and does it work with angstrom. (for the native
debian installer i need to build all modules internal, so i may have
missed one..)

  Hi Robert,

   thanks for your continued assistance.

The USB<=> WiFi dongle is D-Link DWL-G122 that normally I use with an old laptop to connect to Internet via a
modem/router/Access Point that I have in the basement. It would be wonderful if it could be supported by the Debian
installer, that would save me the big hassles to move everything related to the BB to the basement, at cable distance
from that router...

Regards
Alberto

Hi Alberto,

Give this uImage a try, I enabled every possible usb-wifi adapter
(along with the previous usb-net adapters). I'm not sure how the
debian-installer works in a wifi environment. (i've never tried it..)

cd /media/disk/
wget http://www.rcn-ee.com/deb/kernel/CC-v2.6.27-2a3408b-oer4
mv CC-v2.6.27-2a3408b-oer4 uImage

Regards,

FYI: Did some more tests with 2.6.27-oer4, basically the reason i
didn't have the vram:2M,vram:4M on the debian wiki, they don't seem to
work with DSS1 (2.6.28 with DSS2 will probally work better).

Tested with 2.6.27-oer4 (DSS1) that i uploaded yesterday.

video=omapfb:mode:1280x720@60

omapfb: using mode 1280x720@60
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized

video=omapfb:vram:2M,vram:4M:mode:1280x720@60

omapfb: using mode 1024x768@60
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized

video=omapfb:vram:4M:mode:1280x720@60

omapfb: using mode 1024x768@60
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized

maybe order?

video=omapfb:mode:1280x720@60:vram:2M,vram:4M

io scheduler cfq registered (default)
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized
(aka didn't report back mode)

maybe ,/:

video=omapfb:vram:2M:vram:4M:mode:1280x720@60

omapfb: using mode 1024x768@60
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized

Weird... :wink: Probably just have to wait for 2.6.28..

the vram: params are for DSS1, DSS2 uses it's own allocation.

regards,

Koen

Alberto -

If you want to try the latest 2.6.28-rc, it's now posted on my site.
it doesn't seem to be suffering from the usb resets like the previous
RC kernels, and is now 56% the way thru a native debian install. (all
wifi-usb/eth-usb modules are built-in just like on the 2.6.27 i posted
yesterday)

http://www.rcn-ee.com/deb/kernel/CC-v2.6.28-rc6-75b7ae0-oer3

Koen -

Does Toni, have a nice writeup on the DSS2 settings, or is it buried
in the code?

I attempted, video=omapfb:mode:1280x720@60

But according to dmesg, it skipped that information and set the
default as 1024x768

Regards,

DSS2 only allows compile modes at the moment.

regards,

Koen

----- snip -----

Robert,

  many thanks. I tried your 2.6.27, and indeed seems to recognize the
D-Link dongle, but then it says that it needs an additional non-free
module, named RT73.bin, which frankly I don't know how to put in that
kernel. I found some source code for it, but of course I cannot
compile it on the PC with a Pentium processor, and on the BB I don't
have yet a working Linux to use for the compilation. Somebody
suggested to use QEMU on the PC to cross compile that RT73 module, but
I haven't been able to have QEMU running, as it gives me strange (to
me...) error messages. Don't forget that I am totally a newcomer, as
far Linux in general is concerned.

As a last resort I tried also with a Zyxel dongle,. This time the
additional module needed was different, it asked for something named
z1211/z1211b_ub .... no joy either....

The ideal would be to have a uImage with one (or both) of those
modules already built-in....

TNX
Alberto

Darn.. I'm not sure how we are going to copy that *.bin file to the SD
card before we format it.

Due to this situation, I'd recommend you use the QEMU method, it's
slower, but you can utilize a PC that's already net connected. After
which copy the needed *.bin files onto the sd card and boot the
beagleboard.

Regards,

have yet a working Linux to use for the compilation. Somebody
suggested to use QEMU on the PC to cross compile that RT73 module, but
I haven't been able to have QEMU running, as it gives me strange (to
me...) error messages. Don't forget that I am totally a newcomer, as
far Linux in general is concerned.

And i just happened to notice this, what error are you getting with
QEMU? Debian Lenny and Ubuntu 8.10 work with out any tweaks in my
testing (amd64). (8.04 and lower had to atleast rebuild from svn..)

Regards,

Robert,

   this is the log of the errors I get when trying to start QEMU under
Kubuntu 8.04.
A friend suggested that I *must* install Debian instead of Kubuntu for
what I want to do.
Probably I will follow his advice, but I am also interested in your
opinion.

Thanks
Alberto

  this is the log of the errors I get when trying to start QEMU under
Kubuntu 8.04.
A friend suggested that I *must* install Debian instead of Kubuntu for
what I want to do.
Probably I will follow his advice, but I am also interested in your
opinion.

Thanks
Alberto

-------------------------------------------------------------------------

root@Kubuntu-KDE3:/home/i2phd/debian-armel# qemu-system-arm -M
versatilepb -kernel vmlinuz-2.6.26-1-versatile -initrd
initrd.gz -m 256 -hda /dev/sdb -append "root=/dev/ram mem=256M"
No protocol specified
No protocol specified

     =======================| DirectFB 1.0.1 |

          (c) 2001-2007 The DirectFB Organization (directfb.org)
          (c) 2000-2004 Convergence (integrated media) GmbH
        ------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-04-08 15:15)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
variable.
(!) DirectFB/Core: Could not initialize 'system' core!
    --> Initialization error!
Could not initialize SDL - exiting
root@Kubuntu-KDE3:/home/i2phd/debian-armel#

(K)ubuntu is fine for doing this work, but you will have to recompile
qemu from trunk, the default version has a habbit of locking up
whenever qemu tried to fsck an sd card. (debian lenny just has a more
recent version that works vs 8.04).. (or you could just pull the
packages from intrepid)

Could not initialize SDL - exiting

Looking thru google, can you start 'xeyes' or 'xterm' from the command line?

Regards,