>> Of course: you have 8MB of flash, so there's plenty of space for a jffs
>> partition. In my case, there's around 128KB of flash left (of the 2MB).
> Wow. I didn't know the 700 had so little flash.
Since it has an IDE drive, that's actually quite enough: it only needs
to be able to hold the ke
On Sat, 2008-07-12 at 01:13 -0400, Stefan Monnier wrote:
>
> Of course: you have 8MB of flash, so there's plenty of space for a jffs
> partition. In my case, there's around 128KB of flash left (of the 2MB).
Wow. I didn't know the 700 had so little flash.
> For starters, I don't need dropbear i
> USBs are now at at least 8 GBytes which means a pretty healthy linux
> system could be up and running once the USB image is booted !
The USB I used until recently was 200GB.
Stefan "USB != flash"
___
openwrt-devel mailing list
openw
On Sat, 12 Jul 2008, RHS Linux User wrote:
> If I understand your point about the 3rd option?
>
> 1. The driver(s) could either be in the kernel,
>
> 2. In the greater kernel image (flash chip) as drivers loaded after
> kernel boot.
>
> 3. On some removeable device (USB or whatev
Hi All,
If I understand your point about the 3rd option?
1. The driver(s) could either be in the kernel,
2. In the greater kernel image (flash chip) as drivers loaded after
kernel boot.
3. On some removeable device (USB or whatever).
If the drivers are capable of being loa
On Sat, 12 Jul 2008, RHS Linux User wrote:
>
> Hi All,
>
>IMHO there is a VERY VERY important point being discussed here.
>
>1. Should the kernel be VERY small with drivers and everything possible
> loaded during boot as needed.
yes.
this has been another installment of "simple answers t
On Sat, 2008-07-12 at 10:15 -0400, RHS Linux User wrote:
> Hi All,
>
>IMHO there is a VERY VERY important point being discussed here.
>
>1. Should the kernel be VERY small with drivers and everything possible
> loaded during boot as needed.
>
>or
>
>2. Should the kernel "have i
Hi All,
IMHO there is a VERY VERY important point being discussed here.
1. Should the kernel be VERY small with drivers and everything possible
loaded during boot as needed.
or
2. Should the kernel "have it all"?
For me the answer is obvious and VERY IMPORTANT.
If we ch
>> a 1.8MB .trx is already too big to be able to get a jffs partition.
> I seem to do it just fine here:
[...]
> /dev/mtdblock35.9M624.0k 5.3M 10% /jffs
Of course: you have 8MB of flash, so there's plenty of space for a jffs
partition. In my case, there's around 128KB of fla
On Sat, 2008-07-12 at 01:03 -0400, Stefan Monnier wrote:
>
> I can't remember doing anything special for that. For what it's worth
> those nodes are created by `hotplug2' (which is a udev replacement for
> embedded devices), so make sure you have it installed in your /rom.
Yeah, they do seem to
>> I did a few weeks ago.
>> http://article.gmane.org/gmane.comp.embedded.openwrt.devel/1599
> FWIW, your patches have the same result on my configuration,
> where /dev/sda* never shows up. I tend to suspect that your (really
> full) /rom has a package which is enabling the creation of these devi
On Fri, 2008-07-11 at 16:01 -0400, Stefan Monnier wrote:
> > Would you care to post your /sbin/mount_root here?
>
> I did a few weeks ago.
> http://article.gmane.org/gmane.comp.embedded.openwrt.devel/1599
Here's an alternate implementation as per our discussion. In this case,
do the USB (or IDE)
On Fri, 2008-07-11 at 23:55 -0400, Stefan Monnier wrote:
>
> a 1.8MB .trx is already too big to be able to get a jffs partition.
I seem to do it just fine here:
# df -h
FilesystemSize Used Available Use% Mounted on
tmpfs14.6M 32.0k 14.6M 0% /tmp
> Why "just"? What else are you putting on the rom? My .trx is currently
> just under 2MB.
a 1.8MB .trx is already too big to be able to get a jffs partition.
My .trx is currently 1.9MB, including all the modules needed for a USB
root and an IDE root (tho I only care about the IDE root ones).
>
On Fri, 2008-07-11 at 16:01 -0400, Stefan Monnier wrote:
>
> I did a few weeks ago.
> http://article.gmane.org/gmane.comp.embedded.openwrt.devel/1599
FWIW, your patches have the same result on my configuration,
where /dev/sda* never shows up. I tend to suspect that your (really
full) /rom has a
On Fri, 2008-07-11 at 23:00 -0400, Stefan Monnier wrote:
>
> You may be right, but one way or another in order to mount an external
> drive, I need to have those kernel modules in the flash, whether in the
> /rom or the /jffs filesystems.
Agreed.
> So maybe if I don't put them in the
> /rom, I j
> You noted in one of your past post(s) that you actually ran out of room
> on in your flash image for a jffs partition. I think I can see why.
> You have to put all of the needed kernel modules (usb-storage, scsi,
> etc.) into it.
You may be right, but one way or another in order to mount an ext
Stefan,
You noted in one of your past post(s) that you actually ran out of room
on in your flash image for a jffs partition. I think I can see why.
You have to put all of the needed kernel modules (usb-storage, scsi,
etc.) into it.
I guess the benefit of doing the pivot_root to the USB storage *
On Fri, 2008-07-11 at 16:01 -0400, Stefan Monnier wrote:
>
> I did a few weeks ago.
> http://article.gmane.org/gmane.comp.embedded.openwrt.devel/1599
Cool. Let me give that a try. I suspect by /dev/sda* entries will not
be created when that script runs, but let me try it out and modify as
neces
> Would you care to post your /sbin/mount_root here?
I did a few weeks ago.
http://article.gmane.org/gmane.comp.embedded.openwrt.devel/1599
> Yeah. I have already built and installed my own firmware, but having to
> do that on each "debugging" pass is a real PITA, especially given you
> trash yo
On Fri, 2008-07-11 at 14:18 -0400, Stefan Monnier wrote:
>
> Could be, indeed. I do this kind of dance in /sbin/mount_root instead,
> which runs before rcS and the `hotplug' daemon properly creates the
> device nodes for me.
Hrm.
> But IIRC the hotplug daemon running at the time of
> mount_root
>> IIRC it may appear somewhere under /dev/discs or somesuch (it appears
>> under /dev/sda* on my 2.6 kernels, but IIRC it was different with the
>> 2.4 kernel).
> I think that depends on some service being available to create devices
> nodes, like devfs or udev. At rcS time nothing of the sort e
On Thu, 2008-07-10 at 23:13 -0400, Stefan Monnier wrote:
>
> IIRC it may appear somewhere under /dev/discs or somesuch (it appears
> under /dev/sda* on my 2.6 kernels, but IIRC it was different with the
> 2.4 kernel).
I think that depends on some service being available to create devices
nodes, l
> 31 0256 mtdblock0
> 31 1 7872 mtdblock1
> 31 2 7092 mtdblock2
> 31 3 5888 mtdblock3
> 31 4 64 mtdblock4
>8 01003520 sda
>8 11003504 sda1
> No /dev/sda* entries show up though. I guess I need udev for dynamic
On Thu, 2008-07-10 at 21:38 -0400, Stefan Monnier wrote:
>
> Have you tried "ehci-hcd" (i.e. with a dash rather than an underscore)?
Doh! "Just because it's written on the Internet does not necessarily
make it true", and my corollary: "even more so for a Wiki page".
I just assumed something a l
> All of the above listed modules load just fine except ehci_hcd. It
> gives an error:
> insmod: Loading module failed: No such file or directory
Have you tried "ehci-hcd" (i.e. with a dash rather than an underscore)?
Stefan
___
openwrt-deve
I'm trying to follow the instructions at
http://wiki.openwrt.org/UsbStorageHowto#head-48a82837822ffa8e49a817d3800f3f02c6bd7fb4
to have my ASUS WL-500g Premium boot from the usb storage device I have
plugged in. I have usb storage working. I can mount the device on /mnt and
all that is peachy.
27 matches
Mail list logo
