Home

I will upgrade to the 2.6 kernel...

Submitted by Jeremy
on November 16, 2003 - 4:06pm
when 2.6.0 is released.
17% (316 votes)
after a few stable 2.6 kernels have been released.
17% (330 votes)
when 2.6.10 is released.
3% (53 votes)
when my distribution makes it available to me.
16% (295 votes)
I've been using it since 2.6.0-test
30% (573 votes)
I've been using it since late 2.5 development
11% (202 votes)
I've been using it since early 2.5 development
5% (86 votes)
never. I'm still happy with my ultra-stable 2.2 kernel.
2% (35 votes)
Total votes: 1890

i'd use it if lirc worked

Anonymous
on
November 17, 2003 - 2:59am

...but right now, lirc works just with 2.4...

lirc

Tomasz T.
on
November 17, 2003 - 12:40pm

Try lirc-0.7pre and kernel patch avaiable somewhere from http://bytesex.org/

--
:wq

[x] when vmware doesn't requi

Anonymous
on
November 17, 2003 - 10:09am

[x] when vmware doesn't require so much voodoo, and when my ATI drivers worked.

Anonymous
on
November 17, 2003 - 11:08am

I got ATI drivers working for 2.6, biggest problem was that the wrong AGP drivers were loaded, in this case some via agp module needed to be loaded instead of agpgart, can find it in /lib/modules/path/to/agpstuff (may be the case for other chipsets too). Also needed to download another driver package, because the first one didn't compile (don't forget to make sure that /usr/src/linux points to the 2.6 kernel).

VMware works fine with 2.6.0-testxx

Anonymous
on
November 21, 2003 - 9:31pm

I've been using the 2.6.0-test RPMS from Arjun for a couple of months now without any real problems. With the semi-supported patch/script (from vmware (vmware-any-any-update??.tar.gz) it's as simple as unpacking the archive and running a script. See the vmware newsgroup for good support and discussion.

I'd use it if it worked with my ATAPI cdrom. [NT]

molo
on
November 17, 2003 - 12:45pm

I'm in 2.4 now so I can read/burn CDs. Even reading CDs fails on 2.6.0-test9 (with the ide-cd driver, not ide-scsi).

I've found this as well

Anonymous
on
November 18, 2003 - 1:37pm

I'm in 2.4 now so I can read/burn CDs. Even reading CDs fails on 2.6.0-test9 (with the ide-cd driver, not ide-scsi).

I've found this as well, with 2.6.0-test9-mm3.

Reading CDs and DVDs via the ATAPI interface works most of the time, but will eventually hang the box (hard, requiring a power cycle)... particularly if I am watching a DVD.

Writing DVDs via the ATAPI interface is unreliable, but has worked on occasion. Writing CDs results in CDs that fail checksum checks against their origin ISOs (and the CDs are useless).

Using ide-scsi instead of ATAPI fixes the writing difficulties. I have not yet confirmed whether it also fixes the hard hangs when reading lots of data from DVDs.

So it looks like you are correct -- ATAPI support in 2.6.0-test9-* still needs quite a bit of work, either on the kernel side, or on the application side (dvd+rw-tools, cdrtools).

Mine is different.

molo
on
November 18, 2003 - 1:46pm

Yes, its certainly broken, but mine is broken differently. And its certainly on the kernel side. No hard locks for me. Instead, I quickly error out when reading from the cd. There's then a bunch of messages in the kernel buffer. I get this with out without DMA enabled. Similar errors when writing CDs (aka making coasters). I'm back on 2.4 until this gets resolved.

I tried emailing Jens Axboe, but I never got a response.

Here's an example session of an attempted read:

# dd if=/dev/hdc of=/dev/null
dd: reading `/dev/hdc': Input/output error
128+0 records in
128+0 records out
65536 bytes transferred in 10.317440 seconds (6352 bytes/sec)

# dmesg
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev hdc, sector 4293091416
Buffer I/O error on device hdc, logical block 32
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev hdc, sector 4293091420
Buffer I/O error on device hdc, logical block 33
hdc: command error: status=0x51 { DriveReady SeekComplete Error }

[.. repeats ..]

Then, without DMA:


# hdparm -d0 /dev/hdc

# dd if=/dev/hdc of=/dev/null
dd: reading `/dev/hdc': Input/output error
1800+0 records in
1800+0 records out
921600 bytes transferred in 20.447388 seconds (45072 bytes/sec)

# dmesg
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev hdc, sector 1800
Buffer I/O error on device hdc, logical block 225
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev hdc, sector 1808
Buffer I/O error on device hdc, logical block 226
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev hdc, sector 1816
Buffer I/O error on device hdc, logical block 227
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50

[.. repeats ..]

I tried emailing Jens Axboe, but I never got a response.

-molo

I'm not speake english and it's the problem.I'm not you answer

Anonymous
on
March 10, 2004 - 7:35am

I love you. actually, I'm studing computer science in order to find a job

why not use it

Anonymous
on
November 18, 2003 - 2:48am

Only real problem I've run into at the moment is valgrind, which I really wanted to try out, but I guess I'll be waiting until they update it (better that then downgrade). I've been using it since 2.5.70, and it is actually usable now (on 2.5.70, I remember ncurses for me kept on bombing out).

overall, its looking good.. Many apps work on 2.6, its definately stable.. hasn't jammed up for me ever (even 2.5.70 never did, except by my dumb fault, like messing around with kernel modules). I feel the new schedulars have helped a massive amount (trying to play a game on 2.4, then 2.6 confirmed this for me), and hopefully, by 2.6.3, everyones using it, like it deserves. Hopefully by 2.8, the company which owns the unix copywrites (we all know who they are), by then are completely out of the equation too.

Not really related, but anyone on gentoo tried udev yet? Just curious if its stable enough, and complete enough to use instead of /dev. And I know gentoo needs /dev support to boot, so curious if it will currently even boot using udev instead of compiled in udev...

probably better to wait I guess then..

auzy
on
November 20, 2003 - 1:25am

well, udev 006 just came out (this is the same guy again), and I guess development and effort to get udev working well, will accellerate and it will properly be supported. Thanks, guess I'll just wait a bit.. hopefully 2.6 test10 comes out soon though, I'm getting bored with 2.6 test9 already, might try the mm patch

when I get it to run

Anonymous
on
November 18, 2003 - 6:56am

I tried test2 and test9 but I didn't get it to run on my PC.. my ps/2 keyboard does not respond after booting the test9..

Check your .config

molo
on
November 18, 2003 - 1:37pm

See if your .config contains these lines:


CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VGA_CONSOLE=y

See also the Post-Halloween document.

I did but ..

michal017
on
November 20, 2003 - 3:49am

Yes, I have all these in my .config file.

as soon as i have support for

Anonymous
on
November 20, 2003 - 5:12am

as soon as i have support for my hardware, so mainly this happens:

- ATI releases their drivers foor 2.6 (has happend in the mean time, i think)

- nvidia brings out their nforce drivers foor 2.6 (there are exprerimental drivers afaik, but i prefer real, working ones ...)

nforce and 2.6

Anonymous
on
November 23, 2003 - 12:09pm

Kernel 2.6.0-test9-mm4 compiled on fedora core 1 works perfectly with my nforce2 motherboard (asus a7n8x).

The new GPL forcedeth driver for the onboard lan worked without changing any settings (previously used kernel 2.4 with nvidia driver).

When my module will be available

Anonymous
on
November 20, 2003 - 7:40am

I'm waiting for my adsl modem (Sagem Fast USB 800, cf: www.eagle-usb.fr.st) to be compatible with 2.6. Otherwise, it's useless...

...when I'll be able to use my Firewire HDs

Anonymous
on
November 21, 2003 - 5:41pm

Sadly each -test release I checked fails to reckon my hard-drive whereas it worked fine with 2.4.x... I'm using it on a Sony Vaio C1VE but a friend using a "regular" box faces the same problems with those bleeeeding edge kernel series... I really hope to see it working soon as I really enjoy those the rest of the time when I have no need to use ieee1394...

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.