Re: Tool to bounce mails
On Saturday 11 October 2003 01:47 am, Paul Johnson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, Oct 10, 2003 at 11:49:32AM -0400, Daniel B. wrote: > > > Nice logo...where's the content? > > > > What do you mean? > > Ah, Konq 3.2 only shows the logo and a big blank page. > Konq 3.1 does the same thing, but I was able to read the article by using the source. > - -- > .''`. Paul Johnson <[EMAIL PROTECTED]> > > : :' : > > `. `'` proud Debian admin and user > `- Debian - when you have better things to do than fix a system > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQE/h7WqUzgNqloQMwcRAurXAJ40AtzvVY5kyMKfYrcIgb5Hab9iEACdFNyz > Cn6Mg48nDQE8INYtnhzHpuA= > =4Uhb > -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pasting into vi inserts many indents
On Tuesday 18 November 2003 01:27 pm, Brian wrote: > Hi, > Lately, if I open a file with vi from inside a gnome-terminal and then > select a large chunk of text, (it doesn't matter where, e.g., Mozilla or > the same vi session, both do it), it corrupts the formatting with many > indents. The pasted output inserts more indents on each line than there > were on the previous line to create a "cascading formatting". Can someone > point me to how I can stop this? I know I can fix past problems with > cat file | tr -d '\t' , but how can I stop the bug in the first place? > However, I can't get it to do it now for an example. > > Brian > > -- This is due to a vi setting, autoindent. Try typing :set noai before pasting text. If you want ai back on, :set ai. :help ai for more info. If that's not it, I may need more details. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sound driver
On Friday 19 November 2004 16:08, Jason Rennie wrote: > On Thu, Nov 18, 2004 at 11:51:22AM -0700, Justin Guerin wrote: > > Sounds like you have a DMA or IRQ problem. Can you check which DMA and > > IRQ channels are assigned during Knoppix boot, and during Debian boot? > > You may have to tell the sound module to use a specific IRQ when it's > > loaded. I had to do the same thing with my ISA card, when I first > > configured it. I just went down the list of available IRQs before I > > got to one that worked. > > Did some reading on the subject. The Sound How-To confirms your > suspicisions: > > Another symptom is sound samples that loop. This is usually caused > by an IRQ conflict. > > The Boot Prompt How-To has information on boot arguments, but they > don't seem to work. I tried both "sound=22" and "snd-via82xx=22" > (after making sure I had alsa-modules-2.4.27-1-686 installed), but the > card gets configured with IRQ 18. Here's the dmesg output: > > Via 686a/8233/8235 audio driver 1.9.1-ac3 > via82cxxx: Six channel audio available > PCI: Setting latency timer of device 00:11.5 to 64 > ac97_codec: AC97 Audio codec, id: VIA97 (Unknown) > via82cxxx: board #1 at 0xE000, IRQ 18 > > [EMAIL PROTECTED]:~$ cat /proc/cmdline > root=/dev/hdb2 ro snd-via82xx=22 > These won't work, because the arguments are provided to the kernel, not to the module. If your sound driver were compiled into the kernel, this would be the proper way to provide the argument. Since it's not, you've got to provide the argument when the module actually loads. > Any ideas what else I should try? > > Many thanks, > > Jason One easy way is to specify the option as an argument to modprobe. I can't remember the exact format, but I think it's sufficient to do "modprobe snd-via82xx irq=22". I'll keep looking for the proper format, but I'll send this message, just in case the above works. As for making it permanent across a reboot, you've got two options. You can compile the module in the kernel, and specify the IRQ on the kernel command line (as you did above), or you can edit a file somewhere and provide the argument to modprobe when it loads the module at boot time. I'm trying to find that file, but I haven't yet. :-/ I'll let you know if I find the information I'm lacking. Sorry I can't be of more help right now, but it was so long ago that I had to twiddle with my sound card. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sound driver
On Friday 19 November 2004 16:41, Justin Guerin wrote: > On Friday 19 November 2004 16:08, Jason Rennie wrote: > > On Thu, Nov 18, 2004 at 11:51:22AM -0700, Justin Guerin wrote: > > > Sounds like you have a DMA or IRQ problem. Can you check which DMA > > > and IRQ channels are assigned during Knoppix boot, and during Debian > > > boot? You may have to tell the sound module to use a specific IRQ > > > when it's loaded. I had to do the same thing with my ISA card, when > > > I first configured it. I just went down the list of available IRQs > > > before I got to one that worked. > > > > Did some reading on the subject. The Sound How-To confirms your > > suspicisions: > > > > Another symptom is sound samples that loop. This is usually caused > > by an IRQ conflict. > > > > The Boot Prompt How-To has information on boot arguments, but they > > don't seem to work. I tried both "sound=22" and "snd-via82xx=22" > > (after making sure I had alsa-modules-2.4.27-1-686 installed), but the > > card gets configured with IRQ 18. Here's the dmesg output: > > > > Via 686a/8233/8235 audio driver 1.9.1-ac3 > > via82cxxx: Six channel audio available > > PCI: Setting latency timer of device 00:11.5 to 64 > > ac97_codec: AC97 Audio codec, id: VIA97 (Unknown) > > via82cxxx: board #1 at 0xE000, IRQ 18 > > > > [EMAIL PROTECTED]:~$ cat /proc/cmdline > > root=/dev/hdb2 ro snd-via82xx=22 > > These won't work, because the arguments are provided to the kernel, not > to the module. If your sound driver were compiled into the kernel, this > would be the proper way to provide the argument. Since it's not, you've > got to provide the argument when the module actually loads. > > > Any ideas what else I should try? > > > > Many thanks, > > > > Jason > > One easy way is to specify the option as an argument to modprobe. I > can't remember the exact format, but I think it's sufficient to do > "modprobe snd-via82xx irq=22". I'll keep looking for the proper format, > but I'll send this message, just in case the above works. > > As for making it permanent across a reboot, you've got two options. You > can compile the module in the kernel, and specify the IRQ on the kernel > command line (as you did above), or you can edit a file somewhere and > provide the argument to modprobe when it loads the module at boot time. > I'm trying to find that file, but I haven't yet. :-/ I'll let you know > if I find the information I'm lacking. Sorry I can't be of more help > right now, but it was so long ago that I had to twiddle with my sound > card. > > Justin OK, you need to edit /etc/modules.conf and provide the option there. I'm pretty sure the format is "irq=22", but not 100% sure. See the man page for modules.conf in order to get the general syntax right. They don't document the options format, because they are module dependent, but it should get you most of the way there. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sound driver
On Saturday 20 November 2004 09:38, Jason Rennie wrote: > On Fri, Nov 19, 2004 at 04:41:26PM -0700, Justin Guerin wrote: [snip] > > So, I've been succesful in getting the sound driver (vi82cxxx_audio) > to not load upon boot. However, it now looks like the problem is > deeper than just passing the right IRQ to the module... :( /sbin/lsmod > shows no sound driver and when I try to play an ogg file, I get > "Error: Cannot open device oss." But, "lspci -v" shows that the sound > card has been assigned IRQ 18! > > :00:11.5 Multimedia audio controller: VIA Technologies, Inc. > VT8233/A/8235/8237 AC97 Audio Controller (rev 50) Subsystem: VIA > Technologies, Inc.: Unknown device 4161 > Flags: medium devsel, IRQ 18 > I/O ports at e000 [size=256] > Capabilities: > > Just to check, I tried "sudo /sbin/modprobe via82cxxx_audio irq=22". > It gives the error "Warning: ignoring irq=22, no such parameter in > this module". > > Anyway, the sound card is getting assigned an IRQ before the sound > module is loaded. It seems that something is going wrong at the PnP > layer! Feels like every time I figure something out, there's another > problem lurking underneath... > > Jason Hmm. Perhaps you can set the IRQ in your BIOS setup? If not, there may be another module that will accept the IRQ parameter. It could be the driver for the PCI bus, but I have no idea what module that is. You might boot knoppix in expert mode to see which module load manages to change the IRQ parameter. It might also be present in the boot logs. If you can't seem to get the IRQ changed, perhaps physically rearranging the cards on your PCI bus will help. The defaults might work if you switch slots. Sorry I can't be of more help. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: initrd kernel image, dual boot with NTLDR
On Monday 22 November 2004 07:06, Brian Coiley wrote: > Hi all. > > As a complete newbie, I've had lots of help from people here over the > last few days, and as a result have upgraded Woody to Sarge. However, I > have also been advised to install a 2.4 kernel version, as opposed to the > 2.2 version that was installed with Woody. > > I tried to do this as follows: > > apt-get install kernel-image-2.4.27-1-k7 > > But, I get a message saying, among other stuff, that I need to configure > my boot loader to use initrd. It also gives instructions on how to do > this for LILO. BUT, this is a dual-boot machine, with W2K, and I'm using > NTLDR, not LILO. So, does anyone know how I fix this using NTLDR or, if > it can't be done, how I can change from using NTLDR to using LILO > (crucially, without breaking Windows!) > > Thanks > > Brian Hi Brian, I don't have any experience using NTLDR, but boot loaders aren't usually that complex, so I think I know what you could do. Lilo should be installed on to the boot sector of your Linux partition, not the MBR of the drive. Once that is done, you follow the instructions on how to change LILO to boot your new kernel. You don't have to worry about NTLDR at all, so long as you make NTLDR point to LILO (i.e. the boot sector of your partition). What happens in that case is your computer starts executing whatever program is at the MBR (should be NTLDR). NTLDR allows you to choose what you boot. If you choose Windows, it boots. If you choose Linux, it hands control over to LILO. LILO then asks you to choose which kernel you want to boot. After you choose, LILO hands off to the kernel, and you're off and running. Alternately, you can choose to install LILO in the MBR. If you configure LILO to give you the option to boot windows, you can let LILO manage your booting, and still boot windows. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.7 kernel panic
On Monday 29 November 2004 23:04, machoamerica wrote: > i compiled the 2.6.7 kernel from source using make-kpkg. when i > boot i get this: > > UDF-fs: No partition found (1) > Kernel panic: VFS: unable to mount root fs on unknown block(3,4) > Can you post a couple more lines before the panic? > /dev/hda4 is the root partition and has /boot on it as well. it's > an ext3 partition. i have no UDF partitions to my knowledge. > I think this is due to the order in which file systems are attempted. I believe you can get this error, but still succeed. > kernel options that may have relevance that i set for 2.6.7 are: > > CONFIG_EXT3_FS=y > CONFIG_BLK_DEV_IDE=y > CONFIG_BLK_DEV_IDEDISK=y > CONFIG_BLK_DEV_RAM=y > CONFIG_BLK_DEV_RAM_SIZE=16384 > CONFIG_BLK_DEV_INITRD=y > CONFIG_BLK_DEV_IDEPCI=y > CONFIG_DEVFS_FS=y > FWIW, those look fine, so far as I know. > worse, my old 2.4.18 kernel no longer works. i'm assuming this > means that what i'm doing wrong is something trivial & stupid. > my current lilo.conf is: > > boot=/dev/hda > compact > lba32 > timeout=200 > prompt > > # To use the new LILO boot menu, add the following > bitmap=/boot/debianlilo.bmp > bmp-table=109p,148p,1,7 > bmp-colors=0,15,8,15,1,7 > bmp-timer=514p,144p,0,15 > > # don't think this is needed: > #install=/boot/boot-bmp.b > > map=/boot/map > vga=normal > delay=20 > default=Linux > image=/vmlinuz > label = Linux > # i've tried commenting out read-only, but to no avail > read-only > initrd=/initrd.img > root=/dev/hda4 > > image=/vmlinuz.old > label = "Linux 2.4" > read-only > append = "hdc=ide-scsi hdd=ide-scsi" > initrd=/initrd.img.old > root=/dev/hda4 > > other=/dev/hda1 > label="Windows 98" > > thanks in advance for any help, > macho It seems as if your kernel image (the initial ram disk) is actually loaded, right? That would lead me to believe it is not your boot loader that is the problem, but rather your kernel image. On the other hand, if your old image is also found, but does not boot, then clearly the problem is broader than just your new kernel. Have you checked your root file system for errors? Is your computer from 1998 or earlier? Older bios's don't support LBA, and if your kernels or your map file isn't within the first 1024 cylinders, your out of luck. It could be that installing a new kernel moved the map file outside of the first 1024 cylinders, but I would think that would cause the kernels not to be found, so you wouldn't get as far as you did. Still, that's the reason some advocate a separate /boot partition: it can be small, and fully contained within the first 1024 cylinders, eliminating this problem. It shouldn't be necessary on newer computers, however. When you reran lilo after the install, it didn't complain, did it? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: testing apt-get not upgrading
On Friday 03 December 2004 04:38, Brendan J Simon wrote: > I'm running testing and apt-get wont upgrade quite a few packages. > I'm want to upgrade to mozilla-firefox and mozilla-thunderbird but these > are being held back, along with quite a few other files. > I'm doing the standard apt-get update/upgrade. > > If I do apt-get install mozilla-firefox it will install it but it is > telling me it is going to remove a whole lot of packages like gnome and > gnome-core. I do not want that, at least I think I don't. > > If I try to apt-get install gnome, it tells me it can't becuase of other > packages like gnome-office. > > If I apt-get install gnome-office, it will upgrade but will remove > gnome. How can installing gnome-office remove gnome ??? > Is gnome, gnome-themes, gnome-core, etc no longer required ??? > > Is there anything I can do or do I just have to wait until these > dependencies are fixed. This doesn't happen on another machine I have > at work but I think that is because gnome isn't installed. > > Thanks, > Brendan Simon. > Melbourne/Australia. Hi Brendan, Have you tried apt-get dist-upgrade? Upgrade won't install new packages or remove packages, but dist-upgrade will, in an attempt to resolve dependencies. Keep a close eye on what it wants to do before you let it, however. Testing is testing, and there could be conflicts in package dependencies that could lead to removing packages you don't actually want to, but those cases are rare and with Sarge this close to release, I doubt that's the problem, unless parts of gnome 2.8 have started to trickle in. Don't immediately fret if installing gnome-office wants to remove gnome. Gnome is a metapackage, and unless it wants to remove all the dependencies too, you won't lose anything. Quite often, packages that provide the same (or very similar) things change names, and you'll have to remove the old named one to install the new one. That's what dist-upgrade was designed to solve for you. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Error apt-getting new EM64T kernel
On Tuesday 14 December 2004 12:27, Simon Buchanan wrote: > Replies *below* :) > > Adam Aube wrote: > > Please don't top post (which is putting your reply above the original > > mesage) - it makes the thread harder to follow. > > > > Simon Buchanan wrote: > >>Adam Aube wrote: > >>>Simon Buchanan wrote: [snip error message installing kernel] Just a quick thing to check, does the partition where your kernel and image reside have sufficient free space. I had problems before with a kernel package not building the initial ram disk image OK, and it turned out my /boot partition was full. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lost /dev/modem Symlink After Purging Udev And Reinstalling
Leonard Chatagnier wrote: > This request for help is being reposted as no one offered any help. > Please, would someone respond with some help, even if its just a link > offering a solution that a relative newbie can implement. > > > After Purging udev including rming the entire /etc/udev directory and > reinstalling to fix a sound problem I have > to create the modem symbolic link, ln -s /dev/ttySHCF0 /dev/modem every > time I boot up. I've tried > ChatagnierL-Home:/etc/udev/scripts# /etc/init.d/udev restart > Recreating device nodes...done. > ChatagnierL-Home:/etc/udev/scripts# > After rebooting, still no /dev/modem and have to create symlink again > ChatagnierL-Home:/etc/udev/scripts# /usr/bin/udevtest /dev/modem > version 056 > looking at '/dev/modem' > sysfs_open_class_device_path failed > ChatagnierL-Home:/etc/udev/scripts# > Googled for above message and found 7 items concerning older versions of > udev with pages of script that I wouldn't > dare try. > > There were 2 or 3 files in /etc/udev/rules.d dir that were no recreated > after reinstalling udev that goes something like: > hfcpci.conf and 10 or 50sound.rules. The hfcpci.conf is probably > pertinent to the problem. How can I recreate it? You mention that you installed your driver from hfcpci~1.deb, which tells me that you downloaded a driver from the manufacturer. Nothing in /etc/udev belonging to the hfcpci package should have been deleted, but if it was, you should reinstall that package to get those config files back. > > Considered running the script inputdev.sh, read sh man and info but > couldn't determine which option to use. Never have run a script before > but it seems to use Debian I going to have to do it. Could someone clue > me in if this is the > correct script to use and the proper switch to use. I am a relative > newbie and not a programmer, just a user. > I've also read the udev manual and googled on the subject, and its over > my head. > A quick solution is desirable as my system is fully functional > otherwise(until the next upgrade/dist-upgrade anyway). I'm using > kernel-image 2.6.8-2-686 an upgrading under testing with udev version > .056-2 installed. > There is no entry regarding /dev/modem, only a capi entry, in the > udev.rules file or in the devfs.rules file. > > _*NOT SUBSCRIBED-PLZ COPY MY EMAIL ADDRESS*__* > *_ > Thanks for any help, > Leonard Chatagnier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Custom Kernel 2.4.18 = No Loadable Modules?
Tony Vandiver wrote: > Hi All, > > I started with a Debian Woody Distribution 3.0r5 where the kernel > version is 2.2.20. I couldn't compile the Omnivision ov59x driver for > a webcam and so based on the FAQ for the driver, I decided to upgrade > to kernel 2.4. I found some instructions for this, and after a few > tries, I now have a semi-working system using kernel version 2.4.18. > My problem is that I don't seem to have any modules available for > loading. The /lib/modules/2.2.20 is full of *o object modules under > subfolders like net and misc, but my /lib/modules/2.4.18 has no such > files. I tried compiling the driver, and it created a ov59x.o file > that I managed to get into /lib/modules/2.4.18/kernel/drivers/usb, but > now that's the only object file available. When I built the kernel, I > downloaded and untarred the 2.4.18 source, then did : > > > ln -s /usr/src/kernel-source-2.4.18 linux > cd /usr/src/linux > make menuconfig# selecting several supported modules including my > network card and usbcore, usb-uhci... make-kpkg kernel-image You say you selected them. Did you select to compile them into the kernel, or did you select to compile them as modules? Your symptoms point to the former. You won't have modules to load unless you ask for them. You could, if you wanted, download and install the precompiled 2.4.18, then take the /boot/config file from that kernel package, place it in your source directory as .config, then compile, and you'll have all the familiar modules. But modules are only necessary when you actually have the hardware to use them (or suspect one day you will) > cd /usr/src > dpkg -i kernel-image-2.4.18_10.Custom_i386.deb > > rebooted to a working kernel > > However, modconf shows no available modules > > I tried doing a make modules_install, but all compiles complained that > there was nothing to do. It attempts to look in directories like > /usr/src/kernel-source-2.4.18/drivers/usb where there are valid source > files like usbcore.c, but it says : Make[2]: Nothing to be done for > 'modules_install' > > I've seen a lot of newsgroup suggestions regarding this and the need to > upgrade modutils, but my modutils version is 2.4.15-1 so I'm wondering > what else to look for. > > Thanks for any help, > > Tony Vandiver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Post "apt-get dist-upgrade" question:
On Sunday 10 October 2004 10:11, Eric Dickner wrote: > --- Jule Slootbeek <[EMAIL PROTECTED]> wrote: > > \* stupid question *\ > > i am safe to assume that you restarted gnome/kde > > after you ran a > > dist-upgrade correct? > > Yes, I restarted using the new "Sarge" kernel and > everything. > > > unless you download the source through apt-get or > > are running gnome/kde > > from a non-standard location everything should have > > been updated. > > I used "apt-get dist-upgrade" and I assumed that I > would be getting binary .deb's that would be > automatically installed. > > I am running kde/gnome from where ever the binary > Woody CD's I bought put it. > > >-JSS If that's the case, then the new KDE / Gnome should "just work". What is leading you to believe that KDE / Gnome are not the current version? Also, post the output of "apt-cache policy kde" and "apt-cache policy gnome". You might also want to check out the individual packages they depend on, and their dependencies, until you get to app packages like konqueror or nautilus, because the meta-package versions don't always match their dependencies' versions. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't find /dev/dsp ?
On Friday 15 October 2004 11:16, belahcene wrote: > thank you for reply > Yes I am using 2.6 kernel > > the strange is that > inst162:~# insmod snd-pcm-oss > insmod: can't read 'snd-pcm-oss': No such file or > directory > Yes, that is strange. > while the lsmod gives : > nst162:~# lsmod |grep os > snd_pcm_oss48168 0 > snd_pcm85412 1 snd_pcm_oss > snd_mixer_oss 16640 1 snd_pcm_oss > snd50148 4 > snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss > > the user "bela" belongs to the audio group > this is the line in /etc/group > inst162:~# cat /etc/group | grep audio > audio:x:29:bela > rather than do that, use the groups command. That will indicate which groups your session is aware you are part of. If you were to add yourself to a new group without logging out, what you did would still indicate you are part of the group, but the groups command would not. That is probably not your problem, though. > is there a program like sndconfig (on RH) or > soundcardconfig-knoppix (knoppix) > thanks a lot > bela Yes, there is. Try the package sndconfig. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keeping woody
On Tuesday 28 September 2004 10:52, s. keeling wrote: > Incoming from Clive Menzies: > > On (28/09/04 10:02), s. keeling wrote: > > > Incoming from Clive Menzies: > > > > On (28/09/04 05:57), [EMAIL PROTECTED] wrote: > > > > > I have a machine running woody and another running sargs. When > > > > > the big switchover comes, I want the woody machine to continue > > > > > running woody and not follow stable to a big change to sarge. Oh > > > > > -- I will > > > > > > > > In your /etc/apt/sources.list change references from "stable" to > > > > "woody" and then you will continue to track woody. > > > > > > ... Mostly. This trick doesn't appear to work here: > > > > > > # this works: > > > deb http://security.debian.org/debian-security stable/updates main > > > contrib non-free > > > > > > # this doesn't: > > > deb http://security.debian.org/debian-security woody/updates main > > > contrib non-free > > > > Ah! Well this does here: > > deb http://security.debian.org/ woody/updates main > > Not for me: > > (0) root /root_ aptitude update > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information... Done > W: Couldn't stat source package list http://security.debian.org > woody/updates/main Packages > (/var/lib/apt/lists/security.debian.org_dists_woody_updates_main_binary-i >386_Packages) - stat (2 No such file or directory) W: Couldn't stat source > package list http://security.debian.org woody/updates/main Packages > (/var/lib/apt/lists/security.debian.org_dists_woody_updates_main_binary-i >386_Packages) - stat (2 No such file or directory) W: You may want to > update the package lists to correct these missing files > > Are you sure this isn't just an aptitude problem? Aptitude doesn't seem to like it when you change sources.list. Have you tried apt-get update first? I find that when I add a new source, I have to use apt-get update first, then aptitude update will work. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NOT ANSWERED asus a7n8x built in nic and intel pro 100 S nic
On Wednesday 29 September 2004 16:01, Ian L wrote: > At 02:20 PM 9/29/2004, you wrote: > >On Wed, 29 Sep 2004 13:54:49 -0700 > > > >Ian L <[EMAIL PROTECTED]> wrote: [snip] > I'm just having no luck at all with this. After it finished installing, > the boot process fails. The last few lines on the screen are: > > /dev/ide/host0/bus0/target0/lun0: unknown partition table > pivot_root: no such file > /sbin/init: 426: cannot open dev/console: no such file > kernel panic: attempted to kill init! > > i rebooted and was offered the choice to boot into recovery mode, but > that fails also with the same errors. > > Any suggestions? > > thanks, > > Ian Apparently, your partition table is corrupt. What does it look like? What is each partition supposed to contain? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: make xconfig & xfree???
On Thursday 30 September 2004 08:11, Robert Tilley wrote: > On Wednesday 29 September 2004 11:40 pm, Jeremy Brown wrote: > > > > Might want to try doing: > > > > bash$ xhost + > > > > as a regular user, before attempting to connect to the X server as ^ > > root. > > > > Jeremy > > [EMAIL PROTECTED]:/usr/src/linux-2.6.8.1# xhost + > xhost: unable to open display "" > > ??? > > Thanks, Bob The rest is left as an exercise for the reader. I would recommend using some of the other suggestions given in this thread before using xhost +. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mouse
On Thursday 30 September 2004 12:37, [EMAIL PROTECTED] wrote: > I'm running Woody. I have several machines connected via a Belkin KVM > switch. Works great. The problem is that the wheel does not function on > debian. I'm not that concerned about it, because it does work, but it > would be nice to be able to use the wheel to scroll. thanks... Check your XF86Config or XF86Config-4 file, and make sure your mouse has the z axis mapping options: Option "ZAxisMapping" "4 5" If it doesn't, add it (dpkg-reconfigure xserver-xfree86 or hand edit if you don't want to use debconf) and restart X. If it does, post your entire pointer config section, and relevant parts of your XFree86.log file, and maybe we can help. Also, let us know which applications you've tried to use the mouse wheel in. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NOT ANSWERED asus a7n8x built in nic and intel pro 100 S nic
On Thursday 30 September 2004 15:00, Ian L wrote: > At 07:58 AM 9/30/2004, you wrote: > >On Wednesday 29 September 2004 16:01, Ian L wrote: > > > At 02:20 PM 9/29/2004, you wrote: > > > >On Wed, 29 Sep 2004 13:54:49 -0700 > > > > > > > >Ian L <[EMAIL PROTECTED]> wrote: > > > >[snip] > > > > > I'm just having no luck at all with this. After it finished > > > installing, the boot process fails. The last few lines on the screen > > > are: > > > > > > /dev/ide/host0/bus0/target0/lun0: unknown partition table > > > pivot_root: no such file > > > /sbin/init: 426: cannot open dev/console: no such file > > > kernel panic: attempted to kill init! > > > > > > i rebooted and was offered the choice to boot into recovery mode, but > > > that fails also with the same errors. > > > > > > Any suggestions? > > > > > > thanks, > > > > > > Ian > > > >Apparently, your partition table is corrupt. What does it look like? > > What is each partition supposed to contain? > > > >Justin Guerin > > I only had 2 partitions. > hda1 / 18 gigs ext3 > hda2 swap 2 gig > > Does it matter if i use grub or lilo? or install them into the mbr or > hda1? > > thanks > > Ian Grub vs. Lilo is personal preference most of the time. Install them into the MBR if you want to use it to boot all OSes present on your system. Install to hda1 if you want to use a different boot loader. If you got this far, that's not your problem. You've already found the kernel (or the initial ram disk), the problem is mounting your root partition. Can you say what the partitions are marked as? I believe ext3 should be 0x83, and swap should be 0x82. I take it those are the only two partitions on the drive? Another thing to check is that you've got your device nodes created properly. If you're running devfs and it fails to start, you'll get this kind of error. Are you using devfs, udev, or plain /dev? Oh, you may also need to post the fstab contents (at least for your primary drive). That could also be the source of the error. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt question
On Wednesday 29 September 2004 20:29, Bradley Alexander wrote: > Got a quick apt question. I had a DIMM go bad in my sid system, and > thanks to having to hard reset it during troubleshooting, a couple of > filesystems got trashed. > > I removed the bad DIMM, and was able to rebuild the filesystems > (reiserfs). However, a slew of files (700+) got put in lost+found. Since > the bulk of them were in /, it was mainly Debian packages. > > In order to make things right again, I ran debsums -s, and got all of the > packages that either had missing files or bad md5sums on the files. > > Once I had my list, I did the following: > > [defiant ~]# apt-get install --ignore-missing --reinstall `cat deblist` > In spiite of the --ignore-missing (many are older versions of packages > that _should_ have been removed when the newer versions were installed), > I got stuff like: > > Reinstallation of automake is not possible, it cannot be downloaded. > Reinstallation of epan is not possible, it cannot be downloaded. > Reinstallation of gnapster is not possible, it cannot be downloaded. > Reinstallation of gtkhtml1.1 is not possible, it cannot be downloaded. > ... > Reinstallation of libgtkhtml1.1-3 is not possible, it cannot be > downloaded. Reinstallation of libgtkhtml1.1-data is not possible, it > cannot be downloaded. Reinstallation of libhdf5-serial is not possible, > it cannot be downloaded. Package libid3-3.7-13 is not available, but is > referred to by another package. This may mean that the package is > missing, has been obsoleted, or is only available from another source > E: Package libid3-3.7-13 has no installation candidate > > Is there a way to get around the messages above without individually > removing them from the apt-get list (and the system)? And why doesn't > --ignore-missing seem to work? > -- > --Brad Did you do an apt-get update first? If so, are you sure that the errors you're seeing are from the --ignore-missing and not from the --reinstall flag? What I mean is, --reinstall says to "Re-Install packages that are already installed and at the newest version." If a package can't be downloaded, it isn't at the newest version, so reinstall probably shouldn't work. Ignore missing seems more geared towards new packages. The combination may not be trying to do what you think it is, but a developer would be able to answer that for sure. The error message about libid3-3.7-13 indicates either a packaging error, or your not up to date. Also, it could be that package is in a different repository, which is not in your sources.list file. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: floppy in kernel 2.6: is not a block device
On Wednesday 29 September 2004 21:53, Dan Jacobson wrote: > Can't use my floppy drive in Linux 2.6. > G> As root in /dev type: MAKEDEV floppy > ./MAKEDEV: don't know how to make device "floppy" > G> Another piece, is "udev" installed? > OK, I installed it and rebooted. > G> If it is, it should create those auto-magically. > No it didn't. ls /dev/f* shows none. Now trying > ./MAKEDEV fd0 > shows lots of supposed action, but ls doesn't show any changes. > On a second run there is no output, so supposedly its changes are > registered somewhere. Maybe I have to reboot to see them too... > G> Or you can manually use "mknod" to create them. > G> Here is my listing for /dev/fd0: > G> brw-rw 1 root floppy 2, 0 2003-11-12 09:24 /dev/fd0 > G> That would be: > G> mknod --mode=0660 /dev/fd0 b 2 0 > Done. However still, > mount: /dev/fd0 is not a valid block device > OK, that's better than the earlier > mount: special device /dev/fd0 does not exist > no help from modprobe ide-floppy and floppy either. > I was able to use the floppy in Linux 2.4. Not in 2.6. > > In fact, I now notice using reboot(8) no longer reboots, just hangs > ttys. pstree shows it is stuck doing "shutdown -r 0 w". I will remove > udev forthwith. A second try hung my last tty and I had to walk over > to press a hard reset. Geez. I notice purging udev leaves files > behind. Their name flew off my screen and now I won't ever be able to > find them without repeating an install/purge. > > Ok, now rebooting again, luckily with no filesystem damage after the > hard reboot, I see all the /dev/fd* stuff is indeed there. However, > as much as I try, /dev/fd0 is not a valid block device. I use 2.6, and udev, and my floppy works with the /lib/modules/2.6.6-1-686/kernel/drivers/block/floppy.ko module. Did you try that module without using ide-floppy at the same time? When I try "modprobe floppy ide-floppy" I get an error message indicating ide-floppy is not a valid option for modprobe floppy. What is the output when you use just modprobe floppy? When your module initializes correctly, you'll get a message like this: inserting floppy driver for floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 If you didn't get that middle line, then your floppy drive won't work. Once the module is loaded, udev will create the device node. I believe devfs will as well. If you don't have either of those, then manually creating the device node should work. You're getting errors with your device node because your driver isn't working. Note that the above is my guess that you need the floppy driver, not the ide-floppy driver. Open your case and take a look: how is your floppy connected? To its own bus, or to the ide bus? That will tell you what you need. Hope that helps, Justin Guerin p.s. I copied you because it's been so long since you posted. Hope that's OK. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DMA issue
On Saturday 25 September 2004 10:28, Josh Lauricha wrote: > On Sep 23, 2004, at 9:13 AM, Justin Guerin wrote: > > On Wednesday 22 September 2004 14:50, Josh Lauricha wrote: [snip] > Well, taking Justin's advice, I've pulled the disk put it into another > computer and tried to use the smarttools on it. smartctl -a /dev/hdc > shows it's SMART capable, however smart -s on fails. I'd take it this > is a good sign the drives dead? > > But I just noticed that, when mounted ro it works okay. > Dead, or in the process. Using it in ro mode is great, because it allows you to get your data off before it dies. The on-drive controller having errors is a bad sign. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NOT ANSWERED asus a7n8x built in nic and intel pro 100 S nic
On Friday 01 October 2004 16:47, Ian L wrote: [snip] > However, using that older version of debian i just installed it fine and > it booted up fine. I have one probably though in trying to upgrade this > version ... how do i upgrade it without a working network card? i tried > installing the 2.6.8 kernel package before but there was a never ending > list of package dependencies which made it a PITA to try and upgrade. Can > i download all the packages from somewhere, burn them to cd and then let > apt upgrade using the cdrom as the source? > > thanks again for the help > > Ian Yes, you can. You can download the cd images using jigdo (if you have a working Debian computer with a network), or just download the full iso, then run apt-cdrom to add them to your sources.list file. You can then update and upgrade your system. See http://www.debian.org/distrib/cd for detailed instructions on the many ways to obtain CD images, if you can't use jigdo for some reason (like it isn't installed or your only Debian machine is the one without networking). You can also use the CD you installed from to install extra software. You might want to look into apt-zip, though I don't have any experience with it. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glxgears slow under 2.6, fast under 2.4
On Thursday 07 October 2004 07:15, Ric Otte wrote: > Things are very slow for me under 2.6 kernels. Under 2.4.16 I was able > to play tuxracer just fine, but under 2.6.6 things are so slow that it is > unplayable (a second or so pause between command and action). I ran > glxgears under 2.4.16 and got output like: > 2430 frames in 5.0 seconds = 486.000 FPS > Under 2.6.6 I get output like: > 1332 frames in 5.0 seconds = 266.400 FPS > I ran glxinfo and noticed that under 2.4.16 direct rendering was YES but > it was NO under 2.6.6. I then tried upgrading to 2.6.8.1 (changing the > agpgart chipset to via from intel in the kernel (i do have a via chipset) > and things got worse under glxgears with the correct chipset in the > kernel: 860 frames in 5.0 seconds = 172.000 FPS > I do notice that under 2.4.16 I get the following in dmesg: > dmesg |grep agpgart > Linux agpgart interface v0.99 (c) Jeff Hartmann > agpgart: Maximum main memory to use for agp memory: 439M > agpgart: Detected Via Apollo Pro KT266 chipset > agpgart: AGP aperture is 32M @ 0xfc00 > and under 2.6.6 I get: > Linux agpgart interface v0.100 (c) Dave Jones > [drm:drm_init] *ERROR* Cannot initialize the agpgart module. > while under 2.6.8.1 I get: > $ dmesg |grep agpgart > Linux agpgart interface v0.100 (c) Dave Jones > [drm:mga_probe] *ERROR* Cannot initialize the agpgart module. > agpgart: Detected VIA KT266/KY266x/KT333 chipset > agpgart: Maximum main memory to use for agp memory: 439M > agpgart: AGP aperture is 32M @ 0xfc00 > So things seemed to improve under 2.6.8.1 in that at least I'm detecting > the via chipset, but I'm still not initializing the agpgart module. I'm > using a Matrox g550 video card. > > Any suggestions as to what might be wrong or what to do would be > appreciated. I'm not a debian expert, and I suspect I may be doing > something > obviously wrong. > Thanks, > Ric Just a guess, but did you reconfigure X to run at a nice value of 0? The 2.4 kernels ran best when X was niced to -10, but with the 2.6 anticipatory scheduler, it turns out to be a bad thing. Also, check out your /etc/modules contents. Are you trying to load some modules you shouldn't? >From your error messages, it does seem that 2.6.8 properly initializes the agpgart, but I don't know why it also gives you the error message. You didn't indicate whether direct rendering was turned on in 2.6.8.1. Was it still off? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cant boot with kernel 2.6.8
On Wednesday 06 October 2004 16:33, Ian Lipsky wrote: > I've been trying to get the 2.6.8 kernel installed. But it keeps failing > to boot. > > nforce2 ide controller at pci slot :00:09.0 > nforce2 chipset revision 162 > nforce2 not 100% native mode, will probe irqs later > nforce2 bios didnt set cable bits correctly, enabling workaround > > > > /dev/ide/host0/bus0/target0/lun0: unknown partition table > NTFS driver 2.1.15 flags R/O MODULE > pivot_root: no such file or directory > /sbin/init: 426: cannot open dev/console: no such file > kernel panic: attempted to kill init! > > I've been using google to try and find a solution but so far no luck. My > lilo.conf file looks like this: > > image=/vmlinuz > label=Linux > read-only > initrd=/initrd.img > > I can boot with the older 2.14.18 kernel with no problem. I tried > downloading and installing the nforce drivers from nvidia (even though > they just seem to be audio and network drivers, no ide drivers) but i > couldnt get that to install either. Tells me gcc version check failed, or > if i try to compile it manually tells me make command not found (gcc is > installed). > > Any suggestions? > > Ian Hi Ian, This link may prove useful. http://www.geocities.com/rlcomp_1999/f10errors.html "After reading the man page on fdisk for Linux, I realized that it will assume its own geometry if fdisk for Linux is the first utility to partition the disk." I believe your situation falls into this category? It's not complete, and it might be old, but it could help. Hope it does. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody: boot fail after upgrade
On Friday 08 October 2004 02:40, Howard Chin wrote: > I installed woody using the stable distribution a few weeks ago. Recently > I decided to upgrade to the testing distribution because the packages are > more up-to-date in that distribution. > So I changed the apt source in /etc/apt/source.list and replace the word > "stable" with "testing" in the http entry. > I then used dselect to update the package list and installed all the > recommended packages and upgrades. > After the upgrade, I can no longer boot. The system hang right after the > BIOS screen with only "Li" printed. Seemed like something went wrong with > the bootloader. Can someone let me know how it can be fixed? > Howard Hi Howard, According to the Lilo man page, the first stage loader tried to pass control to the second stage loader, but it detected an error. Are any hex digits printed after the LI? If so, they give information about the nature of the error. It is very unusual that upgrading your software would cause boot problems of this nature. Did you change any hardware configuration? Did you install a new kernel? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cant boot with kernel 2.6.8
On Thursday 07 October 2004 17:09, Ian L wrote: > At 10:43 AM 10/7/2004, you wrote: > >On Wednesday 06 October 2004 16:33, Ian Lipsky wrote: [snip] > > > >Hi Ian, > > > >This link may prove useful. > >http://www.geocities.com/rlcomp_1999/f10errors.html > > > >"After reading the man page on fdisk for Linux, I realized that it will > >assume its own geometry if fdisk for Linux is the first utility to > >partition the disk." > > > >I believe your situation falls into this category? It's not complete, > > and it might be old, but it could help. > > > >Hope it does. > > > >Justin Guerin > > Sorry to be so dense, but i dont quite understand that. He realized it > will assume its own geometry ... what exactly is 'it' ? Also, if my > partitions are bad, wouldnt the 2.4.18 kernel also fail to boot? > > I cant remember what was used to partition the disk ... it probably was > fdisk ... whatever the default partitioning tool is that comes with woody > should be what i used to partition this disk. Also, his solution seems to > be to re-create the partitions ... thats just going to wipe out the > install and put me back at the beginining isnt it? > > thanks for the help ... sorry i dont see how this helps me. > > Ian The point is, did you ever use a Dos / Windows utility to partition the disk, or did you buy it new and partition it with the installer? Yes, his solution re-creates the partitions, and yes, you would then have to reinstall (or maybe not, since the partition table would be identical), but during the reinstall, you wouldn't have to make the partitions, you could just install. The feeling I got from the web page was that this would allow things to proceed normally. As for why one kernel boots and the other doesn't, I don't know. I suspect it's related to your bootloader and the fact that the installed kernel comes from the same source as the partition table, but that's a total guess. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can only ping after kernel upgrade
On Friday 15 October 2004 12:43, Bernie Berg wrote: > Howdy, > I loaded up woody with the bootbf2.4-xfs_with_basedebs.iso netist image > yesterday. I then proceeded to upgrade my kernel to 2.4.27. I used > apt-get to get the sources, copied the orig config from /boot, ran make > oldconfig (used the defaults) and then ran make-kpkg to compile. I then > installed it with dpkg -i and rebooted. Everything seems to come up > right, except I cannot access any network recourses. I CAN ping, but > that is it. I can ping internal and external addresses. I can also > ping with dns resolution (I pinged www.yahoo.com). I also pinged with > larger packet sizes (1200) and it still pings fine... but I cannot use > lynx, ftp, or apt-get. I tried loading the nic driver (3c59x) as a > module or compiling into he kernel, it doesn't work either way. I tried > assigning the address static and dhpc, doesn't work either way. I works > fine with the vanilla kernel. > > Any ideas why that is happening? > Thanks! > -- > bernie Hi Bernie, Compare the config of the working kernel to the non-working kernel. Specifically, check the networking section. Also, make sure that the modules listed in the working kernel are either also loaded in the new kernel, or are built into the kernel. In case you don't know, the config for package kernels is in /boot/config. If you can't figure it out, post the networking section of your new kernel config, and maybe we can help. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Certain web pages on Mozilla cause my screen to go funny.
On Monday 18 October 2004 01:59, Adam Funk wrote: > Certain web pages cause my screen to "go funny" with horizontal lines > for a few seconds, then leave it looking ugly until I log out of GDM > and back in again. This happens only with Firefox and Mozilla; I can > look at the same pages in Konqueror and Galleon. It used to happen > occasionally on slashdot.org (usually on Apple-related pages, I think) > but not www.theregister.co.uk is giving me trouble. I use XFCE4 but > I've had the same problem in GNOME. > > Here's a screenshot of the after-effects. > http://www.ducksburg.com/misc/snapshot12.png > > Below is some information I think might be relevant. Please ask for > anything else that might help. > > Thanks, > Adam > > Package list: > ii gdm 2.4.4.7-3 > ii mozilla 1.6-5 > ii mozilla-browser 1.6-5 > ii mozilla-locale-de-at 1.6-4 > ii mozilla-mailnews 1.6-5 > ii mozilla-psm 1.6-5 > ii mozilla-xft 1.6-5 > ii xfree86-common 4.3.0.dfsg.1-8 > ii xfce44.0.5-1 > ii xfce4-artwork0.0.4-3 > ii xfce4-datetime-plugin0.2-3 > ii xfce4-diskperf-plugin1.3-3 > ii xfce4-iconbox4.0.6-1 > ii xfce4-mcs-manager4.0.6-1 > ii xfce4-mcs-plugins4.0.6-1 > ii xfce4-mixer 4.0.6-1 > ii xfce4-panel 4.0.6-1 > ii xfce4-session0.1.3+20031213-5 > ii xfce4-systemload-plugin 0.3.3-4 > ii xfce4-systray4.0.6-1 > ii xfce4-themes 4.0.6-1 > ii xfce4-toys 4.0.6-1 > ii xfce4-trigger-launcher 4.0.6-1 > ii xfce4-utils 4.0.6-1 > > Excerpt from /etc/X11/XF86Config-4 > > Section "Device" > Identifier "S3 SAVAGE4 PRO/32MB PCI" > Driver "savage" > Option "SWCursor" "on" > Option "HWCursor" "off" > EndSection > > Section "Monitor" > Identifier "DELL P790" > HorizSync 30-92 > VertRefresh 50-150 > Option "DPMS" > EndSection The only time I've experienced anything like this, it was due to video card misconfiguration. I think this happened when I was running at too high a color depth for the resolution and refresh rate I was using. Once I backed it down, the problem went away. Of course, my problem wasn't triggered by web pages that I could tell, but some windows appeared normal, and some had lines throughout. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OT] hardware problem
On Wednesday 20 October 2004 07:17, Hugo Vanwoerkom wrote: > Hi Debian! > > I have a problem and would like suggestions on how to isolate what is > wrong. > > 1. I am running a Abit KT7A with 2 Maxtor HDD's 80GB + 40GB > Model=Maxtor 6Y080P0, FwRev=YAR41BW0, SerialNo=Y2FAZ3HE hda > Model=Maxtor 6E040L0, FwRev=NAR61590, SerialNo=E1FS8RWE hdb > and 3 256MB 168 pin memory cards. > So how long did you have this arrangement working fine? That is, how long did you have two drives and 3 DIMMs working with no problems? > 2. Last summer I bought a new power supply that has double ballbearings, > the original one don't. I put it in and after 20 minutes one disk goes > "bad". He can't access it. When you boot, you see garbage in the bios > identification field. I put the old powersupply in and the problem goes > away. I think the new powersupply is bad. I tried this twice and the > results are the same. > Is the new power supply rated to handle the load? If not, you'll get all sorts of strange problems. You indicate that you replaced the power supply with the old one. Are all the events mentioned below with the old power supply? I am answering as if yes, but if these happened using the new one, that would be my first guess. > 3. A few days ago, I suddenly have trouble copying an iso file from one > partition on hda to another: it takes forever, what normally takes 10 > seconds or so, now takes 10 minutes. > Sounds like DMA was turned off. Are you running smartmontools? If so, what does it say? > 4. Yesterday I tried the new Sarge installer and it hangs in "Starting > up the partitioner" booting with linux26. I file bug #277177. I try > installing a 2.4.27 kernel and that works but on booting it he turns off > DMA on the disks, says it has errors. > What are the specific error messages? > 5. I leave the system powered down overnight, boot a Sarge partition on > hda and now the system can't access hdb. I reboot and the bios id of the > hdb disk is garbage. But just a second before I could boot 2.6.7 on a > partition on that disk. > > I want to identify the problem, preferably without buying new hardware > at first. I now think it is the mobo, but how do I know? > > Suggestions? > > Hugo. You might also see what happens if you specify the hard drive geometry in the BIOS setup, rather than having autodetect. If the BIOS is currently not autodetecting the drives, then I would definitely suspect the motherboard, unless you're cutting the power and the mobo battery is dead. One easy thing to check, though, is your power supply connections. Make sure none of them are loose. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Formatting an unused partition
On Tuesday 19 October 2004 17:50, [KS] wrote: > In trying to find out how to do that, here is one way > I can think of: > > mkfs -v -t ext3 /dev/hdb10 > > Any other suggestions? > > /KS > Well, if you want a ReiserFS file system, install the package progsreiserfs and use the mkfs.reiserfs command. If you want an XFS file system, try mkfs.xfs from the xfsprogs package. If you want JFS, use jfs_mkfs from the jfsutils package. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Koqueror & Kaffeine
On Wednesday 20 October 2004 05:03, Erik Jakobsen wrote: > Hi. > > At the present I use Konqueror when I want to play NetRadio. > > The audiointerface is default to be kaboodle in konqueror, but even it > starts up, > I cannot get it to play. > > On other linuxsystems I use kaffeine. > > How can accociate kaffeine with konqueror ?. > > OS here is Debian Sarge. > > Erik Jakobsen You don't associate kaffeine with Konqueror, you associate kaffeine with they file type. Open up the KDE control center, open up the file associations module (in the KDE components section, at least for KDE 3.3 in Sid), and find the entry for the file type. Make sure kaffeine is the default. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sunrpc
On Tuesday 19 October 2004 17:03, Art Edwards wrote: > We just got a notice from security that sunrpc has an integer overflow. > Is this still a problem for Debian? It seems that sunrpc is a > kernel-level issue, so if this is a problem, does anyone have a remedial > suggestion? > > Art Edwards Check the archives for debian-security and debian-security-announce, if you aren't subscribed. Or is that where you got the message from? Regardless, you have a couple of options. If you don't really need rpc, turn it off. If you do need it, what version of Debian are you running? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Formatting an unused partition
On Wednesday 20 October 2004 13:43, [KS] wrote: > All right, thats done. I used the following command: > $ mkfs.ext3 -v /dev/hdb10 > > mkfs wrote the inodes, made the journal, etc. and I > could see the type as ext3 when I checked /dev/hdb > with cfdisk. > > My next question is, how to allow users to write to > the partition. Current permissions are drwxr_xr_x > root:root. Should I just use chmod og+w for > /mount/part10 (assuming I'm mouting it under /mount in > dir part10)? Would it be better to make this partition > similar to /tmp with the "t" bit set? Please suggest. > No, use the umask option in your /etc/fstab. You might also want to read the mount and fstab man pages, to give you an idea of what other options are available to you. Which options you use depends largely on your setup and how you intend to use the partition. > This is off topic: Does anyone know how to send > replies to threads in correct order using yahoo mail? > > Thanks. > No, I don't know how to correctly reply to threads using Yahoo mail. Sorry. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Koqueror & Kaffeine
On Wednesday 20 October 2004 11:10, Erik Jakobsen wrote: > Justin Guerin wrote: > >You don't associate kaffeine with Konqueror, you associate kaffeine with > >they file type. Open up the KDE control center, open up the file > >associations module (in the KDE components section, at least for KDE 3.3 > > in Sid), and find the entry for the file type. Make sure kaffeine is > > the default. > > > >Hope that helps, > >Justin Guerin > > Hi Justin > > Thanks for yor reply. I have the same as you have in Sid, but cannot get > it to work. > I'm sure I have done something wrong. > > Would you please look at the screendump at www.urbakken.dk/kaffeine.png > ?. > > TIA > > Erik Jakobsen. It looks like the application is only associated with the native playlist file type. You need to associate the actual audio file type with kaffeine. Can you tell me what the name of the file you are trying to listen to is? Is it a .mp3, .ra, or what? Somewhere under the audio group should be a file type that matches. Once you figure out which file you need to load with kaffeine, look for its entry in the file associations, and make sure kaffeine is listed. I checked out net radio, but it seems that you need to create a login to listen. I can't do that from work, sorry. HTH, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compaq armada m700
On Monday 18 October 2004 02:41, Eduard Pauna wrote: > hi to all, > > from a little time a have the notebook from $subj. i installed on it > debian but i think i am a little stucked - couldn't find with google > or on the hp.com site the HorizSync & > VertRefresh for the display and i'm using those reported by knoppix > but i'm not so sure they are the right one. > > Thanks for time, help or ideas Hi Eduard, Can you tell us why you think the values Knoppix uses are wrong? It seems that the notebook is only capable of 1024x768 at 24 bpp color. I found this on Google, it may help you out: http://sakeos.net/~jk/debian-Compaq-M700.html It seems to indicate the information you want: El Horizontal Sync és 31.5-56 i la Vertical sync és 50-100.5. Els video-modes serà 1024x768. Color per defecte 16. You could always try xvidtune, but be careful you don't break your system. Hope that helps, Justin Guerin
Re: Control another Linux box to play mp3s....
On Monday 25 October 2004 15:06, Kevin Wang wrote: > Hello, list, > > I'm thinking about if it is possible to let another Linux box to sound > remotely. > > Any thought? > > Kevin Hi Kevin, If you use KDE, open the Control Center, open the Sound and Multimedia section, and select the Sound System module. Click on the "Enable networked sound" checkbox, and apply the changes. If you use Gnome instead, I'd guess there's a similar option in one of its control center modules. If you aren't using a sound server, then you'll essentially have to write one. On the other hand, rather than go this route, you could always create a shared drive from one machine, mount it in the second machine, and place the sound files themselves in the shared folder. Then, you can use local apps to play your mp3s. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't Boot 2.6 Kernel -- IDE is a Module
On Monday 25 October 2004 16:09, Brian White wrote: > When I try to install a stock Debian kernel (2.6-386) on my system, it > won't boot any longer (VFS: Unable to mount root fs). The stock 2.2 > kernel that comes with Woody rescue disk boots fine. > > As far as I can tell, it's because the 2.6 kernel is compiled with IDE > as a module instead of including it in the kernel proper. Is there > something I still need to do to allow this module to be loaded? > > Thanks! > > Brian > ( [EMAIL PROTECTED] ) > > - >-- A hundred years from now it will not matter what my bank account > was, the sort of house I lived in, or the kind of car I drove... But the > world may be different because I was important in the life of a child. > - >-- ( Couldn't verify my signature? Use > http://www.precidia.com/precidia.crt ) You need to make sure the required modules are in the initial ram disk. You'll want to look at the initrd-tools package. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DHCP questions...
On Monday 25 October 2004 09:08, Kevin Wang wrote: > Hello, all, > > PS print a line as below: > > 318 ?S 0:00 /sbin/dhclient-2.2.x -q eth0 > > I've referred to man page of dhclient, see no argument of 'q', however. > What does it affect after all? > I don't have a stable box to check, but does man dhcp-options-dhclient help? How about man dhclient-script? If neither of those show the option, how about running /sbin/dhclient-2.2.x -h? If none of them show what it does, you should submit a bug report. If you want my guess as to what -q does, it puts the program in quiet mode, suppressing most output, to make the program more suitable for running in a script (such as a boot script). > Second, where or how to check if the lease of DHCP expires? I know > "ipconfig /all" can do this under Windows. > There may be a better way, but one way you can do this is look through the log, probably /var/log/syslog. If it's been a while since you brought up networking, you may have to look in an older copy of syslog. > Thanks! > > Kevin Wang Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X settings not applying?
On Sunday 24 October 2004 22:17, Eric Scott wrote: > Heya, I've got a new woody installation. My Panasonic E15 monitor > diplays up to 1024x768. 800x600 works with the default settings on > basically any operating system, but to get 1024x768 to purr I had to > tweak the refresh rate(s). First I figured out on Windows that it only > works right under 75Hz vertical. Then under Mandrake and Suse I found > that the horizontal had to include something in the neighborhood of 65. > Setting something like [EMAIL PROTECTED] with a horizontal rate of 30-60 > has made this this work swell with everything else... then I decided to > try woody. I dried dpkg-reconfigure xserver-xfree86, and supposedly set > it all right (VESA driver... same as I use in SuSE). I looked at the > config file, and have tried messing with it... everything's fine. > Restart X NO difference. It does the exact same thing as it usually Note that once you hand edit your XF86 config file, dpkg-reconfigure won't overwrite your changes. Check the list archives for how to undo this, if you don't have a copy of the original somewhere. > does with [EMAIL PROTECTED] display fine, but with the image "leaning" > off to the right side of the screen and, strangley enough, seemingly > folding underneath itself. The part of the screen that is off to the > right of the monitor displays in reverse... kinda like a transluscent > folded-under burritto shell. The old-style knobs to center and size the > display area don't turn far enough to center the image. > > Clear as mudd? Good. Basically, X doesn't seem to be displaying > @75Hz like I tell it to, and insists on doing 60Hz. Any help? >Thanx, >ES Are you still using the vesa driver, or did you change to the driver specific to your chipset? If you don't know, check the Device section of your config file. To find out which chipset you have, use lspci. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: atp-get error
On Wednesday 27 October 2004 19:28, Vadik wrote: > I just upgraded to Sarge and /I am getting this error, any > recomendation on what to do? > > Thanks > > - > / > # apt-get dist-upgrade > Reading Package Lists... Done > Building Dependency Tree... Done > Calculating Upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 1 not fully installed or removed. > Need to get 0B of archives. > After unpacking 0B of additional disk space will be used. > Do you want to continue? [Y/n] > Setting up libapache-mod-perl (1.29.0.2-13) ... > Error: mod_frontpage.so does not have a corresponding .info file. > The above errors might cause apache to not work properly or start > Please refer to the documentation on how to fix it or report it to > Debian Apache Mailing List <[EMAIL PROTECTED]> if in doubt > on how to proceed > dpkg: error processing libapache-mod-perl (--configure): > subprocess post-installation script returned error exit status 20 > Errors were encountered while processing: > libapache-mod-perl > E: Sub-process /usr/bin/dpkg returned an error code (1) If you don't really need the libapache-mod-perl package, remove it. If you do, file a bug report, or report your error to the debian-apache list. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: booting install cd
On Tuesday 26 October 2004 21:52, jacob wrote: > Hello > > Downloaded CD image and created installation CD configuered BIOS to boot > from CD drive but cannot boot. > Have no problem booting Windows Installation CD's > > Regards > Jacob Sounds like your disk is bad. Check the md5sum of the image. If that's wrong, you'll need to download the image again. If that's right, you may have just gotten a bad burn. Try burning another CD. If all else fails, the Debian homepage has links where you can buy CD images for basically the cost of the media (and shipping). Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't mount DVD any more
On Wednesday 27 October 2004 19:03, Tong wrote: > Hi, > > I used to be able to mount my dvd, but not now any more. > What did you change in between the times when you could mount it and when you couldn't? Every detail you can remember is important. > Here is my fstab: > > $ grep dvd /etc/fstab > /dev/dvd/mnt/dvdauto noauto,user > Can you post the full listing of the device node? > When I mount explicitly, I get: > > % mount -t iso9660 /dev/dvd /mnt/dvd/ > mount: wrong fs type, bad option, bad superblock on /dev/dvd, >or too many mounted file systems >(could this be the IDE device where you in fact use >ide-scsi so that sr0 or sda or so is needed?) > > % mount -t iso9660 /dev/sr0 /mnt/dvd/ > mount: block device /dev/sr0 is write-protected, mounting read-only > mount: No medium found > > What I can do? > Hmm, why did you use /dev/sr0? Is /dev/dvd a link pointing to it? If it is, then please post the full listing of /dev/sr0. If it's not, indicate why you think /dev/sr0 is the proper device node. The error "No medium found" means mount thinks the drive is correct, but there's no readable disk in it. What disk are you trying to mount? Don't try to mount a music CD. Make sure whatever disk you're using is valid, or else you'll never get this error to disappear. Do you have a known good data disk you can try? > Here is my kernel modules: > > $ lsmod | grep -Ei 'scsi|cd|dvd|ide' > ide-scsi8464 0 (autoclean) > scsi_mod 85312 4 (autoclean) [sr_mod sg sd_mod ide-scsi] > ide-cd 27936 0 > cdrom 25056 0 [sr_mod ide-cd] > ide-detect 288 0 (autoclean) (unused) > ide-disk 12512 12 (autoclean) > ide-core 94108 12 (autoclean) [ide-scsi ide-cd ide-detect > sis5513 ide-disk] > > Thanks > > tong Oh, yeah, what kernel are you running? Are you running devfs, or udev? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with sound (esound) since a few days
On Thursday 28 October 2004 02:55, Uwe Dippel wrote: > Though I didn't change anything on purpose; just the usual upgrades, I > lost my sound a few days ago. > Only today is the time to check it: > > esd doesn't start any longer (it always did): > > $ esd & > [1] 28425 > $ /dev/dsp: No such device > /dev/dsp is the oss sound device, which makes me think esd is configured to use oss. Have you tried configuring esd to use alsa instead? > > Esound is and remains installed: > > # apt-get install esound > Reading Package Lists... Done > Building Dependency Tree... Done > esound is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > > Quite a few modules are loaded: > > # lsmod | grep snd > snd_intel8x0m 20264 0 > snd_intel8x0 36460 0 > snd_ac97_codec 70020 2 snd_intel8x0m,snd_intel8x0 > snd_pcm_oss55048 0 > snd_mixer_oss 20096 1 snd_pcm_oss > snd_pcm98728 3 snd_intel8x0m,snd_intel8x0,snd_pcm_oss > snd_timer 25668 1 snd_pcm > snd_page_alloc 11752 3 snd_intel8x0m,snd_intel8x0,snd_pcm > gameport4704 1 snd_intel8x0 > snd_mpu401_uart 7968 1 snd_intel8x0 > snd_rawmidi25156 1 snd_mpu401_uart > snd_seq_device 8200 1 snd_rawmidi > snd57156 10 > snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_p >cm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore > 10336 1 snd > These are alsa modules, but I notice that you've loaded the pcm oss emulation module, which means using oss should still work. > > Finally, the lspci -v gives me: > > :00:1f.5 Multimedia audio controller: > Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller > (rev 01) > Subsystem: Dell: Unknown device 0139 > Flags: bus master, medium devsel, latency 0, IRQ 7 I/O ports at > d800 [size=256] > I/O ports at dc40 [size=64] > Memory at faeff800 (32-bit, non-prefetchable) [size=512] Memory > at faeff400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] > Power Management version 2 > > > Any help ? Are you using udev or devfs? If udev, is the daemon running? /dev/dsp should get created by udev when you load the snd_pcm_oss module. I don't have a computer running devfs to check, but I would imagine it's largely the same. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ftp clients
On Monday 01 November 2004 14:41, Richard Lyons wrote: > Any recommendations for convenient ftp client for uploading web pages, > galleries, etc., and for updating the same? > > I used to use gftp -- but it has become cranky (in Sarge, under icewm, > it is liable to crashes, cannot use bookmarks properly, etc.), and I > prefer not to have to load up all that gnomery if possible anyway. > > I tried xftp, but it seems dysfunctional (I can log onto remote > computer, but cannot actually make anything appear in xftp's windows, > cannot cause any command to be executed). > > I tried ncftp2, which is ok, as far as it goes. > > I tried lftp and plain ftp, but uploading 40 files takes a while and a > good bit of concentration. > > I'd really like a mc-like display, or a simple X-windows app. I just > went to examine mc, and found it has an ftp capability, but I don't > seem to be able to actually upload anything with it. I get a > permissions problem that was not present with ftp or lftp. > > Does anybody here have a favorite they'd like to recommend? > > TIA > If you're using KDE, you can use your favorite HTML editor and bookmark the FTP site in the file open dialog. Just enter the FTP information in the "often used folders" bar (the one at the top), in the form ftp://[EMAIL PROTECTED] You can then work with the files on the FTP site as if they're local. As for uploading a bunch of files, you could use Konqueror. Split your view in half, point one half at your local files, and the other put ftp://[EMAIL PROTECTED] in the location bar, and then drag and drop. You can also save your view as a profile, including the locations, so all you have to do is load a profile and your FTP site will come up automatically. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
On Tuesday 02 November 2004 06:02, [EMAIL PROTECTED] wrote: > Hello all, > > I'm a Linux newbie. Been trying RedHat, Fedora, Mandrake distros and > finally thought of something more serious so here I am. So far I was used > to go for an Ext3 filesystem for my 'root' and 'home' partitions. Very > convenient, as I don't know a lot about the other exotic filesystems > available with Linux. But here, installing a very freshly downloaded set > of Debian cd's, the installer did not offer me the 'EXT3' choice. The > best I could get was 'EXT2'. How comes ? > Because the modules for ext3 (and other file systems) have not been loaded. If you want to install on ext3, you can download the module floppy, and load it before you partition your disk. You will then see the option to choose ext3. In this manner, you can also make other filesystems available, such as xfs and reiserfs. Also, note that it is trivial to upgrade an ext2 file system to ext3 by using the tune2fs program. This can be done at any time. > By the way I find it kind of awkward that the default kernel offered by > Debian is a 2.2 (a pain in the arse if you think about setting up a sound > device, as Alsa is not included). > > Could anyone enlighten me with some explanation ? > > Thanx, > > Vince. Once you have Debian installed, you can install a newer kernel. Woody has 2.4 series kernels available, though I don't recall what the latest is. Of course, you could also follow the recommendation of the others on this list and download and install Sarge. It's what I would do. But, if you have a reason not to, then maybe the above information will help. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kjournald high cpu usage
On Monday 01 November 2004 10:18, Stephan Zehrer wrote: > Hi, > > i have following problem with sarge 2.6.8 kernel and ext3. > > When the xserver is running the cpu usage is periodically very high > so it blocks for a second and no normal working is possible. > > The harddisk is running in DMA mode and the pc is fast enough. > (i did not have the problem with 2.4...) > > Any idea? > > bye Steve What is the nice value of X? If it's -10, set it to 0. The 2.6 scheduler doesn't need X niced to -10, but it was useful in 2.4. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with QT-applications
On Monday 01 November 2004 06:57, Stephan Palmer wrote: > Hi Debian User Usegroup, > > since one of my recent dist-upgrades, KDE / QT - applications crash right > away on my debian unstable system. If I change the LC_CTYPE-locale-value > from "en_US.ISO-8859-15" to "C", they start again normally. Does anyone > of you people have an idea whats causing this ? > > Thank you very much, > Stephan Palmer Hi Stephan, You're more likely to get an answer if you post some debugging output. Either start an application in debug mode, or use strace (or both) and post the results. Otherwise, only someone who's had the same problem can help you, or else they can only guess. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with QT-applications
On Tuesday 02 November 2004 14:54, Stephan Palmer wrote: > On Tue, 02 Nov 2004 23:10:09 +0100, Justin Guerin wrote: > > On Monday 01 November 2004 06:57, Stephan Palmer wrote: > >> Hi Debian User Usegroup, > >> > >> since one of my recent dist-upgrades, KDE / QT - applications crash > >> right away on my debian unstable system. If I change the > >> LC_CTYPE-locale-value from "en_US.ISO-8859-15" to "C", they start > >> again normally. Does anyone of you people have an idea whats causing > >> this ? > >> > >> Thank you very much, > >> Stephan Palmer > > > > Hi Stephan, > > > > You're more likely to get an answer if you post some debugging output. > > Either start an application in debug mode, or use strace (or both) and > > post the results. Otherwise, only someone who's had the same problem > > can help you, or else they can only guess. > > > > Justin Guerin > Hi Justin, > > thank you very much for your hint! > > A strace output of a crashing kwrite-application can be found at: > > http://www.uni-koblenz.de/~stpalmer/kwrite_strace.txt > > A strace output of non-crashing kwrite after "export LC_CTYPE=C" can be > found at: > > http://www.uni-koblenz.de/~stpalmer/kwrite_strace_working.txt > > And the problem description again: > > "Hi Debian User Usegroup, > > since one of my recent dist-upgrades, KDE / QT - applications crash right > away on my debian unstable system. If I change the LC_CTYPE-locale-value > from "en_US.ISO-8859-15" to "C", they start again normally. Does anyone > of you people have an idea whats causing this ? > > Thank you very much, > Stephan Palmer" > > Can anybody of you help me - with those outputs ? That would be great. > > Thanks again, > Stephan Palmer > This is just a guess, but I think you might have a problem with fonts. Just before the SIGSEGV, there's a note about openoffice fonts. You might want to check and see if there's a problem with the KDE fonts you've chosen supporting your locale. Hopefully, someone more knowledgeable can shed some light on the problem. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: aptitude keeps trying to replace my vim-gtk and ftpd
On Wednesday 03 November 2004 01:02, Micha Feigin wrote: > For some reason aptitude constently (every apgrade) tried to replace my > vim-gtk with vim-tcl and ftpd with pure-ftpd, any ideas why? > > I don't have any pinning setup. I would guess that you have some packages installed that recommend or suggest vim-tcl or pure-ftpd, and there's possibly an aptitude setting that asks aptitude to install suggested or recommended packages. Since vim-tcl replaces vim-gtk, aptitude would want to install vim-tcl and remove vim-gtk. However, if vim-gtk was not installed automatically, then it shouldn't be trying to do this. One reason it might try, however, is because vim-tcl provides something that vim-gtk doesn't. If the version of both that aptitude is dealing with don't both provide gvim, then there's a package bug in there somewhere. If you want to track this down, look at the reverse depends on vim-tcl, until you come to a package you installed. Perhaps it is the culprit. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: aptitude keeps trying to replace my vim-gtk and ftpd
On Wednesday 03 November 2004 12:35, Wayne Topa wrote: > Jules Dubois([EMAIL PROTECTED]) is reported to have said: > > On Wed, 03 Nov 2004 10:54:56 -0500, Wayne Topa wrote: > > > I just ran aptitude and it got "The following packages are unused and > > > will be REMOVED". There are 8 packages it wants to remove, one of > > > which is bluefish, which I am using as I run aptitude.(?) > > > > Bluefish is an HTML editor based on GTK, not an aptitude helper. Or > > did you mean you were running the two applications at the same time? > > Yes runnig bluefish editing my home web page. > > > > A lot of people swear by aptitude but this behavior has made me swear > > > _at_ it more and more. > > > > If you want to keep bluefish, tell aptitude you installed it > > "manually". > > I didn't install it manually. I had a total system wipeout about a > month ago and got the 14 disk Sarge release disks to get back online. > It was part of the workstation install. BTW I have been running > Debian since '94 and I have never had as many problems with an > installation as I did this time. Still working on getting everything > I had before the melt-down working again (over 2 weeks now). > Note that if you use aptitude to install the package "gnome", then all of the dependencies of that package will be tagged as automatically installed, and when you request that "gnome" be removed, aptitude will remove all the automatically installed dependencies, too (provided they're not needed by a manually installed package). This behavior is great when it's exactly what you want, and no worse than apt-get's when you don't. > > > There _might_ be some good reason for the way aptitude doese > > > things but I can't find them. > > > > Bluefish is marked as "automatically installed", and since > > (apparently) nothing you've installed "manually" depends on it, > > aptitude is removing it for you. > > AFAIK aptitude installed it in the first place. What I don't > understand is, how did it decide I wasn't using it? ie: > "The following packages are unused" ??? As bluefish is an HTML > editor I wonder what I should install that could/would smarten up > aptitude? > Any package that depends on bluefish would do it. Another, easier way, is to mark the package as manually installed. Then, aptitude will never try to remove it in this manner. > > > I would appreciate any explaination for this bizarre behaviour. > > > > What you're describing is a feature of aptitude. You can stop it, > > easily, from removing bluefish if you really wanted to keep > > bluefish. There may be a way to stop aptitude from removing > > "unused" packages, but since I want it to do that, I haven't > > checked. > > > > There's nothing bizarre involved. > > Well it struck me a bit odd that I had bluefish runing an edit of my > web page and aptitude was somehow informed that it wasn't being used. > aptitude has a different definition of the word "used" (fortunately, it uses the commonly accepted definition of the word "is"). "Used", to aptitude, means that a package that you manually installed depends on it. Aptitude doesn't care if the application is running, it only checks if any packages installed on your system depend on bluefish (or whatever package). If there are none (or all the ones it finds were automatically installed to satisfy dependencies), it tries to remove the package. > In the two weeks I've been trying to get back to where I was, apitiude > has removed then installed then removed over 50 Meg of packages. > Thank God most were on the CD set! > > Thanks for your reply. I think I'll just remove aptitude and keep > doing the dselsct update ; apt-get dist-upgrade. Seems a bit more > understandable then what I have seen from aptitude. > > Thanks again > > Wayne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: aptitude keeps trying to replace my vim-gtk and ftpd
On Wednesday 03 November 2004 13:52, Erik Steffl wrote: > Wayne Topa wrote: > > Jules Dubois([EMAIL PROTECTED]) is reported to have said: > >>On Wed, 03 Nov 2004 10:54:56 -0500, Wayne Topa wrote: > >>>I just ran aptitude and it got "The following packages are unused and > >>>will be REMOVED". There are 8 packages it wants to remove, one of > >>> which is bluefish, which I am using as I run aptitude.(?) > > ... > > >>If you want to keep bluefish, tell aptitude you installed it > >> "manually". > > > > I didn't install it manually. I had a total system wipeout about a > >AFAIK aptitude considers the package intentionally installed if you > do installation using aptitude. Otherwise it will try to remove the > package (if nothing else depends on it). > Not exactly. Aptitude considers the package intentionally installed if you specifically request it, like doing "aptitude install bluefish" from the command line, or selecting it from the interactive interface. However, if you do "aptitude install gnome", bluefish will be installed as a dependency of gnome, and will be marked as automatically installed. Aptitude will try to clean up after itself by removing the package when all packages that bluefish depends on (and are manually installed) are removed. >to fix it just hit '+' (ask aptitude to install it) when it tries to > remove it. From then on it will know you want the package. > >I guess the underlying problem is that apt-get doesn't differentiate > between packages installed as a dependency and packages installed > explicitly by user so aptitude has nothing to decide whether you > installed the package. > > erik Actually, aptitude should consider all packages installed with apt-get (and other non-aptitude installed packages) as manually installed. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How do I know what sound system I'm using?
On Wednesday 03 November 2004 08:57, icebiker wrote: > I'm trying to sort out an arts problem (which is that I can't get it to > listen to my sound card's line in). I'm thinking it's a mixer problem. > > I'm using whatever sound system the sarge install gave me, but how do I > know what it is? > to find out, use lsmod. If you see a bunch of snd* modules, you're using alsa. If you can't tell, use locate to find the modules you do have loaded. OSS modules are in .../kernel/sound/oss/ > - kmix says it's using OSS. How do you know this? I couldn't find anything in kmix that told me whether it was using alsa or oss. I'm curious, because I'd like to know what my kmix says I'm using. > - the KDE Info center says I'm using ALSAv1.0.4 emulation mode emulation mode means alsa is emulating the oss interface. So, applications that only know oss talk to alsa, and alsa translates from oss speak to alsa speak, and plays the sound (or whatever). > - lsmod says I've got snd_mixer_oss loaded, but I think that's an alsa > module. > You are correct, it's an alsa module, but its job is to provide a mixer interface to oss speaking programs. > So I think I've got alsa, but I'm afraid to install alsa-utils in case I > break something. > > /icebiker Don't be afraid to install alsa-utils. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't use kb3 to copy cd's.
On Thursday 04 November 2004 16:09, Damon Chesser wrote: > I have two devices: hdc > cd writer, hdd > cd reader. I can play audio > cd's from hdd, I can mount cd's with mp3's and play them. I can burn > ISO's on hdc or make data cd's with hdc using k3b. I never or almost > never copy a cd. When I tried copying a cd from hdd to hdc via k3b, k3b > reports the cd is empty medium. Different cd's, different types of > data. Correct devices set up in k3b, using generic-mmc for cdrdao > driver for the burner and the reader. Problem pursists as root or > user. What am I missing? I have R&R'd the reader with a different > reader, same problem. If you need more info, please ask, I have tried > to provide as much as needed. > > -- > Damon L. Chesser > [EMAIL PROTECTED] You might want to rearrange your hardware after reading about the -immed option in the cdrecord man page: -immed Tell cdrecord to set the SCSI IMMED flag in certain commands (load/eject/blank/close_track/close_session). This can be useful on broken systems with ATAPI harddisk and CD/DVD writer on the same bus or with SCSI systems that don't use disconnect/reconnect. These systems will freeze while blanking or fixating a CD/DVD or while a DVD writer is filling up a session to the minimum amount (approx. 800 MB). Setting the -immed flag will request the command to return immediately while the operation proceeds in the background, making the bus usable for the other devices and avoiding the system freeze. This is an experimental feature which may work or not, depending on the model of the CD/DVD writer. A correct solution would be to set up a correct cabling but there seem to be notebooks around that have been set up the wrong way by the manufacturer. As it is impossible to fix this problem in notebooks, the -immed option has been added. A second experimental feature of the -immed flag is to tell cdrecord to try to wait short times while writing to the media. This is expected to free the IDE bus if the CD/DVD writer and the data source are connected to the same IDE cable. In this case, the CD/DVD writer would otherwise usually block the IDE bus for nearly all the time making it impossible to fetch data from the source drive. See also minbuf= and -v option. Use both features at your own risk. If it turns out that it would make sense to have a separate option for the wait feature, write to the author and convince him. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [CONFUSED NEWBIE] Cron
On Friday 05 November 2004 11:49, Joseph wrote: > Hi folks. > > This is probably very simple stuff, but I'm thoroughly confused. I > have an "off-the-shelf" Debian installation provided by my ISP. When > I do a ps -ef I get > (amongst other things) the following > root 195 1 0 Oct28 ?00:00:01 /usr/sbin/cron > All fine and normal so far. > Now, according to the manual to have cron services I should be running > a cron daemon called crond. Lo and behold whereis returns > # whereis crond > crond: > Still normal. > Now, "cron" is not "crond" I apparently don't even have a "crond" > software installed. > I added a new line to crontab: > 0 0 * * * root /usr/lib/cgi-bin/send_hit_count.cgi > Oops. Check out the man page for cron and especially crontab(5). > 1. send_hit_count.cgi apparently is not being executed. It works > interactively, but there are no messages that would indicate that it > was executed by cron. What do I need to do, in order to have cron > execute send_hit_count.cgi? > Fix your crontab entry above to: 0 0 * * * /usr/lib/cgi-bin/send_hit_count.cgi > 2. What is /usr/sbin/cron doing there? It seems to forever be in > memory, and I do occassionally receive CRON email messages with > reports, such as > /etc/cron.daily/logrotate: > > It is waiting until the time comes to start a job. If you happen to do a ps while a cron job is running, you'll see CROND. > 3. Do I need to install crond? > How do I do that? > It is installed, as evidenced by the cron messages you get. > 4. Should I get rid of the cron process documented above? > Nope. > TIA, > Joseph Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't use kb3 to copy cd's.
On Friday 05 November 2004 15:21, Damon wrote: > Justin Guerin wrote: > >On Thursday 04 November 2004 16:09, Damon Chesser wrote: > >>I have two devices: hdc > cd writer, hdd > cd reader. I can play audio > >>cd's from hdd, I can mount cd's with mp3's and play them. I can burn > >>ISO's on hdc or make data cd's with hdc using k3b. I never or almost > >>never copy a cd. When I tried copying a cd from hdd to hdc via k3b, > >> k3b reports the cd is empty medium. Different cd's, different types > >> of data. Correct devices set up in k3b, using generic-mmc for cdrdao > >> driver for the burner and the reader. Problem pursists as root or > >> user. What am I missing? I have R&R'd the reader with a different > >> reader, same problem. If you need more info, please ask, I have tried > >> to provide as much as needed. > >> > >>-- > >>Damon L. Chesser > >>[EMAIL PROTECTED] > > > >You might want to rearrange your hardware after reading about the -immed > >option in the cdrecord man page: > >-immed Tell cdrecord to set the SCSI IMMED flag in certain commands > >(load/eject/blank/close_track/close_session). This can be useful on > >broken systems with ATAPI harddisk and CD/DVD writer on the same bus or > >with SCSI systems that don't use disconnect/reconnect. These systems > > will freeze while blanking or fixating a CD/DVD or while a DVD > > writer is filling up a session to the minimum amount (approx. 800 MB). > > Setting the -immed flag will request the command to return > >immediately while the operation proceeds in the background, making > > the bus usable for the other devices and avoiding the system freeze. > > This is an experimental feature which may work or not, depending on > > the model of the CD/DVD writer. A correct solution would be to set up > > a correct cabling but there seem to be notebooks around that have been > > set up the wrong way by the manufacturer. As it is impossible to fix > > this problem in notebooks, the -immed option has been added. > > A second experimental feature of the -immed flag is to > >tell cdrecord to try to wait short times while writing to the media. > > This is expected to free the IDE bus if the CD/DVD writer and the data > > source are connected to the same IDE cable. In this case, the CD/DVD > > writer would otherwise usually block the IDE bus for nearly all the > > time making it impossible to fetch data from the source drive. See > > also minbuf= and -v option. > > > > Use both features at your own risk. If it turns out > > that it would make sense to have a separate option for the wait > > feature, write to the author and convince him. > > > >Hope that helps, > >Justin Guerin > > It kinda helps :) I am not (or am not supposed to be using) scisi > emulation. I am using a 2.6.8.1-k7 image from debian, so maybe somehow > scsi is emulating, only the devices do show up as hdd and hdc, both on > the same controler. How can I check for scsi emulation. I don't think > I can turn it off in the kernel as I use a thumb drive which does show > up as a scsi device (sda1 FWIW). I am leaning toward a kernel config > problem, but I don't know what it would be. Did you try copying the CD with the -immed flag? If so, what happened? Did you try moving your CD writer (or reader) to the other IDE bus? If so, what happened? SCSI emulation is not your problem. Your problem is having the reader and writer on the same IDE bus. However, to check for SCSI emulation, check your boot loader to see if you've appended the option hdx=ide-scsi. Given that you're accessing the drives as hdc and hdd, which are IDE device names. Justin Guerin p.s. please reply to the list, as I'm subscribed and more people can help than just me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.8-1-686 unable to mount root
On Thursday 04 November 2004 20:11, Eddy Jacob wrote: > Hi everyone, > > I'm running debian, sarge. I installed the OS from Knoppix 3.4. I want > to use kernel 2.6.8, but I've got a problem on booting > kernel-image-2.6.8-1-686. I got this: > > Kernal panic: VFS: Unable to mount root fs on unknown-block(3,7) > > Currently I'm using kernel 2.4.26 default from Knoppix. I also got > similar error when trying kernel-image-2.4.26.-1-686. I really don't > know how to get it working. > I've tried googling the web and searching all debian's list archive, > and found many pages related to that specific error, but the solutions > suggested were to compile the kernel with file system driver compiled > and something about MSDOS partition support built into the kernel not > as module. > > But I don't want to compile the kernel. What I don't understand is, > why the package I downloaded from debian sarge, causes that error? Is > it really because of the file system driver not compiled into the > kernel? I thought that packages from sarge should be common enough so > that user can just download them and use it. > > Also, the kernel-image downloaded from debian is unable to use the > vesafb (I guess). my vga option in lilo.conf is vga=791, which is > working under knoppix default. > > BTW, my lilo.conf is like: > > image=/boot/vmlinuz-2.4.26 > label="Linux" > initrd=/boot/initrd.img-2.4.26 > append="ramdisk_size=50 lang=de apm=power-off hda=scsi > hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce" > read-only > > image=/boot/vmlinuz-2.4.26-1-686 > label="Linux-686" > vga=extended > initrd=/boot/initrd.img-2.4.26-1-686 > append="ramdisk_size=50 lang=de apm=power-off hda=scsi > hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce" > read-only > > image=/boot/vmlinuz-2.6.8-1-686 > label="Linux-2.6" > vga=extended > initrd=/boot/initrd.img-2.6.8-1-686 > append="ramdisk_size=50 lang=en apm=power-off hda=scsi nomce" > read-only > > I don't have a clue to why all hdx is equal to scsi. and what > apm=power-off means and nomce? > hdx=scsi: There's a big debate on that one, but basically, it's for CD burning. If you don't need to burn CDs, you probably don't need it. apm=power-off: This is a switch meant to make your computer power completely off when you choose shutdown from the gui menu, or when you issue the shutdown command from the command line. If your computer is really old, your bios won't support it, and it won't work anyway. If you don't care, take it out. Your computer may work anyway. nomce: "This command disables self-diagnosis checks performed on the CPU. The kernel enables self-diagnosis on the CPU by default (called Machine Check Exception). On some older Compaq machines, this check is run too often and may need to be disabled." Some of this information was gleaned from this page: http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/install-guide/ch-bootopts.html > Anyone have a solution to this? I've been trying to find answer to > this for a week. Many thanks. You did run lilo after you installed the new kernels, right? You did tell lilo that your kernels use an initrd, right? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.8-1-686 unable to mount root
On Saturday 06 November 2004 02:35, Eddy Jacob wrote: > On Fri, 05 Nov 2004 16:49:23 -0700, Justin Guerin <[EMAIL PROTECTED]> wrote: > > On Thursday 04 November 2004 20:11, Eddy Jacob wrote: > > > Hi everyone, > > > > > > I'm running debian, sarge. I installed the OS from Knoppix 3.4. I > > > want to use kernel 2.6.8, but I've got a problem on booting > > > kernel-image-2.6.8-1-686. I got this: > > > > > > Kernal panic: VFS: Unable to mount root fs on unknown-block(3,7) > > > > > > Currently I'm using kernel 2.4.26 default from Knoppix. I also got > > > similar error when trying kernel-image-2.4.26.-1-686. I really don't > > > know how to get it working. > > > I've tried googling the web and searching all debian's list archive, > > > and found many pages related to that specific error, but the > > > solutions suggested were to compile the kernel with file system > > > driver compiled and something about MSDOS partition support built > > > into the kernel not as module. > > > Yes, this will likely fix your problem. However, it is not the only way. Since you don't want to compile your own kernel, you can use the initial ram disk to hold the modules. > > > But I don't want to compile the kernel. What I don't understand is, > > > why the package I downloaded from debian sarge, causes that error? Is > > > it really because of the file system driver not compiled into the > > > kernel? I thought that packages from sarge should be common enough so > > > that user can just download them and use it. > > > This error might be happening because Knoppix is not Debian. Last time I did a Knoppix hard disk install, it used XFS. XFS is provided as a file system driver module in some kernels (I'm pretty sure Sarge has it), but you have to make sure that you add it to the initial ram disk in order to boot properly. Stock kernels don't compile XFS into the kernel because they want to keep the kernel lean, and it's not explicitly required to have your file system driver compiled in statically in order to use it. Stock kernels are all about flexibility, so everything is compiled as a module. It's just that the file system module is harder to use than the rest. In any case, I could be wrong, if your file system isn't XFS. What does /etc/fstab say? Also, are those modules in the initial ram disk? > > > Also, the kernel-image downloaded from debian is unable to use the > > > vesafb (I guess). my vga option in lilo.conf is vga=791, which is > > > working under knoppix default. > > > > > > BTW, my lilo.conf is like: > > > > > > image=/boot/vmlinuz-2.4.26 > > > label="Linux" > > > initrd=/boot/initrd.img-2.4.26 > > > append="ramdisk_size=50 lang=de apm=power-off hda=scsi > > > hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce" > > > read-only > > > > > > image=/boot/vmlinuz-2.4.26-1-686 > > > label="Linux-686" > > > vga=extended > > > initrd=/boot/initrd.img-2.4.26-1-686 > > > append="ramdisk_size=50 lang=de apm=power-off hda=scsi > > > hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce" > > > read-only > > > > > > image=/boot/vmlinuz-2.6.8-1-686 > > > label="Linux-2.6" > > > vga=extended > > > initrd=/boot/initrd.img-2.6.8-1-686 > > > append="ramdisk_size=50 lang=en apm=power-off hda=scsi > > > nomce" read-only > > > > > > I don't have a clue to why all hdx is equal to scsi. and what > > > apm=power-off means and nomce? > > > > hdx=scsi: > > There's a big debate on that one, but basically, it's for CD burning. > > If you don't need to burn CDs, you probably don't need it. > > apm=power-off: > > This is a switch meant to make your computer power completely off when > > you choose shutdown from the gui menu, or when you issue the shutdown > > command from the command line. If your computer is really old, your > > bios won't support it, and it won't work anyway. If you don't care, > > take it out. Your computer may work anyway. > > nomce: > > "This command disables self-diagnosis checks performed on the CPU. The > > kernel enables self-diagnosis on the CPU by default (called Machine > > Check Exception). On some old
Re: Can't burn CDs since kernel 2.6.7 - am I the only one?
On Tuesday 09 November 2004 11:33, Alan Chandler wrote: > Following my upgrading to linux 2.6.7 I have been unable to burn a CD. > This is still true now, even as root, with kernel 2.6.9, having also > tried 2.6.8 > > I know there was a lot of fuss with cdrecord and 2.6.8, but my problems > seem to predate that. > > What happens, when I try to do any simple command is that one of the > child processes of cdrecord seems to be stuck in the D state in the > kernel. That is, its done an uninterrruptable IO request which has not > been detected as completed by the kernel driver (ide-cd?). This means > you can't kill the process (even with kill -9) and the only way to get > rid of it is with a reboot. (there was a recent discussion on processes > getting into this state on the kernel mailing list). > > Just so everyone is clear of the situation, the second IDE channel has > two cdrom like drives. /dev/hdc is the cdrw device which I am trying to > use to burn, /dev/hdd is a dvd device. > > I used the simple command > > cdrecord dev=ATA:1,0,0 blank=fast > > and (with a Rewriteable CD in the drive) it then preceeds to hang. > > As I can reboot into Windows XP and burn CDs perfectly, and (at least for > me) means I have been with a substandard system for a couple of months > now. Google around as hard as I try, I cannot seem to find any indication > that someone else has such a problem (other than the debian bug report > 265747) > > It looks to me to be some form of kernel error in the driver. Has anyone > any idea, even if have have to rebuild the kernel, how I can debug this? > > I had the same problem using 2.6.6 and a USB DVD writer burning CDs with K3B as the frontend. Switching to a CD writer, I haven't had problems. I don't have the DVD writer anymore, so I can't check it, and I have no idea what was going wrong, but you should know that you are not alone. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't burn CDs since kernel 2.6.7 - am I the only one?
On Wednesday 10 November 2004 08:37, Brian Pack wrote: > On Wed, 2004-11-10 at 10:06 -0500, Colin wrote: > > Justin Guerin wrote: > > > On Tuesday 09 November 2004 11:33, Alan Chandler wrote: > > > > > > I had the same problem using 2.6.6 and a USB DVD writer burning CDs > > > with K3B as the frontend. Switching to a CD writer, I haven't had > > > problems. I don't have the DVD writer anymore, so I can't check it, > > > and I have no idea what was going wrong, but you should know that you > > > are not alone. > > > > My problem is just the opposite. I have both an IDE CD writer and an > > IDE DVD writer. k3b recognizes the DVD writer as a DVD writer ONLY > > (not a CD writer) and recognizes the CD writer as a CD-ROM only. I > > can't write CDs with k3b but I can with cdrecord. Weird. I'm using > > 2.6.9. > > Which version of k3b are you using? This was a problem up to v. 0.11.5. > Current is 0.11.17. Using the Debianized kernel from > kernel-source-2.6.8-4 or newer, and k3b 0.11.17, I no longer have this > problem. Well, right now, I'm using 0.11.17, but I don't know what I was running when I had the problem with the DVD writer. I'll see if I can get my hands on it and try again. I'm still on 2.6.6, however. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: advice on updating kernel image
On Wednesday 10 November 2004 11:20, Randall Smith wrote: > Hi, > > I need some advice on updating my kernel. I currently have kernel > 2.4.25-1 installed from the initial sarge installation and would like to > upgrade to the current kernel version (2.4.27). The machine is a DELL > POWEREDGE 2500 that uses aicraid, aic7xxx modules. These modules are > required to boot and I am concerned that if I upgrade the kernel using > aptitude install kernel-imagexxx, I will not be able to boot. I'm not a > linux newbie, but I'm not very knowledgeable of the boot process. Any > help would be appreciated. > > Thanks. > > Randall Just make sure those modules are placed in the initial ram disk, and everything will be fine. Note that when you install a new kernel image using aptitude, your old kernel will still be bootable. Just remember to run lilo or update-grub before you reboot. That way, if anything goes wrong with your new kernel, you can boot your old one. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA modem
On Wednesday 10 November 2004 12:20, [EMAIL PROTECTED] wrote: > How can I tell if a modem is set up properly? > > If I insert the card I get the higher pitched beep and a message that > ttyS01 is a 16550A. Hmmm - is that good or bad? Does it mean that (when > I eventually get round to using the modem to dial up) everything is OK? > > Grateful for any light anyone can shed! > > Regards > > - Joe I believe you should get two beeps. If the second beep is a lower tone, I think that means configuration failed. One beep may mean the card was not detected at all, but don't quote me on that. Still, the fact that it reports ttyS01 as a 16550A is a good thing, as that's what happens on my notebook when I plug in a pcmcia modem. In any case, check your logs to see what exactly happened. I'd start with /var/log/syslog. If it looks like everything is OK, then fire up pppconfig, and have it autodetect your modem. If that doesn't work, post the relevant portion of your syslog, your kernel version, whether your using udev, devfs, or old style /dev, the chipset of your modem, and your relevant modules loaded, and someone one this list may be able to help you. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ext3 file system crash
On Tuesday 09 November 2004 21:36, Eddy Jacob wrote: > Hi all, > > Like the earlier post from other user, I also experienced this. I am > asking for help here or ideas. > > I installed knoppix 3.4 to harddisk (debian based option), kernel > 2.4.26, and using ext3 for all my file system. my etc/fstab: > > # filesystem mountpoint type options dump pass > /dev/hda7 / ext3 defaults,errors=remount-ro 0 1 > /dev/hda9 /var ext3 defaults,errors=remount-ro 0 1 > /dev/hda10 /tmp ext3 defaults,errors=remount-ro 0 1 > /dev/hda11 /home ext3 defaults,errors=remount-ro 0 1 > > proc /proc proc defaults 0 0 > /dev/fd0 /floppy autofs defaults,user,noauto,showexec,umask=022 0 0 > usbdevfs /proc/bus/usb usbdevfs defaults 0 0 > sysfs /sys sysfs defaults 0 0 > > one day, suddenly, my / file system crash after reboot. and I have to > answer lots of yes.. to fix the error. after that, I think some of > system files were deleted and I can get into the system anymore.. it > just hangs. after that, I've to reinstall knoppix, upgrading to sarge > again, etc. > > After some reading, I thought to set my file system check interval to > be every few days, every 3 mounts or 1 day. But, everytime, the root > (/) file system was checked, at 90%, there are some errors. some time > it was fixed with still some error, sometime it was clean. Until > today, the file root (/) system is never really clean after reboot. > > I don't know what is wrong with my PC, some time, the system reported > ext3fs error on console.. I can't remember the message. > > any help would be really appreciated. thanks. I would recommend installing smartmontools and checking the health of your hard drive. This many errors suggests hardware problems. You should not need to check your drives once a day. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upgrading KDE
On Wednesday 10 November 2004 19:15, downtime null wrote: > Hello Debian Users! > > Let me start by saying that I am new to Debian, not Linux. I'm not > familiar with some of the conventions and tools specific to Debian. I > switched to Debian because I've always heard great things about its > package management and I know that it uses binary packages (as opposed > to Gentoo, which has fantastic package management, but only uses > source). > > I would like to upgrade to at least KDE 3 (3.3 would be nice), but apt > is giving me fits. I'm sure it's something simple that I'm just > overlooking. When I type the command 'apt-get -f install kde', I get : > > Reading Package Lists... Done > Building Dependency Tree... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > > Since you only requested a single operation it is extremely likely that > the package is simply not installable and a bug report against > that package should be filed. > The following information may help to resolve the situation: > > Sorry, but the following packages have unmet dependencies: > kde: Depends: kde-core but it is not going to be installed >Depends: kde-amusements but it is not going to be installed > E: Sorry, broken packages > > The only line I have in my sources.list is : > > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > > I'm using testing because stable seems to use thoroughly tested but very > outdated packages. Shouldn't the '-f' switch cause apt-get to resolve > the dependencies? > > As an alternative, and I hate to even suggest this, is it generally > considered a Bad Thing (tm) to use RPMs in Debian? > > I'm having some other issues with my system, but I'd like to get this > resolved first and take things one step at a time. > > Any help in this matter is appreciated. > > Thanks. The nice thing about apt-get and its ilk is that they will keep recursing until all dependencies are solved or determined to be unsolvable. The not so nice thing is that the error messages won't recurse all the way down. What you tried to install, kde, is a metapackage. It depends on other packages, which you can see if you use "apt-cache show kde". Of those dependencies, kde-core and kde-amusements had problems, but the rest were OK. If you then type apt-get install kde-core kde-amusements, the output should tell you that one or more packages these depend on will not be installed. You can do this until you see the actual cause of the problem. Alternately, since kde is a metapackage, you could elect to install only the components you know you want, letting apt-get take care of the dependencies, but hopefully avoiding the broken package that's keeping all of kde from going in at once. Note that this is what makes testing and unstable different from stable: packages will be broken from time to time (though not that often). They usually get fixed quickly, though occasionally they have lasted a while. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: konqueror and supported protocols
On Tuesday 16 November 2004 05:40, Curt Howland wrote: > The KDE Info Center index has an entry for "Protocols". This is the > list of available "IO slaves" in Konqueror, like "http:/", "file:/", > "smb:/". Looking there now I see "fish:/" but also "ssh:/" is listed. > > I'm having problems right now with "smb:/" giving the message: > > An error occurred while loading smb:/: > > Could not start process Unable to create io-slave: > klauncher said: Error loading 'kio_smb'. > . > > "smb:/" worked last week, but I'm on Sid and there was a KDE upgrade > over the weekend and it seems to have broken. Oh well. Is it working > for anyone else? > > Curt- > > Hi Curt, I am not having this problem. The smb io_slave is from the package kdebase-kio-plugins, and I have version 3.3.1-2 installed, which is up to date as of today. I wonder if your Sid is completely up to date? I.e., have you done an apt-get upgrade recently? I have had problems before with KDE where apps don't launch correctly when I upgrade only KDE and its dependencies. There seem to be some dependencies that aren't mentioned, but I can never figure out what exactly they are. However, after an upgrade, things start to work again, even though the KDE versions didn't change. On the other hand, I get an illegal instruction error when I launch aptitude (in graphical mode, i.e. with no arguments). Otherwise, it works in command line mode. I'm completely up to date, so I don't know what's wrong there. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: advice on updating kernel image
On Monday 15 November 2004 15:20, Randall Smith wrote: > Justin Guerin wrote: > > On Wednesday 10 November 2004 11:20, Randall Smith wrote: [snip] > > Just make sure those modules are placed in the initial ram disk, and > > everything will be fine. > > That's what I'm uncertain about how to do. Do I have to do this > manually or will aptitude figure out what to do. I did not do this > manually when I installed Debian. > > If I have to do it manually, how do I go about it? How can I see what > is in my current initial ram disk? I'm lost on this subject. > > Randall > You have to do it manually. Start with man mkinitrd. It will tell you that you have to place the modules you want in your ram disk in the /etc/mkinitrd/modules file, and check the config file to make sure mkinitrd will place those files in the resulting image. For example, I boot a raid 1 root partition, using reiserfs, so mine includes the modules reiserfs, md, and raid1. After you edit the modules file, run mkinitrd, and point your boot loader at the new image. As for seeing what's in your current initial ram disk, I'm afraid I don't know. It is, however, an image, and you might possibly mount it using the loopback interface, but I've never done that. Justin Guerin [snip] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sound driver
On Tuesday 16 November 2004 15:48, Jason Rennie wrote: > In short: I can't play ogg files on my Debian Sarge (2.4.27) machine, > but I can if I boot off a Knoppix live CD (v3.6, kernel 2.4.27). > i.e. the drivers I have installed on my Debian Sarge machine aren't > working. I'd like to set things up to use the sound drivers that > Knoppix uses, but I don't know how. Does anyone out there know how > I'd go about doing this? Here's the output of /sbin/lsmod on Debian > Sarge: > > Module Size Used byTainted: PF > via82cxxx_audio21564 1 > ac97_codec 13300 0 [via82cxxx_audio] > uart401 6436 0 [via82cxxx_audio] > sound 57480 0 [via82cxxx_audio uart401] > soundcore 3940 4 [via82cxxx_audio sound] Ok, you're using the OSS modules > via82cxxx 10856 1 (autoclean) > This is for the IDE chipset (notice the dependence on ide-core). It's got nothing to do with sound, save the fact that it's made by the same company. > Here's lsmod output for Knoppix: > > Module Size Used byNot tainted > via82cxxx_audio19448 1 > ac97_codec 11916 0 [via82cxxx_audio] > uart401 6052 0 [via82cxxx_audio] > sound 55276 0 [via82cxxx_audio uart401] > soundcore 3428 4 [via82cxxx_audio sound] > OK, Knoppix is also using OSS. > My sound card is built into my Via motherboard. via82cxxx_audio and > via82cxxx appear to be the driver modules. The size of > via82cxxx_audio differs and Knoppix doesn't use via82cxxx. The size discrepency is most likely due to differing kernel versions. What kernel are you using in Sarge? How about in Knoppix? > But, I can't rmmod via82cxxx on Debian: > > [EMAIL PROTECTED]:~$ sudo rmmod via82cxxx > Password: > via82cxxx: Device or resource busy > This means that something is using the sound card. If I had to guess, it's your sound server. Do you have one running (esound, arts, etc?)? If you stop your sound server, then quit all applications which use sound (like your mixer, if it's running), you can unload the module. There's no reason to do this, however, unless you want to run Alsa instead. First things first, though. Let's get OSS running before you switch. > In case it's useful, here's the output of ogg123 (looks the same for > both Debian and Knoppix): > > Audio Device: OSS audio driver output > > Playing: ogg/king_crimson/sleepless_the_concise_king_crimson/red.ogg > Ogg Vorbis stream: 2 channel, 44100 Hz > Title: Red > Artist: King Crimson > Genre: 17 > Date: 1993 > Album: Sleepless (The Concise King Crimson) > > Any help would be much appreciated! > > Thanks, > > Jason Hmm, the above output would seem to suggest that ogg123 is actually working. If there isn't an error message you forgot to copy, how about turning up the volume via a mixer? > > P.S. Many thanks to Maurits van Rees and Wim De Smet for helping me > get this far! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sound driver
On Thursday 18 November 2004 07:59, Jason Rennie wrote: > On Wed, Nov 17, 2004 at 01:25:51PM -0700, Justin Guerin wrote: > > The size discrepency is most likely due to differing kernel versions. > > What kernel are you using in Sarge? How about in Knoppix? > > Both are 2.4.27 > > > Hmm, the above output would seem to suggest that ogg123 is actually > > working. If there isn't an error message you forgot to copy, how about > > turning up the volume via a mixer? > > Sorry, forgot to mention the details of the problem... the first > second of the song is repeated continuously. It works in the sense > that I get out sound and it is sound from the song that I'm trying to > play, but it only plays the first second, over-and-over again. > Imagine a CD or record that keeps skipping. > > Jason Sounds like you have a DMA or IRQ problem. Can you check which DMA and IRQ channels are assigned during Knoppix boot, and during Debian boot? You may have to tell the sound module to use a specific IRQ when it's loaded. I had to do the same thing with my ISA card, when I first configured it. I just went down the list of available IRQs before I got to one that worked. Hope that helps, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: weird pb
On Tuesday 29 June 2004 06:18, [EMAIL PROTECTED] wrote: > Hi, > > I have a really weird problem on one of my box (woody): > > [(14:15:00) Linux Wifix ~]$ ls > Segmentation fault > [(14:15:02) Linux Wifix ~]$ > > any idea? > > Aurel > This kind of thing will happen when libc is broken. Did you do anything that could modify libc? Or did you install coreutils from testing but libc from stable? If ls is the only program that's having this kind of trouble, it's possible that ls itself is corrupt. That could be because your disk is going bad, or ls has been trojaned (poorly). If neither of these is the case, we'll need more information, such as when it last worked and what happened in between then and now. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: arts problems
On Friday 02 July 2004 15:42, Roy Pluschke wrote: > Hi, > > I'm running sid with a 2.6 kernel and recently have noticed that the > sound quality through juk is horrible. I investigated further and it > seems to be an arts problem (all other apps which don't use arts sound > fine). I've tried modifying everything possible in the kde sound > configuration panel without any success. Is anyone else having this > problem? I sure miss juk. > > thanks in advance > RJP Hi Roy, I am sort of having the same problem. The sound quality through juk is OK, but it eats up 50-75% of my CPU, whereas piping XMMS through aRTS uses next to none. I remember seeing something about aRTS using a certain library by default that wasn't optimal, and the replacement suggested took my system CPU usage down from 50-75% to ~5%, but after an upgrade, the situation is back, and I can't find the original hint, nor recall what I did. :-( Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pppd authentication problem
On Thursday 08 July 2004 00:31, James Sinnamon wrote: > Dear Debian users, > > Until now, I have been accustomed to having ppp work without the need > to understand a great deal. > > However, I have not been able to get kppp to work on my new Debian > sarge/testing system in the same way it used to work on my previous > RedHat 9.0 system. > > In the log window, I see the word "CONNECT" after roughly 10 seconds, > but am immediately disconnected, seemingly before ppp even begins > to authenticate itself. The errors shown are: > > Jul 8 14:25:59 localhost pppd[1065]: The remote system is \ > required to authenticate itself > Jul 8 14:25:59 localhost pppd[1065]: but I couldn't find any \ > suitable secret (password) for it to use to do so. > Jul 8 14:25:59 localhost pppd[1065]: (None of the available \ > passwords would let it use an IP address.) > > A copy of ~/.kde/share/config/kppprc can be found at: > > http://www.sos.cable.nu/debian/debug/kppprc.txt > > Can anyone spot what is wrong or what is missing? > > BTW, is there a relationship between kppp and ppp? Does kppprc > have anything to do with the files in /etc/ppp/ ? ... or > with /etc/network/interfaces ? > > TIA > > James > Hi James, The problem is due to a change in pppd defaults. It used to not require the remote system to authenticate itself, but now it is required. You have a few options to fix this, including: Run kppp as suid root, and provide the option "noauth" Edit the default arguments of pppd and replace "auth" with "noauth". You will have to be root to do this. Hope that helps. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: My eth0 is gone
On Thursday 08 July 2004 13:25, * Tong* wrote: > Hi, > > Hysterically, after I reboot Debian, my eth0 device is gone. > > % networking start > eth0: ERROR while getting interface flags: No such device > > % ifconfig eth0 inet 192.168.0.99 up > SIOCSIFADDR: No such device > eth0: ERROR while getting interface flags: No such device > eth0: ERROR while getting interface flags: No such device > > Luckily, I managed to get it back. I'm just wondering, > > what could be the reason that I lost my eth0? I remove the > discover package, could it be the reason? Is discover package > really necessary? > No, discover isn't really necessary. In fact, it could possibly be the source of the problem, but that's only speculation. > I get it back by > > modprobe sis900 > depmod -a > > Can the effect last beyond next boot (and beyond)? > > Thanks You can make the module load each boot by adding "sis900" (without the quotes) to a line by itself in the /etc/modules file. That way, it will get loaded each boot. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fwd: Hello Justin
-- Forwarded Message -- Subject: Hello Justin Date: Wednesday 21 July 2004 07:02 From: tapan <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hi Justin, Cud you able to make pppd uphere is what I am facing I am using linux 2.0.x and want to test the existing pppd application. I have enabled TCP/IP in networking options, ppp in network device support. But after loading the image in MCF5249 (Motorola Coldfire board) and then executing 'pppd' with different options ..etc' nothing is happening. I am getting as > pppd pppd: The remote system is required to authenticate itself but I pppd: couldn't find any suitable secret (password) for it to use to do so. pid 8: failed 256 Can you give a try for the ppd application and tell me the procedure how to make this to work. Want to know where I am going wrong. Thanks Tapan --- Tapan, You will be much more likely to get useful answers if you post to the list, and don't email people individually. The problem you are having is because of the default option in newer versions of pppd. The "auth" option is set by default. Check out "man pppd" for details, but basically, you're requiring the remote system to authenticate itself, when you probably should not. Change that option to "noauth" and try again. Post to the list if you still have problems. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mkinitrd: RAID support requires raidtools2
On Thursday 22 July 2004 15:57, Alec Berryman wrote: > I'm trying to do software raid on a fresh install of Woody with a > 2.4.26 kernel. In order to load the software raid I need to make an > initrd image, so I installed initrd-tools. However, when I run > mkinitrd, I get the following message: > > # mkinitrd -o /boot/initrd.img-2.4.26 2.4.26 > /usr/sbin/mkinitrd: RAID support requires raidtools2 > > I've got raidtools2 installed (even though I am using mdadm). I have > the module 'md' specified in /etc/mkinitrd/modules. What can I do to > fix this error? One quick thing to try is adding raid1 (or whatever raid level you're running) to /etc/mkinitrd/modules. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: starting second md device at boot time
On Tuesday 27 July 2004 06:30, Richard Marshall wrote: > Hello, > > I have built a debian sarge system on a dell poweredge with a pair of > SCSI disks, but no Raid controller. I have sucessfully configured one md > raid 1 device (/dev/md0, mounted as the / partition) using the sarge > installer and the system is functioning very well. I am now trying to > create a second md raid 1 device on the remaing space on the disks > (approx 60 GB). > > I sucessfully create the raid array (/dev/md1) using mdadm, and a cat > /proc/mdstat show that the device has been created and is working > correctly. However, when I reboot the machine, the new raid device > doesn't start, and I have to go through the whole process again. > > How do I get this second raid device to start at boot time with the other > md device? > > TIA > > Rich Hi Rich, Just a few basic questions, since you always try the easy way first. Are your partitions that make up /dev/md1 marked as linux raid autodetect (FD)? Is your second raid device present in fstab? Once those two things are verified, post the boot up output related to the second raid array, and maybe we can help more. Also, post the output of /proc/mdstat after the boot. HTH. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: starting second md device at boot time
On Wednesday 28 July 2004 02:17, Richard Marshall wrote: > >Hi Rich, > > > >Just a few basic questions, since you always try the easy way first. > > Are your partitions that make up /dev/md1 marked as linux raid > > autodetect (FD)? Is your second raid device present in fstab? > > The partitions are marked as fd, and the array creates sucessfully. I > also have an appropriate entry in /etc/fstab. > Out of curiosity, what does the line look like? > Also, if I run 'mdadm --assemble /dev/md1 /dev/sda5 /dev/sdb5' after the > reboot, the the array appears again, and I can mount it without any > problems. > > >Once those two things are verified, post the boot up output related to > > the second raid array, and maybe we can help more. Also, post the > > output of /proc/mdstat after the boot. > > The output of /proc/mdstat before a reboot is: > > Personalities : [raid1] > md1 : active raid1 sda5[0] sdb5[1] > 60934400 blocks [2/2] [UU] > > md0 : active raid1 sda3[0] sdb3[1] > 8787456 blocks [2/2] [UU] > > unused devices: > > After reboot it is: > > Personalities : [raid1] > md0 : active raid1 sda3[0] sdb3[1] > 8787456 blocks [2/2] [UU] > > unused devices: > > > I have also run dpkg-reconfigure mdadm after creating the new array, and > I can't help feeling it something to do with this. I have tried putting > an appropriate entry into /etc/mdadm/mdadm.conf, but don't know what the > exact format should be. But here's what I have so far: > > DEVICE /dev/sda* /dev/sdb* > ARRAY /dev/md1 UUID=263f5308:d2877768:142f22b5:c434a317 > devices=/dev/sda5,/dev/sdb5 > Since you've got your raid going (after the manual start), you can create your config file automatically. Just issue the command "mdadm --detail --scan" and redirect the output to /etc/mdadm.conf. You'll then have to manually add the device line, and even though you can, I wouldn't use wildcards, I'd spell out each device involved in the raid. In your case, I'm guessing the file could end up looking like this (at least for md1): device /dev/sda5 /dev/sdb5 /dev/sda3 /dev/sdb3 array /dev/md1 UUID=263f5308:d2877768:142f22b5:c434a317 devices=/dev/sda5,/dev/sdb5 Of course, the last two lines are actually one line in the config file. Note that while you don't need a config file, without one "you'd need to specify more detailed information about an array on the command in order to activate it." [1] Also note that you only need one device line for the config file. You don't need one per array. > > I presume you mean the dmesg output, so relevant bits are below, but > there is no mention of the md device in there (part of the problem I > guess). The problem md device has xfs format on it and you can see that > failing to find the superblock(?) on the last line I've included: > > > Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 > md: md0 stopped. > md: bind > md: bind > raid1: raid set md0 active with 2 out of 2 mirrors > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Adding 979956k swap on /dev/sda2. Priority:-1 extents:1 > Adding 979956k swap on /dev/sdb2. Priority:-2 extents:1 > EXT3 FS on md0, internal journal > Real Time Clock Driver v1.12 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx hdc: GCR-8483B, ATAPI CD/DVD-ROM drive > ide1 at 0x170-0x177,0x376 on irq 15 > hdc: ATAPI 48X CD-ROM drive, 128kB Cache > Uniform CD-ROM driver Revision: 3.20 > Capability LSM initialized > device-mapper: 4.1.0-ioctl (2003-12-10) initialised: [EMAIL PROTECTED] > kjournald starting. Commit interval 5 seconds > EXT3 FS on sda1, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on sdb1, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > SGI XFS with ACLs, security attributes, realtime, large block numbers, no > debug enabled > SGI XFS Quota Management subsystem > XFS: SB read failed > > Other information: Kernel is sarge 2.6.7-1-686, > Lilo does the boot honours, and I'm sure that md is a module, not > compiled into the kernel (but how do I confirm?) > > Thanks again, > > Rich You can confirm that md is a module by either looking at /boot/config-2.6.7-1-686 or by looking at the output of lsmod. Either way, the raid capability is there, as your first raid array is built and mounted correctly
Re: starting second md device at boot time
850 active sync /dev/sda5 >0 0 850 active sync /dev/sda5 >1 1 8 211 active sync /dev/sdb5 > > file-srvdeb:/home/rich# mdadm -E /dev/sdb5 > /dev/sdb5: > Magic : a92b4efc > Version : 00.90.00 >UUID : 5c158e6e:dc2e6e64:ad9592f8:c72b0868 > Creation Time : Tue Jul 27 15:45:41 2004 > Raid Level : raid1 > Device Size : 60934400 (58.11 GiB 62.40 GB) >Raid Devices : 2 > Total Devices : 2 > Preferred Minor : 1 > > Update Time : Wed Jul 28 16:45:50 2004 > State : clean, no-errors > Active Devices : 2 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 0 >Checksum : dbdfe8c2 - correct > Events : 0.390 > > > Number Major Minor RaidDevice State > this 1 8 211 active sync /dev/sdb5 >0 0 850 active sync /dev/sda5 >1 1 8 211 active sync /dev/sdb5 > > > thanks again, > > Rich Hmm, it seems that your UUIDs output by mdadm after the raid is running do not match the ones you posted from the config file snippet. That is definitely a problem. I think you might need to change the values in the config file to match the values in the actual array. HTH Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: starting second md device at boot time
On Thursday 29 July 2004 02:21, Richard Marshall wrote: > > >Since you've got your raid going (after the manual start), you can > > > create your config file automatically. Just issue the command "mdadm > > > --detail --scan" and redirect the output to /etc/mdadm.conf. You'll > > > then have to manually add the device line, and even though you can, I > > > wouldn't use wildcards, I'd spell out each device involved in the > > > raid. In your case, I'm guessing the file could end up looking like > > > this (at least for md1): > > I discovered something very odd last night. The raid array starts when > the system is shutting down... Still can;t get it to start at boot time > though :( Were you able to build the XFS module into the initrd? If that didn't work, did dmesg change? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can apt* find var/cache/files?
On Saturday 31 July 2004 10:25, Brian Astill wrote: > Basicaly the question is in the subject line :-) > > I recently re-installed, saving my original home files and so on, > including the .deb files from /var/cache. I have put those files back > into /var/cache. > > Will apt or aptitude find those files, or will they want to download > them again? > > -- > Regards, > Brian > sos-sa.org.au I've done this very thing on a few occasions. I use aptitude, and I copied the files to /var/cache/apt/archives/, and aptitude used the local copies automatically, provided they were up to date. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde warning messages
On Friday 07 May 2004 10:43, Rodney D. Myers wrote: > i normally don't run apps from the shell, I'm using windowmaker. > > This morning I tried k3b, and kprinter, since the shell was open. > > When I ran either of these the shell had bunch of warning messages > scroll by; > > sudo kprinter > kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ > group 16x16/stock/chart not valid. kdecore (KIconLoader): WARNING: Icon > directory /usr/share/icons/hicolor/ group 16x16/stock/code not valid. > kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ > group 16x16/stock/data not valid. kdecore (KIconLoader): WARNING: Icon > directory /usr/share/icons/hicolor/ group 48x48/stock/object not valid. > kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ > group 48x48/stock/table not valid. kdecore (KIconLoader): WARNING: Icon > directory /usr/share/icons/hicolor/ group 48x48/stock/text not valid. > kprinter: WARNING: KFilterBase::findFilterByExtension : no filter found > for text/plain > > How do go about correcting these warnings? > > Thanks Hi Rodney, I can't tell you how to get rid of the last warning, but the KIconLoader errors are pretty simple. They are telling you that there is no icon with that specific name in the folder you've told it to look. Basically, it means that the icon set that you are using doesn't have a native icon, and it is instead using the default icon. For example, I use the kids icon set, which doesn't have an application icon for kuickshow. So, when I launch kuickshow from the command line, kde wants to look in the /usr/share/icons/kids/16x16/apps/ folder for a file named kuickshow.png, and put that icon in my new window's titlebar. However, no such file exists, so it instead grabs the icon from the folder /usr/share/icons/crystalsvg/16x16/apps/. It prints out a vary similar warning as to what you see when it does this. So if you use the kde control center to change your icon set to the default, those errors will go away. Of course, if you don't want to do that, you could always create the icon that's missing. ;-) The warning is quite harmless. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade: mkinitrd: module raid1 not found
On Monday 31 May 2004 12:00, Bob wrote: > Hi, > > I'm attempting to upgrade from 2.6.2 to kernel 2.6.6, compiling from the > kernel-source package, > make-kpkg --initrd kernel_image modules_image > and trying to install with dpkg -i > > This used to work fine, but now I get > > Setting up kernel-image-2.6.6-jn040531a (dizzy.1.0) ... > /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Module raid1 not found. > Failed to create initrd image. > > My system is indeed running raid1, but raid1 support is compiled into the > kernel (both the current 2.6.2 and the new 2.6.6). > > I must admit that I don't understand the details of using or updating > modules; in the past I just did the above steps and everything worked.. > > This is an extract of 'grep -R raid1 /etc': > > /etc/modutils/raidtools2:alias md-personality-3 raid1 > /etc/modules.conf:alias md-personality-3 raid1 > /etc/modprobe.d/aliases:alias md-personality-3 raid1 > > I tried to comment out these lines but I still get the error. > > Any help appreciated! I guess the raid1 module is not required since it > is compiled into the kernel? If you have any hints, please let me know. > Thanks a lot! > > Bob Hi Bob, You are correct: a raid1 module is not required since you compiled it into the kernel. Actually, because you compiled it into the kernel, no module was built, which is why it can't be found. To fix this error the most simple way, re-configure your kernel to build raid1 as a module, then compile again. On the other hand, since you're building your own kernel, why not just build in all the components you know you'll need at boot time, and build the rest (ones that you only think you might need) as modules. That way, you won't even have to use an initial ram disk. But back to fixing your error without rebuilding your kernel: where is mkinitrd's confdir? It's supposed to be /etc/mkinitrd, and if it's trying to put the raid1 module into the initial ram disk, then it should be in the config files somewhere, but your grep doesn't seem to have found it. It's possible it's in /usr or somewhere else. If you find it, check to see that that's not the culprit. Let the list know what route you decide to take and how it works. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't play audio CD's
On Thursday 03 June 2004 12:39, James Hosken wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I've just got my sound card working by installing the 2.6.6 kernel. I've > been using xmms to play some mp3s. But I can't play and audio CD's. > > I understand that you don't need to mount the CD to play it. But I can't > work out what I need to do to play the CD. > > I've googled and looked over at xmms.org but I couldn't find any to tell > me what to do. > > I've got a DVD and a CD-RW setup as > lrwxrwxrwx1 root root3 Nov 26 2003 cdrom1 -> hdc > lrwxrwxrwx1 root root4 Feb 12 21:34 cdrom2 -> scd0 > > I'm a member of the following grups > james cdrom audio www-data src > You need to check the permissions of /dev/hdc and /dev/scd0. If their group is not cdrom (or something else you belong to), you won't be able to read them. Given the error message below, I'd be surprised if the actual device nodes were OK. > > In the Xmms Preferances, I've gone to CD Player Audio Config and set the > first device as /dev/cdrom1 > and the directory as /mnt/dvd > > On checking the drive I get the error > > "Failed to open device /dev/cdrom1 > Error: Permission denied > Directory /mnt/dvd OK." > > Please could some one tell me what I need to do to get this working. > Regards > James > > Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
alsa + arts sound
Hi list, I'm having a problem I can't figure out with sound. Alsa is configured and works properly, and so is arts, apparently. I say this because XMMS plays just fine using the arts output plugin. However, I can't get any event sounds to play via the kcontrol interface, even when I test the sound from kcontrol. But the same sounds do play when I use the command line (artsdsp mpg123 some.mp3). It even plays while XMMS plays. But still, no event sounds. I'm running sid, almost all up to date (KDE is totally up to date), using kernel 2.6.6 and alsa. I'm not sure what package this problem could be in, so I'm not sure if this is a known bug. If anyone can send me a clue, I'd appreciate it. Thanks, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't mount DVD-ROM
On Thursday 10 June 2004 13:11, Luis R Finotti wrote: > Dear all, > > For some reason I can't mount my DVD-ROM anymore. I put a data CD in it > and I get the following message when I try to mount it: > > debian[~]% mount /dvd/ > mount: wrong fs type, bad option, bad superblock on /dev/hdc, >or too many mounted file systems >(could this be the IDE device where you in fact use >ide-scsi so that sr0 or sda or so is needed?) > > Here is my fstab file: > > debian[~]% more /etc/fstab > # /etc/fstab: static file system information. > # > # > > /dev/hda3 / ext3defaults,errors=remount-ro > 0 1 /dev/hda2 noneswapsw0 >0 proc/proc procdefaults >0 0 none/devfs devfs defaults > 00 /dev/fd0/floppy autodefaults,user,noauto >0 0 /dev/cdrom /cdrom iso9660 > defaults,ro,user,noauto 0 0 /dev/hdc/dvd > iso9660 defaults,ro,user,noauto 0 0 #/dev/hda1 /win >msdos defaults,ro,user,noauto 0 0 /dev/hda1 /win > ntfsdefaults,ro,user,noauto 00 none > /proc/bus/usb usbfs defaults,user 0 0 > If you specify a mount option, you don't need to include "defaults". In other words, your last line could be: /proc/bus/usb usbfs user0 0 > This did work before. It's been a little while since I tried to mount it > so I don't know what I did that made it stop working... (I recentlty > changed hda3 from ext2 to ext3 and installed hotplug.) > The above suggestion isn't your problem, since, as you say, it worked before. > Note: I can mount the same data CD using my CD-ROM drive and in Windows I > can read the CD from the DVD drive, so I guess it is not hardware > related. > > I posted the output of dmesg if you want/need to take a look: > > http://www.math.ucsb.edu/~finotti/dvd/dmesg > This excerpt from your dmesg shows the problem: SCSI subsystem driver Revision: 1.00 scsi0 : SCSI host adapter emulation for IDE ATAPI devices Vendor: PIONEER Model: DVD-ROM DVD-116 Rev: 1.07 Type: CD-ROM ANSI SCSI revision: 02 Vendor: ATAPI Model: CD-R/RW 12X8X32 Rev: 9.AB Type: CD-ROM ANSI SCSI revision: 02 Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 sr0: scsi3-mmc drive: 12x/40x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.12 sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray It would appear your dvd is being treated as a SCSI device. Check your scsi device nodes, and change your fstab as appropriate. > Thanks and my best to all, > > Luis Good job including a link to your dmesg output. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE Window Controls Stop Responding
On Wednesday 09 June 2004 20:49, [EMAIL PROTECTED] wrote: > I have this weird problem where, in KDE 3.2, my window controls stop > responding -- that is, I mean i can't click the minimize, maximize, or > close controls on the Window title bar. In fact, I can't click and drag > the window at all, nor can I grab the edges and resize. > > The problem goes away when I restart, though. > > Anyone ever seen this? Or have an idea how to fix it? > > Moe Please start a new subject with a new message, and don't just respond to another list message. It messes up the way some readers thread messages. I've seen this problem, but I've got no idea what caused it. It went away for me when I logged out. Unless you're talking about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214514 Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't mount DVD-ROM
On Thursday 10 June 2004 16:36, Luis R Finotti wrote: > > It would appear your dvd is being treated as a SCSI device. Check your > > scsi device nodes, and change your fstab as appropriate. > > That was it. Thank you so much Justin! > > I don't how that happened? But is there any problem in having the DVD > drive as a SCSI device when it actually isn't? > > Thanks again! > > Luis I believe that the ide-scsi module grabs the device before the regular ide driver does. Since you actually want to use ide-scsi for your cd writer, I don't think you can avoid this. But I might be mistaken. There should be no problems with having the DVD drive as a SCSI device when it actually isn't. At least, I have never heard of this causing problems. Anyone on the list know differently? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Soundproblems: Only right channel (unstable / 2.6.6 / terratec xfire 1024 (cs46xx))
On Monday 14 June 2004 13:10, Daniel Klein wrote: > Hey all, > > I recently installed a fresh debian on my box (I need not really mention > how happy I am with everything so far - that would only seem like > flattery to get more willing helpers - so instead I will mention this > fact and hope to get more willing helpers through my great insight into > internet communication :P). I used to run SuSE 7.2 before, with an Alsa > of version 0.5 something. Lots of things did not work there, but normal > playback of PCM worked fine. Now the situation is reversed: Lots of > things work very well with Alsa 1.0.4 (I believe it's 1.0.4 - that's > what alsamixer says - any way I can use apt-cache to find out which > version of alsa I have installed?), but there is a problem with normal > sound playback (read wav, mp3, ogg, whathaveyou): For some strange > reason, only the right channel plays. Right before I installed this > fresh debian I was using Win XP, and I remember very well that this > problem did not exist. It did not exist in my SuSE either. It's been > like this for weeks now, I frequently change between speakers and > headphones, so I'm rather sure it's nothing to do with either speakers > or connector on the soundcard. > > I am using debian unstable, kernel 2.6.6, alsa 1.0.4 (presumably), my > card is a Terratex XFire 1024 which runs the cs46xx chip (I remember > this information to be correct back from my alsa setup in SuSE). If > there's any other information about my system that'd be relevant, any > conf files or anything, ask away. > > Thank you for your attention already, > > Daniel Klein Hi Daniel, Use alsamixer and check that the master and pcm devices have both channels unmuted to the same level. Normal alsa configuration is everything muted, so I'm not sure how one channel could have been adjusted without the other, but it's an easy solution if that's the problem, so give that a quick whirl. Also, I can't think of another reason only one channel would play, besides a hardware problem. And it sounds like you're sure this is not the case. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: raid0 initialization
On Tuesday 15 June 2004 07:53, Harland Christofferson wrote: > this is my fist time installing raid0 on a machine that is not a > new install. /dev/hda has gobs of good data i don't want to lose. > /dev/hdc is newly partitioned and formatted before installing the > raid tools. > > kernel version is 2.4.18-k7 > > i installed raidtools2 and mdadm. > You don't need both. I don't think it will do any harm to have both installed, though. > i created a new file /etc/raidtab > > raiddev /dev/md0 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > persistent-superblock 1 > device /dev/hda1 > raid-disk 0 > device /dev/hdc1 > raid-disk 1 > Above, you said you wanted to install raid0, but your config file indicates raid1. Double check that your config file really says what you want. > > then, i tried > $# mkraid md0 > > which responded > $# device md0 is not described in the config file > The error message is quite specific. You did not describe device md0 in any config file. You did describe /dev/md0, however. > i am reluctant to try > $# mkraid -f /dev/md0 > > the force flag just seems scary to me. > > any suggestions? What is the partition type on /dev/hda1 and /dev/hdc1? If they are not both FD (Linux raid autodetect), your raid array won't work. Note that, if you have data on /dev/hda1 that you want to keep, you should mark that disk as a failed disk. Then, when you make your raid array, data won't get erased from /dev/hda1. You can then mount the disk and the raid and copy the data from one to the other. Once your data is on the raid, mark the /dev/hda1 disk as a live disk, and the raid will re-sync, and your data will be intact. If the partition type is not causing your problem, let us know and we'll try something else. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: raid0 initialization
On Tuesday 15 June 2004 08:56, Harland Christofferson wrote: > *snip* > > > > >What is the partition type on /dev/hda1 and /dev/hdc1? If they > >are not both > >FD (Linux raid autodetect), your raid array won't work. > > the partition type? okay ... new territory for me. they are ext2 > w/ ID of 83. they are the boot partitions. > You will need to change them to ID of FD using a program like cfdisk in order to use them in a raid array. > >Note that, if you have data on /dev/hda1 that you want to keep, > >you should > >mark that disk as a failed disk. Then, when you make your raid > >array, data > >won't get erased from /dev/hda1. You can then mount the disk and > >the raid > >and copy the data from one to the other. Once your data is on the > >raid, > >mark the /dev/hda1 disk as a live disk, and the raid will re-sync, > >and your > >data will be intact. > > i am really glad this did not work the first time. i DO want to keep > the data intact on /dev/hda. should i mount each partition of /dev/hdc? > what i want to have occur is all partitions on /dev/hda be mirrored > on /dev/hdc. > This is pretty standard. You need to partition /dev/hdc to match /dev/hda with respect to partition sizes, but make the partition types FD. For each partition, create an md device with the /dev/hdcx partition as disk 0 and /dev/hdax partition as disk 1, and be sure to mark disk 1 as a failed disk. Then, use mkraid to build the array. Note that if you have /dev/hdax mounted and you don't properly have the partition labeled as a failed disk, building the raid will fail and you won't lose data. After you build the array, format it with whatever file system type you're going to use. Then mount the array somewhere, and begin to copy your data over to the array. When all your data is copied, modify your boot loader to point to the raid that contains /boot and /, and reboot. Now, you should be able to unmount all partitions from /dev/hda. Once you have done that, change the partition ID to FD, remove the failed marker from the raid config, and the drives will sync. At that point, you're done. It sounds simple, but if you get into trouble, you might want to search the archives for problems other people have had, or you might want to check out this link: http://rootraiddoc.alioth.debian.org/ It's quite complete, very recent, and a good resource. I recommend reading it, unless you want to test your backup strategy. ;-) Good luck, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange problem with sound card
On Monday 14 June 2004 23:57, j smith wrote: > i have SB 16 and Debian 3.0. after compiling kernel > 2.4, i put the following to /etc/modules: > > sound > uart401 > sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 > > it seems that sound driver works, because lbreakout2's > sound effect is OK and xawtv'TV sound is OK. but i > can't record TV sound in xawtv. it complains:"oss: > read: Input/output error". later i found "cat foo.au > >/dev/audio" does not work, with dmesg, i found > > "Sound:DMA(output)time out - IRQ/DRQ config error?" > > please help me! > I would try changing the IRQ value to whatever else is available and seeing if that helps. You might also want to try changing the DMA value, too. I had to go through nearly all combinations before I got my sound card to work. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what do i need to install???
On Tuesday 15 June 2004 09:11, Cecil wrote: > I have installed my nvidia driver problem free before... But now when i > try to get my kernel headers, it says it cant find them. I have > updated... And I am running testing. > > Couldn't find package kernel-headers-2.6.6-1-386 > > Cecil That package isn't in testing yet, but you could pull it from unstable if you want to. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SA going downhill
On Wednesday 16 June 2004 04:45, Antony wrote: > Hi all, >[ big snip] > > Is there anything that I can do about this? I know about training it, > but doesn't that need thousands of messages to work? > > A Yes, training spamassassin requires thousands of messages to work, both ham messages and spam messages. When I first installed spamassassin, it caught nothing. I didn't realize that thousands meant thousands. Once I got a thousand spam messages to train it on, it started working better and better. My hit rate now is probably 75% or greater, with no false positives (I've only ever had one false positive). I know 75% isn't awesome, but I'm being conservative, because I don't really track it that closely, and I don't want to mislead you into thinking it'll be perfect. But it's enough that I get most of my spams properly identified. I don't have spamassassin set to autolearn, and I've noticed that right after I train it with the newest messages, it works great. Then, new style spam comes out, and it does poorly for a bit. I then train it on the newest spams, and it works great again. That's what autolearn is for, I guess, but I'd rather not have to deal with false positives. I could train it once a day via a cron job, but I haven't done that yet. As always, your mileage may vary, but hopefully not that much! :-) Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: scheduler
On Friday 18 June 2004 05:00, jawahar basha wrote: > hi , > > i am new to debian linux, having debian linux system. > > i have doubt about scheduler, how to stop the scheduler and where i want > to change scheduler timing . > > > kindly help me > > Thanks > Regards > > syed > > _ > Apply to 50,000 jobs now. http://go.msnserver.com/IN/50740.asp Post your > CV on naukri.com today. To stop the scheduler, do this as root: $ /etc/init.d/cron stop To keep it from running ever again, do this as root: $ apt-get remove cron To change the timing, edit the appropriate cron entry. You don't say which scheduled job you want to change, so I don't know if it's in cron.daily, cron.hourly, or somewhere else. "man cron" will give you a good start. If this answer is not specific enough, please ask a more specific question. We are all willing to help, and we welcome you to the group. Also, if English is not your native language, you might try looking for a list that is in your native language, especially if the language barrier is keeping you from being specific. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel panic - no /dev/console
On Friday 18 June 2004 13:36, Chris Metzler wrote: > On Fri, 18 Jun 2004 14:43:49 -0400 > > Derrick 'dman' Hudson <[EMAIL PROTECTED]> wrote: > > On Fri, Jun 11, 2004 at 02:45:36PM +1000, glenn wrote: > > | When i boot off this image I get a kernel panic, following a message > > | from sbin/init, that it cant find dev/console. > > | > > | Any ideas what I have to do? > > | > > | incidentally, ls -l /dev/console gives : > > | crwx-- 1 root tty 5, 1 Jun 11:14:40 /dev/console > > > > Maybe this will help? > > > > $ ls -l /dev/console > > crw-rw1 root root 5, 1 2004-06-12 10:48 > > /dev/console > > Do you think that's it? I have > > stax:~-595> ls -l /dev/console > crw---1 root tty5, 1 Jun 17 20:44 /dev/console > > and things work o.k. > > -c I think the complaint about /dev/console is a red herring. I encountered this problem just yesterday, if memory serves me. The problem was actually related to the kernel modules in the initrd and the root drive. Basically, my root drive was a raid1 (but /boot was not), and the raid modules were not in the initial ram disk. I solved the problem by manually making a ram disk, then booting off of it instead of the one that was provided with my kernel (which is 2.6.6, incidentally). Glenn, does your root partition require any driver modules that aren't part of the initial ram disk? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alt-tab locks user in / kde 3.2.2 / debian unstable / kernel 2.6.6
On Monday 21 June 2004 08:25, Daniel Klein wrote: > Hey, > > I've posted this on the kde list and I've submitted a bug into the kde > bugtracker, but on the kde list it was suggested that I might want to > post this on here as well, so here we go with a link: > > http://bugs.kde.org/show_bug.cgi?id=83737 > > In short, alt-tabbing in KDE does Very Bad Things from time to time (so > far, roughly 2 or 3 times a day). More details --> read the bug > description, if you're interested. > > There was also mention of kde-debian and debian-kde and whatnot, but > truth be told, I just want that bug to be brought to the attention of > the right people, I don't want to invest hours into having it solved. If > you think I must absolutely repost this on either debian-kde or > kde-debian, tell me and I'll do that as well. > > Thanks already for any kind of interest, > > Daniel I have never had this kind of problem, and I use KDE all the time. Have you tried to log in to your locked box from another box (ssh)? If so, is there any process hogging resources? Can you start killing suspect applications? That may help you track down the culprit. Also, you might try starting x0rfbserver remotely, then trying to connect via VNC. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /dev/hda2 on / type unknown ???
On Tuesday 22 June 2004 07:13, David Fokkema wrote: > On Tue, Jun 22, 2004 at 03:12:23PM +0200, Felix C. Stegerman wrote: > > Norman Walsh wrote: > > >My root partition is /dev/hda2. My machine boots up and runs fine. > > > > > >$ cat /etc/fstab | grep hda2 > > >/dev/hda2 / ext2defaults,errors=remount-ro > > > 0 1 > > >$ mount | grep hda2 > > >/dev/hda2 on / type unknown (rw,errors=remount-ro) > > > > > >That looks a little frightening to me. I touched /forcefsck and > > >rebooted. It found errors on the root partition, claimed to fix them, > > >and rebooted but the result was still an "unknown" partition type. > > > > > >Thoughts? > > > > I just read your post and looked at my own situation. > > What I found rather surprised me. > > > > Same 'unknown type' here: > > $ mount | grep hda5 > > /dev/hda5 on / type unknown (rw,noatime,errors=remount-ro) > > > > I looked at /proc/mounts which also seemed to have a strange entry: > > $ cat /proc/mounts | grep '/ ' > > rootfs / rootfs rw 0 0 > > /dev/root / ext3 rw,noatime 0 > > > > I've never heard of rootfs and was unable to find some useful > > information quickly. > > > > Unfortunately I don't know whether /proc/mounts used to look different, > > since I never really used it. > > > > It might be of interest which version of Debian you and I are using, > > and what kernel. My set-up: > > Linux 2.6.7-mm1 (built from kernel.org) > > Debian testing/unstable (APT prefers unstable) > > > > It'd be nice if someone could shed some light on this. > > Damn! I have it too... I guess it's nothing, but still... :-/ > > kernel 2.4.26-1-686 / unstable > > David > I do not have an unknown type for my root partition, but I do have the rootfs partition: $ mount | grep '/ ' /dev/md0 on / type reiserfs (rw) $ cat /proc/mounts | grep '/ ' rootfs / rootfs rw 0 0 /dev/root.old / cramfs ro 0 0 /dev2/root2 / reiserfs rw 0 0 I am running sid, 2.6.6 deb image. I believe the cramfs is the initial ram disk image. Perhaps that may be why my root partition is a known type. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange colors
On Tuesday 22 June 2004 06:06, frank coldewe wrote: > Hi, > > since i have installed woody and kde i have problems with the colors on > the screen. > In some applycations like freeamp, gimp and sane ... the colors are not > right. grey is green or blue ans so go on... any idea ?? > > greetings frank It sounds like your KDE color choices are not being applied to GTK apps. I believe there's a setting somewhere in the KDE control center, but I'm not sure if it's in the version in woody. Check it out and see if that's your problem. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with noflushd in Sarge
On Monday 16 August 2004 16:19, Matthew T. Atkinson wrote: > 'ello, > > I'm pretty sure that noflushd is not spinning down /dev/hdd after 5 mins > (which is how I have it set up). Unfortunately, no messages from it are > appearing in syslog (they used to in Woody) so I am unable to tell > exactly what isn't working. > > Has anyone else had these problems? Is there a known bug and/or > workaround? > > Thanks in advance for any info you may be able to provide... > > bye just now, > > Hi Matthew, I know of two things that could be causing your problem. First, are you running a journaling file system? If so, don't expect your hard drive to be spun down. I think searching the archives will reveal some specifics. Second, are you using a 2.6 series kernel? I seem to recall that noflushd had to have some changes to work with 2.6 kernels, and since you don't say what version you're on, I can't rule this out. Even when this was the case, though, noflushd did print out an error message when it was started. Does it print out an error message when you start it by hand? Does it appear in ps or top? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems mounting nfs with pcmcia
On Monday 16 August 2004 17:43, John L Fjellstad wrote: > I'm setting up a Debian Linux system at a friend's house. He has Debian > Woody (with backports) on the server, and Debian Sarge on the client. > > The client has a pcmcia card for networking. I'm trying to set up so > that the nfs shares are mounted automatically when he boots up, but it > doesn't happen. > > I put this in his fstab: > 192.168.1.1:/data/share /net/share nfsrsize=8192,wsize=8192,_netdev > 0 0 > > But the system won't mount it at boot up (no problem mounting it manually > after logging in as a user, using mount -a -t nfs). > > I then figured it might be something with being pcmcia, so I added the > mount point to /etc/pcmcia/network.opts MOUNTS="/net/share". That > didn't work either. > > I checked the logs and it seems the problem is, the system in both cases > tries to mount the nfs filesystems before the network is fully up. > > I tried to move the mountnfs.sh /etc/init.d script to a much later stage > (from S45 to S70), but it didn't help. Does anyone have any idea what I > can do next? I have nfs filesystems mounted on my own system without > problems, so I'm not sure what his problem is. > > We both run the same software both places (dhcp3 on server and client). > I'm guessing when you moved your init script from S45 to S70, the error message was the same. If there was no reason that you chose 70, you could always move mountnfs.sh back further and see if that works. If it still doesn't work at S99, then you could always add a call to the shell script from the end of the networking script, then remove the backgrounding, if present. You might have to add a delay to the start of the mountnfs.sh script, or you could use the builtin wait function when calling the network startup scripts. Hope that helps, Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: raid 5 on boot? root?
On Tuesday 17 August 2004 11:13, Richard Weil wrote: > I don't know if my configuration is (a) setup badly, or (b) impossible. > Before I spend too much more time on it, I wonder if anyone has > relevant experience. > > Is it possible to have both boot and root on RAID 5? I'm getting a > kernel panic mid-way through boot. Assuming it's not possible, what > about if boot is on a normal drive and root is on RAID 5? > > I'm running up-to-date Sarge with kernel 2.6.7. I'm using the stock > Debian kernel and the Grub boot loader. > > Thanks, > > Richard > > Hi Richard, It is possible to have both root and boot on a raid partition. I've done it with raid1. I can't imagine raid5 would be any different. One way to do this is to custom compile your kernel to include all the relevant drivers you need (raid and file system) to mount your root partition. Debian stock kernels have the drivers compiled as modules, which isn't good enough. They need to be compiled into the kernel unless... You build an initial ram disk image which includes the necessary modules. Then, you can use the stock kernels. You just need to make sure the initrd was built with the modules you need. I have heard that grub might have some limitations booting from a raid partition, but I can't say for sure either way. I haven't tried with grub yet. Oh, and also, some old bioses might have problems. Otherwise, it's possible. Note that it's easier to have /boot on a non-raid, so you might set it up non-raid at first, then move the /boot partition to raid when you've got / working correctly. Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: anti-freeze
On Sunday 22 August 2004 02:42, Jim McCloskey wrote: > One of the machines I use regularly has a nasty habit of suddenly > locking completely (it happens maybe a couple of times a month). It's > always when X is running, and, I am nearly sure, always when a browser > is being used. This is a Debian testing system, running kernel 2.4.23. > Mozilla-Firefox is the browser that is mostly used. > > It's not just that X freezes; the whole system becomes autistic. In > this state, it can't be reached from the network (no ssh, no ping, no > nothing). The only way out, as far as I know, is with the > power-button. Ctl-Alt-Del produces no response. Nor does Alt-SysRq, > which means, I suppose, that the kernel is dead. > > These events leave no trace whatever in the logs and so it's > frustratingly hard to do any useful trouble-shooting. I thought that > they might be caused by a corrupt memory-module, and so I ran memtest > for the best part of a day. However it found no errors. > > I know that this much doesn't provide a lot of information to go on, > and I apologize for that. But does anyone know of ways to work on a > problem such as this? > > I'd be really grateful for any tips or pointers. > > Jim I had a similar problem before. If I wasn't running X, the computer had no problem. If I did run X, it would freeze completely after a random amount of time. It would even freeze running Knoppix. I eventually discovered that the video card didn't properly support the resolution I was using, even though it would display properly. Have you tried using the vesa driver? Justin Guerin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
