New Posts  All Forums:Forum Nav:

Fesity Fawn - Page 2

post #21 of 83
3/30/07 at 7:59pm
well, I got the big issues to work for me in Feisty- Restricted module mahager didn't work because it needed to be updated (along with 150 other things!! :wow) but of course I didn't know that as I couldn't get online with my wireless card. I ended up plugging in via an ethernet cord, which downloaded the updates and allowed me to set up the Nvidia driver and Beryl. Had to edit my xorg.conf to get the correct screen resolution and refresh rate, but that wasn't bad. I finally was able to get wireless working after I read up on keyrings and what they do. Basically, I had to fist create a keyring with the WEP code on it, then add my home network in. It had me set a keyring password (nt my WEP key, but my login password), and then it worked!

So now my problems with the Feisty Beta are much less serious. THe one I'm working on now is that my touchpad driver isn't being recognized (even though Synaptic Package Manager says it's installed), and I can't use scroll or click-drag functions.

edit: synaptic touchpad works now! I had manually added in the synaptic touchpad settings in xorg.conf, but I just realized that there is a list of all input devices and the touchpad wasn't on it. d'oh! So I added the touchpad to the list and now it's working nicely! After tweaking some settings, it's almost as good as it is in Windows. I don't have any scrolling problems at all (I did with Dapper).
Reply
Reply
post #22 of 83
4/12/07 at 5:19pm
Thread Starter 
1 week to go til feisty goes official.
hope everyone has a clean install and everything works!
although i know abf probably won't try it after he has found his love for pclinuxos
Reply
Reply
post #23 of 83
4/12/07 at 11:48pm
i am actually considering giving ubuntu a shot again since you guys do claim it got faster since the switch from the i386 to default kernel.....i'll also try that prelinking and other junk...but like i said...its just a try. if all hell breaks loose, back to pclos i go!
Reply
Reply
post #24 of 83
4/13/07 at 10:31am

triumph and tragedy

Quote:
Originally Posted by BIGEE1212
1 week to go til feisty goes official.
hope everyone has a clean install and everything works!
although i know abf probably won't try it after he has found his love for pclinuxos

The triumph
A couple of days ago, I noticed that the upgrades that were being downloaded by the update manager included updates to the nonfree kernel stuff and the nvidia modules. So yesterday, I had another go (nvidia-new module) and got the nvidia driver, 97.55 working!

Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder3)  Mon Feb 26 23:38:46 PST 2007

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen         "Default Screen" 0 0
    InputDevice    "Generic Keyboard"
    InputDevice    "Configured Mouse"
    InputDevice    "stylus" "SendCoreEvents"
    InputDevice    "cursor" "SendCoreEvents"
    InputDevice    "eraser" "SendCoreEvents"
    InputDevice    "Synaptics Touchpad"
EndSection

Section "Files"

\t# path to defoma fonts
    FontPath        "/usr/share/fonts/X11/misc"
    FontPath        "/usr/share/fonts/X11/cyrillic"
    FontPath        "/usr/share/fonts/X11/100dpi/:unscaled"
    FontPath        "/usr/share/fonts/X11/75dpi/:unscaled"
    FontPath        "/usr/share/fonts/X11/Type1"
    FontPath        "/usr/share/fonts/X11/100dpi"
    FontPath        "/usr/share/fonts/X11/75dpi"
    FontPath        "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
    Load           "i2c"
    Load           "bitmap"
    Load           "ddc"
    Load           "extmod"
    Load           "freetype"
    Load           "glx"
    Load           "int10"
    Load           "vbe"
EndSection

Section "InputDevice"
    Identifier     "Generic Keyboard"
    Driver         "kbd"
    Option         "CoreKeyboard"
    Option         "XkbRules" "xorg"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "us"
    Option         "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
    Identifier     "Configured Mouse"
    Driver         "mouse"
    Option         "CorePointer"
    Option         "Device" "/dev/input/mice"
    Option         "Protocol" "ImPS/2"
    Option         "ZAxisMapping" "4 5"
    Option         "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
    Identifier     "Synaptics Touchpad"
    Driver         "synaptics"
    Option         "SendCoreEvents" "true"
    Option         "Device" "/dev/psaux"
    Option         "Protocol" "auto-dev"
    Option         "HorizScrollDelta" "0"
EndSection

Section "InputDevice"

\t\t\t\t\t\t\t# /dev/input/event
\t\t\t\t\t\t\t# for USB
    Identifier     "stylus"
    Driver         "wacom"
    Option         "Device" "/dev/wacom"\t# Change to 
    Option         "Type" "stylus"
    Option         "ForceDevice" "ISDV4"\t\t# Tablet PC ONLY
EndSection

Section "InputDevice"

\t\t\t\t\t\t\t# /dev/input/event
\t\t\t\t\t\t\t# for USB
    Identifier     "eraser"
    Driver         "wacom"
    Option         "Device" "/dev/wacom"\t# Change to 
    Option         "Type" "eraser"
    Option         "ForceDevice" "ISDV4"\t\t# Tablet PC ONLY
EndSection

Section "InputDevice"

\t\t\t\t\t\t\t# /dev/input/event
\t\t\t\t\t\t\t# for USB
    Identifier     "cursor"
    Driver         "wacom"
    Option         "Device" "/dev/wacom"\t# Change to 
    Option         "Type" "cursor"
    Option         "ForceDevice" "ISDV4"\t\t# Tablet PC ONLY
EndSection

Section "Monitor"
    Identifier     "Generic Monitor"
    HorizSync       28.0 - 96.0
    VertRefresh     43.0 - 60.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "nVidia Corporation G71 [Quadro FX 2500M]"
    Driver         "nvidia"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "nVidia Corporation G71 [Quadro FX 2500M]"
    Monitor        "Generic Monitor"
    DefaultDepth    24
    Option         "RenderAccel" "True"
    Option         "AllowGLXWithComposite" "True"
    Option         "AddARGBGLXVisuals" "True"
    SubSection     "Display"
        Depth       1
        Modes      "1920x1200"
    EndSubSection
    SubSection     "Display"
        Depth       4
        Modes      "1920x1200"
    EndSubSection
    SubSection     "Display"
        Depth       8
        Modes      "1920x1200"
    EndSubSection
    SubSection     "Display"
        Depth       15
        Modes      "1920x1200"
    EndSubSection
    SubSection     "Display"
        Depth       16
        Modes      "1920x1200"
    EndSubSection
    SubSection     "Display"
        Depth       24
        Modes      "1920x1200"
    EndSubSection
EndSection

Section "Extensions"
    Option         "Composite" "Enable"
EndSection

Flushed by success I installed Beryl 0.2.1 too, and soon has rotating desktops, water ripple cursors and flaming windows to amuse myself with.

I had rebooted a couple of times and it was all working well. I hadn't gone as far as setting Beryl to auto-load on startup, though.

The tragedy
Update manager downloaded a bunch of other updates last night. I admit that I payed no atttention to what they were.
I rebooted and ... oops. Won't boot. The kubuntu logo appears, with a progress bar sitting at the very start and not moving. Then there is a pause fr a while, Finally I get a text screen which says:

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) built in shell (ash)
Enter 'help' for a list of built-in commands

/bin/sh: can't access tty; job control turned off
(initramfs) _

What is a busybox and how bad is this?
Reply
Reply
post #25 of 83
4/13/07 at 12:06pm
Hmm well it boots.

Unfortunatly I would need more info to tell what exactly is going on. Busybox is generally a series of software, often times used for a base to a system.

http://busybox.net/about.html

What is odd to me about this is the fact that you are in the ASH shell. I didn't even realise that Ubuntu used that.

During bootup you should be able to hit ESC to see what is going on, and even possibly start an interactive startup, do that and see if you can tell what is failing. Also check dmesg.

Seablade

PS Betting that if ABF switches he goes through 5 distros before settling on one again
Reply
Reply
post #26 of 83
4/14/07 at 2:56pm
*buntu uses busybox in its initramfs. Initramfs is a very, very small Linux system that mounts certain drivers and other utilities--basically makes sure the hardware is turned on and functional--before booting the rest of the system after switching to the main part of the operating system. Busybox provides the necessary tools for this process without the bloat of using coreutils or comparable, full-size packages.

I've really oversimplified this. If y'all want a more technical explanation, I'll post again with my best understanding of it.
Reply
Reply
post #27 of 83
4/14/07 at 6:58pm
Quote:
Originally Posted by seablade
Hmm well it boots.
No, it halts part way and doesn't complete booting.

Quote:
Originally Posted by seablade
Unfortunatly I would need more info to tell what exactly is going on. Busybox is generally a series of software, often times used for a base to a system.

http://busybox.net/about.html

What is odd to me about this is the fact that you are in the ASH shell. I didn't even realise that Ubuntu used that.
I believe that the busybox in this case is an error recovery console, that is only available during boot.

Apparently there was an error in initramfstools, whatever that is.

The wonders of turned up some other folks with a similar error, something to do with the PATA driver (disks are SATA but the DVD-ROM is PATA?). Not sure it was the same, actually.

Having pondered various ways to recover from this - kubuntu disk does not seem to have a recovery option - I realized that one of the older kernels still listed in the grub menu might boot. It did. I was then able to use the adept updater to download new updates, which included a new kernel, which does not have this error.

So I am back up and running again, have re-enabled NVIDIA driver and Beryl.
Reply
Reply
post #28 of 83
4/14/07 at 6:59pm
Quote:
Originally Posted by Colin Dean
*buntu uses busybox in its initramfs. Initramfs is a very, very small Linux system that mounts certain drivers and other utilities--basically makes sure the hardware is turned on and functional--before booting the rest of the system after switching to the main part of the operating system. Busybox provides the necessary tools for this process without the bloat of using coreutils or comparable, full-size packages.

I've really oversimplified this. If y'all want a more technical explanation, I'll post again with my best understanding of it.

Actually if you have the time, I would be interested. Is it like a microkernel?
Reply
Reply
post #29 of 83
4/19/07 at 5:01pm
Thread Starter 
It's OUT!
just burned the iso, gonna install now.
good luck to everyone else installing feisty!
Reply
Reply
post #30 of 83
4/19/07 at 8:56pm
talk about SLOW! updating my desktop from what started life as a 6.06.... and its d/ling @ .8kb...w00t!
Reply
Reply
post #31 of 83
4/19/07 at 11:21pm
Quote:
Originally Posted by BIGEE1212
It's OUT!
just burned the iso, gonna install now.
good luck to everyone else installing feisty!

For those of us who have been running betas and updating daily, is there any benefit to a clean install up the release version? Last two days I have been told there are no updates available. So I assume its all the same versions.
Reply
Reply
post #32 of 83
4/20/07 at 4:51am
Why not? I've got a Beryl bug (Emerald themes don't work) after I uninstalled and reinstalled it, so I'm going to do a clean install of the official release and hope that fixes it. Currently at 46% downloaded at 425 Kbps. Oh, and for something to amuse yourselves with: https://bugs.launchpad.net/ubuntu/+bug/107648
Reply
Reply
post #33 of 83
4/20/07 at 6:01am
Attempting download now....at 24kbps....

Hopefully my laptop will find this one more friendly than the previous betas. I didnt have a screen, AT ALL. No terminal drop, I'm not sure if X started, my screen just turned off. I even plugged in an external monitor to make sure it wasnt looking at my DVI as a primary monitor.
Reply
Reply
post #34 of 83
4/20/07 at 10:04am
This is what Bittorrent is for

Seablade

Who isn't downloading right now sorry
Reply
Reply
post #35 of 83
4/20/07 at 10:43am
That was with bittorrent
Reply
Reply
post #36 of 83
4/20/07 at 11:38am
I've been running Feisty for over a month now... Only had one issue in that time (Network Manager didn't work with a Static IP- currently fixed). I can't believe with all the major updates nothing seriously broke... Some people seemed to have major kernel issues, so maybe that didn't affect amd64 users.
Reply
Reply
post #37 of 83
4/20/07 at 7:30pm
well, everything except undervolting (The latest kernel release doesn't seem to want to compile correctly. ) is currently working fine in the release version of Ubuntu Feisty (speedstep still doesn't work when using the generic kernel and plugged in, but that's what the 386 kernel is for). For anybody who's interested, I put a screenshot in the April Desktops thread in Off Topic.
Quote:
Originally Posted by bigtrouble77
Some people seemed to have major kernel issues, so maybe that didn't affect amd64 users.
I think they figured out that the main issue was improper recognition of SATA hard drives. And regardless, the issue was fixed in less than 48 hours, as I recall.
Reply
Reply
post #38 of 83
4/20/07 at 8:22pm
As expected, my laptop has zero video in Fesity. Any attempts to boot and and my monitor shuts off right before it starts X.
Reply
Reply
post #39 of 83
4/20/07 at 11:54pm
So when X starts do a CTRL+ALT+F2 to switch to a console to troubleshoot. I might think it might be switching to an external port by default on accident.

Seablade
Reply
Reply
post #40 of 83
4/21/07 at 12:33am
I already made sure it wasnt using my DVI. I'll drop to console and see what happens. Thank you ATI.....
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux & Other OS's