Personal computing discussed
Moderators: renee, SecretSquirrel, notfred
PRIME1 wrote:Posting in support of Kubuntu.
Not a fan of Gnome
axeman wrote:The final word on Linux printing is... get an HP printer. Love 'em or hate 'em, they have about the best support.
http://hplip.sourceforge.net/
notfred wrote:axeman wrote:The final word on Linux printing is... get an HP printer. Love 'em or hate 'em, they have about the best support.
http://hplip.sourceforge.net/
Yup, I checked things out when my 7 year old Epson inket died recently and treated myself to a Laserjet 3350. Network printing and scanning from any PC in my house FTW!
BerserkBen wrote:PRIME1 wrote:Posting in support of Kubuntu.
Not a fan of Gnome
If you like Kubuntu I suggest you try the new Mepis 6.5. The install is really nice and easy, has options to automatically loads Nividia drivers if you have newer Nvidia cards and also has an option for people with p965 chipsets so that it recognizes the Jmicron IDE crap. The default is a KDE desktop with Beryl already installed and ready to go. It uses the Ubuntu/Debian repositories so adding repositories is almost the same as if you were using Kubuntu. Give it a shot.
pete_roth wrote:Hey guys, so far still enjoying linux and learning a bit. I am currently having a hard time with using a wireless nic with my router. My laptop in the living room (much farther than my bedroom in proximity to the signal) can get a "very good" signal, I don't think linux detects it at all.
I tried setting it up manually using all the same settings. Is there some trick to it?
mattsteg wrote:Heh, (k)ubuntu's installer does NOT like my machine(figured I'd give a few *nix desktop apps a shakedown and see if they suck any less. Since some of them are kde stuff I figured I'd go that way). The boot would dead-end unless I did the noapic nolapic dance (then it worked two out of three times). When it got into the live environment and I clicked on the installer, the screen where you choose your install partition would just sit there blank for extended periods of time. Then, as wonderful icing, grub ordered my drives differently when in the OS than when booting, so the all of the entries in the grub boot menu were wrong. No worries, it installed grub to the wrong drive's boot record anyway. Took two tries to get the livecd to boot again so I could put grub where it actually belonged.
notfred wrote:I don't really care since it wasn't a huge deal to get stuff working. The drive issues were just due ide and scsi being flip-flopped, for example. It was relatively trivial to get everything going, just annoying to run into all of those little bugs. The ACPI issue is something that I've run into with other installers on this machine at times as well. No biggie to work around.mattsteg wrote:Heh, (k)ubuntu's installer does NOT like my machine(figured I'd give a few *nix desktop apps a shakedown and see if they suck any less. Since some of them are kde stuff I figured I'd go that way). The boot would dead-end unless I did the noapic nolapic dance (then it worked two out of three times). When it got into the live environment and I clicked on the installer, the screen where you choose your install partition would just sit there blank for extended periods of time. Then, as wonderful icing, grub ordered my drives differently when in the OS than when booting, so the all of the entries in the grub boot menu were wrong. No worries, it installed grub to the wrong drive's boot record anyway. Took two tries to get the livecd to boot again so I could put grub where it actually belonged.
mattsteg, that sounds really bizarre that it would have THAT many problems. Given the need for "noapic nolapic" I'm wondering if your BIOS is feeding some screwy ACPI data to the OS. Have you checked for any BIOS updates for this machine? Or tried some of the methods suggested at places like http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
mattsteg wrote:Interestingly enough, a friend recently installed Ubuntu and had grub misnumber his drives as well. I'm wondering if this happens consistently when you boot off of sata/scsi with IDE drives present.
mattsteg wrote:Seems like a poor idea for 1) anything short of major kernel versions have changes like that 2) installers to use different kernels than they install, knowing this.
bitvector wrote:Even if you do buy into that style of development as appropriate, why the insane disconnect between"big, scary changes" and tiny little version number increments? Big change, big modification of version number. Small change, small modification.mattsteg wrote:Seems like a poor idea for 1) anything short of major kernel versions have changes like that 2) installers to use different kernels than they install, knowing this.
#1 depends on your view of what the Linux kernel people should be doing with their releases. They don't see their job as to provide releases that can immediately be booted by the average end-user without the potential for pain. They have a narrower focus and I think that's appropriate.
mattsteg wrote:Even if you do buy into that style of development as appropriate, why the insane disconnect between"big, scary changes" and tiny little version number increments? Big change, big modification of version number. Small change, small modification.
bitvector wrote:I'm sorry, only a fool considers changes that can break booting to be "minor"But as far as "big, scary changes" go, the renaming of devices in doesn't necessarily count as a big scary change from their perspective, even if it could be from an inexperienced user's perspective.
bitvector wrote:And only a fool would consider that minor as well. So?Similar, a major SMP locking change would be a big scary kernel change that would have virtually no impact from a user's perspective.