Re: Re: problem with display breaking up
What is the video hardware in the system? There may be useful bug information. Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/5598b3d6.8070...@orcon.net.nz
Jessie - running smoothly at last - nouveau driver
Yesterday, I was ready to quit my experience of Jessie (8.1) and return to Wheezy (7.8). After a number of problems encountered and fixed, there was only the video which would occasionally and irregularly crash the system leaving a screen full of tearing. This never happened with Wheezy. The only way out was reboot or power-off. My system has on-board MCP61 nVidia with the ethernet using forcedeth driver and the video (C61 [GeForce 7025/nForce 630a]) using nouveau driver. The solution, probably not ideal but it works until an updated nouveau, is to turn off hardware assisted acceleration. So if anyone else has a similar system and similar problem, try creating a /etc/modprobe.d/nouveau.conf file, containing: options nouveau noaccel=1 Solution found in Debian bug 758460 (after much searching). Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/55986f52.3000...@orcon.net.nz
[SOLVED] Re: forcedeth driver - bug?
Thanks Selim, that fixed it. I had tried that months ago on the Wheezy installation I run, but it did not work then - probably I did not update the module dependencies or the initramfs at that time! I had not realised the importance of the 'options' keyword, having seen few examples of it :-( On Fri, Jun 19, 2015 at 09:06:30AM +1200, Bruce Ward wrote: > >An entry "options forcedeth ms=0 msix=0" in some /etc/modprobe.d/foo.conf >should do thr trick, no? > >Of course, perhaps you tried that already and I'm mis-interpreting >your question completely. Apologies if that's the case. No I have not (yet) tried everything! There may be something in a modprobe.d/foo.conf that could work. I have tried putting the line forcedeth msi=0 msix=0 When you make the foo.conf, don't leave "options" out. into /etc/modules as appeared to work for this Ubuntu user http://ubuntuforums.org/archive/index.php/t-1982856.html but that didn't work for me. He did try > a forcedeth.conf file to /etc/modprobe.d with the following contents: > >options forcedeth msi=0 msix=0 ^^^ Should be like this. Yes, solution is /etc/modprobe.d/forcedeth.conf containing options forcedeth msi=0 msix=0 Thank you, Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/558378f1.6080...@orcon.net.nz
Re: Re: forcedeth driver - bug?
Hi Tomas On Thu, Jun 18, 2015 at 11:12:49PM +1200, Bruce Ward wrote: Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This has "Giga PHY RTL8211CL" ethernet, which lspci reports as: "00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)" It uses the forcedeth driver module, which seems to need parameters "msi=0 msix=0" to work. If I blacklist the driver, I can load it with "modprobe forcedeth msi=0 msix=0" and all is fine. However, it needs this after every reboot and I have not found a way to successfully load the module automatically. Loaded automatically it a) cannot connect to the network, and b) locks the system solid if I try to unload it! Is there some way over this problem or is this a bug? If a bug, who should know about it? Perhaps I'm not reading your mail correctly, but isn't that in the realm of the modprobe.d configs? - From the modprobe.d manpage: NAME modprobe.d - Configuration directory for modprobe SYNOPSIS /usr/lib/modprobe.d/*.conf /etc/modprobe.d/*.conf /run/modprobe.d/*.conf DESCRIPTION [...] COMMANDS [...] options modulename option... This command allows you to add options to the module modulename (which might be an alias) every time it is inserted into the kernel: whether directly (using modprobe modulename or because the module being inserted depends on this module. All options are added together: they can come from an option for the module itself, for an alias, and on the command line. An entry "options forcedeth ms=0 msix=0" in some /etc/modprobe.d/foo.conf should do thr trick, no? Of course, perhaps you tried that already and I'm mis-interpreting your question completely. Apologies if that's the case. - -- t No I have not (yet) tried everything! There may be something in a modprobe.d/foo.conf that could work. I have tried putting the line forcedeth msi=0 msix=0 into /etc/modules as appeared to work for this Ubuntu user http://ubuntuforums.org/archive/index.php/t-1982856.html but that didn't work for me. He did try a forcedeth.conf file to /etc/modprobe.d with the following contents: options forcedeth msi=0 msix=0 But that doesn't do anything. Regards, Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/558332d6.5000...@orcon.net.nz
forcedeth driver - bug?
Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This has "Giga PHY RTL8211CL" ethernet, which lspci reports as: "00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)" It uses the forcedeth driver module, which seems to need parameters "msi=0 msix=0" to work. If I blacklist the driver, I can load it with "modprobe forcedeth msi=0 msix=0" and all is fine. However, it needs this after every reboot and I have not found a way to successfully load the module automatically. Loaded automatically it a) cannot connect to the network, and b) locks the system solid if I try to unload it! Is there some way over this problem or is this a bug? If a bug, who should know about it? Note: the same behaviour in my Wheezy (not surprising when it is the same version of driver module), but I had hoped it would be fixed in Jessie. Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/5582a7b1.5020...@orcon.net.nz
Re: Jessie failed installation woes - they continue!
Installation was on second drive, and grub was installed to the MBR of that drive. Restart dropped me into grub rescue mode with the message about normal.mod not being found. After mounting the drive in Wheezy, I find that the directory that normal.mod is supposed to be in, is not there. There are only 2 files in /boot/grub - vastly different from the grub 1.99 of Wheezy! Try booting from a live CD/USB stick, entering your new installation in a chroot and running update-grub and grub-install /dev/. I had a lot of similar problems (see recent posts on this list) and ended up installing lilo instead of grub. The config is much simpler than grub2. I have found the upgrade to jessie a painful process - the main issues being the change to systemd, grub2 and config changes required in the new Apache. I've almost got everything running properly now. Thanks for reminding me of chroot - that appears to have got grub installed. Problem now, is the boot process hangs after the fsck declares the partition clean ... And that is not far into booting! Bother. Now to go looking for other reported similar failures ... Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/557f91c8.7050...@orcon.net.nz
Jessie failed installation woes
I'm a long-time Debian user and this system (Wheezy) is result of at least 3 dist-upgrades (as well as motherboard upgrades). Last dist-upgrade was not completely successful, so I thought to do a new install of Jessie, onto a second hard drive. Since the current motherboard is AMD FX 64bit capable I tried a couple of AMD64 Live CDs as tasters, since I had some trouble getting the onboard ethernet going in Wheezy i686. Live CDs find the MPC61 ethernet and get me onto the network. Install DVDs find the MCP61 ethernet BUT can't get onto network. After deciding to not configure the network, installation continued until the reboot at the end - that hung the machine. Installation was on second drive, and grub was installed to the MBR of that drive. Restart dropped me into grub rescue mode with the message about normal.mod not being found. After mounting the drive in Wheezy, I find that the directory that normal.mod is supposed to be in, is not there. There are only 2 files in /boot/grub - vastly different from the grub 1.99 of Wheezy! Note that I mentioned 'Install DVDs' above. I gave up on the AMD64 and tried i686 flavour - same problem! I have copied all files from the missing directory (found on install CD & renamed the directory), and now trying to boot from that disc reboots the machine! I am thankful I kept the Jessie install away from the working Wheezy! What can I do now? Bruce -- === Bruce Ward, Nelson, New Zealand -- 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/557cb186.5030...@orcon.net.nz
PDF forms and field issues
I created (LibreOffice) a PDF document with user-entry fields. Sent it to a friend with a Mac to check that it worked. He filled in fields and returned it to me saying it worked fine. There is a problem in that the fields appear blank (except for the one checkbox). Having now tried a number of PDF 'viewers' on the document, I can report: Evince (Gnome 'Document Viewer') - fields are blank until you click in the field. Click to another field and the first goes blank. xpdf - fields are blank GIMP - fields are blank (not surprised) Inkscape - fields are blank (not surprising) LibreOffice with pdfimport - fields are blank imagemagick - shows fields properly!!! Evince, GIMP, and xpdf when run from command-line all give Error: Unknown font in field's DA string Any ideas on work-around? Bruce -- ======= Bruce Ward, Nelson, New Zealand -- 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/54cbee8e.3020...@orcon.net.nz
Latest update was bad news for me!
I've got an ASRock motherboard with AMD AM3 CPU and "Giga PHY RTL8211CL" ethernet, running Wheezy. Had no joy getting the network port running (forcedeth module would kill the whole system as soon as tried to use or even unload it!), so I used an old (faithful) DEC Tulip card (de2104x module). And so it ran for months (or a year or more, through a number of linux updates) without problems. Last week I happened to find a reference in an Ubuntu forum to successfully getting the RTL8211 working - after consultation with ASRock. It involved removing the forcedeth module and reinstalling it with certain parameters. So I tried it, and it worked (without killing the system!); I put the necessary fix in a file in /etc/modprobe.d, and that I used until this morning. I presumably had rebooted in that time to test the fix. This morning the latest Linux security update (DSA3128) arrived and I installed that. It involved a restart, after which I had no network connection - not even with the Tulip card. In fact I was back to rmmod forcedeth killing the system (with a familiar pattern on screen - but locked SOLID). No, I have not been able to get the Tulip working in Wheezy, but I know it is not dead - Puppy Linux (tahr) gets it going just fine (but has other problems apparently from the RTL8211 which it can't connect to the network). After some hours of frustration, I have got the RTL8211 working in Wheezy, but it seems to involve manual loading of the forcedeth driver after every restart. One thing to take from this - ASRock, AMD AM3, and Linux don't play well together. Another is that today's de2104x module doesn't work my card. /vent Bruce Ward -- 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/22678.60.234.158.211.1421400550.squir...@mail.orcon.net.nz
Webcam and GSPCA problem with new kernel partly solved
I am running Lenny and have a Logitech webcam which uses the gspca driver modules. Running the standard (for Lenny) 2.6.26 kernel, I added gspca-modules-2.6.26-2-686 and all is well. Camera is detected as v4l, and cheese works, even producing video with synchronised audio. Because later kernels have gspca modules in kernel, I installed the 2.6.32-bpo.5-686 from lenny-backports. Result - webcam does not work with cheese except for showing the test pattern as seen in gstreamer-properties with test input. When cheese is started, the light on the camera blinks on twice and then stays off - it should be on all the time. The gspca_main and gspca_zc3xx modules are loaded as is v4l1_compat. But it doesn't work! I have now installed libv4l-0 from lenny-backports and used LD_PRELOAD to install the v4l1compat.so module, and have a partly working webcam. I can at least take photographs with cheese but not a working video (rapid movement & some audio - unintelligible), and switching from the cheese desktop loses the picture when I return (although resizing the window does bring the picture back). I don't use the webcam much, but I do like to have everything working properly. I'm not keen to 'upgrade' to squeeze until I can get this fixed. Anyone with any ideas? Thanks, Bruce ======= Bruce Ward, Nelson, New Zealand -- 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/4e8ac58e.40...@orcon.net.nz
Re: Re: Can't locate ndiswrapper module!
Thanks for all the replies. Yes, I'm running Lenny with standard Debian kernel 2.6.26-2-486, and in doing so was hoping to avoid having to compile ndiswrapper. However, I have now done so. (It was not fast!) Chris Bannister's comment about PCcard v. Cardbus may be an issue - the card is Cardbus, the laptop recognises the card with lspci, but I don't yet know if the laptop is fully Cardbus compatible. If I read Geoff Simmons correctly, the pre-compiled modules do not exist any more. My reference was to 'stable' distribution package of ndiswrapper-source on Debian website which suggests that the modules do exist. Seems as though that page needs updating to remove the reference. I note that the corresponding page for Squeeze has no reference to pre-compiled modules. Thanks again. I still have some work to do to see if I can get this card working. Bruce -- ======= Bruce Ward, Nelson, New Zealand -- 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/4c954caa.3070...@orcon.net.nz
Can't locate ndiswrapper module!
I get this message: FATAL: Module ndiswrapper not found. Further investigation leads me to the web page for the Debian package ndiswrapper-source (1.53-2). On that page is found: 'This package provides the source code for the ndiswrapper kernel module. If you use a standard distribution kernel, you mostly will not need this, but use the pre-compiled modules instead.' This looks good (Note this is a "toy" laptop - 48MB RAM - running Lenny with a PCMCIA wireless card with a Marvell chip) if I can avoid having to download source and compile. Problem: I cannot find "pre-compiled modules" anywhere on the Debian site. Do they exist, or are they just a myth? Bruce -- ======= Bruce Ward, Nelson, New Zealand -- 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/4c91dc07.3090...@orcon.net.nz
Re: Lenny does not recognise blank CD; Etch does.
Javier Barroso wrote: Hi, On Wed, Jun 24, 2009 at 7:34 AM, Bruce Ward wrote: On Tue, 2009-06-23 at 07:35 +0200, Frank Lin PIAT wrote: On Mon, 2009-06-22 at 16:49 +1200, Bruce Ward wrote: On Sun, 2009-06-21 at 12:18 +0200, Frank Lin PIAT wrote: On Sun, 2009-06-21 at 21:35 +1200, Bruce Ward wrote: On Sat, 2009-06-20 at 16:35 +0200, Frank Lin PIAT wrote: On Sat, 2009-06-20 at 20:21 +1200, Bruce Ward wrote: I have a machine with a dvd writer (/dev/hdc) and a cd writer (/dev/hdd). under Lenny, the CD writer will not recognise a blank CD. Nothing. The DVD writer will recognise one. Any ideas? Humm... you might want to check how HAL detects that devices. There are some GUIs, but you can send a report with: hal-find-by-capability --capability storage.cdrom | xargs hal-device I reported a bug [1] against hal package, I'm not sure, but my dvd are not recognized anymore, like in this thread ( I referenced it in the bug) I'm using sid, with DVD+-RW GSA-H53L unit. Bruce, did you find any solution to this issue ? Thanks, [1] http://bugs.debian.org/539149 No solution. I have come to the conclusion that it is probably a kernel issue because the kernel never shows that it recognises there is a blank disc in that drive under Lenny. I have a bit of testing to do which hasn't been done because I have been away for a little while. Bruce -- === Bruce Ward, Nelson, New Zealand -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Re: Boot from 2.6.26-2-686 fails - unable to find root device
Juha Tuuna said: >> The boot fails with messages: >>Gave up waiting for root device. >>ALERT! /dev/disk/by-label/D5root does not exist. >> Dropping to a shell! >> >> At that stage there is no /dev/disk directory (let alone a by-label >> subdir!) >> >> I use labels for my partitions because I have a mix of SATA and SCSI >> disks and Etch and Lenny find them in different order! I have exactly >> equivalent GRUB stanzas for both kernels; 2.6.26-1-686 has no problem. >> >Try editing /boot/grub/menu.lst > Look at the working 2.6.26-1 entry and then match the root= in 2.6.26-2 entry > accordingly. That should be it. Done that. That is not the problem - here are the GRUB menu.lst entries: title Debian GNU/Linux, kernel 2.6.26-2-686 root(hd0,0) kernel /vmlinuz-2.6.26-2-686 root=LABEL=D5root ro quiet initrd /initrd.img-2.6.26-2-686 title Debian GNU/Linux, kernel 2.6.26-1-686 root(hd0,0) kernel /vmlinuz-2.6.26-1-686 root=LABEL=D5root ro quiet initrd /initrd.img-2.6.26-1-686 The second one works, the first fails. Why? Bruce -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Boot from 2.6.26-2-686 fails - unable to find root device
I have a problem with the new linux-image (2.6.26-2-686) provided as an update to Lenny. I have no problem with booting from the old image (2.6.26-1-686). The boot fails with messages: Gave up waiting for root device. ALERT! /dev/disk/by-label/D5root does not exist. Dropping to a shell! At that stage there is no /dev/disk directory (let alone a by-label subdir!) I use labels for my partitions because I have a mix of SATA and SCSI disks and Etch and Lenny find them in different order! I have exactly equivalent GRUB stanzas for both kernels; 2.6.26-1-686 has no problem. Any ideas would be appreciated. Bruce -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Is this a bug which should be filed?
On Sun,28.Jun.09, 13:54:35, Bruce Ward wrote: >> I have a machine with 2 IDE CD/DVD drives on the same channel. A >> DVD-RW is /dev/hdc and a Plextor CD-RW is /dev/hdd. I also dual-boot >> between an Etch installation and a Lenny installation; both standard >> GNOME desktops. >> >> The problem is that Lenny will not detect a blank CD in the CD-RW >> drive. Etch does, placing in /var/log/messages this entry: >> kernel: cdrom: This disc doesn't have any tracks I recognize! >> >> There is no corresponding entry, ever, under Lenny although the >> drive light keeps lit (as it does for Etch) and does not go out >> which it does when there is no disk in the drive. >Andrei Popescu responded: >In what way does this affect you? The problem is that it means that with Lenny the CD-RW is unable to write a new CD under GNOME at least. I'm trying to migrate to Lenny, and this is a problem holding up the change. Regards, Bruce Ward -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Is this a bug which should be filed?
I have a machine with 2 IDE CD/DVD drives on the same channel. A DVD-RW is /dev/hdc and a Plextor CD-RW is /dev/hdd. I also dual-boot between an Etch installation and a Lenny installation; both standard GNOME desktops. The problem is that Lenny will not detect a blank CD in the CD-RW drive. Etch does, placing in /var/log/messages this entry: kernel: cdrom: This disc doesn't have any tracks I recognize! There is no corresponding entry, ever, under Lenny although the drive light keeps lit (as it does for Etch) and does not go out which it does when there is no disk in the drive. What if any bug should I file? Thank you Bruce Ward -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Lenny does not recognise blank CD; Etch does.
On Tue, 2009-06-23 at 07:35 +0200, Frank Lin PIAT wrote: > On Mon, 2009-06-22 at 16:49 +1200, Bruce Ward wrote: > > On Sun, 2009-06-21 at 12:18 +0200, Frank Lin PIAT wrote: > > > On Sun, 2009-06-21 at 21:35 +1200, Bruce Ward wrote: > > > > On Sat, 2009-06-20 at 16:35 +0200, Frank Lin PIAT wrote: > > > > > On Sat, 2009-06-20 at 20:21 +1200, Bruce Ward wrote: > > > > > > I have a machine with a dvd writer (/dev/hdc) and a cd writer > > > > > > (/dev/hdd). > > > > > > > > > > > under Lenny, the CD writer will not recognise a blank CD. Nothing. > > > > > > The > > > > > > DVD writer will recognise one. > > > > > > > > > > > Any ideas? > > > > > > > > > > Humm... you might want to check how HAL detects that devices. There > > > > > are > > > > > some GUIs, but you can send a report with: > > > > > > > > > > hal-find-by-capability --capability storage.cdrom | xargs hal-device > > > > > > > > > > I suppose it's important to have a line with "storage.cdrom.cdrw = > > > > > true", then we can check "storage.removable.media_available" ... > > > > > > > > > > Franklin > > > > > > > > > Thanks for the ideas Franklin. > > > > This looks like it might open a can of worms ... > > > > > > Actually, nautilus-cd-burner's README.Debian states: > > > > > > "This code detects available CD writers by examining files in /proc. > > > It will try /proc/sys/dev/cdrom/info which is created by the 'cdrom' > > > module, and /proc/scsi/sg/devices which is created by the 'sg' > > > module. One of these modules must be loaded for nautilus-cd-burner > > > to work." > > I'm running standard Debian 2.6.26-1-686 kernel. Neither installation > > has sg devices; both have /proc/sys/dev/cdrom/info listing both hdd and > > hdc. The only difference between them is that the etch one thinks that > > hdd: > > Can read MRW: 1 > > Can write MRW:1 > > Can write RAM:1 > > That's odd. > Check if upstream program has it's own mailing list, or file a bug. > > Regards, > > Franklin > Many thanks for your time and patience, Franklin. You are right, a difference in the cdrom/info file is odd, or would be if it was true - looks like I led you astray there, as both versions of /proc/sys/dev/cdrom/info are saying the same thing. However, the other things I have found that might be useful, are that the Lenny kernel does not detect the new media when I insert a blank, but Etch puts in /var/log/messages: samarkand kernel: cdrom: This disc doesn't have any tracks I recognize! A problem in cdrom or ide_cd_mod modules? Although there is no Lenny kernel message, hal-find-by-capability does know there is some new medium: storage.removable.media_available = true (bool) Also the drive light stays on when blank media is present. Another difference between the two, but one which seems unlikely to be significant, is that the lshal program finds them in different orders i.e. Etch finds DVD-RW first, Lenny finds CD-RW first. This is also true for 'hal-find-by-capability --capability storage.cdrom'. Regards, Bruce -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Lenny does not recognise blank CD; Etch does.
On Sun, 2009-06-21 at 12:18 +0200, Frank Lin PIAT wrote: > On Sun, 2009-06-21 at 21:35 +1200, Bruce Ward wrote: > > On Sat, 2009-06-20 at 16:35 +0200, Frank Lin PIAT wrote: > > > On Sat, 2009-06-20 at 20:21 +1200, Bruce Ward wrote: > > > > I have a machine with a dvd writer (/dev/hdc) and a cd writer > > > > (/dev/hdd). > > > > > > > under Lenny, the CD writer will not recognise a blank CD. Nothing. The > > > > DVD writer will recognise one. > > > > > > > Any ideas? > > > > > > Humm... you might want to check how HAL detects that devices. There are > > > some GUIs, but you can send a report with: > > > > > > hal-find-by-capability --capability storage.cdrom | xargs hal-device > > > > > > I suppose it's important to have a line with "storage.cdrom.cdrw = > > > true", then we can check "storage.removable.media_available" ... > > > > > > Franklin > > > > > Thanks for the ideas Franklin. > > This looks like it might open a can of worms ... > > Actually, nautilus-cd-burner's README.Debian states: > > "This code detects available CD writers by examining files in /proc. > It will try /proc/sys/dev/cdrom/info which is created by the 'cdrom' > module, and /proc/scsi/sg/devices which is created by the 'sg' > module. One of these modules must be loaded for nautilus-cd-burner > to work." > > So, check if the appropriate modules are loaded, then have a look on the > kernel side (which Kernel do you use? can you test 2.6.26 or 2.6.30) > > Franklin > I'm running standard Debian 2.6.26-1-686 kernel. Neither installation has sg devices; both have /proc/sys/dev/cdrom/info listing both hdd and hdc. The only difference between them is that the etch one thinks that hdd: Can read MRW: 1 Can write MRW:1 Can write RAM:1 Other than this, both files have the same information. What further investigation should I do? Hope this helps! Bruce. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Lenny does not recognise blank CD; Etch does.
On Sat, 2009-06-20 at 16:35 +0200, Frank Lin PIAT wrote: > On Sat, 2009-06-20 at 20:21 +1200, Bruce Ward wrote: > > I have a machine with a dvd writer (/dev/hdc) and a cd writer > > (/dev/hdd). > > > under Lenny, the CD writer will not recognise a blank CD. Nothing. The > > DVD writer will recognise one. > > > Any ideas? > > Humm... you might want to check how HAL detects that devices. There are > some GUIs, but you can send a report with: > > hal-find-by-capability --capability storage.cdrom | xargs hal-device > > I suppose it's important to have a line with "storage.cdrom.cdrw = > true", then we can check "storage.removable.media_available" ... > > Franklin > Thanks for the ideas Franklin. This looks like it might open a can of worms ... First Etch: hal-find-by-capability finds the DVD-RW drive but does not find the Plextor CD-RW drive (yet Etch works the CD-RW OK!). Second Lenny: hal-find-by-capability finds the Plextor CD-RW, but not the DVD-RW! With no blank media in the CD-RW, it reports " storage.removable.media_available = false (bool)" With blank media present, it reports " storage.removable.media_available = true (bool)" Exactly what we would hope for I think. But GNOME seems not to recognise this. I have just written a CD image under Lenny using wodim. What now? Bruce -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Lenny does not recognise blank CD; Etch does.
I have a machine with a dvd writer (/dev/hdc) and a cd writer (/dev/hdd). I have an Etch installation on an ATA HDD, and all works well. I also have, on the same machine, a fresh Lenny installation which is on a SATA disk. In both cases I use a standard (I believe) GNOME setup. Unfortunately (because I wish to move to Lenny and remove the Etch), under Lenny, the CD writer will not recognise a blank CD. Nothing. The DVD writer will recognise one. Etch has no such problem, both drives recognise a blank CD. Why worry about the situation? Well I have found that CDs written slowly with the old CD writer seem to be more reliably read in other CD drives, and I just like to have everything working that should work! Any ideas? Thanks. Bruce Ward === Bruce Ward, Nelson, New Zealand -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Re: Is there a screencapture utility?
Thanks to everyone who contributed to this thread! It looks as though my choices are ImageMagick's import, KSnapshot, or Gimp's Acquire with the possible need for further trimming. Thank you again, Bruce Ward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Lilo boot from second drive - success
Thanks to everyone who chipped in on this, a fix has been found. The problem is really that of getting LILO to boot the slave drive, which BIOS has found to be the first as the removable master is not present! Solution is (in /etc/lilo.conf): disk=/dev/hdb bios=0x80 Works a treat! Bruce Ward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Newbie with modem installation problems
Have been trying unsuccessfully to configure my ADSL connection with a Speedtouch Home modem, connected through an SMC USB connector. It is all working fime in Win 98 and some trial installations I did with red Hat and Mandrake both detected and set up the modem correctly. I would rather use Debian, but things just don't seem to work. The Mandrake setup seems to be using the Pegasus and Red Hat installations seemed to use the Pegasus USB drivers. I have installed hotplug and the pegasus drivers. Hotplug seems to be detecting the USB adapter OK and it lsusb shows an appropriate Ethernet device. It does not seem to be associating this device with the Pegasus drivers, and I don't have any eth0 device available. Anyone give me some clues on how to go about this task? Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Setting up coloured directory listings
Thanks to those who proffered suggestions - I think I've got the answer and am about to test it out. Thanks again, Bruce Ward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Setting up coloured directory listings
Greetings folks. I could use some help. It seems that a basic installation of Woody does not automatically set up dircolors. I know how to enable the coloured directory listings by editing .bashrc and/or .profile in the users home directory. However, I cannot find how to set things so that all newly created users get the coloured listings turned on by default. How can it be done? Thank you. Bruce Ward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
