OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
pepe doesn't have a personal statement currently.
Personal Info
pepe
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
Interests
No Information
Statistics
Joined: 26-May 05
Profile Views: 84*
Last Seen: 27th May 2006 - 03:23 AM
Local Time: Sep 19 2014, 07:53 AM
2 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
* Profile views updated each hour

pepe

Members


Topics
Posts
Comments
Friends
My Content
28 May 2005
Hi Folks,

just got my Z (SL-5500G) a couple of day ago and as it had an earlier version of the Cacko ROM installed, I flashed the lates version [Cacko/Crow ROM update 3.10 (Kernel 2.4.18)]

Now I have some questions and need help.

'dmesg' shows lots of '-W- Don't delete.' Where does that come from and how can it be fixed?

How can I enable logging into /var/log/messages? (temporary and permanently)
I think I read something like 'echo xx > /proc/...' but can't find it anymore.

If I use my 'Socket low Power Ethernet' CF-Card (10Mbit) on a ASUS WL-HDD it works fine (with static as well as dynamic ip-addresses), but if I try to use it on a 10 MBit Hub or with a crossover cable on a laptop I get 'Connection Error - No Connetion detected. - Check your TCP/IP settings.'

The funny thing is that, as long as I don't acknowledge the message, everything (ping, ssh, smb, etc) works. If I'm connected to the Z (e.g. ssh) via eth0 when I acknowledge the message I get a 'Network device bussy' message but the interface then stays up.

'ifconfig -a' via ssh shows me the following.
eth0 Link encap:Ethernet HWaddr 00:C0:1B:06:47:EB
inet addr:192.168.75.99 Bcast:192.168.75.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:12485 (12.1 Kb) TX bytes:5718 (5.5 Kb)
Interrupt:35 Base address:0x300

How can I fix this behavior?

Furthermore, where can I get more details/information about the /dev/mmcdax and /dev/mtdblockx devices?

Cheers,
pepe
Last Visitors
pepe has no visitors to display.

Comments
Other users have left no comments for pepe.

Friends
There are no friends to display.
RSS Lo-Fi Version Time is now: 19th September 2014 - 07:53 AM