Kdebug PPPd Option Is Not Logging Into /etc/syslog To Log The Kernel Level Raw PPP

Before I use Code:

pppd call

Code:

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    1024   0        0 wlp8s0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlp8s0

And then I call the code
server: 50.117.*.*
Code:

	sudo pppd call shayu13
	sudo route add -net 0.0.0.0 dev ppp0

I get the error :
Quote:
SIOCADDRT: Network is down
I must change the code by adding the sleep code.
Code:

	sudo pppd call shayu13
	sleep 15
	sudo route add -net 0.0.0.0 dev ppp0

Why? Thanks

And when I look the route tables:
Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0
0.0.0.0         192.168.1.1     0.0.0.0         UG    1024   0        0 wlp8s0
50.117.**.**  192.168.1.1     255.255.255.255 UGH   0      0        0 wlp8s0
172.16.**.**     0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlp8s0

It seems that 0.0.0.0 has two gateway. Is that OK? Thanks

Hey guys, I am a little confused about run level programs. (concerning centos)

I know when the system boots up the orders will be

bios
MBR
GRUB
kernel
init
runlevel

to my understanding - etc/init looks at /etc/inittab
then where is the run level located?
is it /etc/rc.d/rc0.d...
/etc/rc.d/rc1.d
/etc/rc.d/rc2.d
are these run level programs?

if so, what about /etc/init.d ? doesnt that also execute run level programs?

and how does it know what to start? where does it look

thanks guys just a bit confusing where what looks for what

Hi! I have a failing disk and the kernel messages are the following:
Code:

Απρ 01 15:07:02 Arch kernel: ata1: lost interrupt (Status 0x50)
Απρ 01 15:07:03 Arch kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Απρ 01 15:07:03 Arch kernel: ata1.00: failed command: WRITE DMA
Απρ 01 15:07:03 Arch kernel: ata1.00: cmd ca/00:08:20:32:6a/00:00:00:00:00/e4 tag 0 dma 4096 out
                                         res 40/00:00:4b:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Απρ 01 15:07:03 Arch kernel: ata1.00: status: { DRDY }
Απρ 01 15:07:03 Arch kernel: ata1: soft resetting link
Απρ 01 15:07:03 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:07:03 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:07:03 Arch kernel: ata1.00: configured for UDMA/133
Απρ 01 15:07:03 Arch kernel: ata1.01: configured for UDMA/133
Απρ 01 15:07:03 Arch kernel: ata1: EH complete
Απρ 01 15:09:19 Arch kernel: ata1: lost interrupt (Status 0x50)
Απρ 01 15:09:20 Arch kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Απρ 01 15:09:20 Arch kernel: ata1.00: failed command: READ DMA EXT
Απρ 01 15:09:20 Arch kernel: ata1.00: cmd 25/00:20:e8:b2:fd/00:00:18:00:00/e0 tag 0 dma 16384 in
                                         res 40/00:00:4b:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Απρ 01 15:09:20 Arch kernel: ata1.00: status: { DRDY }
Απρ 01 15:09:20 Arch kernel: ata1: soft resetting link
Απρ 01 15:09:20 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:09:20 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:09:20 Arch kernel: ata1.00: configured for UDMA/133
Απρ 01 15:09:20 Arch kernel: ata1.01: configured for UDMA/133
Απρ 01 15:09:20 Arch kernel: ata1: EH complete

I have 2 disks: sda, sdb. Which disk is it referring to?

Thanks a lot

Hi,

I have recently upgraded to fedora 21 (kernel version 3.17.8-200.fc20.x86_64) and I cannot find
/var/log/dmesg and /var/log/messages !

Have been removed? Is this because the OS's are going to replace init? Or, this is a problem in my system?

I am going to attempt to dual boot both fedora 17 and fedora 21, as my printer can print from FC17 but not from FC21 - posted about this issue in the hardware forum.

I am rather surprised at the level of competence of people posting here, even though it says newbie forum - so I think that this is possibly where I belong too.

I have set up grub to see my fedora 17 kernel - the only problem is, that the root filesystem needs to belong to the fedora 17 kernel as opposed to the fedora 21 kernel. I can't see myself changing fc 21's fstab to have the old lv root device mounted - as /etc belongs to the root partition of fc 21.

I did change the device to reflect the old kernel's root lv partition in the /etc/fstab (fc17), but this doesn't seem to do it.

Does someone know what I am missing?

What Is Linux Kernel?

Those who don't know what is the Linux Kernel they should know it because Linux kernel is the essential part of any Linux operating system. It is responsible for resource allocation, low-level hardware interfaces, security, simple communications, basic file system management, and more. Written from scratch by Linus Torvalds (with help from various developers), Linux is a clone of the UNIX operating system. It is geared towards POSIX and Single UNIX Specification compliances.

Latest Stable Linux Kernel Version 3.18.1
It's been a quiet week, and the patch from rc7 is tiny, so 3.18 is out.
I'd love to say that we've figured out the problem that plagues 3.17 for a couple of people, but we haven't. At the same time, there's absolutely no point in having everybody else twiddling their thumbs when a couple of people are actively trying to bisect an older issue, so holding up the release just didn't make sense. Especially since
that would just have then held things up entirely over the holiday break.
So the merge window for 3.19 is open, and DaveJ will hopefully get his bisection done (or at least narrow things down sufficiently that we have that "Ahaa" moment) over the next week. But in solidarity with Dave (and to make my life easier too let's try to avoid introducing any _new_ nasty issues, ok?]

To read all the changes and bugs fixed Download the changelog below -
Changelog

Why to Upgrade to the Latest Linux kernel

Recently in December Linux Kernel version 3.18.1 has been released and announced by Linus Torvalds. If you are using Ubuntu 14.04/14.10 or Linux Mint or any other debian/Ubuntu based then you can update to the latest kernel 3.18.1 to fix bugs, increase performance and security of the system.


Install Linux Kernel 3.18.1

Because it is not available via PPA, the needed deb packages of Kernel 3.18.1 are available via kernel.ubuntu.com. Follow the instructions for your system’s architecture exactly, in order to get a successful installation.

To install or update Latest Stable Kernel 3.18.1 on Ubuntu 15.04 vivid vervet, Ubuntu 14.10 Utopic Unicorn, Ubuntu 14.04 Trusty Tahr (LTS) , Linux Mint 17.1 Rebecca, Linux Mint 17 Qiana, Pinguy OS 14.04, Elementary OS 0.3 Freya, Elementary OS 0.2 Luna, Peppermint Five, Deepin 2014, LXLE 14.04, Linux Lite 2.0, Linux Lite 2.2 and other Ubuntu derivative systems, open a new Terminal window and bash (get it?) in the following commands:


For Linux system 32 bit :

Pass the following commands in the terminal to download the kernel file.

$ wget http://kernel.ubuntu.com/~kernel-ppa...170637_all.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa...70637_i386.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa...70637_i386.deb

Install Linux Kernel 3.18.1


$ sudo dpkg -i linux-headers-3.18.1*.deb linux-image-3.18.1*.deb

Atfer install complete, update grub and reboot your computer and choose new kernel in grub :

$ sudo update-grub
$ sudo reboot

For Linux system 64 bit :

$ wget http://kernel.ubuntu.com/~kernel-ppa...170637_all.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa...0637_amd64.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa...0637_amd64.deb

Install Linux Kernel 3.18.1

$ sudo dpkg -i linux-headers-3.18.1*.deb linux-image-3.18.1*.deb

Atfer install complete, update grub and reboot your computer and choose new kernel in grub :

$ sudo update-grub
$ sudo reboot

How To Uninstall Linux Kernel 3.18.1

If you come across any problem after installing/upgrading to linux kernel, can uninstall the newly installed kernel and switch back to old kernel.

$ sudo apt-get remove 'linux-headers-3.18.1*' 'linux-image-3.18.1*'

Hi everyone (i hope this is the right section)

Im trying to install the RT patch preempt_rt 3.18.9 im running Ubuntu 14.04 with kernel v 3.16

i installed the rt patch "patch-3.18.9-rt5.patch" and also a new kernel "3.18.9" i patched the patch file with

patch -p1 < patch-3.18.9.patch

but there is somthing i don't know about linking folders of old kernel and new kernel, i searched about it and found

rm -rf linux && ln -s /usr/src/linux-3.18.9 linux && cd /usr/src/linux

then

make oldconfig

then

make menuconfig

i selected Full preemptive kernel then

make

then this error

cc1: some warnings being treated as errors make[2]: * [kernel/locking/locktorture.o] Error 1 make[1]: * [kernel/locking] Error 2 make: *** [kernel] Error 2


So..... Any help?? can someone walk me through this

or any other real time patch, Thanx.. plzzzzzz

I have a USB fax modem, and it logs the following errors when turned on.

I know it is impossible to know for sure, but think it is hardware related? Any chance to salvage?

Also, what are the steps to start troubleshooting?

Thanks

Code:

Jan 17 14:38:26 devserver kernel: generic-usb 0003:0461:4D0F.0066: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1a.0-1.2/input0
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 24 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/all, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 25 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/all, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 26 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 27 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:42 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:42 devserver kernel: hub 3-0:1.0: unable to enumerate USB device on port 1

Hi guys prob a silly question...
i only just read now that linux kernel v4 was released about 11 days ago...can any distros upgrade there kernel to 4 or only specific ones?

Is there really a huge benefit in doing so?

should i just lookup the information in the distros web site?

Hi all,

In my work, I'd like to spawn separate kernel threads (tasks) to execute syscall asynchronously. Specifically, a user thread issues a syscall, goes into kernel, save the syscall number and arguments somewhere in the kernel address space, but does not execute the syscall. A kernel thread which is different from the user thread, will fetch the syscall number and arguments to execute the syscall on behalf of the user thread.
But for file operations such as read, the kernel thread is not aware of the open files of the user threads. For example, if the user thread opens a file and get a file descriptor, then it issue a read() syscall. The kernel thread cannot execute the read() on behalf of the user thread by just using the file descriptor. Thus I need some way to allow the kernel thread share the open files information with the user thread, such that the kernel thread will have the context of the open file to execute read(). I tried to pass the files_struct of the user thread's task_struct to the kernel thread, but it didn't help, read() returns a EFAULT error.
Can anyone give me some suggestions on how to make a kernel thread share the open files with a user thread? Or more straightforward how to execute the read() syscall in the example above in kernel thread? Thank you very much!

--Louis