Re: How to recover when monitor goes blank.
Did you try 'e' as I suggested, or read that page? From there: [quote] 'e' will force the display to be enabled, i.e. it will override the detection if a display is connected. [/quote] Ok, I will try it, but that is a reboot. I guess if I booted with that switch, it will always be on and I would not reach a point of blank screen. Make sense. I just do not like forcing resolution, but better than broken display. Regards Ramesh
Re: How to recover when monitor goes blank.
Not to recover, but to perhaps prevent, via kernel cmdline, one can direct the kernel which framebuffer mode to force-enable with video=, e.g.: video=2560x1440@60e https://www.kernel.org/doc/Documentation/fb/modedb.txt -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata I think kernel thinks that no monitor is attached or KB is present. I want to remote login and tell it to look again and find them. It appears like there is no magic incantation exists for that. I was hoping a write to /sys or /proc file will do the trick, but no such thing seem to exists. Regards Ramesh
Re: How to recover when monitor goes blank.
My Debian machines have Xfce. I configure Applications Menu -> Settings-> Power Manager -> Display -> Display power management -> Off. David This is not a dpms issue. This is the OS thinking that it is not attached to a monitor/KB. I can remote login and remove dpms any time. Besides this happens in a VT also where there is no xfce. I just do not know how to tell Linux/OS that a monitor and kb is attached and it should look for enabling the respective drivers. I thought xrandr is the way to go, but that is only when Xorg is running and not when we are at a VT login prompt. Regards Ramesh
How to recover when monitor goes blank.
Hi, I have my monitor, keyboard and mouse shared through a KVM switch. One host is Linux Debian bookworm 12.5 and another is laptop running Windows 11. When I leave KVM on the laptop side for extended period I have issues switching back to Debian side. When I switch, the screen is blank and KB does not respond as if Debian is running headless. I had to remote login and reboot Debian side with KVM locked on this side to get back the monitor/KB. This happens regardless of whether I am in Xorg or VT. I do not know how to force Debian/Linux to check for monitor/KB again after extended period of disconnect when it has assumed it is running headless. Any solutions? Regards Ramesh
grub-efi install on multiple ESPs.
Hi, I have debian bookworm installed on a raid1 made from /dev/nvme0n1p3 and /dev/nvme1n1p3. Here are the partitions on the two nvme. /dev/nvme0n1p1 = /dev/nvme1n1p1 = 7mb ef02 /dev/nvme0n1p2 = /dev/nvme1n1p2 = 7mb ef00 (Two distinct ESPs on two different nvmes) /dev/nvme0n1p3 = /dev/nvme1n1p3 = 7mb 8300 (Linux RAID) I am currently using /dev/nvme*1*n1p2 as /boot/efi and groub-efi is installed there. I like to also install grub-efi on /dev/nvme*0*n1p1 to mimic RAID1. My Google search does not give me a clear way to do it. There are a lot explanation on how certain things are to be done. Nothing succinctly describes the grub-install step. Since this is boot and grub, I like to be sure before I mess up some uefi files and make the system unbootable. Can I mount the second esp on /mnt and do a simple grub-install --efi-directory=/mnt? Or should I undo current /boot/efi mount and mount second esp there and do a grub-install? I was going to try a dry-run option, but I do not see one in "man grub-install." Regards Ramesh
Re: How do I specify a custom apt dependency between kernel image and its headers?
If I understand you correctly, you want to set it up so that for every package pair linux-image- linux-headers- attempting to install the former results in also installing the latter? And you want this to apply not just for a specific version number, but for every version number, including ones that haven't come out yet? Yes this is what I want. Just off the top of my head, I don't think there's any way to accomplish that. The only possible avenue I can think of for adding an effective I was hoping I can add some rule based on regex in /etc/apt/preferences.d that will accomplish this. Well, if there isn't one then there is nothing much I can do. Since the system is accessible by ssh even if screen goes blank by a imperfect install of just linux-image, I can always ssh and then install headers and reinstall image to get nvidia-driver rebuilt and reboot. So, it is not that I am completely broken without this rule, but I wish it is something that can force/automate. Thanks for taking the time to respond with detail. Before I go, I have one question. When I try to install linux-image, apt tries to trigger a nvidia-driver build, but fails because headers are not present. However, it still completes the image install and changes grub menu etc. I prefer it stopped and complained. Is there a way to tell it to error out on this step, so that I will be prompted to look at this more closely? Typically, this message flies by on the screen and I was lucky that I saw it the last time. Regards Ramesh
How do I specify a custom apt dependency between kernel image and its headers?
I have nvdia card that requires binary driver to work in my system. Xorg is unable display anything with free driver. Since nvidia-driver has to be built for each kernel install, I need to install headers also. This seem to work automatically for any standard kernel release in bullseye. However when I install newer kernel from backport, apt does not install headers automatically. How do I tie the install of linux-image to linux-header so that I cannot install image without the headers. Regards Ramesh
Re: Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
Hi Ramesh, this might help. The bug is fixed with kernel 6.0.2-1 https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1 All the best to you Eike Elke, Thanks. v6.1 is available on bullseye-backports. I installed it and the trouble is gone now. BTW, does non-free firmware tied to kernel version? I use firmware-realtek to deal with my dragon 2.5G NIC that seems to be unstable without realtek-firmware. I want to make sure I use the correct version (for linux v6.1), if there is such a requirement. Regards Ramesh
I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.
I wanted to upgrade my server from 10 year old HW to something newer. THis server runs debian bullseye with v5.19 kernel from backports. Here is the list of items I got in the upgraded system 1. Intel z690 mother board (asrock steel legend) 2. Core i3-13100 cpu 3. Super Flower 650W PSU, 4. G.SKILL DDR4 RAM 5. 2x SK hynix P31 nvme SSD 1TB each. I reused these from old build 1. Geforce GT 630 video card 2. SAS9211i HBA card for extra SATA ports 3. All my large spinning drives that contained data in RAID6 and RAID1 I made a raid1 on mvme ssd and created 3 partitions. In one I installed debian testing (bookworm with v6.1 kernel) and in another, I image copied the old installation I had before the HW upgrade. Debian bookworm runs fine and reboots/shutsdown as expected. My old system copied over also works fine for most part. It boots and runs everything that I care about. All my RAID disks are working. No issue as long as it runs. The only trouble I have is that it refuses to reboot/shutdown/poweroff. It seem to go through all steps and reach the end but seem to get stuck in this endless cycle complaining about some blkdev issue. Here are the last lines printed on the console that shows the cycle [OK] Reached target Power-off [67652.NN] block device autoloading is deprecated and will be removed [67667.NN] blkdev_get_no_open: 119 callbacks suppressed I assume by "[OK]..." line that we are really at the end of shut down process. When I turn off physically using power switch and reboot, I do not get any fsck error messages. So, I assume that filesystems are safe and kernel is somehow lost in some thread and cannot end the reboot process. Any ideas what I can do? Regards Ramesh
Re: My X freezes on cold days - how to get back control
Hi, When left overnight in dpms state, my Xorg stays in that stateignoring any key inputs when I attempt to use the system next daymorning. This happens only when the overnight temps go low enough totrigger some issue. I can login remotely, but cannot kill Xorg with anyof the known signals. I tried using sysrq methods to get backkeyboard/screen control, but that does not work either. Nothing otherthan soft or hard reboot works. Last night, I tried to add a crontab entry to exit Xorg around 1am to see if the console also locks up. It did not. However, this is just one day of testing. Will try doing this for the next week before concluding that this works. Ramesh
Re: My X freezes on cold days - how to get back control
This sounds suspiciously like a hardware issue: a loose connector or a loose IC in its socket. I'd shut the thing down, and remove and re-insert every connector. If that doesn't work, do the same, and open up the case and re-seat cards, ICs, and cables. I'd also tighten up any screws. I thought I did this the last year this happened. However, I might have missed some items in your checklist. Will do it again. I thought exactly like you the first time this happened. So, I am happy that I was not imagining things. Regards Ramesh
My X freezes on cold days - how to get back control
Hi, When left overnight in dpms state, my Xorg stays in that state ignoring any key inputs when I attempt to use the system next day morning. This happens only when the overnight temps go low enough to trigger some issue. I can login remotely, but cannot kill Xorg with any of the known signals. I tried using sysrq methods to get back keyboard/screen control, but that does not work either. Nothing other than soft or hard reboot works. Most of the time I can reboot remotely and to get back everything, but sometimes, even that does not work. After issuing reboot, remote connection closes and the system stays on. I have to push the power button and hold for PS to power off and do a hard power cycle to get the system back. My system is based on "ASRock X570 PRO4 AMD AM4 ATX" motherboard and "AMD Ryzen 5 3600" CPU. I also have a Nvidia 1030 GPU based video card with binary driver installed. Here is my SW info: Debian bullseye Linux 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux Following nvidia related packages are installed in addition to standard Xorg that comes with bullseye. i A glx-alternative-nvidia - allows the selection of NVIDIA as GLX provider i A libnvidia-glcore - NVIDIA binary OpenGL/GLX core libraries i A libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library i A nvidia-alternative - allows the selection of NVIDIA as GLX provider i nvidia-detect - NVIDIA GPU detection utility i A nvidia-installer-cleanup - cleanup after driver installation with the nvidia-installer i A nvidia-kernel-common - NVIDIA binary kernel module support files i A nvidia-kernel-dkms - NVIDIA binary kernel module DKMS source i A nvidia-kernel-support - NVIDIA binary kernel module support files i A nvidia-legacy-check - check for NVIDIA GPUs requiring a legacy driver i A nvidia-modprobe - utility to load NVIDIA kernel modules and create device nodes i A nvidia-settings - tool for configuring the NVIDIA graphics driver i nvidia-smi - NVIDIA System Management Interface i A nvidia-support - NVIDIA binary graphics driver support files i A nvidia-vdpau-driver - Video Decode and Presentation API for Unix - NVIDIA driver i nvidia-vulkan-common - NVIDIA Vulkan driver - common files i xserver-xorg-video-nvidia - NVIDIA binary Xorg driver Please let me know if there is something I can do before changing my video card. Regards Ramesh
Re: How to reset one ethernet port?
charles@hawk:~$ apt-file search rtl_nic/rtl8168g-2.fw firmware-realtek: /lib/firmware/rtl_nic/rtl8168g-2.fw charles@hawk:~$ You should do similarly. If the log shows that the driver wants firmware but can't find it, you may need to install the appropriate firmware package. I understand that some hardware will work without the firmware blob, but work much better with it. This may be one of those situations. I remember reading somewhere (while researching to buy my hardware) that they had to remove firmware to make the NIC work. So, I thought I should not install any binary firmware. Now that I hear that you are using the firmware, I am going to try adding it to see if that changes anything. Let us hope it is just this. Regards Ramesh
Re: How to reset one ethernet port?
> This is the lspci output on the two ethernet port.
>
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Find out the kernel module that supports it ('lspci -v -s 02:00.0 | grep
-i kernel' or similar should do it), then rmmod and modprobe it.
If all else fails, check your logs to be sure your kernel module is
loading the correct binary blob (from the firmware-realtek package).
I only have firmware-linux-free and both NIC use the same kernel driver
yoda [rramesh] 313 > sudo lspci -v -s 02:00.0 | fgrep -i kernel
Kernel driver in use: r8169
Kernel modules: r8169
yoda [rramesh] 314 > sudo lspci -v -s 03:00.0 | fgrep -i kernel
Kernel driver in use: r8169
Kernel modules: r8169
I like to only work on the broken NIC and not touch the other, if
possible. However, if the other solution (from Dan) does not work, I
will try this one. If not, there is always warm or cold reboot since
this issue happens only after a week or two.
Regards
Ramesh
How to reset one ethernet port?
Hi, I have a linux based firewall that seem to hang because one of its ethernet port stops working. I suspect bad hardware, but could be a driver issue also. So far, I have only been able to reboot to get it working. However, I prefer to reset the port to get it working without a reboot. Is it possible to do something with ifconfig/ifup/ethtool? Simple ifdown followed by ifup does not fix it. My system is this: https://www.amazon.com/Generation-Processor-Beelink-U59-Computer/dp/B0B7729Q3M/ref=sr_1_44_sspa?keywords=dual%2Bnet&qid=1661469460&s=pc&sr=1-44-spons&th=1 It is running this: Linux yoda 5.18.0-0.deb11.3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.14-1~bpo11+1 (2022-07-28) x86_64 GNU/Linux PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian /etc/debian_version = 11.5 This is the lspci output on the two ethernet port. 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Note that the kernel is from backport to work with newer intel CPU (N5105) Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
On 7/15/22 00:31, Ram Ramesh wrote: On 7/14/22 09:15, Ram Ramesh wrote: Hi Ramesh, There are numerous reports (mostly old, afaics) of the issue you describe, but with various suggested reasons. I suspect the avahi related part is a consequence rather than a cause - I didn't think avahi was capable of disabling interfaces, the message looks like it's updating a table/list (etc) and "...no longer relevant..." messages appear in my syslog if I deliberately disconnect from wifi. Please can you provide syslog extracts from just before and during a time when this has happened, using: $ sudo cat /var/log/syslog | grep -i -E "avahi|network" (must be capital -E and no spaces around the | inside the speech marks) Is there anything that seems relevant in $ sudo dmesg -T ? Out of interest, did you try running for a while with just the power management tweak? Thanks, Gareth Yes, I believe I did. I did not use /sys/... power/control method. Instead, I kept the network alive by "ping -i 60 ". However, I am not 100% sure of this. So, I will revert some of my changes and get you the relevant logs. Thanks for your continued interested in this matter. Regards Ramesh Mmm... It has been about 10 hours since my reboot after removing "deny-interfaces=$extif," and I have not had the earlier issue of interface disappearing. I will let it run overnight to see. However, I think I wont be able to reproduce the problem. Earlier, I was trying to keep the interface alive with "ping -i 60 xxx" instead of setting "/sys/usb/ power/control" to "on". Not sure if that was not enough and $extif actually powered off in between pings and avahi-daemon was simply reporting this in daemon.log. However, kernel reset the interface status and (may be) dhclient was not written to handle this sort of issue. So, it simply could not work with the interface anymore as it was not initialized to perform DHCP. I wonder why this did not affect ping as it was chugging along without any issues. That is too many wild guesses and I am not sure why the problem does not exists now. I will update again later tomorrow when it has run another 12+ hours. Regards Ramesh No issues still. So, I will call this done for now and report again, if this shows up after a few days. Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
On 7/14/22 09:15, Ram Ramesh wrote: Hi Ramesh, There are numerous reports (mostly old, afaics) of the issue you describe, but with various suggested reasons. I suspect the avahi related part is a consequence rather than a cause - I didn't think avahi was capable of disabling interfaces, the message looks like it's updating a table/list (etc) and "...no longer relevant..." messages appear in my syslog if I deliberately disconnect from wifi. Please can you provide syslog extracts from just before and during a time when this has happened, using: $ sudo cat /var/log/syslog | grep -i -E "avahi|network" (must be capital -E and no spaces around the | inside the speech marks) Is there anything that seems relevant in $ sudo dmesg -T ? Out of interest, did you try running for a while with just the power management tweak? Thanks, Gareth Yes, I believe I did. I did not use /sys/... power/control method. Instead, I kept the network alive by "ping -i 60 ". However, I am not 100% sure of this. So, I will revert some of my changes and get you the relevant logs. Thanks for your continued interested in this matter. Regards Ramesh Mmm... It has been about 10 hours since my reboot after removing "deny-interfaces=$extif," and I have not had the earlier issue of interface disappearing. I will let it run overnight to see. However, I think I wont be able to reproduce the problem. Earlier, I was trying to keep the interface alive with "ping -i 60 xxx" instead of setting "/sys/usb/ power/control" to "on". Not sure if that was not enough and $extif actually powered off in between pings and avahi-daemon was simply reporting this in daemon.log. However, kernel reset the interface status and (may be) dhclient was not written to handle this sort of issue. So, it simply could not work with the interface anymore as it was not initialized to perform DHCP. I wonder why this did not affect ping as it was chugging along without any issues. That is too many wild guesses and I am not sure why the problem does not exists now. I will update again later tomorrow when it has run another 12+ hours. Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
Hi Ramesh, There are numerous reports (mostly old, afaics) of the issue you describe, but with various suggested reasons. I suspect the avahi related part is a consequence rather than a cause - I didn't think avahi was capable of disabling interfaces, the message looks like it's updating a table/list (etc) and "...no longer relevant..." messages appear in my syslog if I deliberately disconnect from wifi. Please can you provide syslog extracts from just before and during a time when this has happened, using: $ sudo cat /var/log/syslog | grep -i -E "avahi|network" (must be capital -E and no spaces around the | inside the speech marks) Is there anything that seems relevant in $ sudo dmesg -T ? Out of interest, did you try running for a while with just the power management tweak? Thanks, Gareth Yes, I believe I did. I did not use /sys/... power/control method. Instead, I kept the network alive by "ping -i 60 ". However, I am not 100% sure of this. So, I will revert some of my changes and get you the relevant logs. Thanks for your continued interested in this matter. Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
Hi Ramesh, Please could you post some example daemon.log entries and any surrounding entries that seem related? Also is there anything in /var/log/syslog that seems to relate? Perhaps $ sudo cat /var/log/syslog | grep x where x = the interface name concerned. Thanks, Gareth Hi Gareth, This is what I find in daemon.log Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for fe80::daeb:97ff:febf:5ad0 on enxd8eb97bf5ad0. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for 192.168.1.124 on enxd8eb97bf5ad0. After this happens, most of my net access goes down. Firefox cannot get to google.com/youtube.com. DNS lookup also returns nothing for external hosts. I see similar messages on /var/log/syslog also Jul 12 18:27:16 new-yoda avahi-daemon[441]: Interface enxd8eb97bf5ad0.IPv6 no longer relevant for mDNS. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Leaving mDNS multicast group on interface enxd8eb97bf5ad0.IPv6 with address fe80::daeb:97ff:febf:5ad0. Jul 12 18:27:16 new-yoda dhclient[550]: receive_packet failed on enxd8eb97bf5ad0: Network is down Jul 12 18:27:16 new-yoda avahi-daemon[441]: Interface enxd8eb97bf5ad0.IPv4 no longer relevant for mDNS. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Leaving mDNS multicast group on interface enxd8eb97bf5ad0.IPv4 with address 192.168.1.124. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for fe80::daeb:97ff:febf:5ad0 on enxd8eb97bf5ad0. Jul 12 18:27:16 new-yoda avahi-daemon[441]: Withdrawing address record for 192.168.1.124 on enxd8eb97bf5ad0. Jul 12 18:27:17 new-yoda kernel: [ 8560.412306] asix 1-1:1.0 eth0: register 'asix' at usb-:00:14.0-1, ASIX AX88772 USB 2.0 Ethernet, d8:eb:97:bf:5a:d0 Jul 12 18:27:17 new-yoda NetworkManager[448]: [1657668437.0609] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/6) Jul 12 18:27:17 new-yoda systemd-udevd[1494]: Using default interface naming scheme 'v247'. Jul 12 18:27:17 new-yoda systemd-udevd[1494]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 12 18:27:17 new-yoda kernel: [ 8560.449674] asix 1-1:1.0 enxd8eb97bf5ad0: renamed from eth0 Jul 12 18:27:17 new-yoda NetworkManager[448]: [1657668437.1103] device (eth0): interface index 5 renamed iface from 'eth0' to 'enxd8eb97bf5ad0' Jul 12 18:27:17 new-yoda systemd-udevd[1494]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jul 12 18:27:19 new-yoda ModemManager[489]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin Looks like kernel finds usb NIC again and tries to do something? Since dhclient is not aware, it does not know how to handle. I get this from dhclient for the *next* DHCPDISCOVER/REQUEST Jul 12 19:45:04 new-yoda dhclient[550]: DHCPREQUEST for 192.168.1.124 on enxd8eb97bf5ad0 to 192.168.1.254 port 67 Jul 12 19:45:04 new-yoda dhclient[550]: send_packet: Network is unreachable Jul 12 19:45:04 new-yoda dhclient[550]: send_packet: please consult README file regarding broadcast address. Hope you can find something useful. For now, I simply edited avahi-daemon.conf and denied this interface as one not to be observed/managed. That fixed the part of the problem. Other issue is reported in one of my followup. Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
On 7/12/22 19:21, Ram Ramesh wrote: On 7/11/22 11:30, Ram Ramesh wrote: Experts, I have a firewall machine built recently and it runs debian bullseye (v11). It has two ethernet interfaces - one internal ($intf) and one external ($extf). My external port runs dhclient to get its IP address and internal port runs dnsmasq to provide DNS service to internal/protected hosts. Usual iptables rules are established to prevent attack/entry into internal net from external net and allow proper internet access to internal net hosts. I had this system working fine (on an older machine) since debian 5.0.7. I have not upgraded that machine as it is working fine. However that hardware is too old (10+ years) and I wanted to replace it with something more modern running latest OS and that is why I built the above machine. My old machine does not seem have avahi-daemon. So, it runs fine. However, my new machine has this daemon running which notices that $extif does not have much activity and disables it after some timeout idle time. I initially thought my firewall rules are suspect and was banging my head for a while adding extra rules for DHCPDISCOVER/REQUEST etc thinking that those are blocked. Today I noticed that my $extif is vanishing and /var/log/daemon.log shows some avahi-daemon messages about that interface being disabled/withdrawn or some such thing. As a next step, I want to tell avahi-daemon that it should not work on that interface as it is not meant to be fooled around. Do I use deny-interface $extif or allow-interface $intif only? Which is proper? Will doing one of these solve my problem of $extif vanishing from ifconfig? If you think there is something else that I can do that is better, please let me know that too. Much appreciate any help. Please let me know if you need anything else that will help to resolve this problem. Regards Ramesh It appears that this is not an issue with avahi-daemon. My $extif is through usb NIC and that seem to go down due to some sort of powersave autosuspend. Currently I am running ping -i 60 and that keeps the net up and $extif has not vanished for a day. I did some googling on how to disable autosuspend, but answers were quite confusing. Do you know a simple way to disable autopowerdown of just this usb NIC? May be there is something that I can do with ethtool? Regards Ramesh I take back some of what I said. It is both - I mean usb autosupend+avahi_daemon. I need to keep the adaptor from autosuspending and tell avahi-daemon not to disable the interface in the OS. I also found the power/control entry in /sys/bus/usb/ for my usb NIC. It is not in the usual place. lsusb does not list my usb ethernet adapter at all. I had to manually search to find it and set its power/control to "on" With all this done, so far my net is up and running fine. Will wait a couple days with a couple of reboots to make sure I have captured all fixes in some boot scripts. After that this problem can be thought of as solved. Regards Ramesh
Re: avahi-daemon allow/deny interfaces question
On 7/11/22 11:30, Ram Ramesh wrote: Experts, I have a firewall machine built recently and it runs debian bullseye (v11). It has two ethernet interfaces - one internal ($intf) and one external ($extf). My external port runs dhclient to get its IP address and internal port runs dnsmasq to provide DNS service to internal/protected hosts. Usual iptables rules are established to prevent attack/entry into internal net from external net and allow proper internet access to internal net hosts. I had this system working fine (on an older machine) since debian 5.0.7. I have not upgraded that machine as it is working fine. However that hardware is too old (10+ years) and I wanted to replace it with something more modern running latest OS and that is why I built the above machine. My old machine does not seem have avahi-daemon. So, it runs fine. However, my new machine has this daemon running which notices that $extif does not have much activity and disables it after some timeout idle time. I initially thought my firewall rules are suspect and was banging my head for a while adding extra rules for DHCPDISCOVER/REQUEST etc thinking that those are blocked. Today I noticed that my $extif is vanishing and /var/log/daemon.log shows some avahi-daemon messages about that interface being disabled/withdrawn or some such thing. As a next step, I want to tell avahi-daemon that it should not work on that interface as it is not meant to be fooled around. Do I use deny-interface $extif or allow-interface $intif only? Which is proper? Will doing one of these solve my problem of $extif vanishing from ifconfig? If you think there is something else that I can do that is better, please let me know that too. Much appreciate any help. Please let me know if you need anything else that will help to resolve this problem. Regards Ramesh It appears that this is not an issue with avahi-daemon. My $extif is through usb NIC and that seem to go down due to some sort of powersave autosuspend. Currently I am running ping -i 60 and that keeps the net up and $extif has not vanished for a day. I did some googling on how to disable autosuspend, but answers were quite confusing. Do you know a simple way to disable autopowerdown of just this usb NIC? May be there is something that I can do with ethtool? Regards Ramesh
avahi-daemon allow/deny interfaces question
Experts, I have a firewall machine built recently and it runs debian bullseye (v11). It has two ethernet interfaces - one internal ($intf) and one external ($extf). My external port runs dhclient to get its IP address and internal port runs dnsmasq to provide DNS service to internal/protected hosts. Usual iptables rules are established to prevent attack/entry into internal net from external net and allow proper internet access to internal net hosts. I had this system working fine (on an older machine) since debian 5.0.7. I have not upgraded that machine as it is working fine. However that hardware is too old (10+ years) and I wanted to replace it with something more modern running latest OS and that is why I built the above machine. My old machine does not seem have avahi-daemon. So, it runs fine. However, my new machine has this daemon running which notices that $extif does not have much activity and disables it after some timeout idle time. I initially thought my firewall rules are suspect and was banging my head for a while adding extra rules for DHCPDISCOVER/REQUEST etc thinking that those are blocked. Today I noticed that my $extif is vanishing and /var/log/daemon.log shows some avahi-daemon messages about that interface being disabled/withdrawn or some such thing. As a next step, I want to tell avahi-daemon that it should not work on that interface as it is not meant to be fooled around. Do I use deny-interface $extif or allow-interface $intif only? Which is proper? Will doing one of these solve my problem of $extif vanishing from ifconfig? If you think there is something else that I can do that is better, please let me know that too. Much appreciate any help. Please let me know if you need anything else that will help to resolve this problem. Regards Ramesh
Re: memtest86+ on 12th gen intel
On 6/13/2022 12:27 PM, Bijan Soleymani wrote: Here's a post on the issues with memtest86+ (the free software version) and UEFI: https://askubuntu.com/questions/917961/can-i-boot-memtest86-if-im-using-uefi Sorry for the spam, looks like they just added UEFI support last week: https://www.memtest.org/ "Changelog * Rewrite code for UEFI 32 & 64 bits" Bijan Nothing worked. Both memtest86 and memtest86+ with grub or standalone boot did not work on my core-i312100. I suspect it is a display driver problem. My regular bullseye install itself had this blank screen problem. Only upgrading to kernel 5.16 from backport got my system working. Memtest is having very similar issues. With grub both versions of memtest removes menu and backgroud splash screen shows and no more activity. With boot USB, BIOS flashscreen, black screen, nothing more. If anyone got this working on a 12th gen core i3/5/7, please follow up and let me know how you got it working. Please copy me in your post, if it is while (aka months) before you see this and followup. Regards Ramesh
memtest86+ on 12th gen intel
I had memtest86+ working just fine on a legacy bullseye install. However, due to age of the CPU, I recently upgraded to 12th gen i3-12100. As part of the upgrade, I also changed over to UEFI boot. In addition I had to upgrade kernel to 5.16 using backports to get video working right. Now memtest86 in the grub menu does not work. Once selected, grub menu goes away and the background debian 11 canvas shows up and nothing after that. Memtest never starts. I removed memtest86+ and reinstalled and that did not help. I looked for it in backports and as far as I can tell there is no package matching memtest. Please help. I bought two sticks of RAM and would like to test it when possible. My search on internet did not bring up any useful article. May be I do not know how to search for this specific item. BTW, debian boots and runs as expected. Just that memtest does not start up. May be, just may be, it starts up, but cannot use iGPU (UHD 730, I think) to display activities. Regards Ramesh
Re: Debian 11 bullseye - will it work on 12th gen core i3-12100?
On 4/25/22 16:45, Dan Ritter wrote: Ram Ramesh wrote: My age old intel NUC with pentium N3700 is sick and needs What kind of "sick"? Not repairable? It randomly freezes and had to be hard rebooted. Tried replacing power supply and RAM and disk (all other are part of the NUC box), but that did not work. Ran various diagnostics that I can get hold of and no issue. If I do not use it/idle, it will not freeze for days. Since you've been inside the box, I expect you cleaned all the dust out -- but is there any chance that the CPU fan has frozen or is otherwise impeded? This really sounds like an overheating problem. -dsr- Earlier, I had not opened enuf to inspect heat sinks/fan. Today I did that and it kind of looked dirty. I cleaned and made sure fan spun readily. I did not take apart the heatsink to check the thermal paste. That looked too risky. Similarly, I did not check if the fan actually runs visually. There is some noise and mild airflow when I turn on. So, it should be working. After all this cleaning, the situation is the same. It dies randomly if I do something (like pause on some video) Only hard boot will work. So, not sure what kind of sickness it has. So, may be it is telling me to replace. Since syslog has nothing, I assume it is not something kernel can catch. Regards Ramesh
Re: Debian 11 bullseye - will it work on 12th gen core i3-12100?
> My age old intel NUC with pentium N3700 is sick and needs What kind of "sick"? Not repairable? It randomly freezes and had to be hard rebooted. Tried replacing power supply and RAM and disk (all other are part of the NUC box), but that did not work. Ran various diagnostics that I can get hold of and no issue. If I do not use it/idle, it will not freeze for days. Regards Ramesh
Re: Debian 11 bullseye - will it work on 12th gen core i3-12100?
Hi Ramesh, Debian 11 was released almost 1 year ago. For new hardware you will need Debian testing. For Debian 11 (current stable) you'll need second hand hardware. Kind regards Georgi Gorgi, Are you guessing or know this for a fact? What is second hand hardware? 11th gen or 10th gen intel? Sorry I am asking more questions. Thanks for your time. Please answer if you can. Regards Ramesh
Re: Debian 11 bullseye - will it work on 12th gen core i3-12100?
Do you _really_ need to swap the current disk? If not: put a new disk into new hardware and you only have to copy data over. Ideally NVME or something fast. You may find some use for the old NUC: the only reason I say this particularly is because you installed with BIOS boot and changing that may be as much trouble as a new install. mythtv - debian-multimedia - yours to sort out, I think, but again, you may find it easier to have a spare machine that (sort of) works while you debug the new NUC Hope this helps - with every good wish, as ever, Andy Cater Andy, My question is about compatibility of running debian bullseye on latest hardware. When I tried 10th gen core-i3 with buster, xorg did not work as it needed Linux 5.xx over the default 4.x on buster (at that time). I want to know if such a thing exists with 12th gen CPU. Another question is with legacy boot. I did think about swapping disk out. Suppose I fresh install UEFI bullseye, can I simply add a new partition and copy over old install and update-grub from fresh install to add the old system to menu? Will it boot old copy as is or do I have to convert that in to full UEFI meaning change grub_pc to grub_efi in the old install? I could start with copy of old system with new/fresh UEFI install as that will pick up the old system, if such a cross combo will work. Regards Ramesh
Re: Which nvidia driver? xset +dpms issues. Is my video card dead/broken?
Your graphics adapter is modern enough so you should install"nvidia-driver" package.Additional essential packages are: "nvidia-driver-bin","nvidia-driver-libs", "nvidia-kernel-support", "nvidia-kernel-dkms", andothers.If all of them already installed, try to re-install "nvidia-kernel-dkms"package. It will rebuild DKMS module using kernel sources to match kernel in use. It is a good idea to do this, after every update of kernel image, tomake sure a new kernel and DKMS module will be 100% compatible. Thanks for the info. I took the video card out and reinstalled it, jiggling it sufficiently. That seem to have fixed it. So, I am not going to jinx it with changing driver until I am sure the issue is gone. After that I will update the driver with the above one as I am interested in having mainstream driver to minimize any compatibility issues. Regards Ramesh
aptitude safe-upgrade vs apt-get upgrade.
Hi,
I am trying to upgrade the current setup and I am unable to
understand the differences between aptitude vs. apt-get usage.
When I do apt-get -s upgrade, I get
myth2 [rramesh] 100 > sudo apt-get -s upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
gstreamer1.0-gl gstreamer1.0-plugins-bad gstreamer1.0-plugins-base
gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly libasound2-plugins
libavcodec58 libavformat58 libavresample4 libavutil56 libchromaprint1
libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0
libgstreamer-plugins-base1.0-0 libswresample3 libswscale5
linux-image-amd64
mythtv-frontend
0 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
Clearly nothing is going to be done. However aptitude -s safe-upgrade
shows that it will install these.
myth2 [rramesh] 101 > sudo aptitude -s safe-upgrade
Resolving dependencies...
The following NEW packages will be installed:
libcdio19{a} libfaac0{a} libfdk-aac2{a} libilbc2{a} libkvazaar4{a}
liblrdf0{a} libmfx1{a} libopenh264-5{a} libx264-157{a} libx265-176{a}
linux-image-4.19.0-12-amd64{a}
The following packages will be REMOVED:
libcdio18{u} libcrystalhd3{u} libssh-gcrypt-4{u} libvpx5{u}
libx264-155{u} libx265-165{u}
The following packages will be upgraded:
gstreamer1.0-gl gstreamer1.0-plugins-bad gstreamer1.0-plugins-base
gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly libasound2-plugins
libavcodec58 libavformat58 libavresample4 libavutil56 libchromaprint1
libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0
libgstreamer-plugins-base1.0-0 libswresample3 libswscale5
linux-image-amd64
17 packages upgraded, 11 newly installed, 6 to remove and 1 not upgraded.
Need to get 72.9 MB of archives. After unpacking 270 MB will be used.
Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?]
Would download/install/remove packages.
This makes me wonder if it is better to use aptitude over apt-get. Why
these differences? What is the correct way to maintain a working system
and still keep the system up to date.
Regards
Ramesh
kvm win8 guest audio is terrible.
I created a fresh install of debian stretch amd64. In that, I created a qemu/kvm guess install of win8. It only accepted hda as a valid sound card. All others show us without drivers. So, I am limited to only HDA as -soundhw. Further HDA sounds so broken if I try to test with any sound file or youtube video. It is grainy/distorted and outright horrible. Google searches mentions something about MSI and those approaches are simply not accepted by win8. So, I could not use them. I am wondering if there is something fundamentally wrong with windows guests or is there a setting that I am missing? Ramesh
[stretch] unlock with keyfile LVM encrypted rootfs -- hung at boot
Hello everyone!
I'm currently trying to find a method to decrypt my rootfs at boot
time with a keyfile on debian stretch.
I've successfully implemented a method ([1] and [2]) which uses a
custom script to read the first 2048bit
from the usbkey memory to decrypt the disk, but I actually need to
store the keyfile on a filesystem.
Someone [3] told me about an old post on debian-user mailing list:
https://lists.debian.org/debian-user/2017/12/msg00523.html
That's exactly what I need. I don't mind patching cryptroot script
(appended [4]) to do it, so I decided to test it.
I've create a VM (kvm/qemu), partitioned the disks this way (a classic
crypted debian LVM partitioning):
root@debian:~ $ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 1.2G 0 disk
vdb 8:16 0 20.8G 0 disk
├─vdb18:17 0 243M 0 part /boot
├─vdb28:18 0 1K 0 part
└─vdb58:21 0 20.5G 0 part
└─vdb5_crypt 254:00 20.5G 0 crypt
├─debian--vg-root 254:10 18G 0 lvm /
└─debian--vg-swap_1 254:20 2.3G 0 lvm [SWAP]
Configured as in the mailing list tutorial, updated initramfs, updated
grub, rebooted.
I've followed the tutorial step by step, but still at boot time the system hung:
Reading all physical volumes. This may take a while...
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Reading all physical volumes. This may take a while...
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
...
ALERT! /dev/vdb5 does not exist.
Check cryptopts=source bootarg: cat /proc/cmdline
or missing modules. devices: cat /proc/modules: ls /dev
-r Dropping to a shell. Will skip /dev/vdb5 if you can't fix.
Busybox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' fro a list of built-int commands.
(initramfs)
(initramfs) _
It seems unable to find the disk to decrypt (/dev/vdb5).
I was so sad, I've thought I've found the right way...
So I digged more and suddenly I've thought maybe it could be my LVM
partition scheme.
With no real expectations I've created another VM, with the following
partition scheme:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 11024M 0rom
vda 254:0 0 20G 0 disk
|_vda1 254:0 0 953M 0part /boot
|_vda2 254:0 0 1K 0part
|_vda5 254:0 0 17G 0 part
|_vda5_crypt 254:0 0 17G 0 crypt /
|_vda6 254:0 0 2G0 part
|_vda6_crypt 254:0 0 2G0 crypt[SWAP]
Configured, updated, rebooted.
And it works!
So I'm a bit stuck here and I've decided to write to this mailing list
hoping someone may illuminate me,
why does it hung with LVM partitioning?
Could there it be some tricks to make it work?
Now to my point of view I think it could be a missing or erroneous
cmdline parameter, or/and the cryptroot script in the tutorial
(appended [4]) maybe is causing this. But I don't know yet how to fix
this.
The cmdline I used with LVM partitioning is:
BOOT_IMAGE=/vmlinuz-4.9.0-7-amd64
root=/dev/mapper/debian--vg-root ro
cryptopts=target=vda5_crypt,source=/dev/disk/by-uuid/b59bb85d-abec-4562-90c3-1f3d0ab34036
The cmdline used without LVM:
BOOT_IMAGE=/vmlinuz-4.9.0-7-amd64
root=UUID=b59bb85d-abec-4562-90c3-1f3d0ab34036 ro quiet
I also tried to decrypt LVM partitioned device from initramfs panic
shell, but I succeeded only on an actual machine, on a virtual machine
the devices didn't appear (no /dev/vda).
A partitioning scheme without LVM may be ok to my usecase, but I would
like to understand why it does not work and if it can be fixed.
Thank you for your time,
Lorenzo
REF:
[1]
https://www.oxygenimpaired.com/debian-lenny-luks-encrypted-root-hidden-usb-keyfile
[2]
https://www.oxygenimpaired.com/ubuntu-with-grub2-luks-encrypted-lvm-root-hidden-usb-keyfile
[3]
https://unix.stackexchange.com/questions/471854/decrypt-root-device-at-boot-with-keyfile-on-usb-debian-stretch
[4] cryptroot script:
#!/bin/sh
PREREQ="cryptroot-prepare"
#
# Standard initramfs preamble
#
prereqs()
{
# Make sure that cryptroot is run last in local-top
for req in $(dirname $0)/*; do
script=${req##*/}
if [ $script != cryptroot ]; then
echo $script
fi
done
}
case $1 in
prereqs)
prereqs
exit 0
;;
esac
# source for log_*_msg() functions, see LP: #272301
. /scripts/functions
# define $askpass
askpass="/lib/cryptsetup/askpass"
#
#
Please help me resize my ext4 file system to size > 16TB
Hi, I have kernel 3.13 and e2fsprog 1.42.9 (as part of mybuntu 14.04.5 LTS). With this, is it possible to resize2fs my ext4 RAID6 /dev/md0 to 24TB (ie >16TB)? If so, please help me get there. If not, please recommend the upgrades needed to the setup before this can be done. So, far, my google says I need to do "tune2fs -O extents,uninit_bg,dir_index /dev/md0" which I already did and I still get the dreaded message "resize2fs: New size too large to be expressed in 32 bits." There are mentions of a 64bit option for the ext4 file system. I can see how this relates to the error message from resize2fs, but I do not know what I should do to get that update done for my /dev/md0. Also all of the message that I come across relating to 64bit option, only talk about how to *create* a brand new file system with 64bit. None of them tell me how to convert existing one. In fact, many of them scare me saying that it will be unsupported in older kernels. I am not really sure if my kernel is too old or not. Also, they talk about a switch -b for resize2fs that is not supported in the version installed currently on my system/release. Pleas help me figure out the correct sequence of steps. What packages need update, if current kernel/release is ok? Or, do I need to upgrade to a newer release before this is possible? Thanks Ramesh
How to delay resume after suspend to get disks ready, using kernel command line switch?
Problem: I am having a problem with ubuntu 14.04 resume from suspend. I suspect a race condition in boot process. I have a mpt2sas (LSISAS2008: FWVersion(20.00.07.00)) host adapter to which several of my disks are attached. On occasions, there is a delay before these devices become available. However, kernel tries to assemble RAID6 that includes these disks before they become available. As a result the array gets assembled in a degraded mode. My question: I like to tell kernel to delay resume until LSI card finishes its card identifying devices. Can I use resumedelay/rootdelay switches in grub.cfg to accomplish this? If so, which one I should use? Ramesh
DEBIAN REPOSITORIES FOR UBUNTU DAPPER ?
Dear Friends! I use Ubuntu Dapper Drake (on x86 pc) and wanted to install "isomaster" software package about which I read in a linux magazine. As this package was unavailable in my synaptic package manager with Ubuntu repositories, I downloaded the package from Debian website. While attempting the installation, I encountered dependency errors. I believe these errors can be overcome by adding appropriate Debian repositories to the etc/apt/sources.list file of my Ubuntu OS. Please (1) clarify if I can have both Ubuntu repositories and debian repositories enabled at the same time ? (2) Do I need any key to access the Debian repositories ? (3) give me the exact debian package source location lines, that I need to add to my etc/sources.list file, so I can henceforth install packages from Debian repositories without any dependency errors. Following are the contents of my present /etc/apt/sources.list file (if it may be of any use in suggesting a solution to my problem): - deb cdrom:[Ubuntu 6.06 _Dapper Drake_ - Release i386 (20060531.2)]/ dapper main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper main restricted # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper-updates main restricted # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper-updates main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper universe # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper universe deb http://in.archive.ubuntu.com/ubuntu/ dapper-backports main restricted universe multiverse # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu dapper-security main restricted # deb-src http://security.ubuntu.com/ubuntu dapper-security main restricted deb http://security.ubuntu.com/ubuntu dapper-security universe # deb-src http://security.ubuntu.com/ubuntu dapper-security universe ## ## ## How to install Automatix on Ubuntu, Kubuntu, and Xubuntu ## gksudo kwrite /etc/apt/sources.list ## Uncomment the following lines deb http://in.archive.ubuntu.com/ubuntu dapper main # deb-src http://in.archive.ubuntu.com/ubuntu dapper main ## If you use Ubuntu or Xubuntu Dapper, add the following line to the end of the file. # deb http://www.getautomatix.com/apt dapper main ## If you use Kubuntu, add the following line to the end of the file. # deb http://www.getautomatix.com/apt kubuntu main #AUTOMATIX REPOS START deb http://archive.canonical.com/ubuntu dapper-commercial main deb http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu dapper-updates universe multiverse deb http://archive.ubuntu.com/ubuntu dapper-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu dapper universe multiverse #AUTOMATIX REPOS END --- thanks, sairam
[no subject]
Dear Friends! I use Ubuntu Dapper Drake (on x86 pc) and wanted to install "isomaster" software package about which I read in a linux magazine. As this package was unavailable in my synaptic package manager with Ubuntu repositories, I downloaded the package from Debian website. While attempting the installation, I encountered dependency errors. I believe these errors can be overcome by adding appropriate Debian repositories to the etc/apt/sources.list file of my Ubuntu OS. Please (1) clarify if I can have both Ubuntu repositories and debian repositories enabled at the same time ? (2) Do I need any key to access the Debian repositories ? (3) give me the exact debian package source location lines, that I need to add to my etc/sources.list file, so I can henceforth install packages from Debian repositories without any dependency errors. Following are the contents of my present /etc/apt/sources.list file (if it may be of any use in suggesting a solution to my problem): - deb cdrom:[Ubuntu 6.06 _Dapper Drake_ - Release i386 (20060531.2)]/ dapper main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper main restricted # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper-updates main restricted # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper-updates main restricted deb http://in.archive.ubuntu.com/ubuntu/ dapper universe # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper universe deb http://in.archive.ubuntu.com/ubuntu/ dapper-backports main restricted universe multiverse # deb-src http://in.archive.ubuntu.com/ubuntu/ dapper-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu dapper-security main restricted # deb-src http://security.ubuntu.com/ubuntu dapper-security main restricted deb http://security.ubuntu.com/ubuntu dapper-security universe # deb-src http://security.ubuntu.com/ubuntu dapper-security universe ## ## ## How to install Automatix on Ubuntu, Kubuntu, and Xubuntu ## gksudo kwrite /etc/apt/sources.list ## Uncomment the following lines deb http://in.archive.ubuntu.com/ubuntu dapper main # deb-src http://in.archive.ubuntu.com/ubuntu dapper main ## If you use Ubuntu or Xubuntu Dapper, add the following line to the end of the file. # deb http://www.getautomatix.com/apt dapper main ## If you use Kubuntu, add the following line to the end of the file. # deb http://www.getautomatix.com/apt kubuntu main #AUTOMATIX REPOS START deb http://archive.canonical.com/ubuntu dapper-commercial main deb http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu dapper-updates universe multiverse deb http://archive.ubuntu.com/ubuntu dapper-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu dapper universe multiverse #AUTOMATIX REPOS END --- thanks, sairam
Re: http://picasaweb.google.com/talk2ram/HpProblems
Hi any update on this problem any one can guide me how can restore this problem and make use of my HP servers. thanks ram
Re: http://picasaweb.google.com/talk2ram/HpProblems
No. This looks like the right image AFAICT. You may want to check out: http://tldp.org/HOWTO/html_single/PA-RISC-Linux-Boot-HOWTO/#hardware this is my compatable server R class is basically the same as D class. In there it mentions this list if you encounter problems: [EMAIL PROTECTED] let me subscriber for that group to solve this problem thanks ram
Re: http://picasaweb.google.com/talk2ram/HpProblems
On 2/26/07, Clive Menzies <[EMAIL PROTECTED]> wrote: On (26/02/07 18:30), ram wrote: > iam trying to install Debian on HP R class 9000 > but i dont see iam able to make success > can some one help me ot resolve this problem > > > http://picasaweb.google.com/talk2ram/HpProblems > > any solution for this problem > any help will be great I know you posted this before and got no response. It looks as though bootable media is not recognised. What are you trying to install? If sarge try the daily etch builds: http://www.debian.org/devel/debian-installer/ http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/hppa/iso-cd/debian-testing-hppa-netinst.iso Just want to ask you is, i have downloaded from daily snapshot is this different what you have mentioned URL ? what is the suggestions ram
http://picasaweb.google.com/talk2ram/HpProblems
hi iam trying to install Debian on HP R class 9000 but i dont see iam able to make success can some one help me ot resolve this problem http://picasaweb.google.com/talk2ram/HpProblems any solution for this problem any help will be great ram
Re: problem installing Debian on HP R class 9000
Hi all iam using web console to configure HP R Class 9000 Server iam attaching the gif files taken screen shot when its booting here are the Files any suggestion and help will be appriciated http://picasaweb.google.com/talk2ram/HpProblems ram
eth0: Too much work at interrupt, IntrStatus=0x0001.
Hi all I have just installed Debian sarge using bussiness CD, and running firewall between my web server and internet its working fine, but i have problem when i dmesg, iam getting the eth0: Too much work at interrupt, IntrStatus=0x0001. i googled but i did not get proper solution, is there any solution for this eth0 :01:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) eth1 :01:05.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 6c) more /etc/debian_version 3.1 and also eating RAM free total used free sharedbuffers cached Mem: 93736 79444 14292 0 14408 45816 -/+ buffers/cache: 19220 74516 Swap: 281096 0 281096 any suggestions ram
problem installing Debian on HP R class 9000
Hi all I have HP R Class 900 Server I have downloaded debian hppa and reading the document of PA-RISK How to boot and when boot started i select boot from boot p1( is the CDROM connected) I got the menu, and select English, and Country, after that, its reading CD after a 15min i get a error on console Kernel Panic- not syncing:drivers/parisc/ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping resources any help and suggestions Ram
how can use Debian as a network tap
Hi all how can i make debian as a network tap with 3 ethernet cards on for network in and one for network out third one is connected to another debian with ntop to hear the traffic is this possible solution. if yes.. any resources for the same or any suggestion will be welcome ram
Re: does debian can install on HP R Class 9000 Servers
On 1/25/07, Clive Menzies <[EMAIL PROTECTED]> wrote: On (25/01/07 19:08), ram wrote: > I have old Servers, which i can not sell, not some one intrested to Buy > > so i want to use for linux testing, can some one tell me > > is debian can install on HPR class 9000 Servers > > if yes, where can i get the CD and install proceedure Googling on HP R class 9000 debian install produced this: http://tldp.org/HOWTO/html_single/PA-RISC-Linux-Boot-HOWTO/ ya thanks iam following the same just posted message to the group people experiences ram
does debian can install on HP R Class 9000 Servers
Hi I have old Servers, which i can not sell, not some one intrested to Buy so i want to use for linux testing, can some one tell me is debian can install on HPR class 9000 Servers if yes, where can i get the CD and install proceedure ram
Re: Package installation errors
Thanks for the response Pete. I did notice some errors during the upgrade and dist upgrade options. But most unfortunately, there was a power outage before I could capture the errors. So, if I have to revert everything back to the stable version - Sarge, what are steps that I need to follow ? Few things that I can think of from my limited knowledge : 1) My /etc/apt/sources.list has the following : deb http://http.us.debian.org/debian unstable main I assume, I need to change this to : deb http://http.us.debian.org/debian stable main contrib non-free ? That should start updating the packages from the stable versions ? 2) After this, is it as simple as : apt-get -u dist-upgrade ? Also, is there a way to find out what version of stable debian is installed on my system ? I am guessing it is woody but how can I confirm ? Thanks Ram On 12/17/05, Peter Nuttall <[EMAIL PROTECTED]> wrote: On Sat, Dec 17, 2005 at 06:05:00PM -0700, Ram wrote:> Hi all,> i am a new user of linux in general and debian in specific. I recently> updated my system with the following commands :> #apt-get update > #apt-get upgrade> #apt-get dist upgrade>I'm guessing that you upgraded to unstable, which lives up to its name.> kotapc:~# apt-get -f install> Reading package lists... Done > Building dependency tree... Done> Correcting dependencies... Done> The following extra packages will be installed:> udev> The following packages will be upgraded:> udev> 1 upgraded, 0 newly installed, 0 to remove and 50 not upgraded. > 559 not fully installed or removed.this 50 not upgraded, 559 not fully installed business is worrying me.Are you sure your upgrade and dist-upgrade worked?> Need to get 0B/278kB of archives. > After unpacking 307kB of additional disk space will be used.> Do you want to continue [Y/n]? y> (Reading database ... 101947 files and directories currently installed.)> Preparing to replace udev 0.056-2 (using .../archives/udev_0.076-6_i386.deb)> ...> udev requires a kernel >= 2.6.12, upgrade aborted.> dpkg: error processing /var/cache/apt/archives/udev_0.076-6_i386.deb> (--unpack): > subprocess pre-installation script returned error exit status 1> Errors were encountered while processing:> /var/cache/apt/archives/udev_0.076-6_i386.deb> E: Sub-process /usr/bin/dpkg returned an error code (1) > #>iRight now, the sid kernel images are broken. seehttp://wiki.debian.org/TopicDebianDevel for more infomation. Thatsmessing up udev, which as you see wants a recent kernel image. >>> So what am I doing wrong ?I feel I should warn you off running unstable. Its going though a lot ofwork right now, which means massive breakages. Also, before sarge wasreleased, everyone ran unstable or testing becuase woody was too old. I feel that sarge is still reasonably current.>> Thanks for the help in advance> RamSorry I couldn't be more helpPete
Package installation errors
Hi all, i am a new user of linux in general and debian in specific. I recently updated my system with the following commands : #apt-get update #apt-get upgrade #apt-get dist upgrade I now notice that somehow, I can't run my 'vi' or 'vim' commands anymore. So I tried to track the vi command first but wasn't successful as seen below : # which vi # whereis vi vi: /usr/bin/vi /usr/share/vi /usr/share/man/man1/vi.1.gz # ls -l /usr/bin/vi lrwxrwxrwx 1 root root 20 2005-01-22 09:55 /usr/bin/vi -> /etc/alternatives/vi # vi -su: vi: command not found # /usr/bin/vi -su: /usr/bin/vi: No such file or directory # cd /usr/bin/ /usr/bin# ls -l vi lrwxrwxrwx 1 root root 20 2005-01-22 09:55 vi -> /etc/alternatives/vi /usr/bin# ./vi -su: ./vi: No such file or directory /usr/bin# cd /etc/alternatives/ /etc/alternatives# ls -l vi lrwxrwxrwx 1 root root 12 2005-03-09 18:36 vi -> /usr/bin/vim /etc/alternatives# /usr/bin/vim -su: /usr/bin/vim: No such file or directory /etc/alternatives# cd /usr/bin/ /usr/bin# ls -l vim ls: vim: No such file or directory /usr/bin# ls -l vim ls: vim: No such file or directory At this time, I tried to re-install vi/vim as follows, but again got errors : # apt-get install vim-full Reading package lists... Done Building dependency tree... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: udev: Depends: hotplug (>= 0.0.20040329-17) vim-full: Depends: libruby1.8 (>= 1.8.3-3) but it is not going to be installed Depends: tcl8.4 (>= 8.4.5) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). # apt-get -f install Reading package lists... Done Building dependency tree... Done Correcting dependencies... Done The following extra packages will be installed: udev The following packages will be upgraded: udev 1 upgraded, 0 newly installed, 0 to remove and 50 not upgraded. 559 not fully installed or removed. Need to get 0B/278kB of archives. After unpacking 307kB of additional disk space will be used. Do you want to continue [Y/n]? y (Reading database ... 101947 files and directories currently installed.) Preparing to replace udev 0.056-2 (using .../archives/udev_0.076-6_i386.deb) ... udev requires a kernel >= 2.6.12, upgrade aborted. dpkg: error processing /var/cache/apt/archives/udev_0.076-6_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/udev_0.076-6_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) OK. So at this stage, I tried installing the new kernel image as one of the error messages above suggested : # apt-get install linux-image-2.6.14-2-386 Reading package lists... Done Building dependency tree... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: linux-image-2.6.14-2-386: Depends: yaird but it is not going to be installed or initramfs-tools but it is not going to be installed or linux-initramfs-tool udev: Depends: hotplug (>= 0.0.20040329-17) E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). kotapc:~# apt-get -f install Reading package lists... Done Building dependency tree... Done Correcting dependencies... Done The following extra packages will be installed: udev The following packages will be upgraded: udev 1 upgraded, 0 newly installed, 0 to remove and 50 not upgraded. 559 not fully installed or removed. Need to get 0B/278kB of archives. After unpacking 307kB of additional disk space will be used. Do you want to continue [Y/n]? y (Reading database ... 101947 files and directories currently installed.) Preparing to replace udev 0.056-2 (using .../archives/udev_0.076-6_i386.deb) ... udev requires a kernel >= 2.6.12, upgrade aborted. dpkg: error processing /var/cache/apt/archives/udev_0.076-6_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/udev_0.076-6_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) # So what am I doing wrong ? Thanks for the help in advance Ram
