Live usb version of testing
Hi, My machine keeps crashing on Bookworm, and most of the drivers aren't working. I wanted to try a live usb to see if it's just my system's rather crufty history rather than bookworm. How would I get one of these? Thanks James
Problems with the nouveau driver
Hi, I've just had to replace the motherboard, cpu and ram in my PC, and after a few hoops got to the point where I can boot Debian Testing in kde. However I keep getting screen windowing problems before eventually X shuts down. Mouse still works for a while, the graphics card is an nvidia GT 730, How do I go about trying to sort this out. Here's some errors from dmesg [ 188.614806] nouveau :2d:00.0: firmware: failed to load nouveau/nv106_fuc084 (-2) [ 188.614812] nouveau :2d:00.0: Direct firmware load for nouveau/nv106_fuc084 failed with error -2 [ 188.614819] nouveau :2d:00.0: firmware: failed to load nouveau/nv106_fuc084d (-2) [ 188.614820] nouveau :2d:00.0: Direct firmware load for nouveau/nv106_fuc084d failed with error -2 [ 188.614821] nouveau :2d:00.0: msvld: unable to load firmware data [ 188.614823] nouveau :2d:00.0: msvld: init failed, -19 Thanks James
Start ZFS partition on boot.
Hi, I'm having lots of trouble starting my zfs /var partition as part of boot, after an upgrade to Bullseye. I can manually import the partition with zpool import -a and the status of the pool says "no known data errors". journalctl | grep zfs gives the following error; udevadm => systemd-udev-settle.service is deprecated, Please fix zfs-import-cache.service, zfs-load-module.service not to pull it in. systemd-modules-load[466]: Inserted module 'zfs' systemd[1]: zfs-import-cache.service: Job zfs-import-cache.service/start failed with result 'dependency' systemd[1]: zfs-load-module.service: Job zfs-load-module.service/start failed with result 'dependency' I thought maybe /etc/zfs/zpool_tank.cache had got corrupted, so I set it to none,moved the file, rebooted, reset it to /etc/zfs/zpool_tabk.cache and reboot but no joy. I've tried adding "ExecPreStart=/bin/sleep 5" to the service section of /lib/systemd/systemzfs-import-cache Did a systemctl daemon-reload rebooted I've checked that zfs is listed in /etc/modules-load.d/modules.conf and the fact that you don't have to modprobe once started,suggests that it's working. Unfortunately no change. Now I'm wondering did the system try to load the pool after the kernel module, but I don't want to hack around any more and break things. Note that this used to work under Debian 10 and I've not changed the partition. It seems to be related to this; but I don't want to change the system any more, without solid advice. If anyone can offer any help, I'd be very grateful, James
Re: Errors scrolling on boot
Hi, I found dmesg -D which stopped the errors scrolling but I can't find the problem in the logs, or why it's not booting further. Would not having these firmwares installed prevent the boot continuing? I'd understand that I wouldn't have any wireless, but I've a very old usb dongle that will work. The problem I have is that I also have var mounted as zfs, but that's not mounting properly and I can't tell whether it's the upgrade stopping zfs working or the firmwares stopping the boot before then. dmesg isn't that informative and neither is journalctl -xe, unfortunately I can't copy either. Thanks James Would On Sun, 13 Mar 2022 at 22:44, Charles Curley < charlescur...@charlescurley.com> wrote: > On Sun, 13 Mar 2022 22:16:46 + > "Andrew M.A. Cater" wrote: > > > If you used the official media without firmware: add contrib and > > non-free to your /etc/apt/sources.list and try and install the > > firmware / boot with the unofficial non-free .iso, use this as rescue > > medium and install the appropriate non-free firmware you may need. > > That sounds like an Intel wifi adapter. You may want the firmware > package firmware-iwlwifi. > > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > >
Errors scrolling on boot
Hi, I've just upgraded my system to Bullseye and run into a problem on reboot. I'm just getting an error, endlessly: [timestamp] Bluetooth: hci0: Reading Intel version information failed (-22) [timestamp] Bluetooth: hci0: There's an iwlwifi*.ucode error near the start but everything gets overwhelmed with the Bluetooth errors. I can't make these messages stop, and the system won't boot to a gui, although I can log in as root. It's very hard to use. I really need an "OK, I get it!" option so I can work on the machine. I've managed to stop Bluetooth as a service, but still get these errors on reboot. The cards are part of the MSI x570S motherboard, so I can't disconnect them to get a working system. Any ideas? I'm thinking I might have to chroot and use isenkram? Thanks James
Trying to work out what non-Debian or non-Buster packages I need to remove
Hi, I'm trying to upgrade to Bullseye at the moment, but a bit stuck on which non-Debian packages I need to remove; root@hawaiian:~# apt-forktracer | sort | awk -F ' ' '{print $1}' containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras docker-scan-plugin elasticsearch google-chrome-stable kibana libnvpair3linux libuutil3linux libzfs4linux libzpool4linux logstash spl-dkms zfs-dkms zfsutils-linux zfs-zed root@hawaiian:~# aptitude search '?narrow(?installed, ?not(?origin(Debian)))' i A containerd.io - An open and reliable container runtime i docker-ce - Docker: the open-source application container engine i A docker-ce-cli - Docker CLI: the open-source application container engine i A docker-ce-rootless-extras - Rootless support for Docker. i A docker-scan-plugin - Docker scan cli plugin. i elasticsearch - Distributed RESTful search engine built for the cloud i google-chrome-stable - The web browser from Google i kibana - Explore and visualize your Elasticsearch data i logstash - An extensible logging pipeline spl-dkms These (libnvpair3linux, libuutil3linux, libzfs4linux, libzpool4linux, spl-dkms, zfs-dkms, zfsutils-linux, zfs-zed) are from Backports, so do they need to be removed? I ask as my /var is mounted as ZFS and that might get tricky! I can handle removing the docker ones as I'd like to install Podman anyway. Is there a proper way I should do this? Would I be taking a risk keeping elasticsearch, kibana, logstash and chrome or should I just remove those too? Should I comment out the entries in apt/sources.list.d? Thanks James
Re: Changing hardware
Hi, Thanks for all your help, just starting upgrading to Debian 11. Reasons for going with nvidia was it was the cheapest thing I could find, passively cooled, and I do a bit of stuff with Cuda so nvidia is the only game in town. I am using nouveau at the moment, thank god, I'd hate to do this with nvidia kernel drivers! Thanks James On Wed, 9 Mar 2022 at 09:27, Anssi Saari wrote: > piorunz writes: > > > Free drivers are terrible to use if user wants hardware acceleration. > > Clocks are not ramped up, because nouveau does not support re-clocking. > > That means horrible performance, or crashes. I don't ever recommend, or > > sometimes even mention, nouveau. > > Hear, hear. I was actually surprised recently when my "new" laptop > actually produced video with nouveau but after some glitches I just > installed the proprietary nvidia-driver. This "new" laptop is 2016 > vintage with Quadro M2000 video, roughly equivalent to a GTX950 and > hence Maxwell-based. Even for it especially the power management and > video decode/encode acceleration support look pretty sad on the Nouveau > feature matrix (https://nouveau.freedesktop.org/FeatureMatrix.html). > > Not to mention the RTX3070Ti in my desktop. > > Still, impressive effort from the Nouveau project considering how many > chips Nvidia has pushed out over the years. > >
Changing hardware
Hi, My old core2 (8gb ram) died after a power cycle,so I bought an AMD Ryzen 5800 with 32Gb Ram and a new motherboard and a new nvidia graphics card.I converted the boot system over to EFI ( https://blog.getreu.net/projects/legacy-to-uefi-boot/). I was going to upgrade to Debian 11 anyway, but is there a way to update all the drivers and kernel to reflect the new hardware? Thanks James
KDE and Pulseaudio; swapping users
Hi, Does anyone have a solution for the problem that when I switch users, to have any sound as the new user, I have to su to root to kill the other users Pulseaudio. If I don't do this I'm left with a dummy sound card. Thanks James
Re: Could KDE work adequately on a PC with 4 GB of RAM and an Intel Core 2 Duo processor @ 2.33 GHz?
Also, you could spend a bit on money on an SSD, I did. On Wed, 10 Mar 2021 at 11:31, James Allsopp wrote: > Yeah it will work, although it'll work a lot better if you can get an > extra 4Gb off Ebay, I paid about £25. > > For reference I was running it on a 3Ghz 4GbRam Core2Duo. > > On Wed, 10 Mar 2021 at 11:23, Cmdte Alpha Tigre Z > wrote: > >> > I would not do that. I run xfce under Debian 10.4 in 8GB, it's very >> light weight for a window manager. MUCH lighter than KDE. But still a >> little slow sometimes, with more than a few apps open SubCommandante >> Geovanis >> > >> >> Oh, it looks it would be very slowly then. >> It is weird is doesn't looks like I have been reading: >> >> https://www.forbes.com/sites/jasonevangelho/2019/10/23/bold-prediction-kde-will-steal-the-lightweight-linux-desktop-crown-in-2020/?sh=763cb23826d2 >> >> I can't say anything about, because I never used any of them. >> >
Re: Could KDE work adequately on a PC with 4 GB of RAM and an Intel Core 2 Duo processor @ 2.33 GHz?
Yeah it will work, although it'll work a lot better if you can get an extra 4Gb off Ebay, I paid about £25. For reference I was running it on a 3Ghz 4GbRam Core2Duo. On Wed, 10 Mar 2021 at 11:23, Cmdte Alpha Tigre Z wrote: > > I would not do that. I run xfce under Debian 10.4 in 8GB, it's very > light weight for a window manager. MUCH lighter than KDE. But still a > little slow sometimes, with more than a few apps open SubCommandante > Geovanis > > > > Oh, it looks it would be very slowly then. > It is weird is doesn't looks like I have been reading: > > https://www.forbes.com/sites/jasonevangelho/2019/10/23/bold-prediction-kde-will-steal-the-lightweight-linux-desktop-crown-in-2020/?sh=763cb23826d2 > > I can't say anything about, because I never used any of them. >
Install Xrdp on debian 10
Hi, I'm having trouble getting this to work as I'd like, which is pretty much like it works in windows. I want to login through windows and not have to log in using the horrible X11 dialog, which means I can't use a password manager because I can't cut and paste into that window. I only ever want to use one session, if I log out of RDP and come back to it, I'd like all my windows to be exactly as it was. Currently, it's not working at all, it just bounces me out after logging in via the X11 xrdp screen. I've tried with the xorg and x11 options. I've just installed in using apt-get xrdp, and left the /etc/xrdp/xrdp.ini file as is. Thanks for your help
Photos on corrupted SD card
Hi, Does anyone know if there are any good tools in Linux for fixing corruption on FAT32 SD cards. It was in my phone, but I dropped it and broke the phone. Couldn't turn it off as the screen was broken and thoughtlessly removed it whilst on. The files are there, I can see it in Linux, it's just some of the files are broken, i.e. images with odd colours, video files that don't play. I was thinking of just dd'ing the whole card to my pc. Thanks James
Cloud-init in Debian
Hi, Does anyone have an example or tutorial for using cloud-init with debian images. I'm currently trying to do terraform with kvm, but struggling as although terraform picks up the cloud-init, the fqdn and the ssh key isn't working. I'm trying to use this image https://cdimage.debian.org/cdimage/cloud/buster/20201214-484/debian-10-genericcloud-amd64-20201214-484.qcow2 I'm not entirely sure if this is the correct image or not? A lot of the instructions online are for ubuntu or red hat. Thanks James
Re: Import and Export of Zfs pools
On Thu, 26 Nov 2020 at 12:32, Dan Ritter wrote: > James Allsopp wrote: > > Hi, > > I've got a zfs pool that works fine in normal use on my debian system and > > remains after a reboot. > > When I reboot into recovery mode, I have to reimport the pool manually > > using > > zpool import -d /dev/disk/by-id > > > > I export before I reboot, but when I reboot into the full version of > Debian > > 10, the pool isn't there. I can reimport it using the zpool import > command, > > That's expected. > > zpool export prepares the zpool for use on a different system. > It is not part of the usual shutdown procedure. > > > > What I want to do is this; > > > >- Reboot in single user mode > >- import pool. > >- cp -a /var to /tank/var > >- Set the mount point on /tank/var to /var > >- Remove /var entry from /etc/fstab > >- Export the pool > >- Reboot > > > > > > And then I should have a ZFS var for VMs and Docker containers when the > > main OS imports ZFS for /var. > > Don't export the pool. Unmount all ZFS mounts before or as part > of shutdown.. > > -dsr- > > > > > > I tried this with a VM and it worked. > > Thanks > > James > > -- > https://randomstring.org/~dsr/eula.html is hereby incorporated by > reference. > there is no justice, there is just us. > Ok, got all this to work almost; When the system comes back up, it sees no /var directory and tries to fill it. Then the zfs-mount service starts later and can't mount over a non-empty directory. I'm out of ideas now. James
Import and Export of Zfs pools
Hi, I've got a zfs pool that works fine in normal use on my debian system and remains after a reboot. When I reboot into recovery mode, I have to reimport the pool manually using zpool import -d /dev/disk/by-id I export before I reboot, but when I reboot into the full version of Debian 10, the pool isn't there. I can reimport it using the zpool import command, but I have to do that every time unless I reset the cache using; zpool set cachefile=none tank zpool set cachefile=/etc/zfs/zpool.cache tank which I found as the zfs-import-cache.service had failed. My pool isn't particularly complicated; root@hawaiian:~# zpool status pool: tank state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 mirror-0 ONLINE 0 0 0 wwn-0x5f000b074105 ONLINE 0 0 0 wwn-0x50024e9001a4ea77 ONLINE 0 0 0 errors: No known data errors What I want to do is this; - Reboot in single user mode - import pool. - cp -a /var to /tank/var - Set the mount point on /tank/var to /var - Remove /var entry from /etc/fstab - Export the pool - Reboot And then I should have a ZFS var for VMs and Docker containers when the main OS imports ZFS for /var. I tried this with a VM and it worked. Thanks James
Re: dhcp bridge for virtual machines using KVM
On Tue, 22 Sep 2020 at 22:30, Lucas Castro wrote: > > On 9/22/20 5:54 PM, James Allsopp wrote: > > > > On Tue, 22 Sep 2020 at 19:47, Lucas Castro wrote: > >> >> On 9/22/20 1:26 PM, James Allsopp wrote: >> > Hi, >> > I've got a computer that I'm running debian 10 on with KVM. The >> > machine is connected to a OpenWRT router which provides DHCP and DNS >> > to the network, via a wifi link used for the host and an ethernet >> > connection on eth1 used for a bridge >> >> Is your OpenWRT router running in vm on the same host or somewhere else >> throughout physical network eth1? >> >> > The OpenWRT is a completely separate device running at the end of the > cable connected to eth1. The Wireless is also connected to an AP on that > router. All of this is on the 192.168.1.* network. > > > >> > >> > I've set this file up for the bridge in /etc/network/interfaces.d/br0 >> > auto eth1 >> > auto br0 >> > iface br0 inet dhcp >> > bridge_ports eth1 >> > bridge_fd 0 >> > bridge_stp off >> > >> > ifup br0 brought it up nicely and it got an IP address in the range >> > I'd expect. So far so good. The only problem is now, I can't get any >> > of the VM's I create to use this network. When creating a VM using >> > Virtual Machine Manager, it gives me the option to specify shared >> > device name for the network source. One of these is for a network I >> > already created in virsh; >> > >> > >> > host-bridge >> > >> > >> > >> > Try something like this ti get your vm settings. > > virsh -c qemu:///system dumpxml ${GUEST_NAME} | egrep -A5 -i > "network|bridge" > > > i.e. > > virsh -c qemu:///system dumpxml Buster | egrep -A5 -i "network|bridge" > > > > > > >function='0x0'/> > > > > > > > >function='0x0'/> > > > > >> > However, if I set the network to either 'host-bridge' or br0 directly, >> > the route is never set and I can never get a dhcp setting. I've >> > checked ip_forward is set to 1. >> > >> > I'd just like to set it up this way, as it seems really inefficient to >> > have a dhcp and then use difficult to remember static IP's everywhere. >> > >> > Thanks >> > James >> > >> > >> -- >> Lucas Castro >> >> Here's what I get; virsh -c qemu:///system dumpxml proxy1 | egrep -A5 -i "network|bridge" 12:40:09 pm BST james BigRaid ❱ virsh -c qemu:///system dumpxml debian10 | egrep -A5 -i "network|bridge" Thanks James > -- > Lucas Castro > >
Re: dhcp bridge for virtual machines using KVM
On Tue, 22 Sep 2020 at 17:58, Fabien Roucaute wrote: > Le 22/09/2020 à 18:50, James Allsopp a écrit : > > > > I've tried that but I get the same result. > > Thanks > > James > > > > You need to answer to the mailing-list email address, not mine. > If it still doesn't work, we need more information, like the result of > the following commands (you should modify the public IP that appears in > if it's the case) > 'ip a' > 'iptables-save' > 'brctl show' > > Here's ip a ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:1d:7d:0d:2a:9f brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 00:1d:7d:0d:2a:9d brd ff:ff:ff:ff:ff:ff 4: wlan0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b4:ee:b4:84:37:2a brd ff:ff:ff:ff:ff:ff inet 192.168.1.174/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0 valid_lft 27656sec preferred_lft 27656sec inet6 fde6:4511:f54::a55/128 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fde6:4511:f54:0:f195:8361:215d:5f17/64 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::4bf0:ca57:25f0:ed7f/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:1d:7d:0d:2a:9d brd ff:ff:ff:ff:ff:ff inet 192.168.1.206/24 brd 192.168.1.255 scope global dynamic br0 valid_lft 27655sec preferred_lft 27655sec inet6 fde6:4511:f54:0:21d:7dff:fe0d:2a9d/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 fe80::21d:7dff:fe0d:2a9d/64 scope link valid_lft forever preferred_lft forever 6: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:12:5f:1a:5e brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 8: vnet0: mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:8a:6e:57 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe8a:6e57/64 scope link valid_lft forever preferred_lft forever Here's iptables -L iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy DROP) target prot opt source destination DOCKER-USER all -- anywhere anywhere DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (1 references) target prot opt source destination Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-ISOLATION-STAGE-2 (1 references) target prot opt source destination DROP all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-USER (1 references) target prot opt source destination RETURN all -- anywhere anywhere and brctl show bridge name bridge id STP enabled interfaces br0 8000.001d7d0d2a9d no eth1 vnet0 docker0 8000.0242125f1a5e no Thanks! James
Re: dhcp bridge for virtual machines using KVM
On Tue, 22 Sep 2020 at 19:47, Lucas Castro wrote: > > On 9/22/20 1:26 PM, James Allsopp wrote: > > Hi, > > I've got a computer that I'm running debian 10 on with KVM. The > > machine is connected to a OpenWRT router which provides DHCP and DNS > > to the network, via a wifi link used for the host and an ethernet > > connection on eth1 used for a bridge > > Is your OpenWRT router running in vm on the same host or somewhere else > throughout physical network eth1? > > The OpenWRT is a completely separate device running at the end of the cable connected to eth1. The Wireless is also connected to an AP on that router. All of this is on the 192.168.1.* network. > > > > I've set this file up for the bridge in /etc/network/interfaces.d/br0 > > auto eth1 > > auto br0 > > iface br0 inet dhcp > > bridge_ports eth1 > > bridge_fd 0 > > bridge_stp off > > > > ifup br0 brought it up nicely and it got an IP address in the range > > I'd expect. So far so good. The only problem is now, I can't get any > > of the VM's I create to use this network. When creating a VM using > > Virtual Machine Manager, it gives me the option to specify shared > > device name for the network source. One of these is for a network I > > already created in virsh; > > > > > > host-bridge > > > > > > > > > > However, if I set the network to either 'host-bridge' or br0 directly, > > the route is never set and I can never get a dhcp setting. I've > > checked ip_forward is set to 1. > > > > I'd just like to set it up this way, as it seems really inefficient to > > have a dhcp and then use difficult to remember static IP's everywhere. > > > > Thanks > > James > > > > > -- > Lucas Castro > >
dhcp bridge for virtual machines using KVM
Hi, I've got a computer that I'm running debian 10 on with KVM. The machine is connected to a OpenWRT router which provides DHCP and DNS to the network, via a wifi link used for the host and an ethernet connection on eth1 used for a bridge I've set this file up for the bridge in /etc/network/interfaces.d/br0 auto eth1 auto br0 iface br0 inet dhcp bridge_ports eth1 bridge_fd 0 bridge_stp off ifup br0 brought it up nicely and it got an IP address in the range I'd expect. So far so good. The only problem is now, I can't get any of the VM's I create to use this network. When creating a VM using Virtual Machine Manager, it gives me the option to specify shared device name for the network source. One of these is for a network I already created in virsh; host-bridge However, if I set the network to either 'host-bridge' or br0 directly, the route is never set and I can never get a dhcp setting. I've checked ip_forward is set to 1. I'd just like to set it up this way, as it seems really inefficient to have a dhcp and then use difficult to remember static IP's everywhere. Thanks James
Re: Access ZFS pool in debian 10 single user mode
This is just debian grub recovery mode so on the same machine, so hopefully zfsutil will be there. Looked at this; zfs 4214784 9 zunicode 335872 1 zfs zlua 172032 1 zfs zavl 16384 1 zfs icp 331776 1 zfs zcommon98304 2 zfs,icp znvpair90112 2 zfs,zcommon spl 122880 5 zfs,icp,znvpair,zcommon,zavl So if I just modprobe those from the column on the left, it should work? Thanks, James On Wed, 2 Sep 2020 at 22:06, Dan Ritter wrote: > James Allsopp wrote: > > Hi, > > Just trying to move var to a zfs partition. Rebooted into recovery mode, > > but could access the zfs pool. I tried to modprobe zfs, but still > nothing. > > Is there something else I should be doing? > > > > Does your recovery mode have the zfs kernel modules and zfsutil? > > Without it, you'll never mount things. > > -dsr- >
Access ZFS pool in debian 10 single user mode
Hi, Just trying to move var to a zfs partition. Rebooted into recovery mode, but could access the zfs pool. I tried to modprobe zfs, but still nothing. Is there something else I should be doing? Thanks James
Core Q9650 in a case with 5 hard drives
Hi, I'm using an old Core 2 processor in a case with 5 hard drives, one of which is an SSD. It's a server but doesn't get hit particularly hard, so I'm wondering what the options are to try and conserve power with it as it's generating rather a lot of heat. I've looked at powertop, but there didn't seem to be a huge amount there.The processor only scales between 2 and 3Ghz with an ondemand governor. I upgraded the processor from a E8460 and doubled the ram to 8GB, with the same hard drives and this was when I noticed the temperature increase. Thanks
Re: add 2FA to ssh
Hi, You can do it at the same time with a yubikey and editing your pam file. https://developers.yubico.com/yubico-pam/YubiKey_and_SSH_via_PAM.html#:~:text=The%20Yubico%20PAM%20module%20for,YubiKey%20assigned%20to%20the%20user. Been doing this for years, James On Thu, 13 Aug 2020 at 15:24, Toni Mas Soler wrote: > I think 2FA first is better. Thus you don't have to type your password > if you have a wrong 2FA. > > Toni Mas > > Missatge de Pòl Hallen del dia dj., 13 d’ag. > 2020 a les 13:38: > > > > Hi folks :) > > > > > > what it better with 2FA: at ssh login request first 2FA authentication > > next ssh password or viceversa? > > > > thanks! > > > > Pol > > > >
Re: Any success with /var on ZFS in Debian Buster?
Thanks for that. Is it simply a case of installing the DKMS module, building the pool (two drives in my case), formatting and mounting? James On Thu, 30 Jul 2020 at 13:18, Dan Ritter wrote: > elvis wrote: > > > > On 29/7/20 11:56 pm, Dan Ritter wrote: > > > James Allsopp wrote: > > > > Hi, > > > > I was wondering if anyone had enjoyed any success putting /var on a > ZFS > > > > partition in Debian Buster? > > > Yes, on a largish number of servers plus a few desktops and a > > > laptop. > > > > And a follow up, why do you use it? > > - data integrity > - snapshots and zfs send/receive for backups > - good reporting of disk events > - does not incur an unacceptable speed penalty > - well documented, relatively simple method of disk replacement > - pools can be transferred between machines without specific > controller requirements > - flexibility of filesystems-on-pools > > And because I have that experience at work, I am reasonably > happy to run it at home on the systems where it makes sense. > > -dsr- > >
Any success with /var on ZFS in Debian Buster?
Hi, I was wondering if anyone had enjoyed any success putting /var on a ZFS partition in Debian Buster? Thanks James
Re: Cups no longer accepting remote connections for printing.
Hi, Thanks Brian, this is the server; scheduler is running system default destination: HL-2030-series device for HL-2030-series: usb://Brother/HL-2030%20series?serial=L0J260292 HL-2030-series accepting requests since Sun 23 Jul 2017 21:21:32 BST printer HL-2030-series is idle. enabled since Sun 23 Jul 2017 21:21:32 BST The is the client; scheduler is running no system default destination lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden lpstat: Forbidden Here's an nmap for the port on the server. # nmap -sS -p631 hawaiian Starting Nmap 7.70 ( https://nmap.org ) at 2020-02-09 14:07 GMT Nmap scan report for hawaiian (192.168.1.206) Host is up (0.022s latency). Other addresses for hawaiian (not scanned): fde6:4511:f54::1a3 fde6:4511:f54::a55 rDNS record for 192.168.1.206: hawaiian.frankexchangeofviews.uk PORTSTATE SERVICE 631/tcp open ipp MAC Address: 00:1D:7D:0D:2A:9D (Giga-byte Technology) Nmap done: 1 IP address (1 host up) scanned in 0.53 seconds On Sun, 9 Feb 2020 at 12:13, Brian wrote: > On Sun 09 Feb 2020 at 02:06:22 +0000, James Allsopp wrote: > > > HI, > > My printer on a remote machine works when access from that machine, I've > > checked port 631 isn't blocked using Xnat, but I can't work out why I > can't > > print. > > All the user pages say forbidden, and a test page from my local cups > hangs. > > Please give the printer make and model and the outputs of 'lpstat -t' > on server and client. > > -- > Brian. > >
Cups no longer accepting remote connections for printing.
HI, My printer on a remote machine works when access from that machine, I've checked port 631 isn't blocked using Xnat, but I can't work out why I can't print. All the user pages say forbidden, and a test page from my local cups hangs. I'm using Buster on this machine currently. Here's my cupsd.conf, Thanks James # Configuration file for the CUPS scheduler. See "man cupsd.conf" for a # complete description of this file. # # Log general information in error_log - change "warn" to "debug" # for troubleshooting... LogLevel warn PageLogFormat # Deactivate CUPS' internal logrotating, as we provide a better one, especially # LogLevel debug2 gets usable now MaxLogSize 0 # Only listen for connections from the local machine. Listen *:631 Listen /var/run/cups/cups.sock # Show shared printers on the local network. Browsing On BrowseLocalProtocols dnssd #BrowseAllow all #BrowseAddress 192.168.1.*:631 # Default authentication type, when authentication is required... DefaultAuthType Basic # Web interface setting... WebInterface Yes # Restrict access to the server... Order allow,deny Allow localhost Allow 192.168.1.* ServerAlias * # Restrict access to the admin pages... Order allow,deny Allow localhost Allow 192.168.1.* # Restrict access to configuration files... AuthType Default Require user @SYSTEM Order allow,deny # Restrict access to log files... AuthType Default Require user @SYSTEM Order allow,deny # Set the default printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... Order deny,allow Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # All printer operations require a printer operator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... Require user @OWNER @SYSTEM Order deny,allow Order deny,allow # Set the authenticated printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... AuthType Default Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # All printer operations require a printer operator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... AuthType Default Require user @OWNER @SYSTEM Order deny,allow Order deny,allow
Upgrading from Stretch to Buster with docker 3rd party installed
Hi, I was going to upgrade to Buster, but I've got docker installed and am running a container as an ldap server. Consequently I don't want to get rid of it, but the install guide I read suggested removing all 3rd-party repositories before starting. This is the current situatioin with my sources files ❱ cat /etc/apt/sources.list # # deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST 20170617-13:06]/ stretch main #deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST 20170617-13:06]/ stretch main deb http://ftp.uk.debian.org/debian/ stretch main contrib non-free deb-src http://ftp.uk.debian.org/debian/ stretch main contrib non-free deb http://security.debian.org/debian-security stretch/updates main deb-src http://security.debian.org/debian-security stretch/updates main # stretch-updates, previously known as 'volatile' deb http://ftp.uk.debian.org/debian/ stretch-updates main deb-src http://ftp.uk.debian.org/debian/ stretch-updates main ❱ cat /etc/apt/sources.list.d/docker.list deb https://download.docker.com/linux/debian stretch stable If anyone has any advice, please let me know, Thanks
Realtek RTL8188CUS wireless usb stick on Stretch
Hi, I'm having lots of problems getting this usb wireless dongle (Edimax) to pick up and connect to a wireless network. I'm not sure if there's a config from an older wireless getting in the way. The hardware for that isn't installed anymore. I'm running network manager in KDE It's detected by lsusb Bus 002 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] I installed the realtek firmware; apt-get install firmware-realtek The drivers seem loaded correctly (from lsmod) rtl8192cu 69632 0 pcspkr 16384 0 rtl_usb20480 1 rtl8192cu rtl8192c_common53248 1 rtl8192cu rtlwifi77824 3 rtl_usb,rtl8192c_common,rtl8192cu mac80211 671744 3 rtl_usb,rtlwifi,rtl8192cu snd_usb_audio 180224 2 snd_usbmidi_lib28672 1 snd_usb_audio cfg80211 589824 2 mac80211,rtlwifi The widget can detect different AP's (I used a test one from my phone to confirm this), I see the one I want to connect to, but when I click on it, it just goes to "configuring interface" and then I get a disconnect notice, "wifi network could not be found". I've turned off the security on my phone ap to test and this made no difference. Can you point me in the general direction of how to start sorting this out? Thanks James
SSH root login from one ip via certificate only, all other logins password only.
Hi, I need to have one computer I can ssh to other computers as root for Ansible. To do this I've set up a strong certificate with a password, but what I want is to only be able to log in as root from one IP using that cert. All other users should only log in via a password and can do so from any IP. Currently normal user logins are broken with this sshd_config. Can anyone tell me where I'm going wrong? Sudo is not an option. Thanks James # $OpenBSD: sshd_config,v 1.93 2014/01/10 05:59:19 djm Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/local/bin:/usr/bin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options override the # default value. # If you want to change the port on a SELinux system, you have to tell # SELinux about this change. # semanage port -a -t ssh_port_t -p tcp #PORTNUMBER # #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # The default requires explicit activation of protocol 1 #Protocol 2 # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key HostKey /etc/ssh/ssh_host_ecdsa_key HostKey /etc/ssh/ssh_host_ed25519_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 1024 # Ciphers and keying #RekeyLimit default none # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin no #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 #RSAAuthentication yes #PubkeyAuthentication yes # The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2 # but this is overridden so installations will only check .ssh/authorized_keys AuthorizedKeysFile .ssh/authorized_keys #AuthorizedPrincipalsFile none #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no # similar for protocol version 2 #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! #PermitEmptyPasswords no #PasswordAuthentication yes # Change to no to disable s/key passwords #ChallengeResponseAuthentication yes #ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no #KerberosUseKuserok yes # GSSAPI options GSSAPIAuthentication yes GSSAPICleanupCredentials no #GSSAPIStrictAcceptorCheck yes #GSSAPIKeyExchange no #GSSAPIEnablek5users no # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. # WARNING: 'UsePAM no' is not supported in Red Hat Enterprise Linux and may cause several # problems. #UsePAM yes #AllowAgentForwarding yes #AllowTcpForwarding yes #GatewayPorts no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes #PrintMotd yes #PrintLastLog yes #TCPKeepAlive yes #UseLogin no UsePrivilegeSeparation sandbox # Default for new installations. #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #ShowPatchLevel no #UseDNS yes #PidFile /var/run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none # no default banner path #Banner none # Accept locale-related environment variables AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE AcceptEnv XMODIFIERS # override default of no subsystems Subsystem sftp/usr/libexec/openssh/sftp-server # Example of overriding settings on a per-user basis #Match User anoncvs # X11Forwarding no # AllowTcpForwarding no # PermitTTY no # ForceCommand cvs server Match User root Address x.y.z.w PermitRootLogin yes PermitTunnel no PasswordAuthentication no Match all PermitRootLogin no
Re: As seen above: use of su vs sudo
As far as I can see "su -" saves a lot of grief if you're the only admin on a system. Tried sudo ing to a protected directory? Doesn't work. Tired of entering your password every couple of minutes? sudo does mean that the admin actions of a particular user are logged, but unless you lock down what they can do, they can change/delete the logs easily enough. I think this just degenerates into a religious war. If it works for you, and the people around you, great. If not use the other option. On 7 August 2018 at 12:11, Stephan Seitz wrote: > On Di, Aug 07, 2018 at 11:58:48 +0200, Martin Drescher wrote: > >> And I'm curious why Debian still prefers the use of su over sudo? >> > > I don’t know if Debian does, but the difference between su and sudo seems > quite like to the difference between ssh logins with password and with > keys. Both have advantages and disadvantages. > > Shade and sweet water! > > Stephan > > -- > | Public Keys: http://fsing.rootsland.net/~stse/keys.html | >
Re: A minimal relational database in Debian?
+1 for Sqlite unless you need multiuser access. James On 27 February 2017 at 13:17, Richard Owlettwrote: > The last time I needed a relational database my employer was using dBaseII > on a MS-DOS machine. > What is a functional equivalent in the Debian repository? > > I looked at at LibreOffice Base. It was unusable as its "help" system > provided no intrinsic way to increase fonts to a legible size. > > https://packages.debian.org/stable/database/ was not useful as it doesn't > categorize the list. > > Suggestions? > TIA > >
Redirecing root emails to a gmail account
Hello, I want to have the root e-mails sent to my gmail account if possible. I can send email here via commandline echo "This is a test." | mail -s Test but despite editing /etc/aliases so that root points to the external address I can't get this to work. echo "This is a test.(root)" | mail -sv Testing root adding a verbose to the mail command doesn't give any more details. I tried running newaliases, but that didn't make any difference. Any help would be greatly appreciated. James
Pulse audio always starts in suspended; have to restart before anything
Hi, I'm having a problem with pulseaudio where I have to restart it before I can play any music whatsoever. If I list the sinks, my single sink comes up as suspended. My system is relatively fresh install of Wheezy, with pulseaudio running in as my user. My default.pa is: .nofail ### Load something into the sample cache #load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav #load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav #load-sample-lazy pulse-access /usr/share/sounds/generic.wav .fail ### Automatically restore the volume of streams and devices load-module module-device-restore load-module module-stream-restore load-module module-card-restore ### Automatically augment property information from .desktop files ### stored in /usr/share/application load-module module-augment-properties ### Load audio drivers statically ### (it's probably better to not load these drivers manually, but instead ### use module-udev-detect -- see below -- for doing this automatically) #load-module module-alsa-sink device=hw:0,1 #load-module module-alsa-source device=hw:1,0 #load-module module-oss device=/dev/dsp sink_name=output source_name=input #load-module module-oss-mmap device=/dev/dsp sink_name=output source_name=input #load-module module-null-sink #load-module module-pipe-sink ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect tsched=0 .else ### Use the static hardware detection module (for systems that lack udev/hal support) load-module module-detect .endif ### Automatically connect sink and source if JACK server is present .ifexists module-jackdbus-detect.so .nofail load-module module-jackdbus-detect .fail .endif ### Automatically load driver modules for Bluetooth hardware .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif ### Load several protocols .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix ### Network access (may be configured with paprefs, so leave this commented ### here if you plan to use paprefs) #load-module module-esound-protocol-tcp #load-module module-native-protocol-tcp #load-module module-zeroconf-publish load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 ### Load the RTP receiver module (also configured via paprefs, see above) #load-module module-rtp-recv ### Load the RTP sender module (also configured via paprefs, see above) #load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties=device.description='RTP Multicast Sink' #load-module module-rtp-send source=rtp.monitor ### Load additional modules from GConf settings. This can be configured with the paprefs tool. ### Please keep in mind that the modules configured by paprefs might conflict with manually ### loaded modules. .ifexists module-gconf.so .nofail load-module module-gconf .fail .endif ### Automatically restore the default sink/source when changed by the user ### during runtime ### NOTE: This should be loaded as early as possible so that subsequent modules ### that look up the default sink/source get the right value load-module module-default-device-restore ### Automatically move streams to the default sink if the sink they are ### connected to dies, similar for sources load-module module-rescue-streams ### Make sure we always have a sink around, even if it is a null sink. load-module module-always-sink ### Honour intended role device property load-module module-intended-roles ### Automatically suspend sinks/sources that become idle for too long #load-module module-suspend-on-idle ### If autoexit on idle is enabled we want to make sure we only quit ### when no local session needs us anymore. .ifexists module-console-kit.so load-module module-console-kit .endif .ifexists module-systemd-login.so load-module module-systemd-login .endif ### Enable positioned event sounds load-module module-position-event-sounds ### Cork music/video streams when a phone stream is active load-module module-role-cork ### Modules to allow autoloading of filters (such as echo cancellation) ### on demand. module-filter-heuristics tries to determine what filters ### make sense, and module-filter-apply does the heavy-lifting of ### loading modules and rerouting streams. load-module module-filter-heuristics load-module module-filter-apply ### Load DBus protocol .ifexists module-dbus-protocol.so load-module module-dbus-protocol .endif # X11 modules should not be started from default.pa so that one daemon # can be shared by multiple sessions. ### Load X11 bell module #load-module module-x11-bell sample=bell-windowing-system ### Register ourselves in the X11 session manager #load-module module-x11-xsmp ### Publish connection data in the X11 root window #.ifexists module-x11-publish.so #.nofail #load-module
Re: No sound in Wheezy; Pulse audio through Nvidia graphics card to HDMI
How would I go about checking those? James On 24 March 2015 at 14:51, Eric Sharkey e...@lisaneric.org wrote: On Mon, Mar 23, 2015 at 6:31 PM, James Allsopp jamesaalls...@googlemail.com wrote: Sorry, didn't make myself clear, the sound card is an intel hda onboard and there's a small cable which takes this from the motherboard to the nvidia graphics card, which then connects to the HDMI cable. [] I've installed the nvidia drivers With cards like that, the drivers aren't involved and there is no software configuration required for the graphics card. The hardware takes any signal it receives on the SPDIF input and sends it to the HDMI output. If your hardware is working, whatever problem you're having is getting sound out of your SPDIF output on the Intel sound card and not related to anything nvidia or hdmi. Have you checked your mixer settings? Does it work without pulse audio? Eric
No sound in Wheezy; Pulse audio through Nvidia graphics card to HDMI
Hi, Just reinstalled debian and are having lots of problems getting the sound to work through HDMI. I had it working but now it has just stopped. I'm watching the screen through the same HDMI so I presume hardware is good. Eventually I want to use this system to run MPD. Here's my setup as described by aplay; james@Hawaiian:~$ aplay -L null Discard all samples (playback) or generate zero samples (capture) pulse PulseAudio Sound Server default:CARD=Intel HDA Intel, ALC889A Analog Default Audio Device sysdefault:CARD=Intel HDA Intel, ALC889A Analog Default Audio Device front:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog Front speakers surround40:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, ALC889A Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=Intel,DEV=0 HDA Intel, ALC889A Digital IEC958 (S/PDIF) Digital Audio Output james@Hawaiian:~$ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC889A Analog [ALC889A Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC889A Digital [ALC889A Digital] Subdevices: 0/1 Subdevice #0: subdevice #0 In my pulseaudio setup I added the first line here, and commented out the second. load-module module-alsa-sink device=hw:0,1 #load-module module-alsa-source device=hw:1,0 KDE is now giving me an error about internal devices removed; both output and capture on the pulse sound server. I'm not sure where I'm now going with this, so if anyone could help me debug this, I would greatly appreciate it. Thanks, James
Re: No sound in Wheezy; Pulse audio through Nvidia graphics card to HDMI
Included some more hardware information below, Thanks, James On 23 March 2015 at 21:26, Eric Sharkey e...@lisaneric.org wrote: On Mon, Mar 23, 2015 at 9:41 AM, James Allsopp jamesaalls...@googlemail.com wrote: Hi, Just reinstalled debian and are having lots of problems getting the sound to work through HDMI. I had it working but now it has just stopped. I'm watching the screen through the same HDMI so I presume hardware is good. What kind of hardware is it? You've said nvidia but not which model. Sorry, didn't make myself clear, the sound card is an intel hda onboard and there's a small cable which takes this from the motherboard to the nvidia graphics card, which then connects to the HDMI cable. These are shown in the lspci below. 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) I've installed the nvidia drivers; here's the lsmod Module Size Used by cryptd 14517 0 aes_x86_64 16843 3 aes_generic33026 1 aes_x86_64 ppdev 12763 0 lp 17149 0 nfsd 216181 2 nfs 308353 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67306 2 nfs,nfsd sunrpc173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd loop 22641 0 hid_logitech 17472 0 ff_memless 12708 1 hid_logitech usblp 17343 0 snd_hda_codec_realtek 188851 1 snd_usb_audio 89083 0 joydev 17266 0 snd_usbmidi_lib23369 1 snd_usb_audio snd_hda_intel 26259 3 snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi hid_logitech_dj17313 0 snd_hda_codec 78031 2 snd_hda_intel,snd_hda_codec_realtek usbhid 36418 2 hid_logitech_dj,hid_logitech snd_rawmidi23060 2 snd_seq_midi,snd_usbmidi_lib arc4 12458 2 hid81372 3 usbhid,hid_logitech_dj,hid_logitech gspca_ov53413440 0 gspca_main 22764 1 gspca_ov534 videodev 70889 1 gspca_main v4l2_compat_ioctl3216655 1 videodev media 18148 1 videodev nvidia 10492298 38 ath5k 129406 0 snd_hwdep 13186 2 snd_hda_codec,snd_usb_audio snd_pcm68083 3 snd_hda_codec,snd_hda_intel,snd_usb_audio snd_page_alloc 13003 2 snd_pcm,snd_hda_intel snd_seq45126 2 snd_seq_midi_event,snd_seq_midi ath21370 1 ath5k sg 25874 0 snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi sr_mod 21899 0 snd_timer 22917 2 snd_seq,snd_pcm cdrom 35401 1 sr_mod snd52893 17 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_realtek firewire_ohci 35772 0 mac80211 192806 1 ath5k ata_generic12479 0 cfg80211 137243 3 mac80211,ath,ath5k acpi_cpufreq 12935 0 firewire_core 48449 1 firewire_ohci i2c_i801 16870 0 psmouse69265 0 soundcore 13065 1 snd i2c_core 23876 3 i2c_i801,nvidia,videodev evdev 17562 15 serio_raw 12931 0 pcspkr 12579 0 parport_pc 22364 1 mperf 12453 1 acpi_cpufreq rfkill 19012 2 cfg80211 crc_itu_t 12347 1 firewire_core pata_jmicron 12472 0 uhci_hcd 26865 0 r8169 47008 0 mii
Re: Trying to install nvidia-settings
Ah, yes that's worked perfectly. Thanks James On 27 February 2015 at 16:46, Reco recovery...@gmail.com wrote: Hi. On Fri, 27 Feb 2015 16:34:03 + James Allsopp jamesaalls...@googlemail.com wrote: Hi, I'm trying to install nvidia-settings but I'm not sure which option to use. I don't want to break anything or leave the system in a bit of a mess. Here's what happens, james@Hawaiian:~$ sudo aptitude install nvidia-settings The following NEW packages will be installed: libxnvctrl0{a} nvidia-settings pkg-config{a} 0 packages upgraded, 3 newly installed, 0 to remove and 68 not upgraded. Need to get 907 kB of archives. After unpacking 1,927 kB will be used. The following packages have unmet dependencies: nvidia-alternative : Breaks: nvidia-settings ( 319.49) but 304.88-1 is to be installed. Apparently you have nvidia-glx installed from the backports. So, correct way to install nvidia-settings would be sudo aptitude -t wheezy-backports install nvidia-settings Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150227194604.50793d2fb69f1402f3ae4...@gmail.com
Trying to install nvidia-settings
Hi, I'm trying to install nvidia-settings but I'm not sure which option to use. I don't want to break anything or leave the system in a bit of a mess. Here's what happens, james@Hawaiian:~$ sudo aptitude install nvidia-settings The following NEW packages will be installed: libxnvctrl0{a} nvidia-settings pkg-config{a} 0 packages upgraded, 3 newly installed, 0 to remove and 68 not upgraded. Need to get 907 kB of archives. After unpacking 1,927 kB will be used. The following packages have unmet dependencies: nvidia-alternative : Breaks: nvidia-settings ( 319.49) but 304.88-1 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) libegl1-nvidia 2) libgl1-nvidia-glx 3) libgles1-nvidia 4) libgles2-nvidia 5) libnvidia-ml1 6) nvidia-alternative 7) nvidia-driver 8) nvidia-driver-bin 9) nvidia-kernel-dkms 10) nvidia-vdpau-driver 11) xserver-xorg-video-nvidia Leave the following dependencies unresolved: 12) nvidia-settings recommends libgl1-nvidia-glx 13) nvidia-driver recommends libgles1-nvidia (= 340.65-2~bpo70+1) 14) nvidia-driver recommends libgles2-nvidia (= 340.65-2~bpo70+1) 15) nvidia-driver-bin recommends nvidia-driver 16) nvidia-kernel-dkms recommends nvidia-driver (= 340.65) | libcuda1 (= 3 17) nvidia-vdpau-driver recommends nvidia-kernel-dkms (= 340.65-2~bpo70+1) | 18) xserver-xorg-video-nvidia recommends nvidia-driver (= 340.65) 19) xserver-xorg-video-nvidia recommends nvidia-vdpau-driver (= 340.65) 20) xserver-xorg-video-nvidia recommends nvidia-kernel-dkms (= 340.65-2~bpo7 Accept this solution? [Y/n/q/?] Is this OK to accept? Thanks James
Re: Very small fonts in KDE after installing Nvidia drivers
Ok, that worked brilliantly! I just followed Mark's suggestion of putting that line in my 20-nvidia.conf. Thanks! On 26 February 2015 at 19:46, Mark Neyhart mark.neyh...@akleg.gov wrote: On 02/26/2015 02:28 AM, James Allsopp wrote: Hello, I've just installed the nvidia drivers after following the instructions here https://wiki.debian.org/NvidiaGraphicsDrivers but now my fonts are so small they are unreadable. My display is a HDMI television. I think this could be related to the EDID settings but I'm not sure how to set this. I'm using the small piecewise Xorg described in the document. echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf I just went through this last week with Debian Wheezy using a large television driven by an Nvidia card with the proprietary Nvidia driver. I added Option DPI 100 x 100 to my xorg.conf in the Device section for the Nvidia card. In your case I think you should be able to replace your echo statement with: echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\n\tOption DPI 100 x 100\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf Watch out for line wrapping, this should all be on one line. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ef7802.3010...@akleg.gov
Very small fonts in KDE after installing Nvidia drivers
Hello, I've just installed the nvidia drivers after following the instructions here https://wiki.debian.org/NvidiaGraphicsDrivers but now my fonts are so small they are unreadable. My display is a HDMI television. I think this could be related to the EDID settings but I'm not sure how to set this. I'm using the small piecewise Xorg described in the document. echo -e 'Section Device\n\tIdentifier My GPU\n\tDriver nvidia\nEndSection' /etc/X11/xorg.conf.d/20-nvidia.conf I can't run nvidia-settings as I can't read the text, Any ideas what changes I need to make to fix this please? Thanks, James
Disk in a raid array
Hi, I've got home mounted on a LVM partition over two RAID 1 arrays. Unfortunately one of the disks in the second array has dropped out. I can still fdisk -l it, but when I ran dd if=/dev/sdd1 of=/dev/null it got about 132M through a 2Tb drive before crashing out. This doesn't bode well. I can't really afford a new drive, but was wondering if I should just reformat, try and check it for errors and then try and add it back to the array? I was hoping that doing that might allow it to exclude any bad blocks and get me something working for a while whilst I save up. If anyone has any comments, suggestions or queries, I'd be glad to hear them, Thanks, James
Upgrading from squeeze to wheezy
Hi, I've not had access to my machine for a while, and I've just tried to do an upgrade from squeeze to wheezy using the instructions found here; http://www.howtoforge.com/how-to-upgrade-debian-squeeze-to-wheezy and I got to the aptitude full-upgrade part which seemed to hang I've tried dpkg --configure -a apt-get -f install but can't get anything to work. Here's a list of the objections, but I don't know how to solve them, short of installing every package manually. If you've any ideas, I would be grateful to receive them, James Reading package lists... Building dependency tree... Reading state information... You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: brasero : Depends: libbrasero-media3-1 (= 3.4.1-4) but it is not installed Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not installed Depends: libnautilus-extension1a (= 2.91) but it is not installed Depends: libtotem-plparser17 (= 2.32) but 2.30.3-1 is installed Depends: libtracker-sparql-0.14-0 (= 0.10.0) but it is not installed epiphany-browser : Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not installed Depends: libseed-gtk3-0 but it is not installed Depends: libsoup-gnome2.4-1 (= 2.37.1) but 2.30.2-1+squeeze1 is installed Depends: libsoup2.4-1 (= 2.33.92) but 2.30.2-1+squeeze1 is installed Depends: libwebkitgtk-3.0-0 (= 1.7.92) but it is not installed Depends: gsettings-desktop-schemas but it is not installed epiphany-extensions : Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not installed Depends: libwebkitgtk-3.0-0 (= 1.3.10) but it is not installed evince : Depends: libevdocument3-4 (= 3.4.0-3.1) but it is not installed Depends: libevview3-3 (= 3.4.0-3.1) but it is not installed Depends: libgail-3-0 (= 3.0.0) but it is not installed Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not installed Depends: libnautilus-extension1a (= 2.91) but it is not installed Depends: evince-common (= 3.4) but 2.30.3-2+squeeze1 is installed file-roller : Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not installed Depends: libnautilus-extension1a (= 2.91) but it is not installed Depends: nautilus-data (= 3.0) but 2.30.1-2squeeze2 is installed gir1.2-atk-1.0 : Depends: gir1.2-glib-2.0 but it is not installed gir1.2-freedesktop : Depends: gir1.2-glib-2.0 (= 1.32.1-1) but it is not installed gir1.2-pango-1.0 : Depends: gir1.2-glib-2.0 but it is not installed gnome : Depends: gnome-core (= 1:3.4+7+deb7u1) but 1:2.30+7 is installed Depends: network-manager-gnome (= 0.9.4) but it is not installed Depends: aisleriot (= 1:3.4) but it is not installed Depends: cheese (= 3.4) but 2.30.1-2 is installed Depends: evolution (= 3.4) but 2.30.3-5 is installed Depends: evolution-plugins (= 3.4) but 2.30.3-5 is installed Depends: gedit (= 3.4) but 2.30.4-1squeeze1 is installed Depends: gnome-color-manager (= 3.4) but it is not installed Depends: gnome-documents (= 0.4) but it is not installed Depends: gnome-games (= 1:3.4) but 1:2.30.2-2 is installed Depends: gnome-nettool (= 3.2) but 2.30.0-3 is installed Depends: rygel-preferences (= 0.14) but it is not installed Depends: seahorse (= 3.4) but 2.30.1-2 is installed Depends: alacarte (= 0.13.4) but 0.13.2-1 is installed Depends: gimp (= 2.8) but 2.6.10-1+squeeze4 is installed Depends: gnome-media (= 3.4) but 2.30.0-1 is installed Depends: gnome-tweak-tool (= 3.4) but it is not installed Depends: inkscape (= 0.48) but 0.47.0-2+b1 is installed Depends: libreoffice-gnome but it is not installed Depends: libreoffice-writer but it is not installed or abiword (= 2.8) but it is not installed Depends: libreoffice-calc but it is not installed or gnumeric (= 1.10) but it is not installed Depends: libreoffice-impress but it is not installed Depends: simple-scan but it is not installed Depends: tracker-gui but it is not installed Depends: cups-pk-helper (= 0.2) but it is not installed Depends: gedit-plugins (= 3.4) but 2.30.0-1 is installed Depends: gnome-shell-extensions (= 3.4) but it is not installed Depends: gstreamer0.10-ffmpeg (= 0.10.13) but 0.10.10-1 is installed Depends: gstreamer0.10-plugins-ugly (= 0.10.19) but 0.10.15-1 is installed Depends: rygel-playbin but it is not installed Depends: rygel-tracker but it is not installed Depends: telepathy-rakia but it is not installed Recommends: browser-plugin-gnash but it is not installed Recommends: gnome-games-extra-data (= 3.0)
Re: Upgrading from squeeze to wheezy
Thanks Bob, Hit a snag, I thought the upgrade would update the kernel and it's left me with a mismatch. I can't now log into the machine, no ssh and no keyboard. I think I'm going to try and use a netinst disk to rescue the system, unless you've any other ideas? I remember in Linux a long time ago there was a method to step through the boot sequence item by item. Could I wait until the network came up, then drop into a shell? Thanks James On 15 December 2014 at 20:10, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I've not had access to my machine for a while, and I've just tried to do an upgrade from squeeze to wheezy using the instructions found here; http://www.howtoforge.com/how-to-upgrade-debian-squeeze-to-wheezy Why are you using those instructions instead of the official Debian ones? https://www.debian.org/releases/stable/amd64/release-notes/index.en.html and I got to the aptitude full-upgrade part which seemed to hang If you read the howtoforge instructions carefully you will see that it says: Instead of using apt-get upgrade and apt-get dist-upgrade, you can also use the following commands, but please note that on http://www.debian.org/releases/wheezy/amd64/release-notes/ch-upgrading.en.html it reads The upgrade process for some previous releases recommended the use of aptitude for the upgrade. This tool is not recommended for upgrades from squeeze to wheezy.. For me, aptitude has worked fine for all Squeeze to Wheezy upgrades so far. Therefore when you are using the aptitude full-upgrade part above you are explicitly going outside of the official recommended procedure. I strongly recommend the apt-get upgrade and apt-get dist-upgrade approach instead as documented in the offical Debian release notes. I've tried dpkg --configure -a apt-get -f install but can't get anything to work. Did you forget to apt-get update after changing the sources.list file. apt-get update Systems can be complex with complex interactions. If every system were identical then it would be easy to test those and produce a plan that would work for everyone. So first let me say that it is hard because only your system is your system. Here's a list of the objections, but I don't know how to solve them, short of installing every package manually. If you've any ideas, I would be grateful to receive them, My official recommendation would be to follow the instructions in the release notes as that is the best complete source of knowledge on how to upgrade. I will guess that your problem here is some additional undesired source in your /etc/apt/sources.list or /etc/apt/sources.list.d/* files. Ensure you have a good system back. Reset sources.list back to Squeeze: apt-get update apt-get upgrade apt-get dist-upgrade # check removal list carefully! apt-get autoremove dpkg -l | grep ^rc apt-get purge ... find /etc -name '*.dpkg-*' -o -name '*.ucf-*' rm ... dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}' apt-get purge ... Reset sources.list to Wheezy: apt-get update apt-get upgrade apt-get dist-upgrade # check removal list carefully! apt-get autoremove dpkg -l | grep ^rc apt-get purge ... find /etc -name '*.dpkg-*' -o -name '*.ucf-*' rm ... dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}' apt-get purge ... As you can see I suggest cleaning to be very important. Leaving a lot of the lint behind can and does often cause real upgrade problems that does not exist on a clean system. When there is a conflict here I defer to the official Debian release notes. Bob
Re: the developers have spoken
https://lists.debian.org/debian-vote/2014/11/msg00171.html On 19 November 2014 14:41, Dan ganc...@gmail.com wrote: On Wed, Nov 19, 2014 at 3:11 PM, songbird songb...@anthive.com wrote: the vote is in. let us thank each one of them for their efforts to continue making Debian what it is: a fractious and wonderful expression of free source code, the ability to distribute such in a relatively sane and safe manner. kudoes, much love, go jessie! songbird What is the result? I looked at the webpage: https://www.debian.org/vote/2014/vote_003.en.html#outcome and the graph of the webpage: https://vote.debian.org/~secretary/gr_initcoupling/ But I couldn't figure out which is the outcome Thanks, Dani -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cak00fokz8mcczmb0_y3e0xhez8dfvm5ha0ftp3e9ztaxzpb...@mail.gmail.com
Re: Let's have a vote! I was just banned from debian forum for posting a systemd critical message.
Your posts were massively over the top, so I not surprised you got banned. Thanks for flagging up that debian forum, it's gone beneath my radar up to now! On 25 September 2014 20:46, Stephen Allen marathon.duran...@gmail.com wrote: On Thu, Sep 25, 2014 at 09:51:38AM -0700, Gregory Smith wrote: I was just banned from debian forum for posting a systemd critical message. I posted the message found here: https://lists.debian.org/debian-user/2014/09/msg01834.html It was deleted twice and then: You have been *permanently* banned from this board. Please contact the Board Administrator forumad...@forums.debian.net for more information. Reason given for ban: *You know why* *A ban has been issued on your username.* ---end quoted text--- Deservedly so, in my opinion. I'm sure the silent majority are as sick as I am of several people beating this dead horse to death. Most Linux distributions are DoCractic, those that do the work, make the rules. You're free to fork. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140925194627.GB8086@Jessie
Systemd resources
Hi, I'm really cynical about the Systemd concept, but if it looks like it's happening anyway, could we start making a list of recommended tutorials on using it. It would help if people recommending the tutorials had successfully followed them themselves. Yes, I could use Google, but it's a bit lacking in quality control, and a list would be useful to filter out the non-Debian specific stuff or to explain where they're not following best practice. I'm just hoping which ever way this goes in the end, at least the debate (and myself) can get a bit more informed, even if it's just using a VM for fifteen minutes. Please don't post opinions on whether systemd should be used, there are other threads for that. Thanks,
Using LTSP on a Debian server with Raspberry PI thin clients
Hi, To simplify things I was thinking about running a couple of RPI thin clients off my debian server? I would be using either powerline networking or wireless. I think I'll need to install a special bootloader on the RPI as they can't boot using PXE. I was wondering if anyone had actually implemented a system like this, and if it was responsive enough to be useful? Are there any other considerations I might need to think about? All the best, James
Re: FW: [CTTE #727708] Default init system for Debian
Hi, After reading through all the pros and cons, it seems that there isn't a good replacement at all, so it would be better to wait. Admittedly I use OpenRC on my gentoo machine and it's fine. Systemd seems to violate too many Unix principles and Upstart has problems with the canonical copyright licence issues. I'd hate to see Linux get pulled apart between Red Hat and Canonical, so it's important that Debian doesn't act precipitously. James On 12 February 2014 08:06, Tom H tomh0...@gmail.com wrote: On Wed, Feb 12, 2014 at 12:12 AM, Chris Bannister cbannis...@slingshot.co.nz wrote: I tried systemd - booted really fast, but it didn't honor any console font settings I had. I groaned and reverted back realising, after seeing quite a bit of discussion, that there was another setup to learn! In this case the learning would be mandatory if I wanted to get my console back the way I had it! I expect that helping people configure and use systemd will become part of the normal business of this mailing list. I would've expected systemd to respect Debian's native console setup (and this might be worthy of a bug report). systemd uses /etc/vconsole.conf. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=Sy2nD2cFK2VU7K3+cuaec+JiA6rQ=ZgT_WGNcADT6xY=q...@mail.gmail.com
Re: FW: [CTTE #727708] Default init system for Debian
Hi Scott, Fair enough with this point; a. The decision *was* made by Debian developers, as it should be. Those that do, get to make decisions about how they do 'it' - those that use, feel free to use elsewhere - or do their own fork instead of getting others to do it for them. Although I mentioned Gentoo, I've been using Debian for about 5 years now and like it, basing all my new linux systems on it, I just mentioned gentoo as contrast. When you say Default, the difficulty of opting out plays a factor too. If something is so difficult to opt out of, it then becomes Debian's de facto system. It is a worry, perhaps there's some documentation of how to opt out, so I can look at this? Is there a document that summarises what developers thought the pros and cons of each were? I've read LP's comments on systemd, but that hardly falls into the balanced camp. James On 12 February 2014 11:36, Scott Ferguson scott.ferguson.debian.u...@gmail.com wrote: On 12/02/14 20:27, James Allsopp wrote: Hi, After reading through all the pros and cons, it seems that there isn't a good replacement at all, so it would be better to wait. Admittedly I use OpenRC on my gentoo machine and it's fine. Systemd seems to violate too many Unix principles and Upstart has problems with the canonical copyright licence issues. I'd hate to see Linux get pulled apart between Red Hat and Canonical, so it's important that Debian doesn't act precipitously. James a. The decision *was* made by Debian developers, as it should be. Those that do, get to make decisions about how they do 'it' - those that use, feel free to use elsewhere - or do their own fork instead of getting others to do it for them. b. you're flogging a dead horse, the decision *has* been made. c. it's the *default* init system for *Jessie*. Emphasis on default, Debian's commitment to choice remains unaltered. In a futile effort to forestall pointless and unproductive opinions and the debatable 'right' of people to hold and express them. NOTES: I'm not commenting specifically on your post James, it's just a point in the thread to inject my opinion in support of the decision by Debian Technical. Apropos of little - interesting how many of the, um, most passionate views are expressed by those that *don't* use Debian (have deep emotional commitment will travel?). If it's relevant - I don't prefer systemd, but I do prefer the Debian way. Kind regards. snipped -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb5cac.2030...@gmail.com
Re: testing wants to install systemd
Hi, From a casual perusal of the lists systemd, seems to be getting a reputation as one of the those projects to avoid like pulse-audio and mono, but the link you sent sounds more reasonable. Is there a good balanced discussion anywhere? James On 20 November 2013 10:00, Zenaan Harkness z...@freedbms.net wrote: On 11/20/13, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Wed, 2013-11-20 at 09:08 +0100, Slavko wrote: Please, how useful are Arch's things for me as Debian user? My apologies Slavko, I'll rephrase it, the state of Debian's testing initscripts/systemd seems to be neither fish nor fowl. When I experienced this on Arch Linux during the transition from initscripts to systemd, I didn't use it for perhaps 1 year and then, when the transition was finished, there wasn't the choice to use initscripts or systemd anymore, I installed a new Arch Linux. Switching from initscripts to systemd was the only transition ever, that caused issues for me and I'm still not friend with systemd. OK, so Arch transition was handled sub-optimally for you. since anything else but the speed of booting is a step in the wrong direction, instead of human readable scripts, one big binary blob, associated with the name Lennart P.. Seriously, systemd is crap, Ralph, please write a constructive problem and not a ad-hominem against software attack non-argument. Especially, if you have a personal particular crappiness about systemd, which perhaps you disagree about something here: http://0pointer.de/blog/projects/the-biggest-myths.html then that would be much more constructive to useful discussion. Thanks heaps Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnsqvq7keiwnr0b+si-7velem9g7k7cqw0lql1f8kvc5...@mail.gmail.com
Re: New Gnome in Wheezy
You can't. You have to install a different DE. I went for XFCE, but people rate Mate. This is a sore point for a lot of people, but that's the simple options. let the flamewar commence On 10 July 2013 16:56, Ethan Rosenberg, PhD erosenb...@hygeiabiomedical.com wrote: Dear List - I updated and now have the new Gnome. The desktop is impossible, and almost unusable. I do not have the old desktop entries, and cannot find Google Chrome. How do I get the old desktop back? Ethan -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.**debian.orgdebian-user-requ...@lists.debian.orgwith a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**51DD842C.802@hygeiabiomedical.**comhttp://lists.debian.org/51dd842c@hygeiabiomedical.com
Re: Debian machine not booting
Hi, Got the problems solved. I couldn't solve the problem by using the rescue disk, as it wouldn't let me stop the raid array. What I did was drop into the maintenance mode: mdadm --assemble /dev/md1 /dev/sdd1 /dev/sde1 //This should recreate the array mdadm --detail --scan /etc/mdadm/mdadm.conf //edit the file to remove duplicates dpkg-reconfigure linux-image-$(uname -r) then reboot. Huge amount of thanks go to Bob Proulx for all the help along the way, James On 7 July 2013 21:53, James Allsopp jamesaalls...@googlemail.com wrote: Hello, I've been too nervous to reboot, so I've left it in the rescue mode at the point where I assembled the raid arrays and went into boot at the \ partition. Tried to run: mdadm --stop /dev/md127 but got a mdadm: failed to stop array /dev/md127: Device or resource busy. Perhaps a running process, mounted filesustem or active volume group? I tried unmounting /home which stretches onto this disk via LVM, but this made no difference. Any idea how I should proceed? Thanks, James On 5 July 2013 01:10, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! Basically I had expected you to use either rescue mode of the d-i or a livecd or other to assemble the arrays. You did. But neither array came up completely correct. One came up with one disk degraded. The split brain clone came up on md127 instead of md0. The other one came up on md126. So you should fix those using the discussed instructions. I was thinking you would do that from the same system boot that you had posted that information from. But your recent mail implies that you shut the system down and went away for a while. So now it appears you need to rescue the system again by the same method you used to get that information you posted. All of that is fine. Except now we already know the information you posted. And so now we know how those arrays are supposed to go together. But that is okay. You can go through rescue mode and assemble the arrays exactly as you did before. And then --stop the arrays and assemble them correctly. But since we know how they are supposed to be assembled now you could skip the assembly of them in rescue mode or livecd mode or whatever you used and simply assemble the arrays correctly the first time. Basically I think you are going to do: * rescue * assemble arrays * stop arrays * assemble arrays correctly Which is perfectly acceptable. The result will be fine. But now that we know what we need to do you could simply do this: * rescue * assemble arrays correctly But I don't want to distract you with complications like this! :-) And then after you get everything working you should visit the partitioning on that second array. Your partitioning starts at the sector 1. But that won't be aligned. It will cause all writes to be a read-modify-write and performance will suffer. Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Device Boot Start End Blocks Id System /dev/sde1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Instead of using the entire disk starting at 1 it would be much better if you started at sector 2048 as is the new standard for Advanced Format 4k sector drives. I would expect that to be a large performance lever on your system. But fix that after you have your data up and available. Bob
Re: Debian machine not booting
Hello, I've been too nervous to reboot, so I've left it in the rescue mode at the point where I assembled the raid arrays and went into boot at the \ partition. Tried to run: mdadm --stop /dev/md127 but got a mdadm: failed to stop array /dev/md127: Device or resource busy. Perhaps a running process, mounted filesustem or active volume group? I tried unmounting /home which stretches onto this disk via LVM, but this made no difference. Any idea how I should proceed? Thanks, James On 5 July 2013 01:10, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! Basically I had expected you to use either rescue mode of the d-i or a livecd or other to assemble the arrays. You did. But neither array came up completely correct. One came up with one disk degraded. The split brain clone came up on md127 instead of md0. The other one came up on md126. So you should fix those using the discussed instructions. I was thinking you would do that from the same system boot that you had posted that information from. But your recent mail implies that you shut the system down and went away for a while. So now it appears you need to rescue the system again by the same method you used to get that information you posted. All of that is fine. Except now we already know the information you posted. And so now we know how those arrays are supposed to go together. But that is okay. You can go through rescue mode and assemble the arrays exactly as you did before. And then --stop the arrays and assemble them correctly. But since we know how they are supposed to be assembled now you could skip the assembly of them in rescue mode or livecd mode or whatever you used and simply assemble the arrays correctly the first time. Basically I think you are going to do: * rescue * assemble arrays * stop arrays * assemble arrays correctly Which is perfectly acceptable. The result will be fine. But now that we know what we need to do you could simply do this: * rescue * assemble arrays correctly But I don't want to distract you with complications like this! :-) And then after you get everything working you should visit the partitioning on that second array. Your partitioning starts at the sector 1. But that won't be aligned. It will cause all writes to be a read-modify-write and performance will suffer. Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Device Boot Start End Blocks Id System /dev/sde1 1 243201 1953512001 fd Linux raid autodetect Partition 1 does not start on physical sector boundary. Instead of using the entire disk starting at 1 it would be much better if you started at sector 2048 as is the new standard for Advanced Format 4k sector drives. I would expect that to be a large performance lever on your system. But fix that after you have your data up and available. Bob
Re: Debian machine not booting
Thanks Bob, like I say, very much appreciated and I'll let you know how it goes! I'd like to hear about the optimisations, but I think I'll wait till I get the system rebuilt! James On 4 July 2013 00:47, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: Thanks Bob, really can't thank you enough. Just to be clear about this, I'd do these commands from the rescue disk after I have assembled the arrays and gone to the bash shell? Short answer: Yes. Go for it! Longer answer: There are all kinds of things I want to say here. And I already said a lot! There are some optimizations that could be made. But if you do what is outlined it should work. But I don't want to make things more confusing by talking about minor things. I have my fingers crossed for you! :-) Bob
Re: Debian machine not booting
Thanks Bob, really can't thank you enough. Just to be clear about this, I'd do these commands from the rescue disk after I have assembled the arrays and gone to the bash shell? Much appreciated, James On 2 July 2013 22:44, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I don't see sda anywhere. It might be a dual booting Windows disk? Or other. But the BIOS will boot the first disk from the BIOS boot order. BIOS boot order may be different from OS disk order. It can be confusing. I might assume that BIOS sata0 is the same as the OS disk sda but actually it often is different. Let's ignore this for now. You have sdb1 and sdc1 mirrored into md1. I can see that because the UUID is identical. /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 That info is the same as: /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 1 001 removed The UUIDs are identical. Therefore those two disks are mirrors of each other. And note: /dev/md1: (/dev/sde1) Update Time : Tue Jul 2 13:49:55 2013 /dev/md127: (/dev/sdd1) Update Time : Tue Jul 2 13:49:29 2013 sde1 is newer than sdd1. This seems consistent with it being the best copy to keep. If it were the other way around I would think about using the other one. But selecting the right master is important since it is a component of the lvm. How should I proceed from here? I would proceed as previously suggested. I would do this: mdadm --stop /dev/md127 mdadm --manage /dev/md1 --add /dev/sdd1 watch cat /proc/mdstat That will discard the older stale copy of the mirror on sdd1. It will use sdd1 as a mirror of sde1. After doing the add the mirror will sync and you can watch the progress using 'watch cat /proc/mdstat'. Use control-c to interrupt it when you want to stop it. For ruther information: /dev/sdb3: Preferred Minor : 126 ... /dev/sdc3: Preferred Minor : 126 ... That further information looked _okay_ to me. But I would still change the md126 back to md0. mdadm --stop /dev/md126 mdadm --assemble /dev/md0 --update=super-minor /dev/sdb1 /dev/sdc1 cat /proc/mdstat Since it is clean now it will be stopped cleanly and reassembled cleanly and no sync will be needed. The --update=super-minor will reset the superblock with the updated md0 minor device number. Then update /etc/mdadm/mdadm.conf and rebuild the initrd. Bob
Re: Debian machine not booting
Thanks Bob, I'll get back to after I've followed your instructions. I think I'm going to have to learn to type with crossed fingers! I think I initially sorted out all my partitions manually, rather than directly using the installer to do it automatically, Really appreciated, James On 2 July 2013 00:46, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] md126 : active raid1 sdb3[0] sdc3[1] 972550912 blocks [2/2] [UU] So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One full array is assembled. Is /dev/md126 your preferred name for that array? I would guess not. Usually it is /dev/md0 or some such. But when that name is not available because it is already in use then mdadm will rotate up to a later name like /dev/md126. You can fix this by using mdadm with --update=super-minor to force it back to the desired name. Something like this using your devices: mdadm --assemble /dev/md0 --update=super-minor /dev/sdb3 /dev/sdc3 But that can only be done at assembly time. If it is already assembled then you would need to stop the array first and then assemble it again. md127 : active raid1 sdd1[0] 1953510841 blocks super 1.2 [2/1] [U_] md1 : active raid1 sde1[1] 1953510841 blocks super 1.2 [2/1] [_U] I think this array is now has a split brain problem. At this point the original single mirrored array has had both halves of the mirror assembled and both are running. So now you have two clones of each other and both are active. Meaning that each think they are newer than the other. Is that right? In which case you will eventually need to pick one and call it the master. I think the sde1 is the natural master since it is assembled on /dev/md1. cat /etc/mdadm/mdadm.conf ... # definitions of existing MD arrays ARRAY /dev/md0 UUID=a529cd1b:c055887e:bfe78010:bc810f04 Only one array specified. That is definitely part of your problem. You should have at least two arrays specified there. mdadm --detail --scan: ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 That mdadm --scan only found one array is odd. fdisk -l Disk /dev/sda: 120.0 GB, 120033041920 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002ae52 Device Boot Start End Blocks Id System /dev/sda1 1 14593 117218241 83 Linux I take it that this is your boot disk? Your boot disk is not RAID? I don't like that the first used sector is 1. That would have been 63 using the previous debian-installer to leave space for the MBR and other things. But that is a different issue. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes That is an Advanced Format 4k sector drive. Meaning that the partitions should start on a 4k sector alignment. The debian-installer would do this automatically. Disk identifier: 0xe044b9be Device Boot Start End Blocks Id System /dev/sdd1 1 243201 1953512001 fd Linux raid autodetect ^ /dev/sde1 1 243201 1953512001 fd Linux raid autodetect ^ Partition 1 does not start on physical sector boundary. I don't recall if the first sector is 0 or 1 but I think the first sector is 0 for the partition table. Meaning that sector 1 is not going to be 4k aligned. (Can someone double check me on this?) Meaning that this will require a lot of read-modify-write causing performance problems for those drives. The new standard for sector alignment would start at 2048 to leave space for the partition table and other things and still be aligned properly. I don't know if this helps or where to go from here, but I think I need to get the mdadm up and running properly before I do anything. Probably a good idea. If there's any commands you need me to run, please ask, How are you booted now? Are you root on the system through something like the debian-installer rescue boot? Or did you use a live cd or something? Please run: # mdadm --detail /dev/sdd1 # mdadm --detail /dev/sde1 Those are what look to be the split brain of the second array. They will list something at the bottom that will look like: Number Major Minor RaidDevice State this 1 8 171 active sync /dev/sdb1 0 0 810 active sync /dev/sda1 1 1
Re: Debian machine not booting
One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I tried mdadm --detail /dev/sdd1 but it didn't work. I have these results if they help? /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 1 001 removed How should I proceed from here? James On 2 July 2013 09:50, James Allsopp jamesaalls...@googlemail.com wrote: Thanks Bob, I'll get back to after I've followed your instructions. I think I'm going to have to learn to type with crossed fingers! I think I initially sorted out all my partitions manually, rather than directly using the installer to do it automatically, Really appreciated, James On 2 July 2013 00:46, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] md126 : active raid1 sdb3[0] sdc3[1] 972550912 blocks [2/2] [UU] So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One full array is assembled. Is /dev/md126 your preferred name for that array? I would guess not. Usually it is /dev/md0 or some such. But when that name is not available because it is already in use then mdadm will rotate up to a later name like /dev/md126. You can fix this by using mdadm with --update=super-minor to force it back to the desired name. Something like this using your devices: mdadm --assemble /dev/md0 --update=super-minor /dev/sdb3 /dev/sdc3 But that can only be done at assembly time. If it is already assembled then you would need to stop the array first and then assemble it again. md127 : active raid1 sdd1[0] 1953510841 blocks super 1.2 [2/1] [U_] md1 : active raid1 sde1[1] 1953510841 blocks super 1.2 [2/1] [_U] I think this array is now has a split brain problem. At this point the original single mirrored array has had both halves of the mirror assembled and both are running. So now you have two clones of each other and both are active. Meaning that each think they are newer than the other. Is that right? In which case you will eventually need to pick one and call it the master. I think the sde1 is the natural master since it is assembled on /dev/md1. cat /etc/mdadm/mdadm.conf ... # definitions of existing MD arrays ARRAY /dev/md0 UUID=a529cd1b:c055887e:bfe78010:bc810f04 Only one array specified. That is definitely part of your problem. You should have at least two arrays specified there. mdadm --detail --scan: ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 That mdadm --scan only found one array is odd. fdisk -l Disk /dev/sda: 120.0 GB, 120033041920 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002ae52 Device Boot Start End Blocks Id System /dev/sda1 1 14593 117218241 83 Linux I take it that this is your boot disk? Your boot disk is not RAID? I don't like that the first used sector is 1. That would have been 63 using the previous debian-installer to leave space for the MBR and other things. But that is a different issue. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096
Re: Debian machine not booting
For ruther information: /dev/sdb3: Magic : a92b4efc Version : 0.90.00 UUID : a529cd1b:c055887e:bfe78010:bc810f04 Creation Time : Fri Nov 20 09:37:34 2009 Raid Level : raid1 Used Dev Size : 972550912 (927.50 GiB 995.89 GB) Array Size : 972550912 (927.50 GiB 995.89 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 126 Update Time : Tue Jul 2 13:49:18 2013 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 6203fa40 - correct Events : 1036616 Number Major Minor RaidDevice State this 0 8 190 active sync /dev/sdb3 0 0 8 190 active sync /dev/sdb3 1 1 8 351 active sync /dev/sdc3 /dev/sdc3: Magic : a92b4efc Version : 0.90.00 UUID : a529cd1b:c055887e:bfe78010:bc810f04 Creation Time : Fri Nov 20 09:37:34 2009 Raid Level : raid1 Used Dev Size : 972550912 (927.50 GiB 995.89 GB) Array Size : 972550912 (927.50 GiB 995.89 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 126 Update Time : Tue Jul 2 13:49:18 2013 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 6203fa52 - correct Events : 1036616 Number Major Minor RaidDevice State this 1 8 351 active sync /dev/sdc3 0 0 8 190 active sync /dev/sdb3 1 1 8 351 active sync /dev/sdc3 /dev/sdd1: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : a544829f:33778728:79870439:241c5c51 Name : Hawaiian:1 (local to host Hawaiian) Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 3907021954 (1863.01 GiB 2000.40 GB) Array Size : 3907021682 (1863.01 GiB 2000.40 GB) Used Dev Size : 3907021682 (1863.01 GiB 2000.40 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 1e0de6be:bbcc874e:e00e2caa:593de9b1 Update Time : Tue Jul 2 13:51:19 2013 Checksum : a8cf720f - correct Events : 108 Device Role : Active device 0 Array State : A. ('A' == active, '.' == missing) /dev/sde1: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : a544829f:33778728:79870439:241c5c51 Name : Hawaiian:1 (local to host Hawaiian) Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 3907021954 (1863.01 GiB 2000.40 GB) Array Size : 3907021682 (1863.01 GiB 2000.40 GB) Used Dev Size : 3907021682 (1863.01 GiB 2000.40 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 926788c3:9dfbf62b:26934208:5a72d05d Update Time : Tue Jul 2 13:51:05 2013 Checksum : 94e2b4a1 - correct Events : 114 Device Role : Active device 1 Array State : .A ('A' == active, '.' == missing) Thanks James On 2 July 2013 13:52, James Allsopp jamesaalls...@googlemail.com wrote: One other point sda isn't the boot hard drive, that's the partitions /sdb1 and sdc1, but these should be the same (I thought I'd mirrored them to be honest). I tried mdadm --detail /dev/sdd1 but it didn't work. I have these results if they help? /dev/md1: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:55 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 112 Number Major Minor RaidDevice State 0 000 removed 1 8 651 active sync /dev/sde1 /dev/md127: Version : 1.2 Creation Time : Thu Jan 31 22:43:49 2013 Raid Level : raid1 Array Size : 1953510841 (1863.01 GiB 2000.40 GB) Used Dev Size : 1953510841 (1863.01 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Tue Jul 2 13:49:29 2013 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : Hawaiian:1 (local to host Hawaiian) UUID : a544829f:33778728:79870439:241c5c51 Events : 106 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1
Re: Debian machine not booting
: 512 bytes Disk identifier: 0x Disk /dev/md126: 995.9 GB, 995892133888 bytes 2 heads, 4 sectors/track, 243137728 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/dm-0: 10.5 GB, 1048576 bytes 255 heads, 63 sectors/track, 1274 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/dm-1: 36.7 GB, 3670016 bytes 255 heads, 63 sectors/track, 4461 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/dm-2: 1375.7 GB, 1375731712000 bytes 255 heads, 63 sectors/track, 167256 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 512 bytes Disk identifier: 0x Disk /dev/dm-3: 10.5 GB, 1048576 bytes 255 heads, 63 sectors/track, 1274 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x -- I don't know if this helps or where to go from here, but I think I need to get the mdadm up and running properly before I do anything. I get some errors running those commands but they didn't get written to the file. E.g. mdadm --detail --scan mdadm: cannot open /dev/md/Hawaiian:1: No such file or directory mdadm: cannot open /dev/md/1: No such file or directory ARRAY /dev/md/0_0 metadata=0.90 UUID=a529cd1b:c055887e:bfe78010:bc810f04 If there's any commands you need me to run, please ask, Thanks, James On 18 June 2013 20:47, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. Bummer. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. Sounds fine. Assuming that it booted after those changes. When I boot all four drives are detected in BIOS and I've check all the connections. Good. It gets to 3 logical volumes in volume group VolGroup now active which sounds good. That does sound good. Then here's the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/VolGroup-LogVol03 /dev/mapper/VolGroup-LogVol03: The superblock could not be read or does not describe a correct ext2 . Hmm... I am not familiar with that error. But searching the web found several stories about it. Most concerned recent changes to the system that prevented it from booting. I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. And you rebooted in that time period? Otherwise these changes, if not done completely correct, seem prime to have triggered your current problem independent of any other action. You say it was on for a long time. If you had not rebooted in that long time then this may have been a hang-fire problem for all of that time. I'm wondering if some of the drive id's have been switched. If you mean the drive UUIDs then no those would not have changed. Any help would be really appreciated. I'm worried I've lost all my data on home First, do not despair. You should be able to get your system working again. You are probably simply missing the extra raid pair configuration. I strongly recommend using the debian-installer rescue mode to gain control of your system again. It works well and is readily available. Use a standard Debian installation disk. Usually we recommend the netinst disk because it is the smallest image. But any of the netinst or CD#1 or DVD#1 images will work fine for rescue mode since it is not actually installing but booting your system at that point so the difference between them does not matter. You have a disk? Go fish it out and boot it. Here is the official
Debian machine not booting
Hi, I have a debian machine which was on for a long time (~months). Just moved house and rebooted and now it doesn't boot. My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM spanning them. Originally there was just one pair, but then I got two new hard drives and added them. I then increased the space of VolGroup-LogVol03 to cover these new drives and increase the space of Home (/ wass on one of the other logical volume groups). This all worked fine for ages. When I boot all four drives are detected in BIOS and I've check all the connections. It gets to 3 logical volumes in volume group VolGroup now active which sounds good. Then Activating lvm and md swap.. done Checking file sysmtes...fsck from util-linux-ng 2.17.2 Says /dev/sde1: clean /dev/sda1:clean /dev/mapper/VolGroup-LogVol01: clean /dev/mapper/VolGroup-LogVol02: clean Then here's the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/VolGroup-LogVol03 /dev/mapper/VolGroup-LogVol03: The superblock could not be read or does not describe a correct ext2 . NB. All partitions are Ext4, from memory. It then drops to a maintenance shell. and says to check a log (/var/log/fsck/checkfs) but I don't even have a log directory at this point in the boot process. I'm wondering if some of the drive id's have been switched. Apologies for quoting, I'm not using the computer in question. Any help would be really appreciated. I'm worried I've lost all my data on home Thanks, James
Re: Debian 7 Wheezy Stable Relelased
Hi, What I meant was I wan to upgrade an existing system from Squeeze to Wheezy but replacing Gnome2 with XFCE, which seems a more natural upgrade path. I'd rather not have the grief of trying to remove a load of gnome3 libraries. I think I'll have to install XFCE then remove Gnome2 before the upgrade? Thanks, James On 6 May 2013 07:32, Andrei POPESCU andreimpope...@gmail.com wrote: On Du, 05 mai 13, 23:44:36, Carl Fink wrote: That's really odd. Reinstalling Debian from scratch only takes an hour at most, after all. (I use dpkg --get-selections selections.txt to record which packages I had installed.) BTW: +section id=dpkg-set-selections + titlecommanddpkg --set-selections/command changes/title + para +The commanddpkg --set-selections/command command is now aware of the +architecture of packages it selects and can only set the state for known +packages. Therefore an up-to-date filenameavailable/filename +database is needed for the command to be useful. + /para + para +To update the filenameavailable/filename database on an +systemitem role=packageapt/systemitem-based system, run the +commandsync-available/command command from the +systemitem role=packagedctrl-tools/systemitem package. +See the ulink url=url-wiki;Teams/Dpkg/FAQdpkg FAQ/ulink +for more information. + /para +/section (pending inclusion in the Release Notes) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
PureFTPd
Hi, I've a pureFTPD install that I need to increase the quota and max size of one file on. How can I go about doing that? Thanks, James
Using VMware graphics drivers in a kvm windows guest?
Hi, I've heard that kvm windows guests have better graphics performance using the VMware drivers. I've tried to follow some instructions found on the web but can't get the install to run. Has anyone tried this, and if so how did they achieve it? Thanks, James
Re: Poll GNOME 3 + Shell usage
Hi, Another option would be, How many are using Gnome 3 under duress, and would go back to 2 if given the chance?. Really is the first Linux DE I've used where I thought I'd rather be using Windows. James On 11 February 2013 15:23, Erwan David er...@rail.eu.org wrote: On Mon, Feb 11, 2013 at 04:11:00PM CET, Gernot Super superger...@yahoo.com said: Dear fellow debian-users, since there are no concrete numbers how many people actually use GNOME 3 with Gnome-Shell (in debian) i set up a poll to get an impression. Thanks for taking the time! http://poll.pollcode.com/v4czi8 But no means very different things from No I do not use any DE, no I use another DE than gnome, no I use gnome 2, to I use gnome 3 without gnome shell... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130211152339.ga3...@rail.eu.org
Adding a new Raid-1 array to a LVM partition
Hi, Originally set my Debian system up on a raid array (raid 1 made up of 2x1Tb drives) containing four logical volumes, containing the following ext4 partitions. /boot is ext3 and separate, and swap is one partition on each drive. /dev/mapper/VolGroup-LogVol00 / /dev/mapper/VolGroup-LogVol01 /tmp /dev/mapper/VolGroup-LogVol02 /var /dev/mapper/VolGroup-LogVol03 /home # pvdisplay --- Physical volume --- PV Name /dev/md0 VG Name VolGroup PV Size 927.50 GiB / not usable 768.00 KiB Allocatable yes PE Size 4.00 MiB Total PE 237439 Free PE 23689 Allocated PE 213750 PV UUID vYmhhF-z0xf-QqGy-wYyZ-8IS2-bcRB-GlwfGa # vgdisplay --- Volume group --- VG Name VolGroup System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 5 VG Access read/write VG Status resizable MAX LV0 Cur LV4 Open LV 4 Max PV0 Cur PV1 Act PV1 VG Size 927.50 GiB PE Size 4.00 MiB Total PE 237439 Alloc PE / Size 213750 / 834.96 GiB Free PE / Size 23689 / 92.54 GiB VG UUID NhgEud-Mlip-Es6n-E4Bj-U8FU-7Rxx-2tkAVs lvdisplay --- Logical volume --- LV Name/dev/VolGroup/LogVol01 VG NameVolGroup LV UUIDwBchCi-lEZr-ML4C-2o6d-Oh1W-4Lh1-5glhQH LV Write Accessread/write LV Status available # open 1 LV Size9.77 GiB Current LE 2500 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Name/dev/VolGroup/LogVol00 VG NameVolGroup LV UUIDD4DPyJ-yTBC-Lnk8-qq2m-gBt7-WZ6C-v1h6M3 LV Write Accessread/write LV Status available # open 1 LV Size34.18 GiB Current LE 8750 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name/dev/VolGroup/LogVol03 VG NameVolGroup LV UUIDZKD1dH-8qAF-ZrEC-faHL-goeU-KJoZ-9i62PK LV Write Accessread/write LV Status available # open 1 LV Size781.25 GiB Current LE 20 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 --- Logical volume --- LV Name/dev/VolGroup/LogVol02 VG NameVolGroup LV UUIDPzHuVd-Mo6A-yu5x-uNC6-IuwB-V3K4-N5KsAa LV Write Accessread/write LV Status available # open 1 LV Size9.77 GiB Current LE 2500 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 There's only one physical volume, on md0 and one volume group. I've filled my /home so I've bought two 2TB drives and I want to make them into a raid array and add this to VolGroup-LogVol03. I was wondering if someone could check this to see if this is the right plan. Create the raid array: mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[de]1 Create a physical volume on it pvcreate /dev/md1 Extend the volume group vgextend VolGroup /dev/md1 Extend the logical partition lvextend /dev/VolGroup/LogVol03 -l +[large number] Check the partition. e2fsck -f /dev/VolGroup/LogVol03 Resize the filessystem. resize2fs /dev/VolGroup/LogVol03 Should this work? Thanks James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50aeb1bc.1060...@googlemail.com
Re: networking with virtual machine
Hi, I think I had a similar problem. To solve the problem first you need to set up a bridge, there's instructions in lots of places on how to do this, auto br0 iface br0 inet static address 192.168.1.2 network 192.168.1.0 netmask 255.255.255.0 #broadcast 192.168.0.255 gateway 192.168.1.1 bridge_ports eth0 bridge_fd 0 # bridge_hello 2 # bridge_maxage 12 bridge_stp off Then you need to alter the VM's xml file, interface type='bridge' mac address='52:54:00:87:97:a6'/ source bridge='br0'/ Hope this helps, and if you need any more information, just ask James On 14/09/12 00:48, lee wrote: Rob Owensrow...@ptd.net writes: On Thu, Sep 13, 2012 at 10:32:40PM +0200, lee wrote: Hi, since I'm not making any progress: I want to set up a VM (running testing) that can be reachable from the outside over the network. I've done that 2 years or so ago and I forgot how to do the networking setup, and network configuration has changed in the meantime. I need to somehow set up a bridge interface so the guest can tap into it. I don't understand the docs I found about that. Looking at [1], I can see that my physical network adaptor won't have an IP address anymore and that there is only a bridge interface instead. This is probably not what I want, and I remember I did it differently before, after lots of experimenting. If you're using Virtualbox, you don't need to set up a bridged interface with regular Linux tools. You can just select Bridged networking for your virtual machine and Virtualbox handles it. In older versions of Virtualbox, it was necessary to set up a bridged interface using Linux tools. Their documentation covered it fairly well as I recall. I think that was in the version 1.x days. Maybe you can find some of their old documentation. Oh I should have mentioned that I'm not using Virtualbox but qemu/kvm or how it's called. That seems to suggest using a bridge[1], and I find that very confusing. I understand that apparently I am supposed to replace my currently used eth1 by a bride device which uses eth1 and to which I could add other physical devices like eth0. I don't understand what the purpose of adding more physical devices would be and what I actually get when I have such a bridge device and what all that has to do with a guest. It seems to me that having the bridge device in theory would somehow magically enable me to give the guest an IP address in the same network as the host is. That isn't what I want because I want the guest behind the firewall which is on the host (using shorewall). Of course, I also don't want to compromise eth1 in any way and don't want to have my firewall somehow penetrated, which I have no idea about whether it could happen or not with introducing a bridge device. I don't get it, it doesn't make any sense to me. At this point, I don't even know what questions I need to ask. [1]: ... or allowing the guest access to a physical network card, about which I don't know whether my hardware would support it or not --- and I'd have to buy a network cable and plug that into the router in which case the guest still won't be behind the firewall of the host -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5055c5b4.2020...@googlemail.com
Networking for kvm virtual machines
Hello, I'm trying to learn more about networking and set up BIND, LDAP and Nagios on a KVM virtual machine. The VM works great and I can ssh into it from the host, and view the nagios pages from the host. However the VM gets the address 192.168.1.x and the host is 192.168.1.2. What I really want to do is set it up so that the VM just appears as another machine on my network I can view from anywhere on my network. I set up a bridge on the host, configured as below in /etc/network/interfaces; auto lo iface lo inet loopback auto eth0 #iface eth0 inet dhcp iface eth0 inet manual auto br0 iface br0 inet static address 192.168.1.2 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.1.1 bridge_ports eth0 bridge_fd 0 bridge_hello 2 bridge_maxage 12 bridge_stp off If anyone has any suggestions on how to do this I would be very grateful. James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cad3_cnm0aqutapj6e2znvy4df6w8sq9kig6b7mbj3tzxtgy...@mail.gmail.com
Re: Networking for kvm virtual machines
Ah, was worklng from memory, a mistake. Just restarted everything and the address of the virtual machine is 192.168.122.216 so on a different subnet. Looking at the output of ps aux | grep network, I found this: ja@Hawaiian:~$ ps aux | grep network nobody6157 0.0 0.0 22760 956 ?S22:04 0:00 dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --listen-address 192.168.122.1 --except-interface lo --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253 and an /sbin/ifconfig gives this: a@Hawaiian:~$ /sbin/ifconfig br0 Link encap:Ethernet HWaddr 00:1d:7d:0d:2a:9f inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21d:7dff:fe0d:2a9f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5244 errors:0 dropped:0 overruns:0 frame:0 TX packets:5619 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2243410 (2.1 MiB) TX bytes:726685 (709.6 KiB) eth0 Link encap:Ethernet HWaddr 00:1d:7d:0d:2a:9f inet6 addr: fe80::21d:7dff:fe0d:2a9f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12364 errors:0 dropped:0 overruns:0 frame:0 TX packets:13297 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7409297 (7.0 MiB) TX bytes:2040280 (1.9 MiB) Interrupt:31 Base address:0xc000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3377 errors:0 dropped:0 overruns:0 frame:0 TX packets:3377 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8275766 (7.8 MiB) TX bytes:8275766 (7.8 MiB) virbr0Link encap:Ethernet HWaddr fe:54:00:87:97:a6 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:95 errors:0 dropped:0 overruns:0 frame:0 TX packets:69 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22584 (22.0 KiB) TX bytes:16266 (15.8 KiB) vnet0 Link encap:Ethernet HWaddr fe:54:00:87:97:a6 inet6 addr: fe80::fc54:ff:fe87:97a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:95 errors:0 dropped:0 overruns:0 frame:0 TX packets:149 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:23914 (23.3 KiB) TX bytes:21043 (20.5 KiB) so the question is how did virbr0 get here, and how do I alter it to make my VM look like a normal network machine. Thanks, James On 28/08/2012, Bob Proulx b...@proulx.com wrote: James Allsopp wrote: I'm trying to learn more about networking and set up BIND, LDAP and Nagios on a KVM virtual machine. The VM works great and I can ssh into it from the host, and view the nagios pages from the host. However the VM gets the address 192.168.1.x and the host is 192.168.1.2. What number is 'x' above? Hopefully some number other than .1 or .2. auto br0 iface br0 inet static address 192.168.1.2 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.1.1 bridge_ports eth0 bridge_fd 0 bridge_hello 2 bridge_maxage 12 bridge_stp off Remove 'network' line. Remove 'broadcast' line. Let the tool calculate it from 'netmask'. That will prevent errors such as in the above where the broadcast setting is incorrect. :-) [It should have been 192.168.1.255 not 192.168.0.255.] I don't see any other problem. I do not set 'bridge_hello' nor 'bridge_maxage'. I do set 'bridge_maxwait' to 0. YMMV. I also use the resolvconf package and therefore also set dns-nameservers and dns-search but that is a separate thing. Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cad3_cnnvjmhvfkkkqrc-5byq6xgu5+kgm0vk25av7a0zczu...@mail.gmail.com
WICD
HI, I'm running wicd on debian stable and unfortunately wicd can't maintain the connection. Absolutely nothing about the rest of the wireless network has changed. It keeps oscillating through putting interface up obtaining IP addresss Done connecting not connected. When you can get a ping going, gaps of four to six packets fail for ever one that gets through. As part of writing this, I thought about taking out the other network cable (currently attached to a raspberry PI, I'm trying to bridge to) and that solved the problem, However, how to I make wicd keep the wireless connection up with the other cable inserted, would giving it a static IP help? Any ideas how I can get this wicd bridge to work? Thanks James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5032bee0.1010...@googlemail.com
Moving packets from one port to another
Hi, I'm trying to route packets from ones from one interface to another, without using NAT i.e. eth0: 192.168.1.31 (connected to rest of world and DHCP server) eth1: 192.168.1.32 (connected to other computers.) The other computers would be on the 192.168.1.0/24 subnet and hopefully be able to see all the computers on the subnet. I presume I'm going to have to make some sort of bridge, with some forwarding as with IPtables. It would be nice not to have a static IP on the other computers. Any suggestions, or discussion of the options, would be gratefully received, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/502c177a.70...@googlemail.com
Re: PS2 Keyboard not working after latest update
Ok, sorry for the delay in replying, here's what I've found out: I'm using squeeze with a 2.6.32-5-686 kernel. Adding this to the xorg.conf; Section ServerFlags Option AutoAddDevices False EndSection results in the USB mouse not working or keyboard. I've since removed this. However, problem seems to have resolved itself, Thank you very much for all your help, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff37ef1.2060...@googlemail.com
PS2 Keyboard not working after latest update
Hi, I'm really sorry to bother you all about this, but I'm really no closer to solving this problem and am having a lot of difficulties with it. Any advice or pointers on how to solve this would be greatly appreciated as at the moment I just can't use the computer. Thanks, James Hi, I'm sorry but I'm having a bit of a problem with Debian squeeze. The keyboard hardware is working as I can use it in grub but as soon as I get to GDM the keyboard does not respond. Even if I kill GDM via ssh, the keyboard doesn't respond on the terminal. I'm all up to date on upgrades and my xorg.conf is minimal; Section Screen Identifier Default Screen DefaultDepth 16 SubSection Display Depth 16 Modes 1280x1024 EndSubSection EndSection Here's my Xorg.0.log if that helps, there something about a power button but I don't know what to do about it. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 i686 Debian Current Operating System: Linux mexican 2.6.32-5-686 #1 SMP Sun May 6 04:01:19 UTC 2012 i686 Kernel command line: root=UUID=b6f5a669-9108-411f-813d-b59e9a36a80a ro Build Date: 30 October 2011 08:56:49PM xorg-server 2:1.7.7-14 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Jun 28 15:12:55 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 10de:0322:: nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xec00/16777216, 0xe000/134217728, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading
Re: PS2 Keyboard not working after latest update
Hi, Tried both of those but nothing. I have a theory that it might be a Udev problem, but can't be certain. Does anyone have any ideas why a problem like that might arise? James On 29 June 2012 04:18, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Jun 28, 2012 at 03:30:11PM +, James Allsopp wrote: Hi, I'm sorry but I'm having a bit of a problem with Debian squeeze. The keyboard hardware is working as I can use it in grub but as soon as I get to GDM the keyboard does not respond. Even if I kill GDM via ssh, the keyboard doesn't respond on the terminal. It seems not to be related to X then. I'm not running squeeze, so I'm not sure which packages have changed. but, as a suggestion, does either less /var/log/dpkg.log | grep keyboard and/or less /var/log/syslog | grep keyboard show anything of interest. Another thing to remember is that any updates to squeeze are carefully tested and if a bug crept through like that there would be soon be an uproar. Check dmesg output for *any* messages regarding your keyboard. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120629031842.GT4141@tal
PS2 Keyboard not working after latest update
Hi, I'm sorry but I'm having a bit of a problem with Debian squeeze. The keyboard hardware is working as I can use it in grub but as soon as I get to GDM the keyboard does not respond. Even if I kill GDM via ssh, the keyboard doesn't respond on the terminal. I'm all up to date on upgrades and my xorg.conf is minimal; Section Screen Identifier Default Screen DefaultDepth 16 SubSection Display Depth 16 Modes 1280x1024 EndSubSection EndSection Here's my Xorg.0.log if that helps, there something about a power button but I don't know what to do about it. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 i686 Debian Current Operating System: Linux mexican 2.6.32-5-686 #1 SMP Sun May 6 04:01:19 UTC 2012 i686 Kernel command line: root=UUID=b6f5a669-9108-411f-813d-b59e9a36a80a ro Build Date: 30 October 2011 08:56:49PM xorg-server 2:1.7.7-14 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Jun 28 15:12:55 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 10de:0322:: nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xec00/16777216, 0xe000/134217728, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (==) Matched nouveau as autoconfigured driver 0 (==) Matched nv as autoconfigured driver 1 (==)
Re: Unable to get X to start on new flat screen monitor using DVI
Hi, That's really odd about the kernel. The computer was working fine on an old CRT via VGA, and I just plugged my new flat screen in via dvi-d, and you can see start up, but X doesn't start. I'm upgrading to the 2.6.32-686 kernel, will that be new enough? Thanks James On 19 June 2012 20:16, Sven Joachim svenj...@gmx.de wrote: On 2012-06-19 01:19 +0200, Brian wrote: On Mon 18 Jun 2012 at 23:21:03 +, James Allsopp wrote: [drm] failed to load kernel module nouveau (EE) [drm] failed to open device http://nouveau.freedesktop.org/wiki/TroubleShooting and also look at what is happening with nouveau in the output of the 'dmesg' command. That question is easy to answer, the nouveau module does not exist because James is running an obsolete 2.6.30 kernel. Upgrading to the Squeeze kernel should rectify this. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bokfgljj@turtle.gmx.de
Re: Unable to get X to start on new flat screen monitor using DVI
Brilliant, updated the kernel and everything seems fixed now! Thanks very much! James On 20 June 2012 08:18, James Allsopp jamesaalls...@googlemail.com wrote: Hi, That's really odd about the kernel. The computer was working fine on an old CRT via VGA, and I just plugged my new flat screen in via dvi-d, and you can see start up, but X doesn't start. I'm upgrading to the 2.6.32-686 kernel, will that be new enough? Thanks James On 19 June 2012 20:16, Sven Joachim svenj...@gmx.de wrote: On 2012-06-19 01:19 +0200, Brian wrote: On Mon 18 Jun 2012 at 23:21:03 +, James Allsopp wrote: [drm] failed to load kernel module nouveau (EE) [drm] failed to open device http://nouveau.freedesktop.org/wiki/TroubleShooting and also look at what is happening with nouveau in the output of the 'dmesg' command. That question is easy to answer, the nouveau module does not exist because James is running an obsolete 2.6.30 kernel. Upgrading to the Squeeze kernel should rectify this. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bokfgljj@turtle.gmx.de
Re: Unable to get X to start on new flat screen monitor using DVI
/modules/libvbe.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. On 17/06/12 22:47, Brian wrote: On Sun 17 Jun 2012 at 22:29:04 +, James Allsopp wrote: Hi, Got one of my old PC's lying around and I'm trying to get it to work with my nice new LG IPS225V flatscreen. It used to work fine with my CRT over VGA but although I can get a console up, I can't get X to start. I've listed the Xorg log out at the bottom of the e-mail I think it could be that the monitor is refusing anything other than 1900x1080 at 60Hz over which DVI, which my hardware hasn't a hope of driving. There doesn't appear to be any way of turning this down on the monitor. To get some idea of the hardware, this is the lspci [Most of lspci ouput, apart from one line, snipped] 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) You'll like this! On one of my machines: brian@dektop3:~$ lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1) You can compare mine with yours: brian@dektop3:~$ xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096 VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x1024 63.2*+ 1024x768 60.0 800x60060.3 56.2 848x48060.0 640x48059.9 VGA-2 disconnected (normal left inverted right x axis y axis) TV-1 disconnected (normal left inverted right x axis y axis) If I was in your situation and was after 1280x1024 I'd put this in an /etc/X11/xorg.conf: Section Screen IdentifierDefault Screen DefaultDepth 16 SubSection Display Depth 16 Modes 1280x1024 EndSubSection EndSection -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fdfb7df.3000...@googlemail.com
Unable to get X to start on new flat screen monitor using DVI
Hi, Got one of my old PC's lying around and I'm trying to get it to work with my nice new LG IPS225V flatscreen. It used to work fine with my CRT over VGA but although I can get a console up, I can't get X to start. I've listed the Xorg log out at the bottom of the e-mail I think it could be that the monitor is refusing anything other than 1900x1080 at 60Hz over which DVI, which my hardware hasn't a hope of driving. There doesn't appear to be any way of turning this down on the monitor. To get some idea of the hardware, this is the lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:09.0 Network controller: RaLink RT2561/RT61 802.11g PCI 00:0a.0 Multimedia audio controller: Ensoniq 5880B [AudioPCI] (rev 02) 00:0b.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) Thanks for any help, James X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 i686 Debian Current Operating System: Linux mexican 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i686 Kernel command line: root=UUID=b6f5a669-9108-411f-813d-b59e9a36a80a ro Build Date: 30 October 2011 08:56:49PM xorg-server 2:1.7.7-14 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 17 22:13:40 2012 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 10de:0322:: nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xec00/16777216, 0xe000/134217728, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.13.0
Installing packages from Wheezy in Squeeze
Hello, Is there an easy way of installing a package (namely virtinst) from Wheezy in Squeeze? I've tried variations of aptitude install -t wheezy virtinst and aptitude install virtinst/wheezy but with no joy, It goes through the start process but says there's nothing to update or upgrade Thanks, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa02008.9060...@googlemail.com
Anyway of keeping gnome2 while upgrading from Squeeze to Wheezy
Hello, I want to update from Squeeze to Wheezy but want to avoid Gnome 3 at all costs, is there a way of doing this successfully? Thanks James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f99bb0e.8000...@googlemail.com
Differences between using KVM and virt-install?
Hi, I was trying for ages to build a KVM virtual machine using virt-install and it always failed, tried KVM command directly following Gentoo instruction and got it to work first time. Is there any difference in the end result between these two methods? Thanks, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7309e2.8000...@googlemail.com
VNC into a Debian Machine
Hello, I really want to be able to use VNC to be able to view the full Gnome desktop on my laptop. I've been able to view a grey screen and a terminal, using vnc4server and tigervnc or vinagre, but what I'd like to be able to do is just view a whole screen as if I was actually there. I'd like avoid xdmcp if possible, as it would be great to use it from anywhere, rather than just locally, Any suggestions, pointers to good tutorials welcome! Thanks James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f283e1e.6050...@googlemail.com
KVM virtualisation
Hi, I'm having trouble building a kvm virtual machine, The script I'm using to build this is: #!/bin/bash virt-install \ --connect qemu:///system \ -n deb1 \ -r 512 \ --vcpus=1 \ --os-variant=debiansqueeze \ --accelerate \ -v \ -c /var/lib/libvirt/images/debian-6.0.3-amd64-netinst.iso \ -w bridge:br0 \ --vnc \ --disk path=/var/lib/libvirt/images/debiantest.img,size=4 but when I run I get the following error, I've tried to debug this afterwards; awaiian:/home/ja/vm_kvm# ./kvmInstall Starting install... Allocating 'debiantest.img' | 4.0 GB 00:00 Creating domain... |0 B 00:00 Cannot open display: Run 'virt-viewer --help' to see a full list of available command line options Domain installation does not appear to have been successful. If it was, you can restart your domain by running 'virsh start deb1'; otherwise, please restart your installation. Hawaiian:/home/ja/vm_kvm# virsh start deb1 error: failed to get domain 'deb1' error: Unknown failure Hawaiian:/home/ja/vm_kvm# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # nodeinfo CPU model: x86_64 CPU(s): 2 CPU frequency: 2000 MHz CPU socket(s): 1 Core(s) per socket: 2 Thread(s) per core: 1 NUMA cell(s):1 Memory size: 4061292 kB virsh # list --al error: command 'list' doesn't support option --al virsh # list --all Id Name State -- virsh # net-list --all Name State Autostart - vboxnet0 inactive no autostart virsh # net-edit default error: failed to get network 'default' error: Unknown failure virsh # quit Hawaiian:/home/ja/vm_kvm# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # net-autostart default error: failed to get network 'default' error: Unknown failure If anyone can offer me any help on how to fix this I'd be really grateful, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2062b3.8030...@googlemail.com
Trying to build a virtual machine
Hello, I'm trying to build a virtual machine using the following command, ja@Hawaiian:~$ virt-install --connect qemu:///system -n vm10 -r 512 --vcpus=2 --disk path=/var/lib/libvirt/images/vm10.img,size=4 -c /var/lib/libvirt/images/debian-6.0.3-amd64-netinst.iso --vnc --noautoconsole --os-type linux --os-variant debiansqueeze --accelerate --network=bridge:br0 --hvm Starting install... Allocating 'vm10.img'| 4.0 GB 00:00 Creating domain... |0 B 00:00 but it hangs here, does anyone have any advice on how to fix this, or what to check, Thanks James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cad3_cno2kvyuayhhbhpsu4f-ti9idm8iwt5xnn8efcd6grz...@mail.gmail.com
Re: Nvidia drivers
Hi, Found the problem, forgotten to install the nvidia-kernel-dkms package. Very happy all work great now and all of the CUDA stuff I installed also works! Thanks for your comments, Jim On 12/09/11 14:05, James Allsopp wrote: Hi, Having a terrible time trying to get nvidia drivers working. I had them working ages ago but an update broke them whilst I was trying to get CUDA to work. I'm trying to do this properly the nvidia way, and have tried to remove all of the packages using apt, and them used m-a prepare m-a auto-install nvidia and everything went to plan, but when I reboot X fails saying it can't find the modules. ja@Hawaiian:~$ uname -a Linux Hawaiian 2.6.30-2-amd64 #1 SMP Mon Dec 7 05:21:45 UTC 2009 x86_64 GNU/Linux Hawaiian:/home/ja# find / -iname 'nvidia.ko' /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko lsmod shows an nvidia module Hawaiian:/home/ja# lsmod | grep nvidia nvidia 10852808 0 i2c_core 25424 2 i2c_i801,nvidia But it doesn't seem the same size as the other two, which are different from each other. Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko -rw-r--r-- 1 root root 13294487 Sep 12 12:40 /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko -rw-r--r-- 1 root root 11670161 Jan 12 2010 /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko Not exactly sure where to go from here, any advice or requests for more information gratefully received. Thanks, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6f5813.1000...@googlemail.com
Creating a debian virtual machine for Nagios
Hi, I'm trying to create a debian virtual machine to run Nagios on using the following command. virt-install --connect qemu:///system -n nagios -r 2048 --os-type=linux --disk /var/lib/libvirt/images/nagios.img,device=disk,bus=virtio,size=5,sparse=true,format=raw -w bridge=br0,model=virtio --vnc --noautoconsole -c /home/ja/isos/debian-6.0.2.1-amd64-netinst.iso but it hangs and I get the following errors in the log Sep 13 12:44:45 Hawaiian kernel: [44156.897947] libvirtd[2479]: segfault at 7f1381004bdf ip 00419363 sp 7f137b9b0230 error 7 in libvirtd[40+dc000] Sep 13 12:47:55 Hawaiian libvirtd: 12:47:55.860: warning : qemudStartup:1832 : Unable to create cgroup for driver: No such device or address Sep 13 12:47:55 Hawaiian libvirtd: 12:47:55.943: warning : lxcStartup:1900 : Unable to create cgroup for driver: No such device or address Sep 13 12:50:21 Hawaiian libvirtd: 12:50:21.005: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed Sep 13 12:50:21 Hawaiian libvirtd: 12:50:21.475: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed Sep 13 12:50:21 Hawaiian libvirtd: 12:50:21.575: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed Sep 13 12:50:21 Hawaiian libvirtd: 12:50:21.847: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed Sep 13 12:54:44 Hawaiian libvirtd: 12:54:44.000: warning : virEventUpdateHandleImpl:150 : Ignoring invalid update watch -1 and when I press ctrl-C I get this error, ja@Hawaiian:~/VMscripts$ ./nagios Starting install... Allocating 'nagios.img' | 5.0 GB 00:00 Creating domain... |0 B 00:00 ^CERRORpoll on socket failed: Interrupted system call Traceback (most recent call last): File /usr/bin/virt-install, line 975, in do_install ret, state = check_domain_state() File /usr/bin/virt-install, line 961, in check_domain_state dominfo = dom.info() File /usr/lib/python2.6/dist-packages/libvirt.py, line 766, in info if ret is None: raise libvirtError ('virDomainGetInfo() failed', dom=self) libvirtError: poll on socket failed: Interrupted system call Guest installation complete... restarting guest. ^CERRORpoll on socket failed: Interrupted system call Domain installation does not appear to have been successful. If it was, you can restart your domain by running 'virsh start nagios'; otherwise, please restart your installation. ERRORpoll on socket failed: Interrupted system call Traceback (most recent call last): File /usr/bin/virt-install, line 1033, in module main() File /usr/bin/virt-install, line 935, in main dom.create() File /usr/lib/python2.6/dist-packages/libvirt.py, line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: poll on socket failed: Interrupted system call Does anyone have any ideas on how to solve this? Best regards James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6f58ec.9050...@googlemail.com
Nvidia drivers
Hi, Having a terrible time trying to get nvidia drivers working. I had them working ages ago but an update broke them whilst I was trying to get CUDA to work. I'm trying to do this properly the nvidia way, and have tried to remove all of the packages using apt, and them used m-a prepare m-a auto-install nvidia and everything went to plan, but when I reboot X fails saying it can't find the modules. ja@Hawaiian:~$ uname -a Linux Hawaiian 2.6.30-2-amd64 #1 SMP Mon Dec 7 05:21:45 UTC 2009 x86_64 GNU/Linux Hawaiian:/home/ja# find / -iname 'nvidia.ko' /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko lsmod shows an nvidia module Hawaiian:/home/ja# lsmod | grep nvidia nvidia 10852808 0 i2c_core 25424 2 i2c_i801,nvidia But it doesn't seem the same size as the other two, which are different from each other. Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko -rw-r--r-- 1 root root 13294487 Sep 12 12:40 /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko -rw-r--r-- 1 root root 11670161 Jan 12 2010 /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko Not exactly sure where to go from here, any advice or requests for more information gratefully received. Thanks, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e0387.5080...@googlemail.com
Re: Nvidia drivers
Hi, problem is that I can't get x to start now and need some help, any ideas? On Sep 12, 2011 1:58 PM, Jerome BENOIT g62993...@rezozer.net wrote: Hello List: have your tried the Debian instead: http://packages.debian.org/source/wheezy/nvidia-graphics-drivers http://packages.debian.org/wheezy/nvidia-cuda-dev hth, Jerome On 12/09/11 15:05, James Allsopp wrote: Hi, Having a terrible time trying to get nvidia drivers working. I had them working ages ago but an update broke them whilst I was trying to get CUDA to work. I'm trying to do this properly the nvidia way, and have tried to remove all of the packages using apt, and them used m-a prepare m-a auto-install nvidia and everything went to plan, but when I reboot X fails saying it can't find the modules. ja@Hawaiian:~$ uname -a Linux Hawaiian 2.6.30-2-amd64 #1 SMP Mon Dec 7 05:21:45 UTC 2009 x86_64 GNU/Linux Hawaiian:/home/ja# find / -iname 'nvidia.ko' /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko lsmod shows an nvidia module Hawaiian:/home/ja# lsmod | grep nvidia nvidia 10852808 0 i2c_core 25424 2 i2c_i801,nvidia But it doesn't seem the same size as the other two, which are different from each other. Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko -rw-r--r-- 1 root root 13294487 Sep 12 12:40 /lib/modules/2.6.30-2-amd64/nvidia/nvidia.ko Hawaiian:/home/ja# ls -l /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko -rw-r--r-- 1 root root 11670161 Jan 12 2010 /lib/modules/2.6.30-2-amd64/kernel/drivers/video/nvidia.ko Not exactly sure where to go from here, any advice or requests for more information gratefully received. Thanks, James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e01db.7090...@rezozer.net
Re: Nvidia drivers
Hi, Not really sure how I should move from here. I want the proprietary nvidia drivers as I want to have compiz and use CUDA, so if someone can point me in the direction of the best way to achieve this I would be very grateful. Also I find the whole kernel situation in Debian quite confusing as opposed to Gentoo (my other system) where you just install you're own kernel, compile it and then install the modules. Any advice on recommended documents I should be reading? Thanks, James On 15/04/11 08:06, David Baron wrote: On Friday 15 April 2011 09:41:19 debian-user-digest-requ...@lists.debian.org wrote: Version mismatch detected between the NVIDIA libGL.so and libGLcore.so shared libraries (libGL.so version: 190.53; libGLcore.so version: 195.36.31). Please try reinstalling the NVIDIA driver. Any suggestions? Make sure the version of nvidia-glx, libgl1-nvidia-glx, and nvidia-kernel are all the same. 190.xx.yy isn't compatible with 195.xx.yy. I don't actually see a 190.xx.yy packaged for Debian; did you use the installer from NVidia? If so, you might need to clean that up. The packages from NVidia aren't compatible with Debian packaging. -- Nvidia's proprietary installation places their own libGL.so stuff. Upgrading xorg from Debian will overwrite them so you need to either recompile them or use dpkg-divert to prevent overwriting. Debian's nvidia packages do not have the same versions except for certain legacy drivers. They also place their modules differently. So either find the appropriate Debian ones (I have 260 and I do not know which Debian version to use!) or reinstall nvidia's version completely. Their installation works first time, every time. Then use dpkg-divert to keep it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac1286.1030...@googlemail.com
Re: Nvidia drivers
I get this happening Hawaiian:/home/ja# aptitude install nvidia-kernel-dkms No packages will be installed, upgraded, or removed. so not really sure where to go from here. Jim On 18/04/11 11:43, Erwan David wrote: On Mon, Apr 18, 2011 at 12:29:26PM CEST, James Allsopp jamesaalls...@googlemail.com said: Hi, Not really sure how I should move from here. I want the proprietary nvidia drivers as I want to have compiz and use CUDA, so if someone can point me in the direction of the best way to achieve this I would be very grateful. Also I find the whole kernel situation in Debian quite confusing as opposed to Gentoo (my other system) where you just install you're own kernel, compile it and then install the modules. Any advice on recommended documents I should be reading? Thanks, James Did you try the nvidia-kernel-dkms package ? It will compile and install the nvidia driver against installed kernels and reinstall it when you upgrade kernel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac178b.6090...@googlemail.com
Re: Nvidia drivers
Hi, My source.list has the following; deb http://ftp.uk.debian.org/debian/ stable main non-free contrib deb-src http://ftp.uk.debian.org/debian/ stable main non-free contrib deb http://security.debian.org/ stable/updates main contrib non-free deb-src http://security.debian.org/ stable/updates main contrib non-free but I'm not sure what you mean about reloading? Best regards James On 18/04/11 12:35, Brad Rogers wrote: On Mon, 18 Apr 2011 11:50:51 +0100 James Allsopp jamesaalls...@googlemail.com wrote: Hello James, I get this happening Hawaiian:/home/ja# aptitude install nvidia-kernel-dkms No packages will be installed, upgraded, or removed. Looks as though you haven't got non-free included. Add that, reload and try again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac237a.2050...@googlemail.com
Re: Nvidia drivers
Done, that and still get the same error; full output is Hawaiian:/home/ja# aptitude install nvidia-kernel-dkms No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. W: Did not understand pin type * I think the pin type error is where I tried to force grub to not upgrade to grub2, Thanks, Jim On 18/04/11 13:56, Erwan David wrote: On Mon, Apr 18, 2011 at 01:41:46PM CEST, James Allsopp jamesaalls...@googlemail.com said: Hi, My source.list has the following; deb http://ftp.uk.debian.org/debian/ stable main non-free contrib deb-src http://ftp.uk.debian.org/debian/ stable main non-free contrib deb http://security.debian.org/ stable/updates main contrib non-free deb-src http://security.debian.org/ stable/updates main contrib non-free but I'm not sure what you mean about reloading? Add non-free at the first two lines, then do an aptitude update. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac3eec.2050...@googlemail.com
Re: Nvidia drivers
Hi, I've recently after Squeeze went stable, changed my sources.list from having the keyword testing to stable. I've tried apt-get install --reinstall libgl1-nvidia-glx apt-get install --reinstall nvidia-kernel-dkms which reinstalled those files but I think that there may be a linking problem in Hawaiian:/home/ja# ls -l /usr/lib/libGLc* lrwxrwxrwx 1 root root 22 Apr 18 15:38 /usr/lib/libGLcore.so.1 - libGLcore.so.195.36.31 -rwxr-xr-x 1 root root 20713400 Jan 12 2010 /usr/lib/libGLcore.so.190.53 -rw-r--r-- 1 root root 28862968 Jun 3 2010 /usr/lib/libGLcore.so.195.36.31 Again any advice, and I'd be very grateful, Best regards James On 19/04/11 02:16, Vivek Periaraj wrote: On Mon, 18 Apr 2011, James Allsopp wrote: On 18/04/11 13:56, Erwan David wrote: On Mon, Apr 18, 2011 at 01:41:46PM CEST, James Allsopp jamesaalls...@googlemail.com said: Hi, My source.list has the following; deb http://ftp.uk.debian.org/debian/ stable main non-free contrib deb-src http://ftp.uk.debian.org/debian/ stable main non-free contrib Done, that and still get the same error; full output is Hawaiian:/home/ja# aptitude install nvidia-kernel-dkms No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. W: Did not understand pin type * For me, nvidia-kernel-dkms is in testing and above and not in stable. Here's the output: $ apt-cache policy nvidia-kernel-dkms nvidia-kernel-dkms: Installed: (none) Candidate: 260.19.44-1 Version table: 270.30-1 0 200 http://ftp.us.debian.org/debian/ experimental/non-free i386 Packages 260.19.44-1 0 400 http://ftp.us.debian.org/debian/ testing/non-free i386 Packages 300 http://ftp.us.debian.org/debian/ unstable/non-free i386 Packages So I would suggest adding testing to your repos. I have this: deb http://ftp.us.debian.org/debian testing main contrib non-free Regards, V. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac6690.20...@googlemail.com
Nvidia drivers
Hi, I'm having trouble with my Nvidia drivers, glxinfo gives me the following error. I'm not sure how this happened, during an update I presume. The problem is that I don't seem to be able to update the nvidia-glx package. Version mismatch detected between the NVIDIA libGL.so and libGLcore.so shared libraries (libGL.so version: 190.53; libGLcore.so version: 195.36.31). Please try reinstalling the NVIDIA driver. Any suggestions? Thanks, Jim
Installing Joomla on Debian
Hi, I want to install Joomla 1.6 on Debian, but am wondering why most instructions on the internet include Xampp. I don't think I need this as I already have apache2, mysql and php5 installed. If I installed xampp, would this cause conflicts with the existing installed software? Any help or pointers greatly appreciated, Jim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d94f6e7.9060...@googlemail.com
Re: Unable to print from Windows Vista Laptop via Samba
Hi, Unfortunately, samba doesn't seem to be picking up any changes to my smb.conf even after a restart. Compare the printer related output from testparm [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers to that from the smb.conf file [printers] comment = All Printers browseable = yes path = /var/spool/samba printable = yes guest ok = yes read only = yes writeable = no create mask = 0700 use client driver = yes # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no So I think my problem is that it's not picking up the settings, any more advice would be greatly appreciated, Best regards Jim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5e4a13.1060...@googlemail.com
Re: Unable to print from Windows Vista Laptop via Samba
Hi, Not sure really what you mean about the first point, where should I put that in, but smbclient -L server shows the printer, it's shown on /etc/printcap and if I set windows to print to \\192.168.1.2\printer name I get a test page fine. Not sure if this last one bypasses Samba. What I can't do is get the printer to show up when you browse for it. I think the problem is with Samba as testparm doesn't seem to reflect some of the changes I make. Thanks, Jim On 16/02/11 13:34, Pablo Sánchez wrote: James, do you see through smb (\\server-computer) the printers share ? If you do, can you see the printer listed ? (Camaleón somehow asked you the same question) . Try running # smbclient -L server-computer to see all shares listed by the server . Check if your printer is listed on /etc/printcap . Last resort, install swat and point your browser to http://server-computer:901 to see what shows up . Pablo Thanks Pablo, I'll try that if I can't get it to work through samba. Problem seems to be with the config file not picking up the printing declaration. I have restarted samba after editting the file. Testparm gives me the following [global] workgroup = ETHICSGRADIENT server string = %h server interfaces = lo, eth0 obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes syslog = 0 log file = /var/log/samba/log.%m printcap name = cups dns proxy = No wins support = Yes panic action = /usr/share/samba/panic-action %d [homes] comment = Home Directories valid users = %S create mask = 0700 directory mask = 0700 browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers but if you actually look at the config file; Hawaiian:/etc/samba# grep = smb.conf | grep -v \# | grep -v \; workgroup = EthicsGradient server string = %h server wins support = yes dns proxy = no interfaces = lo eth0 log file = /var/log/samba/log.%m max log size = 5000 syslog = 0 panic action = /usr/share/samba/panic-action %d security = user encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes load printers = yes printing = cups printcap name = cups comment = Home Directories browseable = no read only = yes create mask = 0700 directory mask = 0700 valid users = %S comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = yes read only = yes writeable = no create mask = 0700 useclient driver = yes comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no printing and load printers are clearly defined. Bit confused so could do with some advice on this? Thanks, Jim 2011/2/15 Pablo Sánchez pab...@adinet.com.uy mailto:pab...@adinet.com.uy James, i usually use ipp (internet printing protocol) to print on cups from windows , skipping samba alltogether. Just map the printer over http://printerhost:631/printers/PrinterName . Bear in mind that you can create a raw print spool , o have the real driver of the printer. In the first case you install the driver printer on your pc an then install the printer over http. Remember to share the printer on cups. Regards. Pablo Hi, I have a debian server running samba connected to a local USB printer. I also have a dual boot laptop with windows Vista on it. I can print fine from the server and the linux side of the laptop using CUPS, and even though I can see my home directory via samba in Vista, I can't get it to detect any printers. Vista is on the same Workgroup, I've lowered the firewall, but still windows won't detect it. An Nmap from the laptop shows ports 22,25,80,111,139,445,631 and 2049(all tcp) open. My Samba config is at the bottom, any advice would be greatly appreciated. Thanks, Jim [global] workgroup = ETHICSGRADIENT server string = %h server interfaces = lo, eth0 obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u
Re: Unable to print from Windows Vista Laptop via Samba
Thanks Pablo, I'll try that if I can't get it to work through samba. Problem seems to be with the config file not picking up the printing declaration. I have restarted samba after editting the file. Testparm gives me the following [global] workgroup = ETHICSGRADIENT server string = %h server interfaces = lo, eth0 obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes syslog = 0 log file = /var/log/samba/log.%m printcap name = cups dns proxy = No wins support = Yes panic action = /usr/share/samba/panic-action %d [homes] comment = Home Directories valid users = %S create mask = 0700 directory mask = 0700 browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers but if you actually look at the config file; Hawaiian:/etc/samba# grep = smb.conf | grep -v \# | grep -v \; workgroup = EthicsGradient server string = %h server wins support = yes dns proxy = no interfaces = lo eth0 log file = /var/log/samba/log.%m max log size = 5000 syslog = 0 panic action = /usr/share/samba/panic-action %d security = user encrypt passwords = true passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes load printers = yes printing = cups printcap name = cups comment = Home Directories browseable = no read only = yes create mask = 0700 directory mask = 0700 valid users = %S comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = yes read only = yes writeable = no create mask = 0700 useclient driver = yes comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no printing and load printers are clearly defined. Bit confused so could do with some advice on this? Thanks, Jim 2011/2/15 Pablo Sánchez pab...@adinet.com.uy James, i usually use ipp (internet printing protocol) to print on cups from windows , skipping samba alltogether. Just map the printer over http://printerhost:631/printers/PrinterName . Bear in mind that you can create a raw print spool , o have the real driver of the printer. In the first case you install the driver printer on your pc an then install the printer over http. Remember to share the printer on cups. Regards. Pablo Hi, I have a debian server running samba connected to a local USB printer. I also have a dual boot laptop with windows Vista on it. I can print fine from the server and the linux side of the laptop using CUPS, and even though I can see my home directory via samba in Vista, I can't get it to detect any printers. Vista is on the same Workgroup, I've lowered the firewall, but still windows won't detect it. An Nmap from the laptop shows ports 22,25,80,111,139,445,631 and 2049(all tcp) open. My Samba config is at the bottom, any advice would be greatly appreciated. Thanks, Jim [global] workgroup = ETHICSGRADIENT server string = %h server interfaces = lo, eth0 obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes syslog = 0 log file = /var/log/samba/log.%m printcap name = cups dns proxy = No wins support = Yes panic action = /usr/share/samba/panic-action %d [homes] comment = Home Directories valid users = %S create mask = 0700 directory mask = 0700 browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d59c501.1080...@adinet.com.uy