Ubuntu on VIA C4/disable cpuspeed/where is interactive mode

[Unique_Rabbit]

Hey guys... in a nutshell... :)

Trying to install Ubuntu 6.10 server on a VIA C3 system. Rumor has it of some missing command in the processor that is needed by the latest kernal... can't find much. I have been told to turn of cpuspeed, via grub boot menu, and by using interactive mode.

I can't find interactive mode to bypass it, to eve see if it works...

How/where/when/for how many cookies do I find interactive mode?

Is there another way to turn it off permanently if/when/while doing so?

[dkeav]

umm im not exactly sure what you are asking, im going to guess about cpu frequency scaling which your processor doesnt have, so you dont have to disable it because it just wont do anything anyways, disabling it wont have an effect because it never had an effect to begin with

i think by interactive mode you are either referring to kernel interactive mode which really wont help you, or you mean just logging the console period

either way i fail to see your problem here, if frequency scaling module is causing a problem with stability or something in your kernel, then post some errors and we will go from there, otherwise let it go

[Unique_Rabbit]

I, to the best of my knowledge, can't post any errors, since I can't send you a screenshot of a lockedup machine. :)

When ubuntu goes to boot up, any time other than during installation, it says Starting up... and that's it... game over.

What I'm referring to is, I have seen on another couple of sites, that the VIA C3 processor in this machine lacks some cpu code that all the others have, and that by disabling cpuspeed, it doesn't matter.

Now, "so you dont have to disable it because it just wont do anything anyways, disabling it wont have an effect because it never had an effect to begin with" doesn't seem accurate from what I've read, because the kernel doesn't seem to know it doesn't work, and when it checks to see if it can/has to, it locks the box up. Sort of like it "believes" it can, but when it tries to query the status, it goes to lalaland...

Now, since I can't get into the box, I can't get to error logs, even if I knew where to get them. :)

Now, another post (http://bugs.centos.org/view.php?id=1270) shows this, and that using interactive mode, I can select items (services, I believe) as it is booting, and that I could then bypass cpuspeed, and at least it would boot... I could then try to find out how to remove the ability/service cpuspeed completely...

Make more sense? Sorry, I've been posting this all over, and realized I didn't give you any background, since all I was trying to do was disable/remove cpuspeed, or find the magical interactive mode.

[happybunny]

during ubunto boot up, can you hit like f2 or something to get "behind" the pretty splash screen?

If so, near the begining of the boot process there should be an option that says "HIt I for interactive mode".

[Unique_Rabbit]

No love...

I get the Hit Esc for the Grub Menu.
If I do nothing, it goes to Starting up... and dies.

If I DO hit Esc, I get 3 options:
Ubuntu, kernal 2.6.17-10-server
Ubuntu, kernal 2.6.17-10-server (recovery mode)
Ubuntu, memtest86+

The memtest86+ does what it says... brings up memtest...
The other two do the same as if I had ignored the grub menu...

Starting up... and nothing.

[dkeav]

just a guess but i doubt it has much to do with cpufrequency scaling code in the kernel and probably more to do with lack of decent ACPI support, try disabling acpi

[Unique_Rabbit]

It's all disabled...

Just for reference, did anyone else read the post I listed?

http://bugs.centos.org/view.php?id=1270

It shows the same processor having trouble with linux...

And, I take it, Ubuntu must be something off the beaten path? Since the Internet isn't really too helpful for it. Just the howto that is "exactly what I want", is for Ubuntu.

Oh well, guess I go back to my windows world... at least when something breaks there, I know how to fix it... wasted enough time on linux for this adventure.

Thanks for the help... at least here I got replies... most of the sites I posted to seemed to overlook my posts... hundreds of replies to other stuff, but not even a simple "this is how to get to interactive mode"...

<steps down off soapbox>
<jumps through a (perfectly running) open window>

[dkeav]

you are perfect for windows, encounter a problem and run screaming the other direction, enjoy

[psych-major]

It's all disabled...

Just for reference, did anyone else read the post I listed?

http://bugs.centos.org/view.php?id=1270

It shows the same processor having trouble with linux...


Yes, I read the post you linked, what exactly does a CentOS forum post have to do with a Ubuntu install/issue?

One thing you didn't post was whether you are trying to use the live CD, or alternate install CD. I have seen several cases where the live CD would just hang, probably due to low memory, but I'm not sure, however the install CD would boot and do its job just fine.

By fixing Windows, I assume you mean running to the store like a good lemming and purchasing another one? At least be a little imaginative and run a Mac.

I think what is really at issue here is the soapbox you mentioned in your (hopefully) last post. You are more interested in whining about something you don't care to understand, and you think that your attempt at cleverness might amuse or in some way affect the regular readers here. Oh well, at least you tried.

So, enjoy that Via C3 running Win95, or ME or whatever your MSTD (http://www.urbandictionary.com/define.php?term=MSTD) of choice is. When you eventually wake up and feel Bill's death grip on your unmentionables, and you want to try again on a real OS, humbly approach the forum of Linux knowledge and we will be glad to give you a hand.

[ladoga]

In case you still have your ubuntu install around.

1. Hit "e" while your system is booting up (to edit grub menu).
2. Press arrow down to select kernel.
3. Hit "e" again.
4. Add 1 to the end off line (just press "1" key)
5. hit enter
6. hit "b" to boot up

If your problem is same that is mentioned in CentOS bug report that should solve it.