• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3] 4 5 6
31  Linux Stuff / Kernel / Re: uap8xxx 802.1X / Radius on: October 04, 2010, 10:28:14 AM
I believe you would have to modify the firmware to make that possible.
32  Hardware and U-Boot firmware / U-Boot stuff / Re: plug with only green led on and no serial connection...I need a resurrection on: October 04, 2010, 10:24:55 AM
@Dammuozz, I don't know if Marvell>> is from U-Boot or even lower-level boot software. Can someone clarify? Does U-Boot going bad wipe out the Marvell>> prompt?
Of course, the prompt comes from U-Boot. The "even lower-level boot software" (the boot-ROM) can not have any user interaction features, because it knows nothing about the peripherals connected to the chip.
33  Linux Stuff / Kernel / Re: new kernel available on: October 01, 2010, 07:10:53 AM
The SD-card slot is internally connected to the USB bus. Partitions on a USB Mass Storage device do not become available immediately (you should see a message in the kernel log when they do).
You can try adding "rootdelay=10" to the kernel boot parameters to delay mounting the root file system.
34  Hardware and U-Boot firmware / U-Boot stuff / Re: How to backup the nand on: October 01, 2010, 03:26:36 AM
See http://plugcomputer.org/plugforum/index.php?topic=2252.

You could probably use "nanddump" too, but I haven't tried that myself.
35  General Category / General Discussion / Re: Round #1 - Your feedback required. New SheevaPlug concepts. on: September 28, 2010, 04:23:06 AM
0- Must be very reliable to work 24/7 for many months without human intervention
4- Must be quiet and doesn't include any moving parts
8- Must have the best power efficiency
3- Must be packaged within an enclosure (vs.  bare-bones)
6- Must have the highest processing power available (vs. lowest price/performance).
7- Must have the smallest footprint possible.
5- Must have slick design and look.
1- Must be plug computer form factor and pluggable to a wall outlet.
2- Must be in the price range $100-$150
9- Must be below $100

I believe all those nice features are not worth much if the device as a whole is unreliable. I have been using Wafer-LX-800 SBC as my home gateway/server for about 4 years. I'm very happy with it, although it only satisfies conditions 0 and 4 (and partly 8 ) from the list. About the only reason why I'm trying to switch to GuruPlug Server Plus is that it has gigabit ethernet.

Small footprint is nice, but as for the plug form-factor, I consider it a disadvantage, because it adds extra limitations to where you can put it. Besides, the European "flat" plug is not very good at holding considerable weight in a "big" power socket, which goes back to the reliability question.
36  Hardware and U-Boot firmware / Hardware / Re: Plug computer with FPU? on: September 28, 2010, 04:00:41 AM
The only alternative I see, is to use a traditional server on a Desktop computer with all its downsides.
A plug computer or a "traditional" server are two extreme cases. There is a lot in between. There are dozens of so called SBC (Singe-Board-Computer) with low power consumption and x86 compatible CPU (and FPU). They are rather expensive compared to a plug computer, but still cheaper than a desktop (depends on the configuration, of course).
37  General Category / General Discussion / Re: Enabling relatime on ubifs rootfs at boot? on: September 24, 2010, 12:56:20 AM
/ isn't in my fstab. What should my fstab line look like?
It isn't really needed at all. The / mount in /etc/fstab is just a "formality". The actual mount happens at boot time without /etc/fstab involved.

I found this post but trying "mount -o bind ubi0:rootfs  /mnt" says "special device ubi0:rootfs does not exist", so what special do I need to use?
If you are using "-o bind" then you are mounting a directory, not a device. Without "-o bind" the "mount" utility expects a device node (usually located in /dev).

I don't understand how / gets mounted on boot without an fstab line, anyway.
Well, try to imagine how it would work with fstab. To mount / you would need to read fstab first. But to read it you would need to mount / first. It's a chicken-egg problem. That must be why the root file system is mounted based only on the kernel boot parameters. In fact, fstab is used only by the "mount" utility, which is obviously not involved in mounting the root file system. People often add a line for / in fstab to let "mount" show it properly in the list of active mounts. That is also the reason why the options shown by "mount" can differ from the actual ones, which you can see in /proc/mounts.

/proc/mounts does have relatime there after a boot.
That means the root has been mounted with "relatime". It may be just the default behavior even if "relatime" is not explicitly specified. In that case you can be happy, as you don't have to do anything.

Why would /sbin/mount and /proc/mounts differ? I thought the former just read the latter..
"mount" normally reads /etc/mtab, not /proc/mounts. The former may or may not be a symlink to the latter. That depends on the distribution. If /etc/mtab is not a symlink then its contents are maintained by "mount" itself and can in some cases go out of sync with the reality.

Thanks. I thought it was worth a shot, and it does seem to have worked.  Should I be passing 'ro' or 'rw'?  And back to my original question, what's the proper way to mount with relatime at boot - an fstab entry?
As I mentioned, fstab has no influence on mounting the root. Everything should be specified with kernel boot parameters. You can use "rootflags" parameter to pass arbitrary mount options. However, if "relatime" is already in /proc/mounts then you don't need to do anything.
38  General Category / General Discussion / Re: Enabling relatime on ubifs rootfs at boot? on: September 23, 2010, 12:57:46 AM
Another thing. "rw" is a special kernel boot parameter that is understood by the kernel as a mount option for the root file system. You can't just attach arbitrary mount options to it and expect it to work.
See http://www.kernel.org/doc/Documentation/kernel-parameters.txt.
39  General Category / General Discussion / Re: Enabling relatime on ubifs rootfs at boot? on: September 23, 2010, 12:48:54 AM
The output of "mount" for the root file system is usually what you have in your /etc/fstab. It does not always reflect the actual mount options used. You should do "cat /proc/mounts" to see the real mount options.
40  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server PLUS no complaint about the fan ? on: September 15, 2010, 01:22:22 AM
Slightly off-topic:
I can see that the second (internal) SD-card slot is installed. Did the Plug come like that or did you solder it yourself?
41  General Category / General Discussion / Re: Guruplug as accesspoint on non-default network not connecting on: September 14, 2010, 01:13:26 AM
How you suggest I proceed?  (And thanks for you patience.)  I can, if need be, re-install debian on the guruplug.
I think you could start with restoring the system to a known-good state. So re-installing the OS may be a good idea.
Then you can begin to adjust the configuration to suit your needs, while keeping track of what you have changed so far.

A piece of advice if you don't mind. Try not to follow any "recipes" you find online without understanding first what exactly they do. It may seem too difficult, but it can spare you a great deal of trouble.
42  General Category / General Discussion / Re: compiling C++ for a plug computer on: September 14, 2010, 12:55:26 AM
I cross-compile everything on another Linux machine. Physical, not virtual. Then I rsync to the plug only what is needed at runtime, that is no development headers/libraries (*.a or *.h) and no manpages or other documentation. This way a basic Linux system that can function as a network router/gateway fits in only 40MB, and this is a "normal" system with glibc, bash, etc., no uClibc/busybox.

I believe 512 MB of NAND flash is a lot of space for a lot of stuff. No offense to anyone, but it seems pretty silly to me that people go great lengths to boot from SD card and fill it with tons of bloatware. But, of course, I understand that if one wants to stick with Debian/Ubuntu then he may not have much choice.
43  General Category / General Discussion / Re: Guruplug as accesspoint on non-default network not connecting on: September 13, 2010, 10:47:02 AM
target     prot opt source               destination
MASQUERADE  all  --  anywhere             anywhere
MASQUERADE  all  --  anywhere             anywhere
Masquerading everything from anywhere to anywhere? This just doesn't make any sense. Where are those rules coming from? Did you change anything in the startup scripts or in the system configuration?

Another problem is that eth0 and uap0 are on the same subnet. This is not going to work without some advanced tweaking. You don't want to go that way. Either you should assign addresses on different subnets, so that normal routing can take place, or use bridging.

By the way, I'm not sure I understand what exactly you are trying to accomplish. What do you call "non-default network"?
44  General Category / General Discussion / Re: Guruplug as accesspoint on non-default network not connecting on: September 13, 2010, 01:43:54 AM
There is more to it than just "iptables -L".
To begin with, what is the output of
iptables -t nat -L
cat /proc/sys/net/ipv4/ip_forward
ip addr
45  General Category / General Discussion / Re: Guruplug as accesspoint on non-default network not connecting on: September 12, 2010, 07:14:19 AM
An odd thing is that iwconfig says "no wireless extensions" for uap0.  "uaputl sys_config" correctly reports the ssid and other parameters.
This is not odd at all. The uap driver does not use the "normal" Linux wireless framework.

I don't think your problem has anything to do with uap. It looks more like generic routing/NAT problem, but the information you provided is not enough to say anything specific.
Pages: 1 2 [3] 4 5 6