Web lists-archives.com

Re: problem with wheezy boot?




it's not mount partition that cause problem

the display problem is so serious that I can't see anything on screen and have to reboot.

i will go out and can't use debian PC at home for about 9 hours
and may not reply soon

Thanks!


On Thursday, October 26, 2017 8:48 PM, Weaver <weaver@xxxxxxxxxx> wrote:


On 2017-10-27 10:32, Long Wind wrote:
> is it possible to disable drm during boot?
> i think it cause problem some times
> debian has ati display problem with my other PC early
> strangely the only way I know to solve it is:
> remove PC case, insert or remove some PCI card
> and then wheezy boot OK
>
> windows XP share same disk with wheezy,
>
> it never has such problem, so the problem is with wheezy
> linux isn't as stable as i thought
>
> i have tried methods below, it doesn't work
> enter BIOS menu, make some change, and reboot
>
> i want to try wheezy kernel for 486
> kernel for 686(default) and AMD all have problem
> if fail, i will have to try stretch
>
> below are msg related to problem:
>
> Oct 27 07:53:57 debian kernel: [    6.488556] saa7134[0]: registered
> device radio0
> Oct 27 07:53:57 debian kernel: [    6.565769] [drm] radeon kernel
> modesetting enabled.
> Oct 27 07:53:57 debian kernel: [    6.566363] [drm] initializing
> kernel modesetting (RS480 0x1002:0x5954 0x103C:0x3009).
> Oct 27 07:53:57 debian kernel: [    6.566402] [drm] register mmio
> base: 0xFDAF0000
> Oct 27 07:53:57 debian kernel: [    6.566407] [drm] register mmio
> size: 65536
> Oct 27 07:53:57 debian kernel: [    6.568562] [drm] Generation 2 PCI
> interface, using max accessible memory
> Oct 27 07:53:57 debian kernel: [    6.568573] radeon 0000:01:05.0:
> VRAM: 64M 0x000000007C000000 - 0x000000007FFFFFFF (64M used)
> Oct 27 07:53:57 debian kernel: [    6.568581] radeon 0000:01:05.0:
> GTT: 512M 0x0000000080000000 - 0x000000009FFFFFFF
> Oct 27 07:53:57 debian kernel: [    6.569323] [drm] Detected VRAM
> RAM=64M, BAR=128M
> Oct 27 07:53:57 debian kernel: [    6.569332] [drm] RAM width 128bits
> DDR
> Oct 27 07:53:57 debian kernel: [    6.569616] [TTM] Zone  kernel:
> Available graphics memory: 444626 kiB
> Oct 27 07:53:57 debian kernel: [    6.569622] [TTM] Zone highmem:
> Available graphics memory: 1004214 kiB
> Oct 27 07:53:57 debian kernel: [    6.569628] [TTM] Initializing pool
> allocator
> Oct 27 07:53:57 debian kernel: [    6.569641] [TTM] Initializing DMA
> pool allocator
> Oct 27 07:53:57 debian kernel: [    6.569701] [drm] radeon: 64M of
> VRAM memory ready
> Oct 27 07:53:57 debian kernel: [    6.569707] [drm] radeon: 512M of
> GTT memory ready.
> Oct 27 07:53:57 debian kernel: [    6.569746] [drm] GART: num cpu
> pages 131072, num gpu pages 131072
> Oct 27 07:53:57 debian kernel: [    6.587847] [drm] radeon: ib pool
> ready.
> Oct 27 07:53:57 debian kernel: [    6.587972] [drm] radeon: 3 quad
> pipes, 1 z pipes initialized.
> Oct 27 07:53:57 debian kernel: [    6.605644] [drm] PCIE GART of 512M
> enabled (table at 0x0000000034C00000).
> Oct 27 07:53:57 debian kernel: [    6.605701] radeon 0000:01:05.0: WB
> enabled
> Oct 27 07:53:57 debian kernel: [    6.605710] [drm] fence driver on
> ring 0 use gpu addr 0x80000000 and cpu addr 0xf7239000
> Oct 27 07:53:57 debian kernel: [    6.605718] [drm] Supports vblank
> timestamp caching Rev 1 (10.10.2010).
> Oct 27 07:53:57 debian kernel: [    6.605723] [drm] Driver supports
> precise vblank timestamp query.
> Oct 27 07:53:57 debian kernel: [    6.605746] [drm] radeon: irq
> initialized.
> Oct 27 07:53:57 debian kernel: [    6.605871] [drm] Loading R300
> Microcode
> Oct 27 07:53:57 debian kernel: [    6.626288] saa7134 ALSA driver for
> DMA sound loaded
> Oct 27 07:53:57 debian kernel: [    6.626358] saa7134[0]/alsa:
> saa7134[0] at 0xfddfe000 irq 22 registered as card -1
> Oct 27 07:53:57 debian kernel: [    6.661730] [drm] radeon: cp
> finalized
> Oct 27 07:53:57 debian kernel: [    6.661771] radeon 0000:01:05.0:
> f7195400 unpin not necessary
> Oct 27 07:53:57 debian kernel: [    6.663512] [drm] Radeon Display
> Connectors
> Oct 27 07:53:57 debian kernel: [    6.663516] [drm] Connector 0:
> Oct 27 07:53:57 debian kernel: [    6.663520] [drm]  VGA
> Oct 27 07:53:57 debian kernel: [    6.663527] [drm]  DDC: 0x68 0x68
> 0x68 0x68 0x68 0x68 0x68 0x68
> Oct 27 07:53:57 debian kernel: [    6.663531] [drm]  Encoders:
> Oct 27 07:53:57 debian kernel: [    6.663536] [drm]    CRT1:
> INTERNAL_DAC2
> Oct 27 07:53:57 debian kernel: [    6.663540] [drm] Connector 1:
> Oct 27 07:53:57 debian kernel: [    6.663544] [drm]  DVI-D
> Oct 27 07:53:57 debian kernel: [    6.663548] [drm]  HPD1
> Oct 27 07:53:57 debian kernel: [    6.663554] [drm]  DDC: 0x198 0x198
> 0x19c 0x19c 0x1a0 0x1a0 0x1a4 0x1a4
> Oct 27 07:53:57 debian kernel: [    6.663559] [drm]  Encoders:
> Oct 27 07:53:57 debian kernel: [    6.663562] [drm]    DFP1:
> INTERNAL_DVO1
> Oct 27 07:53:57 debian kernel: [    6.675572] No connectors reported
> connected with modes
> Oct 27 07:53:57 debian kernel: [    6.675581] [drm] Cannot find any
> crtc or sizes - going 1024x768
> Oct 27 07:53:57 debian kernel: [    6.682234] [drm] fb mappable at
> 0xD8040000
> Oct 27 07:53:57 debian kernel: [    6.682240] [drm] vram apper at
> 0xD8000000
> Oct 27 07:53:57 debian kernel: [    6.682244] [drm] size 3145728
> Oct 27 07:53:57 debian kernel: [    6.682248] [drm] fb depth is 24
> Oct 27 07:53:57 debian kernel: [    6.682252] [drm]    pitch is 4096
> Oct 27 07:53:57 debian kernel: [    6.682399] fbcon: radeondrmfb (fb0)
> is primary device
> Oct 27 07:53:57 debian kernel: [    6.693180] Console: switching to
> colour frame buffer device 128x48
> Oct 27 07:53:57 debian kernel: [    6.702556] fb0: radeondrmfb frame
> buffer device
> Oct 27 07:53:57 debian kernel: [    6.702561] drm: registered panic
> notifier
> Oct 27 07:53:57 debian kernel: [    6.702574] [drm] Initialized radeon
> 2.16.0 20080528 for 0000:01:05.0 on minor 0
> Oct 27 07:53:57 debian kernel: [    8.046068] EXT4-fs (sda3):
> re-mounted. Opts: (null)
> Oct 27 07:53:57 debian kernel: [    8.223826] EXT4-fs (sda3):
> re-mounted. Opts: errors=remount-ro
> Oct 27 07:53:57 debian kernel: [    8.336582] loop: module loaded
> Oct 27 07:53:57 debian kernel: [    9.258764] FAT-fs (sda5): utf8 is
> not a recommended IO charset for FAT filesystems, filesystem will be
> case sensitive!
> Oct 27 07:53:57 debian kernel: [    9.306737] FAT-fs (sda6): utf8 is
> not a recommended IO charset for FAT filesystems, filesystem will be
> case sensitive!
> Oct 27 07:53:57 debian kernel: [    9.331055] FAT-fs (sda7): utf8 is
> not a recommended IO charset for FAT filesystems, filesystem will be
> case sensitive!
> Oct 27 07:53:57 debian kernel: [  10.616226] ADDRCONF(NETDEV_UP):
> eth0: link is not ready
> Oct 27 07:53:58 debian kernel: [  12.222717] tg3 0000:02:00.0: eth0:
> Link is up at 100 Mbps, full duplex
> Oct 27 07:53:58 debian kernel: [  12.222728] tg3 0000:02:00.0: eth0:
> Flow control is on for TX and on for RX
> Oct 27 07:53:58 debian kernel: [  12.223068] ADDRCONF(NETDEV_CHANGE):
> eth0: link becomes ready
> Oct 27 07:55:31 debian shutdown[2307]: shutting down for system reboot


FAT-fs?

Why not msdos?

--
"It is the duty of the patriot to protect his country from its
government."
-- Thomas Paine

Registered Linux User: 554515