Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 13 of 13
Dear Friends, Please try to avoid compile and load the module programs through by X window. Reason is:Modules can't print to the screen like printf() can, but they can log ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Jun 2006
    Posts
    15

    Dear Friends,
    Please try to avoid compile and load the module programs through by X window.
    Reason is:Modules can't print to the screen like printf() can, but they can log information and warnings, which ends up being printed on your screen, but only on a console. If you insmod a module from an xterm, the information and warnings will be logged, but only to your log files. You won't see it unless you look through your log files. To have immediate access to this information, do all your work from console.
    Only the above reason, the peoples did not get any output on the screen. And why we want to go to show the output to the location, /cat, each and every time?. Not necessary, if we follows the proper way.

  2. #12
    Just Joined!
    Join Date
    Jul 2006
    Posts
    5

    about printk

    loading the module by insmod command will not print anything on the console.

    Use the command : dmesg

    It will show many messages, the last one will contain your " hello world" message

  3. #13
    Just Joined!
    Join Date
    Jul 2006
    Posts
    5

    about printk

    after compiling & loading the module by insmod command , if it's succesful ( no errors are given) use the command: dmesg

    U'll see the "hello world" message of ur program.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •