| View previous topic :: View next topic |
| Author |
Message |
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
 Posted: Wed Jul 07, 2004 7:36 pm Post subject: Re: bootsplash |
 |
|
| Tazok wrote: | | Mafteah wrote: |
Yes, It should work. |
Cool, bootsplash is working again.
But I don't get more than 60Hz using this line:
video=vesafb:ywrap,vram:16,1024x768-16@75 |
try
video=vesafb:ywrap,1024x768-32@75
_________________
http://www.mafteah.co.il |
|
| Back to top |
|
 |
Tazok
Guru
Joined: 25 Oct 2003
Posts: 310
|
| Posted: Wed Jul 07, 2004 7:46 pm Post subject: Re: bootsplash |
|
|
| Mafteah wrote: |
try
video=vesafb:ywrap,1024x768-32@75 |
Hmm, this does not work with framebuffer at all.
In my dmesg output, I found the following lines:
| Code: | vesafb: abort, cannot ioremap video memory 0x8000000 @ 0xd0000000
vesafb: probe of vesafb0 failed with error -5 |
|
|
| Back to top |
|
|
theonlymcc
Apprentice
Joined: 16 Sep 2003
Posts: 274
Location: NC
|
| Posted: Wed Jul 07, 2004 7:53 pm Post subject: |
|
|
I still get a kernel crash using vesafb:tng. Here is part of the trace that I can see.
| Code: | kernel BUG at arch/i386/kernel/smp.c: 358!
invalid operand: 0000 [#1]
PREEMPT SMP
... blah blah
<6> note: vesafb[43] exited with preempt_count 2 |
|
|
| Back to top |
|
|
sparhawk37
n00b
Joined: 20 Jun 2004
Posts: 24
|
| Posted: Wed Jul 07, 2004 7:54 pm Post subject: |
|
|
| Zyne wrote: | well... I still seem to be having quite a few problems with my SATA.
I tried using my old .config, and tried compiling the love-sources back from scratch, and I'm still stuck at the same problem. My sata devices don't get added to the devices list (/dev/hde and /dev/hdg)
I just unmerged the love-sources just because they're of no use to me like this. My main hd (root) is PATA, but my data disks are SATA, and I can't work without those...
my hardware: ASUS A7N8X Deluxe M/B with sil3112A SATA chipset.
Here's the output of my /var/log/messages:
| Code: |
Jul 7 19:52:23 vubserver NFORCE2: IDE controller at PCI slot 0000:00:09.0
Jul 7 19:52:23 vubserver NFORCE2: chipset revision 162
Jul 7 19:52:23 vubserver NFORCE2: not 100% native mode: will probe irqs later
Jul 7 19:52:23 vubserver NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
Jul 7 19:52:23 vubserver NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
Jul 7 19:52:23 vubserver ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
Jul 7 19:52:23 vubserver ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Jul 7 19:52:23 vubserver hda: IC35L060AVVA07-0, ATA DISK drive
Jul 7 19:52:23 vubserver hdb: WDC WD200EB-00CSF0, ATA DISK drive
Jul 7 19:52:23 vubserver ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jul 7 19:52:23 vubserver hdc: Pioneer DVD-ROM ATAPIModel DVD-105S 013, ATAPI CD/DVD-ROM drive
Jul 7 19:52:23 vubserver hdd: LITE-ON LTR-48246S, ATAPI CD/DVD-ROM drive
Jul 7 19:52:23 vubserver ide1 at 0x170-0x177,0x376 on irq 15
Jul 7 19:52:23 vubserver hda: max request size: 128KiB
Jul 7 19:52:23 vubserver hda: 120103200 sectors (61492 MB) w/1863KiB Cache, CHS=65535/16/63, UDMA(100)
Jul 7 19:52:23 vubserver hda: cache flushes supported
Jul 7 19:52:23 vubserver /dev/ide/host0/bus0/target0/lun0: p1 p2 p3
Jul 7 19:52:23 vubserver hdb: max request size: 128KiB
Jul 7 19:52:23 vubserver hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(100)
Jul 7 19:52:23 vubserver hdb: cache flushes supported
Jul 7 19:52:23 vubserver /dev/ide/host0/bus0/target1/lun0: p1
Jul 7 19:52:23 vubserver hdc: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Jul 7 19:52:23 vubserver Uniform CD-ROM driver Revision: 3.20
Jul 7 19:52:23 vubserver hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Jul 7 19:52:23 vubserver libata version 1.02 loaded.
Jul 7 19:52:23 vubserver sata_sil version 0.54
Jul 7 19:52:23 vubserver ACPI: PCI interrupt 0000:01:0b.0[A] -> GSI 11 (level, low) -> IRQ 11
Jul 7 19:52:23 vubserver ata1: SATA max UDMA/100 cmd 0xF8854080 ctl 0xF885408A bmdma 0xF8854000 irq 11
Jul 7 19:52:23 vubserver ata2: SATA max UDMA/100 cmd 0xF88540C0 ctl 0xF88540CA bmdma 0xF8854008 irq 11
Jul 7 19:52:23 vubserver ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:207f
Jul 7 19:52:23 vubserver ata1: dev 0 ATA, max UDMA/133, 240121728 sectors:
Jul 7 19:52:23 vubserver ata1: dev 0 configured for UDMA/100
Jul 7 19:52:23 vubserver scsi0 : sata_sil
Jul 7 19:52:23 vubserver ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
Jul 7 19:52:23 vubserver ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
Jul 7 19:52:23 vubserver ata2: dev 0 configured for UDMA/100
Jul 7 19:52:23 vubserver scsi1 : sata_sil
Jul 7 19:52:23 vubserver Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
Jul 7 19:52:23 vubserver Type: Direct-Access ANSI SCSI revision: 05
Jul 7 19:52:23 vubserver Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Jul 7 19:52:23 vubserver Type: Direct-Access ANSI SCSI revision: 05
|
here's my kernel .config (only relevant snips)
| Code: |
# SCSI low-level drivers
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_SIL=y
CONFIG_SCSI_QLA2XXX=y
|
relevant output of lspci:
| Code: |
0000:01:0b.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
|
looks like I'm gonna have to wait for a future release of the love-sources. |
Somewhere in MM (not sure where), LIBATA became the default for SATA drives. From my understanding, this means all SATA drives show up under the SCSI subsystem. Your drives /dev/hde and /dev/hdg will show up instead as /dev/sd* (not sure on the leters). If you disable SATA support under SCSI Devices completely, (not at my linux right now, can't be more specific), it should re-enable the SATA drives under the IDE subsystem. However, the kernel is moving towards using LIBATA and /dev/sd* for SATA drives, so it might just be easier to change your /etc/fstab or /etc/raidtab to point to /dev/sd* you won't need to reformat, or change anything else.
 |
|
| Back to top |
|
|
HezniK
n00b
Joined: 11 Apr 2004
Posts: 61
Location: Szczecin, Poland
|
| Posted: Wed Jul 07, 2004 7:54 pm Post subject: |
|
|
hi
i got copuple of questions:
1.
| Quote: |
video=vesafb:ywrap,vram:16,1024x768-16@85 splash=silent
|
what vram:16 options is for? and how order of these options matter? is something like this:
| Code: | | video=mtrr,vram:16,vesafb:ywrap,1024x768 |
is gonna work?
2. Is with this love7 Qingy now operational? (see thread below, last page)
https://forums.gentoo.org/viewtopic.php?t=72022
cheers
_________________
------------------------------
Autor tego postu zaprzecza jakoby aktywnie dzialal w ruchu anarchistycznym. |
|
| Back to top |
|
|
Zyne
Guru
Joined: 08 Jun 2004
Posts: 334
|
| Posted: Wed Jul 07, 2004 8:01 pm Post subject: |
|
|
| sparhawk37 wrote: |
Somewhere in MM (not sure where), LIBATA became the default for SATA drives. From my understanding, this means all SATA drives show up under the SCSI subsystem. Your drives /dev/hde and /dev/hdg will show up instead as /dev/sd* (not sure on the leters). If you disable SATA support under SCSI Devices completely, (not at my linux right now, can't be more specific), it should re-enable the SATA drives under the IDE subsystem. However, the kernel is moving towards using LIBATA and /dev/sd* for SATA drives, so it might just be easier to change your /etc/fstab or /etc/raidtab to point to /dev/sd* you won't need to reformat, or change anything else.
|
I actually thought of that too while testing the new lover kernel.
However when I do ls /dev/sd* I get no results, where I used to get a result if I did ls /dev/hd*
I'm gonna try to use only the mm patches now, and see how that works out  |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Wed Jul 07, 2004 8:25 pm Post subject: qingy |
|
|
| HezniK wrote: | hi
2. Is with this love7 Qingy now operational? |
Yup, it's been working here for the last couple of releases
The syntax for the video args (and I should have remembered this earlier) is in | Code: | | /usr/src/linux/Documentation/fb/vesafb.txt |
Basically,
| Quote: | You can pass options to vesafb using "video=vesafb:option" on the kernel
command line. Multiple options should be separated by comma, like this:
"video=vesafb:ypan,1024x768-32@85" |
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
Zyne
Guru
Joined: 08 Jun 2004
Posts: 334
|
| Posted: Wed Jul 07, 2004 8:38 pm Post subject: |
|
|
| Mafteah wrote: | | Zyne wrote: | | Mafteah wrote: | | Can you tell me what kernel works for you with SATA? |
well... Unpatched 2.6.7 (what I'm running now) runs great!
I also tried 2.6.7-rc1 last week (or maybe 2 weeks ago) and that one worked great too for what I needed (no bootsplash for me)
it's actually just this one that doesn't seem to be willing to work for me. |
Can you try SATA with mm6? |
I just did that, and it still doesn't work.
so the good news is that it's not a bug in the love-sources.
The bad news however is that it's either a big in the -mm patches (not very likely) or a problem in the configuration of my kernel (very likely  ).
Problem is that I don't have the time anymore to play around with the new kernels, so I'm gonna keep the unpatched kernel for the time being
Thanks a lot for the help and all the time you put in creating the love-sources!!!!! |
|
| Back to top |
|
|
tatesworld
n00b
Joined: 25 Oct 2003
Posts: 67
|
| Posted: Wed Jul 07, 2004 8:58 pm Post subject: |
|
|
All working fine here , looking good,
mind you, me never had problem with xmms on previous release,
My splash image has gone on boot, but am working on fixing that now, maybe becouse I have linux tux logo on boot
recompiling kernel without tux to see if that fixes it |
|
| Back to top |
|
|
StuRReaL
Tux's lil' helper
Joined: 25 Oct 2003
Posts: 117
|
| Posted: Wed Jul 07, 2004 8:59 pm Post subject: |
|
|
| i've just built my kernel but just a quick question. Do these sources have supermount? and if not can they be added in the next release? please |
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
| Posted: Wed Jul 07, 2004 9:10 pm Post subject: |
|
|
| StuRReaL wrote: | | i've just built my kernel but just a quick question. Do these sources have supermount? and if not can they be added in the next release? please |
just use ivman
_________________
http://www.mafteah.co.il |
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
|
| Back to top |
|
|
teedog
Apprentice
Joined: 09 Mar 2004
Posts: 211
|
| Posted: Wed Jul 07, 2004 9:13 pm Post subject: |
|
|
| StuRReaL wrote: | | Do these sources have supermount? and if not can they be added in the next release? please |
As noted in the 2.6.7_rc1-love1 release notes:
| Quote: | | supermount is gone for GOOD, i included submount which is less evil but that's a temp fix until ivman ( http://ivman.sf.net ) gets more popular. |
|
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
| Posted: Wed Jul 07, 2004 9:25 pm Post subject: |
|
|
To fix USB problems please try:
| Code: | ===== drivers/usb/core/usb.c 1.281 vs edited =====
--- 1.281/drivers/usb/core/usb.c Wed Jun 30 09:44:26 2004
+++ edited/drivers/usb/core/usb.c Wed Jul 7 15:47:23 2004
@@ -64,6 +64,7 @@
/* Not honored on modular build */
static DECLARE_RWSEM(usb_all_devices_rwsem);
+static DECLARE_WAIT_QUEUE_HEAD(usb_all_devices_wqh);
static int generic_probe (struct device *dev)
@@ -933,6 +934,7 @@
{
up(&udev->serialize);
up_read(&usb_all_devices_rwsem);
+ wake_up(&usb_all_devices_wqh);
}
/**
@@ -940,10 +942,15 @@
*
* This is necessary when registering a new driver or probing a bus,
* since the driver-model core may try to use any usb_device.
+ *
+ * Unfortunately we have to use a separate wait queue, because we need
+ * to make sure that a thread waiting for a writelock won"t block other
+ * threads from acquiring a readlock.
*/
void usb_lock_all_devices(void)
{
- down_write(&usb_all_devices_rwsem);
+ wait_event(usb_all_devices_wqh,
+ down_write_trylock(&usb_all_devices_rwsem));
}
/**
@@ -952,6 +959,7 @@
void usb_unlock_all_devices(void)
{
up_write(&usb_all_devices_rwsem);
+ wake_up(&usb_all_devices_wqh);
}
|
_________________
http://www.mafteah.co.il |
|
| Back to top |
|
|
tatesworld
n00b
Joined: 25 Oct 2003
Posts: 67
|
|
| Back to top |
|
|
StuRReaL
Tux's lil' helper
Joined: 25 Oct 2003
Posts: 117
|
| Posted: Wed Jul 07, 2004 9:35 pm Post subject: |
|
|
| teedog wrote: | | StuRReaL wrote: | | Do these sources have supermount? and if not can they be added in the next release? please |
As noted in the 2.6.7_rc1-love1 release notes:
| Quote: | | supermount is gone for GOOD, i included submount which is less evil but that's a temp fix until ivman ( http://ivman.sf.net ) gets more popular. |
|
do i have to select submount in when i create my kernel config or not, as i did not see an option and how do i configure it in my fstab? |
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
| Posted: Wed Jul 07, 2004 9:36 pm Post subject: |
|
|
| StuRReaL wrote: | | teedog wrote: | | StuRReaL wrote: | | Do these sources have supermount? and if not can they be added in the next release? please |
As noted in the 2.6.7_rc1-love1 release notes:
| Quote: | | supermount is gone for GOOD, i included submount which is less evil but that's a temp fix until ivman ( http://ivman.sf.net ) gets more popular. |
|
do i have to select submount in when i create my kernel config or not, as i did not see an option and how do i configure it in my fstab? |
Dont use SuperMount!
Use Ivman (http://ivman.sf.net/)
_________________
http://www.mafteah.co.il |
|
| Back to top |
|
|
StuRReaL
Tux's lil' helper
Joined: 25 Oct 2003
Posts: 117
|
| Posted: Wed Jul 07, 2004 9:38 pm Post subject: |
|
|
i was asking about how to use submount not supermount or maybe you could tell me out to use the Ivman
I understand the hole DON'T USE SUPERMOUNT |
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
| Posted: Wed Jul 07, 2004 9:40 pm Post subject: |
|
|
| StuRReaL wrote: | i was asking about how to use submount not supermount or maybe you could tell me out to use the Ivman
I understand the hole DON'T USE SUPERMOUNT |
http://ivman.sf.net/ !!
_________________
http://www.mafteah.co.il |
|
| Back to top |
|
|
StuRReaL
Tux's lil' helper
Joined: 25 Oct 2003
Posts: 117
|
| Posted: Wed Jul 07, 2004 9:41 pm Post subject: |
|
|
FFS ok ok ok, looks i'll be needing to use udev too looking at the how to on these forums, i feel another kernel compile coming on  |
|
| Back to top |
|
|
Dinini
Apprentice
Joined: 11 Jun 2003
Posts: 236
|
| Posted: Wed Jul 07, 2004 9:46 pm Post subject: |
|
|
| HezniK wrote: | | Quote: |
video=vesafb:ywrap,vram:16,1024x768-16@85 splash=silent
|
what vram:16 options is for? and how order of these options matter? is something like this:
| Code: | | video=mtrr,vram:16,vesafb:ywrap,1024x768 |
is gonna work? |
To stop some confusion vesafb-tng is only coded to work with 32 bit systems. If you're on 64 bit hardware use the old vga= setup method.
The documentation is in "Documentation/fb/vesafb.txt" (which lists many more options than described here). I'll be the first to admit the upper section giving the old "vga=" setup instructions (64bit only) before the newer "video=vesafb:" section (32bit only) makes life confusing if you don't already know which section you're supposed to be looking through for information.
vram:16 limits the available video memory available for remapping to 16 MiB (which was the default with the old vesafb code) and solves many problems with video memory allocation for folks with the really nice video cards.
The format of the line is "video=vesafb:<vesa framebuffer options, separated by commas>". mtrr and vram:16 are vesafb options so they need to follow the "vesafb:" delimiter. you need to specify 16 bpp if you expect to see a bootsplash 1024x768-16, because the default is 8bpp which is not supported by bootsplash. The "mode line" is formatted as <dimension>-<bpp>@<refresh rate> so 1024x768 with 16bpp at 75Hz would be 1024x768-16@75
try | Code: | | video=vesafb:mtrr,ywrap,vram:16,1024x768-16 |
Last edited by Dinini on Wed Jul 07, 2004 9:52 pm; edited 1 time in total |
|
| Back to top |
|
|
Mafteah
Apprentice
Joined: 30 May 2003
Posts: 265
Location: IL
|
|
| Back to top |
|
|
adrenalin
Tux's lil' helper
Joined: 29 Dec 2002
Posts: 129
|
| Posted: Wed Jul 07, 2004 10:55 pm Post subject: |
|
|
i2c is broken for me with love:
| Code: | i2c /dev entries driver
: Error requesting region 5000 .. 5007 for SMB1
nForce2 SMBus 0000:00:01.1: Error probing SMB1.
: Error requesting region 5500 .. 5507 for SMB2
nForce2 SMBus 0000:00:01.1: Error probing SMB2.
|
works with 2.6.7-mm6 |
|
| Back to top |
|
|
DocterD
Tux's lil' helper
Joined: 15 May 2004
Posts: 129
|
| Posted: Wed Jul 07, 2004 11:17 pm Post subject: |
|
|
| same Error but not Only with Love. With Stardust too... (Nforce2) |
|
| Back to top |
|
|
redshift
Tux's lil' helper
Joined: 26 Nov 2003
Posts: 98
|
| Posted: Wed Jul 07, 2004 11:55 pm Post subject: |
|
|
Mafteah:
Thanks for the USB patch, but it didn't fix my problem - my MS USB keyboard won't work. My MS USB mouse is fine, but I get a "HID device not claimed by input or hiddev" message upon boot.
It works fine with 2.6.6-love5, but as soon as I boot with 2.6.7, bam. (Only changed 4k stacks and regparm in my .config - and I tried changing them back, but same problem.)
_________________
Tom |
|
| Back to top |
|
|
|
Unsupported Software
