SimplyMEPIS 6.0 Linux Final Release:

  • Thread starter Thread starter Bad Dog
  • Start date Start date
Mark said:
Craig, pay attention to what Bad Dog here says -- I know him by another
nym in a different forum, and he is much more knowledgeable than I am
regarding MEPIS.

Yup Uncle Mark, the way we keep bumping in to each other on net, I knew
it was just a matter of time, not that I'm trying to hide. :-)

--
regards,
Bad Dog

INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0
KDE 3.5.1 - Kernel 2.6.15-26-686-SMP - My iMAC runs Debian Sarge
 
My experience says otherwise. Programmers who do it for free are doing
it for their own pleasure, not for mine. Nothing wrong with that at
all, just don't compare them to people who are actually programming
for me in order to get me to spend some of my money.

Good. Since they're programming for you, could you please ask them
to stop this WPA/DRM/WGA stuff?

Thank you. :o)
 
Mark said:
I've seen that. I figure it's only a matter of time.




Please do. This is a strange one.

I obviously am out of my league with this kind of thing, but it makes no
sense to me that a MEPIS driver could disable a NIC in Windows. <shrug>

A lot of NIC hardware support shutting off, "waking up" & other stuff.
NIC drivers for Winderz & Unix (& I'd imagine Linux) support this and,
once a NIC is turned off, well...it's off. eh? Notice that unplugging
the 'puter undoes the dammage
It's pretty cool when the guy that writes the freaking distro responds
to the bug reports. Talk about a one-man-band...
Whoa. That's the Mepis guy? What fun!

-Craig
 
Bad said:
Yup Uncle Mark, the way we keep bumping in to each other on net, I
knew it was just a matter of time, not that I'm trying to hide. :-)

Keep this up and I'm gonna think you're a net-stalker. :O)
 
I have an oddity on my oldish (700MHz, 256MB) Dell laptop. If I *reboot*
from MEPIS or Ubuntu to XP on that machine, I lose the 'tap-click'
function on the touchpad. (The left and right mouse click buttons work
fine.) Boot direct to XP on powerup and it's there. <shrug>

Are you sure you don't need a driver to give you the tap-click
function? Maybe something by Alps? Maybe linux does something to
prevent the driver from loading on a warm boot?
 
I obviously am out of my league with this kind of thing, but it makes no
sense to me that a MEPIS driver could disable a NIC in Windows. <shrug>

There are some things that can be set (or reset) that don't go back to
normal until you turn the power off, and that the Windows driver may
assume (remember, this is Windows) are at the power-up default, so it
doesn't set them to what it needs.
 
Al said:
Are you sure you don't need a driver to give you the tap-click
function? Maybe something by Alps? Maybe linux does something to
prevent the driver from loading on a warm boot?

I've really not investigated it. For me, it's a very minor annoyance.
It's rare that I would really feel the need to reboot from MEPIS or
Ubuntu into Windows. The laptop is more toy than tool, used for the
occasional road trip and on the infrequent technical house call. If I'm
playing on the net, I boot to MEPIS or Ubuntu and stay there. If I need
access to my "toolbox", I boot to Windows.
 
OK;

(this is wrt my Broadcom 440 10/100 NIC being made unavailable on win2k
after I'd installed mepis 6.0 on another partition. Fwiw, this has been
reported to occur w/3.1 and 3.3.1 as well)

Warren was right: Apparently both mepis network drivers (the one in the
kernel and the other added on boot up) were wrecking mayhem on
shut-down. The solution is to:

1) remove the offending network driver via synaptic (or apt-get)
2) shut down system and /unplug/ computer from electrical outlet
3) replug, reboot
4) all is well

Thx to...was it "bad" dog? Anyway, that guy w/the funny name who
recommended I email devATmepis.org w/the problem. Thx to Mark for being
so enthused about this disto that I couldn't let it slip by.

For those who like the "user-friendly" aspect of Ubuntu but chafe
against its restrictions, Mepis seems to be just as user-friendly but
closer in flexibility to Debian.

fyi

-Craig
 
Craig said:
Thx to...was it "bad" dog? Anyway, that guy w/the funny name who
recommended I email devATmepis.org w/the problem. Thx to Mark for being
so enthused about this disto that I couldn't let it slip by.

Bad Dog is into this distro up to his elbows. Me, I'm just a rowdy fan.

I gotta pull for Warren -- he's a true craftsman when it comes to this
stuff. This is what open source is all about.
 
Craig said:
(this is wrt my Broadcom 440 10/100 NIC being made unavailable on win2k
after I'd installed mepis 6.0 on another partition. Fwiw, this has been
reported to occur w/3.1 and 3.3.1 as well)
Warren was right: Apparently both mepis network drivers (the one in the
kernel and the other added on boot up) were wrecking mayhem on
shut-down. The solution is to:
1) remove the offending network driver via synaptic (or apt-get)
2) shut down system and /unplug/ computer from electrical outlet
3) replug, reboot
4) all is well
Thx to...was it "bad" dog? Anyway, that guy w/the funny name who
recommended I email devATmepis.org w/the problem. Thx to Mark for being
so enthused about this disto that I couldn't let it slip by.
For those who like the "user-friendly" aspect of Ubuntu but chafe
against its restrictions, Mepis seems to be just as user-friendly but
closer in flexibility to Debian.

Now, how is that for support...How much did you say you paid for that
distro. :-) Craig, I'm happy it's working for you.

--
regards,
Bad Dog

INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0
KDE 3.5.1 - Kernel 2.6.15-26-686-SMP - My iMAC runs Debian Sarge
 
Mark said:
Bad Dog is into this distro up to his elbows.

Just an Old Dog with to much free time on my hands.
Me, I'm just a rowdy fan.

Sure you are. ;-)
I gotta pull for Warren -- he's a true craftsman when it comes to this
stuff. This is what open source is all about.

He's da Man!

--
regards,
Bad Dog

INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0
KDE 3.5.1 - Kernel 2.6.15-26-686-SMP - My iMAC runs Debian Sarge
 
The 433MHz processor should suffice, but for the Live CD to be
reasonably useful you really need 512MB RAM. Installed you could get
away with 256MB. 128MB just ain't gonna cut it either way.

It does install and run on 128 Mb!!

Ive opened the open office wordprocessor, but got no docs could access to
play with.

I plugged in my memory stick and it worked right away! but I couldn't make
amarok play any of the midi files on it - but I could play a CD.

I was going to change the boot order to windows first, the way you told me,
but menu1st has changed, so I didn't dare touch it - I wonder if you could
help again? it looks a lot simpler, but I don't want to make it unbootable,
or have to work in the knigon equivalent of DOS to rescue it.

The new menu1st file looks like this

"timeout 15
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title MEPIS at hda3, kernel 2.6.15-26-386
root (hd0,2)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/hda3 nomce quiet vga=791
boot

title Windows at hda1
rootnoverify (hd0,0)
chainloader +1

title MEMTEST
kernel /boot/memtest86+.bin"


If it hasn't damaged the windoze on that box, I might try it on my main
one, Mepis clearly needs more whizz than that box has; or upgrade the
memory, but it's prolly easier to bite the bullet.

I'd be very grateful if you could advise how to alter this

mike
 
mike said:
It does install and run on 128 Mb!!
Excellent!

Ive opened the open office wordprocessor, but got no docs could access to
play with.

I plugged in my memory stick and it worked right away! but I couldn't make
amarok play any of the midi files on it - but I could play a CD.

That may mean you need to install some codecs. Open Synaptic, then
Settings>Repositories, and make sure all the repos are enabled. Then
Reload, Mark All Upgrades, and Apply. Hopefully, that should do it.
I was going to change the boot order to windows first, the way you told me,
but menu1st has changed, so I didn't dare touch it - I wonder if you could
help again? it looks a lot simpler, but I don't want to make it unbootable,
or have to work in the knigon equivalent of DOS to rescue it.

The new menu1st file looks like this

"timeout 15
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title MEPIS at hda3, kernel 2.6.15-26-386
root (hd0,2)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/hda3 nomce quiet vga=791
boot

title Windows at hda1
rootnoverify (hd0,0)
chainloader +1

title MEMTEST
kernel /boot/memtest86+.bin"

Open this same file as root using Super User File Manager, then simply
use cut/paste to move the Windows "stanza" above the MEPIS stanza. Save
changes from the File dropdown. This will move Windows to the top of the
boot list and will make it the default boot after 15 seconds.
 
Mark said:
http://en.wikipedia.org/wiki/Shite
"A synonym for shit which originated from Ireland."

It gives ones words a harsher edge.

It figures...

I picked up "shite" from a fine Irish gent. Pleasantly, out here in
California, it's still an overlooked oddity and chances are it is taken
in the same vein as "stuff."

-Craig aka "the cuss-whisperer"
 
ORIGINAL MESSAGE:



------------ REPLY SEPARATOR ------------

I normally don't like "me too" postings, but me too on this one.

If there is a website where you can go and purchase hardware
guaranteed to work with Linux, it isn't getting much exposure.

If you know of one, expose it!


Guarantees are not that hard to find. The hard part is avoiding the
bogus ones.

I was just looking at the Knoppix.com site, debating whether to invest
a few hours once more in getting the latest LiveCD (my last Knoppix
download cost me three coasters, a few wasted hours, and nothing to
show for it in the end).

While there, I noticed that the very modest system requirments don't
appear to have changed in the past two years or so (486 CPU, 128MB of
RAM for GUI use ...). Question is, is it true, or has Knopper just
been too busy to update it?



Mepis is pretty good compared to a lot of the Knoppix imitators out
there, but nothing to get ecstatic about. I loaded a two year old
Simply Mepis this evening to look at a hard drive DOS/Windows can't
seem to figure out. It appeared to get a handle on it readily, even
though it was connected via USB2.0. OTOH, it couldn't copy two files
sitting on a 256MB CompactFlash card in a USB card reader connected
to the same USB hub.
 
Back
Top