I'm running Slack91 and 2.6.0-xx since about 3 weeks (now 2.6.0-11).
Everything works without any upgrade in Slack. It's very stable and quick with the new low latency features. I just experienced some FB problems when first building my config, but now it's ok.
I have been having some trouble with framebuffer acceleration (black screen on boot) with radeon mobility m6(or m9?)... it thats the same problem you had, please mail your solution to it03(at)it(dot)kth(dot)se
As already mentioned, in lilo.conf, vga=normal
cures the black screen (on my nvidia system too).
Don't know why framebuffer console doesn't work
otherwise, but I can't imaging its a Slackware
issue.
Lilo doesn't need to be altered in any way. Slackware 9.1's default kernel (2.4.22) includes support for framebuffer console mode. You just need to make sure you either compile this feature into your new 2.6.x kernel, or tell lilo not to use this feature (by way of vga=normal). Many people forget to compile in framebuffer console support because it is listed as developmental code, even though it is stable. It wont show up as an option in your kernel config unless you select "Prompt for development and/or incomplete code/drivers" from the code maturity level menu. After developmental code is enabled, then framebuffer console support will appear under the Device drivers/Graphics support section.
heya .. im having the exact same problem on slackware 9.1 . Im using an nvidia riva tnt card (stb velocity 4400 with 16mb ram) and for some reason framebuffer will not work; lilo will just boot up to a blank screen. (the black screen of death) It worked fine with kernel 2.4.22, but since i installed 2.6.1 i am forced to use plain text mode console. Ive tried using 'vga=791' 'vga=795' 'vga=ask'.. but just end up having to use 'vga=normal' or one of the other text specifications.
im sure i checked all the framebuffer options when making the kernel .. if anyone has any ideas, please offer them!
which framebuffer did you configure for your riva tnt card?
I have a tnt card as well and it would not work with the rivafb
driver. The old vesafb driver works fine though. This is
with the 2.6.1 kernel.
once again, im using a riva tnt card (stb velocity 4400, 16mb ram) i selected both the vesafb and the rivafb during the make menuconfig .. so one or the other should have worked .. unfortunately that wasnt the case .. ive read the changelog for andrew morton's latest 2.6.2-rc1-mm3 patch and it looks like it fixes some fb issues .. but i havent tested it
here are the pertinent lines from my .config:
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
CONFIG_FB_RIVA=y
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
CONFIG_FONT_SUN8x16=y
- only 1 install CD
- Kernel 2.6.3 as main kernel compiled with support for frame buffer console , and lots of modules for hardware compatibility
- No KDE, just GNOME and WINDOWMAKER
Hello jeremy. I'm having the exact same problem with Slackware 9.1. I compiled the newest stable kernel (2.6.3) with FrameBuffer + VESA support, and... when i try to boot it up with any vga parameter, it just shows the black screen of death.
Had th same problem with 2.6.4. Worked after some tinkering of the console drivers to find the right one. Otherwise upgrade to 2.6.4 is very smooth apart from some usb/sound driver problems in startup scripts (probably my own fault).
Now running 2.6.4-rc1 on slack-current, with udev unleashed in /dev ;-), ALSA is going fine, daily IDE CD burning, heavy net traffic (poor 8139 on fire), nvidia binary drivers on XFree 4.3.
Got big uptimes, heavy loadavg ;-). I'm rebooting only with new kernel and everything seems stable as rock.
So, SLACK IS BORN FOR KERNEL 2.6 !! ;-)
[Note: I'm still using 2.4 on production machines, 2.2 on routers ;-)]
I am running slackware-current and i had no problems at all until i ran lilo again after updating kernel to 2.4.25-grsec.
I am sure (almost...) that it's not the kernel. This problem is not new to me as in my laptop (ASUS L1400) as i always had it in slackware. However, has i also have redhat linux installed, i typically use the exact same conf file (excepting paths) and it works perfectly.
Now, i don't want to be attached to redhat forever, specially now that is becoming a commercial distro.
Anyway, i still didn't found what can make the difference to make lilo work on redhat and not in slackware.
Using slackware i can only get it working (not perfectly) using:
vga = "normal"
though i wanted to get something like vga = 773 (as in redhat) working...
Hi can you send me your .config file for ASUS L1400
for compiling the kernel I'm not sure but maybe I'm doing something wrong because always have Kernel PANIC :(((((
no problemo
running 2.6.0test11 right now
pha
works great
No problem here, i use 2.6.0-test9. For lilo "VGA=normal" is all i had to change.
Works ok.
I use Slackware 9.1 and Slackware current and 2.6.0-test11 with patch bk5. Seems to work ok now. Experienced bad lockups with older kernel versions.
Be sure to use the patches 2.6.0-test11-bk5 or better, they realy fix things ;-).
It works
I'm running Slack91 and 2.6.0-xx since about 3 weeks (now 2.6.0-11).
Everything works without any upgrade in Slack. It's very stable and quick with the new low latency features. I just experienced some FB problems when first building my config, but now it's ok.
Worth trying :))
framebuffer
I have been having some trouble with framebuffer acceleration (black screen on boot) with radeon mobility m6(or m9?)... it thats the same problem you had, please mail your solution to it03(at)it(dot)kth(dot)se
//
Pontus
See above
As already mentioned, in lilo.conf, vga=normal
cures the black screen (on my nvidia system too).
Don't know why framebuffer console doesn't work
otherwise, but I can't imaging its a Slackware
issue.
vga=normal
Lilo doesn't need to be altered in any way. Slackware 9.1's default kernel (2.4.22) includes support for framebuffer console mode. You just need to make sure you either compile this feature into your new 2.6.x kernel, or tell lilo not to use this feature (by way of vga=normal). Many people forget to compile in framebuffer console support because it is listed as developmental code, even though it is stable. It wont show up as an option in your kernel config unless you select "Prompt for development and/or incomplete code/drivers" from the code maturity level menu. After developmental code is enabled, then framebuffer console support will appear under the Device drivers/Graphics support section.
Good luck!
-->ryan
Thanks
Alright, I never saw the option for Framebuffer console, that is why. Thanks a bunch!!!
no framebuffer under 2.6.1
heya .. im having the exact same problem on slackware 9.1 . Im using an nvidia riva tnt card (stb velocity 4400 with 16mb ram) and for some reason framebuffer will not work; lilo will just boot up to a blank screen. (the black screen of death) It worked fine with kernel 2.4.22, but since i installed 2.6.1 i am forced to use plain text mode console. Ive tried using 'vga=791' 'vga=795' 'vga=ask'.. but just end up having to use 'vga=normal' or one of the other text specifications.
im sure i checked all the framebuffer options when making the kernel .. if anyone has any ideas, please offer them!
thanks
jeremy
vesafb or rivafb?
which framebuffer did you configure for your riva tnt card?
I have a tnt card as well and it would not work with the rivafb
driver. The old vesafb driver works fine though. This is
with the 2.6.1 kernel.
framebuffer
once again, im using a riva tnt card (stb velocity 4400, 16mb ram) i selected both the vesafb and the rivafb during the make menuconfig .. so one or the other should have worked .. unfortunately that wasnt the case .. ive read the changelog for andrew morton's latest 2.6.2-rc1-mm3 patch and it looks like it fixes some fb issues .. but i havent tested it
here are the pertinent lines from my .config:
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
CONFIG_FB_RIVA=y
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
CONFIG_FONT_SUN8x16=y
thanks in advance for any advice
cheers
jeremy
Slackware 9.1 with kernel 2.6
Hi,
Minislack is a small fork of Slackware9.1 :
- only 1 install CD
- Kernel 2.6.3 as main kernel compiled with support for frame buffer console , and lots of modules for hardware compatibility
- No KDE, just GNOME and WINDOWMAKER
I'm searching for a WEB repository for the ISO.
If someone is interested, let me know :)
Thanks
Interested!
I need this minislack dist!
RE: Minislack is a small fork of Slackware9.1
Interested.
Minislack
Hello,
For you to download the ISO of Minislack, I need first to upload it to a WEB repository.
My repository cannot accept more than 100Mo, so I need another one.
Thanks
mini slack
I can provide space. e-mail me cwebgo@flotown.com
Thanks
Hi,
I wanted to thank you for your proposal for hosting Minislack on kerneltrap.
I didn't saw your answer at the time, and I've finally found a hosting site.
See http://shweps.free.fr
Thanks again,
Regards
JP
Hello jeremy. I'm having the
Hello jeremy. I'm having the exact same problem with Slackware 9.1. I compiled the newest stable kernel (2.6.3) with FrameBuffer + VESA support, and... when i try to boot it up with any vga parameter, it just shows the black screen of death.
With the 2.4.22 works perfectly :/
What's wrong?
Slack 9.1; 2.6.4 and FB console
Had th same problem with 2.6.4. Worked after some tinkering of the console drivers to find the right one. Otherwise upgrade to 2.6.4 is very smooth apart from some usb/sound driver problems in startup scripts (probably my own fault).
Ok
Work ok with 2.6.3-mm3
Minislack
Hello,
For you to download the ISO of Minislack, I need first to upload it to a WEB repository.
My repository cannot accept more than 100Mo, so I need another one.
Thanks
Minislack
Hello,
Have you found a repository for Minislack? If so, I would like to try it out.
Thanks
JP
Yes, you can go the website http://shweps.free.fr/minislack.html
Have fun, and please let me know if something doesn't fit your needs, I will do my best to improve Minislack in this way :))
Best regards
JP
Everything is fine
Now running 2.6.4-rc1 on slack-current, with udev unleashed in /dev ;-), ALSA is going fine, daily IDE CD burning, heavy net traffic (poor 8139 on fire), nvidia binary drivers on XFree 4.3.
Got big uptimes, heavy loadavg ;-). I'm rebooting only with new kernel and everything seems stable as rock.
So, SLACK IS BORN FOR KERNEL 2.6 !! ;-)
[Note: I'm still using 2.4 on production machines, 2.2 on routers ;-)]
black screen
hi
I am running slackware-current and i had no problems at all until i ran lilo again after updating kernel to 2.4.25-grsec.
I am sure (almost...) that it's not the kernel. This problem is not new to me as in my laptop (ASUS L1400) as i always had it in slackware. However, has i also have redhat linux installed, i typically use the exact same conf file (excepting paths) and it works perfectly.
Now, i don't want to be attached to redhat forever, specially now that is becoming a commercial distro.
Anyway, i still didn't found what can make the difference to make lilo work on redhat and not in slackware.
Using slackware i can only get it working (not perfectly) using:
vga = "normal"
though i wanted to get something like vga = 773 (as in redhat) working...
thanks in advance
.config for ASUS L1400
Hi can you send me your .config file for ASUS L1400
for compiling the kernel I'm not sure but maybe I'm doing something wrong because always have Kernel PANIC :(((((
m_frizzi(at)libero.it
TIA
MAnlio
slackware rocks
oi....running kernel 2.6.5.....works like a dream.....changed to GRUB though...so much easier & better lookin ;)
no its defanattly NOTT.
no its defanattly NOTT.
Works for Me
antitux@evil:~$ uname -a
Linux evil 2.6.6 #1 Sat Jun 19 06:26:42 MST 2004 i686 unknown unknown GNU/Linux
antitux@evil:~$ lspci
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:04.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
01:04.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 03)
01:04.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port
02:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)
antitux@evil:~$ df -hTa
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 xfs 9.4G 963M 8.4G 11% /
/dev/hda2 xfs 19G 3.5G 16G 19% /usr
/dev/hda3 xfs 83G 15G 69G 18% /home
devpts devpts 0 0 0 - /dev/pts
proc proc 0 0 0 - /proc
usbfs usbfs 0 0 0 - /proc/bus/usb
antitux@evil:~$ free -m
total used free shared buffers cached
Mem: 501 232 269 0 7 160
-/+ buffers/cache: 64 437
Swap: 980 0 980
Asus L1400
Does anyone know what type of graphics card the Asus L1400 has
It's got a Intel 82830 Graphi
It's got a Intel 82830 Graphics Controller.
Adapter Ram - 48MB
Hope this helps
The L1400 has an Intel i830M
The L1400 has an Intel i830M which shares its memory with the system.