Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
On Thursday 05 Mar 2015 21:46:12 Marc Joliet wrote: > Am Thu, 5 Mar 2015 21:19:46 + > schrieb Mick : > > On Thursday 05 Mar 2015 18:33:23 Todd Goodman wrote: > > > Is this a WiFi NIC? > > > > > > Is it possible the device is powering down? > > > > > > I've had lots of problems with WiFi devices powering down (both driver > > > issues as well as just trying to disable the default setting of > > > powering down.) > > > > > > Todd > > > > If not a WiFi, have you also tried to mirror a port at the router where > > the DHCP server is running and sniff packets there? Does the router see > > the DHCPREQ coming through from the client PCs? > > They apparently don't even reach the managed switch, which is what the PC > is directly connected to (but again: the third affected PC is on a > different switch). I find this very confusing :-/ (and so does our local > sysadmin, or so I'm told). > > (I have to mention that the best I can do is relay ideas here to my boss > and the aforementioned sysadmin, as I don't have access to any of the > network hardware and software, save for the affected PCs. I am mostly > trying to collect ideas.) If the router does not see the dhcp request frames coming from the PCs then the problem won't be with the router. Check that the NIC on the affected PCs is not trying to save power by shutting down, whether this is wired or wireless. As Alan said you'll need to pass some driver parameter to the NIC, I usually do this via the /etc/conf.d/modules file, or by adding a .conf file in /etc/modprobe.d/ Besides the latest drivers, also check that you are using the latest firmware for the NIC if it uses any and check the logs after increasing verbosity on the driver to make sure it loads without errors. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Virtualbox-guest-additions-4.3.24 breaks 3D acceleration in linux guests (?)
On Thu, 05 Mar 2015 16:27:25 -0800 walt wrote: > On 03/05/2015 02:25 PM, walt wrote: > > Downgrading Virtualbox to 4.3.20-r1 fixes the problem on one ~amd64 > > machine but, of course, not the other one . > > For reasons I don't know, the gentoo devs split the "guest-additions" > into two parts: they put the vboxvideo kernel module into the gentoo > xf86-video-virtualbox package, and the vboxguest+vboxsf kernel modules > into the virtualbox-guest-additions package. > > Anyway, starting with a vbox gentoo snapshot from Mar 3 (before the > update to vbox-4.3.24) I upgraded only the virtualbox-guest-additions > (not the xf86-video-virtualbox package) and found that everything > still works normally. > > I then upgraded the xf86-video-virtualbox package and discovered that > 3D video acceleration was broken, just as before. > > I then downgraded the xf86-video-virtualbox package to 4.3.20 (leaving > the virtualbox-guest-additions at 4.3.24) and found the 3D > acceleration working normally again. > > That clearly implicates the vboxvideo.ko kernel module as the cause of > the breakage, I think. > > Opinions/comments are most welcome. File a bug at b.g.o. what you describe has much potential to trip up many people :-) Alan
Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
On Thu, 5 Mar 2015 13:33:23 -0500 Todd Goodman wrote: > * Marc Joliet [150305 04:47]: > [..SNIP..] > > 1.) The NIC is brought up (some built-in Intel model). > > > > 2.) A DHCP client configures it. > > > > 3.) The network connection is lost at some point (the amount of > > time this takes varies, but it can be as little as 20 minutes). > > > > 4.) Eventually the lease runs out and the DHCP client tries to > > renew it, but gets no response. Sometimes, after many hours (at > > least 6), it will get a DHCPACK, but that's it. One of our > > sysadmins says that not only does the DHCP server never see the > > packets, but the managed switch that the PC is directly attached to > > *also* never does (again, except for when the occasional DHCPACK > > comes). > > > > 4.) Restart the network device. A reboot is not required, but it > > is necessary to terminate the DHCP client. After that everything > > works again. > > > > 5.) GOTO 3. > [..SNIP..] > > Is this a WiFi NIC? > > Is it possible the device is powering down? > > I've had lots of problems with WiFi devices powering down (both driver > issues as well as just trying to disable the default setting of > powering down.) +1 I've seen similar things many times myself (but nevr on Intel network kit so far) A lot of reading and Googling usually leads to the solution: - firmware upgrade for the hardware - use the correct driver (this is often non-obvious) - try the in-kernel driver vs any out-of-tree vendor driver - apply driver parameters designed to work around buggy hardware (this often involves (much reading) Alan
[gentoo-user] Re: new linux router
Nicolas Sebrecht laposte.net> writes: > > On Wed, Mar 04, 2015 at 03:10:40PM +, James wrote: > > > I'd like to be able to download some open source linux to the router > > hardware if updates and pathces are not maintained by the vendor? > > That way I do not purchase something that is to be abandoned in > > a few years by the vendor. > > > > It's just a small home/office so 3x100Mb E would be fine, but GigE > > ports would be better. I'm flexible on the CPU/arch of the hardware, > > so all discussion and suggestions are welcome. In an idealized world > > I'd pay extra for a gentoo_derivative based router; but all I find > > is the WRT, devil_linux and such, nothing really cool and interesting. > > For the hardware, you could get a alix2d3: > http://www.pcengines.ch/alix2d3.htm I actually recently acquired one of these from a friend. > For the distribution, I'd recommend Alpine: > http://www.alpinelinux.org/about Why would that be better than putting lilblue (gentoo) on the board. Maybe somebody who has success with booting off of usb (and that definitely is not me) could test lilblue on an alix2d3 board? http://wiki.gentoo.org/wiki/Install_Gentoo_on_a_bootable_USB_stick https://wiki.gentoo.org/wiki/Project:Hardened_uClibc/Lilblue I'm not sure the arch of a 500 MHz AMD Geode LX800; isn't that compatible with i686 binaries? I found this: " When it comes to compiling, just compile with -march=geode. That option is defined on any i386/x86-64 gcc, so no real need to cross-compile. If you want to run the binary on your compiler host as well (without a recompile), try something like -march=i486 -mtune=geode. " How did you have your make.conf files (or similar under Alpine) set up? If I go this route, I'd really rather run gentoo or something quite similar, rather than a distro I not familiar with. > That's the combo I used in a recent past and it worked quiet fine > (802.1q VLAN, traffic shaping with tc, advanced firewall with scripted > iptables rules, ethernet cards controlled with ethtool (I could fix > speed/duplex for incompatible network hardware), ssh, etc). I'm not familiar with Alpine linux. How many of your scripts would be useful on gentoo? If what you did is sensitive, just drop to me privately. > While there is no wifi I found this MUCH better than WRT54GL, for > example. Yep, not in love with any of the wrt54 codes/systems/hardwares. I do not need or want a wireless interface on this device. thx, James
Re: [gentoo-user] See bootup/poweroff screen?
On Thursday, March 05, 2015 3:16:55 AM Dale wrote: > Yea, it won't catch everything. This is sort of designed for that point > where one log stops and the other hasn't started yet. This is usually > where dmesg stops and syslog and friends hasn't yet started. Of course, > if /var isn't mounted, well, it has no where to go. > > Isn't those init thingys supposed to fix this sort of thing tho? Isn't > it supposed to store it in memory until /var is mounted and then dump it? > > Dale > > :-) :-) > Even late on the boot process the OpenRC log won't catch everything. I think it only logs openrc messages, if it comes from some program it's probably on the system log (or nowhere at all). -- Fernando Rodriguez
[gentoo-user] Re: Virtualbox-guest-additions-4.3.24 breaks 3D acceleration in linux guests (?)
On 03/05/2015 02:25 PM, walt wrote: > Downgrading Virtualbox to 4.3.20-r1 fixes the problem on one ~amd64 > machine but, of course, not the other one . For reasons I don't know, the gentoo devs split the "guest-additions" into two parts: they put the vboxvideo kernel module into the gentoo xf86-video-virtualbox package, and the vboxguest+vboxsf kernel modules into the virtualbox-guest-additions package. Anyway, starting with a vbox gentoo snapshot from Mar 3 (before the update to vbox-4.3.24) I upgraded only the virtualbox-guest-additions (not the xf86-video-virtualbox package) and found that everything still works normally. I then upgraded the xf86-video-virtualbox package and discovered that 3D video acceleration was broken, just as before. I then downgraded the xf86-video-virtualbox package to 4.3.20 (leaving the virtualbox-guest-additions at 4.3.24) and found the 3D acceleration working normally again. That clearly implicates the vboxvideo.ko kernel module as the cause of the breakage, I think. Opinions/comments are most welcome.
[gentoo-user] Virtualbox-guest-additions-4.3.24 breaks 3D acceleration in linux guests (?)
I state this as a question because I'm seeing different behavior on different ~amd64 machines (as usual ;) After upgrading from vbox-4.3.20-r1 to 4.3.24 yesterday I find that my linux guests have no 3D acceleration. Downgrading Virtualbox to 4.3.20-r1 fixes the problem on one ~amd64 machine but, of course, not the other one . I'm still playing with downgrading mesa, etc, on the still-broken machine to see what happens. Anyone else noticing similar problems?
Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
Am Thu, 5 Mar 2015 21:19:46 + schrieb Mick : > On Thursday 05 Mar 2015 18:33:23 Todd Goodman wrote: > > * Marc Joliet [150305 04:47]: > > [..SNIP..] > > > > > 1.) The NIC is brought up (some built-in Intel model). > > > > > > 2.) A DHCP client configures it. > > > > > > 3.) The network connection is lost at some point (the amount of time this > > > takes > > > > > > varies, but it can be as little as 20 minutes). > > > > > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, > > > but > > > > > > gets no response. Sometimes, after many hours (at least 6), it will > > > get a DHCPACK, but that's it. One of our sysadmins says that not > > > only does the DHCP server never see the packets, but the managed > > > switch that the PC is directly attached to *also* never does (again, > > > except for when the occasional DHCPACK comes). > > > > > > 4.) Restart the network device. A reboot is not required, but it is > > > necessary > > > > > > to terminate the DHCP client. After that everything works again. > > > > > > 5.) GOTO 3. > > > > [..SNIP..] > > > > Is this a WiFi NIC? > > > > Is it possible the device is powering down? > > > > I've had lots of problems with WiFi devices powering down (both driver > > issues as well as just trying to disable the default setting of powering > > down.) > > > > Todd > > If not a WiFi, have you also tried to mirror a port at the router where the > DHCP server is running and sniff packets there? Does the router see the > DHCPREQ coming through from the client PCs? They apparently don't even reach the managed switch, which is what the PC is directly connected to (but again: the third affected PC is on a different switch). I find this very confusing :-/ (and so does our local sysadmin, or so I'm told). (I have to mention that the best I can do is relay ideas here to my boss and the aforementioned sysadmin, as I don't have access to any of the network hardware and software, save for the affected PCs. I am mostly trying to collect ideas.) -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup pgpqNq9iG2GUe.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
Am Thu, 5 Mar 2015 13:33:23 -0500 schrieb Todd Goodman : > * Marc Joliet [150305 04:47]: > [..SNIP..] > > 1.) The NIC is brought up (some built-in Intel model). > > > > 2.) A DHCP client configures it. > > > > 3.) The network connection is lost at some point (the amount of time this > > takes > > varies, but it can be as little as 20 minutes). > > > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, but > > gets no response. Sometimes, after many hours (at least 6), it will > > get a > > DHCPACK, but that's it. One of our sysadmins says that not only does > > the DHCP server never see the packets, but the managed switch that the > > PC > > is directly attached to *also* never does (again, except for when the > > occasional DHCPACK comes). > > > > 4.) Restart the network device. A reboot is not required, but it is > > necessary > > to terminate the DHCP client. After that everything works again. > > > > 5.) GOTO 3. > [..SNIP..] > > Is this a WiFi NIC? Nope, it's wired. > Is it possible the device is powering down? I mentioned the possibility, but don't find it *that* credible, since three different PCs (with different NICs) have shown the problem. Plus, sometimes the one affected PC I work on can still reach the internet (i.e., a browser works), even though it has already ceased to be reachable. [...] -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup pgpzmZvBUN2SC.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 16:13:59 -0500 Mike Gilbert wrote: > On Thu, Mar 5, 2015 at 2:08 PM, German wrote: > > On Thu, 5 Mar 2015 13:45:51 -0500 > > Mike Gilbert wrote: > > > >> On Thu, Mar 5, 2015 at 12:28 PM, German wrote: > >> > On Thu, 5 Mar 2015 12:47:36 + > >> > Neil Bothwick wrote: > >> > > >> >> On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: > >> >> > >> >> > > > > Is /var on your root filesystem? If so, it sounds like something > >> >> > > > > is trying to write to it before it has been remounted rw. Try > >> >> > > > > adding rw (and removing ro if present) to your kernel options. > >> >> > > > > > >> >> > > > > >> >> > > > Ok, thanks. What file should I write these options to? > >> >> > > > >> >> > > Your bootloader config, that's where you specify the kernel boot > >> >> > > options. > >> >> > > >> >> > That's what I thought, however I use gummiboot. Can you give an > >> >> > example, to show your gummiboot config once again? > >> >> > >> >> Add it to the options line in the relavent file in /boot/loader/entries. > >> >> > >> >> Or test it first by pressing e at the menu and adding it there > >> > > >> > > >> > So any other idea on hhow to fix it? Anyone? > >> > >> Can you please post the output of the following commands? > >> > >> stat /lib64/rc > >> > >> stat /lib64/rc/cache > > > > stat /lib64/rc/cache > > > > stat: cannot stat /lib64/rc/cache: No such file or directory > > > > I'll also put stat /lib64/rc later. I am thinking if there is no "cache" > > file, probably this will give you some clue. I am retyping this from my > > laptop screen and /lib64/rc is quite lengthy. Thank you. Please tell me if > > you really need it ( and me) and I'll take my time and retype it. > > It's supposed to be a directory. Try running mkdir -p /lib64/rc/cache. It seems the error is gone. But I wonder why I didn't have /lib64/rc/cache directory. This was a fresh install. > -- German
Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
On Thursday 05 Mar 2015 18:33:23 Todd Goodman wrote: > * Marc Joliet [150305 04:47]: > [..SNIP..] > > > 1.) The NIC is brought up (some built-in Intel model). > > > > 2.) A DHCP client configures it. > > > > 3.) The network connection is lost at some point (the amount of time this > > takes > > > > varies, but it can be as little as 20 minutes). > > > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, > > but > > > > gets no response. Sometimes, after many hours (at least 6), it will > > get a DHCPACK, but that's it. One of our sysadmins says that not > > only does the DHCP server never see the packets, but the managed > > switch that the PC is directly attached to *also* never does (again, > > except for when the occasional DHCPACK comes). > > > > 4.) Restart the network device. A reboot is not required, but it is > > necessary > > > > to terminate the DHCP client. After that everything works again. > > > > 5.) GOTO 3. > > [..SNIP..] > > Is this a WiFi NIC? > > Is it possible the device is powering down? > > I've had lots of problems with WiFi devices powering down (both driver > issues as well as just trying to disable the default setting of powering > down.) > > Todd If not a WiFi, have you also tried to mirror a port at the router where the DHCP server is running and sniff packets there? Does the router see the DHCPREQ coming through from the client PCs? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, Mar 5, 2015 at 2:08 PM, German wrote: > On Thu, 5 Mar 2015 13:45:51 -0500 > Mike Gilbert wrote: > >> On Thu, Mar 5, 2015 at 12:28 PM, German wrote: >> > On Thu, 5 Mar 2015 12:47:36 + >> > Neil Bothwick wrote: >> > >> >> On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: >> >> >> >> > > > > Is /var on your root filesystem? If so, it sounds like something >> >> > > > > is trying to write to it before it has been remounted rw. Try >> >> > > > > adding rw (and removing ro if present) to your kernel options. >> >> > > > > >> >> > > > >> >> > > > Ok, thanks. What file should I write these options to? >> >> > > >> >> > > Your bootloader config, that's where you specify the kernel boot >> >> > > options. >> >> > >> >> > That's what I thought, however I use gummiboot. Can you give an >> >> > example, to show your gummiboot config once again? >> >> >> >> Add it to the options line in the relavent file in /boot/loader/entries. >> >> >> >> Or test it first by pressing e at the menu and adding it there >> > >> > >> > So any other idea on hhow to fix it? Anyone? >> >> Can you please post the output of the following commands? >> >> stat /lib64/rc >> >> stat /lib64/rc/cache > > stat /lib64/rc/cache > > stat: cannot stat /lib64/rc/cache: No such file or directory > > I'll also put stat /lib64/rc later. I am thinking if there is no "cache" > file, probably this will give you some clue. I am retyping this from my > laptop screen and /lib64/rc is quite lengthy. Thank you. Please tell me if > you really need it ( and me) and I'll take my time and retype it. It's supposed to be a directory. Try running mkdir -p /lib64/rc/cache.
Re: [gentoo-user] No network ( Solved, I am connected, thanks)
On Thursday 05 Mar 2015 10:12:33 German wrote: > On Thu, 05 Mar 2015 09:36 + > > Peter Humphrey wrote: > > On Wednesday 04 March 2015 21:26:53 German wrote: > > > On Wed, 4 Mar 2015 18:25:07 + > > > > > > Mick wrote: > > > > Now that you're connected, or should I say BEFORE you got connected, > > > > you should also consider configuring a firewall for your IPv4 > > > > (and/or IPv6) network. > > > > > > What package I should use for this on a console? I want something > > > simple but efficient. > > > > I use shorewall. It's not too hard to understand and I haven't seen any > > reports of problems with it. > > Thanks for recommendation Also have a look at: net-firewall/arno-iptables-firewall It's just a script for iptables, but with an easy to walk through configuration file. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 13:45:51 -0500 Mike Gilbert wrote: > On Thu, Mar 5, 2015 at 12:28 PM, German wrote: > > On Thu, 5 Mar 2015 12:47:36 + > > Neil Bothwick wrote: > > > >> On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: > >> > >> > > > > Is /var on your root filesystem? If so, it sounds like something > >> > > > > is trying to write to it before it has been remounted rw. Try > >> > > > > adding rw (and removing ro if present) to your kernel options. > >> > > > > > >> > > > > >> > > > Ok, thanks. What file should I write these options to? > >> > > > >> > > Your bootloader config, that's where you specify the kernel boot > >> > > options. > >> > > >> > That's what I thought, however I use gummiboot. Can you give an > >> > example, to show your gummiboot config once again? > >> > >> Add it to the options line in the relavent file in /boot/loader/entries. > >> > >> Or test it first by pressing e at the menu and adding it there > > > > > > So any other idea on hhow to fix it? Anyone? > > Can you please post the output of the following commands? > > stat /lib64/rc > > stat /lib64/rc/cache stat /lib64/rc/cache stat: cannot stat /lib64/rc/cache: No such file or directory I'll also put stat /lib64/rc later. I am thinking if there is no "cache" file, probably this will give you some clue. I am retyping this from my laptop screen and /lib64/rc is quite lengthy. Thank you. Please tell me if you really need it ( and me) and I'll take my time and retype it. -- German
[gentoo-user] Re: new linux router
On Wed, Mar 04, 2015 at 03:10:40PM +, James wrote: > I'd like to be able to download some open source linux to the router > hardware if updates and pathces are not maintained by the vendor? > That way I do not purchase something that is to be abandoned in > a few years by the vendor. > > It's just a small home/office so 3x100Mb E would be fine, but GigE > ports would be better. I'm flexible on the CPU/arch of the hardware, > so all discussion and suggestions are welcome. In an idealized world > I'd pay extra for a gentoo_derivative based router; but all I find > is the WRT, devil_linux and such, nothing really cool and interesting. For the hardware, you could get a alix2d3: http://www.pcengines.ch/alix2d3.htm For the distribution, I'd recommend Alpine: http://www.alpinelinux.org/about That's the combo I used in a recent past and it worked quiet fine (802.1q VLAN, traffic shaping with tc, advanced firewall with scripted iptables rules, ethernet cards controlled with ethtool (I could fix speed/duplex for incompatible network hardware), ssh, etc). While there is no wifi I found this MUCH better than WRT54GL, for example. -- Nicolas Sebrecht
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, Mar 5, 2015 at 12:28 PM, German wrote: > On Thu, 5 Mar 2015 12:47:36 + > Neil Bothwick wrote: > >> On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: >> >> > > > > Is /var on your root filesystem? If so, it sounds like something >> > > > > is trying to write to it before it has been remounted rw. Try >> > > > > adding rw (and removing ro if present) to your kernel options. >> > > > > >> > > > >> > > > Ok, thanks. What file should I write these options to? >> > > >> > > Your bootloader config, that's where you specify the kernel boot >> > > options. >> > >> > That's what I thought, however I use gummiboot. Can you give an >> > example, to show your gummiboot config once again? >> >> Add it to the options line in the relavent file in /boot/loader/entries. >> >> Or test it first by pressing e at the menu and adding it there > > > So any other idea on hhow to fix it? Anyone? Can you please post the output of the following commands? stat /lib64/rc stat /lib64/rc/cache
Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
* Marc Joliet [150305 04:47]: [..SNIP..] > 1.) The NIC is brought up (some built-in Intel model). > > 2.) A DHCP client configures it. > > 3.) The network connection is lost at some point (the amount of time this > takes > varies, but it can be as little as 20 minutes). > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, but > gets no response. Sometimes, after many hours (at least 6), it will get a > DHCPACK, but that's it. One of our sysadmins says that not only does > the DHCP server never see the packets, but the managed switch that the PC > is directly attached to *also* never does (again, except for when the > occasional DHCPACK comes). > > 4.) Restart the network device. A reboot is not required, but it is necessary > to terminate the DHCP client. After that everything works again. > > 5.) GOTO 3. [..SNIP..] Is this a WiFi NIC? Is it possible the device is powering down? I've had lots of problems with WiFi devices powering down (both driver issues as well as just trying to disable the default setting of powering down.) Todd
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 12:47:36 + Neil Bothwick wrote: > On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: > > > > > > Is /var on your root filesystem? If so, it sounds like something > > > > > is trying to write to it before it has been remounted rw. Try > > > > > adding rw (and removing ro if present) to your kernel options. > > > > > > > > > > > > > Ok, thanks. What file should I write these options to? > > > > > > Your bootloader config, that's where you specify the kernel boot > > > options. > > > > That's what I thought, however I use gummiboot. Can you give an > > example, to show your gummiboot config once again? > > Add it to the options line in the relavent file in /boot/loader/entries. > > Or test it first by pressing e at the menu and adding it there So any other idea on hhow to fix it? Anyone? > > > -- > Neil Bothwick > > Fragile. Do not turn umop ap1sdn! -- German
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, Mar 5, 2015 at 12:08 PM, Neil Bothwick wrote: > On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote: > >> I personally use dracut which has quite a few bells and whistles. If >> you're using systemd as has already been pointed out it runs the >> journal during early boot and merges it into the system journal when >> it pivots. I believe that if you're not using systemd it captures >> whatever it does to a log file in /run, > > My understanding of the man page is that it only does that if you use the > rd.debug option. That wouldn't surprise me. I tend to use that option since I run stuff like root on btrfs, or root on nfs with kernel/initramfs over PXE and such - so you can imagine I'm a bit more likely to run into bugs than the typical root-on-ext4-sda1 sort. -- Rich
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote: > I personally use dracut which has quite a few bells and whistles. If > you're using systemd as has already been pointed out it runs the > journal during early boot and merges it into the system journal when > it pivots. I believe that if you're not using systemd it captures > whatever it does to a log file in /run, My understanding of the man page is that it only does that if you use the rd.debug option. -- Neil Bothwick Gigabyte: (n.) more than you can comprehend and less than you'll need. pgpYIpKa3PgST.pgp Description: OpenPGP digital signature
Re: [gentoo-user] No 'libs' in world file?
On Wed, Mar 4, 2015 at 8:06 AM, Walter Dnes wrote:
> On Tue, Mar 03, 2015 at 12:01:04AM +0100, Andreas K. Huettel wrote
>
> > Well... let's say it like this:
> >
> > If you look at your world file, you should for each line be able to
> > immediately say "yes I know what this is and I need it". Where "I need
> it"
> > means "I need it directly", and *not* "I need it because some other
> package
> > needs it".
> >
> > In most cases this means that libraries should not be in the world file.
> > You'll rarely say "Yes I need Boost." Instead you may need LibreOffice,
> and
> > that needs Boost...
>
> Rather than try to remember everything, let the computer do some of
> the work for you (novel idea ). Use the command...
>
> xargs -a /var/lib/portage/world -n 1 equery d
>
Just thought of using 'equery d $(
> to determine which files would be pulled in as dependancies.
> ***WARNING: DO NOT REDIRECT OR PIPE***. It won't work. Use a 2nd term
> for the output, along with {CTRL-S} and {CTRL-Q} to stop and restart the
> output. You'l have to run the command with root privileges to see the
> file /var/lib/portage/world Here's how it starts off for me...
>
>
> [d531][root][~] xargs -a /var/lib/portage/world -n 1 equery d
> * These packages depend on app-admin/localepurge:
> * These packages depend on app-admin/logrotate:
> * These packages depend on app-admin/sudo:
> * These packages depend on app-admin/syslog-ng:
> * These packages depend on app-arch/zip:
> sys-devel/gcc-4.8.3 (app-arch/zip)
> www-client/seamonkey-2.32 (app-arch/zip)
>
> There are no ebuilds depending on localepurge, logrotate, sudo, or
> syslog-ng. It's up to you whether or not you want them. However, zip
> is an absolute dependancy of gcc and seamonkey, and can be removed from
> my world file. Absolute dependancies are easy. *BEWARE OF CONDITIONAL
> DEPENDANCIES*; e.g.
>
> * These packages depend on dev-perl/File-MimeInfo:
> x11-misc/xdg-utils-1.1.0_rc2 (perl ? dev-perl/File-MimeInfo)
>
> That says if you've built x11-misc/xdg-utils-1.1.9_rc2 withe the
> "perl" USE flag, then dev-perl/File-MimeInfo will be pulled in as a
> dependancy. You have to check whether you've used that USE flag on that
> ebuilds.
>
> And a "lib" is not necessarily always a direct dependancy. E.g. my
> HDHomerun OTA TV tuner requires the media-libs/libhdhomerun ebuild to be
> explicitly installed.
>
>
> Walter Dnes
> I don't run "desktop environments"; I run useful applications
>
>
Re: [gentoo-user]
If your trying to unsubscribe, your Email address you used was wrong... Remove the from the To: line and try again :) On 6/03/2015 1:02 AM, Ryan Tasson wrote: === Cut document turnaround time by 90% with CudaSign. Get unlimited eSignatures for just $1 per user/month. Get CudaSign now: https://www.cudasign.com DISCLAIMER: This e-mail and any attachments to it contain confidential and proprietary material of Barracuda, its affiliates or agents, and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, Mar 5, 2015 at 8:19 AM, Dale wrote: > > I just recall reading somewhere, systemd or not, that that is how it is > supposed to work. After all, it can't run fsck and such while mounted > rw from my understanding. Keep in mind that an initramfs is nothing more than an archive file containing some kind of init implementation (often just a shell script) that the kernel unpacks and launches. It does whatever it is designed to do. Some are more bare-boned than others. I personally use dracut which has quite a few bells and whistles. If you're using systemd as has already been pointed out it runs the journal during early boot and merges it into the system journal when it pivots. I believe that if you're not using systemd it captures whatever it does to a log file in /run, but I don't think it necessarily runs a full syslog listening to /dev/log and so on. That said, nothing is really running that early in boot so as long as it logs its own work you're fine. Often the level of logging is configurable. -- Rich
[gentoo-user]
=== Cut document turnaround time by 90% with CudaSign. Get unlimited eSignatures for just $1 per user/month. Get CudaSign now: https://www.cudasign.com DISCLAIMER: This e-mail and any attachments to it contain confidential and proprietary material of Barracuda, its affiliates or agents, and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 12:47:36 + Neil Bothwick wrote: > On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: > > > > > > Is /var on your root filesystem? If so, it sounds like something > > > > > is trying to write to it before it has been remounted rw. Try > > > > > adding rw (and removing ro if present) to your kernel options. > > > > > > > > > > > > > Ok, thanks. What file should I write these options to? > > > > > > Your bootloader config, that's where you specify the kernel boot > > > options. > > > > That's what I thought, however I use gummiboot. Can you give an > > example, to show your gummiboot config once again? > > Add it to the options line in the relavent file in /boot/loader/entries. > > Or test it first by pressing e at the menu and adding it there. Ok Neil, I hit e at the boot and added rw to boot option, so it looked like root=/dev/sda3 rw I still get cache is not writeable warning when system poweroffs. What else can be causing this? > > > -- > Neil Bothwick > > Fragile. Do not turn umop ap1sdn! -- German
Re: [gentoo-user] See bootup/poweroff screen?
cov...@ccs.covici.com wrote: > Dale wrote: > >> Neil Bothwick wrote: >>> On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: >>> Thanks Dale, done it. Unfortunately it doesn't log everything. For instance "Warning: /lib64/rc/cache is not writable" wasn't written to /var/log/rc.log >>> Of course it wasn't. Warnings about /var not being writeable are not going >>> to be written to /var. >>> >>> >> Yea, it won't catch everything. This is sort of designed for that point >> where one log stops and the other hasn't started yet. This is usually >> where dmesg stops and syslog and friends hasn't yet started. Of course, >> if /var isn't mounted, well, it has no where to go. >> >> Isn't those init thingys supposed to fix this sort of thing tho? Isn't >> it supposed to store it in memory until /var is mounted and then dump it? > Make sure your kernel log buffer is as high as it will go, I use 21 if > memory serves which is about a meg or so. Also, I find with an init > thingy and using systemd (Yes I know, don't start a flame war), then I > see everything in its system journal -- much more even than rc.log used > to give me. > I just recall reading somewhere, systemd or not, that that is how it is supposed to work. After all, it can't run fsck and such while mounted rw from my understanding. It's been to long ago since I read that tho. Add in that I'm kick boxing with the flu right now and things are fuzzy at least. That kernel log buffer does ring a bell somewhere out there. Dale :-) :-)
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 07:37:39 -0500, German wrote: > > > > Is /var on your root filesystem? If so, it sounds like something > > > > is trying to write to it before it has been remounted rw. Try > > > > adding rw (and removing ro if present) to your kernel options. > > > > > > > > > > Ok, thanks. What file should I write these options to? > > > > Your bootloader config, that's where you specify the kernel boot > > options. > > That's what I thought, however I use gummiboot. Can you give an > example, to show your gummiboot config once again? Add it to the options line in the relavent file in /boot/loader/entries. Or test it first by pressing e at the menu and adding it there. -- Neil Bothwick Fragile. Do not turn umop ap1sdn! pgpa4sVFPVHZz.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 12:34:05 + Neil Bothwick wrote: > On Thu, 5 Mar 2015 05:10:03 -0500, German wrote: > > > > Is /var on your root filesystem? If so, it sounds like something is > > > trying to write to it before it has been remounted rw. Try adding rw > > > (and removing ro if present) to your kernel options. > > > > > > > Ok, thanks. What file should I write these options to? > > Your bootloader config, that's where you specify the kernel boot options. That's what I thought, however I use gummiboot. Can you give an example, to show your gummiboot config once again? > > > -- > Neil Bothwick > > If at first you don't succeed, redefine success. -- German
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 05:10:03 -0500, German wrote: > > Is /var on your root filesystem? If so, it sounds like something is > > trying to write to it before it has been remounted rw. Try adding rw > > (and removing ro if present) to your kernel options. > > > > Ok, thanks. What file should I write these options to? Your bootloader config, that's where you specify the kernel boot options. -- Neil Bothwick If at first you don't succeed, redefine success. pgpM2a9W8iiyj.pgp Description: OpenPGP digital signature
Re: [gentoo-user] See bootup/poweroff screen?
Dale wrote: > Neil Bothwick wrote: > > On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: > > > >> Thanks Dale, done it. Unfortunately it doesn't log everything. For > >> instance "Warning: /lib64/rc/cache is not writable" wasn't written > >> to /var/log/rc.log > > > > Of course it wasn't. Warnings about /var not being writeable are not going > > to be written to /var. > > > > > > Yea, it won't catch everything. This is sort of designed for that point > where one log stops and the other hasn't started yet. This is usually > where dmesg stops and syslog and friends hasn't yet started. Of course, > if /var isn't mounted, well, it has no where to go. > > Isn't those init thingys supposed to fix this sort of thing tho? Isn't > it supposed to store it in memory until /var is mounted and then dump it? Make sure your kernel log buffer is as high as it will go, I use 21 if memory serves which is about a meg or so. Also, I find with an init thingy and using systemd (Yes I know, don't start a flame war), then I see everything in its system journal -- much more even than rc.log used to give me. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 12:22:07 +0200 Alan McKinnon wrote: > On Thu, 5 Mar 2015 03:09:46 -0500 > German wrote: > > > How to fix this? Thanks > > > > I haven't the foggiest idea. > > > But, in your shoes, I'd probably find out more about chown and chmod Perhaps it sholdn't be writable. I thought about chmod +x but decided to wait before I hear a few explainations about what's going on > > > -- > alan.mckin...@gmail.com > -- German
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 03:09:46 -0500 German wrote: > How to fix this? Thanks > I haven't the foggiest idea. But, in your shoes, I'd probably find out more about chown and chmod -- alan.mckin...@gmail.com
Re: [gentoo-user] No network ( Solved, I am connected, thanks)
On Thu, 05 Mar 2015 09:36 + Peter Humphrey wrote: > On Wednesday 04 March 2015 21:26:53 German wrote: > > On Wed, 4 Mar 2015 18:25:07 + > > Mick wrote: > > > Now that you're connected, or should I say BEFORE you got connected, > > > you should also consider configuring a firewall for your IPv4 > > > (and/or IPv6) network. > > > > What package I should use for this on a console? I want something > > simple but efficient. > > I use shorewall. It's not too hard to understand and I haven't seen any > reports of problems with it. Thanks for recommendation > > -- > Rgds > Peter. > > -- German
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 08:24:44 + Neil Bothwick wrote: > On Thu, 5 Mar 2015 03:09:46 -0500, German wrote: > > > How to fix this? Thanks > > Is /var on your root filesystem? If so, it sounds like something is > trying to write to it before it has been remounted rw. Try adding rw (and > removing ro if resent) to your kernel options. > Ok, thanks. What file should I write these options to? > > -- > Neil Bothwick > > For security reasons, all text in this mail is double-rot13 encrypted. -- German
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, 05 Mar 2015 03:16:55 -0600, Dale wrote: > > Of course it wasn't. Warnings about /var not being writeable are not > > going to be written to /var. > Yea, it won't catch everything. This is sort of designed for that point > where one log stops and the other hasn't started yet. This is usually > where dmesg stops and syslog and friends hasn't yet started. Of course, > if /var isn't mounted, well, it has no where to go. > > Isn't those init thingys supposed to fix this sort of thing tho? Isn't > it supposed to store it in memory until /var is mounted and then dump > it? The combination of dracut and systemd means it all goes in the journal. The journal is kept in memory and then flushed to disk later in the boot process. journalctl is rather neat, being able to search both dmesg and system logs in one go, and apply various search criteria, is far more flexible than the alternatives. -- Neil Bothwick WWW: World Wide Wait pgpaZAm1M5h1e.pgp Description: OpenPGP digital signature
[gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
Hi all,
at work I'm (well, *we* are) facing an interesting problem. Since we are sort
of stabbing in the dark here, I thought I'd ask here. Also, since this is from
work, I will not be able to diverge very many details (not to mention that as a
student worker I simply don't *know* many details). However, I do have
permission from my boss to ask about this in an anonymised fashion.
The symptom we're seeing is that the NIC goes down and DHCP packets stop getting
through after a certain amount of time. What happens is:
1.) The NIC is brought up (some built-in Intel model).
2.) A DHCP client configures it.
3.) The network connection is lost at some point (the amount of time this takes
varies, but it can be as little as 20 minutes).
4.) Eventually the lease runs out and the DHCP client tries to renew it, but
gets no response. Sometimes, after many hours (at least 6), it will get a
DHCPACK, but that's it. One of our sysadmins says that not only does
the DHCP server never see the packets, but the managed switch that the PC
is directly attached to *also* never does (again, except for when the
occasional DHCPACK comes).
4.) Restart the network device. A reboot is not required, but it is necessary
to terminate the DHCP client. After that everything works again.
5.) GOTO 3.
(Note that I have observed that steps 3 and 4 do not necessarily occur in
order.)
This has been rather baffling, since this problem is limited to 3 computers.
One of them (the longest running) runs Gentoo, courtesy of me. This is the
first one we saw the problem with. Since we couldn't figure it out (switching
from dhcpcd to dhclient, turning off the firewall, monitoring with tcpdump,
etc., all with help from one of our sysadmins; Google, too, of course), Gentoo
was "blamed", so we got a replacement PC with Fedora 20 on it, which *also*
showed this behaviour. Both PCs run some special software (some of it mine).
Thus, at some point this software was "blamed".
So we started experimenting: we configured the Fedora PC to *not* start the
special software, and have not seen any problems all week. Yesterday afternoon
I then started *one* of the programs, and had not seen any problems yet by the
time I went home.
So that would speak *for* that theory, right? Well, for comparison, my boss
recently started running a separate PC, also with a bog-standard Fedora 20.
Guess what: it *also* shows the *exact* same behaviour as the other two PCs
("journalctl -u NetworkManager" shows pages upon pages of unanswered
DHCPREQUESTs, with the occasional response thrown in). Note here that this PC
is on a different switch and in a different VLAN.
The choice of Fedora comes from the fact that we use a Fedora based distro
internally, so it is "known". PCs running it have *not* shown the behaviour
above (AFAIK not even *once*). Thus, one of the few things I can think of is
finding out what is different about them relative to the standard Fedora.
Right now my main ideas on what the culprit could be are:
- The computers' kernel/network device is improperly configured. That is,
maybe special configuration is needed for the computers to work properly as
clients in the network. I'm thinking of support for some (from my
perspective) obscure protocol(s).
- It's a network problem. The three computers are in two different VLANs,
while the workplace computers running the internal Fedora based distro are in
a third (the main network that all the normal Windows and Linux workstations
are connected to). However, they are on the same switch as the two computers
running my software. One argument against this is that the Windows PC that
runs on the same VLAN does *not* have any problems like this.
One of the other ideas I had was faulty power management, and I did read of
problems of the sort regarding the exact same network card that is in the old
Gentoo machine on an HP support forum (from around 2008). However, the local
sysadmin said that they have had nothing but good experience with those network
cards. Also: *three* computers with NIC power management problems? That sounds
a bit far-fetched to me. Nevertheless, I am not fully discounting the
possibility.
You can imagine how confusing and frustrating this is.
So, has anybody here ever experienced something like this? Any ideas on what
could be the cause?
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
pgp9dnj00NEdP.pgp
Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] No network ( Solved, I am connected, thanks)
On Wednesday 04 March 2015 21:26:53 German wrote: > On Wed, 4 Mar 2015 18:25:07 + > Mick wrote: > > Now that you're connected, or should I say BEFORE you got connected, > > you should also consider configuring a firewall for your IPv4 > > (and/or IPv6) network. > > What package I should use for this on a console? I want something > simple but efficient. I use shorewall. It's not too hard to understand and I haven't seen any reports of problems with it. -- Rgds Peter.
Re: [gentoo-user] See bootup/poweroff screen?
Neil Bothwick wrote: > On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: > >> Thanks Dale, done it. Unfortunately it doesn't log everything. For >> instance "Warning: /lib64/rc/cache is not writable" wasn't written >> to /var/log/rc.log > > Of course it wasn't. Warnings about /var not being writeable are not going > to be written to /var. > > Yea, it won't catch everything. This is sort of designed for that point where one log stops and the other hasn't started yet. This is usually where dmesg stops and syslog and friends hasn't yet started. Of course, if /var isn't mounted, well, it has no where to go. Isn't those init thingys supposed to fix this sort of thing tho? Isn't it supposed to store it in memory until /var is mounted and then dump it? Dale :-) :-)
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: > Thanks Dale, done it. Unfortunately it doesn't log everything. For > instance "Warning: /lib64/rc/cache is not writable" wasn't written > to /var/log/rc.log Of course it wasn't. Warnings about /var not being writeable are not going to be written to /var. -- Neil Bothwick Why is bra singular and pants plural? pgpLOBeY3eDtd.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Warning: /lib64/rc/cache is not writable
On Thu, 5 Mar 2015 03:09:46 -0500, German wrote: > How to fix this? Thanks Is /var on your root filesystem? If so, it sounds like something is trying to write to it before it has been remounted rw. Try adding rw (and removing ro if resent) to your kernel options. -- Neil Bothwick For security reasons, all text in this mail is double-rot13 encrypted. pgpvOUPSrgPDT.pgp Description: OpenPGP digital signature
[gentoo-user] Warning: /lib64/rc/cache is not writable
How to fix this? Thanks -- German
Re: [gentoo-user] See bootup/poweroff screen?
On Thu, 05 Mar 2015 00:17:34 -0600 Dale wrote: > German wrote: > > I have a SSD in my laptop and the system boots really fast so I can't see > > the details of the warnings it displays. Are there any way to scroll the > > screen or see some system boot's logs? Thanks > > > > > You may want to read this post and try this method too. I did this ages > ago and on occasion, it helps. > > http://forums.gentoo.org/viewtopic-p-7682938.html#7682938 > > It should scroll to it but it's the second post that is made by PeGa! > that may help. The messages go to this file: /var/log/rc.log > > Dale > > :-) :-) * > * Thanks Dale, done it. Unfortunately it doesn't log everything. For instance "Warning: /lib64/rc/cache is not writable" wasn't written to /var/log/rc.log -- German
