danleff
Moderators-
Content count
2895 -
Joined
-
Last visited
Everything posted by danleff
-
psmouse.c : bad data from KBC - timeout This is a keyboard controller issue. Do you have a PS/2 keyboard that you can plug-in and see if the issue goes away? I don't know the solution, but it would be interesting if this solves it.
-
It's interesting how our experiences differ. I'm running Core 3 right now. It's doing some funky things in the background right now, but has been generally stable. It is also the first distro I have been able to get my wireless card to work with, although it's with a third party driver (linksys WMP54gv4 card using the ralink driver). it locked up solid with ndiswrapper (stack issues). kinda reminds me of Windows! I also have Mandrake 10 beta version running rock solid. However, it refuses to compile a generic kernel-source and won't conect my wireless card. I have to agree with Dapper Dan, stay one version behind and you get a much more stable and flexible system.
-
The issue with Wine, is that there are a few flavors. If you installed the rpm version during your install of Mandrake (it sounds like you did), you need to uninstall previous packages before trying a new one. The version that comes with Mandrake is not the newest, of course, but is new enough to work well. Let us know which one you installed, say wine-20041015, or whatever. Then we can help you with the install options, such as you mentioned. But, before you do anything, go to a terminal window and just type in wine and see if it comes up with a version. This means that you did install the rpm package, during your Mandrake install process. You can also go to the start-->manage computer-->Install/remove packages-->Remove packages and type in wine and you will see if it has a candidate to uninstall. Of course, don't uninstall it, if you want to try it out. just see if it is there, already installed.
-
From the threads that I have seen, this is mostly an issue with laptops and synaptic touchpads. However, there are also references to desktops also. I am curious, do you have both a usb mouse and keyboard? What make/model pc is it? I bet it is a Fedora and hardware issue. I have also seen some patches posted by the kernel experts, but with varied results. Fedora just posted an updated kernel, but it does not make mention of this issue that I could see in the changelog.
-
Try booting with Mandrake #2 disk. When it gives you an error about not being an install disk, switch the cd to #1, hit enter, and see if the install continues. Are you using cdrw or cdr media?
-
The Mandrake install is having trouble with the dvd drive, not the hard drive. Is this by chance a combo dvd/cdrw drive? My install fusses with this combo drive and has trouble reading cdr disks as well.
-
From the Unofficial Fedora faq page; The new 2.6 kernel in Fedora Core can't fit on a floppy disk. So, you can't boot or install from a floppy. However, you can install from a CD, hard drive, or even USB disk (if your computer supports booting from a USB disk).
-
Try booting from cd #2 and see if the install starts ok. Try to read the error message, if you can, such as "cd media read error"?
-
I'm just struggling with wireless now, but got everything (minus the modem) working on my Thinkpad R-30. What wireless card do you have currently? What distro are you leaning toward right now? Just for kicks, look at Fedora on your system here.
-
Is it possible to post a little more information for us to go on? What Biostar motherboard is this? How much ram (memory) is in the system? What monitor are you using (make + model)?
-
Which version of Wine are you trying to install? What is the full package name? Did you take a look at the Wine install how-to? I assume that you did not install the Wine version already that comes with Mandrake? What specific errors are you having trying to do the install?
-
Rebooting problems are frustrating, finding the cause is sometimes difficult. Your system specs. are the minimal that Suse would need. 1. the first issue is the medium that you are using to boot. I assume the suse cd disks are commercial? If not, if you burned your own boot disk, say to do a net install, what speed did you burn the disk at? If a commercial set, try booting from cd #2 and see if the install starts ok. Use the keyboard to pick the installation button/menu, not the mouse. 2. Hardware. Well, it seems that the memory is OK, but you may have a funky cdrom drive. If you burned your own disks, what medium are you using, cdrw or cdr media? You also tried removing some hardware from the system. That is a good start. What power rating is your power supply? Have you tried any other OS on the system, such as Windows?
-
Automatic USB dection for digital camera/external HD?
danleff replied to LinuxCrusader's topic in Everything Linux
Try this digikam link. It should help in getting Digikam to see your camera, which is probably a usb mass storage camera. -
Look at the users manual. It gives full instructions on how to mount the card in Linux. Assuming that you have no other card plugged into usb; Try the following, as root user in a terminal; mkdir /mnt/rundisk mount /dev/sda1 /mnt/rundisk Then use the file manager (in superuser mode) to navigate to the directory. You should be able to read and write to the disk, assuming that the write-protect tab is not switched to "on."
-
Sure. Once you have unpacked the tarball, get into the nvu-0.70 directory and type in a terminal window; ./nvu That should do it! If you want to create an icon on the desktop (KDE); 1. right click on the desktop-->create new-->file-->link to application. 2. Under the application bar, browse to the directory where the tarball is uncompressed and choose the nvu script (not the nvu-bin file). 3. An icon can be found by choosing the icon button under "general" other icons and browse to the nvu-0.70 directory-->icons, and choose an icon.
-
I think Dan is on it. Linux does not like spaces in directory names. His method will bypass this issue and allow the directory to be read properly, not looked at as a command. The space makes Linux think that this is a command. I have a wifi card (D-Link) installed on my system. The madwifi works fine in one distro (CVS version) and ndiswrapper in another (from source). Dan, don't you have a Linksys in one of your systems? I may need help with this, as I just purchased one (WMP54G).
-
USB 2.0 drives can be problematic. Did you insert the pen drive in a usb 2 slot? In other words, in one of the primary usb ports on the back of the box, or a secondary port on the front of the box? Also, did the flash drive come pre-formatted? Any way to check and make sure of this? Can the pen drive get detected in Windows, if you have Windows installed? What make and model pen drive is this?
-
Try as root user; lspcidrake | grep -i eth not ispcidrake | grep -i eth OK, if you have to input your own values in Windows, then this is a static connection. Then try ifconfig. again as root user and see if the values are the same as on the Windows system. You should see two entries, one for lo (local) and another for eth0, which should be the internet connection.
-
OK...let's go step by step. The lan card is connected by a cat5 network cable only? You do not have the usb connected to the system from the router as well? When you set up the card, it looks like you went right to adding in the ip values...in other words static configuration. Are you sure that the isp is not dynamic? In dynamic setups, you do not need to put in the values for ip and dns. Just choose DHCP and skip the ip address and so on, just hitting the enter key (do not add any values) when going through the wizard. And, when going through the wizard, you are choosing "lan" to go through the wizard? In other words, this is the choice that you are using, attempting to configure the lan card, not the router? This is what I would do, as it has been reported in the compatability section that this board works fine with Linux. Try getting to a terminal window, as root, and type in the following; lspcidrake | grep -i eth See if you get some output, like; e100........Intel Corp.... Let us know what the result is. Try deleting all the entries in the Control Center for the current tries that you did. Re-boot the system and get back into the Control Center, adding a new connection for lan. Pick DHCP on bootup and follow the wizard, again, not adding any static values, just keep hitting the enter key when asked for such, allowing the configuration to finish. Re-boot the system again and see if the connection comes up. As you boot the system and the text scrolls by, you should see; eth0...................OK. If this fails, let us know. Thanks for the reply about the kernel. Some folks use custom kernels on install. I just wanted to make sure. About the driver on the cd. What we don't know, is what the driver was written for, the older kernel (2.4) or the version that comes with Mandrake (2.6 series). Often, they are written for older distros that did not have support for the lan card. Mandrake 10 should. So, before installing such a driver, let's see if Mandrake picks up the onboard card, which it should. It did on mine, after a few tries.
-
If the CPU usuage is at 100% all the time, this is a serious problem. The bios that you mention clearly states "BIOS for 1557/M10 64MB Video RAM only." If this is not your system, you should not be using this bios. many people make this mistake, trying to upgrade a bios with a version that is not made specifically (exactly) for their system and hardware. This complaint seems common for the laptop, see the Aopen forum article here. I suggest that you contact Aopen and share your problem with them. They will need to fix the issue. While it looks like others have done the same thing as you, your system's symptoms I would consider significant and need a solution. Again, I would contact Aopen and ask what you can do. I would also not attempt to re-flash the bios again, until you get some direction in this area from the company. It looks like others have attempted to re-flash again and had errors, hopefully not fatal ones!
-
My knowledge of ADSL is limited, but this motherboard has a via 6103 onboard lan, I believe. Your connection to the isp is static or dynamic? I would think that you just need to use dhcp to get a connection, unless you have a specific setup? I assume that the onboard lan is connected to the router? In the Control Center, does you card show up as an option to configure? I also noticed that you posted another thread about drivers. Before trying to install additional drivers, could you post where you found the driver and what led you to believe that you needed the additional driver? In other words, did you find this as a possible solution somewhere? Mandrake should pick up your onboard lan, as long as it is enabled in the bios, without additional drivers. When you installed Mandrake, did you go with the default install with the 2.6 kernel?
-
Originally posted by mjwebb007: Quote: Thanks. That it what I thought. I want to work with it a bit and realize I can pretty much recover from mistakes in GRUB.... One question is that I want to install Linspire 4.5 as one of my distros....I know it pretty much overrides everything else or did they fix that in 4.5? Also if I install it on my IDE hard drive all by itself can I still use grub to boot the computer then get to the sole partition and installation on that single drive without corrupting everything else? Yes, grub is good in this respect. You can edit it at the boot menu and test settings to see if it works. In terms of Linspire, I suggested not installing it right now, as it will over write your MBR with Lilo. There is no fix, this is what Lindows does. It is designed to be the main distro on the system and makes the decision to install lilo on the mbr, regardless. This is a feature for users who are not going to multiboot anything except Linspire and Windows. You can choose to install it later on when your current system is totally bootable, by disconnecting all your sata drives and doing the install. I do not recommend doing this anytime soon, since you need to solve your current boot issues with grub and sata. The issue with sata drives, I am just learning (I have one on one of my boxes now) is that there is no master/slave assignment to sata drives. So, you can't expect that drive designations will be straightforward as ide drives. You need to come up with one plan and stick to it. Don't keep changing boot options and orders of the drives. We need to see what Suse is seeing right now, related to your sata drives. Please do this. Go to /boot/grub in Suse and open up the menu.lst file. Post what that says so we can look at it. Also, get to a terminal window and type in df (hit the enter key). Post what this says on this thread also, so we can see what suse is seeing your drives at currently.
-
I have to agree with the Dapper. I remember my first Linux days. I was lucky enough to have a mentor on a forum who guided me through. I remember bugging them quite a bit...but boy was it helpful. I eventually became an admin on the site (which now is gone). The idea is not to answer all the questions asked...nobody has all that knowledge. But, rather getting people involved and stimulate thought toward solutions... to think through the problem. I also agree with egorgry...everybody has their own strengths and eventually someone has a path to a solution. The only attitude here is collective knowledge!
-
ASRock K7VT4A+; via-rhine; snd-via82xx: Very ugly...
danleff replied to felixbecker2's topic in Linux Hardware
What distro and version are you using? It should work fine, according to the Compatability section. Check your bios settings and make sure that the all the onboard sound functions are enabled. Also, you may want to look at this article about your board. -
Mandrake 10.1 Newbie needs boot floppy please help!!!
danleff replied to mainaa's topic in Everything Linux
What method of downloading will you be using? Modem or nic card on the desktop. If modem, what modem is in the system? Your system specs. are too small to install Mandrake. I also wonder about your video card. You would need more than 1.2 gigs of hard drive space to do a proper install. You might try Damn Small Linux. But you will still need a way to download and extract the files. Also look at DSL install from a floppy.