problems with gentoo-dev-sources-2.6.8

nekonoko · Posted: Wed Aug 18, 2004 5:33 am Post subject:

Interesting - I just burned a CD-R with K3b totaling 600MB and everything worked as it should. What errors are you getting?
_________________
Ecchi nano wo ikenai to omoimasu!

petrjanda · Posted: Wed Aug 18, 2004 5:50 am Post subject:

So does any1 know how to get bootsplash back?
_________________
There is, a not-born, a not-become, a not-made, a not-compounded. If that unborn, not-become, not-made, not-compounded were not, there would be no escape from this here that is born, become, made and compounded. - Gautama Siddharta

ashtophet · Guru Joined: 08 Aug 2004 Posts: 397

sillynazgul · n00b Joined: 18 Aug 2004 Posts: 2

sindre · Guru Joined: 01 Nov 2002 Posts: 315 Location: Norway

nekonoko · Posted: Wed Aug 18, 2004 10:30 am Post subject:

Jefklak · l33t Joined: 26 Oct 2003 Posts: 818 Location: Belgium

Same VFAT thing that does NOT work here.
Using 2.6.8.1-ck1

naseweis · Posted: Wed Aug 18, 2004 2:17 pm Post subject:

Jefklak: You need to enable support for that in your kernel config under "filesystems ---> Native Language Support".
You can set up the right (windows) codepage for your country under "filesystems ---> DOS/FAT/NT Filesystems"
You might as well need to load the 'nls_cpxxx' module manually. On my system, it wasn't autoloaded by the fat drivers.
_________________
Nothing makes a person more productive than the last minute.

Jefklak · l33t Joined: 26 Oct 2003 Posts: 818 Location: Belgium

HermanR · Posted: Wed Aug 18, 2004 9:46 pm Post subject:

After fixing the VFAT-thing in my kernel config (thanks all of you!), I just installed gentoo-dev-sources-2.6.8-r1, which introduces the vesafb-tng framebuffer.

The new framebuffer works okay (I now have 1280x1024@85 instead of 1024x768@60!), but still no bootsplash.

The entry in my grub.conf for this kernel is:

anthonyr · n00b Joined: 28 Jan 2004 Posts: 26 Location: Calgary

gcasillo · Posted: Thu Aug 19, 2004 12:28 am Post subject:

Hell, I couldn't even boot the damn 2.6.8 kernel. It couldn't find my hard drive, a Maxtor SATA and ICH chipset. Root partition should be /dev/hde3, but it can't find it. I tried a couple other drive letters unsuccesfully, and decided to fall back to 2.6.7-r13.

Why is 2.6.8 so fouled up in so many ways? It doesn't even seem close to useable.

anthonyr · n00b Joined: 28 Jan 2004 Posts: 26 Location: Calgary

pengu · Posted: Thu Aug 19, 2004 1:15 am Post subject:

Headrush · Posted: Thu Aug 19, 2004 1:33 am Post subject:

I am using the gentoo-dev-sources-r1 (2.6.8.1)
I am also using udev.

My fstab file has vfat for my windows partition and it mounts fine every time.
K3B has no problems so far with my Sony DRU500A dvd burner.
Gensplash seems to be working too.

I am using the alsa-driver-1.0.5a, not the one included in the kernel. The only problem I have is when alsasound is activated on boot, the machine stops. Its not hung, has the cursor continues to blink in on the framebuffer screen, but never go any further.

Ashe · n00b Joined: 14 Nov 2003 Posts: 34 Location: Sheffield, UK

So lets see.. what's currently broken for me with gentoo-dev-sources 2.6.8?

1) Cdrecord won't burn as user. This is a kernel problem mentioned above, but I seem to remember reading somewhere that it was a deliberate 2.6.8 design decision? I dunnow.

2) supermount removed from gentoo-dev-sources patchset. This is pretty much the other killer for me as far as 2.6.8 is concerned. Submount refuses to work properly unless I set the kernel source to writeable (which is a security risk and a half) and kind of defeats the point of why everyone says we shouldn't be using kernelspace automounting anyway. Ivman is just plain broken for me, insofar as it doesn't unmount cd's properly, partly design decisions in ivman, partly still odd bugs in ivman.

so hey ho, back to 2.6.7 we go.
_________________
"Every problem in the universe can be solved by finding the right long-haired prettyboy, and beating the crap out of him."

saccory · Posted: Thu Aug 19, 2004 2:40 pm Post subject:

mlybarger · Guru Joined: 04 Sep 2002 Posts: 480

gcasillo · Posted: Thu Aug 19, 2004 7:17 pm Post subject:

saccory · Posted: Fri Aug 20, 2004 8:31 am Post subject:

darkangael · Tux's lil' helper Joined: 04 Jul 2003 Posts: 132

pengu · Posted: Tue Aug 24, 2004 12:25 am Post subject:

Chonhulio · n00b Joined: 04 Mar 2003 Posts: 6 Location: Germany

About the cd-recording issues:

The problem is, that Linux' handling of generic-SCSI devices (this includes ATAPI, USB and FireWire CD/DVD-recorders or tape drives) is insecure.
If /dev/hdc is a CD-ROM or CD-RW device, any user with mere read access to /dev/hdc can overwrite the drive's firmware and completely ruin the drive.
To fix this, a command filter was introduced shortly before 2.6.8 was released. This filter is rather pointless, has obviously never been tested and will never achieve security and functionality at the same time. Currently, it just breaks a lot of apps.

See this thread for a discussion and a few fixes proposed by me and others:
http://marc.theaimsgroup.com/?t=109260648900001&r=1&w=2

However, up to now, the only reliable fix is to disable filtering completely. (As proposed by me and frowned upon by Alan Cox).
In the future applications need to be fixed (This means setuid-root supoort. k3b is in a truly bad shape for this). Additionally the kernel should provide a way to configure filters per device to support legacy apps and special cases.

The additional issues concerning audio-cds are real bugs. Con Kolivas has patches:
http://ck.kolivas.org/patches/2.6/2.6.8.1/2.6.8.1-ck4/split-out/bio_uncopy_user-mem-leak.patch
http://ck.kolivas.org/patches/2.6/2.6.8.1/2.6.8.1-ck4/split-out/bio_uncopy_user2.diff

pengu · Posted: Tue Aug 24, 2004 9:56 pm Post subject: