VectorLinux 7.0 Beta1 bug thread

[fogpipe]

The intel driver (2.14) in the latest beta  is unstable, x quits after not too long with this error:
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error

I have the intel 845g variant of the intel i915. The driver (2.13) in the first beta i tried  was much more stable and noticeably faster.

Much more about this here: http://www.google.com/search?q=intel_uxa_prepare_access%3A+bo+map+failed%3A+Input%2Foutput+error&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

check the top two links

EDIT: I uninstalled the 2.14 intel driver and installed the 2.13 driver from the older beta, xf86-video-intel-2.13.0-i486-1vl70.txz. X seems stable and fast, im tailing the Xorg log and getting no errors. If it gets wonky ill let you know.

Ok, looks like the 2.13 drivers suffer the same problem, they last longer tho and after they start throwing the above error, it doesnt kill X, it just starts rendering in software (vesa?) mode. Very very slowly.

[uelsk8s]

fogpipe,
can you try the kernel here: http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-2.6.37.3-i686-1vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-modules-2.6.37.3-i686-1vl70.txz

let us know if there are any changes.

Thanks,
Uelsk8s

[fogpipe]

fogpipe,
can you try the kernel here: http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-2.6.37.3-i686-1vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-modules-2.6.37.3-i686-1vl70.txz

let us know if there are any changes.

Thanks,
Uelsk8s

I will try that thanks I installed the new 1.10 beta tho and have another problem for another topic. but i will try that kernel.

EDIT: Using beta 1.10. Installed the new kernel, changed the links in boot, booted to the new kernel, did a depmod -a just to make sure and i will let you know how it goes thanks

New kernel (2.6.37.3-i686-1vl70), frozen video after not too long here is the last bit of the syslog at the time:

Mar 14 11:05:12 VL110beta kernel: [    3.946402] VFS: Mounted root (xfs filesystem) readonly on device 8:21.
Mar 14 11:05:12 VL110beta kernel: [    7.730259] ACPI: resource 0000:00:1f.3 [io  0x1880-0x189f] conflicts with ACPI region SBUS [ 0x00001880-0x0000188f flags 0x53]
Mar 14 11:05:12 VL110beta kernel: [    9.809416] fb: conflicting fb hw usage inteldrmfb vs VGA16 VGA - removing generic driver
Mar 14 11:05:12 VL110beta kernel: [    9.826183] Console: switching to colour VGA+ 80x25
Mar 14 11:05:12 VL110beta kernel: [    9.893466] Console: switching to colour frame buffer device 80x30
Mar 14 11:05:24 VL110beta avahi-daemon[1785]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mar 14 11:06:05 VL110beta gdm-binary[1973]: no suitable security token driver could be found
Mar 14 11:22:44 VL110beta kernel: [ 1069.661023] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 14 11:22:44 VL110beta kernel: [ 1069.670223] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 143809 at 143807, next 143810)
Mar 14 11:22:44 VL110beta kernel: [ 1069.997027] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 14 11:22:44 VL110beta kernel: [ 1069.997135] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 143815 at 143807, next 143816)
Mar 14 11:22:44 VL110beta kernel: [ 1069.997243] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Mar 14 11:22:44 VL110beta kernel: [ 1069.997250] [drm:i915_reset] *ERROR* Failed to reset chip.

The ACPI errors are one of the reasons i immediately recompile kernels to work on this crackerjack box hardware.

And here is the last bit of the Xorg log at the time:

[  1357.744] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.745] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.745] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.746] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.746] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.750] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.751] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error

I appreciate the attempted help, i have vl 6 running stably with a few tweaks in xorg and the kernel, and im thankful for that, i guess i will deal with vl7 in about the same way when its final.

[fogpipe]

I just installed the 1.10 beta and am getting errors trying to start firefox.

This is a fresh install with a newly created user. During the install i kept my home partition, but the user is newly created. No modifications to the install at all except creating that user.
I booted from the install cd with the commandline "linux root=/dev/sdb5 ro video=640x480.
The only unusual thing i noticed during the install was that it said that it was 802 mb and it was installing from a iirc 700 mb cd. If thats the problem i can always install from a hd partition. Screenshot of the errors attached. The input / output error dialog box is trying to start from the panel icon.

EDIT: the other apps i have tried work fine, posting this from the 1.10 beta using opera

[rm-r]

ldd  Intel proprietary download

man rdev

NOTE warnings

rdev -v /dev/sd_path option


grep -e EE -e WW /var/log/Xorg.0.log

Now redundant ~ but after lengthy exchanges, you are now appending  "video="  to boot string in VL 6

That was suggested way back in original  suggestions to Colonel Panic

Code:

Edit lilo.conf
(Example: Include line)  Vga=791 (see URL, choose from list)
(Alternate example) append="video=vesafb:mtrr,ywrap,1024x768-32@85"

(If you check, that was before you posted outre theories  Re frame buffers)

Until Intel (& other OEM suppliers) stop  enforcing need for fbcon etc, work-arounds;

Upstream Xorg, kernel (KMS)... then ultimately Distro developers  > have little FOSS alternatives  to correct

[Pita]

Beta-1.10

same problem with flash drive as in Beta-1.9/6/7

Only in Beta-1.8 there was no such problem as posted then.

user cannot mount flash drive when clicking on USB icon:  "Failed to mount "4.0 GB Filesystem", Not Authorized"
If in fstab /dev/sdc1 is enabled it can be mounted by sudo, however, then no
USB icon shows.

Loggin-out of X, console reports:
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.

Logged-in as root. Flash drive can be mounted with USB icon.
Command 'mount' then shows /dev/sdc1 is mounted even so it is disabled in fstab.

[uelsk8s]

Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?

[fogpipe]

My firefox problem was apparently due to xulrunner not being installed, dont know what happend there.
I have downgraded to xf86-video-intel-2.13.0 and the i486 version of libdrm and x is alot more stable, in fact with that and the latest kernel compiled with no acpi, X hasnt crashed once in the last 14 hours or so of almost continual use.

[Pita]

Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?

99.9 % of time I start with startx in runlevel 2.
For curiosity I have tried gdm in VL7* would not remember now if there
was a difference. Will check it out.
Anyhow, eventually it should not make a difference just as in VL6-STD.

[Pita]

Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?

99.9 % of time I start with startx in runlevel 2.
For curiosity I have tried gdm in VL7* would not remember now if there
was a difference. Will check it out.
Anyhow, eventually it should not make a difference just as in VL6-STD.

Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Cannot start fluxbox since there is no provision for it in gdm Session.

[vector]

Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!

Pita....... try startxfce4 instead of startx from runlevel 2 see if everything goes ok after that
let us know

Cheers,
Vec

[GrannyGeek]

Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Cannot start fluxbox since there is no provision for it in gdm Session.

I'm not sure what problem you're referring to. I always use runlevel 2 and startxfce4 and have no severe problems unless I'm having a general X problem.

I got a new computer a couple of weeks ago with NVidia 6150SE onboard graphics. I've had a problem getting my monitor's native 1280x1024 resolution in the correct 5:4 aspect ratio. It's running okay at 1024x768. I haven't had time to see if I can solve the problem but today I hope to install VL6 SOHO Deluxe on it and will see if the problem persists. I think SOHO Deluxe may include the proprietary NVidia driver, which I think is what I need in VL7 but it's not there yet.

This computer is my main test machine, replacing my ancient 1.3 GHz Celeron Tualatin. Linux loved that computer and the computer loved Linux. I hated retiring it, but it couldn't run streaming video without annoying choppiness and it didn't support modern things like SATA, 48-bit LBA, or PCI-e. I got tired of suffering so when I saw this refurbed computer for a very good price, I got it. As it turns out, I think the computer was new and HP was just getting rid of old inventory. So far I'm very happy with it but I've installed just VL7 beta1 and 1.8. I was going to copy over my VL partitions for different versions but decided I'd be better off installing "clean" because the hardware is very different from the Celeron's hardware. The old Celeron had a Radeon 9200 graphics card and ran well with the xorg radeon driver and gave me 1280x1024 with no work on my part.
--GrannyGeek

[Pita]

Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!

Pita....... try startxfce4 instead of startx from runlevel 2 see if everything goes ok after that
let us know

Cheers,
Vec

That's what I have been doing all the time while testing Alpha/Beta in runlevel 2 on console
startxfce4 which causes the problem that user cannot mount flash drive or camera as explained.
Just to make sure I did it now again and the result is the same unlike with runlevel 4.

I will mention as well that in xfce4 runlevel 2 or 4 if I give the command
"startx /usr/bin/startfluxbox -- :2" fluxbox will open, however, commands do not
show in fluxbox, like opening xterm, instead they are all executed and show-up
in xfce4 (Alt-F7). This is not the case in VL6-STD.

[M0E-lnx]

I dont know if this has been addressed yet or not, but as of

Code:

root:# cat /etc/vector-version
Vector Linux 7.0 STD Beta 2 built on MAR-12-2011

Running vsuper gives an error

Code:

vluser:$ vsuper vpackager
/usr/bin/vpackager
gksu: error while loading shared libraries: libgnome-keyring.so.0: cannot open shared object file: No such file or directory

gnome-keyring seems to be installed, but libgnome-keyring is an entirely different package, and it is not present in this release.
Installing libgnome-keyring gets us past that error, but pops another one

Code:

gksu: error while loading shared libraries: libORBit-2.so.0: cannot open shared object file: No such file or directory

So, bottom line, this libgnome-keyring and ORBit2 need to be added to the release before final comes out.

[hata_ph]

Running VL7Beta2 and notice firefox name is change to Namoroka...and missing icon issue with firefox in the menu too