Re: Equation system resolver
Try SCILAB. It is very much like Matlab and it is free. James E. Merritt - Original Message - Nicolas <[EMAIL PROTECTED]> writes: > Is there a equation system resolver in debian or linux in general? > Basicly, I need to resolv equation systems or simplify very long and > complicated equations. -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Can't get KDE working!
Hi everyone, I am having a problem with my KDE not running, or rather it is running but all I get when I type: startx is twm. A few weeks ago, I installed woody on my computer and finally got X to work. I have an ATI Rage 128 video card and during the installation, I chose KDE as my windows manager. The installation did not properly set up my video card, I had to edit the XF86Config-4(I think that is the proper name) file. But now, when I start Debian, I don't get the X server running but the startup says KDE is running. When I type "startx" I get twm. I even installed the latest XFree86. 1. How do I get X to start automatically? 2. How do I get KDE to run instead of twm? Any help would be appreciated. Thank you and have a nice day!! James E. Merritt -- ___ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup One click access to the Top Search Engines http://www.exactsearchbar.com/mailcom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HP 712/60 questions
Hi Larry, I have been using Debian Linux on two 712/100. I bought a cdrom that was compatible with these machines. Not all cdroms drives will allow the 712's to bot off of them. I think maybe the newer SCSI cdrom's will work. Anyway, I suggest subscribing to [EMAIL PROTECTED], they are more than willing to help with any Debian questions relatyed to the HPPA machines. It seems, from what I have been able to gather, the HPPA architecture has made it very difficult for the Linux community to make a suitable Linux kernel that will run on these machines. I am not sure if you could simply cross compile on another machine and load that into your 712 machines. The easiest way to go is buy the distro from one of the vendors on the debian.org website. I bought mine from Abexia and was very pleased with how well the installation went, although I had never installed Debian before so the learning curve was the installation. I use KDE as my window manager and it takes a while to load it on my machines, but once it is up and running it performs very well. The video uses only 8 bit depth, it will not owrk on any higher bit depth. But for me, that is more than enough to learn Debian. Hope this helps and I did not ramble too much...smile. James E. Merritt - Original Message - From: "Larry Crouch" <[EMAIL PROTECTED]> Date: Tue, 26 Aug 2003 11:00:01 -0400 To: <[EMAIL PROTECTED]> Subject: HP 712/60 questions > Hello, > > First of all I'm unfamiliar with Unix/Linux/Debian > and such since I've been in the Windows world > for many years. > > I came across 3 HP 712/60 workstations and > figured this would be a good project to acquaint > myself with Linux. > > The learning curve has been very substantial > so please bear with me. > > The workstations have no floppy or CD drive. > The only way to load PALO (I think that's the > boot loader for Linux) is via a lifimage stored > on a remote boot server. > > The HPs boot HPUX and then an application. > I've seen the BOOT_ADMIN and ISL > screens enough to turn auto boot off and > verify that everything seems to be as discussed > in various Debian web pages. > > I guess I have to load Linux onto one of > my PCs (I have a couple of Pentiums not > being used at the moment), load the Linux > sources, run the cross-compiler with certain > options to create a lifimage and then enable > a DHCP daemon so the HP box can boot > from it. > > Is this the path or am I completely offbase. > > Any help is appreciated. > > -- > Larry Crouch > [EMAIL PROTECTED] > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Trying to get modem to work with Debian
Hi all, I have a US Robotics USR5699B PCI modem and I am trying to get it installed under Debian Woody. According to Windows, it is installed on COM5, IRQ 11. Under Debian, I had to create the com port as ttyS5, then use setserial /dev/ttyS5 irq 11. Then I tried using wvdial and that does not work, apparently it does not recognize the port. I don't remember the exact error messages. Since I am using KDE, I tried using kppp, but kpp does not give the choice of /dev/ttyS5. 1. Will this modem work under Debian or am I wasting my time? 2. If it will work, how do I get kppp to recognize /dev/ttyS5? Of more to the point, how do I get this modem to work? Thanks in advance for any help on this problem. I would like to move over to Linux as my main OS, if only I can get a modem for internet access. I knew I should have spent the extra $20 to get the other US Robotics modem that said it was also for Linux, but being unemployed at the moment, I am trying to save money...smile. James E. Merritt [EMAIL PROTECTED] [EMAIL PROTECTED] -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup Search Smarter - get the new eXact Search Bar for free! http://www.exactsearchbar.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
Hi everyone, I am having a little problem with my Debian Woody. The other day when I tried to boot into Woody, it started the normal text bootup screen before it goes into to KDE graphical login screen. But, during the text portion of the boot up process, it stopped and gave this message: VFS: Cannot open root device "346" or 03:47. Please append a correct "root=" boot option. Kernel Panic: VFS: Unable to mount root fs on 03:46. What does all of this mean, what is going on and what can I do to correct this? I am lost at this point. Thank you all for any help you can give me. Have a great day! James E. Merritt [EMAIL PROTECTED] -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cannot Open Root Device - Was: Unidentified subject!
Hi, Hi Kent, sorry for not using a meaningful subject, often time I overlook those emails without a useful subject myself, never know what you will get with all these crazy viruses, etc. going around...smile. I hit SEND before checking my email more carefully. Also to Andreas, I am sorry I responded to your response and my email package uses the poster, not the newsgroup, as it's TO: address. I try never to respond directly unless the poster requests it. Also, by responding back to the newsgroup maybe others can benefit from the thread. As far as I know my disk configuration has not changed and I have not added any new hard drives. I remember doing something with the kernel a while back, but it has worked since then, unless I was very lucky and now my luck has run out...smile. My system is dual boot, Windows XP on one drive as partition hda1 and then linux as one partition on a second hard drive as hdb1, with three dos partitions on that same drive (hdb5, hdb6, hdb7). Do I type this at the lilo boot screen: linux root=/dev/hdb1? And if I can't get that to boot into Debain, how do I check the boot loader configuration? I will try booting from my original install disk and check the hard drive, which I hope is not going bad. And I will check the /etc/lilo.conf, now that I get thinking more about this I, as I stated earlier I changed the kernel and I thought the I read somewhere to change the /etc/lilo.conf, maybe that was not the thing to do. I just checked my notes and found this from when I changed the kernel: Add initrd=/initrd to /etc/lilo.conf. If I have already done so, then put do_initrd=YES in /etc/kernel-img.conf. Which I recall doing. Maybe we are on to something here? I am learning as I go, even though I have been doing basic things with Linux for a number of years. I will let everyone know what I find. Thanks for the help and I will keep you informed of my success, hopefully...smile. James E. Merritt - Original Message - From: Kent West Date: Fri, 23 Jan 2004 13:56:34 -0600 To: [EMAIL PROTECTED] Subject: Cannot Open Root Device - Was: Unidentified subject! > JAMES MERRITT wrote: > > >Hi everyone, > > > >I am having a little problem with my Debian Woody. The other day when I tried to > >boot into Woody, > >it started the normal text bootup screen before it goes into to KDE graphical login > >screen. > >But, during the text portion of the boot up process, it stopped and gave this > >message: > > > >VFS: Cannot open root device "346" or 03:47. > >Please append a correct "root=" boot option. > >Kernel Panic: VFS: Unable to mount root fs on 03:46. > > > >What does all of this mean, what is going on and what can I do to correct this? > >I am lost at this point. > > > > > > Let me encourage you to use a meaningful subject line. > > It means that for whatever reason, the system can't find your root > partition. Have you upgraded your kernel lately, or switched from ext2 > to ext3, or something similar? > > Do you have a Debian installation CD, or a Knoppix CD? If so, boot off > either of those, then you can mount your hard drive and take a look > around to see what might be broken. Perhaps you need to fsck your root > partition; perhaps /etc/lilo.conf got changed to point to the wrong > partition; perhaps you're dual-booting and Windows got virus-infected > which messed with the partition table; perhaps you have a failing hard > drive. Any number of things. > > -- > Kent > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cannot Open Root Device - Was: Unidentified subject!
I tried typing linux root=/dev/hdb1 at the lilo prompt and it says something about that not being one of the choices. The lilo menu I see is: Linux WinNT (hda1) WinNT or DOS (hdb6) <- This is not a valid bootable disk, I don't know why it is there. Then I tried booting from my original install disk1 and it just takes me right into the Debian install menu. Is there something I can do from there? I'm wondering if maybe /dev/hdb1 is no longer a valid boot point, maybe something messed up. Thanks again. James E. Merritt - Original Message - From: Kent West Date: Fri, 23 Jan 2004 17:18:14 -0600 To: [EMAIL PROTECTED] Subject: Re: Cannot Open Root Device - Was: Unidentified subject! > JAMES MERRITT wrote: > > > >I am having a little problem with my Debian Woody. The other day when I tried to > >boot into Woody, > >it started the normal text bootup screen before it goes into to KDE graphical login > >screen. > >But, during the text portion of the boot up process, it stopped and gave this > >message: > > > >VFS: Cannot open root device "346" or 03:47. > >Please append a correct "root=" boot option. > >Kernel Panic: VFS: Unable to mount root fs on 03:46. > > > > >As far as I know my disk configuration has not changed and I have not added any new > >hard drives. I remember doing something with the kernel a while back, but it has > >worked since then, unless I was very lucky and now my luck has run out...smile. > > > >My system is dual boot, Windows XP on one drive as partition hda1 and then linux as > >one partition on a second hard drive as hdb1, with three dos partitions on that > >same drive (hdb5, hdb6, hdb7). Do I type this at the lilo boot screen: linux > >root=/dev/hdb1? And if I can't get that to boot into Debain, how do I check the > >boot loader configuration? > > > >I will try booting from my original install disk and check the hard drive, which I > >hope is not going bad. > >And I will check the /etc/lilo.conf, now that I get thinking more about this I, as > >I stated earlier I changed the kernel and I thought the I read somewhere to change > >the /etc/lilo.conf, maybe that was not the thing to do. I just checked my notes and > >found this from when I changed the kernel: > > > >Add initrd=/initrd to /etc/lilo.conf. If I have already done so, then put > >do_initrd=YES in > >/etc/kernel-img.conf. > > > >Which I recall doing. Maybe we are on to something here? > > > > > > Your /etc/lilo.conf should have some lines something like these: > > boot=/dev/hda > Root=/dev/hdb1 > image=/vmlinuz > label=Linux > read-only > initrd=/initrd.img > > ls -l / > should show something like this: > lrwxrwxrwx 1 root root 28 Nov 6 13:38 initrd.img -> > boot/initrd.img-2.4.20-1-686 > lrwxrwxrwx 1 root root 25 Nov 6 13:38 vmlinuz -> > boot/vmlinuz-2.4.20-1-686 > > and of course those boot/ in the previous two lines should exist: > -rw-r--r-- 1 root root 660989 Mar 25 2003 vmlinuz-2.4.20-1-686 > -rw-r--r-- 1 root root 2916352 Mar 27 2003 > initrd.img-2.4.20-1-686 > > Once you boot into your installer, you should be able to mount your > /dev/hdb1 root partition, and then shell out to a prompt with Alt-F2. > You should find your root mounted under /target. > > You might want to "chroot target" to make your hdb1 root file system the > "active" system, and then run "lilo" to make sure the lilo.conf settings > are applied to your boot system. > > Alternatively, you might can just do as someone else suggested, and as > you mention above: at the boot: prompt, enter > linux root=/dev/hdb1 > > btw, the "initrd=/initrd.img" line in /etc/lilo.conf must be there for > initrd-style kernels to boot, but the "do_initrd=YES" line just > suppresses the reminder to make sure the "initrd" line exists in > lilo.conf on future upgrades of the kernel. > > -- > Kent > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
