headers
Aroop Maliakkal | 1 Sep 2005 06:04

Re: The /dev/mem info please

Hi Mukund,

For me the command is working quite fine.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thu Sep 01 <at> Admin#dd if=/dev/mem of=/tmp/ramfile count=1 bs=1024
1+0 records in
1+0 records out
Thu Sep 01 <at> Admin#od -x /tmp/ramfile
0000000 0001 0000 ef6f f000 e2c3 f000 ef6f f000
0000020 ef6f f000 ff54 f000 5cd8 f000 ef6f f000
0000040 fea5 f000 e987 f000 ef6f f000 ef6f f000
0000060 ef6f f000 ef6f f000 ef6f f000 ef6f f000
0000100 09ae c000 f84d f000 f841 f000 3400 f000
0000120 e739 f000 f859 f000 3422 f000 efd2 f000
0000140 e7a4 f000 2497 f000 fe6e f000 ff53 f000
0000160 3427 f000 f0a4 f000 efc7 f000 5951 c000
0000200 000d 0000 ef6f f000 ef6f f000 ef6f f000
0000220 ef6f f000 ef6f f000 ef6f f000 ef6f f000
*
0000400 ec59 f000 9020 f000 f065 f000 6b52 c000
0000420 ef6f f000 ef6f f000 ef6f f000 ef6f f000
*
0000600 0000 0000 0000 0000 0000 0000 0000 0000
*
0000640 ef6f f000 ef6f f000 ef6f f000 ef6f f000
0000660 ef6f f000 09ae c000 ef6f f000 ef6f f000
0000700 9aa0 f000 ecf3 f000 ef6f f000 ef6f f000
0000720 ee3a f000 f0fc f000 ed00 f000 ef6f f000
0000740 0000 0000 0000 0000 0000 0000 0000 0000
*
(Continue reading)

Permalink | Reply | 0 comments |
headers
raja | 1 Sep 2005 06:24

help regarding project

Hi,
     Will you please suggest me some good mini projects to do that 
includes kernel programming and device drivers.Will you please help me.

Thanking you,
Raja
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Permalink | Reply | 0 comments |
headers
Mukund JB. | 1 Sep 2005 06:33
Picon

RE: The /dev/mem info please

Dear Aroop,

Well that depends on the kernel as I guess. I am using 2.6.10 kernel
(Intel based system).
I heard that this problem of 'Bad Address' is NOT present on 2.4.x
kernels. What kernel are you using?

I just have doubt here.
Does the /dev/mem device represent the entire physical memory on the
system?
Please through some light on this.
How do I interpret the /proc/meminfo and iomem interfaces?

Thanks & Regards,
Mukund Jampala

>-----Original Message-----
>From: Aroop Maliakkal [mailto:aroop <at> poornam.com]
>Sent: Thursday, September 01, 2005 9:34 AM
>To: Mukund JB.
>Cc: linux-newbie <at> vger.kernel.org
>Subject: Re: The /dev/mem info please
>
>Hi Mukund,
>
>For me the command is working quite fine.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Thu Sep 01 <at> Admin#dd if=/dev/mem of=/tmp/ramfile count=1 bs=1024
>1+0 records in
>1+0 records out
(Continue reading)

Permalink | Reply | 1 comment |
headers
rekha vn | 1 Sep 2005 08:40
Picon
Favicon

RHEL 3 hardware list

i'd like to have the hardware compatability list    of
rhel 3(kernel 2.4.21-4).thanks in advance

		
__________________________________ 
Yahoo! Mail for Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Permalink | Reply | 1 comment |
headers
mhb | 1 Sep 2005 09:12
Picon
Favicon

where can I get ext3 patch for linux-2.4.1

Hi

Most of the related sites has ext3 patches for 2.4
kernels but I could not found any for 2.4.1.
where can I find It?

thanks

		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Permalink | Reply | 0 comments |
headers
Arturas Moskvinas | 1 Sep 2005 10:23
Picon

Re: RHEL 3 hardware list


> i'd like to have the hardware compatability list    of
> rhel 3(kernel 2.4.21-4).thanks in advance

You should ask vendor (Red Hat) about compatibility list not
linux-newbie maillist. It is vendor specific question...

Arturas M. 

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Permalink | Reply | 0 comments |
headers
Arturas Moskvinas | 1 Sep 2005 10:30
Picon

Re: where can I get ext3 patch for linux-2.4.1

> Hi
> 
> Most of the related sites has ext3 patches for 2.4
> kernels but I could not found any for 2.4.1.
> where can I find It?

I think you are using way too old kernel, consider an upgrade...

Arturas M.
Permalink | Reply | 0 comments |
headers
James Miller | 1 Sep 2005 17:44

X (core input device) probs under Debian unstable; solution?

I finally got around to trying more earnestly to tackle this problem. 
The motivation was that I lost CD burning capability by reverting to the 
2.4.27 kernel (the kernel that actually gave me a working mouse and thus a 
working X) and I finally needed to get it back.  Searching the internet I 
was able to find some information that got the mouse, and thus the gui, 
working again.

Before searching the 'net, I actually decided I might try upgrading the 
xserver to xorg. I did that, and ran dpkg-reconfigure xserver-xorg, trying 
various mouse options, but the core pointer still was not found and the 
gui wouldn't start.  That's when I started searching the 'net.

I found a message on the debian-users list that mentioned modprobing or 
adding to /etc/modules psmouse and mousedev. I tried modprobing them in 
that order and then running startx and, sure enough, the gui fired up and 
I had a working mouse. I decided to add mousedev to /etc/modules and 
reboot to see if that would do the trick. Having done that, the gui 
started but the mouse wasn't working (cursor did not respond to mouse 
movements). So I added psmouse before mousedev in /etc/modules and 
rebooted.  After this, the gui fired up fine plus I had a responsive mouse 
cursor.  So, the problem I had is pretty much solved (for now, at least).

Why did this happen?  My guess is that since the mouse module wasn't 
getting loaded, no device node was created for it.  Just a guess: I'm not 
techie enough to say for sure.  But one of the tests I ran when I was 
searching out this problem, which involved running od -tx1 /dev/psaux and 
od -tx1 /dev/input/mice, did indicate that these device nodes were 
non-existent.  Maybe more experienced brains than mine on this list can 
figure out why this happened.  At least I've found a solution.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Karthik Vishwanath | 2 Sep 2005 01:54
Favicon

Re: kernel log messages and disk space

On Sun, 21 Aug 2005, at 09:52, Ray Olszewski wrote:

> [cut]

> Wel, device 03:01 is /dev/hda1, and this time (I mean in contrast to 
> James' recent posting) the reports do sound like an emerging hardware 
> failure, especially if you are getting this many of them. So you *may* 
> need a new hard disk.

Thanks Ray, umounting the hard drive, fixed the overflowing messages
problem. I do not think there is any thing "catastrophic" about the drive
per se (/dev/hda1 is a windoze only partition) since it boots into windoze
quite fine...

> But first, let's consider other possibilities ... the one I think of is 
> a combination of a partitioning error and a drive that is nearly full 
> (so the error is just now becoming visiale). Either you or we should 
> look at this information:
> 
> 	output of "df"
> 	the drive's partition table (as reported by fdisk, say).
> 	the physical size of the drive (as reported in dmesg during boot/init, 
> preferably)

definitely a problem with the way fdisk looks at /dev/hda1 it seems: 
heres what fdisk /dev/hda1, then p gives 
----------
Command (m for help): p

Disk /dev/hda1: 13.5 GB, 13596355584 bytes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ray Olszewski | 2 Sep 2005 03:50

Re: kernel log messages and disk space

OK, Karthik. With the extra information, I'm adding the list back in, 
since other might have a more helpful response than I. Specifics below.

Karthik Vishwanath wrote:
> On Thu, 1 Sep 2005, at 17:14, Ray Olszewski wrote to Karthik Vishwanath:
> 
> 
>>I'm sorry, Karthik, but this information doesn't make sense to me.
>>
>>Normally, hda1 would be a partition, not a drive, so I really do not 
>>understand what all this output means. If it is something that makes 
>>sense ... say one of those old versions of Linux that boot from a DOS 
>>directory ... you'll need describe the setup.
>>
>>If not, I'd want to see an fdisk for /dev/hda (the drive itself), not 
>>for a partition.
>>
>>Also, if you look back at my Aug 21 message, I asked for more 
>>information than a partition table. Please provide it.
>>
> 

Just a reminder for others; the original issue was that the logs were 
filling up with messages of this sort (I'm picking a representative 
example):

	Aug 18 07:38:18 mithrandir kernel: attempt to access
		beyond end of device
	Aug 18 07:38:18 mithrandir kernel: 03:01: rw=0,
		want=2031123176, limit=13277691
(Continue reading)

Permalink | Reply | 0 comments |

Gmane